[Bug 1849544] [NEW] package initramfs-tools 0.133ubuntu10 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1
Public bug reported: problem occurred becauuse symlink /initrd.imgpointed to old disco initrd, resolved by forcibly recreating it, for now...? ProblemType: Package DistroRelease: Ubuntu 19.10 Package: initramfs-tools 0.133ubuntu10 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 Date: Mon Oct 21 17:24:50 2019 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2018-02-20 (610 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) PackageArchitecture: all Python3Details: /usr/bin/python3.7, Python 3.7.5rc1, python3-minimal, 3.7.5-1 PythonDetails: /usr/bin/python2.7, Python 2.7.17rc1, python-minimal, 2.7.17-1 RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.4 SourcePackage: initramfs-tools Title: package initramfs-tools 0.133ubuntu10 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to eoan on 2019-10-21 (2 days ago) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package eoan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849544 Title: package initramfs-tools 0.133ubuntu10 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1849544/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1841915] Re: black screen, unresponsive, after logout from gnome Wayland session
as of this morning's updates, this problem seems to have disappeared. I've been able to log out and back in several times to my ubuntu wayland session, at least on my i915 machine (the dell laptop). nb: this morning's updates updated gnome-session-bin and ubuntu-session to 3.33.92-1ubuntu1, gdm3 to 3.33.92-2ubuntu1, but mutter and gnome- shell remain at 3.33.91.. (Also and probably not coincidentally seeing some unrelated dash-or-ubuntudock issues, but i'll wait to see if they're resolved when gnome-shell goes up to 3.33.92 too.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1841915 Title: black screen, unresponsive, after logout from gnome Wayland session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1841915/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1841915] Re: black screen, unresponsive, after logout from gnome Wayland session
My point regarding gnome-session-wayland.target is that if we're seeing different filenames for that file (assuming they're functionally the same) and mine definitely comes from gnome-session-bin, does that suggest we're running different gnome-session-bin versions? And seeing as you're not reproducing an issue i'm seeing regarding the ending of a gnome session... does that difference in what file you're expecting me to have there and the file i *assure* you is actually there... signify anything? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1841915 Title: black screen, unresponsive, after logout from gnome Wayland session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1841915/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1841915] Re: black screen, unresponsive, after logout from gnome Wayland session
minor contextual note: It took me a little while to get the other machine, ssh in (offending ssh key to resolve), call up this page to remind me of the exact commands. The point of which is to say, these weren't taken *immediately* after the logout, but at least a minute later, certainly beyond that timeout discussed earlier. Also therefore that that ssh session started *after* the hang event, didn't log in in advance. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1841915 Title: black screen, unresponsive, after logout from gnome Wayland session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1841915/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1841915] Re: black screen, unresponsive, after logout from gnome Wayland session
journalctl -b output as attached loginctl as below: rachel in ~ at rainbow ➜ loginctl SESSION UID USER SEAT TTY 1 1000 rachel seat0 tty2 3 1000 rachel pts/0 2 sessions listed. rachel in ~ at rainbow ➜ loginctl show-session 1 Id=1 User=1000 Name=rachel Timestamp=Tue 2019-09-03 14:30:40 BST TimestampMonotonic=20750725 VTNr=2 Seat=seat0 TTY=tty2 Remote=no Service=gdm-autologin Scope=session-1.scope Leader=5228 Audit=1 Type=wayland Class=user Active=yes State=closing IdleHint=no IdleSinceHint=0 IdleSinceHintMonotonic=0 LockedHint=no rachel in ~ at rainbow ➜ loginctl show-session 3 Id=3 User=1000 Name=rachel Timestamp=Tue 2019-09-03 14:31:47 BST TimestampMonotonic=87793987 VTNr=0 TTY=pts/0 Remote=yes RemoteHost=192.168.1.109 Service=sshd Scope=session-3.scope Leader=7048 Audit=3 Type=tty Class=user Active=yes State=active IdleHint=no IdleSinceHint=1567517624629274 IdleSinceHintMonotonic=205041051 LockedHint=no ** Attachment added: "jctl.log" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1841915/+attachment/5286446/+files/jctl.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1841915 Title: black screen, unresponsive, after logout from gnome Wayland session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1841915/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1841915] Re: black screen, unresponsive, after logout from gnome Wayland session
It is definitely /usr/lib/systemd/user-gnome-session-wayland.target. dpkg -S on that file gives gnome-session-bin which is on version 3.33.90-2ubuntu2. dpkg -S on the .service file gives no match. This problem didn't start on upgrade to the 5.2 kernels, which happened a few weeks(?) earlier, but immediately when gnome 3.33 dropped. will get the gdm debugging stuff... (had to spend some time in windows doing that for which i'm paid ;-) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1841915 Title: black screen, unresponsive, after logout from gnome Wayland session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1841915/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1841915] Re: black screen, unresponsive, after logout from gnome Wayland session
With --systemd removed as directed I still ended up stuck on a black screen, except this time it had a flashing white text cursor in the top left. (BTW reboots occurred between each test, somewhat perforce...) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1841915 Title: black screen, unresponsive, after logout from gnome Wayland session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1841915/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1841915] Re: black screen, unresponsive, after logout from gnome Wayland session
I tried (just now) deliberately leaving it longer than 30 seconds to come back after a logout. In fact left it longer than 60 seconds. Nothing happening. I wasn't logged in via ssh as well at the time (I hadn't thought the systemd --user instance was related to the ssh session before so presumably might be confusing matters) so there's nothing more to report than that the screen remained resolutely black. There is no /usr/lib/systemd/user/gnome-session-wayland.service file on this system. There is a .target file though which is presumably the one. As the presumably-default timeout didn't seem to be honoured here there didn't seem a lot of point in adding a shorter one so I left the file alone. I'll try the change to /usr/share/wayland-sessions/ubuntu- wayland.desktop (the only file in that directory) and report back in the next comment... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1841915 Title: black screen, unresponsive, after logout from gnome Wayland session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1841915/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1841915] Re: black screen, unresponsive, after logout from gnome
the i915 one (Dell XPS 13 9370) is the one with automatic login enabled. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1841915 Title: black screen, unresponsive, after logout from gnome Wayland session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1841915/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1841915] Re: black screen, unresponsive, after logout from gnome
As attached. ** Attachment added: "lspcik.txt" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1841915/+attachment/5286165/+files/lspcik.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1841915 Title: black screen, unresponsive, after logout from gnome To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1841915/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1841915] Re: black screen, unresponsive, after logout from gnome
... and the other affected machine (just checked it's still affected today after latest updates) ** Attachment added: "lspcik-dell.txt" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1841915/+attachment/5286167/+files/lspcik-dell.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1841915 Title: black screen, unresponsive, after logout from gnome To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1841915/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1841915] Re: black screen, unresponsive, after logout from gnome
Only affects Wayland sessions, not x11. I should have mentioned it earlier, it's been my default for some time now (because #1827428 which still affects latest 19.10) and I forgot. It also seems not to be the upstream bug, unless the discussion there is going off in the wrong directions. They now point the finger at systemd in a bug tracked here: https://github.com/systemd/systemd/issues/13437 . But I can't reproduce that vt-switching issue. (And our systemd is older than any they're looking at.) I only have a problem at logout. ** Bug watch added: github.com/systemd/systemd/issues #13437 https://github.com/systemd/systemd/issues/13437 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1841915 Title: black screen, unresponsive, after logout from gnome To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1841915/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1841915] Re: black screen, unresponsive, after logout from gnome
there are no crash files relating to when this happens. Currently sitting at the machine that *doesn't* have autologin enabled, where it's just happened again, there is nothing in /var/crash relating to this. (nextcloud client keeps crashing, and there are crash files relating to that, the most recent one yesterday). the error tracker shows just the same two nextcloud crashes, most recently yesterday. there is no crash. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1841915 Title: black screen, unresponsive, after logout from gnome To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1841915/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1841915] Re: black screen, unresponsive, after logout from gnome
additionally as it does seem to involve console switching and you might think kernel to be relevant to that, i tried again after the most recent kernel upgrade in 19.10 (5.2.20-15-generic). no change. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1841915 Title: black screen, unresponsive, after logout from gnome To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1841915/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1841915] Re: black screen, unresponsive, after logout from gnome
Network connection does not die. (It appeared to first time but I think that's just my ongoing random - and irrelevant here - avahi issues on this machine.) But gnome-shell is *not* running after triggering the bug, so sudo killall on it just produces "gnome-shell: no process found". So that was the end of following the instructions above. :-) (Also this time round it did fail on the *first* logout too, so the fact of it not having done so the first couple of times may just have been a fluke. There are no other processes with gnome in the name running, nor is mutter. gdm3 and "gdm-session-worker [pam/gdm-autologin]" are apparently up. Using systemctl restart gdm3 seemed to work (I see a login screen) but doesn't really (it didn't autologin as expected per config, and attempting to log in just returns me to the login screen). I stopped gmd3 entirely (systemctl stop gdm3, then noticed "gdm-session- worker [pam/gdm-autologin]" was still running, though may have been a new instance as of the gmd3 restart (based on time started), so killed that manually), but then noticed there's a gnome-shell and other processes owned by me now running, but which I didn't get any sight of visually on the system's screen. After a while (while I was typing the above paragraph) they died on their own, and after *that*, a systemctl start gdm3 seems to have worked. As autologin is enabled, i got back into a new desktop session. This may point to it being related to console switching as suggested in the comments of the upstream bug. Stuff *is* happening (eg: gnome-shell *did* quit on logout, and it looks like I *did* login after the first gdm3 restart), but the console doesn't switch properly, so it appears dead. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1841915 Title: black screen, unresponsive, after logout from gnome To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1841915/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1841915] [NEW] black screen, unresponsive, after logout from gnome
Public bug reported: on logout the screen is black, the system is unresponsive and has to be restarted. (Untested by me yet, but I expect ssh-ing in and restarting gdm would work.) I believe this may be already reported upstream here: https://bugzilla.redhat.com/show_bug.cgi?id=1745554 That's why I've reported this against gdm3 even though I honestly don't know if it might be a gnome-shell, gnome-session or mutter based error. (FWIW without the upstream bug to link to I'd maybe suspect gnome-shell first.) NB: This machine's conf has AutomaticLogin enabled, but another machine also on 19.10 does not, and it's showing the same thing. On *this* machine I found that the *first* time I logged out, it was OK, but not the second time. On the other machine, it fails first time too. It's as if the gdm login screen can appear exactly once. That (and being on gnome 3.33) is why I don't think this is a dupe of #1824588. Nothing appears in /var/crash as a result of this. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gdm3 3.33.90-1ubuntu1 ProcVersionSignature: Ubuntu 5.2.0-13.14-generic 5.2.8 Uname: Linux 5.2.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Aug 29 10:51:22 2019 InstallationDate: Installed on 2018-09-11 (351 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) SourcePackage: gdm3 UpgradeStatus: Upgraded to eoan on 2019-07-16 (43 days ago) mtime.conffile..etc.gdm3.custom.conf: 2019-07-17T00:07:04.528641 ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1841915 Title: black screen, unresponsive, after logout from gnome To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1841915/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827428] Re: Mouse cursor left frozen copy of itself
A bit more detail to reproduce this that I think was missed out before: It happens when the configured desktop mode/scaling is set to a fractional value. You can have that experimental xrandr setting set, but be configured to scaling of 100% or 200% (but see below on latter) and you won't see this problem. Set it to 150%, log out, log in again, you should see it. That applies to my experience anyway on the AMD graphics system. NB: Today when I tried to confirm this, I found that it would ignore my setting scaling to 200% on login, and would instead go in as if it was 100%, which would also be what it showed in the display settings dialogue itself. I'm pretty sure that wasn't the case earlier. I am able to select and use 200% in the session, it just won't be remembered. This sounds like a separate problem though. The problem *here* is what happens when scaling is set to a fractional value like 150% (which it does seem to have no problem remembering). It also means that a kind of workaround is to set scaling to 200% or 100% before logging out, then set it back to the 150% you want after logging in again. The problem is only when you're logging in and the setting is already fractional, so the switch in resolution happens during login. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1827428 Title: Mouse cursor left frozen copy of itself To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1827428/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827428] Re: [nvidia] Mouse cursor left frozen copy of itself
My bug got marked a duplicate of this one but with the latest change that might be wrong: It affected me on a machine with AMD graphics, not nVidia. BTW I recently tried it again on the offchance it had been fixed since (by re-enabling the xrandr scaling setting), and it had not. Also not fixed on 19.10 (which tbh is barely advanced from 19.04 at this stage). On the flipside, a different machine with only Intel graphics (Dell XPS 9370) did *not* show this problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1827428 Title: [nvidia] Mouse cursor left frozen copy of itself To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1827428/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1770915] Re: command not found: -antigen-env-setup
Hello? Still affecting Disco. ** Tags added: disco -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1770915 Title: command not found: -antigen-env-setup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zsh-antigen/+bug/1770915/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1831070] Re: package nvidia-dkms-390 390.116-0ubuntu1 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 1
NB: Post-upgrade upgraded to nvidia-driver-418 from restricted (didn't re-enable graphics-drivers ppa) and all so far seems well. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1831070 Title: package nvidia-dkms-390 390.116-0ubuntu1 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1831070/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1831070] [NEW] package nvidia-dkms-390 390.116-0ubuntu1 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 1
Public bug reported: Just happened trying to upgrade a machine in two immediate steps bionic->cosmic->disco. ProblemType: Package DistroRelease: Ubuntu 19.04 Package: nvidia-dkms-390 390.116-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-20.21-generic 4.18.20 Uname: Linux 4.18.0-20-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 Date: Thu May 30 12:58:24 2019 ErrorMessage: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2018-02-20 (463 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) Python3Details: /usr/bin/python3.7, Python 3.7.3, python3-minimal, 3.7.3-1 PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.16-1 RelatedPackageVersions: dpkg 1.19.6ubuntu1 apt 1.8.1 SourcePackage: nvidia-graphics-drivers-390 Title: package nvidia-dkms-390 390.116-0ubuntu1 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to disco on 2019-05-30 (0 days ago) ** Affects: nvidia-graphics-drivers-390 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package disco -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1831070 Title: package nvidia-dkms-390 390.116-0ubuntu1 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1831070/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827099] Re: package shared-mime-info 1.10-1 failed to install/upgrade: triggers looping, abandoned
ditto upgrading in two steps bionic->cosmic->disco -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1827099 Title: package shared-mime-info 1.10-1 failed to install/upgrade: triggers looping, abandoned To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shared-mime-info/+bug/1827099/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829221] Re: second, dead, mouse pointer left on screen after login, x11 session
It does appear to be related to the xrandr scaling experimental feature, after all. Revert that to default and the issue disappears. Guessing that probably makes it a mutter bug, and being of an experimental feature at that is hopefully of interest to someone but not urgent. In view of that didn't test switching pointing device. ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829221 Title: second, dead, mouse pointer left on screen after login, x11 session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1829221/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829221] [NEW] second, dead, mouse pointer left on screen after login, x11 session
Public bug reported: This seems to have become repeatable, and applies even on the first login session immediately after booting the computer. I don't know if this is the right package to report against; another possible culprit: gdm: When I log into the default "Ubuntu" session (ie: on xorg), gdm's mouse pointer remains on screen during the screen blank, and after the gnome desktop comes up. It stays on the top just like you'd expect of the mouse pointer, but it's immobile and unresponsive. It's left at the same position on the screen that it was while using gdm, and is the same size as it was in gdm (ie: gdm is not scaled, but gnome session desktop scaled to 150% - the *working* in-session mouse pointer is also 150% larger than gdm's dead one). It looks like gdm and gnome are running in the same x11 session? Seeing as the mouse pointer stays solid *during* the transition from gdm into the gnome desktop. Not even a flicker. It's almost as if we're trying to have smooth transitions for these sorts of things, which is good of course, but maybe is a bug in that? It disappears when I log into a Wayland session, it appears only to affect x11 sessions. I've taken to just moving the mouse pointer to the far bottom right corner of the screen before logging in, so at least it's not very intrusive. There are a few reports of similar in askubuntu from a few years back, but with no helpful or applicable solution. eg: https://askubuntu.com/questions/521241/i-have-two-cursors-on-my-screen-one-of-which-is-always-on-top-and-will-never-mo https://askubuntu.com/questions/598096/14-04-second-mouse-pointer-stuck-in-middle-of-the-screen To answer the points made there, the xinput --list output is shown below. Executing that command and rebooting makes no difference. In the Displays Prefs there is no second "Unknown" display to disable. (The machine has precisely one display, and that's all Settings sees. It's a desktop, not a laptop, and it only has an AMD Vega integrated graphics. It also has only one mouse.) rachel@twilight:~$ xinput --list ⎡ Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)] ⎜ ↳ HID 04b4:3003 Mouse id=9[slave pointer (2)] ⎜ ↳ HID 04b4:3003 Consumer Controlid=11 [slave pointer (2)] ⎜ ↳ Microsoft Microsoft® Nano Transceiver v1.0 Mouse id=15 [slave pointer (2)] ⎜ ↳ Microsoft Microsoft® Nano Transceiver v1.0 Consumer Control id=16 [slave pointer (2)] ⎜ ↳ Microsoft Microsoft® Nano Transceiver v1.0 Consumer Control id=17 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Button id=6[slave keyboard (3)] ↳ Power Button id=7[slave keyboard (3)] ↳ HID 04b4:3003 id=8[slave keyboard (3)] ↳ HID 04b4:3003 System Control id=10 [slave keyboard (3)] ↳ HID 04b4:3003 Keyboardid=12 [slave keyboard (3)] ↳ Dell Dell AC511 USB SoundBar id=13 [slave keyboard (3)] ↳ Microsoft Microsoft® Nano Transceiver v1.0id=14 [slave keyboard (3)] ↳ Microsoft Microsoft® Nano Transceiver v1.0 System Control id=18 [slave keyboard (3)] ↳ Eee PC WMI hotkeysid=19 [slave keyboard (3)] ↳ HID 04b4:3003 Consumer Controlid=20 [slave keyboard (3)] ↳ Microsoft Microsoft® Nano Transceiver v1.0 Consumer Control id=21 [slave keyboard (3)] ↳ Microsoft Microsoft® Nano Transceiver v1.0 Consumer Control id=22 [slave keyboard (3)] (I don't know what's with the duplicated MS Nano Transceiver Consumer Control entries) I thought of a couple of things to try after starting to write this ticket but didn't want to lose the ticket in progress, so will add comments if they show up anything. In particular, I am running the experimental feature to enable xrandr fractional scaling. This issue didn't show up right after enabling that, only a couple of days later, so it didn't seem immediately relevant. Also, trying with a different pointing device attached in case that transceiver is doing something odd. (never had problems before, had it years, no idea if that doubling-up has always been there.) ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: ubuntu-session 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 Uname: Linux 5.0.0-15-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed May 15 11:38:19 2019 InstallationDate: Installed on 2019-05-11 (3 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all SourcePackage: gnome-session UpgradeStatus:
[Bug 1828432] [NEW] update-notifier crashes on login
Public bug reported: This looks like a truly ancient bug: #12072. And a slightly less ancient one #38535. But here it is in 19.04. Every time I log into gnome, I see a "System problem detected" dialog. I click on the button to report the problem, and the dialog disappears. While the dialog is up, the update-notifier icon is in the dock to the left. It disappears with the system problem dialog. I'm guessing it's that that breaks, but there's no other visible indication of what it is that's crashing. It's really annoying. :-) Annoying enough I'm considering just removing update-notifier, but it wants to remove ubuntu-desktop-minimal ubuntu-release-upgrader-gtk update-manager as well, which maybe doesn't seem like a great idea. But maybe it's the only way... ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: update-notifier 3.192.18 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu May 9 16:07:43 2019 InstallationDate: Installed on 2018-09-11 (240 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) SourcePackage: update-notifier UpgradeStatus: Upgraded to disco on 2019-01-13 (115 days ago) ** Affects: update-notifier (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1828432 Title: update-notifier crashes on login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/1828432/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1817924] Re: apps launched from gnome shell do not get input focus
i didn't freshly install to see it but i did create a new user, to be sure I had utterly default settings and yes, it's there right from the get-go with certain apps including terminal. but only in x11 (which of course *is* still the default in ubuntu). I switched to wayland and this problem went away. The remaining issues in wayland have proved insufficient to push me back to x11, so I've been able to stop caring about this. :-) I guess people just aren't testing for x11 thoroughly any more. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1817924 Title: apps launched from gnome shell do not get input focus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1817924/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1818517] Re: "Network Login" browser does not remember cookies
trying to get that screenshot was how i discovered it *does* appear to be retaining stuff for a while at least. :-) I'll try to do so next time I'm there. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1818517 Title: "Network Login" browser does not remember cookies To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1818517/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1818517] Re: "Network Login" browser does not remember cookies
actually i think cookies are being held for at least a while, as, sitting in the cafe, I can log out and in, and even reboot, and get logged directly back into the hotspot. But when I come back the next day I'm asked if I even want to accept cookies. It's that being asked to accept cookies every day [that I go there] that annoys me, not whether or not it actually logs me in or i have to click on a button to connect. But in Windows, for instance, it remembered me even though I hadn't booted up windows at the cafe for *months*. so i'm guessing there is cookie retention going on, but on a rather short timeout. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1818517 Title: "Network Login" browser does not remember cookies To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1818517/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1818517] Re: "Network Login" browser does not remember cookies
i mean literally http web cookies from the portal page. if you ignore the network login app (as was the case before it worked reliably), it shows up in your normal browser. This does remember cookies, so you don't get asked if you want to accept cookies every time you go there. What the portal does when it's presented with the cookie it gave you on your last visit is, i think, a matter for the portal. My guess is that it's probably *it* that would auto-connect you under whatever circumstances it sees fit. Otherwise you just get the normal "Click to connect" button. I think *all* this needs is the support for, and storage of, HTTP cookies from the portal, in whatever's providing the browser window component of the Network Login app. My talk of auto-login stuff was just confusing the matter, ignore it. :-) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1818517 Title: "Network Login" browser does not remember cookies To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1818517/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1818517] [NEW] "Network Login" browser does not remember cookies
Public bug reported: This is with respect to the gnome-shell-portal-helper, part of the gnome-shell package, which opens its own browser window to prompt for a wifi hotspot login. It all works fine except one little papercut: Could it remember cookies? So when I go back to the same hotspot most days I don't have to click OK to accept cookies every time before I can actually click to go online. It's possible I suppose they don't all use cookies. The hotspot in question is a BT wifi hotspot, so probably quite common in GB anyway. Desired behaviour, hate to say, is like Windows: It actually remembered my choice from before and just logged me in right away. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.31.90-1ubuntu1 ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20 Uname: Linux 4.19.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Mar 4 14:05:46 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-09-11 (173 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) SourcePackage: gnome-shell UpgradeStatus: Upgraded to disco on 2019-01-13 (49 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco package-from-proposed wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1818517 Title: "Network Login" browser does not remember cookies To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1818517/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1817924] Re: apps launched from gnome shell do not get input focus
Bug only affects X11 sessions. I had a random urge to try out Wayland again. This issue does not arise in Wayland. Apps that were affected under X11 are taking input focus quite happily when launched from shell in Wayland. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1817924 Title: apps launched from gnome shell do not get input focus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1817924/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1817924] Re: apps launched from gnome shell do not get input focus
it's not generally slow enough for the latter to be an issue. :-) Even if I just go nice and slow. Click... window opens... it doesn't have focus... It continues to not have focus until I do something that would give it focus in the normal fashion, like clicking on it, clicking on its dock icon now it's running, alt-tabbing to it... Is this not happening for you in launching gnome-terminal? It's same for me whether from dock, from app grid, from app grid's search field. *Sometimes* it's been slow enough that I think I've seen the window have focus for a tiny moment (the close-window icon in the titlebar is orange for a moment) then it gets taken away. Usually it's too fast to see that happen. BTW I've also tried it with *all* extensions removed, including ubuntu-dock and appindicators and desktop-icons, by removing their packages. No difference. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1817924 Title: apps launched from gnome shell do not get input focus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1817924/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1817924] Re: apps launched from gnome shell do not get input focus
confirmed, gedit seems to be immune for some reason. pretty much anything else i tried is not; calculator, terminal, libreoffice, nautilus... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1817924 Title: apps launched from gnome shell do not get input focus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1817924/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1817924] Re: apps launched from gnome shell do not get input focus
sublime text, slack also immune, firefox, thunderbird are not... so ok it's not universal but *lots* of apps are affected, and the pattern doesn't seem to be gnome/not-gnome. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1817924 Title: apps launched from gnome shell do not get input focus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1817924/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1817924] Re: apps launched from gnome shell do not get input focus
FYI problem remains with all those extensions removed. BTW one does tend to notice it most with apps you type into. I first noticed with terminal, where I'm used to click, then start typing, and it's suddenly become click, click-again, then start typing. With an app you'd tend first to click into anyway, you're more likely to not notice it as the first click in an unfocused window is passed in. (Along the way, minor invisible-to-user bug in that the setting org.gnome.shell.enabled-extensions retains entries for extensions that have been removed. Noticed first because I already didn't have dash-to- dock installed, but did until recently - when without -proposed enabled, the ubuntu dock extension stopped working (works again with -proposed enabled, i think the latest non-proposed version of ubuntu-dock secretly depends on the proposed gnome shell). Confirmed as all those listed extensions remained in that setting after removing all of them. I've just reset it to default value, empty array.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1817924 Title: apps launched from gnome shell do not get input focus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1817924/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1817924] Re: apps launched from gnome shell do not get input focus
NB: If you launch an app from a terminal, eg: gnome-calculator, it *does* then get the input focus; just not when launched from gnome- shell. That's why I didn't think it was a mutter bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1817924 Title: apps launched from gnome shell do not get input focus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1817924/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1817924] [NEW] apps launched from gnome shell do not get input focus
Public bug reported: Observed on upgrading to disco-proposed today... When launching an app from the dock or from the applications grid (so i believe it's a gnome-shell thing rather than a dock thing), the app opens, but does not get the input focus. You have to either click in the window, or clicking again on the icon of the running app in the dock works, to give it focus. An extra step my muscle memory isn't prepared for! It seems like the sort of thing that might be an option rather than a bug, but if so, changing this behaviour back to its previous default is not at all obvious (I haven't found a way). So guessing it is a bug. NB: After launching an app this way, *no* window has focus. It is lost by the app that had it before, but not given to the newly started app. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.31.90-1ubuntu1 ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20 Uname: Linux 4.19.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Feb 27 15:53:07 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-09-11 (169 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) SourcePackage: gnome-shell UpgradeStatus: Upgraded to disco on 2019-01-13 (44 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco package-from-proposed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1817924 Title: apps launched from gnome shell do not get input focus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1817924/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814262] Re: Wired interface gets impossibly high metric 20100
Follow up comment on the upstream bug pointed to a commit where it suggests the rp_filter default should actually now be 2 rather than 1: https://github.com/systemd/systemd/commit/230450d4e4f1f5fc9fa4295ed9185eea5b6ea16e Think at this point I need to just let you guys talk amongst yourself. :-) For me, my fix for now is to uninstall the connectivity-check package, which disables the functionality. I'm not going to mess about changing procps defaults. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814262 Title: Wired interface gets impossibly high metric 20100 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1814262/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814262] Re: Wired interface gets impossibly high metric 20100
Reporting back on this:
The opinion there seems to be that the problem is down to the sys
net.ipv4.conf.*.rp_filter values being set to 1 instead of defaulting to
0. This is done in the procps package, and I'm guessing is the way it is
as a protection against IP spoofing. kernel doc page I was pointed to
says:
Current recommended practice in RFC3704 is to enable strict mode
to prevent IP spoofing from DDos attacks. If using asymmetric routing
or other complicated routing, then loose mode is recommended.
The max value from conf/{all,interface}/rp_filter is used
when doing source validation on the {interface}.
Default value is 0. Note that some distributions enable it
in startup scripts.
Presumably Ubuntu enables by default (I can see it does, in a file in
the procps package) and Red Hat, where it seems the NetworkManager
maintainers sit, does not.
This is going to have to be argued out between procps and network-
manager maintainers I guess. You can have IP spoofing protection or you
can have connectivity checking. Choose one, or argue who should fix it.
:-) Personally, at least for now, my solution is to remove the
connectivity-check package, which was presumably brought in by
something, and keep the procps defaults.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1814262
Title:
Wired interface gets impossibly high metric 20100
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1814262/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1815036] [NEW] uri defined for connectivity check does not have IPv6 address
Public bug reported: As per subject. This package defines the file /usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf, which defines the uri for the connectivity check to be http://connectivity- check.ubuntu.com This hostname does not resolve to an IPv6 address. Therefore, even if the user has fully working IPv6, the connectivity check for IPv6 will fail. As a result, the IPv6 default routes will be heavily deprioritised (ie: having 2 added to the metric) rendering them effectively inoperable absent a deliberate effort to use IPv6-only addresses. NB: This was discovered by-the-by during reporting of bug #1814262 upstream at https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/116#note_114448 It seems to be irrelevant to the main thrust of that bug, which is that IPv4 wired routes are not being identified as working correctly. In fact, when I switch to network-manager-config-connectivity-debian, the hostname defined there *does* have a working IPv6 address, and the issue actually being reported in that other bug does not affect the IPv6 routes, only the IPv4 ones. The bug here probably doesn't need any change made to the package itself, but rather to the networking of the actual target URL. It needs an IPv6 () DNS record, and for it to function on that address. I note in passing the debian connectivity check URL resolves to several IP addresses - four IPv4 addresses and 3 IPv6 addresses, presumably geographically diverse. (It's actually a CNAME to static.debian.org) This looks like it would be a more reliable target for connectivity checks. The ubuntu URL only resolves to a single IPv4 address. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: network-manager-config-connectivity-ubuntu 1.15.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.19.0-12.13-generic 4.19.18 Uname: Linux 4.19.0-12-generic x86_64 ApportVersion: 2.20.10-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Feb 7 12:35:24 2019 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-09-11 (148 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) IpRoute: default via 192.168.1.254 dev enp63s0 proto dhcp metric 100 default via 192.168.1.254 dev wlp2s0 proto dhcp metric 20600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.1.0/24 dev enp63s0 proto kernel scope link src 192.168.1.106 metric 100 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.101 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true PackageArchitecture: all SourcePackage: network-manager UpgradeStatus: Upgraded to disco on 2019-01-13 (24 days ago) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.15.2 connected started full enabled enabled enabled enabled enabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1815036 Title: uri defined for connectivity check does not have IPv6 address To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1815036/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814262] Re: Wired interface gets impossibly high metric 20100
As it recurred again today and showed no signs of correcting itself like it did on Friday, I went ahead and reported it upstream, here: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/116 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814262 Title: Wired interface gets impossibly high metric 20100 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1814262/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1814262] Re: Wired interface gets impossibly high metric 20100
Noted. I see there's no report of anything similar already, and if it was the sort of problem it looked like to me, people would be screaming blue murder about it, so I think I'll wait and see if it recurs or becomes an ongoing problem, rather than a one-off. Maybe my LAN was having a bad hair day... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814262 Title: Wired interface gets impossibly high metric 20100 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1814262/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814262] [NEW] Wired interface gets impossibly high metric 20100
Public bug reported: Actually this might be a heisenbug. I've had an issue with this all morning since network-manager got an update this morning, but just now *while this bug was being submitted* it decided to correct itself. What I was getting was, on a machine (Dell XPS 13 9370) with WiFi and a (Caldigit) Thunderbolt 3 dock with an ethernet port: After the network- manager update I noticed everything was slower than I was used to, and in gnome-shell the network icon showing was the WiFi one, not the wired one. Looking at the output of route, or route -n for simplicity, I would see this: rachel@rainbow:~$ route -n Kernel IP routing table Destination Gateway Genmask Flags Metric RefUse Iface 0.0.0.0 192.168.1.254 0.0.0.0 UG60000 wlp2s0 0.0.0.0 192.168.1.254 0.0.0.0 UG20100 00 enp63s0 169.254.0.0 0.0.0.0 255.255.0.0 U 1000 00 wlp2s0 192.168.1.0 0.0.0.0 255.255.255.0 U 10000 enp63s0 192.168.1.0 0.0.0.0 255.255.255.0 U 60000 wlp2s0 So the metric on the default route on enp63s0 had 20,000 mysteriously added to it, which would obviously make it extremely low-priority. The system was choosing the wifi connection instead, which isn't that great in my office, hence observable slowness. Now, this morning, this seemed to be the sticky situation. It didn't show any sign of changing, whatever I did, after restarts of network- manager, undock/redock, reboots, etc. I could change it manually with ifmetric (and it would work), but that was about it. I would have reported the bug then, but I had to go out. When I got back I plugged in and initially saw the same thing again (that's where the above snippet was pasted from). But *while* the ubuntu-bug network- manager command was running, I noticed the gnome-shell network icon switch to wired, checked again, and saw: rachel@rainbow:~$ route -n Kernel IP routing table Destination Gateway Genmask Flags Metric RefUse Iface 0.0.0.0 192.168.1.254 0.0.0.0 UG10000 enp63s0 0.0.0.0 192.168.1.254 0.0.0.0 UG20600 00 wlp2s0 169.254.0.0 0.0.0.0 255.255.0.0 U 1000 00 wlp2s0 192.168.1.0 0.0.0.0 255.255.255.0 U 10000 enp63s0 192.168.1.0 0.0.0.0 255.255.255.0 U 60000 wlp2s0 So now the wifi connection has 20,000 added to it, which may still be wrong? But I wouldn't otherwise have noticed it because the system is again *behaving* as expected. This all seemed to happen after the network-manager upgrade (from 1.12.6-0ubuntu4 to 1.15.2-0ubuntu1) this morning. I can't say if these metric+20,000 values were present before then, because I didn't have any cause to go looking at it, it always just worked. Could it be some issue with how the newer network-manager, or one of its associated packages, is figuring out the metrics on new connections? Like it's running some new heuristic to determine which one should really be the preferred? If it's like it was just now, when it fixed itself after a minute or so, that's not really a problem, but if it's like it was this morning when it just seemed to be stuck with the ethernet connection at 20100, it is. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: network-manager 1.15.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu19 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Feb 1 13:15:06 2019 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-09-11 (142 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) IpRoute: default via 192.168.1.254 dev wlp2s0 proto dhcp metric 600 default via 192.168.1.254 dev enp63s0 proto dhcp metric 20100 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.1.0/24 dev enp63s0 proto kernel scope link src 192.168.1.106 metric 100 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.101 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true RfKill: 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: Upgraded to disco on 2019-01-13 (18 days ago) nmcli-dev: DEVICE TYPE STATE IP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH wlp2s0 wifi connected full limited /org/freedesktop/NetworkManager/Devices/2 Strange Noises ae54-3c3d-4714-8bf5-7e56bb7249c6 /org/freedesktop/NetworkManager/ActiveConnection/2 enp63s0 ethernet
Re: [Bug 1814088] Re: totem crashed with SIGSEGV in tcache_get() [assertion "nqueue != NULL" failed in g_object_new_internal]
True. And I can confirm it's not listed in my plugins at all. (There's just Cisco OpenH264 and Widevine). Only potentially-relevant extension is Disable HTML5 Autoplay, which if anything should *stop* any video being played before it gets to the software that does it. Only other thing that seems odd, is the mimetime mapping Firefox has for MP3 audio (in prefs) *defaults* to Videos, but in my case it's set to "Use env"... but I wouldn't have set that (is first time I've seen it). It wouldn't be surprising if "Use env" gets it to be sent to Videos too, by a system default? So maybe it was an MP3 file. But not one I knowingly clicked on. ... but finding some MP3 files and playing them in the browser deliberately is working fine. So no, I'm sorry, I'm mystified. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814088 Title: totem crashed with SIGSEGV in tcache_get() [assertion "nqueue != NULL" failed in g_object_new_internal] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1814088/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1814088] Re: totem crashed with SIGSEGV in tcache_get() [assertion "nqueue != NULL" failed in g_object_new_internal]
I agree it's a bit of a nightmare. It was the start of the day and I literally just had Firefox-Next open, and Slack (using the app, not via Firefox). No video had been posted to slack. I can only think some random embedded video went by on the timeline or activities column in tweetdeck (the only tab) on firefox. Nothing else was going on, and said embedded videos usually either work fine or not at all. In the past I've had stuff like this happen when opening a Nautilus window onto a directory with videos in it, so it being the preview of said videos that probably crashed... but not this time. So I agree, there's probably not much to be done about this unless it starts happening more. So far just that one time. (I didn't set it to ignore similar in future.) (NB: replied via email because on-site form is timing out for me, all else working) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814088 Title: totem crashed with SIGSEGV in tcache_get() [assertion "nqueue != NULL" failed in g_object_new_internal] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1814088/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1723615] Re: gnome-shell crashed with SIGSEGV in meta_monitor_mode_get_resolution()
Sure, just thought I'd better say something as it was my report originally. :-) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1723615 Title: gnome-shell crashed with SIGSEGV in meta_monitor_mode_get_resolution() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1723615/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1723615] Re: gnome-shell crashed with SIGSEGV in meta_monitor_mode_get_resolution()
FWIW I can't reproduce this any more either; since 18.04 in fact I've had no problems with gnome-shell crashing. The monitor very nearly always does wake up when it's supposed to now (some difference in the dpms signal being sent? Previously it would always wake for windows and just had a hard time with Linux), and on the few occasions it hasn't, I haven't lost my session and I just needed to powercycle the monitor properly. So I was under the impression this was all fixed. :-) Possibly by not-obviously-related changes elsewhere. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1723615 Title: gnome-shell crashed with SIGSEGV in meta_monitor_mode_get_resolution() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1723615/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1712866] Re: icons from qt applications disappear after screen lock/sleep
FWIW I have *not* seen this since upgrading to Bionic. It was probably fixed sooner, when they said it was, but at some point I gave up on Artful because of various gnome-shell problems including this, went back to Mac, and tried again with a fresh Bionic install, where they almost all seem to have been fixed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1712866 Title: icons from qt applications disappear after screen lock/sleep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1712866/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1773503] [NEW] should offer restart after system firmware upgrade
Public bug reported: The Software app launched by itself this morning to offer me a system firmware (uefi bios) update of my Dell 9370. Presumably in its role as a front-end to fwupd. That's not the bug, that's brilliant, that's pretty much my last remaining reason to keep a Windows partition dealt with. :-) The bug is that when I clicked Update to let it do its job, the procedure *appeared* to fail, not by reporting an error, but simply returning back to the same screen offering the same update. Of course, it was a system firmware update so you need to reboot to apply it, but there was no communication from the app to that effect. Therefore, the bug is that it *looked* like it failed, when it didn't. It's a usability/user communication issue. Expected: After applying the update it should throw up a standard "restart needed" dialogue, as you get on eg: a kernel update. (User can obviously then choose to do it now or later, as normal.) And in that case, also, for the updates tab in Software to not continue to show the update as needing doing. (When I did finally reboot, the update ran completely successfully.) NB: I was watching fwupdmgr monitor while Software ran the update, and indeed it looked there as if the end-state was the previous version of the system firmware was still in place, but no errors reported, so if Software is looking at that (or a more direct-from-the-daemon equivalent) its behaviour may be rational, and the bug is really in what fwupdmgr monitor is reporting. ie: maybe whatever Software is looking at to monitor progress needs to actually report that a reboot is needed, so it can pass that along to the user. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-software 3.28.1-0ubuntu4.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat May 26 09:07:55 2018 InstallationDate: Installed on 2018-04-19 (36 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180409) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-limba N/A gnome-software-plugin-snap3.28.1-0ubuntu4.18.04.1 PackageArchitecture: all SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic package-from-proposed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1773503 Title: should offer restart after system firmware upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1773503/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1766825] Re: Bluetooth issues with Dell XPS 13 (9370)
I hid my earlier posts because I reckoned they were noise, tbh. This one less so. :-) I have replaced the firmware files with those from the windows driver as described above and in the linked-to askubuntu. It worked brilliantly for a few days, no problems at all, but just now failed: Similar to what I found with btusb.enable_autosuspend=n, after one more sleep/wake cycle it came up with both bluetooth *and* wifi interfaces absent. It does at least replicate my earlier findings, that now when it fails, it kills *both* interfaces, not just bluetooth. Maybe that points to a slightly different cause. And at least it does happen far less frequently. Still, the recovery remains to reboot into bios and switch both interfaces off and on again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1766825 Title: Bluetooth issues with Dell XPS 13 (9370) To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1766825/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1766825] Re: Bluetooth issues with Dell XPS 13 (9370)
typically it waited for me to report that it worked before failing. Proving a negative blah indeed. This time my wifi adapter also didn't come back. I suspect this isn't entirely unrelated as aren't they actually the same physical device? In fact that almost makes it weird that usually *only* bluetooth fails to resume. Also, I had that happen exactly once before, on the stock Ubuntu kernel, so I don't think that's a 4.16 mainline issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1766825 Title: Bluetooth issues with Dell XPS 13 (9370) To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1766825/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1766825] Re: Bluetooth issues with Dell XPS 13 (9370)
Catching up as I came at this from another direction. Having got a Windows-installed XPS 13 9370 and installed 18.04 freshly on it itself, its default suspend mode is s2idle, which means lots of battery life gets lost while suspended. But no bluetooth problems. See askubuntu: https://askubuntu.com/questions/1029474/ubuntu-18-04-dell-xps13-9370-no- longer-suspends-on-lid-close?newreg=c37c6aa8b9c94d578157bc0835fe0286 for more about that. But when I applied the working fix for that I encountered the problem described here. I've done some different looking around and found this, a Fedora bug report: https://bugzilla.redhat.com/show_bug.cgi?id=1514836 wherein it looks like they may have fixed it for the XPS 13 9360, and that fix is upstream and I guess will appear in 4.17. However that would need to be amended to take in the 9370 too, as it looks like being the same issue. Currently I'm running the workaround described earlier in that bug report, to use the kernel parameter btusb.enable_autosuspend=n (actually I'm doing it with "options btusb enable_autosuspend=n" in a file in /etc/modprobe.d); but that kernel option only arrived in 4.16 so I'm running the 4.16 mainline kernel to get it. It *appears* to be working, with bluetooth having survived a couple of deep sleeps so far this morning, but I haven't been running it very long to be sure. (Proving a negative blah.) But this is a lesser workaround, as I understand it, telling the bt adapter not to go to sleep during deep sleep, rather than, presumably preferably, letting it sleep but waking it up thoroughly afterwards, which is the suspend-resume fix. I think what we probably want is that fix from Redhat that's in btusb.c in kernel head now, to also be applied to 9370. And then for us to get that kernel! Either presumably when the -hwe kernels start, or Dell can push one out, or anyway in 18.10. ** Bug watch added: Red Hat Bugzilla #1514836 https://bugzilla.redhat.com/show_bug.cgi?id=1514836 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1766825 Title: Bluetooth issues with Dell XPS 13 (9370) To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1766825/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768831] Re: package initramfs-tools 0.130ubuntu3 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1
belately thought of trying: running sudo update-initramfs -k all -c produced no errors for both currently installed kernels: rachel@spitfire:~$ sudo update-initramfs -k all -c update-initramfs: Generating /boot/initrd.img-4.15.0-21-generic update-initramfs: Generating /boot/initrd.img-4.15.0-20-generic FWIW... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768831 Title: package initramfs-tools 0.130ubuntu3 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768831/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768831] [NEW] package initramfs-tools 0.130ubuntu3 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1
Public bug reported: kernel upgrade appeared to go OK actually; on the *second* reboot after that, this appeared after login. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: initramfs-tools 0.130ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-21.22-generic 4.15.17 Uname: Linux 4.15.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Fri Apr 27 13:37:48 2018 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2018-02-20 (71 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: initramfs-tools Title: package initramfs-tools 0.130ubuntu3 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768831 Title: package initramfs-tools 0.130ubuntu3 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768831/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1766928] [NEW] Does not retain choice to trust ssl/tls certificates for irc servers
Public bug reported: (This may actually be an Empathy problem, as I understand it's providing the backend) If an IRC server allows for an SSL/TLS connection (eg: it's a ZNC proxy), but is using a self-signed certificate, Polari, correctly the first time, shows a dialog asking if I want to continue despite this. There is a checkbox where you can indicate that it should remember this choice for all future connections. Checking that checkbox has no effect. The *next* time you need to connect, it will ask you again, and forever more. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: polari 3.28.0-1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 25 17:40:27 2018 InstallationDate: Installed on 2018-04-19 (6 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180409) SourcePackage: polari UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: polari (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1766928 Title: Does not retain choice to trust ssl/tls certificates for irc servers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/polari/+bug/1766928/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1724439] Re: gnome-shell crashed with SIGSEGV in meta_window_get_monitor() from ffi_call_unix64() from ffi_call() from gjs_invoke_c_function() from function_call()
not that we should let this (bug report) thread descend into KDE advocacy but I did actually try that, last time around. I'm afraid I couldn't get the hang of it, and then plasma went all weird on me, like the plasma background not filling the screen kind of weird. But I did try it. :-) Used to use KDE back in the day. -- Rachel On 15/03/18 13:39, dwilches wrote: > > > Rachel, no need to switch to Mac to avoid this problem. What I ended up > doing was this: > > $ sudo add-apt-repository ppa:kubuntu-ppa/backports > $ sudo apt update && sudo apt upgrade > $ sudo apt install kubuntu-desktop > > > -- > Daniel Wilches > > > On Thu, Mar 15, 2018 at 4:21 AM, Rachel Greenham <1724...@bugs.launchpad.net >> wrote: >> Well, my bug #1756036 just got (automatically-i-think) marked as a >> duplicate of this one, and I'm on 18.04 (gnome-shell 3.27.92-0ubuntu1) >> So that's one, Daniel. ;-) I'd been getting this on some mornings, but >> the bug report was getting rejected because of outdated packages until >> this morning. Interestingly it doesn't seem to happen again later in the >> day, so, as noted before, length-of-sleep may be a factor. >> >> I reported a lot on these bugs in 17.10, until I eventually gave up and >> just used my (half-the-speed) mac for a while. Freshly-installed 18.04 >> and tried again, and I *am* having far less trouble. When it does go >> wrong, it "fails better", in that it seems to recover reasonably well >> and leave me with a working session, even if there are a couple of side- >> effects (eg: having both dash-to-dock and the dash in >> activities/applications) which clear on an orderly logout/login. >> >> -- >> You received this bug notification because you are subscribed to the bug >> report. >> https://bugs.launchpad.net/bugs/1724439 >> >> Title: >>gnome-shell crashed with SIGSEGV in meta_window_get_monitor() from >>ffi_call_unix64() from ffi_call() from gjs_invoke_c_function() from >>function_call() >> >> To manage notifications about this bug go to: >> https://bugs.launchpad.net/mutter/+bug/1724439/+subscriptions >> -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1724439 Title: gnome-shell crashed with SIGSEGV in meta_window_get_monitor() from ffi_call_unix64() from ffi_call() from gjs_invoke_c_function() from function_call() To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1724439/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1724439] Re: gnome-shell crashed with SIGSEGV in meta_window_get_monitor() from ffi_call_unix64() from ffi_call() from gjs_invoke_c_function() from function_call()
Well, my bug #1756036 just got (automatically-i-think) marked as a duplicate of this one, and I'm on 18.04 (gnome-shell 3.27.92-0ubuntu1) So that's one, Daniel. ;-) I'd been getting this on some mornings, but the bug report was getting rejected because of outdated packages until this morning. Interestingly it doesn't seem to happen again later in the day, so, as noted before, length-of-sleep may be a factor. I reported a lot on these bugs in 17.10, until I eventually gave up and just used my (half-the-speed) mac for a while. Freshly-installed 18.04 and tried again, and I *am* having far less trouble. When it does go wrong, it "fails better", in that it seems to recover reasonably well and leave me with a working session, even if there are a couple of side- effects (eg: having both dash-to-dock and the dash in activities/applications) which clear on an orderly logout/login. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1724439 Title: gnome-shell crashed with SIGSEGV in meta_window_get_monitor() from ffi_call_unix64() from ffi_call() from gjs_invoke_c_function() from function_call() To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1724439/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1756036] Re: gnome-shell crashed with SIGSEGV in meta_window_get_monitor()
*** This bug is a duplicate of bug 1724439 *** https://bugs.launchpad.net/bugs/1724439 Daniel's latest comment on that bug shows that it looks like it doesn't affect 3.27. This is 3.27. It's a shame those attachments got deleted... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1756036 Title: gnome-shell crashed with SIGSEGV in meta_window_get_monitor() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1756036/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1733567] [NEW] apport fails to send crash reports
Public bug reported: There's an ongoing issue with gnome-shell crashing during or on exit from screen lock. I am no longer able to report when this happens because apport silently refuses to send the bug report. If the automatic whoopsie dialog opens at all (it doesn't, often), and I click to send the report, the window closes, and that's it. If I try to use apport-cli to send a specific .crash file, it shows me the menu, I type S to send the report, and apport-cli exits immediately, and again there's no further action. The crashes may be similar to those posted before, although this being an ongoing and unfixed issue (eg: bug #1723620, bug #1723615), one would expect to be able to send updated bug reports at least to show that, eg: a newer version of the affected packages didn't fix it, or to add a new observation (in this case that despite the crash my login session was not ended by it, which is new). At the very least one would expect to see either the list of possible duplicates, or at very *very* least, a message saying that it's been submitted alreadyk or that my version of the affected package is obsolete (it isn't, although I see apport itself is getting an upgrade, but this problem has already persisted through a few apport upgrades). But there's nothing, no feedback at all, it just exits. I wonder also if what's failed here is the ability to open a new browser window, but if so it affects both google chrome and firefox, when each is set to be the default browser. Also, *this* bug, initiated by typing "ubuntu-bug apport", was submitted just fine, but this bug is not the result of an actual *crash* (ie: resulting in a .crash file). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: apport 2.20.7-0ubuntu3.4 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 Uname: Linux 4.13.0-17-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportLog: ERROR: apport (pid 7178) Tue Nov 21 11:05:18 2017: called for pid 24462, signal 11, core limit 0, dump mode 1 ERROR: apport (pid 7178) Tue Nov 21 11:05:18 2017: executable: /usr/bin/gnome-shell (command line "/usr/bin/gnome-shell") ERROR: apport (pid 7178) Tue Nov 21 11:05:18 2017: debug: session gdbus call: (true,) ERROR: apport (pid 7178) Tue Nov 21 11:06:06 2017: wrote report /var/crash/_usr_bin_gnome-shell.1000.crash ApportVersion: 2.20.7-0ubuntu3.4 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Nov 21 11:15:54 2017 InstallationDate: Installed on 2017-07-30 (113 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to artful on 2017-08-22 (90 days ago) ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1733567 Title: apport fails to send crash reports To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1733567/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1505409] Re: gnome-shell crashed with SIGTRAP in x_io_error() from _XIOError() from _XEventsQueued() from XPending() from gdk_check_xpending() ["Connection to xwayland lost"]
It failed to hold true on day 2 anyway, as today the session didn't survive the overnight sleep. But in any case I re-checked the bug of mine that was marked a duplicate of this one, and saw as it was during one of my brief try-outs with wayland, is irrelevant to my current gnome-session woes, as I'm back on xorg. I had thought this just one of the family of gnome-shell crashers that was affecting both xorg and wayland, but seemingly only with displayport monitors. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1505409 Title: gnome-shell crashed with SIGTRAP in x_io_error() from _XIOError() from _XEventsQueued() from XPending() from gdk_check_xpending() ["Connection to xwayland lost"] To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1505409/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1505409] Re: gnome-shell crashed with SIGTRAP in x_io_error() from _XIOError() from _XEventsQueued() from XPending() from gdk_check_xpending() ["Connection to xwayland lost"]
Interesting For what it's worth: On seeing #44 I tried turning off notification popups and lock screen notifications and left it overnight. On waking I had the usual problems I often (not always) have with my monitors persuading them to wake up (one of them is a model with a known issue with waking up: early-revision Dell P2715Q), but once I'd fought through that (multiple monitor power-cycles) I still had the gnome session that I had left on screen the previous evening. The first time *that's* happened on more than a very short screen lock period since... since I installed the Artful alpha I think. One possible minor glitch, though probably not part of this bug: When the monitors did eventually admit there was a signal coming from the computer, I briefly saw the logged in gnome desktop before it was replaced by the lock screen. Is that supposed to happen? This is on Gnome Xorg session, on nVidia 387.22 (GTX960), gnome-shell 3.26.1-0ubuntu5, mutter 3.26.1-2ubuntu2 (the latter of which I know has a newer version now in proposed which I'll be installing soon). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1505409 Title: gnome-shell crashed with SIGTRAP in x_io_error() from _XIOError() from _XEventsQueued() from XPending() from gdk_check_xpending() ["Connection to xwayland lost"] To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1505409/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1723615] Re: gnome-shell crashed with SIGSEGV in meta_monitor_mode_get_resolution()
In fact I'm already on 387.22 which, I see from a nearby post on the same forum, has the same fix: https://devtalk.nvidia.com/default/topic/1025794/unix-graphics- announcements-and-news/linux-solaris-and-freebsd-driver-387-22/ It hasn't helped. TBH I don't think it applies as (fx: me reading up more on what PRIME sync is) I don't think I'm using PRIME sync... my mobo has integrated Intel HD4600 as well but I don't use it at all, and the nvidia card is selected as default in uefi bios. I've done no prime sync setup at all. There appear to be a shedload of upstream gnome-shell bugs relating to these problems, and not everyone having them is using nVidia, though it may be that they are all using DisplayPort to connect to their monitors, although why something as user-level as gnome-shell is bothered with *which* ports are used is beyond me... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1723615 Title: gnome-shell crashed with SIGSEGV in meta_monitor_mode_get_resolution() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1723615/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1723620] Re: gnome-shell crashed with SIGSEGV in meta_window_update_for_monitors_changed()
Just poking in to say this is still happening, and not magically fixed by Artful's release date. It happened today, but trying to ubuntu-bug the crash file failed. (It just quit when I clicked Continue.) One difference today: Thinking maybe my screen-sleep woes were partly because of gnome shell being in lock mode, I tried instead disabling screen lock and suspend and just using ye olde x11 screen blanking to standby, ie: xset dpms 1200 0 0. It still died, leaving a crash file reporting this same error, at the time I tried to wake things up again. I think again, supported by the description of this bug, it was probably due to slowness in monitors waking up, or one of them having problems waking up fully at all, then gnome-shell responds ungracefully - perhaps even disgracefully - to the change in monitors. gnome shell is so damn fragile. gnome-shell 3.26.1-0ubuntu5 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1723620 Title: gnome-shell crashed with SIGSEGV in meta_window_update_for_monitors_changed() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1723620/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1712866] Re: icons from qt applications disappear after screen lock/sleep
... and they survive at least a short screen lock too. Sorry for the multiple posts. Everyone ignore when anyone says to install sni-qt to fix qt app indicator issues. it doesn't, it makes things worse! :-) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1712866 Title: icons from qt applications disappear after screen lock/sleep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1712866/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1712866] Re: icons from qt applications disappear after screen lock/sleep
just as an aside, relating to comments #13 and #14... removing sni-qt *did* help. I have my appindicators back in xorg. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1712866 Title: icons from qt applications disappear after screen lock/sleep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1712866/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1712866] Re: icons from qt applications disappear after screen lock/sleep
(confirmed stays fixed after a longer sleep (actual suspend) too. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1712866 Title: icons from qt applications disappear after screen lock/sleep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1712866/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1712866] Re: icons from qt applications disappear after screen lock/sleep
Confirmed on my Wayland system: after a short lock-screen test, both my qt indicators, enpass and nextcloud-client, survive the lock period. With respect to another comment above, both of these are the wrong size, the nextcloud one being half its proper size, and the enpass one being the correct width now, but actually double it's proper *height*, or at least stretched vertically to fill the height of the top bar. Which I mention in order to say that despite these size issues their *presence* on the bar after a screen lock still appears to be fixed. Will let it sleep for longer in case that produces different results. (It does with respect to gnome shell crashing bugs, so it seems worth testing.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1712866 Title: icons from qt applications disappear after screen lock/sleep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1712866/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1712866] Re: icons from qt applications disappear after screen lock/sleep
i have sni-qt installed already, i believe as a result of following an earlier hint to the same effect. It didn't actually have any discernible effect for me. (In fact, I wonder if I should remove it...) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1712866 Title: icons from qt applications disappear after screen lock/sleep To manage notifications about this bug go to: https://bugs.launchpad.net/qt/+bug/1712866/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1712866] Re: icons from qt applications disappear after screen lock/sleep
I definitely have 17.10.2 installed, from proposed. On my Xorg system: In fact since this bug was first reported, things have actually gotten worse, in that these days these icons hardly ever appear *at all* from the original login, let alone disappearing after a screen lock. 17.10.2 hasn't fixed this, but OTOH this wasn't precisely the bug you were trying to fix. But as things stand, as usual, my nextcloud and enpass icons are not showing up at all so persistence through a screen lock is untestable. (Also I still have the problem of gnome-shell crashing during screen lock, so it would be hard to test anyway. But that too is the subject of other bug reports.) "hardly ever"? Sometimes, occasionally, they show up, and I don't know what's different about those days. Not today, apparently. This appears to be an Xorg thing. On my wayland machine they do show up on login, and the disappear after screen lock, as originally described. I'll enable proposed on that machine and test over the weekend. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1712866 Title: icons from qt applications disappear after screen lock/sleep To manage notifications about this bug go to: https://bugs.launchpad.net/qt/+bug/1712866/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1721189] Re: Thunderbird 1:52.4.0+build1-0ubuntu1 broken user interface
Yes, I see what you see: the borders around the tabs are missing. Not just on the Security prefpane, on all of them, that have tabs. But that's all that's wrong. (Or at least all that's obviously wrong.) So while I can corroborate you, I think it's a different error and should have a separate bug report. This bug was for the whole user interface falling apart, rendering the application unusable, and has been fixed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1721189 Title: Thunderbird 1:52.4.0+build1-0ubuntu1 broken user interface To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1721189/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1721189] Re: Thunderbird 1:52.4.0+build1-0ubuntu1 broken user interface
Attached. I'm using the Arc theme across the desktop, but no Thunderbird theme (or rather, the default). ** Attachment added: "Screenshot from 2017-10-19 18-44-31.png" https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1721189/+attachment/4976376/+files/Screenshot%20from%202017-10-19%2018-44-31.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1721189 Title: Thunderbird 1:52.4.0+build1-0ubuntu1 broken user interface To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1721189/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1721189] Re: Thunderbird 1:52.4.0+build1-0ubuntu1 broken user interface
Looks fine to me in 1:52.4.0+build1-0ubuntu2. I see the tabs just as they are in the other pref panes. Even if not, it would be a highly localised and minor problem, not at all like the completely broken, unusable user interface, with large parts missing or unstable, that we had as of the original bug report. So it looks like a new issue. Possibly theme related? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1721189 Title: Thunderbird 1:52.4.0+build1-0ubuntu1 broken user interface To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1721189/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1717170] Re: gnome-shell crashes with SIGABRT: mutter:ERROR:backends/meta-monitor-manager.c:2274:meta_monitor_manager_get_logical_monitor_from_number: assertion failed: ((unsigned int) number < g
Adding this to *this* bug, despite the "Fix Released", because it exactly matches the original post for this bug, whereas the others I've encountered and reported on are different: Oct 14 20:02:45 fleetfoot gnome-shell[12750]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->logical_monitors)' failed Oct 14 20:02:45 fleetfoot gnome-shell[12750]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed Oct 14 20:02:45 fleetfoot kernel: [29646.218484] gnome-shell[12750]: segfault at 40 ip 7f9354b11e60 sp 7ffd0b949810 error 4 in libmutter-1.so.0.0.0[7f9354a6c000+141000] Oct 14 20:02:46 fleetfoot gnome-shell[25511]: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. Oct 14 20:02:46 fleetfoot gnome-shell[25511]: JS WARNING: [resource:///org/gnome/shell/ui/main.js 315]: reference to undefined property "MetaStage" Oct 14 20:02:46 fleetfoot gnome-shell[25511]: JS WARNING: [resource:///org/gnome/shell/ui/layout.js 221]: reference to undefined property "MetaWindowGroup" Oct 14 20:02:46 fleetfoot gnome-shell[25511]: JS WARNING: [resource:///org/gnome/shell/ui/osdMonitorLabeler.js 59]: reference to undefined property "MetaDBusDisplayConfigSkeleton" Oct 14 20:02:46 fleetfoot gnome-shell[25511]: JS WARNING: [resource:///org/gnome/gjs/modules/tweener/tweener.js 540]: reference to undefined property "isSpecialProperty" Oct 14 20:02:46 fleetfoot gnome-shell[25511]: JS WARNING: [resource:///org/gnome/shell/ui/slider.js 38]: reference to undefined property "CallyActor" Oct 14 20:02:46 fleetfoot gnome-shell[25511]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->logical_monitors)' failed Oct 14 20:02:46 fleetfoot gnome-shell[25511]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed Oct 14 20:02:46 fleetfoot gnome-shell[25511]: Extension "dash-to-d...@micxgx.gmail.com" had error: TypeError: this._monitor is undefined Oct 14 20:02:46 fleetfoot gnome-shell[25511]: loading user theme: /usr/share//themes/Arc-Dark/gnome-shell/gnome-shell.css Oct 14 20:02:46 fleetfoot gnome-shell[25511]: Some code accessed the property 'DBusMenu' on the module 'interfaces'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway. Oct 14 20:02:46 fleetfoot gnome-shell[25511]: Some code accessed the property 'WORKAROUND_RELOAD_TYPE_REGISTER' on the module 'util'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway. Oct 14 20:02:46 fleetfoot gnome-shell[25511]: Some code accessed the property 'StatusNotifierWatcher' on the module 'statusNotifierWatcher'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway. Oct 14 20:02:46 fleetfoot gnome-shell[25511]: Some code accessed the property 'StatusNotifierWatcher' on the module 'interfaces'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway. Oct 14 20:02:47 fleetfoot kernel: [29647.398006] gnome-shell[25511]: segfault at 40 ip 7f67c43bce60 sp 7ffd22dab610 error 4 in libmutter-1.so.0.0.0[7f67c4317000+141000] Symptoms *observed*, again, were that I was logged out when I returned to the computer the following afternoon. So this happened twice in quick succession. The above fragment is from a 'grep gnome-shell syslog.1', I can provide a fuller log if anyone's interested, but there was no /var/run/crash file generated from this event. gnome-shell: 3.26.1-0ubuntu3 mutter & libmutter-1-0: 3.26.1-2ubuntu1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1717170 Title: gnome-shell crashes with SIGABRT: mutter:ERROR:backends/meta-monitor-
[Bug 1717170] Re: gnome-shell crashes with SIGABRT: mutter:ERROR:backends/meta-monitor-manager.c:2274:meta_monitor_manager_get_logical_monitor_from_number: assertion failed: ((unsigned int) number < g
bug #1723615 came up with this fix in place. Whack-a-mole! :-) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1717170 Title: gnome-shell crashes with SIGABRT: mutter:ERROR:backends/meta-monitor- manager.c:2274:meta_monitor_manager_get_logical_monitor_from_number: assertion failed: ((unsigned int) number < g_list_length (manager->logical_monitors)) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1717170/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1717170] Re: gnome-shell crashes with SIGABRT: mutter:ERROR:backends/meta-monitor-manager.c:2274:meta_monitor_manager_get_logical_monitor_from_number: assertion failed: ((unsigned int) number < g
I had one crash after applying this yesterday (and rebooting): it crashed right out to the console, not even to the login screen, and when I tried logging in again the session failed to start. But since a second reboot it's apparently been fine. This bug went away, and so too has my bug #1720149 (so far anyway, I don't seem able to reproduce it now, although saying so will doubtless trigger it next time I let the displays sleep). I can't explain that first crash, but as I also can't repeat it, I guess we ignore it for now. This in Gnome in Xorg under nVidia 387, modeset=0. xorg sessions seem unable to start with modeset=1 btw. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1717170 Title: gnome-shell crashes with SIGABRT: mutter:ERROR:backends/meta-monitor- manager.c:2274:meta_monitor_manager_get_logical_monitor_from_number: assertion failed: ((unsigned int) number < g_list_length (manager->logical_monitors)) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1717170/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1722779] [NEW] Xorg session exits on login if nvidia modeset=1
Public bug reported: This may relate to this item in the changelog for this version of gdm3: * Drop 95_hide_x11_sessions_with_nvidia_kdms.patch: - No longer needed with nvidia-384 I noticed before this version that indeed, if I enabled modeset on nvidia-387 (which actually worked), I only saw the Wayland sessions in gdm, not the Xorg ones. I actually want Xorg sessions right now (For Reasons I Could Bore You With), but I thought I'd try enabling modeset again when I saw this. Instead what happens is, I see and can choose the Xorg sessions, but when I try to log in using GNOME on Xorg, it just returns back to the gdm login screen, after a pause of a few seconds. There's no obvious signs of an actual crash, in syslog or in /var/crash. I spot this though, during each attempted X session startup: Oct 11 12:39:07 fleetfoot gsd-xsettings[2515]: Failed to get current display configuration state: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.gnome.Mutter.DisplayConfig" does not exist and Oct 11 12:39:21 fleetfoot gnome-shell[2816]: Failed to apply DRM plane transform 0: Invalid argument Oct 11 12:39:21 fleetfoot gnome-shell[2816]: Failed to apply DRM plane transform 0: Invalid argument Oct 11 12:39:21 fleetfoot org.gnome.Shell.desktop[2816]: Disabling glamor and dri3, EGL setup failed Oct 11 12:39:21 fleetfoot org.gnome.Shell.desktop[2816]: Failed to initialize glamor, falling back to sw Wayland session appears to be working fine FWIW, with nvidia-387. But previously I did have a couple of random-seeming system hangs using it, which is one of the boring reasons I'm still preferring Xorg on nvidia. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gdm3 3.26.1-3ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4 Uname: Linux 4.13.0-15-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Oct 11 12:42:42 2017 InstallationDate: Installed on 2017-07-30 (72 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: gdm3 UpgradeStatus: Upgraded to artful on 2017-08-22 (49 days ago) ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1722779 Title: Xorg session exits on login if nvidia modeset=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1722779/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1720149] Re: gnome-shell segv on wake from display or system sleep
It just happened, so attached the crash file that was generated. NB: gnome-shell 3.26.1-0ubuntu2 mutter 3.26.1-1 libmutter-1-0 3.26.1-1 NB: I notice there's also a libmutter-0-0 installed, possibly a hangover from the original zesty install. but ldd $(which gnome-shell) indicates it's linked to libmutter-1.so.0 so it's presumably irrelevant. I've now removed it anyway. This was a bit of a messy event. It went something like this: Attempted to wake system (from displaysleep, wasn't suspended) It appeared at first to work! My session was there. But the displays config was wrong. I noticed that my 4K monitor had (again, I think it's *its* problem) woken up thinking it's a 1440p monitor. As this is usually fixed by powercycling it, I did so. The second monitor (actually the first in discovery order), which is *actually* a 1440p monitor, also went to sleep. Power-cycling *it* woke them both up, (I think; things got confusing) but at that point it came back to the gdm login screen. So I'm guessing around then was where the gnome-shell crash happened. Often it's simpler than that. I wake the system up, it comes up logged- out. ** Attachment added: "_usr_bin_gnome-shell.1000.crash" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1720149/+attachment/4967524/+files/_usr_bin_gnome-shell.1000.crash -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1720149 Title: gnome-shell segv on wake from display or system sleep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1720149/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1720149] Re: gnome-shell segv on wake from display or system sleep
I’m afk today but will try to get this information on Wednesday. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1720149 Title: gnome-shell segv on wake from display or system sleep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1720149/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1720149] Re: gnome-shell segv on wake from display or system sleep
That wouldn't surprise me. I've seen other reports, on IRC, to the same effect. Sadly, displayport is not optional here, not if I actually want to run my monitors at full resolution. Someone mentioned it being a "known bug" in mutter? However they didn't link to it and I wasn't at the keyboard at the time to nag them to do so. It would explain how I haven't seen it at all on the laptop, which I only use with its internal screen. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1720149 Title: gnome-shell segv on wake from display or system sleep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1720149/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1720760] Re: Under Xorg app windows unscaled until gnome tweaks is launched.
Seems to have gone away with recent upgrades. I can't tell exactly which as I was attempting to use wayland under amd and even under nvidia-387 (which worked fine except for a couple of random system freezes during closing windows). Back on nvidia/xorg because of that (although not exhaustively tested that *that* isn't still going to happen), and the scaling problem appears to have resolved. Guessing that was fixed upstream in 3.26.1. mutter version 3.26.1-1 gnome-shell 3.26.1-0ubuntu1 nvidia-387 387.12-0ubuntu0~gpu17.10.1 from graphics-drivers/ppa There were problems *selecting* 200% scaling in this environment with two monitors. I had to try several times before it took, but it did eventually. That'll be a different bug though. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1720760 Title: Under Xorg app windows unscaled until gnome tweaks is launched. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1720760/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1721189] Re: Thunderbird 1:52.4.0+build1-0ubuntu1 broken user interface
Confirmed fixed for me too. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1721189 Title: Thunderbird 1:52.4.0+build1-0ubuntu1 broken user interface To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1721189/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1721602] [NEW] When creating web application, should inherit cookies for site
Public bug reported: I wanted to use GnomeWeb to run Tweetdeck as a saved web application. So I installed epiphany-browser, navigated to tweetdeck.twitter.com, logged in, and then attempted to save it as a web application. This all seemed to work, as well as Tweetdeck itself running apparently happily in there, and being OK with being moved to a screen with a different scaling factor (which Chrome's webapps don't handle, which is why I'm doing this.) When I launched it, it invited me to log in. I clicked on the button, but it opened tweetdeck in Chrome, my default browser. I was already logged in there, so it just opened. There was no-where for me to log in the GnomeWeb web application. I was at an impasse. There seems to be no way in the user interface to do this. I have a workaround: I copied the cookies.sqlite file from ~/.config/epiphany to the webapp subdirectory (ie: ~/.config/epiphany /app-epiphany-tweetdeck-longhexnumber) and relaunched the webapp. This worked. Suggestion for a fix could be that when saving a new web application, to copy the cookies in the main browser cookies list that relate to that web application's site. I didn't do it selectively though, I just copied the whole cookies file (I had not visited another site since installing it so there probably isn't anything else in there that tweetdeck doesn't need). It all seems to be working now, but this is just a commandline workaround. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: epiphany-browser 3.26.1-1ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-14.15-generic 4.13.4 Uname: Linux 4.13.0-14-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Oct 5 18:17:26 2017 InstallationDate: Installed on 2017-07-30 (66 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: epiphany-browser UpgradeStatus: Upgraded to artful on 2017-08-22 (44 days ago) ** Affects: epiphany-browser (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1721602 Title: When creating web application, should inherit cookies for site To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/epiphany-browser/+bug/1721602/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1721577] [NEW] switch monitor configurations crash-freezes desktop
Public bug reported: I hit p by accident. I'll be removing the keybinding now I found it, in org.gnome.mutter.keybindings switch-monitor. It's too common a keystroke I hit when working under macOS that I'm just too likely to hit it by accident. But that's my problem. But it wouldn't be a problem if it didn't crash the system. When I do so, the overlay comes up offering Mirror, Join, External-only, Internal- only options, then the screens blank for a moment, and when they come back, the desktop is completely frozen and unresponsive. Including the pointer, which is immovable. My setup is running a Gnome/Wayland session using nvidia-387 drivers (which apart from this is working perfectly!) I have two monitors, but they're different resolutions, and are currently set to different scaling factors (hence trying so hard to run Wayland on nVidia). I see this in syslog from just before the crash: Oct 5 16:17:12 fleetfoot gnome-shell[1757]: Failed to apply DRM plane transform 0: Invalid argument Oct 5 16:17:12 fleetfoot gnome-shell[1757]: Failed to apply DRM plane transform 0: Invalid argument Oct 5 16:17:12 fleetfoot gnome-shell[1757]: Ignoring length property that isn't a number at line 732, col 24 Oct 5 16:17:12 fleetfoot gnome-shell[1757]: message repeated 2 times: [ Ignoring length property that isn't a number at line 732, col 24] Oct 5 16:17:26 fleetfoot gnome-shell[1757]: [AppIndicatorSupport-FATAL] unable to lookup icon for state-ok ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@Oct 5 16:18:43 fleetfoot rsyslogd: [origin software="rsyslogd" swVersion="8.16.0" x-pid="940" x-info="http://www.rsyslog.com;] start ... and then I hit reset. It was unresponsive. I tried it again, and saw something slightly different. The one thing in common seems to be the gnome-shell "Failed to apply DRM plane transform 0: Invalid" messages. Oct 5 16:19:11 fleetfoot dbus-daemon[1652]: Activating via systemd: service name='org.gtk.vfs.Metadata' unit='gvfs-metadata.service' Oct 5 16:19:11 fleetfoot systemd[1638]: Starting Virtual filesystem metadata service... Oct 5 16:19:11 fleetfoot dbus-daemon[1652]: Successfully activated service 'org.gtk.vfs.Metadata' Oct 5 16:19:11 fleetfoot systemd[1638]: Started Virtual filesystem metadata service. Oct 5 16:19:11 fleetfoot com.intel.dleyna-renderer[1652]: namespace error : xmlns:ms: ' urn:microsoft-com:wmc-1-0' is not a valid URI Oct 5 16:19:11 fleetfoot com.intel.dleyna-renderer[1652]: xmlns:ms=" urn:microsoft-com:wmc-1-0" Oct 5 16:19:11 fleetfoot com.intel.dleyna-renderer[1652]: ^ Oct 5 16:19:11 fleetfoot dleyna-renderer-service[2319]: New media server /com/intel/dLeynaRenderer/server/0 Oct 5 16:19:14 fleetfoot gnome-shell[1702]: Failed to apply DRM plane transform 0: Invalid argument Oct 5 16:19:14 fleetfoot gnome-shell[1702]: Failed to apply DRM plane transform 0: Invalid argument Oct 5 16:19:14 fleetfoot gnome-shell[1702]: Ignoring length property that isn't a number at line 732, col 24 Oct 5 16:19:14 fleetfoot gnome-shell[1702]: Ignoring length property that isn't a number at line 732, col 24 Oct 5 16:19:14 fleetfoot gsd-a11y-keyboa[1923]: The program 'gsd-a11y-keyboard' received an X Window System error.#012This probably reflects a bug in the program.#012The error was 'BadRRCrtc (invalid Crtc parameter)'.#012 (Details: serial 178 error_code 148 request_code 140 (RANDR) minor_code 20)#012 (Note to programmers: normally, X errors are reported asynchronously;#012 that is, you will receive the error a while after causing it.#012 To debug your program, run it with the GDK_SYNCHRONIZE environment#012 variable to change this behavior. You can then get a meaningful#012 backtrace from your debugger if you break on the gdk_x_error() function.) Oct 5 16:19:14 fleetfoot kernel: [ 35.456063] do_trap: 20 callbacks suppressed Oct 5 16:19:14 fleetfoot kernel: [ 35.456065] traps: gsd-a11y-keyboa[1923] trap int3 ip:7f6e22471921 sp:7ffd7f3536b0 error:0 in libglib-2.0.so.0.5400.0[7f6e22421000+111000] Oct 5 16:19:16
[Bug 1505409] Re: gnome-shell crashed with SIGTRAP in x_io_error() from _XIOError() from _XEventsQueued() from XPending() from gdk_check_xpending() ["Connection to xwayland lost"]
I got here because my apport-raised bug #1721492 apparently automatically got marked as a duplicate of this. I'm not so sure: This happened after a kernel upgrade to 4.13.0-14-generic. Yesterday I was happily using this system in a wayland session using nouveau. On reboot with this update, all I saw was a black screen. I had to ssh in from my phone to see in /var/log/syslog a bunch of apparent nouveau-drm failures like this: Oct 5 10:12:46 fleetfoot kernel: [1.304052] [drm] Initialized nouveau 1.3.1 20120801 for :01:00.0 on minor 0 Oct 5 10:12:46 fleetfoot kernel: [4.245166] nouveau :01:00.0: DRM: EVO timeout Oct 5 10:12:46 fleetfoot kernel: [6.245268] nouveau :01:00.0: DRM: base-1: timeout Oct 5 10:12:46 fleetfoot kernel: [8.250984] nouveau :01:00.0: DRM: base-1: timeout Oct 5 10:12:47 fleetfoot kernel: [9.292554] nouveau :01:00.0: bus: MMIO read of FAULT at 61a804 [ IBUS ] Oct 5 10:12:47 fleetfoot kernel: [9.302375] nouveau :01:00.0: bus: MMIO read of FAULT at 61a804 [ IBUS ] Oct 5 10:12:55 fleetfoot kernel: [ 17.770234] nouveau :01:00.0: DRM: base-0: timeout Oct 5 10:12:57 fleetfoot kernel: [ 19.770400] nouveau :01:00.0: DRM: base-0: timeout Oct 5 10:12:57 fleetfoot kernel: [ 19.776398] nouveau :01:00.0: DRM: base-1: timeout Oct 5 10:12:59 fleetfoot kernel: [ 21.776531] nouveau :01:00.0: DRM: base-1: timeout Oct 5 10:12:59 fleetfoot kernel: [ 21.807177] nouveau :01:00.0: DRM: base-0: timeout Oct 5 10:13:01 fleetfoot kernel: [ 23.782358] nouveau :01:00.0: DRM: base-1: timeout Oct 5 10:13:03 fleetfoot kernel: [ 25.801765] nouveau :01:00.0: DRM: base-0: timeout Oct 5 10:13:03 fleetfoot kernel: [ 25.807270] nouveau :01:00.0: DRM: base-1: timeout Oct 5 10:13:05 fleetfoot kernel: [ 27.818059] nouveau :01:00.0: DRM: base-0: timeout Oct 5 10:13:05 fleetfoot kernel: [ 27.823600] nouveau :01:00.0: DRM: base-1: timeout ... and so on. It doesn't stop until I reboot (which hangs, although I think after rsyslogd has closed. I need to hit reset). I had seen this before, on the first kernel 4.13 version in Artful. Reverting then to the last 4.12 let things work for me. But trying that this time, trying to boot kernel 4.13.0.12, didn't help; I just got the same symptoms. Got the system working again by installing the nvidia-387 proprietary drivers and using them in default configuration in an xorg session. On the previous occasion I saw this, it also affected nvidia-384 (as was current then), with continual panics reported in the nvidia-drm module, until I turned off modeset (at the time I had, with partial success, been running wayland on that). I haven't yet tried modeset on this nvidia driver. After I got the system working again, and logged in, I was presented with the apport bug report that led to #1721492. I queried in there whether it was the same issue, but on later seeing syslog it looks like those nouveau errors only show up after gnome-shell (in gdm) is launched. Attached to this comment, the complete syslog of that first session after rebooting from the upgrade. I think those nouveau timeout errors are the thing. Attached to the next comment (as I seem unable to attach more than one file to a comment) is the section from /var/log/apt/history.log showing what was upgraded this morning before that all happened. Other drivers were involved. ** Attachment added: "syslog.nouveaudrm" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1505409/+attachment/4962743/+files/syslog.nouveaudrm -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1505409 Title: gnome-shell crashed with SIGTRAP in x_io_error() from _XIOError() from _XEventsQueued() from XPending() from gdk_check_xpending() ["Connection to xwayland lost"] To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1505409/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1505409] Re: gnome-shell crashed with SIGTRAP in x_io_error() from _XIOError() from _XEventsQueued() from XPending() from gdk_check_xpending() ["Connection to xwayland lost"]
/var/log/history.log section as per above post ** Attachment added: "part-history.log" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1505409/+attachment/4962744/+files/part-history.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1505409 Title: gnome-shell crashed with SIGTRAP in x_io_error() from _XIOError() from _XEventsQueued() from XPending() from gdk_check_xpending() ["Connection to xwayland lost"] To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1505409/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1721493] [NEW] thunderbird ui hopelessly corrupted (screenshot)
Public bug reported: With this version much of the thunderbird UI is unusable and corrupted, with massive redraw failures. This affects Xorg and Wayland sessions on nvidia, nouveau, intel and oss radeon. (When I finally reported it, it was on nvidia/xorg but wanted to stress it wasn't particular to that environment.) Reverting to previous version 1:52.2, which happened to be in my cache, works fine. I realise this is from artful-proposed/main and what am I doing there? The reason being, the version is artful/main is still on thunderbird 45. Until now the proposed builds have been fine. Screenshot attached. Resize the window and the chaos is quite animated. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: thunderbird 1:52.4.0+build1-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-14.15-generic 4.13.4 Uname: Linux 4.13.0-14-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia AddonCompatCheckDisabled: False ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: rachel 1809 F pulseaudio /dev/snd/controlC2: rachel 1809 F pulseaudio /dev/snd/controlC0: rachel 1809 F pulseaudio BuildID: 20171003222123 Channel: Unavailable CurrentDesktop: GNOME Date: Thu Oct 5 10:31:06 2017 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2017-07-30 (66 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) IpRoute: default via 192.168.1.254 dev eno1 proto static metric 100 169.254.0.0/16 dev eno1 scope link metric 1000 192.168.1.0/24 dev eno1 proto kernel scope link src 192.168.1.109 metric 100 Locales: extensions.sqlite corrupt or missing PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=52.4.0/20171003222123 (In use) RunningIncompatibleAddons: False SourcePackage: thunderbird Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to artful on 2017-08-22 (43 days ago) dmi.bios.date: 11/26/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1005 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z87I-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1005:bd11/26/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87I-PRO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS ** Affects: thunderbird (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug artful package-from-proposed ** Attachment added: "Screenshot from 2017-10-05 10-30-50.png" https://bugs.launchpad.net/bugs/1721493/+attachment/4962674/+files/Screenshot%20from%202017-10-05%2010-30-50.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1721493 Title: thunderbird ui hopelessly corrupted (screenshot) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1721493/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1720760] [NEW] Under Xorg app windows unscaled until gnome tweaks is launched.
Public bug reported: Today I learned from omgubuntu how to reset my gnome/ubuntu desktop settings (dconf reset -f /), and thought I'd do it, seeing as I had upgraded from a Zesty install at an earlier stage of 17.10's pre-release period, and further customised as time went on in the normal way of things. Some of the issues I've been having have apparently disappeared, which is good. This has not: On login with this 4K screen (and after bug #1717272 was fixed), desktop scale setting is set to 200% as I'd wish, and gnome-shell is scaled correctly. But the text of the Rubbish Bin icon on the desktop, and the windows of, for instance, Files, Software and Terminal, are all unscaled. (See screenshot.) When I launch gnome-tweaks, all these other windows immediately become correctly scaled, and everything remains properly scaled for the remainder of the session. Note, I haven't *changed* any settings in gnome-tweaks, all I did was *launch* it. (See second screenshot, which it looks like I need to attach to a reply as I can't see how to attach two screenshots to the OP.) (In between the two screenshots I also launched the main settings control panel. Launching this doesn't do anything AFAIK, I was just checking what the default desktop scaling was - and it was 200%, though this might not be a dconf thing and thus survives from before the reset.) This seems only to affect Gnome/Ubuntu sessions under Xorg, not Wayland. I was experiencing this before the dconf reset on two machines, one with nvidia graphics, one with intel iris graphics, so this one, at least, seems not to be an nvidia-related issue. It looks like some value relating to scaling, that affects many apps, is not properly set in Xorg until gnome-tweaks is launched and presumably explicitly refreshes things. Note, a comment on an earlier bug report https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1713323/comments/12 asked about whether launching gnome tweaks changed anything. For me at the time it didn't, so I said so and it seemed unrelated to *that* issue, but I am now seeing it relating to this issue, so wanted to report it clearly as a separate thing - especially seeing as that issue was eventually marked a duplicate of another which has been resolved, whereas this issue still clearly is not resolved. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: mutter 3.26.0+20170925~ea214fb-1ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 2 11:05:35 2017 InstallationDate: Installed on 2017-07-30 (63 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: mutter UpgradeStatus: Upgraded to artful on 2017-08-22 (40 days ago) ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful ** Attachment added: "Screenshot from 2017-10-02 11-02-23.png" https://bugs.launchpad.net/bugs/1720760/+attachment/4960364/+files/Screenshot%20from%202017-10-02%2011-02-23.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1720760 Title: Under Xorg app windows unscaled until gnome tweaks is launched. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1720760/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1720760] Re: Under Xorg app windows unscaled until gnome tweaks is launched.
Attaching second screenshot referred to in original post... ** Attachment added: "Screenshot from 2017-10-02 11-04-16.png" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1720760/+attachment/4960369/+files/Screenshot%20from%202017-10-02%2011-04-16.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1720760 Title: Under Xorg app windows unscaled until gnome tweaks is launched. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1720760/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1720149] Re: gnome-shell segv on wake from display or system sleep
ok, same symptoms occurred with the default theme. So after all it looks like the shell theme has nothing to do with it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1720149 Title: gnome-shell segv on wake from display or system sleep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1720149/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1720149] Re: gnome-shell segv on wake from display or system sleep
well I spoke too soon. Crash occurred with the locally 'built' arc theme. Slightly different though in that this time it *did* hang the system. But it started with the same segv message logged. So back to the default+Ambiance theme to test that for longer. Problem with trying to prove a negative. You can only say "Well it hasn't crashed *yet*" until it does. Damn, I liked that theme. :-( (Of course, now to try to prove the same negative about the default theme... I kind of hope it fails too now so it's not my favourite theme's fault.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1720149 Title: gnome-shell segv on wake from display or system sleep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1720149/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1720149] Re: gnome-shell segv on wake from display or system sleep
arc-theme package uninstalled and instead arc gtk & shell themes installed manually as directed in its github page via autogen. This appears not to be triggering the crash. even though the autogen doesn't know any gnome > 3.22. It may be that similarly rebuilding the arc-theme package for a gnome 3.26 environment would fix it, but I still don't really have a theory as to why it should break, let alone only on nvidia. There's no binaries in it afaik. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1720149 Title: gnome-shell segv on wake from display or system sleep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1720149/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1720149] Re: gnome-shell segv on wake from display or system sleep
I think my modeset=1 test earlier was invalid; I don't think that change was ever applied. It *did* get applied just now with a routine dist- upgrade, which included an update to console-setup, which forced update- initramfs. And then the system was unbootable except via the recovery system. syslog is full of crashes like this in rapid succession: Sep 30 13:33:38 fleetfoot kernel: [ 117.641448] [ cut here ] Sep 30 13:33:38 fleetfoot kernel: [ 117.641467] WARNING: CPU: 0 PID: 221 at /build/linux-s_bACt/linux-4.13.0/drivers/gpu/drm/drm_atomic_helper.c:1682 drm_atomic_helper_commit_hw_done+0x99/0xa0 [drm_kms_helper] Sep 30 13:33:38 fleetfoot kernel: [ 117.641468] Modules linked in: rfcomm hid_magicmouse hidp cmac bnep nls_iso8859_1 nvidia_uvm(POE) hid_apple joydev input_leds hid_generic ath3k btusb btrtl btbcm btintel bluetooth snd_usb_audio snd_usbmidi_lib usbhid hid ecdh_generic snd_hda_codec_hdmi eeepc_wmi asus_wmi cmdlinepart intel_spi_platform intel_rapl intel_spi spi_nor wmi_bmof sparse_keymap mtd x86_pkg_temp_thermal intel_powerclamp kvm_intel kvm snd_hda_codec_realtek snd_hda_codec_generic irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel snd_hda_intel snd_hda_codec pcbc snd_hda_core snd_hwdep arc4 snd_pcm snd_seq_midi ath9k aesni_intel snd_seq_midi_event ath9k_common ath9k_hw snd_rawmidi aes_x86_64 crypto_simd snd_seq glue_helper cryptd ath intel_cstate snd_seq_device intel_rapl_perf mac80211 snd_timer cfg80211 snd soundcore Sep 30 13:33:38 fleetfoot kernel: [ 117.641496] mei_me mei shpchp lpc_ich wmi mac_hid nct6775 hwmon_vid coretemp parport_pc ppdev lp parport ip_tables x_tables autofs4 nvidia_drm(POE) nvidia_modeset(POE) i915 nvidia(POE) i2c_algo_bit drm_kms_helper e1000e syscopyarea sysfillrect sysimgblt fb_sys_fops ahci ptp drm libahci pps_core video Sep 30 13:33:38 fleetfoot kernel: [ 117.641507] CPU: 0 PID: 221 Comm: kworker/u16:6 Tainted: PW OE 4.13.0-12-generic #13-Ubuntu Sep 30 13:33:38 fleetfoot kernel: [ 117.641507] Hardware name: ASUS All Series/Z87I-PRO, BIOS 1005 11/26/2014 Sep 30 13:33:38 fleetfoot kernel: [ 117.641511] Workqueue: events_unbound commit_work [drm_kms_helper] Sep 30 13:33:38 fleetfoot kernel: [ 117.641512] task: 970a91cec5c0 task.stack: b72901e5c000 Sep 30 13:33:38 fleetfoot kernel: [ 117.641515] RIP: 0010:drm_atomic_helper_commit_hw_done+0x99/0xa0 [drm_kms_helper] Sep 30 13:33:38 fleetfoot kernel: [ 117.641515] RSP: 0018:b72901e5fdb8 EFLAGS: 00010286 Sep 30 13:33:38 fleetfoot kernel: [ 117.641516] RAX: 970a8ff8b008 RBX: 0004 RCX: 970a9ca0c000 Sep 30 13:33:38 fleetfoot kernel: [ 117.641516] RDX: 970a8dce1400 RSI: 0001 RDI: 970a93a56c08 Sep 30 13:33:38 fleetfoot kernel: [ 117.641517] RBP: b72901e5fdd8 R08: 970aafa12398 R09: 0018 Sep 30 13:33:38 fleetfoot kernel: [ 117.641517] R10: b72901e5fd88 R11: 0372 R12: 0001 Sep 30 13:33:38 fleetfoot kernel: [ 117.641518] R13: 970a97780b40 R14: 970a93a56c08 R15: 970a93a56c08 Sep 30 13:33:38 fleetfoot kernel: [ 117.641518] FS: () GS:970aafa0() knlGS: Sep 30 13:33:38 fleetfoot kernel: [ 117.641519] CS: 0010 DS: ES: CR0: 80050033 Sep 30 13:33:38 fleetfoot kernel: [ 117.641519] CR2: 7fa55cd3a010 CR3: 0003ff609000 CR4: 001406f0 Sep 30 13:33:38 fleetfoot kernel: [ 117.641520] DR0: DR1: DR2: Sep 30 13:33:38 fleetfoot kernel: [ 117.641520] DR3: DR6: fffe0ff0 DR7: 0400 Sep 30 13:33:38 fleetfoot kernel: [ 117.641521] Call Trace: Sep 30 13:33:38 fleetfoot kernel: [ 117.641524] nvidia_drm_atomic_helper_commit_tail+0x10e/0x170 [nvidia_drm] Sep 30 13:33:38 fleetfoot kernel: [ 117.641527] commit_tail+0x3f/0x60 [drm_kms_helper] Sep 30 13:33:38 fleetfoot kernel: [ 117.641530] commit_work+0x12/0x20 [drm_kms_helper] Sep 30 13:33:38 fleetfoot kernel: [ 117.641532] process_one_work+0x1e7/0x410 Sep 30 13:33:38 fleetfoot kernel: [ 117.641533] worker_thread+0x4a/0x410 Sep 30 13:33:38 fleetfoot kernel: [ 117.641534] kthread+0x125/0x140 Sep 30 13:33:38 fleetfoot kernel: [ 117.641535] ? process_one_work+0x410/0x410 Sep 30 13:33:38 fleetfoot kernel: [ 117.641536] ? kthread_create_on_node+0x70/0x70 Sep 30 13:33:38 fleetfoot kernel: [ 117.641538] ret_from_fork+0x25/0x30 Sep 30 13:33:38 fleetfoot kernel: [ 117.641538] Code: 7d 30 e8 db b8 2c fa 48 89 df c6 07 00 0f 1f 40 00 49 8b 4e 08 41 83 c4 01 44 39 a1 38 03 00 00 7f 98 5b 41 5c 41 5d 41 5e 5d c3 <0f> ff eb c0 f3 c3 90 0f 1f 44 00 00 48 8b 4f 08 8b 81 38 03 00 Sep 30 13:33:38 fleetfoot kernel: [ 117.641552] ---[ end trace ab364b2a1fae43bb ]--- Sep 30 13:33:39 fleetfoot kernel: [ 117.974932] [ cut here ] However that's probably offtopic here, and just speaks to nvidia kms
[Bug 1720149] Re: gnome-shell segv on wake from display or system sleep
It may be the Arc shell theme, in interaction with nVidia: I was unable to reproduce the problem on the Macbook Pro using Xorg gnome session, and that still with the Arc shell theme. Both a short (few minutes) and long (greater than one hour) display sleeps tested. I was also unable to reproduce it on the nVidia-equipped desktop with the Default shell theme selected, on either short or long display sleep. needs-root-rights is still set to yes in this configuration (ie: the same as tested yesterday evening except for switching back to default themes.) I don't know how a theme can cause a segfault, it's just image assets and css. But I'll leave it on Default for now to see if the issue does after all recur. I'll also go back to modeset=1 but needs-root-rights left unset, and wait and see. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1720149 Title: gnome-shell segv on wake from display or system sleep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1720149/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1720149] Re: gnome-shell segv on wake from display or system sleep
That would appear to be very different from what we're trying to report here: 1. It's not hanging. It's presumably exiting, forcing a logout, and it all happens before the monitors are awake enough to show a picture. We're not in a hung state at any point. 2. It's not only suspend, it's wake from only display-sleep too. The rest of the computer isn't suspended or sleeping in any manner. It *also* failed, in the exact same manner, on wake from suspend, but this suggests the problem isn't in suspending or waking from that, but just about the display sleep/wake. 3. It's only affecting nVidia (or at least, for me, it seems not to be also affecting Intel, but I haven't tried such a long sleep under Intel/Xorg and I should - tomorrow, as I'm in bed now). I bet there's no problem. :-) 4. It appears to be only affecting Xorg, although of course with nVidia there's too much else broken when trying to force it to use Wayland (which is, after all, not enabled by default for these reasons). Certainly no such problems on Intel/Wayland which *does* regularly get to sleep for long periods of time between uses, and I've never seen it hang on wake. (Hardware of my Intel graphics machine is an Early 2015 13" Retina Macbook Pro. This specifically is a Broadwell Core-i5 with Intel Iris 6100, and I've only attempted to use it on its own screen, not with any external screens connected. Generally, it runs Linux brilliantly, as far as I've so far tried, and is very happy with Wayland. All hardware just works OOTB.) I'm not using the default ubuntu session (with or without wayland) on either machine, but the GNOME session - wayland on the intel, xorg on the nvidia. Basically just because I wanted vanilla dash-to-dock. I'm not running many extensions, dash to dock, a wallpaper changer, ubuntu appindicators (which isn't working on Xorg on either machine btw, to be the subject of another bug report when I get a round tuit)... and nothing else that I remember right now while I'm not at it. Come to think of it, I do need to test using the default gnome shell theme rather than Arc's. I will tomorrow. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1720149 Title: gnome-shell segv on wake from display or system sleep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1720149/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1720149] Re: gnome-shell segv on wake from display or system sleep
neither change made a difference in the end. the needs-root-rights change (instead of, not as well as, modeset) didn't help either, after a long sleep. Why instead-of not as-well-as? Because the manpage for Xwrapper.config said that its default setting of 'auto' turns needs-root-rights off is kms is enabled and on if it's enabled. So i daresay setting it directly is superfluous, it's controlled by enabling modeset or not. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1720149 Title: gnome-shell segv on wake from display or system sleep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1720149/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1720149] Re: gnome-shell segv on wake from display or system sleep
... and the answer is no. After a longer display-sleep i woke it up to find myself back at the login prompt. Definitely that and not the lock screen. This may in part be related to long-term issues I have with this monitor. Early-revision Dell P2715Q 4K monitors have known firmware- related issues with waking from sleep. It has phases. Sometimes it just works. Sometimes it's narcoleptic, taking the form of just going straight back to sleep after an attempted wake. And sometimes it wakes thinking it's just a 1440p monitor, and I don't notice until I get some text on the screen and think 'that doesn't look right'. That's what happened this time, and I think only happens after a longer sleep. Generally the fix in this instance is to switch the monitor off and on again, and it comes on secure in its identity as a 4K monitor. But as I switched it off, the session I'd just logged into again was again logged out. So I'm guessing Xorg/nVidia/Gnome between them are seeing a *change* in the monitor configuration attached to the computer. I would say it's still a bug that its response to that is to bug out, rather than shape itself around the new reality, but I don't know if that's just something we'll need Wayland working to deal with more gracefully. syslog covering the wake-up attached, FWIW (it's quite busy). There's one segfault in there looking similar to those I saw earlier, from the moment of trying to wake it up: Sep 29 13:59:01 fleetfoot kernel: [15526.672810] gnome-shell[26357]: segfault at 2c ip 7fb47879d434 sp 7ffd919279a8 error 4 in libmutter-1.so.0.0.0[7fb4786ff000+14] However grepping for it in syslog I also see it happened twice earlier today too, while I was away from the computer: Sep 29 10:59:10 fleetfoot kernel: [ 4736.585186] gnome-shell[1892]: segfault at 2c ip 7fb1e3549434 sp 7fff343753c8 error 4 in libmutter-1.so.0.0.0[7fb1e34ab000+14] Sep 29 12:26:32 fleetfoot kernel: [ 9977.733747] gnome-shell[21408]: segfault at 2c ip 7f9d9f7be434 sp 7ffd5a80ce88 error 4 in libmutter-1.so.0.0.0[7f9d9f72+14] It's possible this was triggered by the cat stepping on the keyboard or trackpad. I can also see there *wasn't* any segfault at the time I switched the monitor off and on again, and yet I was still bumped out of my gnome session. I dare suggest that even if the monitor's dodgy and even if the driver is having issues, gnome-shell should not segfault, but fail more gracefully. (Or is it libmutter that's segfaulting?) I'm going to try enabling that 'needs root rights' setting. ** Attachment added: "syslog.wakeup" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1720149/+attachment/4958680/+files/syslog.wakeup -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1720149 Title: gnome-shell segv on wake from display or system sleep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1720149/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1720331] [NEW] Whoopsie continually relaunching
Public bug reported: Today for the first time, and coincidentally looking for a different setting, I went to the Settings->Privacy dialogue. I was also (coincidentally for a different reason, relating to #1720149) already tailing /var/log/syslog to a terminal. Immediately on opening that dialogue, the syslog tail flooded with whoopsie continually relaunching, causing enough work to raise the fan speeds. This is a representative section from towards the end of me letting it, before I killed the service, with some necessary viciousness. Specifically systemctl stop whoopsie (didn't stop it) systemctl disable whoopsie (didn't stop it) (find pid for whoopsie's root process and kill it) (that stopped it) Also for good measure ensured the automatic bug reporting option in the privacy settings dialog was set to manual, which I think was done anyway when I disabled whoopsie, though the dialog wasn't on top at the time for me to be sure. It had been set to automatic when I first opened the dialog. Snippet from syslog attached. It was just repeating this continually for several minutes before I stopped it. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: whoopsie 0.2.58 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CrashReports: 664:1000:119:0:2017-09-25 18:16:58.760134901 +0100:2017-09-25 18:16:58.760134901 +0100:/var/crash/_opt_google_chrome_chrome.1000.upload 640:1000:119:102847031:2017-09-27 20:28:45.352315425 +0100:2017-09-28 09:02:32.195212507 +0100:/var/crash/_usr_bin_gnome-shell.1000.crash 640:1000:119:34020328:2017-09-25 18:16:57.656132936 +0100:2017-09-25 18:16:58.760134901 +0100:/var/crash/_opt_google_chrome_chrome.1000.crash 600:111:119:0:2017-09-25 18:16:59.348145502 +0100:2017-09-25 18:16:59.348145502 +0100:/var/crash/_opt_google_chrome_chrome.1000.uploaded CurrentDesktop: GNOME Date: Fri Sep 29 10:00:34 2017 InstallationDate: Installed on 2017-07-30 (60 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) RelatedPackageVersions: apport-noui N/A SourcePackage: whoopsie UpgradeStatus: Upgraded to artful on 2017-08-22 (37 days ago) ** Affects: whoopsie (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful autoreport-false ** Attachment added: "syslog-snippet" https://bugs.launchpad.net/bugs/1720331/+attachment/4958534/+files/syslog-snippet -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1720331 Title: Whoopsie continually relaunching To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1720331/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1720149] Re: gnome-shell segv on wake from display or system sleep
I tried the modeset change first, as that one we'd presumably prefer to be true anyway one day, whereas giving stuff root that isn't supposed to have root never feels right. :-) It worked. I left it to display sleep for a couple of minutes and on wake I came right back to the desktop. (I don't have screen lock on, so no password needed.) In case the length of sleep makes a difference (don't know why it should) I'll leave it to cut in normally when I go out for a couple of hours shortly, and see what happens when I get back. NB: I had tried enabling this before as part of forcing nvidia to use wayland. I disabled it because (in Wayland) it was terribly sluggish and in the logs I was seeing nvidia_drm panic and presumably relaunch almost continuously, on the 4.13 kernel. Nouveau was also failing on that kernel, even worse, giving just a black screen. That was when I decided to try harder to have a working Xorg system again. :-) But I hadn't tried turning modeset on and still use xorg; I didn't know there was a point in doing so. It seems to be happy. BTW FWIW rachel@fleetfoot:~$ apt-cache policy nvidia-384 nvidia-384: Installed: 384.90-0ubuntu0~gpu17.10.1 Candidate: 384.90-0ubuntu0~gpu17.10.1 Version table: *** 384.90-0ubuntu0~gpu17.10.1 500 500 http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu artful/main amd64 Packages 100 /var/lib/dpkg/status -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1720149 Title: gnome-shell segv on wake from display or system sleep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1720149/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1720149] Re: gnome-shell segv on wake from display or system sleep
I can't reproduce this in Xorg on my non-nvidia machine (on which I normally run Wayland because I can). It appears to be nvidia specific. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1720149 Title: gnome-shell segv on wake from display or system sleep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1720149/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1720149] [NEW] gnome-shell segv on wake from display or system sleep
Public bug reported: The observable symptom is that if I go away and let the computer go either to display sleep or suspend, when I come back and try to wake it up again, I find myself, after sliding up the lock screen, at the gdm login screen. I'm logged out, and logging in gives me a fresh new session. Anything I had open in the previous session is lost. (I'm getting used to saving stuff before I step away from the computer!) The only trace I've been able to find is that in /var/log/syslog I see a line like: Sep 28 14:38:44 fleetfoot kernel: [10621.432586] gnome-shell[1863]: segfault at 2c ip 7f6200e82434 sp 7ffc46f981c8 error 4 in libmutter-1.so.0.0.0[7f6200de4000+14] This happens at the time of attempted wake, not the time of going to sleep. It's preceded by a lot of activity from gdm-x-session that I'm not sure is indicating any error, just the process of waking up. I will attach a portion of syslog surrounding the whole event in the hope it helps. (In fact attaching the whole current syslog file - it has two such events occuring in it, first display sleep/wake at 09:02 this morning, and secondly (because I was experimenting) a suspend-wake at 14:38 this afternoon. This is only affecting Xorg sessions, and may possibly only be affecting where nvidia is in use, I'm not sure about that. But the fact it occurs on display wake alone, not needing the system itself to have suspended (I was trying suspend to see if it *avoided* the problem, which it doesn't), does point the finger in that direction I guess. But ultimately I'm guessing it's gnome-shell itself segfaulting that's causing the login session to end? Not observed on my Wayland system. This is not new as of the current version of gnome-shell but I think it is relatively recent. Now my hackintosh partition is wrecked by a failed upgrade to High Sierra I'm using my Linux system more in earnest than before, so I'm hitting this often enough for it to provoke a bug report (and much of the time, to just turn all auto suspend/display-sleep off and instead shut down the computer when I'm leaving it for any length of time). The ubuntu bug reporter is not picking this up by itself, so I presume a crash report of the sort that uses is not being saved. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.0-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Sep 28 14:41:07 2017 DisplayManager: gdm3 InstallationDate: Installed on 2017-07-30 (59 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: gnome-shell UpgradeStatus: Upgraded to artful on 2017-08-22 (37 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful ** Attachment added: "syslog" https://bugs.launchpad.net/bugs/1720149/+attachment/4958094/+files/syslog -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1720149 Title: gnome-shell segv on wake from display or system sleep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1720149/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
