FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Debian > Debian KDE

 
 
LinkBack Thread Tools
 
Old 06-06-2010, 09:50 AM
Ritesh Raj Sarraf
 
Default broken kde notifications

Hello Modestas,

On Sunday 06 Jun 2010 14:24:27 Modestas Vainius wrote:
> > Here's the link to the screenshot.
> > http://www.researchut.com/tmp/knotify.jpeg
>
> Terminate GNOME processes?

I'm not sure what you mean here. The screenshot shows kopete notifying through
some GNOME notification. My installation tends to be gnome minimal. Acutally, I
don't have any gnome apps installed. Whatever is there is mostly libs pulled
as dependencies.

Can you be specific on what GNOME processes ? My check did not yield even a
single one. I do have a bunch of gtk processes (wicd, virt-manager)


Ritesh
--
Ritesh Raj Sarraf | http://people.debian.org/~rrs
 
Old 06-06-2010, 10:00 AM
Modestas Vainius
 
Default broken kde notifications

Hello,

On sekmadienis 06 Birželis 2010 12:50:40 Ritesh Raj Sarraf wrote:
> Hello Modestas,
>
> On Sunday 06 Jun 2010 14:24:27 Modestas Vainius wrote:
> > > Here's the link to the screenshot.
> > > http://www.researchut.com/tmp/knotify.jpeg
> >
> > Terminate GNOME processes?
>
> I'm not sure what you mean here. The screenshot shows kopete notifying
> through some GNOME notification. My installation tends to be gnome
> minimal. Acutally, I don't have any gnome apps installed. Whatever is
> there is mostly libs pulled as dependencies.
>
> Can you be specific on what GNOME processes ? My check did not yield even a
> single one. I do have a bunch of gtk processes (wicd, virt-manager)

I don't know, I'm not a GNOME expect nor I want to be. But afaik notifications
are desktop-independent and relayed through DBus. So there is a GNOME
application listening on the specific DBus signal (I guess `qdbus
org.freedesktop.Notifications /org/freedesktop/Notifications` stuff) and
preventing KDE plasma desktop from taking the service over.

--
Modestas Vainius <modestas@vainius.eu>
 
Old 06-06-2010, 12:35 PM
Kevin Krammer
 
Default broken kde notifications

On Sunday, 2010-06-06, Modestas Vainius wrote:
> Hello,
>
> On sekmadienis 06 Birželis 2010 12:50:40 Ritesh Raj Sarraf wrote:
> > Hello Modestas,
> >
> > On Sunday 06 Jun 2010 14:24:27 Modestas Vainius wrote:
> > > > Here's the link to the screenshot.
> > > > http://www.researchut.com/tmp/knotify.jpeg
> > >
> > > Terminate GNOME processes?
> >
> > I'm not sure what you mean here. The screenshot shows kopete notifying
> > through some GNOME notification. My installation tends to be gnome
> > minimal. Acutally, I don't have any gnome apps installed. Whatever is
> > there is mostly libs pulled as dependencies.
> >
> > Can you be specific on what GNOME processes ? My check did not yield even
> > a single one. I do have a bunch of gtk processes (wicd, virt-manager)
>
> I don't know, I'm not a GNOME expect nor I want to be. But afaik
> notifications are desktop-independent and relayed through DBus. So there
> is a GNOME application listening on the specific DBus signal (I guess
> `qdbus
> org.freedesktop.Notifications /org/freedesktop/Notifications` stuff) and
> preventing KDE plasma desktop from taking the service over.

Probably notification-daemon or notify-osd.
Once a process claims specified D-Bus name for the notification system, it
owns it. All other programs capable of being a notification provider just
don't get any of the calls.

So if this happens with a clean session, something might have either invoked
the other notification provider before plasma-desktop could claim it or
something created a notification and D-Bus decided to activate one (not sure
if any of the notification providers install a .service file for that though)

Cheers,
Kevin
 
Old 06-06-2010, 05:45 PM
Ritesh Raj Sarraf
 
