Done, https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1645701
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1626935
Title:
[yakkety] desktop is black and/or flickering after plugging in a
Alright, sounds like there's still work to do.
Alberts, please log a new bug describing the remaining issue so it's more
clearly still open :)
Just run: ubuntu-bug nautilus
Or if that fails then:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+filebug
--
You received this bug
Was this tested with HiDPI? On fully updated VM (zesty) with scaling-
factor set to 2 initially window size is correct, but after resizing VM,
nautilus desktop window is 1/4 from size it should have.
I think that I have same problem also on my main pc (also zesty) -
desktop window is only 1/4
@Christopher:
1) It's a physical machine (my laptop).
2) I'm using Ubuntu 16.10.
3) Graphics-wise, it's a standard installation except for the 4.9-rc3
kernel from mainline and a PPA for nvidia graphics drivers (but I wasn't
using the nvidia card at the time this happened, it was all on the
This also fixes a defect we are seeing in a VMWare guest with Ubuntu
16.10. The issue was wallpaper does not get resized when changing to a
higher desktop resolution, leaving a black border around the wallpaper,
and corruption occurs when when dragging a window over that black
border.
--
You
Rocko (rockorequin), you may be affected by another bug outside of the
scope of this report. Hence:
1) Are you referring to a physical, or virtual machine?
2) Are you using Ubuntu 16.10 or some other version?
3) Do you have any PPA/3rd party software installed or is it the default
configuration?
I also saw artefacts this morning all along the bottom 10% of the
desktop background on the laptop monitor (the launcher was rendered
without issues). I'm not sure what triggered it, but I had resumed the
laptop and plugged in a new monitor earlier in the morning. Killing
nautilus and restarting
This bug was fixed in the package nautilus - 1:3.20.3-1ubuntu3.1
---
nautilus (1:3.20.3-1ubuntu3.1) yakkety; urgency=medium
* debian/patches/ubuntu_revert_no_wallpaper.patch: Ensure that
widget_realized_cb is always called, as this sets up the signals that set
things up on
Although I saw some concerning artifacts when running zesty in a
VirtualBox VM the other day (and resizing the window). Those might have
been caused by this fix(?). Needs investigating.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Verified bug is fixed on yakkety using nautilus 3.20.3-1ubuntu3.1
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1626935
Title:
Perhaps someone would like to verify the SRU?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1626935
Title:
[yakkety] desktop is black and/or flickering after plugging in a
second monitor
To
This bug was fixed in the package nautilus - 1:3.20.3-1ubuntu4
---
nautilus (1:3.20.3-1ubuntu4) zesty; urgency=medium
* debian/patches/ubuntu_revert_no_wallpaper.patch: Ensure that
widget_realized_cb is always called, as this sets up the signals that set
things up on
Cool. That would also be the nautilus-in-Xmir wallpaper bug I
encountered recently when you resize the desktop window. I thought it
was Xmir's fault but it's probably this one.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
It looks like this bug is reproducible in VirtualBox by resizing the
guest window. After the nautilus update in yakkety-proposed, the bug is
fixed for that use case.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: nautilus (Ubuntu Yakkety)
Importance: Undecided => High
** No longer affects: mesa (Ubuntu Yakkety)
** No longer affects: mesa (Ubuntu)
** No longer affects: compiz (Ubuntu Yakkety)
** No longer affects: compiz (Ubuntu)
--
You received this bug notification because you are
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: compiz (Ubuntu Yakkety)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1626935
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: mesa (Ubuntu Yakkety)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1626935
Hello Yung, or anyone else affected,
Accepted nautilus into yakkety-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/nautilus/1:3.20.3-1ubuntu3.1 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Uploaded
** Changed in: nautilus (Ubuntu)
Status: Confirmed => In Progress
** Changed in: nautilus (Ubuntu)
Status: In Progress => Fix Committed
** Changed in: nautilus (Ubuntu Yakkety)
Status: New => In Progress
--
You received this bug notification because you are a
** Branch linked: lp:~ubuntu-desktop/nautilus/ubuntu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1626935
Title:
[yakkety] desktop is black and/or flickering after plugging in a
second monitor
** Description changed:
+ [ Description ]
+
+ Nautilus's wallpaper drawing doesn't respond to changes in monitor
+ configuration. Instead of your wallpaper you see black.
+
+ [ Fix ]
+
+ Inside nautilus, the wallpaper widget connects to GTK's "monitors-
+ changed" signal when it is
GTK or nautilus itself somehow changed the order that things are
realized in, which broke an assumption in nautilus that this would
happen after the widget was constructed.
** Also affects: nautilus (Ubuntu Yakkety)
Importance: Undecided
Status: New
** Also affects: mesa (Ubuntu
I'm fixing this by explicitly calling the signal handler once if the
widget is already realized when we connect the signal.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1626935
Title:
[yakkety]
Whatever the logic in nautilus listening for xrandr display layout
changes is, is what seems to be broken. It should be reconfiguring
itself when xrandr reports the displays have changed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Changed in: nautilus (Ubuntu)
Assignee: Sebastien Bacher (seb128) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1626935
Title:
[yakkety] desktop is black and/or flickering
Yep, that's one of two workarounds mentioned in comment #10.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1626935
Title:
[yakkety] desktop is black and/or flickering after plugging in a
second
I've the impression this is due to nautilus not being properly resized
when display size changes (in a VM) or a new one is added...
nautilus -q
and starting the filemanager again should fix this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
I thought it was plausible the underlying cause was the modesetting
driver but up in comment #4 Timo said that it happens without
modesetting and in intel too. So which is true?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Is this a modesetting driver issue? I believe I've seen this happen when
hotplugging an external monitor. It only happens for me with the modeset
driver, though, not the intel driver. The modesetting driver is
excellent for some things (eg it doesn't tear on the external monitor
like the intel
29 matches
Mail list logo
