Thanks Ethan - I'm going to close this one again for now, as you should
be able to submit a crash report with Apport (and this bug doesn't look
related to gnome-settings-daemon anyway.
** Changed in: gnome-settings-daemon (Ubuntu)
Status: Incomplete => Invalid
--
SIGSEGV when opening file
Well I'll be darned - I thought Apport was enabled by default in Karmic.
I guess not. My fault - I assumed it was somehow a type of crash that
was bypassing the detection.
Sorry about that!
--
SIGSEGV when opening files
https://bugs.launchpad.net/bugs/399842
You received this bug notification be
2009/7/17 Sebastien Bacher :
> did you enable apport as described on the wiki documentation?
>
> ** Changed in: gnome-settings-daemon (Ubuntu)
> Status: New => Incomplete
>
> --
> SIGSEGV when opening files
> https://bugs.launchpad.net/bugs/399842
> You received this bug notification because
the stacktrace also lack debug symbols for libdbus and gvfs and gedit
--
SIGSEGV when opening files
https://bugs.launchpad.net/bugs/399842
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubu
did you enable apport as described on the wiki documentation?
** Changed in: gnome-settings-daemon (Ubuntu)
Status: New => Incomplete
--
SIGSEGV when opening files
https://bugs.launchpad.net/bugs/399842
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
Sorry for the spam - meant to put this in the last one.
(gdb) bt
#0 0x00c3f204 in ?? () from /lib/libdbus-1.so.3
#1 0x00c2c62d in ?? () from /lib/libdbus-1.so.3
#2 0x00c2c699 in ?? () from /lib/libdbus-1.so.3
#3 0x00c2b5e7 in ?? () from /lib/libdbus-1.so.3
#4 0x00c2c770 in ?? () from /lib/li
The segfault appears to be in dbus:
(gdb) run
Starting program: /usr/bin/gedit
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
process 28193: type array 97 not a basic type
process 28193: type array 97 not a basic type
process 28193: type in
Please don't close for required crash report when none is generated.
** Changed in: gnome-settings-daemon (Ubuntu)
Status: Invalid => New
--
SIGSEGV when opening files
https://bugs.launchpad.net/bugs/399842
You received this bug notification because you are a member of Ubuntu
Bugs, which
There is no crash file generated by the programs.
It seems to be just about anything that uses the GTK+ file chooser
dialog will crash with SIGSEGV - no .crash report is generated.
This is in Karmic.
~/src/agoban-0.6$ ./agoban
runs... then click on "open file":
process 21297: type array 97 not
Thank you for taking the time to report this bug and helping to make Ubuntu
better. However, your crash report is either missing or challenging to deal
with as a '.crash' file. Please follow these instructions to have apport report
a new bug about your crash that can be dealt with by the automat
The problem is gone after reverting gvfs back to 1.3.1-0ubuntu2 from
1.3.2-0ubuntu1 so I'm doubt now who the culprit is.
How can I link this bug to package gvfs?
Regards,
maykel
--
SIGSEGV when opening files
https://bugs.launchpad.net/bugs/399842
You received this bug notification because you a
11 matches
Mail list logo
