Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: nautilus (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/18
I had the same issue today, and I remember the last thing I done yesterday
before failing was installing the MegaSync extension. I have just removed that
package and restarted and Nautilus is working again.
I hope this would be useful.
--
You received this bug notification because you are a mem
Alright, to confirm, installing the org.gnome.NautilusDevel and running
it has given me a working system again. In case somebody is looking for
a way to get a working system until 20.04 lands.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed
I too have this issue. I just upgraded from 18.04 LTS to 19.10 and
Nautilus starts fine, finishes the check, but I cannot initiate any file
commands like copy, move or delete. Nautilus doesn't respond and GNOME
serves the pop-up to kill Nautilus. Pressing the 'waiting' option
repeatedly doesn't sol
You will find attached the journalctl log for the corrupted session.
It has been anonymized.
** Attachment added: "anonymized journalctl log"
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1850001/+attachment/5300891/+files/jrnl_log_anonymized
** Changed in: nautilus (Ubuntu)
is there any nautilus or gvfs errors/warnings in the log? could you post
those (replacing private name/path if needed)?
** Changed in: nautilus (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nau
>So the hang issue went away
Yes, the reboot wiped everything clean.
>Can you still add the journalctl log from the session where you had the issue
There is a lot of private information in the log, computer name, file names,
paths, that should not be publicly posted.
There are also a lot of erro
So the hang issue went away? Can you still add the journalctl log from
the session where you had the issue?.
the power button not working on the login screen is bug #1847896
** Changed in: nautilus (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a
>Do you mean it hangs on a specific file
No, any file.
>give details on the file/location
~/Downloads
I had to end the nautilus process in System Monitor.
The power down button in the upper right corner of the desktop did not
work. No response at all.
I had to issue the reboot command from ter
Thank you for your bug report. Do you mean it hangs on a specific file an only
this one?
Could you
- give details on the file/location? is it a local directory or a remote mount?
- add your 'journalctl -b 0' log after getting the issue?
- try to use gdb to get a backtrace of nautilus while it's ha
10 matches
Mail list logo
