Thanks. It looks like the nautilus process isn't frozen at all:
https://errors.ubuntu.com/bucket/?id=/usr/bin/nautilus%3A6%3A__GI___poll%3Ag_main_context_poll_unlocked%3Ag_main_context_iterate_unlocked%3Ag_main_context_iteration%3Ag_application_run
Which makes sense because a properly frozen
https://errors.ubuntu.com/user/b0e8093c7497f98ea1d6123f13650b77654510667f8c32cb9b7f39ed46e3c2533bcd265e527269b95a1cc6af2d15e3dc8625bb297ce66b2ecb65680ae6fb9b93
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
No there is no new file attached here. Also be careful not to attach
.crash files to bugs.
Please just tell us the new bug number, or your whoopsie-id.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
Can't you get it from the file attached?
On Thu, 21 Mar 2024, 17:17 Daniel van Vugt, <2058...@bugs.launchpad.net>
wrote:
> You will need to tell us the new bug number, or the user ID.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
>
You will need to tell us the new bug number, or the user ID.
--
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/2058327
Title:
Starting up Files app in external monitor freeze the
Done
--
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/2058327
Title:
Starting up Files app in external monitor freeze the entire monitor
Status in nautilus package in Ubuntu:
New
Let's analyse why the app is frozen... To do that you will need to kill
it while it's frozen:
killall -ABRT nautilus
and then a new crash file is created in /var/crash/. Please then use the
ubuntu-bug command to upload the crash file like:
ubuntu-bug /var/crash/_usr_bin_nautilus.1000.crash
It's on ONE app. I can start it in the primary window and move it to
external monitor.
One important thing to highlight though, sometimes the Files app starts
perfectly without this error, i.e, without this freezing the external
monitor thingy.
--
You received this bug notification because you
Usually because of the version of GTK or Cairo the app uses, based on
that previous bug. Or something else app-specific.
You might be able to select 'Ubuntu on Wayland' on the login screen as a
workaround, and use the same scaling factors as you do now. The only
catch is that may cause different
Not changing the scale. Why it doesn't happen to other apps but only
Files?
** Attachment added: "xrandr.txt"
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2058327/+attachment/5757786/+files/xrandr.txt
--
You received this bug notification because you are a member of Desktop
Before making any system changes, please also run:
xrandr --verbose > xrandr.txt
and attach the resulting text file here.
--
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/2058327
Thanks. This is starting to look familiar since the app window has:
Width: 7680
Height: 4320
and gnome-shell has:
Mar 20 12:51:12 khteh-p17-2i gnome-shell[4276]: Enabling experimental
feature 'x11-randr-fractional-scaling'
So I think you might be hitting a similar issue to bug 2004533
xwininfo: Window id: 0x3400032 "Home"
Root window id: 0x29f (the root window) (has no name)
Parent window id: 0x29f (the root window) (has no name)
1 child:
0x3400033 (has no name): () 1x1+-1+-1 +3839+-1
Absolute upper-left X: 3840
Absolute upper-left Y: 0
Relative
While it's frozen, please open a Terminal window and run:
xwininfo -all
and then click on the frozen Nautilus window. What output then gets
printed in the Terminal window?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in
No. That's what "frozen" mean.
On Wed, 20 Mar 2024, 17:41 Daniel van Vugt, <2058...@bugs.launchpad.net>
wrote:
> While it's frozen, are you able to use any other app on top of the
> frozen window?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
>
While it's frozen, are you able to use any other app on top of the
frozen window?
--
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/2058327
Title:
Starting up Files app in external
It's frozen screen and it doesn't happen to other apps.
--
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/2058327
Title:
Starting up Files app in external monitor freeze the entire
If there's only meant to be one maximized window then we can't tell the
difference between a frozen screen and a frozen window. Please check to
see if the same bug occurs with other apps (and try them maximized too).
--
You received this bug notification because you are a member of Desktop
Damned, the whole screen freezes. You can't click / do anything on the
external monitor!
--
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/2058327
Title:
Starting up Files app in
Without knowing the monitor layout (xrandr) I don't know what I'm seeing
in that screenshot. Are you saying that other apps also fail to render
on the external monitor after the bug has started? And do you mean
"maximized" instead of "minimized"?
--
You received this bug notification because you
Doesn't help. Now the minimized windows shows the picture of the last
application window.
** Attachment added: "Screenshot from 2024-03-20 14-39-39.png"
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2058327/+attachment/5757412/+files/Screenshot%20from%202024-03-20%2014-39-39.png
--
Those steps are to help us find the cause of the issue.
** Package changed: gnome-shell (Ubuntu) => nautilus (Ubuntu)
--
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/2058327
Title:
Why do I need to run the steps? What are they for?
I can't click and do anything on the external monitor which freezes.
Only the primary monitor is available when this happens. I don't have
any network mounts.
--
You received this bug notification because you are a member of Desktop
Packages,
Please try:
* Uninstalling: nautilus-image-converter
* Running: gsettings set org.gnome.nautilus.window-state maximized false
Also when you say "freeze the entire external monitor" does that mean
launching a second different app fails to render on that monitor? Or
does it just mean Nautilus
Please also check if you have any network mounts that they're all
responding (https://gitlab.gnome.org/GNOME/nautilus/-/issues/1354)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
journalctl -b0 > journal.txt
** Attachment added: "journal.txt"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2058327/+attachment/5757402/+files/journal.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in
If you're using X11 with multiple monitors though, the problem can't be
fullscreen direct scanout. It's more likely a bug in the app.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
This might be fullscreen direct scanout, which happens when a window is
maximized on a monitor that has no panel or dock. Please try
unmaximizing the window and just dragging it to the second monitor as a
regular window. This should also help to work around the problem:
gsettings set
There is no real error in that log it seems but if you can't use the
screen nor put other applications there then it's probably a gnome-shell
issue, reassigning
** Package changed: nautilus (Ubuntu) => gnome-shell (Ubuntu)
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => New
--
Mar 19 21:29:10 khteh-p17-2i gnome-shell[3681]: Window manager warning: Buggy
client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3600018
Mar 19 21:29:11 khteh-p17-2i systemd[2265]: Started
app-gnome-org.gnome.DejaDup.Monitor-12179.scope - Application launched by
could you do
$ journalctl -f
trigger the issue then copy the log which was recorded by the previous
command?
--
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/2058327
Title:
Starting
External monitor freezes
On Tue, 19 Mar 2024, 17:05 Sebastien Bacher, <2058...@bugs.launchpad.net>
wrote:
> Could you provide details on what you mean by 'freezes the monitor'? Can
> you move another application there for example?
>
> --
> You received this bug notification because you are
Could you provide details on what you mean by 'freezes the monitor'? Can
you move another application there for example?
--
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/2058327
Title:
apport information
** Tags added: apport-collected mantic
** Description changed:
- Starting up Files app in external monitor freeze the entire external
- monitor. I have to close the Files app in the primary monitor to get
- back to normalcy.
+ Starting up Files app in external monitor freeze
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command only once, as it
will automatically gather debugging information, in a terminal:
apport-collect 2058327
When reporting bugs in the future please use apport by using 'ubuntu-
35 matches
Mail list logo
