[plasmashell] [Bug 369606] Calender: PIM events no longer shown

2016-10-05 Thread Fuchs via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=369606

--- Comment #1 from Fuchs  ---
This is still present in plasma 5.8 final.

-- 
You are receiving this mail because:
You are watching all bug changes.


[plasmashell] [Bug 369606] Calender: PIM events no longer shown

2016-10-05 Thread Fuchs via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=369606

--- Comment #2 from Fuchs  ---
Update: 

this seems to be a duplicate of https://bugs.kde.org/show_bug.cgi?id=368832

However, this is valid not only for CalDAV calendars, but also for integrated
ones such as the Birthday / Events one. 

I can indeed reproduce that updating the calendar does fix the issue (emitting
a signal to update, maybe?) but initially when loaded no events are shown. So
whatever you do on an update, you probably should do that initially as well.

-- 
You are receiving this mail because:
You are watching all bug changes.


[Breeze] [Bug 364931] Regression: Status icon for "not available" (presence) seems to be lacking

2016-06-30 Thread Fuchs via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=364931

--- Comment #1 from Fuchs  ---
Created attachment 99770
  --> https://bugs.kde.org/attachment.cgi?id=99770&action=edit
missing icon

-- 
You are receiving this mail because:
You are watching all bug changes.


[Breeze] [Bug 364931] New: Regression: Status icon for "not available" (presence) seems to be lacking

2016-06-30 Thread Fuchs via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=364931

Bug ID: 364931
   Summary: Regression: Status icon for "not available" (presence)
seems to be lacking
   Product: Breeze
   Version: 5.6.95
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Icons
  Assignee: visual-des...@kde.org
  Reporter: deve...@fuchsnet.ch
CC: kain...@gmail.com

The icon for the "not available" presence seems to be lacking since the most
recent Frameworks / Plasma update.

Reproducible: Always

Steps to Reproduce:
1. Update to the latest frameworks / plasma packages
2. Open something that has presence icons, e.g. the KDE Telepathy contact list
or plasmoid
3. Check for the "not available" status

Actual Results:  
Icon is missing

Expected Results:  
Icon is there

-- 
You are receiving this mail because:
You are watching all bug changes.


[Breeze] [Bug 364931] Regression: Status icon for "not available" (presence) seems to be lacking

2016-07-02 Thread Fuchs via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=364931

--- Comment #3 from Fuchs  ---
This is very odd, 

fuchs@minixfox status % pwd
/usr/share/icons/breeze/status
fuchs@minixfox status % find . | grep user-away-extended
./16/user-away-extended.svg
./22/user-away-extended.svg


and it looks correct when I open it with an image viewer. It, however, is
lacking both in plasma and in the application  (the contact list)

-- 
You are receiving this mail because:
You are watching all bug changes.


[Breeze] [Bug 364931] Regression: Status icon for "not available" (presence) seems to be lacking

2016-07-02 Thread Fuchs via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=364931

--- Comment #6 from Fuchs  ---
Thanks for the quick fix ♥

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 365011] New: Regression: Launcher for eclipse broken

2016-07-02 Thread Fuchs via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=365011

Bug ID: 365011
   Summary: Regression: Launcher for eclipse broken
   Product: plasmashell
   Version: 5.5.95
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Icons-only Task Manager
  Assignee: h...@kde.org
  Reporter: deve...@fuchsnet.ch
CC: plasma-b...@kde.org

When I add a launcher for eclipse in the icon only task manager, it behaves
very weird. It is shown as long as the application is running, then hides and
is re-shown when I start the application, is shown while the application is
running and disappears when I restart the application. 

When re-starting eclipse afterwards, the launcher re-appears where it was
placed before.

Reproducible: Always

Steps to Reproduce:
1. Download eclipse from eclipse.org
2. Install and launch it
3. Right click and add a launcher for when the application is not running
4. Exit and restart eclipse

Actual Results:  
Launcher misbehaving as described above

Expected Results:  
Launcher behaving correctly

-- 
You are receiving this mail because:
You are watching all bug changes.


[plasmashell] [Bug 365011] Regression: Launcher for eclipse broken

2016-07-03 Thread Fuchs via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=365011

--- Comment #2 from Fuchs  ---
Hi Eike, 

I assume you mean

[Containments][1][Applets][96][Configuration][General]
launchers=file:///usr/share/applications/org.kde.konsole.desktop,file:///usr/share/applications/org.kde.dolphin.desktop,file:///home/fuchs/.local/share/applications/firefox.desktop,file:///usr/share/applications/google-chrome-beta.desktop,file:///usr/share/applications/org.kde.konversation.desktop,file:///usr/share/applications/kde4/amarok.desktop,file:///usr/share/applications/smplayer.desktop,file:///home/fuchs/.local/share/applications/org.kde.kate.desktop,file:///home/fuchs/.local/share/applications/Eclipse.desktop,file:///usr/share/applications/libreoffice-writer.desktop,file:///usr/share/applications/libreoffice-calc.desktop,file:///usr/share/applications/libreoffice-impress.desktop,file:///usr/share/applications/org.kde.kontact.desktop,file:///home/fuchs/.local/share/applications/VirtualBox.desktop


this one, from .config/plasma-org.kde.plasma.desktop-appletsrc. 

Thanks for having a look

-- 
You are receiving this mail because:
You are watching all bug changes.


[Breeze] [Bug 365035] New: Regression: folder-tar and folder-scripts missing on smallest size

2016-07-03 Thread Fuchs via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=365035

Bug ID: 365035
   Summary: Regression: folder-tar and folder-scripts missing on
smallest size
   Product: Breeze
   Version: 5.6.95
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Icons
  Assignee: visual-des...@kde.org
  Reporter: deve...@fuchsnet.ch
CC: kain...@gmail.com

Yet another missing icon regression: 

folder-tar and folder-script are lacking at the smallest icon size, which is
especially bad as the default select folder dialogue needs these. See
screenshot.

Reproducible: Always

Steps to Reproduce:
1. Define folders with the above mentioned icons
2. Either open a folder chooser or dolphin with the smallest icon size


Actual Results:  
Icons are missing

Expected Results:  
Icons are displayed

-- 
You are receiving this mail because:
You are watching all bug changes.


[Breeze] [Bug 365035] Regression: folder-tar and folder-scripts missing on smallest size

2016-07-03 Thread Fuchs via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=365035

--- Comment #1 from Fuchs  ---
Created attachment 99823
  --> https://bugs.kde.org/attachment.cgi?id=99823&action=edit
Screenshot of the issue

-- 
You are receiving this mail because:
You are watching all bug changes.


[plasmashell] [Bug 365011] Regression: Launcher for eclipse broken

2016-07-04 Thread Fuchs via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=365011

--- Comment #4 from Fuchs  ---
(In reply to Eike Hein from comment #3)
> Some additional questions/requests:

Sure

> 1. Did you add the launcher using step #3, or did you go via the menu?

I tried both via the menu and via a right click on an existing instance. The
result is the same.

> 2. Did you do it using Plasma 5.6.x or 5.7 (beta)?

This only happens with 5.7 (beta) and I added it there.

> 3. How did you install Eclipse?

With the provided graphical installer when you download it from eclipse.org

Questions 4 and 5 I can't answer before this evening, as currently I have my
work laptop, which has Plasma 5.6 where it works as expected. 

Kind regards, 

Christian

-- 
You are receiving this mail because:
You are watching all bug changes.


[plasmashell] [Bug 365011] Regression: Launcher for eclipse broken

2016-07-04 Thread Fuchs via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=365011

--- Comment #6 from Fuchs  ---
(In reply to Eike Hein from comment #5)
> ^ The reason I asked #3 is because the Eclipse installer didn't put a
> .desktop file into ~/.local for me, so I don't have Eclipse in the menu at
> all.

Odd, maybe that is a leftover, but I will try removing it this evening to see
if that helps. 

> I admit I also have some trouble understanding your first paragraph though,
> it gets a bit confusing to follow. Could you reformat the exact order of
> events in chronological bullets, and be a bit harder on your terminology
> going by the following explanation: A launcher is what's shown before a
> window appears. When a window appears, a launcher should be replaced by the
> window. When the window is closed, it should be replaced by the launcher. I
> need to know the exact sequence of when that intended behavior breaks down,
> and how.

Sure: 

1) Add launcher  (no matter how, let's say via menu for now)
2) Place it somewhere in the middle of other launchers, to see the effect
described later better
3) Click on the launcher: Eclipse starts with the splash screen
4) The launcher quickly disappears and is then replaced with the window, still
at the position in the taskbar where you placed it
5) Exit eclipse
6) The window disappears, the launcher is not there afterwards (there is no
empty space, the launchers that were to the right of it just move to the left
as if it was not there)
7) Start eclipse again  (via krunner or something, since you no longer have the
launcher) 
8) The running window appears where the launcher was before  (not at the right
where new windows without launchers would appear)

-- 
You are receiving this mail because:
You are watching all bug changes.


[plasmashell] [Bug 365011] Regression: Launcher for eclipse broken

2016-07-04 Thread Fuchs via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=365011

--- Comment #8 from Fuchs  ---
(In reply to Eike Hein from comment #7)
> Thanks, that was super helpful. Do you know which version of Plasma 5.7 you
> have exactly? Is it the beta, or a git build?

It's the gentoo plasma-*-5.6.95.ebuild which is built out of tarballs, so
whatever was in these. 

> If it's a git build, do you
> know if you have cc2b38b4? That commit from June 30th might have actually
> addressed this.

I can try to find some time this week to re-compile it with that commit as a
patch to see if that helps.

> Otherwise, when you get home to your system, aside from #4 and #5 it might
> also help to just attach that .desktop file for me, too.

Shall do that, thanks so far.

-- 
You are receiving this mail because:
You are watching all bug changes.


[Oxygen] [Bug 352118] Baloo 5.13.0: tags in tags:/ kioslave don't have an icon

2016-07-04 Thread Fuchs via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=352118

--- Comment #4 from Fuchs  ---
Sorry, this seems to be fixed in recent versions. 
As I don't have a vanilla KDE at hand: 

if the entries in   tags:/have an icon, this is fixed and can be closed.
Works here. 

Thanks :)

-- 
You are receiving this mail because:
You are watching all bug changes.


[plasmashell] [Bug 365011] Regression: Launcher for eclipse broken

2016-07-04 Thread Fuchs via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=365011

--- Comment #9 from Fuchs  ---
[Desktop Entry]
Comment=Eclipse IDE
Exec=/home/fuchs/bin/eclipse/java-neon/eclipse/eclipse.sh
GenericName=Eclipse IDE
Icon=/opt/eclipse/icon.xpm
Name=Eclipse
NoDisplay=false
Path[$e]=
StartupNotify=true
Terminal=0
TerminalOptions=
Type=Application
X-KDE-SubstituteUID=false
X-KDE-Username=



_NET_WM_USER_TIME(CARDINAL) = 825123
_NET_WM_ICON_GEOMETRY(CARDINAL) = 812, 862, 48, 36
_NET_WM_ALLOWED_ACTIONS(ATOM) = _NET_WM_ACTION_MOVE, _NET_WM_ACTION_RESIZE,
_NET_WM_ACTION_MINIMIZE, _NET_WM_ACTION_SHADE, _NET_WM_ACTION_MAXIMIZE_VERT,
_NET_WM_ACTION_MAXIMIZE_HORZ, _NET_WM_ACTION_FULLSCREEN,
_NET_WM_ACTION_CHANGE_DESKTOP, _NET_WM_ACTION_CLOSE
_KDE_NET_WM_FRAME_STRUT(CARDINAL) = 4, 4, 24, 4
_NET_FRAME_EXTENTS(CARDINAL) = 4, 4, 24, 4
_NET_WM_DESKTOP(CARDINAL) = 4
_KDE_NET_WM_ACTIVITIES(STRING) = "fb3af15a-efba-4fde-acd9-7272ef5ea170"
WM_STATE(WM_STATE):
window state: Normal
icon window: 0x0
_NET_WM_STATE(ATOM) = 
WM_HINTS(WM_HINTS):
Client accepts input or input focus: True
Initial state is Normal State.
bitmap id # to use for icon: 0x6e0003a
bitmap id # of mask for icon: 0x6e00040
window id # of group leader: 0x6e1
XdndAware(ATOM) = BITMAP
_NET_WM_ICON(CARDINAL) = 
_KDE_NET_WM_USER_CREATION_TIME(CARDINAL) = 753181
_NET_WM_OPAQUE_REGION(CARDINAL) = 0, 0, 1559, 798
_NET_WM_WINDOW_TYPE(ATOM) = _NET_WM_WINDOW_TYPE_NORMAL
_NET_WM_SYNC_REQUEST_COUNTER(CARDINAL) = 115343416, 115343417
_NET_WM_USER_TIME_WINDOW(WINDOW): window id # 0x6e00037
WM_CLIENT_LEADER(WINDOW): window id # 0x6e1
_NET_WM_PID(CARDINAL) = 18309
WM_LOCALE_NAME(STRING) = "de_CH.UTF-8"
WM_CLIENT_MACHINE(STRING) = "foxpad"
WM_NORMAL_HINTS(WM_SIZE_HINTS):
program specified minimum size: 545 by 26
program specified base size: 0 by 0
window gravity: NorthWest
WM_PROTOCOLS(ATOM): protocols  WM_DELETE_WINDOW, WM_TAKE_FOCUS, _NET_WM_PING,
_NET_WM_SYNC_REQUEST
WM_CLASS(STRING) = "Eclipse", "Eclipse"
WM_ICON_NAME(STRING) = "eclipse - Java - isola/src/isola/gui/GameViewer.java -
Eclipse "
_NET_WM_ICON_NAME(UTF8_STRING) = "eclipse - Java -
isola/src/isola/gui/GameViewer.java - Eclipse "
WM_NAME(STRING) = "eclipse - Java - isola/src/isola/gui/GameViewer.java -
Eclipse "
_NET_WM_NAME(UTF8_STRING) = "eclipse - Java -
isola/src/isola/gui/GameViewer.java - Eclipse "


Currently trying to get a more recent icons only task manager, unfortunately I
can't patch in the commit you mentioned as it depends on others, trying to
compile the whole -workspace and -desktop from 5.7 and hoping it doesn't break.

-- 
You are receiving this mail because:
You are watching all bug changes.


[plasmashell] [Bug 365011] Regression: Launcher for eclipse broken

2016-07-04 Thread Fuchs via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=365011

--- Comment #10 from Fuchs  ---
Unfortunately the 5.7 tarball does not fix the issue.

What I also tried is removing said .desktop file and going through the steps,
then I get

launchers=file:///usr/share/applications/org.kde.konsole.desktop,file:///usr/share/applications/org.kde.dolphin.desktop,file:///home/fuchs/.local/share/applications/firefox.desktop,file:///usr/share/applications/google-chrome-beta.desktop,file:///usr/share/applications/org.kde.konversation.desktop,file:///home/fuchs/.local/share/applications/Mattermost.desktop,file:///usr/share/applications/kde4/amarok.desktop,file:///usr/share/applications/smplayer.desktop,file:///home/fuchs/.local/share/applications/org.kde.kate.desktop,file:///opt/oracle-jdk-bin-1.8.0.92/jre/bin/java?iconData=iVBORw0KGgoNSUhEUgAAADAwCAYAAABXAvmHCXBIWXMAAA7EAAAOxAGVKw4bAAAIgElEQVRoge1aW2xUxxn-_jnn7M2XXV9wDHidrUOpgkBsblUVKdiRojZppWIe2j5iKuUh4gFQWkV9aI3VSo1oU0Ndx33DVt8aVYa2ShSBFNPQC1IjFpWqmIvZYIjtsPbuer3nfmb6sBfvrvdib4x5ySfPas_M_P9831zOzP5j4Es8XtAXdRAfDgVcstPHQGFitF8IHiBQxBHiEpOliPeNaHQTeFZEXQK0sVBIOLyfAYcFEAYAIjonwM-_NhaP_v2WFRZAL4AAMuWBAvMEgIgQIsqIroHzKcuyIlsiQBsLheDwQQADWeMEgPG3L6rnf_FB6qAA-hvc7SGfuw0-
 
Vzs8SjMYU9b4sRwVlq1BNWNY0eahWckoAedkojO6rkc3XUB8OBTwKnxQAMfzhkTn3r6QPvPLD61jjFh_a2MP_L5gWcK1YDkqkuoskulZmHZ6XGFsaL1CagrQRkJ9IH4WQChrkPjfgnPihVOx_RJTjnf498LvC26YdCXEV2YQS03DEfaQresna9WvKkAbDQ5A0NmCypFXf7904vIta7i1sSfc3vS1unq8Fji3MBe_ipQ-H5GJDlUbjYoC9N91D5dOmQO_WZq49pk42-HfG9jMXq-EpDqLufjVBHH-cqWFXlaANtJ9EoTBfCWic01vLpxnJJ_tbn8RbsX_qDivgWElcS_2jwS3jbIiWGmGNhocKCIPRF4dWzzDSB7eavIA4Fb86G5_McBk90eKooRLy4sErIyGwiRoOPdMQOJP17Qjl29Zkztbvx7YavI5uBU_Ovx7A5yxSRTvKcUCZMHPioIKjhBHfvgH9bcd_j0Bn7tti-iWh98XRHvTrpDs9o4X5ucFaKPBgdyumoGYCvz4YYvX3f5Sa-OuLSNaDdua98CrNB-UPZ6-XF5eQOHUAQAIaYggnezwP711DNeBjsA-EGg898yAfO8XzC0x1fLW4q7Wpl3dLrlpy0lWg9fVAr8v-KTH1_Q6kBVAgo4VVuICZ9xK08lm787HwbEmAg0hKJLvdQCQsyfL_NwnIBF4a3l2R9tTO5_q6YHX54HX64YsSaseCKDMR00IAQAi-ydKSglUxZcQObvMd8dxYBoWdN2EcWP-BcDZLQuH9xfaCuCcAvlbvQcOoP_gdxF-djd2dHXA5ZJBVP_PByFKyRfIqOI3Z0dE4A5HLJbAzel7GB018ef33_sBY0S9BeQBEpcEnO_s27cH23e0w9fgqZt0KclKaT12AECM0NzcgK6uDjz__H4wsJdkIUTR7uZAihBo7-KCjgsf_guNDV643AoYW7NpPxY4Doem6lhYWIEA75KRPSYDmWnYeDR6zd_c3fzX8
 
x-XdcBIKpv_KMGFU6GEnpZLs3w-_3MBfxu-ursbLrcCj8cNxrLDTI9PgOCZtSCEyCxiw0TK7kKpgCiR1BYMbsfRE99H95OdeKKzDW6PC4osgVjtObseFC5MIURNn5k3EIdl2jBME4mlFO7OPMBPf3ZjjYAio5xaxgiSxCB98SBGnni579XAiCAgYJk2bNsBz45IqYCQEM7i7P05vHv6PbjcChRFBmMMjBEYk6DIm_NW2ggsWwPnPD8SpmnBNG08eDC_dgRUNflJMrmEWzfvrXFEIHg9gTX5jxqqHi-bH4s_gExApPAUqo2Eerf9REsd-t7LTa2tzXB7XEVGiux7tGxLIISA7Wj5Z8fhWF5O49bNGXz6l8vTMoiiyO4FAgAxJwSGKy3trlde-eY3sLNrG3wNXsgyA2NsUxZxPSIEF7AdB5ZlI_Z5AhPjfwSRdINxIS7lKhIACOrlNp-6cuXfmLlzH9G7c1haTMIwLAguqh4JihqskuoSAQHucBi6ibnPYrhy5RMA4hJlo213M5UABiQCP0o-5_O039nR-mxZZw3ebZAl97qaLcbGRs-yVaj6UtmyufhV6KbTyTLBVzFV0GQg_k7zAdWMXdetZFljzYiDkbSuRNmUeWbrtwNBMxJl21eNRRhO6mI6fXeBZTtmoqh_BA473HgntnyjrAPObWhGAsSkGkkGyybKp1o2maQaSxCCl20_od6D5eingOwPGu_R2XEA0dUq1Lf8q85oSl-Iqkb5IdTNJEwrne_hzUy6kfFdDml9ASntwd-MdPJCXkCGsxgqqknOIBEd-Tx5vawjAFhRF2BaK2Akb1pStRhUfbFse5xbmE_8BwIiH7fKC8iMwupaAKhv-dcdYd1aPv8w-d-KIlLpOaTUuYwzJtWdAGA5fR-aUX7TAoCF5HVYjnra1vU8z-JDviQdycb8c4WDH7zhPx1buRNNqrMVHetGArHETehGcsPTRQggrT1ELHEThpmq2EZSnUVSnY
 
3YhlE0U9a819IjwX5GNFlQIReRnvxKR2_N6BwjCV5PGzzuAFxK-YiGEDYMMwXdTMIwElXO-6vk5-JXEzLRM6WR6vLB3Qph9X_eweT2lmcCjZ7Oqg0WQpLckKXV44hlqTUJlyNfKUJdcWepcjcw-YR_b6ClsWfdJOpFLDWNh8vTUcb5oQ2F13PQRoMDJGg4F_QiIPLxbfPEa2PxQZ-7vW97SxiKtPmHO8tRMRePQDViU7ZhHELBuixFzb19ZTQUzgZ9w1mDBAeG_G8ugDFlsKWxJ9Da0LMpNzWcW1hKzyC2PJ0gYMgyjNO1bNZ9ONFGuk8S4dhqCFJMXb5tDb367tJhWXIN-H1B-H3Buu4PDCuJpZUZrOjzCUfYZ2xdP40qvV6XACBzW-mR-fFiIRi_fNuc-PZYPCyAw4rkCzd5O-FW_FAk35qrVs4t6NYyLEeFasSgGouwHDVCwIRlGOPrJV6XgCIhLqefwA4KIfqzjiIcmDh1UY38_P3lADEWhhC9FZ0QXRKcRxzTnNoo6SI39RoWQhsJ9QniYRIIgEQvQFEIfAqZjT_qfzX4Eo8b_wc7ZAiON6qONABJRU5ErkJggg%3D%3D,file:///usr/share/applications/libreoffice-writer.desktop,file:///usr/share/applications/libreoffice-calc.desktop,file:///usr/share/applications/libreoffice-impress.desktop,file:///usr/share/applications/org.kde.kontact.desktop,file:///home/fuchs/.local/share/applications/VirtualBox.desktop