Default broken kde notifications

Thanks. Purging notification-daemon solved the problem.

Should the kde-full or kde-desktop metapackage have a conflicts on stuff
like these ? An end user will not be aware how the notifications went
broken.

Ritesh


Kevin Krammer wrote:

> On Sunday, 2010-06-06, Modestas Vainius wrote:
>> Hello,
>>
>> On sekmadienis 06 Birželis 2010 12:50:40 Ritesh Raj Sarraf wrote:
>> > Hello Modestas,
>> >
>> > On Sunday 06 Jun 2010 14:24:27 Modestas Vainius wrote:
>> > > > Here's the link to the screenshot.
>> > > > http://www.researchut.com/tmp/knotify.jpeg
>> > >
>> > > Terminate GNOME processes?
>> >
>> > I'm not sure what you mean here. The screenshot shows kopete notifying
>> > through some GNOME notification. My installation tends to be gnome
>> > minimal. Acutally, I don't have any gnome apps installed. Whatever is
>> > there is mostly libs pulled as dependencies.
>> >
>> > Can you be specific on what GNOME processes ? My check did not yield
>> > even a single one. I do have a bunch of gtk processes (wicd,
>> > virt-manager)
>>
>> I don't know, I'm not a GNOME expect nor I want to be. But afaik
>> notifications are desktop-independent and relayed through DBus. So there
>> is a GNOME application listening on the specific DBus signal (I guess
>> `qdbus
>> org.freedesktop.Notifications /org/freedesktop/Notifications` stuff) and
>> preventing KDE plasma desktop from taking the service over.
>
> Probably notification-daemon or notify-osd.
> Once a process claims specified D-Bus name for the notification system, it
> owns it. All other programs capable of being a notification provider just
> don't get any of the calls.
>
> So if this happens with a clean session, something might have either
> invoked the other notification provider before plasma-desktop could claim
> it or something created a notification and D-Bus decided to activate one
> (not sure if any of the notification providers install a .service file for
> that though)
>
> Cheers,
> Kevin

--
Given the large number of mailing lists I follow, I request you to CC me
in replies for quicker response


--
To UNSUBSCRIBE, email to debian-kde-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: if3td7-8pl.ln1@news.researchut.com">http://lists.debian.org/if3td7-8pl.ln1@news.researchut.com
 
Old 06-06-2010, 06:58 PM
Ral Snchez Siles
 
Default broken kde notifications

Hello:

El Domingo, 6 de Junio de 2010, Ritesh Raj Sarraf escribi:
> Thanks. Purging notification-daemon solved the problem.
>
> Should the kde-full or kde-desktop metapackage have a conflicts on stuff
> like these ? An end user will not be aware how the notifications went
> broken.
>
> Ritesh

Pretty please, don't top post....

Going into the issue, it happens that I have notification-daemon installed
and I do have plasma notifications. I wonder why.

Regards,

[...]

--
Ral Snchez Siles
----->Proud Debian user<-----
Linux registered user #416098
 
Old 06-06-2010, 07:01 PM
Kevin Krammer
 
Default broken kde notifications

On Sunday, 2010-06-06, Ritesh Raj Sarraf wrote:
> Thanks. Purging notification-daemon solved the problem.
>
> Should the kde-full or kde-desktop metapackage have a conflicts on stuff
> like these ? An end user will not be aware how the notifications went
> broken.

I don't think this can be solved at a packaging level, a system might be
serving multiple kinds of desktops to different users.

The interesting bit of information would be how the "wrong" notification
provider got started, e.g. whether it was launched by another process or
created through D-Bus activation.

In the first case it would be interesting to know which program that was and
why it does that.

In the second case it would be interesting to see if D-Bus can be told to
start the correct one.

Cheers,
Kevin
 
Old 06-06-2010, 07:51 PM
Modestas Vainius
 
Default broken kde notifications

Hello,

