After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 158893 - Starting up computer rin desktop Gnome results in unexpected interruption of eggcups
Starting up computer rin desktop Gnome results in unexpected interruption of ...
Status: RESOLVED DUPLICATE of bug 151307
Product: eggcups
Classification: Deprecated
Component: notification
unspecified
Other other
: Normal normal
: ---
Assigned To: eggcups maintainers
eggcups maintainers
Depends on:
Blocks:
 
 
Reported: 2004-11-21 10:05 UTC by Jaap Woldringh
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Jaap Woldringh 2004-11-21 10:06:03 UTC
Distribution: Fedora Core release 3 (Heidelberg)
Package: eggcups
Severity: major
Version: GNOME2.8.0 unspecified
Gnome-Distributor: Red Hat, Inc
Synopsis: Starting up computer rin desktop Gnome results in unexpected interruption of eggcups
Bugzilla-Product: eggcups
Bugzilla-Component: notification
Bugzilla-Version: unspecified
BugBuddy-GnomeVersion: 2.0 (2.8.0)
Description:
Description of the crash: Starting up the computer in Gnome (2.8)
results in a message that the application "volume manager" is
interrupted unexpectedly, and immediately after that  follows the same
message for "eggcups". The option to restart gives the same result.
As far as I can see I can still use the computer in Gnome, and can halt
it or reboot it regularly using a terminal in a virtual desktop.

Steps to reproduce the crash:
1. Starting the computer in Gnome desktop
2. 
3. 

Expected Results: A regular startup without error


How often does this happen?
Every time computer is started in Gnome.
It did so too when starting in KDE, but after removing some desktop
links to KDE programs (Knode, Kmahjongg and some other links) it now
starts up in KDE as expected.


Additional Information: At the installation on Monday last week KDE was
installed, and only some days later Gnome. Both ran as expected, but two
days ago shutting off Gnome with some programs active, among which some
KDE programs (Kstars and some other programs) this lasted an unexpected
long time (I did not note how long, only in retrospect I remember that
it lasted longer than I expected).

After that Gnome gave this error every time on firing up, both kernels
(667 and 678) and in KDE too. After removing some desktop links of KDE
programs KDE now starts up well......

I also note that the Gnome panel is empty, except for the virtual
desktops icon.

The installation is fully updated.

I hope this will help you find the cause of this bug :)



Debugging Information:

Backtrace was generated from '/usr/bin/eggcups'

(no debugging symbols found)...Using host libthread_db library
"/lib/tls/libthread_db.so.1".
(no debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...(no debugging symbols found)...(no debugging
symbols found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...[Thread debugging using
libthread_db enabled]
[New Thread -151144768 (LWP 3277)]
(no debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...(no debugging symbols found)...(no debugging
symbols found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...0x004fb7a2 in _dl_sysinfo_int80
() from /lib/ld-linux.so.2

Thread 1 (Thread -151144768 (LWP 3277))

  • #0 _dl_sysinfo_int80
    from /lib/ld-linux.so.2
  • #1 __waitpid_nocancel
    from /lib/tls/libpthread.so.0
  • #2 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 ??
  • #5 dbus_connection_setup_with_g_main
    from /usr/lib/libdbus-glib-1.so.0
  • #6 ec_tray_icon_show_about_window
  • #7 g_child_watch_add
    from /usr/lib/libglib-2.0.so.0
  • #8 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #9 g_main_context_acquire
    from /usr/lib/libglib-2.0.so.0
  • #10 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #11 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #12 main




------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-11-21 05:06 -------


Unknown platform unknown. Setting to default platform "Other".
Unknown milestone "unknown" in product "eggcups".
   Setting to default milestone for this product, '---'
The original reporter of this bug does not have
   an account here. Reassigning to the person who moved
   it here, unknown@bugzilla.gnome.org.
   Previous reporter was jjh.woldringh@planet.nl.
Setting to default status "UNCONFIRMED".
Setting qa contact to the default for this product.
   This bug either had no qa contact or an invalid one.

Comment 1 Jaap Woldringh 2004-11-21 12:26:26 UTC
Original reporter of this bug wants to add that platform is Fedora Core 3 on an
i686 computer.
And I have now created an account with Bugzilla :)
Comment 2 Elijah Newren 2004-11-21 14:37:08 UTC
Thanks for the bug report. This particular bug has already been reported into
our bug tracking system, but please feel free to report any further bugs you find.

*** This bug has been marked as a duplicate of 151307 ***
Comment 3 Jaap Woldringh 2004-11-21 15:40:45 UTC
Tried the fix proposed in 158178, where the same bug is mentioned (sorry for a
duplicate bugreport, I am new in this).
Before I tried it I tried whether Gnome was still (after some use of the
computer) starting Gnome with an error, and it seemed to start  up well. Same
after the "fix":

====
/usr/sbin/prelink /usr/lib/libdbus*so*

And see if that fixes the problem
====

so I don't know whther the bug is really fixed this way.

But:

Shutting down the computer with (I use the Dutch language and have to try and
retranslate) Actions in the panel I get the same error as I did before which is
why I had to shut down or reboot in a terminal:

Application Gnome-panel is interrupted unexpectedly.

So this is not fixed.

For all clarity: this latter bug (the panel one) was not present before the
eggcups one. Rather they appeared at the same time.

This bug is a look-alike of the bug 158845 where it is aid:

=====
I was just browsing the web using firefox when all of the sudden the
error message "gnome-panel" has quit un expectedly pops up.  My options
are to restart application or close.  Choosing "close" just makes the
error message keep popping up over and over again and restart
application just says that the application is already running.
====

only with me it when shutting down from the panel. So far Firefox works beautifully.