Bug 2281 - KDE 4 Pops up three annoying pop-ups upon every switch of Amarok song.
Summary: KDE 4 Pops up three annoying pop-ups upon every switch of Amarok song.
Status: RESOLVED WORKSFORME
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: i586 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-07-26 10:09 CEST by Shlomi Fish
Modified: 2011-08-02 17:58 CEST (History)
1 user (show)

See Also:
Source RPM: kdebase4-workspace-4.6.95-1.mga2.src.rpm
CVE:
Status comment:


Attachments

Description Shlomi Fish 2011-07-26 10:09:36 CEST
Description of problem:

My KDE 4 Pops up three annoying pop-ups whenever a new Amarok song is played, instead of one. This irritates me to no end. How can I fix this problem?

Reproducible: every time.
Manuel Hiebel 2011-07-26 18:25:07 CEST

CC: (none) => balcaen.john

Comment 1 John Balcaen 2011-07-26 19:39:32 CEST
I can't reproduce here (on x86_64) , but i'm already using 4.7.0
Could you please test again on thursday ? (KDE SC 4.7.0 should be out @ this moment).
Comment 2 Shlomi Fish 2011-08-01 15:39:16 CEST
Hi John, thanks for your reply.

(In reply to comment #1)
> I can't reproduce here (on x86_64) , but i'm already using 4.7.0
> Could you please test again on thursday ? (KDE SC 4.7.0 should be out @ this
> moment).

OK, it's already Monday and it's still happening with KDE 4.7.0. Same problem exactly. It's possible that it's a misconfiguration problem which KDE cannot quite handle properly. And I get x3 pop-ups for most other KDE notifications. How can I investigate it further? Should I report it upstream?
Comment 3 John Balcaen 2011-08-01 18:07:12 CEST
(In reply to comment #2)
[...]

>And I get x3 pop-ups for most other KDE notifications.
> How can I investigate it further? Should I report it upstream?

Hum thist is more problematic.
Could you reproduce eventually with the  xguest user ?
Comment 4 Shlomi Fish 2011-08-01 19:54:30 CEST
(In reply to comment #3)
> (In reply to comment #2)
> [...]
> 
> >And I get x3 pop-ups for most other KDE notifications.
> > How can I investigate it further? Should I report it upstream?
> 
> Hum thist is more problematic.

Indeed.

> Could you reproduce eventually with the  xguest user ?

Sorry, but I cannot exhibit the bug in the kdetest user. And it's hard to know how to get KDE to the point where it exhibits the bug. So I guess what I'm going to do now is to bisect ~/.kde4/share/config . Well, I guess that's one way to spend an evening...

These bugs give my life purpose.

Regards,

-- Shlomi Fish
Comment 5 Shlomi Fish 2011-08-01 20:49:06 CEST
(In reply to comment #4)
> (In reply to comment #3)
> > (In reply to comment #2)
> > [...]
> > 
> > >And I get x3 pop-ups for most other KDE notifications.
> > > How can I investigate it further? Should I report it upstream?
> > 
> > Hum thist is more problematic.
> 
> Indeed.
> 
> > Could you reproduce eventually with the  xguest user ?
> 
> Sorry, but I cannot exhibit the bug in the kdetest user. And it's hard to know
> how to get KDE to the point where it exhibits the bug. So I guess what I'm
> going to do now is to bisect ~/.kde4/share/config . Well, I guess that's one
> way to spend an evening...
> 
> These bugs give my life purpose.
> 

Just to keep you up-to-date - after a small amount of bisection, I realised the problem was with my plasma-desktop-appletsrc:

http://paste.debian.net/124776/

I see three =notifications$ lines there, but the question is which ones I need to remove. Can you shed any light on the problem? I am unable to get any help on #kde on Freenode.

Regards,

-- Shlomi Fish
Comment 6 John Balcaen 2011-08-01 21:40:55 CEST
i would try to remove thoses lines :


[Containments][2][Applets][9][Configuration][Applets][71]
geometry=0,0,48,48
immutability=1
plugin=notifications
zvalue=0

[Containments][2][Applets][9][Configuration][Applets][71][Configuration][ExtenderItems][6]
extenderIconName=dialog-information
extenderItemName=jobGroup
extenderItemPosition=0
extenderTitle=Jobs
isCollapsed=true
isGroup=true
sourceAppletId=71
sourceAppletPluginName=notifications

[Containments][28][Applets][92][Configuration][Applets][94]
geometry=0,0,48,48
immutability=1
plugin=notifications
zvalue=0

[Containments][28][Applets][92][Configuration][Applets][94][Configuration][ExtenderItems][8]
extenderIconName=dialog-information
extenderItemName=jobGroup
extenderTitle=Jobs
isCollapsed=true
isGroup=true
sourceAppletId=94
sourceAppletPluginName=notifications
Comment 7 Shlomi Fish 2011-08-02 17:58:10 CEST
Hi John,

(In reply to comment #6)
> i would try to remove thoses lines :
> 

thanks for your advice. However, per advice from people on #kde (who finally answered) I decided to move away the offending file, because it acquired craft. Someone told me he nukes it ever 8 months. Now the offending symptom has disappeared, but so have my virtual desktops' wallpaper's configuration, which I'll have to reconfigure.

So I'm closing this bug because apparently it's a quality (or a misfeature) of KDE's architecture.

Regards,

-- Shlomi Fish

> 
> [Containments][2][Applets][9][Configuration][Applets][71]
> geometry=0,0,48,48
> immutability=1
> plugin=notifications
> zvalue=0
> 
> [Containments][2][Applets][9][Configuration][Applets][71][Configuration][ExtenderItems][6]
> extenderIconName=dialog-information
> extenderItemName=jobGroup
> extenderItemPosition=0
> extenderTitle=Jobs
> isCollapsed=true
> isGroup=true
> sourceAppletId=71
> sourceAppletPluginName=notifications
> 
> [Containments][28][Applets][92][Configuration][Applets][94]
> geometry=0,0,48,48
> immutability=1
> plugin=notifications
> zvalue=0
> 
> [Containments][28][Applets][92][Configuration][Applets][94][Configuration][ExtenderItems][8]
> extenderIconName=dialog-information
> extenderItemName=jobGroup
> extenderTitle=Jobs
> isCollapsed=true
> isGroup=true
> sourceAppletId=94
> sourceAppletPluginName=notifications

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


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