On sekmadienis 06 Birželis 2010 20:45:54 Ritesh Raj Sarraf wrote:
> Thanks. Purging notification-daemon solved the problem.
>
> Should the kde-full or kde-desktop metapackage have a conflicts on stuff
> like these ? An end user will not be aware how the notifications went
> broken.

Now ask yourself if it really makes sense for KDE to conflict with GNOME at
packaging level. My reaction would be: huh, KDE and GNOME cannot be installed
on the system, wtf?

--
Modestas Vainius <modestas@vainius.eu>
 
Old 06-06-2010, 08:02 PM
Ritesh Raj Sarraf
 
Default broken kde notifications

On Monday 07 Jun 2010 01:21:49 Modestas Vainius wrote:
> Hello,
>
> On sekmadienis 06 Birželis 2010 20:45:54 Ritesh Raj Sarraf wrote:
> > Thanks. Purging notification-daemon solved the problem.
> >
> > Should the kde-full or kde-desktop metapackage have a conflicts on stuff
> > like these ? An end user will not be aware how the notifications went
> > broken.
>
> Now ask yourself if it really makes sense for KDE to conflict with GNOME at
> packaging level. My reaction would be: huh, KDE and GNOME cannot be
> installed on the system, wtf?

Okay!! But please fix this. If I have a KDE DE and a bunch of gtk/gnome tools
which pull in notification-daemon, KDE's notification gets hijacked.


--
Ritesh Raj Sarraf | http://people.debian.org/~rrs
 
Old 06-06-2010, 09:09 PM
Kevin Krammer
 
Default broken kde notifications

On Sunday, 2010-06-06, Ritesh Raj Sarraf wrote:
> On Monday 07 Jun 2010 01:21:49 Modestas Vainius wrote:
> > Hello,
> >
> > On sekmadienis 06 Birželis 2010 20:45:54 Ritesh Raj Sarraf wrote:
> > > Thanks. Purging notification-daemon solved the problem.
> > >
> > > Should the kde-full or kde-desktop metapackage have a conflicts on
> > > stuff like these ? An end user will not be aware how the notifications
> > > went broken.
> >
> > Now ask yourself if it really makes sense for KDE to conflict with GNOME
> > at packaging level. My reaction would be: huh, KDE and GNOME cannot be
> > installed on the system, wtf?
>
> Okay!! But please fix this. If I have a KDE DE and a bunch of gtk/gnome
> tools which pull in notification-daemon, KDE's notification gets hijacked.

Do you have any of these tools in autostart or in a saved session?
notification-daemon needs to start before plasma-desktop to be able to
successfully claim the D-Bus name.

Cheers,
Kevin
 
Old 06-06-2010, 09:41 PM
George Kiagiadakis
 
Default broken kde notifications

On Sun, Jun 6, 2010 at 8:45 PM, Ritesh Raj Sarraf <rrs@debian.org> wrote:
> Thanks. Purging notification-daemon solved the problem.
>
> Should the kde-full or kde-desktop metapackage have a conflicts on stuff
> like these ? An end user will not be aware how the notifications went
> broken.
>
> Ritesh

Please no. Personally, I use notification-daemon in kde, as I find it
somewhat better than the kde notifications, which are quite broken in
4.4 (but used to be fine in 4.3), so such a conflict would just give
me a nightmare.

Note that notification-daemon doesn't start automatically if it is
installed. It starts together with gnome applications, so you are
probably running a gnome application that causes the trouble. In an
ideal world, gnome applications should detect and use the kde
notification system, just like kde does with the gnome one. I'm not
sure about the details, but I bet this is something to be fixed in
gnome.

Regards,
George


--
To UNSUBSCRIBE, email to debian-kde-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: AANLkTilBlPBiAs5JwxdNAgarzrb20Wf61kcV8izn805w@mail .gmail.com">http://lists.debian.org/AANLkTilBlPBiAs5JwxdNAgarzrb20Wf61kcV8izn805w@mail .gmail.com
 

Thread Tools




All times are GMT. The time now is 09:49 PM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org