Ok, maybe some progress. It appears I can search among a maximal number
of hits. So that depends per folder. And as soon as Nautilus start to
crash, I have to start all over by rebooting, as even small searches
then crash. (Logging out/in does not make a difference.)
For what it is worth, I:
1 -
*3 Sorry, " sudo cat /proc/sys/fs/inotify/max_user_watches " now gives:
524288
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1852053
Title:
Nautilus Crashes when opening
Well, it definitely is not gsconnect, as I disabled a week ago and the
crashing is back in full force.
I am trying to find some kind of pattern to make it predictable. But
it's mind-boggling so far. I wish few others had same issue ;)
--
You received this bug notification because you are a
Thanks, indeed that hint to a gsconnect issue, could you report it on
https://github.com/andyholmes/gnome-shell-extension-gsconnect/issues/ ?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
The problem is back. But not frequent enough yet to let me catch it
properly, I did get after running 'nautilius -q":
Traceback (most recent call last):
File
"/home/tom/.local/share/nautilus-python/extensions/nautilus-gsconnect.py", line
49, in
localedir=LOCALE_DIR)
File
Thanks for the update, let's close it then, you can reopen if you get it
again and can provide the debug version of the gdb backtrace
** Changed in: nautilus (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
To my surprise, the bug stopped happening few days ago so I cant
replicate. Search works again as intended.
It might have been an update but I am not even sure which one could have
fixed the issue;
So, until further notice, for me it seems solved...
--
You received this bug notification
Thanks, could you do the same with the dbgsym mentioned installed?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1852053
Title:
Nautilus Crashes when opening search field and
I did that:
- In Nautilus I press Ctrl-F and a character and then N freezes and gdb reports
segmetation fault. -(gdb) backtrace
[...]
(org.gnome.Nautilus:12326): Gtk-WARNING **: 11:34:57.526: Duplicate child name
in GtkStack: icons
(org.gnome.Nautilus:12326): Gtk-WARNING **: 11:34:57.579:
Can you open those steps
- ctrl-alt-T
$ nautilus -q
$ gdb nautilus
(gdb) r
(gdb) backtrace
Ideally with libglib2.0-0-dbgsym libgtk-3-0-dbgsym nautilus-dbgsym installed
(enabled of dbg source as explained on
https://wiki.ubuntu.com/Debug%20Symbol%20Packages)
--
You received this bug
Is it possible the crash report auto-uploaded ( cb12411a-045e-11ea-
afb5-fa163e983629 ) ?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1852053
Title:
Nautilus Crashes when
Randomly tried this :
apport-retrace --gdb _usr_bin_nautilus.1000.crash
But that gave me: "ERROR: report file does not contain one of the
required fields: Package"
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in
Sorry I spend about 30 minutes trying to understand how to open a crash
report program. I followed your link and Googled, but these
"explanations" are so unclear that I cant get any further. I use Ubuntu
since version 11 I think and it's remarkable how complex that crash
reporting remained...
In
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
14 matches
Mail list logo
