Ok, the problem is recurring again, so I've gathered a backtrace with
that dbgsym package installed, hopefully it provides more insight as to
where things are getting blocked up.
** Attachment added: "gdb-nautilus-2020-10-19.txt"
[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.
ok well, this is exceptionally weird. I was seeing some issues with my
wine install where the internal state was all messed up and it was just
hanging starting apps and so I blew it away and rebuilt it, and now
I can't reproduce this nautilus issue.
Is there any connection between nautilus
To get debug packages you need to enable the corresponding apt source
https://wiki.ubuntu.com/Debug%20Symbol%20Packages
Could you install libglib2.0-0-dbgsym and try again? It seems it's
waiting in dbus for a service to reply...
--
You received this bug notification because you are a member of
there doesn't seem to be a nautilus-dbg package or similar which
includes the debug symbols, unfortunately. here's a stacktrace from
while it's waiting.
** Attachment added: "gdb-nautilus-2020-08-15.txt"
Thanks but the backtrace would be useful during the minute waiting to
know what it is waiting on... also having debug symbols would also be
useful
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1891712
gdb output from nautilus after startup has completed.
** Attachment added: "gdb-nautilus-2020-08-14.txt"
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1891712/+attachment/5401585/+files/gdb-nautilus-2020-08-14.txt
--
You received this bug notification because you are a member of
Alright, just tested this. ran date before starting nautilus, got "Fri
14 Aug 2020 05:02:02 PM PDT", ran it once the window appeared, got "Fri
14 Aug 2020 05:03:02 PM PDT", so pretty much a full minute to the
second. and here's what I see from journalctl during that period:
Aug 14 17:02:36 boxxy
Thank you for your bug report. Could you add your 'journalctl -b 0' log
after getting the issue and indicate the times where you started
nautilus and saw it displayed?
Could you use gdb while it's doing nothing to get a backtrace as
explained on https://wiki.ubuntu.com/Backtrace ?
** Changed in:
