Bug 9527 - KDE systray notifications not working properly on new accounts
Summary: KDE systray notifications not working properly on new accounts
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 3
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-03-24 16:35 CET by Carlos Vives
Modified: 2015-03-31 16:04 CEST (History)
4 users (show)

See Also:
Source RPM: kdebase4-workspace-4.10.1-1.mga3.src.rpm
CVE:
Status comment:


Attachments
Notification received (74.98 KB, image/jpeg)
2013-03-24 16:36 CET, Carlos Vives
Details
Clicking on the (invisible) notification systray indicator (115.76 KB, image/jpeg)
2013-03-24 16:37 CET, Carlos Vives
Details

Description Carlos Vives 2013-03-24 16:35:22 CET
Description of problem:
KDE systray notification indicator is broken in new accounts. Notification popups are shown properly, but a second copy is shown at the upper-left corner of the desktop. Those copys don't go away but stay until cleared from the notification list.
Systray notification indicator is never shown, but it's still there nonetheless. Clicking on its approximate location shows a copy of the shadow copy notifications instead of the classic popup, background included.

Old accounts are unaffected. I've stumbled upon this bug a few days ago when installing Cauldron on a second computer, but new accounts on my regular computer are affected too.
My old account is a Mandriva -> Mageia 2 -> Mageia 3 account, and it's still using the old autostart/plasma-desktop.desktop system, so maybe there's a problem with plasma-desktop loading order.

Removing notifications from systray and adding a second notification plasmoid serves as a workaround and behaves as expected.

As far as i can tell there's no bug open upstream about this.

.xsession-errors:
plasmapackage:/ui/NotificationDelegate/NotificationDelegate.qml:143:13: QML Item: Detectado bucle de enlace para la propiedad «height»
file:///usr/lib64/kde4/imports/org/kde/plasma/extras/ScrollArea.qml:96: TypeError: Result of expression 'verticalScrollBar' [null] is not an object.
file:///usr/share/apps/plasma/plasmoids/org.kde.notifications/contents/ui/main.qml:139:9: QML Flickable: Detectado posible bucle de anclaje en «fill».

Version-Release number of selected component (if applicable):


How reproducible:
Any notification triggers the error.

Steps to Reproduce:
1. Receive a notification on a new account
2. The notification systray is not shown and a shadow copy of the notification appears on the desktop


Reproducible: 

Steps to Reproduce:
Comment 1 Carlos Vives 2013-03-24 16:36:50 CET
Created attachment 3650 [details]
Notification received
Comment 2 Carlos Vives 2013-03-24 16:37:37 CET
Created attachment 3651 [details]
Clicking on the (invisible) notification systray indicator
Comment 3 AngryPenguin 2013-03-26 11:57:52 CET
I have this issue. Any know how fix it?

Mageia 3 KDE x64 Cauldron - all update.

CC: (none) => xpris

Comment 4 Manuel Hiebel 2013-05-28 23:16:08 CEST
still valid ?

Version: Cauldron => 3

Comment 5 mage man 2013-05-29 05:07:56 CEST
yes still valid. Have it on Mageia 3 KDE x64 fresh new install (only the old home user from Mageia2 home folder used but not the config file I believe)

CC: (none) => mageman

Comment 6 Alejandro Cobo 2013-06-08 14:36:14 CEST
Same problem on Mageia 3 KDE i586 fresh install with all partitions formated (reseted /home).

CC: (none) => alejandrocobo

Comment 7 Arnaud Vacquier 2013-11-29 19:33:37 CET
MGA4B1 too

CC: (none) => inster.css

Comment 8 Marja Van Waes 2015-03-31 16:04:13 CEST
Mageia 3 changed to end-of-life (EOL) status 4 months ago.
http://blog.mageia.org/en/2014/11/26/lets-say-goodbye-to-mageia-3/ 

Mageia 3 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of Mageia
please feel free to click on "Version" change it against that version of Mageia
and reopen this bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

--
The Mageia Bugsquad

Status: NEW => RESOLVED
Resolution: (none) => OLD


Note You need to log in before you can comment on or make changes to this bug.