and again the same behaviour as before. Interesting: if I log out of plasma and
back in, the launcher is shown until I actually launch eclipse, then it is
replaced by the window and then, on close, gone again :(

-- 
You are receiving this mail because:
You are watching all bug changes.


[plasmashell] [Bug 365011] Regression: Launcher for eclipse broken

2016-07-04 Thread Fuchs via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=365011

--- Comment #12 from Fuchs  ---
(In reply to Eike Hein from comment #11)
> Do you have more than one Task Manager? (e.g. multiple panels on different
> screens)

Not knowingly, no.  One screen (notebook), one panel, one icons only task
manager. I'll check the configuration for dead entries as soon as I am home, I
can just grep for panel and a configuration value of icon only tasks.

-- 
You are receiving this mail because:
You are watching all bug changes.


[plasmashell] [Bug 365011] Regression: Launcher for eclipse broken

2016-07-05 Thread Fuchs via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=365011

--- Comment #13 from Fuchs  ---
As mentioned on IRC: 

there were leftovers of old icon tasks (not panels, as far as I am aware) in
the appletsrc. 
Re-creating a new one meant losing all of my plasmoids and their configuration,
but for now I am no longer able to reproduce it. 

As you are able to reproduce it (with slightly different steps) and it still
being a valid bug: I'll leave it in it's current state (NEEDSINFO) and wish you
the best of luck to fix it. Thanks for looking into it.

-- 
You are receiving this mail because:
You are watching all bug changes.


[kmail2] [Bug 365138] New: Regression: new taskbar icon hard to read on both default themes

2016-07-06 Thread Fuchs via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=365138

Bug ID: 365138
   Summary: Regression: new taskbar icon hard to read on both
default themes
   Product: kmail2
   Version: Git (master)
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: UI
  Assignee: kdepim-b...@kde.org
  Reporter: deve...@fuchsnet.ch

Kmail now features a new icon  (monochrome) when there are unread mails. 
However, it is very hard to read with both default themes (see screenshots). 

Reproducible: Always

Steps to Reproduce:
1. Update to the latest kmail version
2. Configure kmail to show unread mails in the systray
3. Have an unread mail

Actual Results:  
Hard to spot and read

Expected Results:  
Easy to spot and read

-- 
You are receiving this mail because:
You are watching all bug changes.


[kmail2] [Bug 365138] Regression: new taskbar icon hard to read on both default themes

2016-07-06 Thread Fuchs via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=365138

--- Comment #1 from Fuchs  ---
Created attachment 99876
  --> https://bugs.kde.org/attachment.cgi?id=99876&action=edit
screenshot of the issue with breeze and breeze-dark

-- 
You are receiving this mail because:
You are watching all bug changes.


[Breeze] [Bug 365035] Regression: folder-tar and folder-scripts missing on smallest size

2016-07-16 Thread Fuchs via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=365035

--- Comment #5 from Fuchs  ---
Hmm, did the fix not make it into Plasma 5.7.1 / frameworks 24? 
While the other icons I reported are fixed, these two appear to be still broken
in dolphin.

-- 
You are receiving this mail because:
You are watching all bug changes.


[plasmashell] [Bug 365740] New: Regression: player controls no longer show for amarok

2016-07-16 Thread Fuchs via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=365740

Bug ID: 365740
   Summary: Regression: player controls no longer show for amarok
   Product: plasmashell
   Version: 5.7.1
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Icons-only Task Manager
  Assignee: h...@kde.org
  Reporter: deve...@fuchsnet.ch
CC: plasma-b...@kde.org

Since the 5.7.1 update I no longer have player controls in the tooltip of the
amarok task. 

The controls are available in the media player control plasmoid (that you can
place in the systray), so mpris and amarok seem to work. Other applications,
such as smplayer, work as expected.

Reproducible: Always

Steps to Reproduce:
1. Update to the lastest plasma
2. Have an amarok entry in the icons only task manager
3. Run amarok
4. Mouse hover

Actual Results:  
Player controls are missing

Expected Results:  
Player controls are there

Frameworks is 5.24, amarok is 2.8.90

-- 
You are receiving this mail because:
You are watching all bug changes.


[Spectacle] [Bug 365741] New: Rectangle selection screenshot: preview is missing on small sizes

2016-07-16 Thread Fuchs via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=365741

Bug ID: 365741
   Summary: Rectangle selection screenshot: preview is missing on
small sizes
   Product: Spectacle
   Version: unspecified
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: General
  Assignee: m...@baloneygeek.com
  Reporter: deve...@fuchsnet.ch

The rectangle selection bug seems to be partially back: 

Whenever you choose the rectangle selection and only select a small area  (in
my case: the popup of taskmanager) no preview is shown. However, if you save
the image the contents are actually there.

Reproducible: Always

Steps to Reproduce:
1. Open spectacle
2. Choose rectangle region
3. Take screenshot of smaller region


Actual Results:  
No preview  (empty area) available, saving the image, however, works

Expected Results:  
Preview available

This seems to only happen with rectangle selection, I can't reproduce it with
e.g. current window and a very small window.

Spectacle is 16.04.3 from gentoo, GPU is nvidia (because that mattered in the
last similar bug, where contents where not saved however)

-- 
You are receiving this mail because:
You are watching all bug changes.


[plasmashell] [Bug 365740] Regression: player controls no longer show for amarok

2016-07-17 Thread Fuchs via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=365740

--- Comment #2 from Fuchs  ---
Do you happen to have a commit link so I can fix it locally? I can't find that
on amarok's gitweb. 

Also: as it worked in 5.7.0 and stopped in 5.7.1, I propose that the old,
working method is used until there is an amarok release containing that fix.

-- 
You are receiving this mail because:
You are watching all bug changes.


[plasmashell] [Bug 365740] Regression: player controls no longer show for amarok

2016-07-17 Thread Fuchs via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=365740

--- Comment #4 from Fuchs  ---
(In reply to Kai Uwe Broulik from comment #3)
> The commit that changed this behavior is [1] which was in *before* the 5.7.0
> final release, so this is not a regression that occured in 5.7.1.

Odd, because it worked for me in 5.7.0 and only broke after updating to 5.7.1.
I shall assume packaging, then.

> The previous method used by just using the DBus service name was
> insufficient and wrong and worked purely by chance with Amarok but did not
> with eg. Dragon Player, Nuvola, and others. The new approach is correct by
> asking the application what its desktop file name is and if Amarok lies to
> us this is solely Amarok's fault.

End users simply won't care whose fault it is. It worked, it no longer works,
they see the error in plasma. So at least a workaround would be nice, because
fixing it does not only require it being commited to amarok (which, as far as I
can see, didn't happen yet) but also someone making a release out of that and
it ending up with packagers. That might take a while, given amarok activity,
and in the meantime it stays broken for users.

As a minor sidenote: as I wrote it works in the media player control plasmoid,
so either that one uses what you consider a wrong method to, or it has a way
which would not break it, maybe that's worth being investigated.

> [1]
> https://quickgit.kde.org/?p=plasma-desktop.
> git&a=commit&h=0d6442d8374f87880de2aad044cd1563ed6fde75

-- 
You are receiving this mail because:
You are watching all bug changes.


[plasmashell] [Bug 365740] Regression: player controls no longer show for amarok

2016-07-17 Thread Fuchs via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=365740

--- Comment #5 from Fuchs  ---
Thinking of it, probably the applet only works because it doesn't have to do a
match between application and dbus, so that one is not an option. Ignore that
part, rest still valid.

-- 
You are receiving this mail because:
You are watching all bug changes.


[frameworks-frameworkintegration] [Bug 365938] New: Setting the application language does not affect some framework controls

2016-07-21 Thread Fuchs via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=365938

Bug ID: 365938
   Summary: Setting the application language does not affect some
framework controls
   Product: frameworks-frameworkintegration
   Version: 5.24.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdelibs-b...@kde.org
  Reporter: deve...@fuchsnet.ch

If you set the language of an application (via Help -> Switch Application
Language, usually) not all controls follow the language. 

Some of them (shared ones, such as context menus of text boxes) still follow
the system language, which makes the application language inconsistent.

The sample I choose to reproduce this with is  "konversation", but according to
developers it also affects other applications, such as systemsettings

Reproducible: Always

Steps to Reproduce:
1. Open Konversation
2. Switch the language of the application to something that isn't the system
language (in my case: Swiss German is the system language, Konversation is set
to English)
3. Restart konversation
4. Right click into the text input field to make the context menu pop up

Actual Results:  
Half of the entries are system language / German (shared ones), half of the
entries are English (the ones added by the application)

Expected Results:  
All entries are in the language chosen for that specific application

-- 
You are receiving this mail because:
You are watching all bug changes.


[frameworks-frameworkintegration] [Bug 365938] Setting the application language does not affect some framework controls

2016-07-21 Thread Fuchs via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=365938

--- Comment #1 from Fuchs  ---
Created attachment 100232
  --> https://bugs.kde.org/attachment.cgi?id=100232&action=edit
Screenshot of the issue, demonstrated in konversation

-- 
You are receiving this mail because:
You are watching all bug changes.


[dolphin] [Bug 366203] Information panel: scroll bar has ugly background

2016-07-28 Thread Fuchs via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=366203

--- Comment #1 from Fuchs  ---
Created attachment 100350
  --> https://bugs.kde.org/attachment.cgi?id=100350&action=edit
Screenshot of the issue

-- 
You are receiving this mail because:
You are watching all bug changes.


[dolphin] [Bug 366203] New: Information panel: scroll bar has ugly background

2016-07-28 Thread Fuchs via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=366203

Bug ID: 366203
   Summary: Information panel: scroll bar has ugly background
   Product: dolphin
   Version: 15.12.3
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: panels: information
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: deve...@fuchsnet.ch

The information panel uses a scrollbar which has a background of a different
(darker shade) colour than the Qt control around it. 

See screenshot. 

In the folders and places panels, the correct scrollbar is used.

Reproducible: Always

Steps to Reproduce:
1. Open Dolphin
2. Have the information sidebar shown
3. Make sure there is a scrollbar

Actual Results:  
Scrollbar has an ugly background colour

Expected Results:  
Scrollbar has the standard background colour  (as in the places or folders
panel)

-- 
You are receiving this mail because:
You are watching all bug changes.


[plasmashell] [Bug 369606] New: Calender: PIM events no longer shown

2016-10-01 Thread Fuchs via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=369606

Bug ID: 369606
   Summary: Calender: PIM events no longer shown
   Product: plasmashell
   Version: 5.7.95
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Digital Clock
  Assignee: plasma-b...@kde.org
  Reporter: deve...@fuchsnet.ch

The PIM events plugin is loaded and the list of calendars is shown correctly,
however, in the pop-up calendar itself no events are shown. 

On the console I get a 

"log_akonadicore: Job error:  "Collection does not exist" for collection:
QVector() " 

error message.

Reproducible: Always

Steps to Reproduce:
1. Enable PIM support in the settings
2. Enable and of your calendars

Actual Results:  
Events are not shown

Expected Results:  
Events are shown

KDEPIM-addons is 16.08.1

-- 
You are receiving this mail because:
You are watching all bug changes.


[Bluedevil] [Bug 371492] New: Receiving files via bluetooth fails

2016-10-22 Thread Fuchs via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=371492

Bug ID: 371492
   Summary: Receiving files via bluetooth fails
   Product: Bluedevil
   Version: 5.8.2
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: daemon
  Assignee: now...@gmail.com
  Reporter: deve...@fuchsnet.ch

Receiving files via bluetooth no longer works, both trying to send from my
mobile phone (Galaxy S4 with android) and a different Laptop  (KDE Plasma 5.6)
sending the file fails

Reproducible: Always

Steps to Reproduce:
1. Try to send a file to plasma desktop with bluedevil


Actual Results:  
Sending the file fails 

Expected Results:  
Sending the file succeeds

It doesn't matter whether the other device is authorized / trusted or not.
There is no dialogue to accept / deny the file, and if auto-accept is set to
trusted or even all devices, the file is still not accepted. 

The icon in the systray briefly changes and that's it. There are no log entries
to be found in the usual places. 

Sending a file from that PC works, also does media control with the very same
other device. It is just receiving files that fails.

Bluez:5.42
Bluez-Qt: 5.27.0
Qt: 5.7.0

-- 
You are receiving this mail because:
You are watching all bug changes.


[Bluedevil] [Bug 371492] Receiving files via bluetooth fails

2016-10-22 Thread Fuchs via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=371492

--- Comment #2 from Fuchs  ---
(In reply to David Rosca from comment #1)
> Is there anything bluetooth related in the syslog? (dmesg / journalctl)

Nothing dmesg, 
journalctl has a couple of 

Okt 22 20:57:00 foxpad bluetoothd[462]: connect error: Host is down (112)

however, this is not triggered by a failed receive (I just tried sending two
files and re-opened journalctl, nothing has been added, neither does when I
watch it live) 

As said: the icon quickly changes (with the dots left and right of the icon),
so something happens, but then silently fails.

-- 
You are receiving this mail because:
You are watching all bug changes.


[Bluedevil] [Bug 371492] Receiving files via bluetooth fails

2016-10-22 Thread Fuchs via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=371492

--- Comment #4 from Fuchs  ---
(In reply to David Rosca from comment #3)
> Is "obexd" running? If not, please try to manually start it and send the
> file to PC again.

fuchs  887  0.0  0.0  80452  6612 ?S20:24   0:00
/usr/libexec/bluetooth/obexd

Appears to be running.

When I kill it, it is automatically restarted. When I disable bluetooth
integration and restart it, I also don't get any decent debugging information.

-- 
You are receiving this mail because:
You are watching all bug changes.


[Bluedevil] [Bug 371492] Receiving files via bluetooth fails

2016-10-22 Thread Fuchs via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=371492

Fuchs  changed:

   What|Removed |Added

 Resolution|--- |UPSTREAM
 Status|UNCONFIRMED |RESOLVED

--- Comment #6 from Fuchs  ---
Actually, might be a nevermind, 

I just downgraded bluez to 5.39, so a change introduced in bluez seem to be
causing the issue. I'll go check if it is a bug there instead of in bluedevil
first, in case of it being a bluez one I'll come back. Thanks for the help so
far!

-- 
You are receiving this mail because:
You are watching all bug changes.


[plasmashell] [Bug 368909] New: Regression: Windows with demands attention flag are falsely shown on all workspaces

2016-09-16 Thread Fuchs via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=368909

Bug ID: 368909
   Summary: Regression: Windows with demands attention flag are
falsely shown on all workspaces
   Product: plasmashell
   Version: 5.7.95
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Pager
  Assignee: plasma-b...@kde.org
  Reporter: deve...@fuchsnet.ch

As reported on IRC: as the same model is used for the pager as for the
task-manager, windows that have the demands attention flag set will be falsely
shown on all workspaces.

Reproducible: Always

Steps to Reproduce:
1. Have multiple workspaces and a pager
2. Place a window on one workspace, let's take the great IRC client
konversation as an example
3. Have that window trigger demands attention  (e.g. get highlighted in
konversation)

Actual Results:  
Window is shown on all workspaces in the pager, as if it was sticky

Expected Results:  
Window is only shown on the correct workspace

-- 
You are receiving this mail because:
You are watching all bug changes.


[plasmashell] [Bug 360047] New: window title in tooltip not in sync

2016-03-03 Thread Fuchs via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=360047

Bug ID: 360047
   Summary: window title in tooltip not in sync
   Product: plasmashell
   Version: 5.5.95
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Task Manager
  Assignee: h...@kde.org
  Reporter: deve...@fuchsnet.ch
CC: plasma-b...@kde.org

The window title in the tooltip of task manager is not updated when the window
title changes.
This can be best reproduced with the new media control functionality (which is
awesome, by the way. Aside from the usual tiny sizes) 

Reproducible: Always

Steps to Reproduce:
1. Have a media player open, e.g. amarok
2. Mouse hover the entry in the task bar to get the tooltip
3. Use it to skip to the next song

Actual Results:  
The song title is updated in the new player control, but the window title below
stays on the old (now wrong) value

Expected Results:  
Both are updated

Note that this is just one example, in general the text should be kept in sync
with the window title, not just for audio players

-- 
You are receiving this mail because:
You are watching all bug changes.


[Touchpad-KCM] [Bug 359460] Synaptic touchpad wrong settings and limits

2016-03-04 Thread Fuchs via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=359460

Fuchs  changed:

   What|Removed |Added

 CC||deve...@fuchsnet.ch

--- Comment #1 from Fuchs  ---
Confirmed here on gentoo, seen it since the last plasma update. 
Didn't update or change anything on the synaptics or Xorg side, so quite
definitely plasma. 

Plasma 5.5.95, synaptics 1.8.3, Qt 5.5.1

-- 
You are receiving this mail because:
You are watching all bug changes.


[systemsettings] [Bug 359945] Touchpad scroll delta is limited by max. 10

2016-03-04 Thread Fuchs via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=359945

Fuchs  changed:

   What|Removed |Added

 CC||deve...@fuchsnet.ch

--- Comment #1 from Fuchs  ---
Reproducible here since the last plasma update, now using 5.5.95. 

The behaviour changed since the update, without changing values scrolling speed
here increased by various factors (I'd say roughly 8 times as fast). 

Setting values manually via synclient works as a workaround.

-- 
You are receiving this mail because:
You are watching all bug changes.


[plasma4] [Bug 312647] Regression: Pager in new air theme: current desktop not distinguishable from others

2016-03-04 Thread Fuchs via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=312647

Fuchs  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED

--- Comment #2 from Fuchs  ---
Solved in breeze (and breeze dark)

-- 
You are receiving this mail because:
You are watching all bug changes.


[konversation] [Bug 328117] Notification sound broken

2016-03-04 Thread Fuchs via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=328117

Fuchs  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED

--- Comment #2 from Fuchs  ---
Not reproducible any more in recent versions for me

-- 
You are receiving this mail because:
You are watching all bug changes.


[plasma4] [Bug 310587] Popups of hidden systray entry appear at wrong position

2016-03-04 Thread Fuchs via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=310587

Fuchs  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|CONFIRMED   |RESOLVED

--- Comment #3 from Fuchs  ---
Not reproducible for a while now, thus closing.

-- 
You are receiving this mail because:
You are watching all bug changes.


[Touchpad-KCM] [Bug 359460] Synaptic touchpad wrong settings and limits

2016-03-05 Thread Fuchs via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=359460

--- Comment #5 from Fuchs  ---
Wrong settings: 

Device 'SynPS/2 Synaptics TouchPad':
Device Enabled (150):   1
Coordinate Transformation Matrix (152): 1.00, 0.00, 0.00,
0.00, 1.00, 0.00, 0.00, 0.00, 1.00
Device Accel Profile (276): 1
Device Accel Constant Deceleration (277):   2.50
Device Accel Adaptive Deceleration (278):   1.00
Device Accel Velocity Scaling (279):12.50
Synaptics Edges (280):  1751, 5191, 1624, 4282
Synaptics Finger (281): 25, 30, 0
Synaptics Tap Time (282):   180
Synaptics Tap Move (283):   20
Synaptics Tap Durations (284):  180, 100, 100
Synaptics ClickPad (285):   0
Synaptics Middle Button Timeout (286):  75
Synaptics Two-Finger Pressure (287):282
Synaptics Two-Finger Width (288):   7
Synaptics Scrolling Distance (289): 10, 10
Synaptics Edge Scrolling (290): 1, 1, 0
Synaptics Two-Finger Scrolling (291):   1, 1
Synaptics Move Speed (292): 0.25, 0.42, 0.001000, 0.00
Synaptics Off (293):2
Synaptics Locked Drags (294):   0
Synaptics Locked Drags Timeout (295):   5000
Synaptics Tap Action (296): 0, 0, 0, 0, 1, 2, 3
Synaptics Click Action (297):   1, 1, 1
Synaptics Circular Scrolling (298): 0
Synaptics Circular Scrolling Distance (299):0.10
Synaptics Circular Scrolling Trigger (300): 0
Synaptics Circular Pad (301):   0
Synaptics Palm Detection (302): 1
Synaptics Palm Dimensions (303):5, 200
Synaptics Coasting Speed (304): 0.00, 50.00
Synaptics Pressure Motion (305):30, 160
Synaptics Pressure Motion Factor (306): 1.00, 1.00
Synaptics Grab Event Device (307):  0
Synaptics Gestures (308):   1
Synaptics Capabilities (309):   1, 0, 1, 1, 1, 1, 1
Synaptics Pad Resolution (310): 85, 60
Synaptics Area (311):   0, 0, 0, 0
Synaptics Noise Cancellation (312): 25, 25
Device Product ID (271):2, 7
Device Node (272):  "/dev/input/event5"


Correct settings (manually): 

Device 'SynPS/2 Synaptics TouchPad':
Device Enabled (150):   1
Coordinate Transformation Matrix (152): 1.00, 0.00, 0.00,
0.00, 1.00, 0.00, 0.00, 0.00, 1.00
Device Accel Profile (276): 1
Device Accel Constant Deceleration (277):   2.50
Device Accel Adaptive Deceleration (278):   1.00
Device Accel Velocity Scaling (279):12.50
Synaptics Edges (280):  1751, 5191, 1624, 4282
Synaptics Finger (281): 25, 30, 0
Synaptics Tap Time (282):   180
Synaptics Tap Move (283):   20
Synaptics Tap Durations (284):  180, 100, 100
Synaptics ClickPad (285):   0
Synaptics Middle Button Timeout (286):  75
Synaptics Two-Finger Pressure (287):282
Synaptics Two-Finger Width (288):   7
Synaptics Scrolling Distance (289): 120, 120
Synaptics Edge Scrolling (290): 1, 1, 0
Synaptics Two-Finger Scrolling (291):   1, 1
Synaptics Move Speed (292): 0.25, 0.42, 0.001000, 0.00
Synaptics Off (293):2
Synaptics Locked Drags (294):   0
Synaptics Locked Drags Timeout (295):   5000
Synaptics Tap Action (296): 0, 0, 0, 0, 1, 2, 3
Synaptics Click Action (297):   1, 1, 1
Synaptics Circular Scrolling (298): 0
Synaptics Circular Scrolling Distance (299):0.10
Synaptics Circular Scrolling Trigger (300): 0
Synaptics Circular Pad (301):   0
Synaptics Palm Detection (302): 1
Synaptics Palm Dimensions (303):5, 200
Synaptics Coasting Speed (304): 0.00, 50.00
Synaptics Pressure Motion (305):30, 160
Synaptics Pressure Motion Factor (306): 1.00, 1.00
Synaptics Grab Event Device (307):  0
Synaptics Gestures (308):   1
Synaptics Capabilities (309):   1, 0, 1, 1, 1, 1, 1
Synaptics Pad Resolution (310): 85, 60
Synaptics Area (311):   0, 0, 0, 0
Synaptics Noise Cancellation (312): 25, 25
Device Product ID (271):2, 7
Device Node (272):  "/dev/input/event5"

-- 
You are receiving this mail because:
You are watching all bug changes.


[plasmashell] [Bug 360047] window title in tooltip not in sync

2016-03-05 Thread Fuchs via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=360047

Fuchs  changed:

   What|Removed |Added

 Resolution|FIXED   |---
 Status|RESOLVED|UNCONFIRMED

--- Comment #2 from Fuchs  ---
Unfortunately not fully fixed with the above mentioned patch, still occurs,
oddly enough sometimes it now works.

-- 
You are receiving this mail because:
You are watching all bug changes.


[Powerdevil] [Bug 360537] New: Keyboard Backlight endless loop when changed, only inside plasma session

2016-03-14 Thread Fuchs via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=360537

Bug ID: 360537
   Summary: Keyboard Backlight endless loop when changed, only
inside plasma session
   Product: Powerdevil
   Version: 5.5.95
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-de...@kde.org
  Reporter: deve...@fuchsnet.ch

I have a thinkpad T430 which recently gained a better keyboard backlight
driver. 
It works in a VT both with the keyboard shortcut (FN+Space) or via dbus,
however, it breaks when inside a Plasma 5 session, as there is an endless loop
of the backlight cycling between the 3 states. 

qdbus --system org.freedesktop.UPower /org/freedesktop/UPower/KbdBacklight
org.freedesktop.UPower.KbdBacklight.GetBrightness   
0

qdbus --system org.freedesktop.UPower /org/freedesktop/UPower/KbdBacklight
org.freedesktop.UPower.KbdBacklight.GetMaxBrightness
2


Reproducible: Always

Steps to Reproduce:
0. Have a Thinkpad T430  (other models might be affected too, I don't have any)
1. Be in a Plasma 5 session
2. Change the Keyboard backlight, either via keyboard, via dbus or via the
battery plasmoid

Actual Results:  
Brightness endlessly cycles through possible states

Expected Results:  
Brightness is set correctly, as it is when switching to a VT

Plasma is 5.6 Beta, Qt is 5.5.1,  Kernel is 4.5 

Any information on how I could debug and solve this is appreciated.

-- 
You are receiving this mail because:
You are watching all bug changes.


[Powerdevil] [Bug 360537] Keyboard Backlight endless loop when changed, only inside plasma session

2016-03-14 Thread Fuchs via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=360537

--- Comment #1 from Fuchs  ---
Looking at the code so far, my best guess would be that it tries to round (with
the very limited amount of steps, 0,1,2) and horribly fails, which never lets
it rest at a certain value. If that is the case, I hope the logic can be
adapted to cope with that. Otherwise someone needs to dig a bit further.

-- 
You are receiving this mail because:
You are watching all bug changes.


[Powerdevil] [Bug 360537] Keyboard Backlight endless loop when changed, only inside plasma session

2016-03-14 Thread Fuchs via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=360537

--- Comment #2 from Fuchs  ---
Ignore the last comment, actual issue is the following: 

per default the key triggers keycode 236 (keysym 0x1008ff04,
XF86KbdLightOnOff), which by default in KDE Plasma is configured to toggle the
keyboard light. However, at the same time the keyboard light is changed by the
BIOS. This seems to get plasma / powerdevil in a confused state so it doesn't
stop cycling through them. 

If somehow possible, I highly recommend disabling that default keybinding on
affected thinkpads. If not possible some logic will be needed to avoid that,
because otherwise owners of affected hardware will run into this issue with
recent kernels and KDE plasma, changing their keyboard brightness leading to an
endless cycle  (which, as a side effect, triggers the lovely pop up which won't
disappear either. In short: the session is rendered quite unusable) 

If I can somehow help resolving this issue  (xev or dbus monitor logs or
whatnot): let me know. 

Workaround for me: disable that keybinding in systemsettings.

-- 
You are receiving this mail because:
You are watching all bug changes.


[Powerdevil] [Bug 360537] Keyboard Backlight endless loop when changed, only inside plasma session

2016-03-15 Thread Fuchs via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=360537

--- Comment #3 from Fuchs  ---
As discussed on IRC: 

I also checked why using the slider or dbus would trigger the buggy behaviour. 
As expected, the driver is silly enough to emit 

keycode 236 (keysym 0x1008ff04, XF86KbdLightOnOff)

even if you didn't touch the keyboard, it just does this on all keyboard
brightness changes. Huzzah.

-- 
You are receiving this mail because:
You are watching all bug changes.


[Powerdevil] [Bug 360537] Keyboard Backlight endless loop when changed, only inside plasma session

2016-03-18 Thread Fuchs via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=360537

--- Comment #8 from Fuchs  ---
As a sidenote there is a BIOS setting on how the brightness key should behave,
I can't remember whether that is only related to the thinklight (which gets
turned on after 3 presses) or also the keyboard levels. I'll update the bug
report if there are any changes. 

As discussed on IRC, just to have this documented here as well: 

the keyboard event emitted unfortunately also has other side effects, e.g. when
using the slider of the battery plasmoid it closes it. So it would be great to
have that fixed upstream in kernel. Also the OSD is obviously not shown when
the key binding is disabled, this should be workaroundable with a little script
and dbus, I'll also update the bug report when I manage something. Won't have
time today / in the next two days though. Thanks so far for everybody involved.

-- 
You are receiving this mail because:
You are watching all bug changes.


[Powerdevil] [Bug 360537] Keyboard Backlight endless loop when changed, only inside plasma session

2016-03-19 Thread Fuchs via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=360537

--- Comment #10 from Fuchs  ---
Augh, obviously replace 2 above with $MAX, my bad. (And in this case maybe
check for non-null, even though this should™ not be possible)

-- 
You are receiving this mail because:
You are watching all bug changes.

[Powerdevil] [Bug 360537] Keyboard Backlight endless loop when changed, only inside plasma session

2016-03-19 Thread Fuchs via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=360537

--- Comment #9 from Fuchs  ---
To get the OSD back, I created the following script (Adapt paths where needed,
should work in POSIX compliant shells) and bound it to XF86KbdLightOnOff.
Therefore now using the keyboard or the battery plasmoid slider (aside from
closing itself) works including displaying the OSD.

#!/bin/sh
# Get the maximum value
MAX=`/usr/bin/qdbus --system org.freedesktop.UPower
/org/freedesktop/UPower/KbdBacklight
org.freedesktop.UPower.KbdBacklight.GetMaxBrightness`
# Get the current value. Dbus currently (kernel 4.5) gives wrong values for
GetBrightness, so we fetch it via the proc interface
CUR=`grep status /proc/acpi/ibm/kbdlight | awk '{print $2}'`

# Calculate percentage
PER=$(($CUR * 100 / 2))

# Invoke OSD
/usr/bin/qdbus org.kde.plasmashell /org/kde/osdService
org.kde.osdService.keyboardBrightnessChanged $PER

exit 0

-- 
You are receiving this mail because:
You are watching all bug changes.


[plasmashell] [Bug 360789] New: Keyboard arrow keys inverted?

2016-03-20 Thread Fuchs via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=360789

Bug ID: 360789
   Summary: Keyboard arrow keys inverted?
   Product: plasmashell
   Version: 5.5.95
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Milou
  Assignee: m...@vhanda.in
  Reporter: deve...@fuchsnet.ch
CC: plasma-b...@kde.org

I assume this is milou, it's the "search and launch" thingie with a magnifier
glass as icon. 

If I place it on my panel (bottom of the screen) and type something, the arrow
keys are inverted when going through the results.

Reproducible: Always

Steps to Reproduce:
1. Put milou in a panel (bottom of screen here)
2. Open it
3. Search something
4. Go through results with up + down arrow keys

Actual Results:  
The up arrow selects the item below, the down arrow selects the item above

Expected Results:  
The up arrow selects the item above, the down arrow the item below

-- 
You are receiving this mail because:
You are watching all bug changes.


[Breeze] [Bug 364449] New: Regression: after updating frameworks and plasma kmail is missing the "sent" icon

2016-06-18 Thread Fuchs via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=364449

Bug ID: 364449
   Summary: Regression: after updating frameworks and plasma kmail
is missing the "sent" icon
   Product: Breeze
   Version: 5.6.5
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Icons
  Assignee: visual-des...@kde.org
  Reporter: deve...@fuchsnet.ch
CC: kain...@gmail.com

After updating to plasma 5.6.5.1 and frameworks 5.23  kmail is missing the icon
for "sent" e-mails. 

See the attached screenshot for details. 

Before the update the old (coloured) icon was used.

Reproducible: Always

Steps to Reproduce:
1. Update to the mentioned frameworks and plasma versions
2. Start kmail
3. Open the sent folder

Actual Results:  
Icons are missing

Expected Results:  
Icons are there

kmail is from kdepim 16.04.2

-- 
You are receiving this mail because:
You are watching all bug changes.


[Breeze] [Bug 364449] Regression: after updating frameworks and plasma kmail is missing the "sent" icon

2016-06-18 Thread Fuchs via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=364449

--- Comment #1 from Fuchs  ---
Created attachment 99562
  --> https://bugs.kde.org/attachment.cgi?id=99562&action=edit
Lacking icons (right side of the image, in the list)

-- 
You are receiving this mail because:
You are watching all bug changes.


[Breeze] [Bug 364452] New: Regression: after updating frameworks and plasma kmail is missing the "task" icon

2016-06-18 Thread Fuchs via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=364452

Bug ID: 364452
   Summary: Regression: after updating frameworks and plasma kmail
is missing the "task" icon
   Product: Breeze
   Version: 5.6.5
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Icons
  Assignee: visual-des...@kde.org
  Reporter: deve...@fuchsnet.ch
CC: kain...@gmail.com

In addition to Bug 364449: 

After updating to plasma 5.6.5.1 and frameworks 5.23 kmail is missing the icon
for "task" e-mails. See the attached screenshot for details. It is lacking in
both the filter and also if you add it as a column / in the settings for the
column. It is not missing in the context menu.

Reproducible: Always 

Steps to Reproduce: 
1. Update to the mentioned frameworks and plasma versions
2. Start kmail 
3. Either open the column settings or have a "task" icon configured

Actual Results: Icons are missing

Expected Results: Icons are there

kmail is from kdepim 16.04.2

Reproducible: Always

-- 
You are receiving this mail because:
You are watching all bug changes.


[Breeze] [Bug 364452] Regression: after updating frameworks and plasma kmail is missing the "task" icon

2016-06-18 Thread Fuchs via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=364452

--- Comment #1 from Fuchs  ---
Created attachment 99566
  --> https://bugs.kde.org/attachment.cgi?id=99566&action=edit
Screenshot of the issue, mind that it is not only missing in the filter, but
also in the list itself.

-- 
You are receiving this mail because:
You are watching all bug changes.


[plasmashell] [Bug 364491] New: Regression: Search has black text on black background and is unreadable with breeze-dark

2016-06-19 Thread Fuchs via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=364491

Bug ID: 364491
   Summary: Regression: Search has black text on black background
and is unreadable with breeze-dark
   Product: plasmashell
   Version: 5.5.95
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Widget Explorer
  Assignee: plasma-b...@kde.org
  Reporter: deve...@fuchsnet.ch

See the attached screenshot, the search in the widget explorer uses dark text
on dark background and is completely unreadable

Reproducible: Always

Steps to Reproduce:
1. Upgrade to 5.7 beta
2. Use breeze-dark as theme
3. Add a widget
4. Use the search

Actual Results:  
Text is unreadable

Expected Results:  
Text is readable

-- 
You are receiving this mail because:
You are watching all bug changes.


[plasmashell] [Bug 364491] Regression: Search has black text on black background and is unreadable with breeze-dark

2016-06-19 Thread Fuchs via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=364491

--- Comment #1 from Fuchs  ---
Created attachment 99598
  --> https://bugs.kde.org/attachment.cgi?id=99598&action=edit
Screenshot of the issue

-- 
You are receiving this mail because:
You are watching all bug changes.


[plasmashell] [Bug 364492] New: Upgrade from 5.6: if existing launchers are there, moving around icons deletes them

2016-06-19 Thread Fuchs via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=364492

Bug ID: 364492
   Summary: Upgrade from 5.6: if existing launchers are there,
moving around icons deletes them
   Product: plasmashell
   Version: 5.5.95
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Icons-only Task Manager
  Assignee: h...@kde.org
  Reporter: deve...@fuchsnet.ch
CC: plasma-b...@kde.org

I upgraded from 5.6 to 5.7 beta with icon only task manager and existing
launchers. 
When moving around icons, these launchers got removed. 

Removing and re-adding a fresh icon tasks resolved this, but of course it would
be nice if 5.6 settings would be properly taken over

Reproducible: Always

Steps to Reproduce:
1. Use Icon only taskmanager
2. Create some launchers
3. Upgrade from 5.6 to 5.7, grab a launcher and drag it around

Actual Results:  
Other launchers get removed

Expected Results:  
Launchers are kept

-- 
You are receiving this mail because:
You are watching all bug changes.


[Breeze] [Bug 364449] Regression: after updating frameworks and plasma kmail is missing the "sent" icon

2016-06-19 Thread Fuchs via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=364449

--- Comment #3 from Fuchs  ---
(In reply to andreas from comment #2)
> Hi Fuchs,

Hi Andreas.

> In this bug I think it's not a bug, cause when you select an item (blue
> selection) the icon color change to the color of the text (white). This is
> new (and awesome).

Please re-read the bug report and attachment description. 
It is a bug, the icon that is lacking is on the _right_ side, in the list of
e-mails.

Thanks, kind regards, 

Christian

-- 
You are receiving this mail because:
You are watching all bug changes.


[Breeze] [Bug 364449] Regression: after updating frameworks and plasma kmail is missing the "sent" icon

2016-06-19 Thread Fuchs via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=364449

--- Comment #5 from Fuchs  ---
No worries, thanks for having a look and fixing :)

-- 
You are receiving this mail because:
You are watching all bug changes.


[Breeze] [Bug 364449] Regression: after updating frameworks and plasma kmail is missing the "sent" icon

2016-06-24 Thread Fuchs via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=364449

--- Comment #7 from Fuchs  ---
debatable, given it wasn't kmail I updated when the bug occurred and it working
in older versions. I recommend at least for now fixing it where it broke.

-- 
You are receiving this mail because:
You are watching all bug changes.


[Breeze] [Bug 364449] Regression: after updating frameworks and plasma kmail is missing the "sent" icon

2016-06-24 Thread Fuchs via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=364449

--- Comment #9 from Fuchs  ---
I have an older kubuntu at paw, I'll give you another screenshot of how it used
to look when it worked.

-- 
You are receiving this mail because:
You are watching all bug changes.


[Breeze] [Bug 364449] Regression: after updating frameworks and plasma kmail is missing the "sent" icon

2016-06-24 Thread Fuchs via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=364449

--- Comment #10 from Fuchs  ---
Created attachment 99681
  --> https://bugs.kde.org/attachment.cgi?id=99681&action=edit
old icon

-- 
You are receiving this mail because:
You are watching all bug changes.


[kmail2] [Bug 364452] Regression: after updating frameworks and plasma kmail is missing the "task" icon

2016-06-26 Thread Fuchs via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=364452

--- Comment #3 from Fuchs  ---
Thank you very much for looking into and fixing both of these! 

Kind regards, 

Christian

-- 
You are receiving this mail because:
You are watching all bug changes.


[Baloo] [Bug 364858] New: Regression: Re-add a decent way of displaying what files baloo is indexing / extracting

2016-06-28 Thread Fuchs via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=364858

Bug ID: 364858
   Summary: Regression: Re-add a decent way of displaying what
files baloo is indexing / extracting
   Product: Baloo
   Version: 5.9.90
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: grave
  Priority: NOR
 Component: General
  Assignee: m...@vhanda.in
  Reporter: deve...@fuchsnet.ch
CC: pinak.ah...@gmail.com

These days I, again, had an issue with baloo_file_extractor eating all of my
CPU and a lot of my RAM. 

It is, at least as far as I was able to tell, completely impossible to debug
that, as baloo no longer prints out what file it is currently indexing /
extracting, and lsof and the likes also don't help. 

Please re-add a way to display this, whether it being the inode numbers being
displayed in ps as it used to be or via balooctl or whatever else.

For now the only solution was to, again, completely disable baloo file
indexing.

Reproducible: Always

Steps to Reproduce:
1. Have baloo eat your CPU
2. Try to find out why 

Actual Results:  
You can't

Expected Results:  
You can

-- 
You are receiving this mail because:
You are watching all bug changes.


[konversation] [Bug 363503] New: Letters are lost when a line breaks inside a (channel) link

2016-05-25 Thread Fuchs via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=363503

Bug ID: 363503
   Summary: Letters are lost when a line breaks inside a (channel)
link
   Product: konversation
   Version: frameworks
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: ircview
  Assignee: argo...@gmail.com
  Reporter: deve...@fuchsnet.ch
CC: konversation-de...@kde.org

Konversation dynamically breaks lines that are too wide for the chatview. 
However, if that break happens inside of a (channel) link, some letters might
not be displayed. 

See the attached screenshots.

Reproducible: Always

Steps to Reproduce:
1. Write a channel name, e.g. #foo-barbaz
2. Resize the window so the line is too wide and a line break is added
3. Move that linebreak inside of #foo-barbaz

Actual Results:  
#foo-barbaz is missing a letter

Expected Results:  
#foo-barbaz is written like that

Qt 5.5 and 5.6 seem to be affected, tested on Gentoo and Kubuntu

-- 
You are receiving this mail because:
You are watching all bug changes.


[konversation] [Bug 363503] Letters are lost when a line breaks inside a (channel) link

2016-05-25 Thread Fuchs via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=363503

--- Comment #1 from Fuchs  ---
Created attachment 99176
  --> https://bugs.kde.org/attachment.cgi?id=99176&action=edit
Screenshot of the issue

-- 
You are receiving this mail because:
You are watching all bug changes.


[konversation] [Bug 363503] Letters are lost when a line breaks inside a (channel) link

2016-05-25 Thread Fuchs via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=363503

--- Comment #2 from Fuchs  ---
Created attachment 99177
  --> https://bugs.kde.org/attachment.cgi?id=99177&action=edit
Correct version

-- 
You are receiving this mail because:
You are watching all bug changes.


[plasma-nm] [Bug 363698] New: Same icon used for VPN connection and disconnected

2016-05-30 Thread Fuchs via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=363698

Bug ID: 363698
   Summary: Same icon used for VPN connection and disconnected
   Product: plasma-nm
   Version: 5.6.4
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: applet
  Assignee: jgrul...@redhat.com
  Reporter: deve...@fuchsnet.ch
CC: lu...@kde.org

The current networkmanager applet uses a blue colour to indicate VPN
connections  (which is debatable, given on wired connections the blue line is
hard to catch, plus blue is not associated with secure connections, other
applications use green for that) 

However, the same icon is used when wireless is active but there is no
connection. 
In this case the wireless icon should be used but with the same colour as
disabled wireless and no connection: red.

See the attached screenshots

Reproducible: Always

Steps to Reproduce:
1. Open a wireless connection
2. Connect to VPN
3. Disconnect all wireless connections

Actual Results:  
The icon is still the same

Expected Results:  
The icon changes

Marked as major because this is highly misleading and suggests a secured
connection when there is none.

-- 
You are receiving this mail because:
You are watching all bug changes.


[plasma-nm] [Bug 363698] Same icon used for VPN connection and disconnected

2016-05-30 Thread Fuchs via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=363698

--- Comment #1 from Fuchs  ---
Created attachment 99261
  --> https://bugs.kde.org/attachment.cgi?id=99261&action=edit
Icon used when connected but without VPN

-- 
You are receiving this mail because:
You are watching all bug changes.


[plasma-nm] [Bug 363698] Same icon used for VPN connection and disconnected

2016-05-30 Thread Fuchs via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=363698

--- Comment #2 from Fuchs  ---
Created attachment 99262
  --> https://bugs.kde.org/attachment.cgi?id=99262&action=edit
Icon used when connected with VPN

-- 
You are receiving this mail because:
You are watching all bug changes.


[plasma-nm] [Bug 363698] Same icon used for VPN connection and disconnected

2016-05-30 Thread Fuchs via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=363698

--- Comment #3 from Fuchs  ---
Created attachment 99263
  --> https://bugs.kde.org/attachment.cgi?id=99263&action=edit
Icon used when disconnected

-- 
You are receiving this mail because:
You are watching all bug changes.


[konversation] [Bug 355652] double entry for spell checking language

2015-12-07 Thread Fuchs via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=355652

--- Comment #4 from Fuchs  ---
(In reply to Sudhir Khanger from comment #2)
> I think it would be a good idea to remove spell check options from
> Konversation and follow whatever is set in SystemSettings.

Great idea, please also remove them from kmail, kate and calligra and
libreoffice while at it, no need for them there either. 

Jokes aside: there are lots of people, me included, who speak multiple
languages and thus write and read in multiple languages. Similar to why you
need this option in the above mentioned applications, you definitely need them
in konversation, and you need them by channel. I'm glad that frameworks seem to
now offer this by default on text input fields, so for people with a version
recent enough simply only that one should be shown, and for people with older
versions the current solution should still be available.

-- 
You are receiving this mail because:
You are watching all bug changes.


[konsole] [Bug 356450] New: Konsole crashes on close

2015-12-09 Thread Fuchs via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356450

Bug ID: 356450
   Summary: Konsole crashes on close
   Product: konsole
   Version: unspecified
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: konsole-de...@kde.org
  Reporter: deve...@fuchsnet.ch

Application: konsole (15.11.90)

Qt Version: 5.5.1
Operating System: Linux 4.3.0-gentoo x86_64
Distribution: "Gentoo Base System release 2.2"

-- Information about the crash:
- What I was doing when the application crashed:

Closing konsole via keyboard shortcut

Gentoo Linux, x86_64

The crash can be reproduced sometimes.

-- Backtrace:
Application: Konsole (konsole), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
[KCrash Handler]
#6  0x7f2df2076477 in raise () from /lib64/libc.so.6
#7  0x7f2df20778ca in abort () from /lib64/libc.so.6
#8  0x7f2df20b5728 in ?? () from /lib64/libc.so.6
#9  0x7f2df20bb016 in ?? () from /lib64/libc.so.6
#10 0x7f2df20bb81e in ?? () from /lib64/libc.so.6
#11 0x7f2deed6194f in QMetaCallEvent::~QMetaCallEvent() () from
/usr/lib64/libQt5Core.so.5
#12 0x7f2deed619a9 in QMetaCallEvent::~QMetaCallEvent() () from
/usr/lib64/libQt5Core.so.5
#13 0x7f2deed3ecd7 in QCoreApplication::removePostedEvents(QObject*, int)
() from /usr/lib64/libQt5Core.so.5
#14 0x7f2deed643cd in QObjectPrivate::~QObjectPrivate() () from
/usr/lib64/libQt5Core.so.5
#15 0x7f2deed644f9 in QObjectPrivate::~QObjectPrivate() () from
/usr/lib64/libQt5Core.so.5
#16 0x7f2deed6c0f0 in QObject::~QObject() () from
/usr/lib64/libQt5Core.so.5
#17 0x7f2de05e48d9 in QXcbConnection::~QXcbConnection() () from
/usr/lib64/libQt5XcbQpa.so.5
#18 0x7f2de05eb79e in QXcbIntegration::~QXcbIntegration() () from
/usr/lib64/libQt5XcbQpa.so.5
#19 0x7f2de05eb889 in QXcbIntegration::~QXcbIntegration() () from
/usr/lib64/libQt5XcbQpa.so.5
#20 0x7f2def061fac in QGuiApplicationPrivate::~QGuiApplicationPrivate() ()
from /usr/lib64/libQt5Gui.so.5
#21 0x7f2def589ff9 in QApplicationPrivate::~QApplicationPrivate() () from
/usr/lib64/libQt5Widgets.so.5
#22 0x7f2deed6c0f0 in QObject::~QObject() () from
/usr/lib64/libQt5Core.so.5
#23 0x7f2def061db9 in QGuiApplication::~QGuiApplication() () from
/usr/lib64/libQt5Gui.so.5
#24 0x7f2def58bcc0 in QApplication::~QApplication() () from
/usr/lib64/libQt5Widgets.so.5
#25 0x7f2df2407c96 in kdemain () from /usr/lib64/libkdeinit5_konsole.so
#26 0x7f2df2063620 in __libc_start_main () from /lib64/libc.so.6
#27 0x004007c9 in _start ()

Possible duplicates by query: bug 355829, bug 355595, bug 353736, bug 352213,
bug 351922.

Reported using DrKonqi

-- 
You are receiving this mail because:
You are watching all bug changes.


[konsole] [Bug 343803] Konsole keeps running in background after closing window with nvidia drivers

2016-01-16 Thread Fuchs via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=343803

Fuchs  changed:

   What|Removed |Added

 CC||deve...@fuchsnet.ch

--- Comment #47 from Fuchs  ---
This appears to be fixed in 361.18, can someone still reproduce it with this
version? 

(They fixed a different Qt triggered bug in that release, might have been a
similar or even the same cause)

-- 
You are receiving this mail because:
You are watching all bug changes.


[okular] [Bug 335033] [Forms][Checkbox] Printing shows a 4 instead of a checkmark

2016-01-25 Thread Fuchs via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=335033

Fuchs  changed:

   What|Removed |Added

 CC||u.fu...@yahoo.de

--- Comment #5 from Fuchs  ---
This is my workaround for the problem:
Checkboxes are printed correctly if somewhere in the PDF-document a review (F6)
emphasis (yellow pencil) is made. Transparancy can be set to 1%, so this mark
is not printed actually.

-- 
You are receiving this mail because:
You are watching all bug changes.


[frameworks-plasma] [Bug 361626] Long-clicking plasmoids to display the handle is non-intuitive with mouse input

2016-04-11 Thread Fuchs via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=361626

Fuchs  changed:

   What|Removed |Added

 CC||deve...@fuchsnet.ch

--- Comment #1 from Fuchs  ---
Minor input as I directed the user here, due to this coming up frequently
enough in #kde on IRC: 

One possibility would be to at least add an entry to the context menu which
opens that side bar or have a submenu with the possibilities of the side bar 
(move, resize, rotate, close). 
Opening the context menu is rather intuitive and well known on desktop systems. 

Kind regards, 

Fuchs

-- 
You are receiving this mail because:
You are watching all bug changes.


[konversation] [Bug 361833] New: next/previous icons missing on buttons in search

2016-04-15 Thread Fuchs via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=361833

Bug ID: 361833
   Summary: next/previous icons missing on buttons in search
   Product: konversation
   Version: frameworks
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: konversation-de...@kde.org
  Reporter: deve...@fuchsnet.ch

Apparently in the KF5 version the icons on prev/next buttons in the search are
missing. 

Icon set used is the default (breeze)

Reproducible: Always

Steps to Reproduce:
1. Open the search (Ctrl+F)
2. Look at the prev / next buttons


Actual Results:  
They don't have an icon but blank space on the left

Expected Results:  
They have an icon or no blank space on the left

-- 
You are receiving this mail because:
You are watching all bug changes.


[konsole] [Bug 343803] Konsole keeps running in background after closing window with nvidia drivers

2016-02-14 Thread Fuchs via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=343803

--- Comment #62 from Fuchs  ---
Mike: My guess would be that it depends on whether you use the glvnd library or
not. 

Could you try installing the driver with it and see if the problem persists? 
I can't reproduce it when using glvnd  (which, despite the problem it had,
would be my recommendation)

-- 
You are receiving this mail because:
You are watching all bug changes.


[Breeze] [Bug 359387] New: Since update to KF 5.19: wrong breeze icons used for amarok and konversation in icon tasks

2016-02-14 Thread Fuchs via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=359387

Bug ID: 359387
   Summary: Since update to KF 5.19: wrong breeze icons used for
amarok and konversation in icon tasks
   Product: Breeze
   Version: unspecified
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Icons
  Assignee: uri_herr...@nitrux.in
  Reporter: deve...@fuchsnet.ch
CC: kain...@gmail.com

Today I updated to KF 5.19
Since then in the icons only tasks plasmoids the wrong icons are used for
konversation and amarok.

Other applications are fine, the correct icon seems to be used in other places
(namely: the kwin icon, the pager) 

Not sure which component  is at fault here, but it would be nice if that could
be fixed, monochrome icons don't look good for application icons, and if it is
only two of them, they stick out rather badly.

Reproducible: Always

Steps to Reproduce:
1. Update to KF5 5.19   (tested on gentoo)
2. Use icons only task manager
3. Add konversation and amarok as starters or run them

Actual Results:  
The wrong (monochrome) icon is shown instead of the app icon

Expected Results:  
The correct (coloured) icon is shown

This is size independent, making the panel smaller or bigger (and thus the icon
scaling) didn't resolve it.  I removed the plasma related files in ~/.cache,
that didn't help either.

-- 
You are receiving this mail because:
You are watching all bug changes.


[Breeze] [Bug 359387] Since update to KF 5.19: wrong breeze icons used for amarok and konversation in icon tasks

2016-02-14 Thread Fuchs via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=359387

--- Comment #1 from Fuchs  ---
Created attachment 97191
  --> https://bugs.kde.org/attachment.cgi?id=97191&action=edit
Screenshot of the issue

-- 
You are receiving this mail because:
You are watching all bug changes.


[plasmashell] [Bug 359388] New: Icons for third party applications (namely: hp systemtray, skype, possibly also others) not displayed

2016-02-14 Thread Fuchs via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=359388

Bug ID: 359388
   Summary: Icons for third party applications (namely: hp
systemtray, skype, possibly also others) not displayed
   Product: plasmashell
   Version: 5.5.4
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: System Tray
  Assignee: plasma-b...@kde.org
  Reporter: deve...@fuchsnet.ch

Might be related to the update to KF 5.19 I just made: 

Third party qt applications, namely skype and hp-systray (from hplip) that I
tested, no longer have an icon in the systray. The space is reserved, but they
just show up as blank.

Reproducible: Always

Steps to Reproduce:
1. Open a non-KDE / non-status notifier application with a systray icon

Actual Results:  
Icon is not shown

Expected Results:  
Icon is shown

SNI Qt: 0.2.6-r1
Qt: 5.5.1
KF:  5.19
Plasma: 5.5.4

-- 
You are receiving this mail because:
You are watching all bug changes.


[plasmashell] [Bug 359388] Icons for third party applications (namely: hp systemtray, skype, possibly also others) not displayed

2016-02-14 Thread Fuchs via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=359388

--- Comment #1 from Fuchs  ---
Created attachment 97192
  --> https://bugs.kde.org/attachment.cgi?id=97192&action=edit
Screenshot of the issue

Screenshot of the issue, the part before - Skype is not a bug, I just removed
my Skype handle because I don't need that to be public.

-- 
You are receiving this mail because:
You are watching all bug changes.


[konsole] [Bug 356450] Konsole crashes on close

2016-02-14 Thread Fuchs via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356450

Fuchs  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED

--- Comment #1 from Fuchs  ---
Fixed when using an nvidia driver with glvnd, as not all of them do, it would
still be nice if this could be fixed in general.

-- 
You are receiving this mail because:
You are watching all bug changes.


[konversation] [Bug 352800] Channel Mode Buttons: hard to distinguish state with breeze (and possibly other themes)

2016-02-14 Thread Fuchs via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=352800

Fuchs  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED

--- Comment #1 from Fuchs  ---
Fixed in more recent versions

-- 
You are receiving this mail because:
You are watching all bug changes.


[plasmashell] [Bug 359388] Icons for third party applications (namely: hp systemtray, skype, possibly also others) not displayed

2016-02-14 Thread Fuchs via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=359388

--- Comment #2 from Fuchs  ---
Additional info: this only happens when sni-qt is installed, the new
xembedsniproxy works, _if_ sni-qt is not installed. However, this seems to not
have been communicated well or received well by packagers, as e.g. gentoo still
offers sni-qt and does not autostart xembedsniproxy. Shall add this as a bug
report to gentoo.

-- 
You are receiving this mail because:
You are watching all bug changes.


[Breeze] [Bug 359387] Since update to KF 5.19: wrong breeze icons used for amarok and konversation in icon tasks

2016-02-14 Thread Fuchs via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=359387

--- Comment #3 from Fuchs  ---
(In reply to andreas.sturmlechner from comment #2)
> It's quite the opposite for me; The blue amarok:4 icon has always stuck in
> the system tray, while now it blends in with the rest. konversation:5 has
> been using a monochrome icon for a long time already.

Not in the system tray. In the regular task list. In the systemtray it is (and
was) correct.

-- 
You are receiving this mail because:
You are watching all bug changes.


[Breeze] [Bug 359387] Since update to KF 5.19: wrong breeze icons used for amarok and konversation in icon tasks

2016-02-14 Thread Fuchs via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=359387

--- Comment #4 from Fuchs  ---
Update: the issue seems to be
/usr/share/plasma/desktoptheme/default/icons/konversation.svgz

which is taken (for whatever reason, that should be the systray icon, not the
app icon) instead of /usr/share/icons/breeze/apps//konversation.svg(z) 

When I rename that file and remove the cache, the correct file is taken. 
Not sure which component leads to the wrong one being taken, but it's quite
likely in frameworks 5.19, because that is the thing I updated before it broke.

-- 
You are receiving this mail because:
You are watching all bug changes.


[plasmashell] [Bug 359388] Icons for SNI Qt apps not appearing

2016-02-15 Thread Fuchs via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=359388

--- Comment #5 from Fuchs  ---
(In reply to David Edmundson from comment #3)

> I'm going to need dbus logs (run dbus-monitor) for when you start hp system
> tray. Plus ideally command line output from that app.

I'll gladly provide these either in private  (Fuchs on freenode) or if you tell
me how to strip them down. By default, dbus-monitor contains loads of data,
including passwords (!) in cleartext (!!) from kwallet, so I am not going to
put that on bugs.kde.org. 

Also it's a bit tricky to strip it down manually, as just running it the couple
of seconds that were needed whilst hp-systray was starting it produced roughly
6000 lines.

Kind regards, 

Christian

-- 
You are receiving this mail because:
You are watching all bug changes.


[Breeze] [Bug 359387] Since update to KF 5.19: wrong breeze icons used for amarok and konversation in icon tasks

2016-02-17 Thread Fuchs via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=359387

--- Comment #6 from Fuchs  ---
I was hoping for this to be fixed with the other (systray) icon fix backported
via
https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=f640b7c3b14c747f026e5667beddbf7def4d0549,
 unfortunately this seems to be a completely unrelated issue and is still
present.

-- 
You are receiving this mail because:
You are watching all bug changes.


[Breeze] [Bug 359387] Since update to KF 5.19: wrong breeze icons used for amarok and konversation in icon tasks

2016-02-17 Thread Fuchs via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=359387

--- Comment #8 from Fuchs  ---
If it really is by design, then I call that faulty behaviour from an UX
perspective. 

1) The icon used differs between icon tasks and everywhere else, including the
pager, krunner, the application menu, kwin and the application itself. That's a
massive breach of consistency. 

2) only a very limited amount of applications do provide these icons, so they
also look inconsistent within icon tasks. 

If this is by design: faulty behaviour. If it isn't: faulty behaviour. So still
a bug to be fixed.

-- 
You are receiving this mail because:
You are watching all bug changes.


[Breeze] [Bug 359387] Since update to KF 5.19: wrong breeze icons used for amarok and konversation in icon tasks

2016-02-17 Thread Fuchs via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=359387

--- Comment #10 from Fuchs  ---
In addition to that, the monochrome icons yet again get used in places where
they weren't supposed to be used, so I'd say it even actively goes against the
UX guidelines wrt icons. 

So yeah, I'd say this still needs to be fixed.

-- 
You are receiving this mail because:
You are watching all bug changes.


[plasmashell] [Bug 359387] Since update to KF 5.19: wrong breeze icons used for amarok and konversation in icon tasks

2016-02-18 Thread Fuchs via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=359387

--- Comment #14 from Fuchs  ---
I assume it was the changes in src/declarativeimports/core/iconitem.cpp with
5184ac94 that also caused the systray regression, mixed with how icon tasks
decided which icon to take. 

As you know this logic, Eike, you hopefully can point people to the right place
to fix it. 

But yes, the change came with an update of frameworks, which doesn't contain
icon tasks (as I initially wrote, I think)

-- 
You are receiving this mail because:
You are watching all bug changes.


[plasmashell] [Bug 359387] Since update to KF 5.19: wrong breeze icons used for amarok and konversation in icon tasks

2016-02-21 Thread Fuchs via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=359387

Fuchs  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 Resolution|--- |FIXED

--- Comment #15 from Fuchs  ---
Fixed by https://phabricator.kde.org/D991,  thanks.

-- 
You are receiving this mail because:
You are watching all bug changes.


[plasmashell] [Bug 359387] Since update to KF 5.19: wrong breeze icons used for amarok and konversation in icon tasks

2016-02-27 Thread Fuchs via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=359387

--- Comment #19 from Fuchs  ---
(In reply to Hrvoje Senjan from comment #18)
> I don't think so unfortunately (at least not upstream).
> usesPlasmaTheme is a new property since 5.19.0.

Yeah, it's not yet released, I applied the patch manually. I assume it will be
fixed by the next bugfix release.

-- 
You are receiving this mail because:
You are watching all bug changes.


[kontact] [Bug 368186] New: Kontact crashes when displaying content of message or akregator news

2016-09-03 Thread Matthias Fuchs via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=368186

Bug ID: 368186
   Summary: Kontact crashes when displaying content of message or
akregator news
   Product: kontact
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: matz.fu...@gmx.at

Application: kontact (5.3.0 (QtWebEngine))

Qt Version: 5.6.1
Frameworks Version: 5.25.0
Operating System: Linux 4.7.2-1-default x86_64
Distribution: "openSUSE Tumbleweed"

-- Information about the crash:
- What I was doing when the application crashed:
I clicked on a message in the message list (to show its content in widget
below).

The crash can be reproduced every time.

-- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f28389d0940 (LWP 2672))]

Thread 33 (Thread 0x7f26e3baa700 (LWP 2752)):
#0  0x7f283123509f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f28289a4129 in  () at /usr/lib64/libQt5WebEngineCore.so.5
#2  0x7f28289a4840 in  () at /usr/lib64/libQt5WebEngineCore.so.5
#3  0x7f28289a4a10 in  () at /usr/lib64/libQt5WebEngineCore.so.5
#4  0x7f28289a15cd in  () at /usr/lib64/libQt5WebEngineCore.so.5
#5  0x7f283122f474 in start_thread () at /lib64/libpthread.so.0
#6  0x7f28353883ed in clone () at /lib64/libc.so.6

Thread 32 (Thread 0x7f26e9683700 (LWP 2726)):
#0  0x7f2830623034 in g_mutex_unlock () at /usr/lib64/libglib-2.0.so.0
#1  0x7f28305de57c in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#2  0x7f28305def5b in  () at /usr/lib64/libglib-2.0.so.0
#3  0x7f28305df14c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#4  0x7f2835ec2aeb in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#5  0x7f2835e6a76a in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#6  0x7f2835c903b3 in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#7  0x7f2835c952d8 in  () at /usr/lib64/libQt5Core.so.5
#8  0x7f283122f474 in start_thread () at /lib64/libpthread.so.0
#9  0x7f28353883ed in clone () at /lib64/libc.so.6

Thread 31 (Thread 0x7f26e9e84700 (LWP 2724)):
#0  0x7f283537fa1d in poll () at /lib64/libc.so.6
#1  0x7f28305df036 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f28305df14c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f2835ec2aeb in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f2835e6a76a in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f2835c903b3 in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7f2835c952d8 in  () at /usr/lib64/libQt5Core.so.5
#7  0x7f283122f474 in start_thread () at /lib64/libpthread.so.0
#8  0x7f28353883ed in clone () at /lib64/libc.so.6

Thread 30 (Thread 0x7f26f9421700 (LWP 2716)):
#0  0x7f2830623034 in g_mutex_unlock () at /usr/lib64/libglib-2.0.so.0
#1  0x7f28305de57c in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#2  0x7f28305def5b in  () at /usr/lib64/libglib-2.0.so.0
#3  0x7f28305df14c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#4  0x7f2835ec2aeb in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#5  0x7f2835e6a76a in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#6  0x7f2835c903b3 in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#7  0x7f2835c952d8 in  () at /usr/lib64/libQt5Core.so.5
#8  0x7f283122f474 in start_thread () at /lib64/libpthread.so.0
#9  0x7f28353883ed in clone () at /lib64/libc.so.6

Thread 29 (Thread 0x7f26f9c22700 (LWP 2714)):
#0  0x7f283537ba7d in read () at /lib64/libc.so.6
#1  0x7f2830621c70 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f28305deb06 in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f28305defd4 in  () at /usr/lib64/libglib-2.0.so.0
#4  0x7f28305df14c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#5  0x7f2835ec2aeb in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#6  0x7f2835e6a76a in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#7  0x7f2835c903b3 in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#8  0x7f2835c952d8 in  () at /usr/lib64/libQt5Core.so.5
#9  0x7f283122f474 in start_thread () at /lib64/libpthread.so.0
#10 0x7f28353883ed in clone () at /lib64/libc.so.6

Thread 28 (Thread 0x7f26fa863700 (LWP 2711)):
#0  0x7fff1e38fadc in clock_gettime ()
#1  0x7f28353950a6 in clock_gettime () at /lib64/libc.so.6
#2  0x7f2835d40d96 in  () at /usr/lib64/libQt5Core.so.5
#3  0x7f2835ec0699 in QTimerInfoList::updateCu

[Akonadi] [Bug 338186] Since updating to the latest Kubuntu packages Kmail is not picking up imap mail.

2016-03-22 Thread Michael Fuchs via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=338186

--- Comment #103 from Michael Fuchs  ---
Thanks for taking care of this.

-- 
You are receiving this mail because:
You are watching all bug changes.


[Akonadi] [Bug 338186] Since updating to the latest Kubuntu packages Kmail is not picking up imap mail.

2015-12-21 Thread Michael Fuchs via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=338186

--- Comment #90 from Michael Fuchs  ---
With Kmail 5.1 (kmail 15.12 on ArchLinux) I found another workaround:

This time you got to disable "Enable server-side subscriptions" then the mails
in inbox also appear. Changing the "Download all meeages for offline use."
option doesn't have a positive nor negative effect.

-- 
You are receiving this mail because:
You are watching all bug changes.


[Akonadi] [Bug 338186] Since updating to the latest Kubuntu packages Kmail is not picking up imap mail.

2015-12-30 Thread Michael Fuchs via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=338186

--- Comment #94 from Michael Fuchs  ---
As I wrote before the courier devs won't solve this bug, because they don't
think it actually *is* a bug.

http://sourceforge.net/p/courier/mailman/message/33686723/

KMail is the only IMAP-Client i know, which has such massive problems with
courier servers.

-- 
You are receiving this mail because:
You are watching all bug changes.


  1   2   >