[Bug 1777378] Re: [nvidia] GDM no longer presents GUI login Ubuntu 18.04
Thanks for searching. It appears this is now a problem in the nvidia driver only, if not a hardware/cable problem. So reassigning... ** Package changed: gdm3 (Ubuntu) => nvidia-graphics-drivers-390 (Ubuntu) ** No longer affects: mutter (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1777378 Title: [nvidia] GDM no longer presents GUI login Ubuntu 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1777378/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1777378] Re: [nvidia] GDM no longer presents GUI login Ubuntu 18.04
Just did a locate for all xorg.conf: sudo locate -i xorg.conf /usr/share/X11/xorg.conf.d /usr/share/X11/xorg.conf.d/10-amdgpu.conf /usr/share/X11/xorg.conf.d/10-nvidia.conf /usr/share/X11/xorg.conf.d/10-quirks.conf /usr/share/X11/xorg.conf.d/10-radeon.conf /usr/share/X11/xorg.conf.d/40-libinput.conf /usr/share/X11/xorg.conf.d/70-wacom.conf /usr/share/doc/xserver-xorg-video-intel/xorg.conf /usr/share/man/man5/xorg.conf.5.gz /usr/share/man/man5/xorg.conf.d.5.gz The only file named xorg.conf is attached. ** Attachment added: "xorg.conf" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1777378/+attachment/5154458/+files/xorg.conf -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1777378 Title: [nvidia] GDM no longer presents GUI login Ubuntu 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1777378/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1777378] Re: [nvidia] GDM no longer presents GUI login Ubuntu 18.04
It appears the login screen processes are all running fine (gdms.txt). The only remaining problem I can see is that the nvidia driver can't find your monitor: Jun 19 21:46:18 little-black-box /usr/lib/gdm3/gdm-x-session[1441]: (II) NVIDIA(0): Validated MetaModes: Jun 19 21:46:18 little-black-box /usr/lib/gdm3/gdm-x-session[1441]: (II) NVIDIA(0): "NULL" Jun 19 21:46:18 little-black-box /usr/lib/gdm3/gdm-x-session[1441]: (II) NVIDIA(0): Virtual screen size determined to be 640 x 480 Jun 19 21:46:18 little-black-box /usr/lib/gdm3/gdm-x-session[1441]: (WW) NVIDIA(0): Unable to get display device for DPI computation. Jun 19 21:46:18 little-black-box /usr/lib/gdm3/gdm-x-session[1441]: (==) NVIDIA(0): DPI set to (75, 75); computed from built-in default Please attach a copy of this file if you can find one of them: /etc/X11/xorg.conf /etc/xorg.conf /usr/etc/X11/xorg.conf /usr/lib/X11/xorg.conf Please also try unplugging/replugging the monitor, or replacing the monitor cable. And if you have a different monitor then please also try that. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1777378 Title: [nvidia] GDM no longer presents GUI login Ubuntu 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1777378/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1777378] Re: [nvidia] GDM no longer presents GUI login Ubuntu 18.04
The machine in question has a single monitor with a resolution of 1920x1080. And newjournal.txt for 4 from #34. ** Attachment added: "newjournal.txt" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1777378/+attachment/5154437/+files/newjournal.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1777378 Title: [nvidia] GDM no longer presents GUI login Ubuntu 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1777378/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1777378] Re: [nvidia] GDM no longer presents GUI login Ubuntu 18.04
For 1 from #34. ** Attachment added: "gdms.txt" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1777378/+attachment/5154435/+files/gdms.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1777378 Title: [nvidia] GDM no longer presents GUI login Ubuntu 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1777378/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1777378] Re: [nvidia] GDM no longer presents GUI login Ubuntu 18.04
For 2 from #34. ** Attachment added: "dpkgl.txt" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1777378/+attachment/5154436/+files/dpkgl.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1777378 Title: [nvidia] GDM no longer presents GUI login Ubuntu 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1777378/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1752091] Re: gvfsd-metadata[1703]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed
Has this bug been fixed? I encountered this when I trying to install the latest version of 18.04. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1752091 Title: gvfsd-metadata[1703]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1752091/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1777378] Re: [nvidia] GDM no longer presents GUI login Ubuntu 18.04
Thanks for doing all that. If there are no crash files then I wonder is everything actually running despite not being visible? 1. From ssh, please run: ps auxw | grep gdm > gdms.txt and send us the output. 2. Please also send the output of: dpkg -l > dpkgl.txt 3. How many monitors (and what resolution) are connected? 4. Now you've replaced the nvidia driver please again run: journalctl -b > newjournal.txt and send the result. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1777378 Title: [nvidia] GDM no longer presents GUI login Ubuntu 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1777378/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1777318] Re: GDM3 completely ignore pam_group
** Description changed: + https://gitlab.gnome.org/GNOME/gdm/issues/393 + + --- + I'm using some ubuntu machine in a network where users data came from LDAP. I've setup PAM/NSS to use LDAP account and all works as expected. Apart assigning local group to users, via pam_group. I've added to /etc/pam.d/common-auth (to the end): - authoptionalpam_group.so + authoptionalpam_group.so and added to /etc/security/group.conf: - *; *; %sysops; Al-2400; adm,sudo,admin,dip,cdrom,floppy,plugdev,lpadmin,sambashare + *; *; %sysops; Al-2400; adm,sudo,admin,dip,cdrom,floppy,plugdev,lpadmin,sambashare but groups are not added as expected, i'm not in 'admin' or 'sudo' group (eg, i cannot do administrative tasks) and if i fire up a terminal: - gaio@dora:~$ id - uid=1000(gaio) gid=1001(casa) gruppi=1001(casa),1000(sysops),1003(bbs) + gaio@dora:~$ id + uid=1000(gaio) gid=1001(casa) gruppi=1001(casa),1000(sysops),1003(bbs) note that group assignment works, eg: - gaio@dora:~$ ssh localhost - gaio@localhost's password: - Welcome to Ubuntu 18.04 LTS (GNU/Linux 4.15.0-23-generic x86_64) + gaio@dora:~$ ssh localhost + gaio@localhost's password: + Welcome to Ubuntu 18.04 LTS (GNU/Linux 4.15.0-23-generic x86_64) - * Documentation: https://help.ubuntu.com - * Management: https://landscape.canonical.com - * Support:https://ubuntu.com/advantage + * Documentation: https://help.ubuntu.com + * Management: https://landscape.canonical.com + * Support:https://ubuntu.com/advantage + * Canonical Livepatch is available for installation. + - Reduce system reboots and improve kernel security. Activate at: + https://ubuntu.com/livepatch - * Canonical Livepatch is available for installation. -- Reduce system reboots and improve kernel security. Activate at: - https://ubuntu.com/livepatch + 0 pacchetti possono essere aggiornati. + 0 sono aggiornamenti di sicurezza. - 0 pacchetti possono essere aggiornati. - 0 sono aggiornamenti di sicurezza. - - Last login: Sun Jun 17 14:36:50 2018 from 127.0.0.1 - gaio@dora:~$ id - uid=1000(gaio) gid=1001(casa) gruppi=1001(casa),4(adm),24(cdrom),25(floppy),27(sudo),30(dip),46(plugdev),116(lpadmin),126(sambashare),1000(sysops),1003(bbs) + Last login: Sun Jun 17 14:36:50 2018 from 127.0.0.1 + gaio@dora:~$ id + uid=1000(gaio) gid=1001(casa) gruppi=1001(casa),4(adm),24(cdrom),25(floppy),27(sudo),30(dip),46(plugdev),116(lpadmin),126(sambashare),1000(sysops),1003(bbs) Previous LTS (16.04) with LightDM works as expected. This bug seems very similar to #880104 . Thanks. ** Changed in: gdm3 (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1777318 Title: GDM3 completely ignore pam_group To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1777318/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1756379] Re: Delay start of gnome-software service
Unassigning myself I mean. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1756379 Title: Delay start of gnome-software service To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1756379/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1756379] Re: Delay start of gnome-software service
Assigning myself as there doesn't seem to be a clear decision on if we want this or not (I have not strong opinion either way). ** Changed in: gnome-software (Ubuntu) Assignee: Robert Ancell (robert-ancell) => (unassigned) ** Changed in: gnome-software (Ubuntu Bionic) Assignee: Robert Ancell (robert-ancell) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1756379 Title: Delay start of gnome-software service To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1756379/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1631499] Re: package libglib2.0-0:i386 2.48.1-1~ubuntu16.04.1 failed to install/upgrade: dependency problems - leaving triggers unprocessed
This, libglib2.0-0:i386 2.48.1-1~ubuntu16.04.1, is not a package from the official Ubuntu archive so there is nothing we, the developers of Ubuntu, can do about it. ** Changed in: glib2.0 (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1631499 Title: package libglib2.0-0:i386 2.48.1-1~ubuntu16.04.1 failed to install/upgrade: dependency problems - leaving triggers unprocessed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1631499/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1652734] Re: installing kernel 4.9.0 and this crash happened installing package libglib2.0-0:amd64 2.48.1-1~ubuntu16.04.1 [origin: Ubuntu] failed to install/upgrade: dependency problems - leaving
You'll need to bring this up with the developers of elementary OS. ** Changed in: glib2.0 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1652734 Title: installing kernel 4.9.0 and this crash happened installing package libglib2.0-0:amd64 2.48.1-1~ubuntu16.04.1 [origin: Ubuntu] failed to install/upgrade: dependency problems - leaving triggers unprocessed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1652734/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1725121] Re: package desktop-file-utils 0.23-1ubuntu3 failed to install/upgrade: dependency problems - leaving triggers unprocessed
*** This bug is a duplicate of bug 1769954 *** https://bugs.launchpad.net/bugs/1769954 ** This bug has been marked a duplicate of bug 1769954 package desktop-file-utils 0.23-1ubuntu3 failed to install/upgrade: dependency problems - leaving triggers unprocessed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to desktop-file-utils in Ubuntu. https://bugs.launchpad.net/bugs/1725121 Title: package desktop-file-utils 0.23-1ubuntu3 failed to install/upgrade: dependency problems - leaving triggers unprocessed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/desktop-file-utils/+bug/1725121/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1777318] Re: GDM3 completely ignore pam_group
Done. https://gitlab.gnome.org/GNOME/gdm/issues/393 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1777318 Title: GDM3 completely ignore pam_group To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1777318/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1777674] Re: Ubuntu 18.04 hangs at "kvm: exiting hardware virtualization" on AMD servers
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.17 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.18-rc1 ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => High ** Changed in: linux (Ubuntu Bionic) Status: New => Incomplete ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1777674 Title: Ubuntu 18.04 hangs at "kvm: exiting hardware virtualization" on AMD servers To manage notifications about this bug go to: https://bugs.launchpad.net/dellserver/+bug/1777674/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1777378] Re: [nvidia] GDM no longer presents GUI login Ubuntu 18.04
As per #32: 1 Purged all nvidia packages. 2 apt autoremoved, autocleaned. 3 Removed ppa:graphics-drivers (added for a previous attempt to fix this bug) 4 Apt update 5 Apt Installed nvidia-driver-390 6 Rebooted machine Still no graphical login. ALso, strangely, no new or updated files in /var/crash. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1777378 Title: [nvidia] GDM no longer presents GUI login Ubuntu 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1777378/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1773334] Re: Ubuntu 18.04 mounted network shares not appearing under devices in file manager
Reported upstream: https://gitlab.gnome.org/GNOME/glib/issues/1424 ** Package changed: udisks2 (Ubuntu) => glib2.0 (Ubuntu) ** Changed in: glib2.0 (Ubuntu) Importance: Undecided => High ** Changed in: glib2.0 (Ubuntu) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1773334 Title: Ubuntu 18.04 mounted network shares not appearing under devices in file manager To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1773334/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1773334] [NEW] Ubuntu 18.04 mounted network shares not appearing under devices in file manager
You have been subscribed to a public bug: Apologies if this is not the correct package to file this bug/regression against. On my 18.04 desktop installs (Gnome shell and Ubuntu Mate) when mounting network shares (SMB and NFS) they no longer appear under Devices in file manager (Nautilus or Caja), the mounts do succeed and are accessible at their mount points. In 16.04 and 17.10 these mounts appeared under Devices (Screenshot of mounted network shares on Ubuntu Mate 17.10 attached) I am using the following code to mount NFS shares `sudo mount.nfs 192.168.2.123:/mnt/freenas-data1/photobackup /media/philroche/photobackup` and for SMB shares `sudo mount.cifs //192.168.2.123/photobackup /media/philroche/photobackup` Is this a bug/regression, or perhaps it is an intentional change? I did ask this on IRC in #ubuntu and askubuntu.com but no reply. Expected behaviour: I expected the mounted network shares to appear under Devices in File manager Actual behaviour: Mounting network shares does succeed as expected but does not appear under Devices in File manager as it did in previous releases. Requested details: Description:Ubuntu 18.04 LTS Release:18.04 udisks2: Installed: 2.7.6-3 Candidate: 2.7.6-3 Version table: *** 2.7.6-3 500 500 http://ie.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status ** Affects: glib2.0 (Ubuntu) Importance: High Status: Triaged -- Ubuntu 18.04 mounted network shares not appearing under devices in file manager https://bugs.launchpad.net/bugs/1773334 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1777674] Re: Ubuntu 18.04 hangs at "kvm: exiting hardware virtualization" on AMD servers
Logs where the hang is not seen: [ 75.448494] kvm: exiting hardware virtualization [ 76.187482] reboot: Restarting system [ 76.191663] reboot: machine restart [ 76.197621] ACPI MEMORY or I/O RESET_REG. The last 3 lines are not seen when the hang is observed. ** Attachment added: "console-logs-no-failure-case" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777674/+attachment/5154317/+files/console-logs-no-failure.txt ** Also affects: dellserver Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1777674 Title: Ubuntu 18.04 hangs at "kvm: exiting hardware virtualization" on AMD servers To manage notifications about this bug go to: https://bugs.launchpad.net/dellserver/+bug/1777674/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1777674] [NEW] Ubuntu 18.04 hangs at "kvm: exiting hardware virtualization" on AMD servers
Public bug reported: Ubuntu 18.04 hangs at "kvm: exiting hardware virtualization" on AMD servers when under graceful reboot stress for 12hrs. * This hand is observed only when Onboard SATA DVD Drive is connected. * Not seen with Ubuntu 16.04.4 (HWE kernel v4.13) * Seen with Ubuntu 18.04 (4.15.0-23-generic, 4.15.0-20-generic) Steps: Setup a DellEMC AMD server with Onboard DVD Drive, install Ubuntu 18.04 and start reboot stress After a few reboots, observe that the machine hangs at "kvm: exiting hardware virtualization" and does not proceed with reboot cycles. Only physical reset helps in continuing the reboot test. ** Affects: dellserver Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Attachment added: "console-logs" https://bugs.launchpad.net/bugs/1777674/+attachment/5154314/+files/console-logs.txt ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1777674 Title: Ubuntu 18.04 hangs at "kvm: exiting hardware virtualization" on AMD servers To manage notifications about this bug go to: https://bugs.launchpad.net/dellserver/+bug/1777674/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1777654] [NEW] openvpn connection with secret is broken
Public bug reported: when connecting an openvpn 2.4 server via ovpn configuration with a secret, journalctl shows this: gnome-shell[5063]: JS ERROR: error while reading VPN plugin output keyfile: GLib.KeyFileError: Key file does not have key “Title” in group “VPN Plugin UI” _showNewStyleDialog@resource:///org/gnome/shell/ui/components/networkAgent.js:515:40 wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22 _readStdoutNewStyle/<@resource:///org/gnome/shell/ui/components/networkAgent.js:489:17 2018-06-19 15:39:44 example.com NetworkManager[966]: [1529415584.4116] vpn-connection[0x560e3577e840,b65547a8-8a347-1c21-c747-5296902abc6e,"Notebook",0]: Failed to request VPN secrets #3: No agents were available for this request. 2018-06-19 15:39:44 example.com NetworkManager[966]: [1529415584.4126] vpn-connection[0x560e3577e840,b65547a8-8a347-1c21-c747-5296902abc6e,"Notebook",0]: VPN plugin: state changed: stopped (6) 2018-06-19 15:39:44 example.com NetworkManager[966]: [1529415584.4131] vpn-connection[0x560e3577e840,b65547a8-8a347-1c21-c747-5296902abc6e,"Notebook",0]: VPN service disappeared ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager-openvpn 1.8.2-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: Tue Jun 19 15:33:29 2018 InstallationDate: Installed on 2018-06-19 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: network-manager-openvpn UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: network-manager-openvpn (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to network-manager-openvpn in Ubuntu. https://bugs.launchpad.net/bugs/1777654 Title: openvpn connection with secret is broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1777654/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1767564] Re: Ubuntu 18.04 Workspaces only change on primary monitor
Throwing in my two bits, I have multiple monitors - they are my desktop. When I switch desktops I expect both to switch together. I see that Jim expected each to be independent - I could live with that too, but it's not the behavior I expect. My situation is a desktop with multiple monitors, not a laptop with an external monitor; that probably contributes to the way I look at it. Linux 4.15.0-23-generic x86_64 Ubuntu 18.04 LTS (Bionic Beaver) == /sys/devices/pci:00/:00:01.0/:01:00.0 == modalias : pci:v10DEd1CB2sv10DEsd11BDbc03sc00i00 vendor : NVIDIA Corporation model: GP107GL [Quadro P600] driver : nvidia-driver-390 - distro non-free recommended driver : xserver-xorg-video-nouveau - distro free builtin -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1767564 Title: Ubuntu 18.04 Workspaces only change on primary monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1767564/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1717807] Re: When the menu contains too elements, the bottom ones does not appear
I also experienced this bug with a different clipboard history indicator. Also, these kind of applications (those that keep a history of clipboard contents for easy retrieval) are relatively common, so I disagree with the "low" priority categorization of this bug, which literally makes any indicator that is higher than your given screen height useless. As the sole purpose of this plugin is to display and allow interaction with indicators, such an issue seems fairly important. :-) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1717807 Title: When the menu contains too elements, the bottom ones does not appear To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1717807/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1777579] Re: 18.04 Dekstop LTS DNS behavior (systemd-resolved)
** Package changed: ubuntu => systemd (Ubuntu) ** Tags added: bionic -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1777579 Title: 18.04 Dekstop LTS DNS behavior (systemd-resolved) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1777579/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1777579] [NEW] 18.04 Dekstop LTS DNS behavior (systemd-resolved)
You have been subscribed to a public bug: Hi, I am using te latest Ubuntu Mate Desktop 18.04 LTS release and have issues getting local DNS to work. In my network I maintain a central router instance that povides DHCP and DNS successfully over many years. The DHCP assigns a valid address and correct DNS information to my above mentioned network client. However DNS resolution does not work for DNS records maintained in my router for my local network. See here: (local DNS server on .3.1) uho@Asus:~/Schreibtisch$ systemd-resolve --status Global DNSSEC NTA: 10.in-addr.arpa 16.172.in-addr.arpa 168.192.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19.172.in-addr.arpa 20.172.in-addr.arpa 21.172.in-addr.arpa 22.172.in-addr.arpa 23.172.in-addr.arpa 24.172.in-addr.arpa 25.172.in-addr.arpa 26.172.in-addr.arpa 27.172.in-addr.arpa 28.172.in-addr.arpa 29.172.in-addr.arpa 30.172.in-addr.arpa 31.172.in-addr.arpa corp d.f.ip6.arpa home internal intranet lan local private test Link 2 (wlp2s0) Current Scopes: DNS LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no DNS Servers: 192.168.3.1 uho@Asus:~/Schreibtisch$ uho@Asus:~/Schreibtisch$ nslookup filou Server: 127.0.0.53 Address:127.0.0.53#53 ** server can't find filou: SERVFAIL uho@Asus:~/Schreibtisch$ nslookup filou 192.168.3.1 Server: 192.168.3.1 Address:192.168.3.1#53 Non-authoritative answer: Name: filou Address: 192.168.3.10 uho@Asus:~/Schreibtisch$ nslookup 192.168.3.10 10.3.168.192.in-addr.arpa name = filou. Authoritative answers can be found from: uho@Asus:~/Schreibtisch$ The example above shows that DNS forward lookup for "filou" does not work, only reverse lookup works. The same behavior with explicit DNS setting in network manager. Any idea what's wrong? To me this looks weirdly broken. BTW: Old school setting in /etc/resolv.conf works like a charm. BR Uwe ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- 18.04 Dekstop LTS DNS behavior (systemd-resolved) https://bugs.launchpad.net/bugs/1777579 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1775145] Re: Please merge gnome-shell 3.28.2 from Debian
** Changed in: gnome-shell (Ubuntu Bionic) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Tags removed: rls-bb-incoming -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1775145 Title: Please merge gnome-shell 3.28.2 from Debian To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1775145/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1777099] Re: [backport] DRM devices opened by logind stay referenced indefinitely by PID 1
** Changed in: systemd (Ubuntu) Status: Triaged => In Progress ** Also affects: systemd (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu Bionic) Status: New => In Progress ** Changed in: systemd (Ubuntu Bionic) Importance: Undecided => High ** Changed in: systemd (Ubuntu Bionic) Assignee: (unassigned) => Alberto Milone (albertomilone) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1777099 Title: [backport] DRM devices opened by logind stay referenced indefinitely by PID 1 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1777099/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1760201] Re: ubuntu 18.04 GDM - missing icons and letters on login screen with nouveau + Wayland
I'd like to report that this issue is also being reproduced with nouveau on NVIDIA GF108. However, my dmesg does not seem to contain nouveau errors. dmesg sample containing nouveau (as above): [5.254956] nouveau :01:00.0: enabling device (0006 -> 0007) [5.255096] nouveau :01:00.0: NVIDIA GF108 (0c1480a1) [5.285074] nouveau :01:00.0: bios: version 70.08.a8.00.2b [5.393498] nouveau :01:00.0: fb: 2048 MiB DDR3 [5.449440] nouveau :01:00.0: DRM: VRAM: 2048 MiB [5.449441] nouveau :01:00.0: DRM: GART: 1048576 MiB [5.449444] nouveau :01:00.0: DRM: TMDS table version 2.0 [5.449454] nouveau :01:00.0: DRM: DCB version 4.0 [5.449455] nouveau :01:00.0: DRM: DCB outp 00: 02010300 [5.449457] nouveau :01:00.0: DRM: DCB conn 00: [5.451120] nouveau :01:00.0: DRM: MM: using COPY0 for buffer copies [5.485363] nouveau :01:00.0: DRM: allocated 1024x768 fb: 0x6, bo 10a8d043 [5.488176] nouveau :01:00.0: fb0: nouveaufb frame buffer device [5.512017] [drm] Initialized nouveau 1.3.1 20120801 for :01:00.0 on minor 1 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1760201 Title: ubuntu 18.04 GDM - missing icons and letters on login screen with nouveau + Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1760201/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1712866] Re: icons from qt applications disappear after screen lock/sleep
This happening to me in 18.04 Bionic: the icons disappear after lock/sleep and do not appear on login. Restarting with Alt+F2 + r makes them reappear. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-appindicator in 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 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1777514] Re: gnome-shell crashed with SIGABRT (corrupted double-linked list) in free() from ... _mesa_glsl_release_builtin_functions() from _mesa_destroy_shader_compiler_caches() from _mesa_destr
Hmm, problem: https://errors.ubuntu.com/problem/c1f46d2d92c2be5d4c6d68c44ef0817ccea8ccab is not being deduplicated accurately by the robots at errors.ubuntu.com. 5 hours ago the stack trace was in Mesa as mentioned above. And now it's something different. So we must generalize this bug to match :S ** Summary changed: - gnome-shell crashed with SIGABRT (corrupted double-linked list) in free() from ... _mesa_glsl_release_builtin_functions() from _mesa_destroy_shader_compiler_caches() from _mesa_destroy_shader_compiler() from one_time_fini() from __run_exit_handlers() from exit() + gnome-shell crashed with SIGABRT (corrupted double-linked list) in free() ** No longer affects: mesa (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1777514 Title: gnome-shell crashed with SIGABRT (corrupted double-linked list) in free() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1777514/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1777514] Re: gnome-shell crashed with SIGABRT (corrupted double-linked list) in free() from ... _mesa_glsl_release_builtin_functions() from _mesa_destroy_shader_compiler_caches() from _mesa_destr
Not sure if this was the correct "corrupted double linked list" issue but if it is, it was happening under Wayland. Fresh install. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1777514 Title: gnome-shell crashed with SIGABRT (corrupted double-linked list) in free() from ... _mesa_glsl_release_builtin_functions() from _mesa_destroy_shader_compiler_caches() from _mesa_destroy_shader_compiler() from one_time_fini() from __run_exit_handlers() from exit() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1777514/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs