On Mon, Feb 15, 2010 at 1:55 PM, Michael Biebl <[email protected]> wrote: > Teodor MICU wrote: >> On Mon, Feb 15, 2010 at 12:38 PM, Martin Pitt <[email protected]> wrote: >>> Teodor [2010-02-15 11:44 +0200]: >>>> Justification: renders package unusable >>> I downgraded this to important, since it does not affect all users. >> >> It does for me on all 3 desktop hosts running Debian (squeeze/testing). > > Could you explain in more detail what kind of setup you are using (partitions, > lvm, hardware, ide/sata driver). Is this setup identical on all 3 desktops?
I use 'lvm2' only on my home desktop. For my work desktop and laptop I have only a single ROOT system partition (no software/hardware RAID setup). All of them are on SATA, including the CD/DVD writer. > How do you trigger the crash? > Does it happen when you insert/remove external hardware? I don't do anything special, it just doesn't respond to any "Unmount" command and that 'segfault' at every session start (if it doesn't already run). >> The files are attached, but probably some extra libraries should be >> installed for the missing debugging symbols. > > To get a more meaningfull backtrace, please follow the instructions on [1] Please excuse me for not knowing which debug package to install. I've searched for a -dbg package for 'devicekit*/disk*' and found none. I've installed libc6-dbg and because of this you could see some info about the latest symbol in the previously attached 'gdb' trace. Thanks -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/[email protected]
