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 158787 - gnome-volume-manager crashes every time on login
gnome-volume-manager crashes every time on login
Status: RESOLVED DUPLICATE of bug 158702
Product: gnome-volume-manager
Classification: Deprecated
Component: general
unspecified
Other other
: Normal normal
: ---
Assigned To: Robert Love
Robert Love
Depends on:
Blocks:
 
 
Reported: 2004-11-20 05:39 UTC by vr10
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.7/2.8



Description vr10 2004-11-20 05:39:38 UTC
Distribution: Fedora Core release 3 (Heidelberg)
Package: gnome-volume-manager
Severity: blocker
Version: GNOME2.8.0 unspecified
Gnome-Distributor: Red Hat, Inc
Synopsis: gnome-volume-manager crashes every time on login
Bugzilla-Product: gnome-volume-manager
Bugzilla-Component: general
Bugzilla-Version: unspecified
BugBuddy-GnomeVersion: 2.0 (2.8.0)
Description:
Description of the crash:
I Recently installed a Fresh copy of Fedora Core 3, and then compiled a
new kernel with ntfs support. (I might have also updated a few packages
through up2date). Since then, each and every time i login (as myself, or
root), I first  get a dialog saying that gnome-volume-manager has
crashed, and then one saying eggcups has crashed (which keeps
reappearing). 
Then, I thought it must be because of the kernel, but on a reboot with
another kernel, I still got the same error. This leads me to believe
that I might have updated a few packages which are causing this problem.
The problem seems to originate from the HAL module, but I'm not sure.

Steps to reproduce the crash:
I'm not sure about the steps needed, but you could try the following:
1. Use a kernel (2.6.9+) with ntfs support
2. Use all the latest updates of Fedora Core 3
3. Login, and hope that it'll crash :)

Expected Results:
On logging in:
gnome-volume-manager crashes
eggcups crashes

How often does this happen?
Every time

Additional Information:



Debugging Information:

Backtrace was generated from '/usr/bin/gnome-volume-manager'

(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)...[Thread debugging using
libthread_db enabled]
[New Thread -151107360 (LWP 13660)]
(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)...(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)...0x002c37a2 in _dl_sysinfo_int80
() from /lib/ld-linux.so.2

Thread 1 (Thread -151107360 (LWP 13660))

  • #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 hal_initialize
    from /usr/lib/libhal.so.0
  • #6 main




------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-11-20 00:39 -------


Unknown platform unknown. Setting to default platform "Other".
Unknown milestone "unknown" in product "gnome-volume-manager".
   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 vr10@hotmail.com.
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 Elijah Newren 2004-11-20 05:50:30 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.

Matches the stack trace in bug 158775, which has been marked as a duplicate of
158702.

*** This bug has been marked as a duplicate of 158702 ***