don't reopen expired bugs if you are not the original submiter, report a
new bug instead
** Changed in: nautilus (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Not sure if it is the same issue. Also a segfault though. gdb and
valgrind logs attached.
** Attachment added: "nautilus-crash-logs.tgz"
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1607711/+attachment/5001907/+files/nautilus-crash-logs.tgz
--
You received this bug notification
** Changed in: nautilus (Ubuntu)
Status: Expired => Confirmed
** Changed in: nautilus (Ubuntu)
Status: Confirmed => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1607711
Title:
[Expired for nautilus (Ubuntu) because there has been no activity for 60
days.]
** Changed in: nautilus (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I uninstalled python-nautilus package and rebooted and then I did not
get SIGSEGV for some time, but now I again started getting this crash:
misel@misel-amphinicy[~]:
[13:59:13] $ nautilus
Maximum number of clients reached
** (nautilus:29472): WARNING **: Could not open X display
Initializing
On Fri, Jul 29, 2016 at 1:47 PM, Sebastien Bacher
wrote:
> do you get the issue without python-nautilus installed?
> --
>
I'll try out and get back with the results...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
do you get the issue without python-nautilus installed?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1607711
Title:
Starting nautilus crashes with Segmentation Fault
To manage notifications about
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please try to obtain a backtrace following the
instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload
the backtrace (as an attachment) to the bug report. This will greatly
help us in tracking down