Summary: | hal makes nautilus crash on removing media | ||
---|---|---|---|
Product: | hal | Reporter: | Vladimir Kokarev <matrix47> |
Component: | libhal | Assignee: | David Zeuthen (not reading bugmail) <zeuthen> |
Status: | REOPENED --- | QA Contact: | |
Severity: | normal | ||
Priority: | medium | CC: | fhimpe, matrix47 |
Version: | unspecified | ||
Hardware: | x86-64 (AMD64) | ||
OS: | Linux (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: | ||
Attachments: | crash stack trace |
If nautilius crash because a device was removed in HAL it's a problem of Nautilis and not HAL. Please report the problem to GNOME. here's gnome bug, where I was told to report it here: http://bugzilla.gnome.org/show_bug.cgi?id=564894 Except when Nautilus is crashing because of something happening inside of libhal, which we clearly can't do anything about: at libhal.c:1065 ~filter_func(). #6 0x00000000007e7640 in ?? () #7 0x00007f1826fd3e39 in filter_func (connection=0x81dd40, message=0x95d490, user_data=<value optimized out>) at libhal.c:1065 udi = 0x93e004 "/org/freedesktop/Hal/devices/volume_empty_dvd_plus_r" object_path = 0x9b3418 "/org/freedesktop/Hal/Manager" error = {name = 0x0, message = 0x0, dummy1 = 1, dummy2 = 0, dummy3 = 0, dummy4 = 0, dummy5 = 1, padding1 = 0x80fb10} ctx = (LibHalContext *) 0x8320c0 It'd be nice to have a better stacktrace to see where exactly it's crashing, but it can't be far from there. (In reply to comment #3) > Except when Nautilus is crashing because of something happening inside of > libhal, which we clearly can't do anything about: "We" being the Nautilus source, of course. A. Walton: can you suggest a method for getting a better stacktrace? |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.
Created attachment 22138 [details] crash stack trace when I remove any removeable device from my pc, nautilus crashes this happens, for example, when I eject dvd drive or detach an usb-webcam my hal version is 0.5.11 the bug remained with 0.5.12rc1