539449 - Downloading a file causes "libnotify-Message: GetCapabilities call failed..." message in .xsession-errors

Status: RESOLVED WORKSFORME

(Firefox :: General, defect)

Description

[Graham Gordon]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-GB; rv:1.9.2) Gecko/20100105 Firefox/3.6
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-GB; rv:1.9.2) Gecko/20100105 Firefox/3.6

If I download a file from a web page (any), after the initial download, I get "libnotify-Message: GetCapabilities call failed: The name org.freedesktop.Notifications was not provided by any .service files" in my .xsession-errors file. The download completes and all appears to work, but the error message is recorded in the .xsession-errors file. This seems to only happen on the first download; subsequent downloads don't seem to bring up this error message.

I have tried this with a fresh profile (closed Firefox, renamed my ~/.mozilla directory and restarted Firefox) as well as my current profile (recently updated from 3.5.7 to 3.6rc1), but on both occasions, the same error message happens.

Reproducible: Sometimes

Steps to Reproduce:
1. Go to a website with a download link.
2. Click on download link to download file.
3. Save file.
4. Go and take a look at your .xsession-errors file in your favourite editor.
Actual Results:  
Download is successful, but .xsession-errors file contains "libnotify-Message: GetCapabilities call failed: The name org.freedesktop.Notifications was not provided by any .service files". Downloads after the initial one will appear not to touch the .xsession-errors file with an error message.

Expected Results:  
Download to be successful, but .xsession-errors file not touched.

I'm running Debian Lenny with Xfce (the version supplied by Debian Lenny). Pentium IV processor, 1GB RAM, 128MB Nvidia GeForce GX5200 video card.

Comment 1

[Graham Gordon]

Sorry for the additional noise, but to make it clear, in case there's any ambiguity, this happens to me on Firefox 3.6rc1. This didn't happen with 3.5.7.

Comment 2

[Tyler Downer [He/Him]]

Reporter, are you still seeing this issue with Firefox 3.6.13 or later in safe mode or a fresh profile? If not, please close. These links can help you in your testing.
http://support.mozilla.com/kb/Safe+Mode
http://support.mozilla.com/kb/Managing+profiles

Comment 3

[Tyler Downer [He/Him]]

This bug has had the CLOSEME tag for several weeks and the date in the tag is far gone. If the reporter can still see this issue, Please retest with Firefox 3.6.x or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). Then please remove the closeme tag in the whiteboard, mark the bug against the proper version and comment on the bug.

Comment 4

[Graham Gordon]

(In reply to comment #2)
> Reporter, are you still seeing this issue with Firefox 3.6.13 or later in safe
> mode or a fresh profile? If not, please close. These links can help you in your
> testing.
> http://support.mozilla.com/kb/Safe+Mode
> http://support.mozilla.com/kb/Managing+profiles

Sorry, I must have missed this posting. I don't have this issue any more, so it seems "fixed". Mind you, I'm currently using Firefox 4.0b12 and Debian Squeeze with Xfce. Still, it seems fixed, so I'll close this (hopefully I'm doing this right).

Comment 5

[Tyler Downer [He/Him]]

WFM actually, but thanks for the report