Re: [Desktop-packages] [Bug 1764087] Re: Wrongly boots into low graphics mode
Hello Chris, Writing to you direct rather than through the bug - hope you don't mind. I too had my first failure today using the new kernel, manifesting itself in the same way. It's getting a bit tiresome now and I have little faith in it being corrected. I have spent quite a bit of time researching the issue and trying a few things out to no avail. There are other things needing my attention just now. So, it was always in my plans to install 18.04 LTS at some stage. Rather than do a fresh install of 16.04 LTS which I had thought was a way of hopefully overcoming the problem, I may as well go for 18.04 LTS. I just need to plan things out so that I manage to safely backup my documents and all my settings (I have very low vision and my settings are important to me). The planning and preparation in itself will take some time. When I get round to it I will let you know how things go. Best Regards Dave On 24 April 2018 at 22:29, Chris Perry wrote: > Hi Dave, I'm using the new kernel (4.13.0-39-generic) and I still get > the error (though my laptop did start up once without the error). > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1764087 > > Title: > Wrongly boots into low graphics mode > > Status in xorg package in Ubuntu: > New > > Bug description: > Description: Ubuntu 16.04.4 LTS > Release: 16.04 > > Lenovo T410 with VGA compatible controller [0300]: Intel Corporation > Core Processor Integrated Graphics Controller [8086:0046] (rev 02) > > Booting from latest kernel ThinkPad-T410 4.13.0-38-generic > #43~16.04.1-Ubuntu SMP Wed Mar 14 17:48:43 UTC 2018 x86_64 x86_64 > x86_64 GNU/Linux goes into low graphics mode and also effects wi-fi > connection insofar as it does not connect to my router. > > Whereas booting from 4.13.0-37-generic #42~16.04.1-Ubuntu SMP Wed Mar > 7 16:03:28 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux works most of the > time but occasionally has the same effects. > > I have had to submit this report after booting from 4.13.0.37 in order > to submit bug. > > ProblemType: Bug > DistroRelease: Ubuntu 16.04 > Package: xorg 1:7.7+13ubuntu3 > ProcVersionSignature: Ubuntu 4.13.0-37.42~16.04.1-generic 4.13.13 > Uname: Linux 4.13.0-37-generic x86_64 > .tmp.unity_support_test.0: > > ApportVersion: 2.20.1-0ubuntu2.15 > Architecture: amd64 > CompizPlugins: No value set for `/apps/compiz-1/general/ > screen0/options/active_plugins' > CompositorRunning: compiz > CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' > CompositorUnredirectFSW: true > CurrentDesktop: Unity > Date: Sun Apr 15 10:40:31 2018 > DistUpgraded: Fresh install > DistroCodename: xenial > DistroVariant: ubuntu > ExtraDebuggingInterest: Yes, if not too technical > GraphicsCard: >Intel Corporation Core Processor Integrated Graphics Controller > [8086:0046] (rev 02) (prog-if 00 [VGA controller]) > Subsystem: Lenovo Core Processor Integrated Graphics Controller > [17aa:215a] > InstallationDate: Installed on 2016-09-24 (567 days ago) > InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 > (20160719) > MachineType: LENOVO 2519Y11 > ProcEnviron: >LANGUAGE=en_GB:en >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_GB.UTF-8 >SHELL=/bin/bash > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-37-generic > root=UUID=58d362c2-ed1e-479b-84f5-e5d8a782b08f ro quiet splash > vt.handoff=7 > SourcePackage: xorg > Symptom: display > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 02/14/2013 > dmi.bios.vendor: LENOVO > dmi.bios.version: 6IET85WW (1.45 ) > dmi.board.name: 2519Y11 > dmi.board.vendor: LENOVO > dmi.board.version: Not Available > dmi.chassis.asset.tag: No Asset Information > dmi.chassis.type: 10 > dmi.chassis.vendor: LENOVO > dmi.chassis.version: Not Available > dmi.modalias: dmi:bvnLENOVO:bvr6IET85WW(1.45):bd02/14/2013:svnLENOVO: > pn2519Y11:pvrThinkPadT410:rvnLENOVO:rn2519Y11:rvrNotAvailable:cvnLENOVO: > ct10:cvrNotAvailable: > dmi.product.family: ThinkPad T410 > dmi.product.name: 2519Y11 > dmi.product.version: ThinkPad T410 > dmi.sys.vendor: LENOVO > version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 > version.ia32-libs: ia32-libs N/A > version.libdrm2: libdrm2 2.4.83-1~16.04.1 > version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1 > version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A > version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1 > version.xserver-xorg-core: xserver-xorg-core N/A > version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A > version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A > version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A > version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A > xserver.bootTime: Sun Apr 15 08:52:
[Desktop-packages] [Bug 1757321] Re: udisks2 must depend on libblockdev-crypto2 and libblockdev-mdraid2 instead of suggests [Can't mount encrypted USB drive after upgrade to bionic]
seanlano, if you boot the live cd and then run "dpkg -l libblockdev- crypto2 | cat", what do you see? How about "dpkg -l udisks2 | cat"? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to udisks2 in Ubuntu. https://bugs.launchpad.net/bugs/1757321 Title: udisks2 must depend on libblockdev-crypto2 and libblockdev-mdraid2 instead of suggests [Can't mount encrypted USB drive after upgrade to bionic] Status in udisks2 package in Ubuntu: Fix Released Bug description: after upgrading to bionic, attempts to mount an encrypted USB drive fail with the error "function bd_crypto_luks_open_blob called but not implemented" Installing libblockdev-crypto2 and libblockdev-crypto-dev and rebooting appears to have fixed it, but should that be necessary? or at least better documented? (https://www.distrowatch.com/weekly.php?issue=20171113 is the only reference I could find on the error) [Workaround] 1. Install libblockdev-crypto2 2. Restart udisks: $ systemctl restart udisks2 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: udisks2 2.7.6-2ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: GNOME CustomUdevRuleFiles: 90-xhc_sleep.rules 70-snap.core.rules Date: Tue Mar 20 20:28:39 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2015-08-21 (942 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150819) MachineType: Apple Inc. MacBookPro11,4 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic.efi.signed root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash vt.handoff=1 SourcePackage: udisks2 UpgradeStatus: Upgraded to bionic on 2018-03-20 (0 days ago) dmi.bios.date: 06/05/2015 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP114.88Z.0172.B04.1506051511 dmi.board.name: Mac-06F11FD93F0323C5 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,4 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-06F11FD93F0323C5 dmi.modalias: dmi:bvnAppleInc.:bvrMBP114.88Z.0172.B04.1506051511:bd06/05/2015:svnAppleInc.:pnMacBookPro11,4:pvr1.0:rvnAppleInc.:rnMac-06F11FD93F0323C5:rvrMacBookPro11,4:cvnAppleInc.:ct9:cvrMac-06F11FD93F0323C5: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro11,4 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1757321/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1766799] Re: gnome-control-center (ERROR) ../shell/cc-panel-list.c → 926 → cc_panel_list_set_active_panel → assertion failed → (data != NULL)
** Summary changed: - /usr/bin/gnome-control-center:ERROR:../shell/cc-panel-list.c:926:cc_panel_list_set_active_panel: assertion failed: (data != NULL) + gnome-control-center (ERROR) ../shell/cc-panel-list.c → 926 → cc_panel_list_set_active_panel → assertion failed → (data != NULL) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1766799 Title: gnome-control-center (ERROR) ../shell/cc-panel-list.c → 926 → cc_panel_list_set_active_panel → assertion failed → (data != NULL) Status in gnome-control-center package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-control-center. This problem was most recently seen with package version 1:3.28.1-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/73835fe215683e2f5f85df231eb2750a57e96c65 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1766799/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1762984] Re: DNS resolving not working due to wrong entry in resolv.conf
More on this: After a fresh reboot but also after wake from suspend I have to set the DNS server in /etc/resolv.conf manually to get DNS resolving working. This is the output of ``systemd-resolve --status`` before manual changes: root@thettop:~# 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 4 (virbr0-nic) Current Scopes: none LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no Link 3 (virbr0) Current Scopes: none LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no Link 2 (wlp1s0) Current Scopes: DNS LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no DNS Servers: 192.168.0.1 DNS Domain: local And this is the content of /etc/resolv.conf before any manual changes: thet@thettop:~$ more /etc/resolv.conf # This file is managed by man:systemd-resolved(8). Do not edit. # # This is a dynamic resolv.conf file for connecting local clients to the # internal DNS stub resolver of systemd-resolved. This file lists all # configured search domains. # # Run "systemd-resolve --status" to see details about the uplink DNS servers # currently in use. # # Third party programs must not access this file directly, but only through the # symlink at /etc/resolv.conf. To manage man:resolv.conf(5) in a different way, # replace this symlink by a static file or a different symlink. # # See man:systemd-resolved.service(8) for details about the supported modes of # operation for /etc/resolv.conf. nameserver 127.0.0.53 search local -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1762984 Title: DNS resolving not working due to wrong entry in resolv.conf Status in network-manager package in Ubuntu: New Bug description: In my ``/etc/resolv.conf`` I have the entry: ``` nameserver 127.0.0.53 ``` I'm connected to the network via WIFI. My IP is ``192.168.0.31`` The network-manager applet shows me automatic DNS configuration and a DNS server of 192.0.0.1, which is correct. Changing DNS configuration in the network-manager applet to manual and editing it there doesn't work either. I have to edit the resolv.conf file in order to get DNS resolving work. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 11 11:51:58 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-04-09 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) IpRoute: default via 192.168.0.1 dev wlp1s0 proto dhcp metric 20600 169.254.0.0/16 dev wlp1s0 scope link metric 1000 192.168.0.0/24 dev wlp1s0 proto kernel scope link src 192.168.0.31 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMP TIMESTAMP-REALAUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE NSACIAGCHQ5 f8431fbb-6f3c-4848-bcc4-4449012df3f7 wifi 1523440039 Mi 11 Apr 2018 11:47:19 CEST yes 0 no /org/freedesktop/NetworkManager/Settings/2 yes wlp1s0 activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- welanseppaf2f9fd1-2a81-4e2c-95e5-3f4e9a9997b9 wifi
[Desktop-packages] [Bug 1766799] [NEW] gnome-control-center (ERROR) ../shell/cc-panel-list.c → 926 → cc_panel_list_set_active_panel → assertion failed → (data != NULL)
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-control-center. This problem was most recently seen with package version 1:3.28.1-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/73835fe215683e2f5f85df231eb2750a57e96c65 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1766799 Title: gnome-control-center (ERROR) ../shell/cc-panel-list.c → 926 → cc_panel_list_set_active_panel → assertion failed → (data != NULL) Status in gnome-control-center package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-control-center. This problem was most recently seen with package version 1:3.28.1-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/73835fe215683e2f5f85df231eb2750a57e96c65 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1766799/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1757321] Re: udisks2 must depend on libblockdev-crypto2 and libblockdev-mdraid2 instead of suggests [Can't mount encrypted USB drive after upgrade to bionic]
I just tried the Live CD daily build for Bionic, I still see the error "Error unlocking /dev/sdc1: Failed to activate device: Operation not permitted (udisks-error-quark, 0)" (see attached screenshot) when trying to unlock a LUKS external disk with the Disks program. This comes up regardless of if I enter the correct or incorrect password. ** Attachment added: "Screenshot from 2018-04-25 05-53-48.png" https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1757321/+attachment/5126894/+files/Screenshot%20from%202018-04-25%2005-53-48.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to udisks2 in Ubuntu. https://bugs.launchpad.net/bugs/1757321 Title: udisks2 must depend on libblockdev-crypto2 and libblockdev-mdraid2 instead of suggests [Can't mount encrypted USB drive after upgrade to bionic] Status in udisks2 package in Ubuntu: Fix Released Bug description: after upgrading to bionic, attempts to mount an encrypted USB drive fail with the error "function bd_crypto_luks_open_blob called but not implemented" Installing libblockdev-crypto2 and libblockdev-crypto-dev and rebooting appears to have fixed it, but should that be necessary? or at least better documented? (https://www.distrowatch.com/weekly.php?issue=20171113 is the only reference I could find on the error) [Workaround] 1. Install libblockdev-crypto2 2. Restart udisks: $ systemctl restart udisks2 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: udisks2 2.7.6-2ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: GNOME CustomUdevRuleFiles: 90-xhc_sleep.rules 70-snap.core.rules Date: Tue Mar 20 20:28:39 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2015-08-21 (942 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150819) MachineType: Apple Inc. MacBookPro11,4 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic.efi.signed root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash vt.handoff=1 SourcePackage: udisks2 UpgradeStatus: Upgraded to bionic on 2018-03-20 (0 days ago) dmi.bios.date: 06/05/2015 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP114.88Z.0172.B04.1506051511 dmi.board.name: Mac-06F11FD93F0323C5 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,4 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-06F11FD93F0323C5 dmi.modalias: dmi:bvnAppleInc.:bvrMBP114.88Z.0172.B04.1506051511:bd06/05/2015:svnAppleInc.:pnMacBookPro11,4:pvr1.0:rvnAppleInc.:rnMac-06F11FD93F0323C5:rvrMacBookPro11,4:cvnAppleInc.:ct9:cvrMac-06F11FD93F0323C5: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro11,4 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1757321/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1766775] [NEW] Notifications do not disappear
Public bug reported: I frequently have notifications that do not disappear after being shown. This is particularly prevalent with power management notifications. Most of the time when I wake my computer from suspend, I see the following notification at the top: "Automatic suspend - Computer will suspend very soon because of inactivity." that never goes away. Presumably, this was shown before my computer went to sleep, and should have disappeared but didn't. I have to either click on the notification, or click on the time to open the notification menu to get it to disappear. Occasionally, the same behaviour occurs with other, random notifications. This is a long-standing issue for me, that I'm just now getting around to reporting. I'm on 17.10, gnome-shell 3.26.2-0ubuntu0.1, and running the gnome-session (not Ubuntu). I don't know if the issue is present on Gnome 3.28, but plan to find out once 18.04 final is released. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1766775 Title: Notifications do not disappear Status in gnome-shell package in Ubuntu: New Bug description: I frequently have notifications that do not disappear after being shown. This is particularly prevalent with power management notifications. Most of the time when I wake my computer from suspend, I see the following notification at the top: "Automatic suspend - Computer will suspend very soon because of inactivity." that never goes away. Presumably, this was shown before my computer went to sleep, and should have disappeared but didn't. I have to either click on the notification, or click on the time to open the notification menu to get it to disappear. Occasionally, the same behaviour occurs with other, random notifications. This is a long-standing issue for me, that I'm just now getting around to reporting. I'm on 17.10, gnome-shell 3.26.2-0ubuntu0.1, and running the gnome-session (not Ubuntu). I don't know if the issue is present on Gnome 3.28, but plan to find out once 18.04 final is released. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1766775/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1749895] Re: Mouse & Keyboard completely unresponsive when starting a VM
[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1749895 Title: Mouse & Keyboard completely unresponsive when starting a VM Status in gnome-shell package in Ubuntu: Expired Status in mutter package in Ubuntu: Expired Bug description: Could be virt-manager or gnome-shell related. I was passing through 1 USB device that wasn't my main mouse or keyboard. Otherwise pretty normal configuration that I've used before. After the VM's bios screen, the whole system froze except the clock in the desktop menu bar/panel. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.2-0ubuntu0.1 Uname: Linux 4.15.1-041501-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Feb 15 23:47:02 2018 DisplayManager: gdm3 InstallationDate: Installed on 2017-10-27 (112 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1749895/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1749895] Re: Mouse & Keyboard completely unresponsive when starting a VM
[Expired for mutter (Ubuntu) because there has been no activity for 60 days.] ** Changed in: mutter (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1749895 Title: Mouse & Keyboard completely unresponsive when starting a VM Status in gnome-shell package in Ubuntu: Expired Status in mutter package in Ubuntu: Expired Bug description: Could be virt-manager or gnome-shell related. I was passing through 1 USB device that wasn't my main mouse or keyboard. Otherwise pretty normal configuration that I've used before. After the VM's bios screen, the whole system froze except the clock in the desktop menu bar/panel. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.2-0ubuntu0.1 Uname: Linux 4.15.1-041501-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Feb 15 23:47:02 2018 DisplayManager: gdm3 InstallationDate: Installed on 2017-10-27 (112 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1749895/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1742482] Re: Double-click doesn't open default application
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nautilus (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1742482 Title: Double-click doesn't open default application Status in nautilus package in Ubuntu: Confirmed Bug description: Ubuntu 18.04 Nautilus 1:3.26.0-0ubuntu1 Bluefish 2.2.10 When I open a .php file from a FTP server browsed with Nautilus, Chrome is opened instead of the default application Bluefish. Steps to reproduce: 1. Connect to an FTP server via Nautilus 2a. Double-click on a .php file: chrome opens and the file is downloaded 2b. Right click and select 'open with' and then Bluefish: the file is opened in bluefish as expected So, on the double-click from Nautilus the wrong app (chrome!) is opened even if the .php files are associated with bluefish. Thanks ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluefish 2.2.9-1 ProcVersionSignature: Ubuntu 4.14.0-15.18-generic 4.14.12 Uname: Linux 4.14.0-15-generic x86_64 ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jan 10 17:12:27 2018 ExecutablePath: /usr/bin/bluefish InstallationDate: Installed on 2015-12-07 (765 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: bluefish UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1742482/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1561278] Re: internal sound card not detected HP X2
alsa-info output: http://www.alsa- project.org/db/?f=12cbba27e12cc27ede2a9934df4f3a1ce12ff545 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1561278 Title: internal sound card not detected HP X2 Status in alsa-driver package in Ubuntu: Confirmed Bug description: HP Pavilion X2 - No sound card detected. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6 Uname: Linux 4.4.0-15-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Wed Mar 23 18:18:32 2016 InstallationDate: Installed on 2016-03-18 (5 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/11/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.04 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 813E dmi.board.vendor: HP dmi.board.version: 34.10 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.04:bd09/11/2015:svnHP:pnHPPavilionx2Detachable:pvrType1ProductConfigId:rvnHP:rn813E:rvr34.10:cvnHP:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion x2 Detachable dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1561278/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1561278] Re: internal sound card not detected HP X2
Have the same issue with Ubuntu 17.10 $ uname -a Linux raiaHPx2 4.13.0-39-generic #44-Ubuntu SMP Thu Apr 5 14:25:01 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux "aplay -l" gives the following $aplay -l List of PLAYBACK Hardware Devices card 0: Audio [Intel HDMI/DP LPE Audio], device 0: HdmiLpeAudio [Intel HDMI/DP LPE Audio] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: Audio [Intel HDMI/DP LPE Audio], device 1: HdmiLpeAudio [Intel HDMI/DP LPE Audio] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: Audio [Intel HDMI/DP LPE Audio], device 2: HdmiLpeAudio [Intel HDMI/DP LPE Audio] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: bytcrrt5640 [bytcr-rt5640], device 0: Baytrail Audio (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: bytcrrt5640 [bytcr-rt5640], device 1: Deep-Buffer Audio (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 Attempted to solve with following the directions here with dkms https://wiki.ubuntu.com/Audio/UpgradingAlsa/DKMS but did not fix the no sound issue. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1561278 Title: internal sound card not detected HP X2 Status in alsa-driver package in Ubuntu: Confirmed Bug description: HP Pavilion X2 - No sound card detected. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6 Uname: Linux 4.4.0-15-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Wed Mar 23 18:18:32 2016 InstallationDate: Installed on 2016-03-18 (5 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/11/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.04 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 813E dmi.board.vendor: HP dmi.board.version: 34.10 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.04:bd09/11/2015:svnHP:pnHPPavilionx2Detachable:pvrType1ProductConfigId:rvnHP:rn813E:rvr34.10:cvnHP:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion x2 Detachable dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1561278/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1766758] Re: Gnome software can uninstall some programs but not others
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: http://iso.qa.ubuntu.com/qatracker/reports/bugs/1766758 ** Tags added: iso-testing -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1766758 Title: Gnome software can uninstall some programs but not others Status in gnome-software package in Ubuntu: New Bug description: As seen in Gnome Software 3.28.1 within a daily build of Xubuntu 18.04 i386 downloaded 12hrs ago. I used the Gnome Software GUI to uninstall the games bundled with Xubuntu (Gnome Sudoku, Mines, and the cluster of games grouped as "SGT Puzzles Collection". Gnome Sudoku was uninstalled as expected, but both Mines and the puzzles collection disappeared from the "installed" list within Software while still remaining in the XFCE main menu and are still launchable. See attached screenshot. This is a different bug to the one listed as Bug #1563322, as that one refers to externally-sourced programs. Thanks, Ken. *** --- ApportVersion: 2.20.9-0ubuntu6 Architecture: i386 CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-24 (0 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release i386 (20180424) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-limba N/A gnome-software-plugin-snap3.28.1-0ubuntu4 Package: gnome-software 3.28.1-0ubuntu4 PackageArchitecture: i386 ProcVersionSignature: Ubuntu 4.15.0-19.20-generic 4.15.17 Tags: bionic Uname: Linux 4.15.0-19-generic i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1766758/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1766755] Re: gnome-shell crashed with signal 5 in _XIOError()
*** This bug is a duplicate of bug 1505409 *** https://bugs.launchpad.net/bugs/1505409 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1505409, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1766755/+attachment/5126799/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1766755/+attachment/5126801/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1766755/+attachment/5126804/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1766755/+attachment/5126805/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1766755/+attachment/5126806/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1766755/+attachment/5126807/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1766755/+attachment/5126808/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1505409 gnome-shell crashed with SIGTRAP in x_io_error() from _XIOError() from _XEventsQueued() from XPending() from gdk_check_xpending() ["Connection to xwayland lost"] ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1766755 Title: gnome-shell crashed with signal 5 in _XIOError() Status in gnome-shell package in Ubuntu: New Bug description: every time i start computer, this error occurse ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu4 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME-Greeter:GNOME Date: Tue Apr 24 19:13:59 2018 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2017-10-25 (181 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/false Signal: 5 SourcePackage: gnome-shell StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 _XIOError () from /usr/lib/x86_64-linux-gnu/libX11.so.6 _XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6 XPending () from /usr/lib/x86_64-linux-gnu/libX11.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 Title: gnome-shell crashed with signal 5 in _XIOError() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1766755/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1766758] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1766758/+attachment/5126828/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1766758 Title: Gnome software can uninstall some programs but not others Status in gnome-software package in Ubuntu: New Bug description: As seen in Gnome Software 3.28.1 within a daily build of Xubuntu 18.04 i386 downloaded 12hrs ago. I used the Gnome Software GUI to uninstall the games bundled with Xubuntu (Gnome Sudoku, Mines, and the cluster of games grouped as "SGT Puzzles Collection". Gnome Sudoku was uninstalled as expected, but both Mines and the puzzles collection disappeared from the "installed" list within Software while still remaining in the XFCE main menu and are still launchable. See attached screenshot. This is a different bug to the one listed as Bug #1563322, as that one refers to externally-sourced programs. Thanks, Ken. *** --- ApportVersion: 2.20.9-0ubuntu6 Architecture: i386 CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-24 (0 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release i386 (20180424) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-limba N/A gnome-software-plugin-snap3.28.1-0ubuntu4 Package: gnome-software 3.28.1-0ubuntu4 PackageArchitecture: i386 ProcVersionSignature: Ubuntu 4.15.0-19.20-generic 4.15.17 Tags: bionic Uname: Linux 4.15.0-19-generic i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1766758/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1766758] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1766758/+attachment/5126826/+files/Dependencies.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1766758 Title: Gnome software can uninstall some programs but not others Status in gnome-software package in Ubuntu: New Bug description: As seen in Gnome Software 3.28.1 within a daily build of Xubuntu 18.04 i386 downloaded 12hrs ago. I used the Gnome Software GUI to uninstall the games bundled with Xubuntu (Gnome Sudoku, Mines, and the cluster of games grouped as "SGT Puzzles Collection". Gnome Sudoku was uninstalled as expected, but both Mines and the puzzles collection disappeared from the "installed" list within Software while still remaining in the XFCE main menu and are still launchable. See attached screenshot. This is a different bug to the one listed as Bug #1563322, as that one refers to externally-sourced programs. Thanks, Ken. *** --- ApportVersion: 2.20.9-0ubuntu6 Architecture: i386 CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-24 (0 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release i386 (20180424) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-limba N/A gnome-software-plugin-snap3.28.1-0ubuntu4 Package: gnome-software 3.28.1-0ubuntu4 PackageArchitecture: i386 ProcVersionSignature: Ubuntu 4.15.0-19.20-generic 4.15.17 Tags: bionic Uname: Linux 4.15.0-19-generic i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1766758/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1766758] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1766758/+attachment/5126827/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1766758 Title: Gnome software can uninstall some programs but not others Status in gnome-software package in Ubuntu: New Bug description: As seen in Gnome Software 3.28.1 within a daily build of Xubuntu 18.04 i386 downloaded 12hrs ago. I used the Gnome Software GUI to uninstall the games bundled with Xubuntu (Gnome Sudoku, Mines, and the cluster of games grouped as "SGT Puzzles Collection". Gnome Sudoku was uninstalled as expected, but both Mines and the puzzles collection disappeared from the "installed" list within Software while still remaining in the XFCE main menu and are still launchable. See attached screenshot. This is a different bug to the one listed as Bug #1563322, as that one refers to externally-sourced programs. Thanks, Ken. *** --- ApportVersion: 2.20.9-0ubuntu6 Architecture: i386 CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-24 (0 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release i386 (20180424) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-limba N/A gnome-software-plugin-snap3.28.1-0ubuntu4 Package: gnome-software 3.28.1-0ubuntu4 PackageArchitecture: i386 ProcVersionSignature: Ubuntu 4.15.0-19.20-generic 4.15.17 Tags: bionic Uname: Linux 4.15.0-19-generic i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1766758/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1766758] Re: Gnome software can uninstall some programs but not others
...this was after having installed Xubuntu successfully, and rebooted. ** Tags added: apport-collected bionic ** Description changed: As seen in Gnome Software 3.28.1 within a daily build of Xubuntu 18.04 i386 downloaded 12hrs ago. I used the Gnome Software GUI to uninstall the games bundled with Xubuntu (Gnome Sudoku, Mines, and the cluster of games grouped as "SGT Puzzles Collection". Gnome Sudoku was uninstalled as expected, but both Mines and the puzzles collection disappeared from the "installed" list within Software while still remaining in the XFCE main menu and are still launchable. See attached screenshot. This is a different bug to the one listed as Bug #1563322, as that one refers to externally-sourced programs. Thanks, Ken. *** + --- + ApportVersion: 2.20.9-0ubuntu6 + Architecture: i386 + CurrentDesktop: XFCE + DistroRelease: Ubuntu 18.04 + InstallationDate: Installed on 2018-04-24 (0 days ago) + InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release i386 (20180424) + InstalledPlugins: + gnome-software-plugin-flatpak N/A + gnome-software-plugin-limba N/A + gnome-software-plugin-snap3.28.1-0ubuntu4 + Package: gnome-software 3.28.1-0ubuntu4 + PackageArchitecture: i386 + ProcVersionSignature: Ubuntu 4.15.0-19.20-generic 4.15.17 + Tags: bionic + Uname: Linux 4.15.0-19-generic i686 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1766758 Title: Gnome software can uninstall some programs but not others Status in gnome-software package in Ubuntu: New Bug description: As seen in Gnome Software 3.28.1 within a daily build of Xubuntu 18.04 i386 downloaded 12hrs ago. I used the Gnome Software GUI to uninstall the games bundled with Xubuntu (Gnome Sudoku, Mines, and the cluster of games grouped as "SGT Puzzles Collection". Gnome Sudoku was uninstalled as expected, but both Mines and the puzzles collection disappeared from the "installed" list within Software while still remaining in the XFCE main menu and are still launchable. See attached screenshot. This is a different bug to the one listed as Bug #1563322, as that one refers to externally-sourced programs. Thanks, Ken. *** --- ApportVersion: 2.20.9-0ubuntu6 Architecture: i386 CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-24 (0 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release i386 (20180424) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-limba N/A gnome-software-plugin-snap3.28.1-0ubuntu4 Package: gnome-software 3.28.1-0ubuntu4 PackageArchitecture: i386 ProcVersionSignature: Ubuntu 4.15.0-19.20-generic 4.15.17 Tags: bionic Uname: Linux 4.15.0-19-generic i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1766758/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1766758] [NEW] Gnome software can uninstall some programs but not others
Public bug reported: As seen in Gnome Software 3.28.1 within a daily build of Xubuntu 18.04 i386 downloaded 12hrs ago. I used the Gnome Software GUI to uninstall the games bundled with Xubuntu (Gnome Sudoku, Mines, and the cluster of games grouped as "SGT Puzzles Collection". Gnome Sudoku was uninstalled as expected, but both Mines and the puzzles collection disappeared from the "installed" list within Software while still remaining in the XFCE main menu and are still launchable. See attached screenshot. This is a different bug to the one listed as Bug #1563322, as that one refers to externally-sourced programs. Thanks, Ken. *** ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New ** Tags: xubuntu xubuntu-exp ** Attachment added: "gnome software cannot uninstall mines program.png" https://bugs.launchpad.net/bugs/1766758/+attachment/5126823/+files/gnome%20software%20cannot%20uninstall%20mines%20program.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1766758 Title: Gnome software can uninstall some programs but not others Status in gnome-software package in Ubuntu: New Bug description: As seen in Gnome Software 3.28.1 within a daily build of Xubuntu 18.04 i386 downloaded 12hrs ago. I used the Gnome Software GUI to uninstall the games bundled with Xubuntu (Gnome Sudoku, Mines, and the cluster of games grouped as "SGT Puzzles Collection". Gnome Sudoku was uninstalled as expected, but both Mines and the puzzles collection disappeared from the "installed" list within Software while still remaining in the XFCE main menu and are still launchable. See attached screenshot. This is a different bug to the one listed as Bug #1563322, as that one refers to externally-sourced programs. Thanks, Ken. *** To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1766758/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1747345] Re: Software Centre - initial dialogue box disappears by itself, and error message appears
** Changed in: gnome-software (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1747345 Title: Software Centre - initial dialogue box disappears by itself, and error message appears Status in gnome-software package in Ubuntu: Fix Released Bug description: Freshly-installed i386 version of Lubuntu daily build downloaded last night. I went into System Tools > Software, and was greeted with an initial welcome screen / dialogue box that read "Let's Go Shopping!" (among other bits I didn't get a chance to read, and it had an OK / Proceed button or similar). Before I had a chance to read all this or click the button, that window disappeared, leaving me with the main Software Centre interface, but with the error message "Sorry, something went wrong", along with an "X" to dismiss that message. This error message appeared directly beneath the All / Installed / Updates buttons at the top of the screen. At the time this happened, I was online via a solid mobile broadband (aka cellular broadband) connection. Thanks, Ken. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1747345/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1760078] Re: Double login required from suspend
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: http://iso.qa.ubuntu.com/qatracker/reports/bugs/1760078 ** Tags added: iso-testing -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1760078 Title: Double login required from suspend Status in lightdm package in Ubuntu: New Bug description: Following a suspend. Get unlock screen - which then gets me a desktop. Returned to unlock screen to enter password a second time. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: lightdm 1.25.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Mar 30 12:09:46 2018 InstallationDate: Installed on 2018-03-08 (21 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180306.1) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1760078/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1766733] Re: package gnome-accessibility-themes 3.18.0-2ubuntu1 failed to install/upgrade: package gnome-accessibility-themes is not ready for configuration cannot configure (c
Thank you for taking the time to report this bug and helping to make Ubuntu better. Reviewing your log files attached to this bug report it seems that a package failed to install due to a segmentation fault in the application being used for the package installation process. Unfortunately, this bug report isn't very useful in its current state and a crash report would be much more useful. Could you try recreating this issue by enabling apport to catch the crash report 'sudo service apport start force_start=1' and then trying to install the same package again? This process will create a new bug report so I am marking this one as Invalid. Thanks again for helping out! [This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.] ** Tags added: package-install-segfault ** Changed in: gnome-themes-standard (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-themes-standard in Ubuntu. https://bugs.launchpad.net/bugs/1766733 Title: package gnome-accessibility-themes 3.18.0-2ubuntu1 failed to install/upgrade: package gnome-accessibility-themes is not ready for configuration cannot configure (current status 'half-installed') Status in gnome-themes-standard package in Ubuntu: Invalid Bug description: d ProblemType: Package DistroRelease: Ubuntu 16.04 Package: gnome-accessibility-themes 3.18.0-2ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 Date: Tue Apr 24 19:14:23 2018 Dependencies: DuplicateSignature: package:gnome-accessibility-themes:3.18.0-2ubuntu1 Setting up avahi-utils (0.6.32~rc+dfsg-1ubuntu2.1) ... dpkg: error processing package gnome-accessibility-themes (--configure): package gnome-accessibility-themes is not ready for configuration ErrorMessage: package gnome-accessibility-themes is not ready for configuration cannot configure (current status 'half-installed') InstallationDate: Installed on 2018-04-24 (0 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: gnome-themes-standard Title: package gnome-accessibility-themes 3.18.0-2ubuntu1 failed to install/upgrade: package gnome-accessibility-themes is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-themes-standard/+bug/1766733/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1766747] Re: package apt-config-icons (not installed) failed to install/upgrade: dpkg-deb --control subprocess returned error exit status 127
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to appstream in Ubuntu. https://bugs.launchpad.net/bugs/1766747 Title: package apt-config-icons (not installed) failed to install/upgrade: dpkg-deb --control subprocess returned error exit status 127 Status in appstream package in Ubuntu: New Bug description: doesnt work ProblemType: Package DistroRelease: Ubuntu 18.04 Package: apt-config-icons (not installed) ProcVersionSignature: Ubuntu 4.15.0-19.20-generic 4.15.17 Uname: Linux 4.15.0-19-generic x86_64 ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 Date: Tue Apr 24 20:50:23 2018 DuplicateSignature: package:apt-config-icons:(not installed) Removing sessioninstaller (0.20+bzr150-0ubuntu4.1) ... dpkg-deb: error while loading shared libraries: libzstd.so.1: cannot open shared object file: No such file or directory dpkg: error processing archive /tmp/apt-dpkg-install-1Qdb18/0-appstream_0.12.0-3_amd64.deb (--unpack): dpkg-deb --control subprocess returned error exit status 127 ErrorMessage: dpkg-deb --control subprocess returned error exit status 127 Python3Details: /usr/bin/python3.6, Python 3.6.5rc1, python3-minimal, 3.6.4-1 PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6~beta1 SourcePackage: appstream Title: package apt-config-icons (not installed) failed to install/upgrade: dpkg-deb --control subprocess returned error exit status 127 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1766747/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1766747] [NEW] package apt-config-icons (not installed) failed to install/upgrade: dpkg-deb --control subprocess returned error exit status 127
Public bug reported: doesnt work ProblemType: Package DistroRelease: Ubuntu 18.04 Package: apt-config-icons (not installed) ProcVersionSignature: Ubuntu 4.15.0-19.20-generic 4.15.17 Uname: Linux 4.15.0-19-generic x86_64 ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 Date: Tue Apr 24 20:50:23 2018 DuplicateSignature: package:apt-config-icons:(not installed) Removing sessioninstaller (0.20+bzr150-0ubuntu4.1) ... dpkg-deb: error while loading shared libraries: libzstd.so.1: cannot open shared object file: No such file or directory dpkg: error processing archive /tmp/apt-dpkg-install-1Qdb18/0-appstream_0.12.0-3_amd64.deb (--unpack): dpkg-deb --control subprocess returned error exit status 127 ErrorMessage: dpkg-deb --control subprocess returned error exit status 127 Python3Details: /usr/bin/python3.6, Python 3.6.5rc1, python3-minimal, 3.6.4-1 PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6~beta1 SourcePackage: appstream Title: package apt-config-icons (not installed) failed to install/upgrade: dpkg-deb --control subprocess returned error exit status 127 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: appstream (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to appstream in Ubuntu. https://bugs.launchpad.net/bugs/1766747 Title: package apt-config-icons (not installed) failed to install/upgrade: dpkg-deb --control subprocess returned error exit status 127 Status in appstream package in Ubuntu: New Bug description: doesnt work ProblemType: Package DistroRelease: Ubuntu 18.04 Package: apt-config-icons (not installed) ProcVersionSignature: Ubuntu 4.15.0-19.20-generic 4.15.17 Uname: Linux 4.15.0-19-generic x86_64 ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 Date: Tue Apr 24 20:50:23 2018 DuplicateSignature: package:apt-config-icons:(not installed) Removing sessioninstaller (0.20+bzr150-0ubuntu4.1) ... dpkg-deb: error while loading shared libraries: libzstd.so.1: cannot open shared object file: No such file or directory dpkg: error processing archive /tmp/apt-dpkg-install-1Qdb18/0-appstream_0.12.0-3_amd64.deb (--unpack): dpkg-deb --control subprocess returned error exit status 127 ErrorMessage: dpkg-deb --control subprocess returned error exit status 127 Python3Details: /usr/bin/python3.6, Python 3.6.5rc1, python3-minimal, 3.6.4-1 PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6~beta1 SourcePackage: appstream Title: package apt-config-icons (not installed) failed to install/upgrade: dpkg-deb --control subprocess returned error exit status 127 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1766747/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1765556] Re: nvidia-prime needs a reboot to switch between dGPU/hGPU
Yes, same thing wit the latest version of Ubuntu 18.04 installed (Fresh install) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1765556 Title: nvidia-prime needs a reboot to switch between dGPU/hGPU Status in nvidia-prime package in Ubuntu: New Bug description: I previously used Ubuntu 16.04 and Nvidia 375 driver with a Nvidia Geforce 635M and Sandy Bridge i7. To switch between the 2 Optimus cards (Intel hybrid and Nvidia discrete), one had to go into nvidia- settings, switch, logoff, login back, and the change was applied. I now have a Nvidia Quadro M2000 and a Skylake Xeon which has some Sync/Mux feature (whatever does that mean) with the Nvidia 390 driver. First of all, installing nivida-prime doesn't install bbswitch-dkms. Then, once the GPU switch is made, it triggers update-initramfs, recompile the kernel modules, and one needs to reboot the system to get the GPU change. Even when we install bbswitch-dkms. So am I getting a wrong impression or is there something twisted here ? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nvidia-prime 0.8.7 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 19 19:20:01 2018 Dependencies: InstallationDate: Installed on 2018-04-08 (11 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180408) PackageArchitecture: all SourcePackage: nvidia-prime UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1765556/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1762952] Re: Alternative shortcut for layout switching Alt+Shift unexpectedly set by default
True. That's what the discussion I linked to in comment #6 is about, and there is a xorg-server patch in a PPA to address the issue. (Haven't tested it.) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1762952 Title: Alternative shortcut for layout switching Alt+Shift unexpectedly set by default Status in gnome-control-center package in Ubuntu: New Status in gnome-shell package in Ubuntu: Confirmed Bug description: Version: Ubuntu 18.04 Final Beta with default Gnome Shell included in 18.04 Steps to reproduce: 1. Define two keyboard input methods in Settings -> Region & Language -> Input Sources 2. Open several applications 3. Observe that application windows can be iterated with Alt + Tab 4. Once application window iteration was begun with Alt + Tab, try to iterate backwards with Alt + Shift + Tab. 5. Try to change keyboard input method switching hotkeys in Settings -> Region & Language -> Input Sources -> Options. 6. Observe that Keyboard shortcut for "Alternative switch to next source" is set to "Alt + Shift" and that keyboard shortcuts can only be changed in Settings -> Devices -> Keyboard -> Keyboard Shortcuts. 7. Observe that the shortcut for "Alternative switch to next source" is not available for configuration in Settings -> Devices -> Keyboard -> Keyboard Shortcuts. Actual state: * Performing step 4 does not select the previous app in application switcher but instead changes keyboard input method. Expected state: * The shortcut for "Alternative switch to next source" can be changed and / or deactivated in Settings -> Devices -> Keyboard -> Keyboard Shortcuts. Notes: * The above was working fine in Ubuntu 17.10. I assume "Alternative switch to next source" did not exist in that version of Gnome Shell. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1762952/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1748000] Re: Remove from the archive: this legacy driver is unmaintained upstream
It's the only driver that manages the thermal load correctly on the video card in my old HP laptop :( -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-304-updates in Ubuntu. https://bugs.launchpad.net/bugs/1748000 Title: Remove from the archive: this legacy driver is unmaintained upstream Status in nvidia-graphics-drivers-304 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-304-updates package in Ubuntu: Fix Released Bug description: This driver branch is now dead upstream, so it should be removed from bionic. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1748000/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 913958] Re: nautilus crashed with SIGABRT: nautilus_window_slot_get_current_uri, code should not be reached
Thank you for reporting this bug to Ubuntu. Ubuntu 12.04 (precise) reached end-of-life on April 28, 2017. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: nautilus (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/913958 Title: nautilus crashed with SIGABRT: nautilus_window_slot_get_current_uri, code should not be reached Status in nautilus package in Ubuntu: Incomplete Bug description: I was trying to open a new tab. If it's of any relevance, I have dropbox running. It's the first time I've seen this crash in the 3 or 4 days I've been using 12.04 alpha. ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: nautilus 1:3.2.1-2ubuntu6 [modified: usr/share/applications/nautilus-home.desktop] ProcVersionSignature: Ubuntu 3.2.0-8.14-generic 3.2.0 Uname: Linux 3.2.0-8-generic x86_64 ApportVersion: 1.90-0ubuntu1 Architecture: amd64 Date: Mon Jan 9 14:20:48 2012 ExecutablePath: /usr/bin/nautilus InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (2029.1) ProcCmdline: nautilus -n Signal: 6 SourcePackage: nautilus StacktraceTop: raise () from /lib/x86_64-linux-gnu/libc.so.6 abort () from /lib/x86_64-linux-gnu/libc.so.6 g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () ?? () Title: nautilus crashed with SIGABRT in raise() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/913958/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 827892] Re: nautilus crashed with SIGABRT in __kernel_vsyscall() on directory mounted by sftp
Thank you for reporting this bug to Ubuntu. Ubuntu 11.04 (natty) reached end-of-life on October 28, 2012. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: nautilus (Ubuntu) Status: Triaged => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/827892 Title: nautilus crashed with SIGABRT in __kernel_vsyscall() on directory mounted by sftp Status in Nautilus: Expired Status in nautilus package in Ubuntu: Incomplete Bug description: Hi, I had crash on a directory mounted by sftp on another Ubuntu 11.04 computer. ProblemType: Crash DistroRelease: Ubuntu 11.04 Package: nautilus 1:2.32.2.1-0ubuntu13 ProcVersionSignature: Ubuntu 2.6.38-10.46-generic 2.6.38.7 Uname: Linux 2.6.38-10-generic i686 Architecture: i386 Date: Wed Aug 17 11:06:23 2011 ExecutablePath: /usr/bin/nautilus InstallationMedia: Ubuntu-Netbook 10.04 "Lucid Lynx" - Release i386 (20100429.4) ProcCmdline: nautilus --sm-client-id 2a76b30e6-84b1-4373-9a4e-5ee34aabb9c4 --sm-client-state-file /home/username/.config/session-state/nautilus-1313487431.desktop ProcEnviron: LANGUAGE=fr_FR:en PATH=(custom, user) LANG=fr_FR.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: nautilus StacktraceTop: __kernel_vsyscall () raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 abort () at abort.c:92 g_assertion_message () from /lib/i386-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/i386-linux-gnu/libglib-2.0.so.0 Title: nautilus crashed with SIGABRT in __kernel_vsyscall() UpgradeStatus: Upgraded to natty on 2011-05-01 (107 days ago) UserGroups: adm admin cdrom dialout fuse lpadmin plugdev sambashare XsessionErrors: (xfce4-terminal:1978): Gdk-CRITICAL **: IA__gdk_window_get_window_type: assertion `GDK_IS_WINDOW (window)' failed To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/827892/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1765593] Re: Cannot restart synaptic if cancelled the first time
Can confirm issue has been fixed gnome-shell (3.28.1-0ubuntu2) bionic; urgency=medium [ Marco Trevisan (Treviño) ] * js-ui-Choose-some-actors-to-cache-on-the-GPU.patch: - Improve rendering of shell elements moving rendering to GPU (LP: #1744001) [ Jeremy Bicha ] * Cherry-pick polkitAgent-Guard-against-repeated-close-calls.patch: - Fix PolicyKit authorization prompt after cancelling once (LP: #1765353) -- Marco Trevisan (Treviño) Mon, 23 Apr 2018 15:29:28 -0500 ** Changed in: gnome-shell (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1765593 Title: Cannot restart synaptic if cancelled the first time Status in gnome-shell package in Ubuntu: Fix Released Bug description: To reproduce the bug: - click the Synaptic icon in Ubuntu-dock - when the password dialog appears, click Cancel - click the Synaptic icon in Ubuntu-dock Synaptic will not start It's possible to start Synaptic from the terminal ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell-extension-ubuntu-dock 0.9.1 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME Date: Fri Apr 20 07:08:47 2018 InstallationDate: Installed on 2018-04-01 (18 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180330) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1765593/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1762952] Re: Alternative shortcut for layout switching Alt+Shift unexpectedly set by default
By the way, the real, underlying problem is of course that overlapping shortcuts should be possible (like in Mac and Windows), which is caused by this XKB bug reported 14 years ago (and still active): https://bugs.freedesktop.org/show_bug.cgi?id=865 It is basically about activating shortcuts on keypress vs key release. ** Bug watch added: freedesktop.org Bugzilla #865 https://bugs.freedesktop.org/show_bug.cgi?id=865 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1762952 Title: Alternative shortcut for layout switching Alt+Shift unexpectedly set by default Status in gnome-control-center package in Ubuntu: New Status in gnome-shell package in Ubuntu: Confirmed Bug description: Version: Ubuntu 18.04 Final Beta with default Gnome Shell included in 18.04 Steps to reproduce: 1. Define two keyboard input methods in Settings -> Region & Language -> Input Sources 2. Open several applications 3. Observe that application windows can be iterated with Alt + Tab 4. Once application window iteration was begun with Alt + Tab, try to iterate backwards with Alt + Shift + Tab. 5. Try to change keyboard input method switching hotkeys in Settings -> Region & Language -> Input Sources -> Options. 6. Observe that Keyboard shortcut for "Alternative switch to next source" is set to "Alt + Shift" and that keyboard shortcuts can only be changed in Settings -> Devices -> Keyboard -> Keyboard Shortcuts. 7. Observe that the shortcut for "Alternative switch to next source" is not available for configuration in Settings -> Devices -> Keyboard -> Keyboard Shortcuts. Actual state: * Performing step 4 does not select the previous app in application switcher but instead changes keyboard input method. Expected state: * The shortcut for "Alternative switch to next source" can be changed and / or deactivated in Settings -> Devices -> Keyboard -> Keyboard Shortcuts. Notes: * The above was working fine in Ubuntu 17.10. I assume "Alternative switch to next source" did not exist in that version of Gnome Shell. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1762952/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1766331] Re: nautilus preference is not remembered
I can't reproduce this on Files 3.26.3-0ubuntu4 on Ubuntu 18.04. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1766331 Title: nautilus preference is not remembered Status in nautilus package in Ubuntu: New Bug description: Description: Ubuntu Bionic Beaver (development branch) Release: 18.04 apt-cache policy nautilus nautilus: Installed: 1:3.26.3-0ubuntu4 Candidate: 1:3.26.3-0ubuntu4 Version table: *** 1:3.26.3-0ubuntu4 500 500 http://mirror.math.princeton.edu/pub/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status nautilus -> Files -> Preferences -> Behaviour changes I make here fail to be remembered for example by default value of -> Behaviour -> Open Action -> is "Double click to open items" however when I choose "Single click to open items" then close nautilus and re-open nautilus that Preference change did not take This is also true for other Preference changes ... nautilus fails to retain Preference changes Importantly when I make same change using tool dconf-editor on a virgin box it correctly make the setting changes ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.3-0ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 23 14:51:39 2018 GsettingsChanges: InstallationDate: Installed on 2018-02-23 (58 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: dropbox 2015.10.28 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1766331/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1713034] Re: gnome-shell crashed with SIGABRT in _ip_get_path_for_wd() ["assertion failed: (wd >= 0)"]
** Changed in: glib Status: Unknown => Confirmed ** Changed in: glib Importance: Unknown => Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1713034 Title: gnome-shell crashed with SIGABRT in _ip_get_path_for_wd() ["assertion failed: (wd >= 0)"] Status in GLib: Confirmed Status in gnome-shell package in Ubuntu: Triaged Bug description: https://errors.ubuntu.com/problem/3554ed6882d41ea6b6fe921fbc9450c857b89eaa https://errors.ubuntu.com/problem/7d4e9fc521926903d3f796d9d01b38c242396745 --- ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.24.3-0ubuntu4 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 ApportVersion: 2.20.6-0ubuntu7 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Aug 25 12:05:50 2017 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2014-08-13 (1107 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140810) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: gnome-shell StacktraceTop: g_assertion_message () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: gnome-shell crashed with SIGABRT in g_assertion_message() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1713034/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1766575] Re: Drop libnss-myhostname recommends
gnome-control-center uses hostnamed via D-Bus to change the hostname. The documentation says to use libnss-myhostname. Good luck convincing the systemd maintainers to change their mind on this issue. https://www.freedesktop.org/wiki/Software/systemd/hostnamed/ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1766575 Title: Drop libnss-myhostname recommends Status in gnome-control-center package in Ubuntu: Fix Committed Status in gnome-control-center source package in Bionic: Fix Committed Bug description: gnome-control-center added a Recommends: libnss-myhostname years ago so that it was possible to easily change the hostname in the Details panel. That dependency no longer appears to be needed since we switched to systemd-resolved. Testing Done In both Debian Testing and Ubuntu 18.04 (Debian doesn't use systemd-resolved so seemed useful to try there too). sudo apt uninstall libnss-myhostname Restart Open the GNOME Settings app (gnome-control-center) In the left sidebar, click Devices Enter a different Device name in the block Open a terminal and verify that the hostname has been changed. In Debian, running `ping new-hostname` fails, but it works fine in Ubuntu. Other Info == There are concerns about having libnss-myhostname in the default install. See comment 5 at LP: #1741277. See also LP: #1162475 Note that /etc/hosts isn't updated regardless of whether libnss-myhostname is installed (I guess my bug description there was wrong but there was some kind of bug there.) Regression Potential To quote from the manpage: https://manpages.debian.org/unstable/nss-resolve "Note that systemd-resolved will synthesize DNS resource records in a few cases, for example for "localhost" and the current hostname, see systemd-resolved(8) for the full list. This duplicates the functionality of nss-myhostname(8), but it is still recommended (see examples below) to keep nss-myhostname configured in /etc/nsswitch.conf, to keep those names resolveable if systemd- resolved is not running." Ubuntu uses systemd-resolved by default and it's expected that users who don't want to use that will need to configure some things manually. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1766575/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1766733] [NEW] package gnome-accessibility-themes 3.18.0-2ubuntu1 failed to install/upgrade: package gnome-accessibility-themes is not ready for configuration cannot configure
Public bug reported: d ProblemType: Package DistroRelease: Ubuntu 16.04 Package: gnome-accessibility-themes 3.18.0-2ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 Date: Tue Apr 24 19:14:23 2018 Dependencies: DuplicateSignature: package:gnome-accessibility-themes:3.18.0-2ubuntu1 Setting up avahi-utils (0.6.32~rc+dfsg-1ubuntu2.1) ... dpkg: error processing package gnome-accessibility-themes (--configure): package gnome-accessibility-themes is not ready for configuration ErrorMessage: package gnome-accessibility-themes is not ready for configuration cannot configure (current status 'half-installed') InstallationDate: Installed on 2018-04-24 (0 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: gnome-themes-standard Title: package gnome-accessibility-themes 3.18.0-2ubuntu1 failed to install/upgrade: package gnome-accessibility-themes is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-themes-standard (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-themes-standard in Ubuntu. https://bugs.launchpad.net/bugs/1766733 Title: package gnome-accessibility-themes 3.18.0-2ubuntu1 failed to install/upgrade: package gnome-accessibility-themes is not ready for configuration cannot configure (current status 'half-installed') Status in gnome-themes-standard package in Ubuntu: New Bug description: d ProblemType: Package DistroRelease: Ubuntu 16.04 Package: gnome-accessibility-themes 3.18.0-2ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 Date: Tue Apr 24 19:14:23 2018 Dependencies: DuplicateSignature: package:gnome-accessibility-themes:3.18.0-2ubuntu1 Setting up avahi-utils (0.6.32~rc+dfsg-1ubuntu2.1) ... dpkg: error processing package gnome-accessibility-themes (--configure): package gnome-accessibility-themes is not ready for configuration ErrorMessage: package gnome-accessibility-themes is not ready for configuration cannot configure (current status 'half-installed') InstallationDate: Installed on 2018-04-24 (0 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: gnome-themes-standard Title: package gnome-accessibility-themes 3.18.0-2ubuntu1 failed to install/upgrade: package gnome-accessibility-themes is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-themes-standard/+bug/1766733/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1766733] Re: package gnome-accessibility-themes 3.18.0-2ubuntu1 failed to install/upgrade: package gnome-accessibility-themes is not ready for configuration cannot configure (c
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-themes-standard in Ubuntu. https://bugs.launchpad.net/bugs/1766733 Title: package gnome-accessibility-themes 3.18.0-2ubuntu1 failed to install/upgrade: package gnome-accessibility-themes is not ready for configuration cannot configure (current status 'half-installed') Status in gnome-themes-standard package in Ubuntu: New Bug description: d ProblemType: Package DistroRelease: Ubuntu 16.04 Package: gnome-accessibility-themes 3.18.0-2ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 Date: Tue Apr 24 19:14:23 2018 Dependencies: DuplicateSignature: package:gnome-accessibility-themes:3.18.0-2ubuntu1 Setting up avahi-utils (0.6.32~rc+dfsg-1ubuntu2.1) ... dpkg: error processing package gnome-accessibility-themes (--configure): package gnome-accessibility-themes is not ready for configuration ErrorMessage: package gnome-accessibility-themes is not ready for configuration cannot configure (current status 'half-installed') InstallationDate: Installed on 2018-04-24 (0 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: gnome-themes-standard Title: package gnome-accessibility-themes 3.18.0-2ubuntu1 failed to install/upgrade: package gnome-accessibility-themes is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-themes-standard/+bug/1766733/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1713034] Re: gnome-shell crashed with SIGABRT in _ip_get_path_for_wd() ["assertion failed: (wd >= 0)"]
** Bug watch added: GNOME Bug Tracker #795522 https://bugzilla.gnome.org/show_bug.cgi?id=795522 ** Also affects: glib via https://bugzilla.gnome.org/show_bug.cgi?id=795522 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1713034 Title: gnome-shell crashed with SIGABRT in _ip_get_path_for_wd() ["assertion failed: (wd >= 0)"] Status in GLib: Unknown Status in gnome-shell package in Ubuntu: Triaged Bug description: https://errors.ubuntu.com/problem/3554ed6882d41ea6b6fe921fbc9450c857b89eaa https://errors.ubuntu.com/problem/7d4e9fc521926903d3f796d9d01b38c242396745 --- ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.24.3-0ubuntu4 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 ApportVersion: 2.20.6-0ubuntu7 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Aug 25 12:05:50 2017 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2014-08-13 (1107 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140810) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: gnome-shell StacktraceTop: g_assertion_message () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: gnome-shell crashed with SIGABRT in g_assertion_message() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1713034/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1765724] Re: Xenial -> Bionic - System fails to boot after upgrade - systemd-cryptsetup@cryptswap1.service fails to start
>From dist-upgrade logs: 2018-04-23 09:04:43,230 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process "./xorg_fix_proprietary.py" (No such file or directory) (8)) >From journal: screensaver is broken? Apr 23 14:17:10 ubuntu org.gnome.ScreenSaver[1341]: Unable to init server: Could not connect: Connection refused Apr 23 14:17:10 ubuntu gnome-screensav[1390]: Cannot open display: gnome-shell fails to start? Apr 23 14:17:12 ubuntu gnome-shell[1606]: Failed to create backend: Could not find a primary drm kms device Apr 23 14:17:12 ubuntu gnome-session[1355]: gnome-session-binary[1355]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1 Apr 23 14:17:12 ubuntu gnome-session-binary[1355]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1 Apr 23 14:17:12 ubuntu gnome-session-binary[1355]: Unrecoverable failure in required component org.gnome.Shell.desktop Apr 23 14:17:12 ubuntu gdm-launch-environment][1195]: pam_unix(gdm-launch-environment:session): session closed for user gdm Apr 23 14:17:12 ubuntu systemd-logind[1028]: Removed session c1. Apr 23 14:17:12 ubuntu spice-vdagentd[1186]: Error getting active session: No data available Apr 23 14:17:12 ubuntu dbus-daemon[1645]: [session uid=121 pid=1645] Activating service name='org.gnome.ScreenSaver' requested by ':1.3' (uid=121 pid=1647 comm="/usr/lib/gnome-session/gnome-session-binary --auto Apr 23 14:17:12 ubuntu org.gnome.ScreenSaver[1645]: Unable to init server: Could not connect: Connection refused Apr 23 14:17:12 ubuntu gnome-screensav[1654]: Cannot open display: Apr 23 14:17:12 ubuntu dbus-daemon[1645]: [session uid=121 pid=1645] Activated service 'org.gnome.ScreenSaver' failed: Process org.gnome.ScreenSaver exited with status 1 Apr 23 14:17:12 ubuntu gnome-session[1647]: gnome-session-binary[1647]: CRITICAL: Unable to create a DBus proxy for GnomeScreensaver: Error calling StartServiceByName for org.gnome.ScreenSaver: GDBus.Error:org.f Apr 23 14:17:12 ubuntu gnome-session-binary[1647]: CRITICAL: Unable to create a DBus proxy for GnomeScreensaver: Error calling StartServiceByName for org.gnome.ScreenSaver: GDBus.Error:org.freedesktop.DBus.Error Apr 23 14:17:12 ubuntu gnome-shell[1656]: Failed to create backend: Could not find a primary drm kms device Apr 23 14:17:12 ubuntu gnome-session[1647]: gnome-session-binary[1647]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1 Apr 23 14:17:12 ubuntu gnome-session-binary[1647]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1 Apr 23 14:17:12 ubuntu gnome-session-binary[1647]: Unrecoverable failure in required component org.gnome.Shell.desktop Apr 23 14:17:12 ubuntu gdm-launch-environment][1627]: pam_unix(gdm-launch-environment:session): session closed for user gdm Apr 23 14:17:12 ubuntu gdm3[1187]: GdmDisplay: display lasted 0.292659 seconds Apr 23 14:17:12 ubuntu systemd-logind[1028]: Removed session c2. Apr 23 14:17:12 ubuntu spice-vdagentd[1186]: Error getting active session: No data available Apr 23 14:17:12 ubuntu spice-vdagentd[1186]: Error getting active session: No data available Apr 23 14:17:12 ubuntu gdm3[1187]: Child process -1643 was already dead. This looks like a virtual machine, no? What graphics card does it have configured? is it QLX? and is the virtual machine using UEFI or BIOS? Is KVM available? ** Changed in: cryptsetup (Ubuntu) Status: New => Invalid ** Changed in: systemd (Ubuntu) Status: New => Invalid ** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Xenial -> Bionic - System fails to boot after upgrade - systemd-cryptsetup@cryptswap1.service fails to start + Xenial -> Bionic - System fails to boot after upgrade - gnome-screensaver & gnome-shell fail to start? ** Description changed: Test Case: 1. Install Xenial Desktop with encrypted home 2. Upgrade to bionic 3. Reboot Actual Result - The system hangs on boot when it activates the encrypted swap. There are the following entries in the journal: + The system appears to fail to start gnome-shell / gnome-screensaver: + + Apr 23 14:17:12 ubuntu dbus-daemon[1645]: [session uid=121 pid=1645] Activating service name='org.gnome.ScreenSaver' requested by ':1.3' (uid=121 pid=1647 comm="/usr/lib/gnome-session/gnome-session-binary --auto + Apr 23 14:17:12 ubuntu org.gnome.ScreenSaver[1645]: Unable to init server: Could not connect: Connection refused + Apr 23 14:17:12 ubuntu gnome-screensav[1654]: Cannot open display: + Apr 23 14:17:12 ubuntu dbus-daemon[1645]: [session uid=121 pid=1645] Activated service 'org.gnome.ScreenSaver' failed: Process org.gnome.ScreenSaver exited with status 1 + Apr 23 14:17:12 ubuntu gnome-session[1647]: gnome-session-binary[1647]: CRITICAL: Unable to create a DBus proxy for GnomeScreensaver: Error calling StartServiceByName for org.gnome.ScreenSaver: GDBus.Error:org.f + Apr 23 14:17:12 ubuntu gnome-
[Desktop-packages] [Bug 1713034] Re: gnome-shell crashed with SIGABRT in _ip_get_path_for_wd() ["assertion failed: (wd >= 0)"]
Anyone getting this bug could please attach the report from jouralctl /usr/bin/gnome-shell ** Changed in: gnome-shell (Ubuntu) Status: Confirmed => Triaged ** Changed in: gnome-shell (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1713034 Title: gnome-shell crashed with SIGABRT in _ip_get_path_for_wd() ["assertion failed: (wd >= 0)"] Status in gnome-shell package in Ubuntu: Triaged Bug description: https://errors.ubuntu.com/problem/3554ed6882d41ea6b6fe921fbc9450c857b89eaa https://errors.ubuntu.com/problem/7d4e9fc521926903d3f796d9d01b38c242396745 --- ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.24.3-0ubuntu4 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 ApportVersion: 2.20.6-0ubuntu7 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Aug 25 12:05:50 2017 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2014-08-13 (1107 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140810) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: gnome-shell StacktraceTop: g_assertion_message () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: gnome-shell crashed with SIGABRT in g_assertion_message() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1713034/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1766575] Re: Drop libnss-myhostname recommends
Yes, I understand the reason for the Recommends. By "integrating with this", I meant that gnome-control-center's backend (which I believe is hostnamectl) should be updating /etc/hosts in addition to /etc/hostname. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1766575 Title: Drop libnss-myhostname recommends Status in gnome-control-center package in Ubuntu: Fix Committed Status in gnome-control-center source package in Bionic: Fix Committed Bug description: gnome-control-center added a Recommends: libnss-myhostname years ago so that it was possible to easily change the hostname in the Details panel. That dependency no longer appears to be needed since we switched to systemd-resolved. Testing Done In both Debian Testing and Ubuntu 18.04 (Debian doesn't use systemd-resolved so seemed useful to try there too). sudo apt uninstall libnss-myhostname Restart Open the GNOME Settings app (gnome-control-center) In the left sidebar, click Devices Enter a different Device name in the block Open a terminal and verify that the hostname has been changed. In Debian, running `ping new-hostname` fails, but it works fine in Ubuntu. Other Info == There are concerns about having libnss-myhostname in the default install. See comment 5 at LP: #1741277. See also LP: #1162475 Note that /etc/hosts isn't updated regardless of whether libnss-myhostname is installed (I guess my bug description there was wrong but there was some kind of bug there.) Regression Potential To quote from the manpage: https://manpages.debian.org/unstable/nss-resolve "Note that systemd-resolved will synthesize DNS resource records in a few cases, for example for "localhost" and the current hostname, see systemd-resolved(8) for the full list. This duplicates the functionality of nss-myhostname(8), but it is still recommended (see examples below) to keep nss-myhostname configured in /etc/nsswitch.conf, to keep those names resolveable if systemd- resolved is not running." Ubuntu uses systemd-resolved by default and it's expected that users who don't want to use that will need to configure some things manually. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1766575/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1764087] Re: Wrongly boots into low graphics mode
Hi Dave, I'm using the new kernel (4.13.0-39-generic) and I still get the error (though my laptop did start up once without the error). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1764087 Title: Wrongly boots into low graphics mode Status in xorg package in Ubuntu: New Bug description: Description: Ubuntu 16.04.4 LTS Release: 16.04 Lenovo T410 with VGA compatible controller [0300]: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) Booting from latest kernel ThinkPad-T410 4.13.0-38-generic #43~16.04.1-Ubuntu SMP Wed Mar 14 17:48:43 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux goes into low graphics mode and also effects wi-fi connection insofar as it does not connect to my router. Whereas booting from 4.13.0-37-generic #42~16.04.1-Ubuntu SMP Wed Mar 7 16:03:28 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux works most of the time but occasionally has the same effects. I have had to submit this report after booting from 4.13.0.37 in order to submit bug. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-37.42~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sun Apr 15 10:40:31 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo Core Processor Integrated Graphics Controller [17aa:215a] InstallationDate: Installed on 2016-09-24 (567 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: LENOVO 2519Y11 ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-37-generic root=UUID=58d362c2-ed1e-479b-84f5-e5d8a782b08f ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/14/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 6IET85WW (1.45 ) dmi.board.name: 2519Y11 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6IET85WW(1.45):bd02/14/2013:svnLENOVO:pn2519Y11:pvrThinkPadT410:rvnLENOVO:rn2519Y11:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T410 dmi.product.name: 2519Y11 dmi.product.version: ThinkPad T410 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Sun Apr 15 08:52:27 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.5-0ubuntu2~16.04.1 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1764087/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1588192] Re: GL interfaces seem wedged for Krita on nvidia
compile gcc version for ppa:ubuntu-toolchain-r/test problema. setup ppa:ubuntu-toolchain-r/test dav update kernel drivers nvidia auto make install BUM! my 14.04 lts sudo ppa-purge ppa:ubuntu-toolchain-r/test reinstall nvidia-304 ok. :D -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1588192 Title: GL interfaces seem wedged for Krita on nvidia Status in Snappy: In Progress Status in nvidia-graphics-drivers-304 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-340 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-361 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-304 source package in Xenial: In Progress Status in nvidia-graphics-drivers-340 source package in Xenial: Won't Fix Status in nvidia-graphics-drivers-361 source package in Xenial: Won't Fix Bug description: Krita snap segfaults. I'm running nvidia proprietary drivers on Dell XPS 15. mark@mark-XPS-15-9550:~$ snap install krita 97.84 MB / 97.84 MB [=] 100.00 % 362.82 KB/s Name Version Rev Developer krita 3.0-snap10 1krita mark@mark-XPS-15-9550:~$ krita QCoreApplication::arguments: Please instantiate the QApplication object first krita.lib.pigment: Compiled for arch: ::Vc::AVXImpl krita.lib.pigment: Features supported: krita.lib.pigment: "SSE2" --- yes krita.lib.pigment: "SSSE3"--- yes krita.lib.pigment: "SSE4.1" --- yes krita.lib.pigment: "AVX " --- yes libGL error: No matching fbConfigs or visuals found libGL error: failed to load driver: swrast Segmentation fault (core dumped) mark@mark-XPS-15-9550:~$ To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1588192/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [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()
Great to hear, were you getting this regularly? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in 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() Status in Mutter: In Progress Status in gnome-shell package in Ubuntu: Fix Released Status in mutter package in Ubuntu: Fix Released Status in gnome-shell source package in Bionic: Fix Released Status in mutter source package in Bionic: Fix Released Bug description: https://errors.ubuntu.com/problem/3e662975e4b7e6829b9d68d1c2b06f429e44c854 --- left virtual box to update win10 came back and got error message ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 17 23:37:32 2017 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2017-04-18 (182 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7feb2ed42d94 :mov 0x18(%rax),%eax PC (0x7feb2ed42d94) ok source "0x18(%rax)" (0x0018) not located in a known VMA region (needed readable region)! destination "%eax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: meta_window_get_monitor () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6 ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6 ?? () from /usr/lib/libgjs.so.0 ?? () from /usr/lib/libgjs.so.0 Title: gnome-shell crashed with SIGSEGV in meta_window_get_monitor() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1724439/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1765363] Re: prime-select intel is not powering off the nvidia card
I confirm a power usage issue. Dell 7510 (too !) Ubuntu (GNOME) 18.04 Nvidia M1000M I found that the file : /etc/modprobe.d/blacklist-nvidia.conf is not removed by prime when switching to Nvidia, so the module cannot be loaded (as far I understand the stuff). When I remove it and load with Nvidia mode, the Nvidia module is loaded, not the Nouveau module. The grub option "nouveau.run-pm=0" (or something like that) is either not removed when purging Nvidia-390 stack. Removing it manually allows to use Nouveau with normal (low) power usage. I did not succeed to get a Nvidia-390 with Intel mode AND dGPU powered off. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1765363 Title: prime-select intel is not powering off the nvidia card Status in nvidia-prime package in Ubuntu: Confirmed Bug description: Right now, it seems that prime-select intel makes sure the nvidia driver is not loaded, as nvidia-settings reports. But my power consumption is > 20W. cat /proc/acpi/bbswitch reports the card is still on. If bbswitch and powertop are reliable, then the nvidia card is still powered. This is a thinkpad w520 in Optimus mode. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nvidia-prime 0.8.7 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 19 19:56:21 2018 Dependencies: EcryptfsInUse: Yes InstallationDate: Installed on 2017-12-14 (125 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) PackageArchitecture: all SourcePackage: nvidia-prime UpgradeStatus: Upgraded to bionic on 2018-03-09 (41 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1765363/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1751147] Re: nvidia-304 kernel module failed to build with new bionic kernel [error: implicit declaration of function ‘init_timer’; did you mean ‘init_timers’?]
*** This bug is a duplicate of bug 1737750 *** https://bugs.launchpad.net/bugs/1737750 gcc problem. setup ppa:ubuntu-toolchain-r/test dav update kernel drivers nvidia auto make install BUM! my 14.04 lts sudo ppa-purge ppa:ubuntu-toolchain-r/test reinstall nvidia-304 ok. :D -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-304 in Ubuntu. https://bugs.launchpad.net/bugs/1751147 Title: nvidia-304 kernel module failed to build with new bionic kernel [error: implicit declaration of function ‘init_timer’; did you mean ‘init_timers’?] Status in nvidia-graphics-drivers-304 package in Ubuntu: Confirmed Bug description: After updating to the 4.15.0-10-generic kernel today and rebooting, could log in but not do anything after that (got desktop image and conky, but no panel). Returning to the prior kernel, everything was OK except apport popped up with this error. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: nvidia-304 304.137-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 DKMSKernelVersion: 4.15.0-10-generic Date: Thu Feb 22 15:30:32 2018 DuplicateSignature: dkms:nvidia-304:304.137-0ubuntu2:/var/lib/dkms/nvidia-304/304.137/build/nv.c:3032:5: error: implicit declaration of function ‘init_timer’; did you mean ‘init_timers’? [-Werror=implicit-function-declaration] InstallationDate: Installed on 2018-02-10 (12 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180210) PackageVersion: 304.137-0ubuntu2 Python3Details: /usr/bin/python3.6, Python 3.6.4+, python3-minimal, 3.6.4-1 PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4 RelatedPackageVersions: dpkg 1.19.0.5ubuntu1 apt 1.6~alpha7ubuntu2 SourcePackage: nvidia-graphics-drivers-304 Title: nvidia-304 304.137-0ubuntu2: nvidia-304 kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1751147/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1742837] Re: nvidia-304 304.135-0ubuntu0.16.04.1: nvidia-304 kernel module failed to build (error: initialization from incompatible pointer type [-Werror=incompatible-pointer-t
*** This bug is a duplicate of bug 1717246 *** https://bugs.launchpad.net/bugs/1717246 no work 18.04 a gcc version. setup ppa:ubuntu-toolchain-r/test dav update kernel drivers nvidia auto make install BUM! my 14.04 lts sudo ppa-purge ppa:ubuntu-toolchain-r/test sudo apt-get update sudo apt-get upgrade -y sudo apt-get --reinstall nvidia-304 :D -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-304 in Ubuntu. https://bugs.launchpad.net/bugs/1742837 Title: nvidia-304 304.135-0ubuntu0.16.04.1: nvidia-304 kernel module failed to build (error: initialization from incompatible pointer type [-Werror=incompatible-pointer-types] .unload = nv_drm_unload,) Status in nvidia-graphics-drivers-304 package in Ubuntu: Confirmed Bug description: problems with starup ProblemType: Package DistroRelease: Ubuntu 16.04 Package: nvidia-304 304.135-0ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-42-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Es un directorio: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 304.135 Tue Jan 17 15:26:26 PST 2017 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.5) .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true DKMSKernelVersion: 4.13.0-26-generic Date: Thu Jan 11 11:25:31 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: nvidia-304, 304.135, 4.10.0-42-generic, x86_64: installed nvidia-304, 304.135, 4.4.0-109-generic, x86_64: installed DuplicateSignature: dkms:nvidia-304:304.135-0ubuntu0.16.04.1:/var/lib/dkms/nvidia-304/304.135/build/nv-drm.c:80:15: error: initialization from incompatible pointer type [-Werror=incompatible-pointer-types] GraphicsCard: NVIDIA Corporation G86 [GeForce 8500 GT] [10de:0421] (rev a1) (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. G86 [GeForce 8500 GT] [1682:230b] InstallationDate: Installed on 2017-11-01 (71 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) MachineType: ECS H61H2-CM PackageVersion: 304.135-0ubuntu0.16.04.1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-42-generic root=UUID=eb749f2f-d622-4f9d-bd2d-9e81f86f52e1 ro recovery nomodeset RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.24 SourcePackage: nvidia-graphics-drivers-304 Title: nvidia-304 304.135-0ubuntu0.16.04.1: nvidia-304 kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/28/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.name: H61H2-CM dmi.board.vendor: ECS dmi.board.version: 1.0 dmi.chassis.type: 3 dmi.chassis.vendor: ECS dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd02/28/2013:svnECS:pnH61H2-CM:pvr:rvnECS:rnH61H2-CM:rvr1.0:cvnECS:ct3:cvr: dmi.product.name: H61H2-CM dmi.sys.vendor: ECS version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Thu Jan 11 20:59:51 2018 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputUSB USB Keyboard KEYBOARD, id 8 inputUSB USB Keyboard KEYBOARD, id 9 inputUSB Wheel Mouse MOUSE, id 10 xserver.errors: open /dev/fb0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.3-1ubuntu1~16.04.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1742837/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages
[Desktop-packages] [Bug 1712044] Re: AppArmor profile misses entries
This should be fixed in Ubuntu 18.04 (about to be released this week). ** Package changed: chromium-browser (Ubuntu) => apparmor (Ubuntu) ** Changed in: apparmor (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1712044 Title: AppArmor profile misses entries Status in apparmor package in Ubuntu: Fix Released Bug description: If Chromium is started, a plethora of AppArmor notifications are shown (apparmor-notify installed) and logged to syslog. I would expect that these are included in the supplied AppArmor profile and no notifications/log entries appear. Example in syslog: kernel: [85217.346416] kauditd_printk_skb: 67 callbacks suppressed kernel: [85217.346418] audit: type=1400 audit(1503309729.810:2095): apparmor="ALLOWED" operation="open" profile="/usr/lib/chromium-browser/chromium-browser" name="/proc/1110/setgroups" pid=1110 comm="chromium-browse" requested_mask="w" denied_mask="w" fsuid=1000 ouid=1000 kernel: [85217.346419] audit: type=1400 audit(1503309729.810:2096): apparmor="ALLOWED" operation="capable" profile="/usr/lib/chromium-browser/chromium-browser" pid=1110 comm="chromium-browse" capability=21 capname="sys_admin" kernel: [85217.346420] audit: type=1400 audit(1503309729.810:2097): apparmor="ALLOWED" operation="open" profile="/usr/lib/chromium-browser/chromium-browser" name="/proc/1110/gid_map" pid=1110 comm="chromium-browse" requested_mask="w" denied_mask="w" fsuid=1000 ouid=1000 kernel: [85217.346420] audit: type=1400 audit(1503309729.810:2098): apparmor="ALLOWED" operation="open" profile="/usr/lib/chromium-browser/chromium-browser" name="/proc/1110/uid_map" pid=1110 comm="chromium-browse" requested_mask="w" denied_mask="w" fsuid=1000 ouid=1000 kernel: [85217.347648] audit: type=1400 audit(1503309729.810:2099): apparmor="ALLOWED" operation="capable" profile="/usr/lib/chromium-browser/chromium-browser" pid=1069 comm="chromium-browse" capability=21 capname="sys_admin" kernel: [85217.348429] audit: type=1400 audit(1503309729.814:2100): apparmor="ALLOWED" operation="open" profile="/usr/lib/chromium-browser/chromium-browser" name="/proc//setgroups" pid= comm="chromium-browse" requested_mask="w" denied_mask="w" fsuid=1000 ouid=1000 kernel: [85217.348430] audit: type=1400 audit(1503309729.814:2101): apparmor="ALLOWED" operation="capable" profile="/usr/lib/chromium-browser/chromium-browser" pid= comm="chromium-browse" capability=21 capname="sys_admin" kernel: [85217.348431] audit: type=1400 audit(1503309729.814:2102): apparmor="ALLOWED" operation="open" profile="/usr/lib/chromium-browser/chromium-browser" name="/proc//uid_map" pid= comm="chromium-browse" requested_mask="w" denied_mask="w" fsuid=1000 ouid=1000 kernel: [85217.348432] audit: type=1400 audit(1503309729.814:2103): apparmor="ALLOWED" operation="open" profile="/usr/lib/chromium-browser/chromium-browser" name="/proc//gid_map" pid= comm="chromium-browse" requested_mask="w" denied_mask="w" fsuid=1000 ouid=1000 kernel: [85217.654651] audit: type=1400 audit(1503309730.118:2104): apparmor="ALLOWED" operation="open" profile="/usr/lib/chromium-browser/chromium-browser" name="/proc//setgroups" pid= comm="chromium-browse" requested_mask="w" denied_mask="w" fsuid=1000 ouid=1000 kernel: [85262.883573] kauditd_printk_skb: 114 callbacks suppressed kernel: [85262.883577] audit: type=1400 audit(1503309775.343:2219): apparmor="ALLOWED" operation="exec" profile="/usr/lib/chromium-browser/chromium-browser//xdgsettings" name="/usr/bin/tr" pid=1299 comm="xdg-mime" requested_mask="x" denied_mask="x" fsuid=1000 ouid=0 target="/usr/lib/chromium-browser/chromium-browser//xdgsettings//null-/usr/bin/tr" kernel: [85262.883658] audit: type=1400 audit(1503309775.343:2220): apparmor="ALLOWED" operation="file_inherit" profile="/usr/lib/chromium-browser/chromium-browser//xdgsettings//null-/usr/bin/tr" name="/dev/null" pid=1299 comm="tr" requested_mask="w" denied_mask="w" fsuid=1000 ouid=0 kernel: [85262.883677] audit: type=1400 audit(1503309775.343:2221): apparmor="ALLOWED" operation="file_mmap" profile="/usr/lib/chromium-browser/chromium-browser//xdgsettings//null-/usr/bin/tr" name="/usr/bin/tr" pid=1299 comm="tr" requested_mask="rm" denied_mask="rm" fsuid=1000 ouid=0 kernel: [85262.883697] audit: type=1400 audit(1503309775.343:): apparmor="ALLOWED" operation="file_mmap" profile="/usr/lib/chromium-browser/chromium-browser//xdgsettings//null-/usr/bin/tr" name="/lib/x86_64-linux-gnu/ld-2.23.so" pid=1299 comm="tr" requested_mask="rm" denied_mask="rm" fsuid=1000 ouid=0 kernel: [85262.883802] audit: type=1400 audit(1503309775.343:2223): apparmor="ALLOWED" operation="open" profile="/usr/lib/chromium-browser/chromium-browser//xdgsettings//null-/usr/bin/tr" name="/e
[Desktop-packages] [Bug 1762952] Re: Alternative shortcut for layout switching Alt+Shift unexpectedly set by default
Thanks for sharing that, Carl-Erik. On 2018-04-24 21:25, Carl-Erik Kopseng wrote: > This seems to point to this being some kind of upgrade issue. It does, indeed. The question is which package sets it. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1762952 Title: Alternative shortcut for layout switching Alt+Shift unexpectedly set by default Status in gnome-control-center package in Ubuntu: New Status in gnome-shell package in Ubuntu: Confirmed Bug description: Version: Ubuntu 18.04 Final Beta with default Gnome Shell included in 18.04 Steps to reproduce: 1. Define two keyboard input methods in Settings -> Region & Language -> Input Sources 2. Open several applications 3. Observe that application windows can be iterated with Alt + Tab 4. Once application window iteration was begun with Alt + Tab, try to iterate backwards with Alt + Shift + Tab. 5. Try to change keyboard input method switching hotkeys in Settings -> Region & Language -> Input Sources -> Options. 6. Observe that Keyboard shortcut for "Alternative switch to next source" is set to "Alt + Shift" and that keyboard shortcuts can only be changed in Settings -> Devices -> Keyboard -> Keyboard Shortcuts. 7. Observe that the shortcut for "Alternative switch to next source" is not available for configuration in Settings -> Devices -> Keyboard -> Keyboard Shortcuts. Actual state: * Performing step 4 does not select the previous app in application switcher but instead changes keyboard input method. Expected state: * The shortcut for "Alternative switch to next source" can be changed and / or deactivated in Settings -> Devices -> Keyboard -> Keyboard Shortcuts. Notes: * The above was working fine in Ubuntu 17.10. I assume "Alternative switch to next source" did not exist in that version of Gnome Shell. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1762952/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1762952] Re: Alternative shortcut for layout switching Alt+Shift unexpectedly set by default
Just wanted to chime in on the upgrade path problem. I also upgraded from Ubuntu 17.10 and I also never set this shortcut anywhere. I have always used Super+Space and I have never used the Gnome Tweaks tool before. Using it to disable the shortcut fixed all the issues and the shortcuts using Shift - regardless of program - now work. This seems to point to this being some kind of upgrade issue. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1762952 Title: Alternative shortcut for layout switching Alt+Shift unexpectedly set by default Status in gnome-control-center package in Ubuntu: New Status in gnome-shell package in Ubuntu: Confirmed Bug description: Version: Ubuntu 18.04 Final Beta with default Gnome Shell included in 18.04 Steps to reproduce: 1. Define two keyboard input methods in Settings -> Region & Language -> Input Sources 2. Open several applications 3. Observe that application windows can be iterated with Alt + Tab 4. Once application window iteration was begun with Alt + Tab, try to iterate backwards with Alt + Shift + Tab. 5. Try to change keyboard input method switching hotkeys in Settings -> Region & Language -> Input Sources -> Options. 6. Observe that Keyboard shortcut for "Alternative switch to next source" is set to "Alt + Shift" and that keyboard shortcuts can only be changed in Settings -> Devices -> Keyboard -> Keyboard Shortcuts. 7. Observe that the shortcut for "Alternative switch to next source" is not available for configuration in Settings -> Devices -> Keyboard -> Keyboard Shortcuts. Actual state: * Performing step 4 does not select the previous app in application switcher but instead changes keyboard input method. Expected state: * The shortcut for "Alternative switch to next source" can be changed and / or deactivated in Settings -> Devices -> Keyboard -> Keyboard Shortcuts. Notes: * The above was working fine in Ubuntu 17.10. I assume "Alternative switch to next source" did not exist in that version of Gnome Shell. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1762952/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1766694] Re: If U1 is pre configured in g-o-a LivePatch in g-i-s fails to install
** Changed in: gnome-online-accounts (Ubuntu) Assignee: (unassigned) => Andrea Azzarone (azzar1) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1766694 Title: If U1 is pre configured in g-o-a LivePatch in g-i-s fails to install Status in Release Notes for Ubuntu: Fix Released Status in gnome-online-accounts package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Set up a fresh 18.04 machine 2. Login 3. While g-i-s is open, go to gnome-control-center and add a U1 account 4. Close g-c-c 5. Proceed through g-i-s and enable LivePatch 6. You are asked to log in to U1 again (which might be a bug in itself, if there's already an account there, we should prompt to use it) 7. Go through the login process 8. Click Connect 9. The g-o-a window closes and you're back to g-i-s but no action is taken to install LivePatch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1766694/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1766694] Re: If U1 is pre configured in g-o-a LivePatch in g-i-s fails to install
Worth noting that if you go to Software & Updates and enable LP from there you are prompted to select the pre existing U1 g-o-a account and set up completes. ** Changed in: ubuntu-release-notes Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1766694 Title: If U1 is pre configured in g-o-a LivePatch in g-i-s fails to install Status in Release Notes for Ubuntu: Fix Released Status in gnome-online-accounts package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Set up a fresh 18.04 machine 2. Login 3. While g-i-s is open, go to gnome-control-center and add a U1 account 4. Close g-c-c 5. Proceed through g-i-s and enable LivePatch 6. You are asked to log in to U1 again (which might be a bug in itself, if there's already an account there, we should prompt to use it) 7. Go through the login process 8. Click Connect 9. The g-o-a window closes and you're back to g-i-s but no action is taken to install LivePatch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1766694/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1766402] Re: Baobab is not in kubuntu 18.04 menu
Hello Rik, thanks, that is right. I delete NotShowIn=KDE; and baobab is in the menu. But why do GNOME this? ** Also affects: baobab (Ubuntu) Importance: Undecided Status: New ** No longer affects: kubuntu-meta (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to baobab in Ubuntu. https://bugs.launchpad.net/bugs/1766402 Title: Baobab is not in kubuntu 18.04 menu Status in baobab package in Ubuntu: New Bug description: Hello, i installed baobab on Kubuntu 18.04. I cannot find it in the menu. With the search i can only start it from the console. Best regards Michael To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/baobab/+bug/1766402/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1766694] [NEW] If U1 is pre configured in g-o-a LivePatch in g-i-s fails to install
Public bug reported: Steps to reproduce: 1. Set up a fresh 18.04 machine 2. Login 3. While g-i-s is open, go to gnome-control-center and add a U1 account 4. Close g-c-c 5. Proceed through g-i-s and enable LivePatch 6. You are asked to log in to U1 again (which might be a bug in itself, if there's already an account there, we should prompt to use it) 7. Go through the login process 8. Click Connect 9. The g-o-a window closes and you're back to g-i-s but no action is taken to install LivePatch ** Affects: ubuntu-release-notes Importance: Undecided Status: Fix Released ** Affects: gnome-online-accounts (Ubuntu) Importance: Medium Status: Confirmed ** Changed in: gnome-online-accounts (Ubuntu) Status: New => Confirmed ** Changed in: gnome-online-accounts (Ubuntu) Importance: Undecided => High ** Changed in: gnome-online-accounts (Ubuntu) Importance: High => Medium ** Also affects: ubuntu-release-notes Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1766694 Title: If U1 is pre configured in g-o-a LivePatch in g-i-s fails to install Status in Release Notes for Ubuntu: Fix Released Status in gnome-online-accounts package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Set up a fresh 18.04 machine 2. Login 3. While g-i-s is open, go to gnome-control-center and add a U1 account 4. Close g-c-c 5. Proceed through g-i-s and enable LivePatch 6. You are asked to log in to U1 again (which might be a bug in itself, if there's already an account there, we should prompt to use it) 7. Go through the login process 8. Click Connect 9. The g-o-a window closes and you're back to g-i-s but no action is taken to install LivePatch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1766694/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1765654] Re: Typo in 2FA prompt "passccode"
Seems like it's correctly spelled in the code:
add_entry (grid2, row++, _("Passc_ode:"), &data->otp_entry);
** Also affects: gnome-online-accounts (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-online-accounts in Ubuntu.
https://bugs.launchpad.net/bugs/1765654
Title:
Typo in 2FA prompt "passccode"
Status in gnome-initial-setup package in Ubuntu:
New
Status in gnome-online-accounts package in Ubuntu:
New
Bug description:
When logging in to Ubuntu SSO for enabling Livepatch, as a member of a
Launchpad team which requires 2FA, I'm prompted for my second factor.
The dialog has a typo and asks for my "passccode"
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-initial-setup 3.28.0-2ubuntu6
ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
Uname: Linux 4.15.0-15-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu5
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 20 10:57:22 2018
InstallationDate: Installed on 2015-07-04 (1021 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
SourcePackage: gnome-initial-setup
UpgradeStatus: Upgraded to bionic on 2018-03-15 (35 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-initial-setup/+bug/1765654/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1766020] Re: package python3 3.6.5-3 failed to install/upgrade: installed python3 package post-installation script subprocess returned error exit status 4
** Also affects: hplip Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1766020 Title: package python3 3.6.5-3 failed to install/upgrade: installed python3 package post-installation script subprocess returned error exit status 4 Status in HPLIP: New Status in hplip package in Ubuntu: Confirmed Bug description: Hello, error came up while updating. Paketmanager has canceled the update completely. Not yet analyzed for errors with console ... ProblemType: Package DistroRelease: Ubuntu 18.04 Package: python3 3.6.5-3 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu6 Architecture: amd64 Date: Sun Apr 22 00:01:23 2018 ErrorMessage: installed python3 package post-installation script subprocess returned error exit status 4 InstallationDate: Installed on 2018-04-04 (17 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) 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: python3-defaults Title: package python3 3.6.5-3 failed to install/upgrade: installed python3 package post-installation script subprocess returned error exit status 4 UpgradeStatus: Upgraded to bionic on 2018-04-04 (17 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/1766020/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1766681] [NEW] Window doesn't bring to front if open torrent file
Public bug reported: When open torrent file using Transmission, it open dialog to add new torrent but window doesn't bring to front or doesn't show any notification (application is ready). In the scenario where transmission is hidden by other application like web/file browser, it's very confusing. Because user open torrent file and nothing happens visually. Affected desktop is Gnome-Shell. No third party extension is in used related to stilling window focus. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: transmission-gtk 2.92-3ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-19.20-generic 4.15.17 Uname: Linux 4.15.0-19-generic x86_64 ApportVersion: 2.20.9-0ubuntu6 Architecture: amd64 CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME Date: Wed Apr 25 00:22:15 2018 ExecutablePath: /usr/bin/transmission-gtk InstallationDate: Installed on 2017-10-26 (180 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: LD_LIBRARY_PATH= PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: transmission UpgradeStatus: Upgraded to bionic on 2018-03-29 (25 days ago) ** Affects: transmission (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to transmission in Ubuntu. https://bugs.launchpad.net/bugs/1766681 Title: Window doesn't bring to front if open torrent file Status in transmission package in Ubuntu: New Bug description: When open torrent file using Transmission, it open dialog to add new torrent but window doesn't bring to front or doesn't show any notification (application is ready). In the scenario where transmission is hidden by other application like web/file browser, it's very confusing. Because user open torrent file and nothing happens visually. Affected desktop is Gnome-Shell. No third party extension is in used related to stilling window focus. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: transmission-gtk 2.92-3ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-19.20-generic 4.15.17 Uname: Linux 4.15.0-19-generic x86_64 ApportVersion: 2.20.9-0ubuntu6 Architecture: amd64 CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME Date: Wed Apr 25 00:22:15 2018 ExecutablePath: /usr/bin/transmission-gtk InstallationDate: Installed on 2017-10-26 (180 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: LD_LIBRARY_PATH= PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: transmission UpgradeStatus: Upgraded to bionic on 2018-03-29 (25 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1766681/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1766685] [NEW] Gnome-initial-setup is shown on next login if appmenu is used to quit it.
Public bug reported: If the user quit gnome-initial-setup using the menu item "Quit" of the appmenu, on next login the wizard should not be auto-started. ** Affects: gnome-initial-setup (Ubuntu) Importance: Medium Assignee: Andrea Azzarone (azzar1) Status: In Progress ** Changed in: gnome-initial-setup (Ubuntu) Importance: Undecided => Medium ** Changed in: gnome-initial-setup (Ubuntu) Assignee: (unassigned) => Andrea Azzarone (azzar1) ** Changed in: gnome-initial-setup (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-initial-setup in Ubuntu. https://bugs.launchpad.net/bugs/1766685 Title: Gnome-initial-setup is shown on next login if appmenu is used to quit it. Status in gnome-initial-setup package in Ubuntu: In Progress Bug description: If the user quit gnome-initial-setup using the menu item "Quit" of the appmenu, on next login the wizard should not be auto-started. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-initial-setup/+bug/1766685/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1766659] Re: pppoeconf should not be in Ubuntu Desktop
I confirm that we should not have ifupdown in the default desktop install in 18.04 and that it would be reasonable IMHO to move pppoeconf to ship-live. I am deferring to Adam to decide whether to accept this change due to the timing of release. ** Changed in: ubuntu-meta (Ubuntu) Status: New => Triaged ** Changed in: ubuntu-meta (Ubuntu) Assignee: Steve Langasek (vorlon) => Adam Conrad (adconrad) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pppoeconf in Ubuntu. https://bugs.launchpad.net/bugs/1766659 Title: pppoeconf should not be in Ubuntu Desktop Status in pppoeconf package in Ubuntu: New Status in ubuntu-meta package in Ubuntu: Triaged Bug description: pppoeconf should not be in Ubuntu Desktop As network-manager on Ubuntu Desktop configures PPP connection all by itself, with ppp recommends and ppp-dev build-depends. pppoeconf should not ship in Ubuntu desktop in Bionic, and thus should not pull in ifupdown on Ubuntu Desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pppoeconf/+bug/1766659/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1766673] [NEW] gnome user shell extensions are not installing
Public bug reported: gnome user shell extensions are not installing when installing from Firefox ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.2-0ubuntu0.1 ProcVersionSignature: Ubuntu 4.13.0-38.43-generic 4.13.16 Uname: Linux 4.13.0-38-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.8 Architecture: amd64 Date: Tue Apr 24 23:19:05 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-04-15 (9 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) ProcEnviron: LANGUAGE=en_IN:en TERM=xterm-256color PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1766673 Title: gnome user shell extensions are not installing Status in gnome-shell package in Ubuntu: New Bug description: gnome user shell extensions are not installing when installing from Firefox ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.2-0ubuntu0.1 ProcVersionSignature: Ubuntu 4.13.0-38.43-generic 4.13.16 Uname: Linux 4.13.0-38-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.8 Architecture: amd64 Date: Tue Apr 24 23:19:05 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-04-15 (9 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) ProcEnviron: LANGUAGE=en_IN:en TERM=xterm-256color PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1766673/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1744001] Re: Expanded panel menus don't fade out cleanly on close
This bug was fixed in the package gnome-shell - 3.28.1-0ubuntu2 --- gnome-shell (3.28.1-0ubuntu2) bionic; urgency=medium [ Marco Trevisan (Treviño) ] * js-ui-Choose-some-actors-to-cache-on-the-GPU.patch: - Improve rendering of shell elements moving rendering to GPU (LP: #1744001) [ Jeremy Bicha ] * Cherry-pick polkitAgent-Guard-against-repeated-close-calls.patch: - Fix PolicyKit authorization prompt after cancelling once (LP: #1765353) -- Marco Trevisan (Treviño) Mon, 23 Apr 2018 15:29:28 -0500 ** Changed in: gnome-shell (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1744001 Title: Expanded panel menus don't fade out cleanly on close Status in GNOME Shell: Confirmed Status in gnome-shell package in Ubuntu: Fix Released Bug description: [ Impact ] Expanded panel menus don't fade out cleanly on close. [ Test case ] 1. Open the panel menu and expand any one of the submenus. 2. Click on the desktop to close the panel menu. Expected: Menu fades out cleanly like when it wasn't expanded. Was: Expanded part of the menu does not fade out cleanly. [ Regression potential ] Shell items might be no properly be refreshed realtime or redrawn To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1744001/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1765353] Re: gnome-control-center crashed with SIGSEGV in acquire_cb() from g_simple_async_result_complete()
This bug was fixed in the package gnome-shell - 3.28.1-0ubuntu2 --- gnome-shell (3.28.1-0ubuntu2) bionic; urgency=medium [ Marco Trevisan (Treviño) ] * js-ui-Choose-some-actors-to-cache-on-the-GPU.patch: - Improve rendering of shell elements moving rendering to GPU (LP: #1744001) [ Jeremy Bicha ] * Cherry-pick polkitAgent-Guard-against-repeated-close-calls.patch: - Fix PolicyKit authorization prompt after cancelling once (LP: #1765353) -- Marco Trevisan (Treviño) Mon, 23 Apr 2018 15:29:28 -0500 ** Changed in: gnome-shell (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1765353 Title: gnome-control-center crashed with SIGSEGV in acquire_cb() from g_simple_async_result_complete() Status in gnome-control-center package in Ubuntu: Invalid Status in gnome-shell package in Ubuntu: Fix Released Bug description: Test Case = Open "Settings" and navigate to "Users". Click on "Unlock" and cancel dialog without inputting a password. "Unlock" becomes unresponsive and Settings will eventually crash. If started from a terminal I see the following output: (gnome-control-center:24951): GLib-GIO-CRITICAL **: 10:26:38.402: g_permission_acquire_finish: assertion 'G_IS_PERMISSION (permission)' failed fish: “gnome-control-center” terminated by signal SIGSEGV (Address boundary error) Regression Potential This commit fixes the bug and was applied upstream. https://gitlab.gnome.org/GNOME/gnome-shell/commit/0327069e83b Other Info == https://errors.ubuntu.com/problem/55b54d35f8bfd6319edbf1e24d53587020b16273 Being discussed on the forums - https://ubuntuforums.org/showthread.php?t=2389622 ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1:3.28.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Apr 19 10:25:11 2018 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2017-11-07 (163 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcCmdline: gnome-control-center --overview ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f7e2de3b845:pushq 0x8(%rax) PC (0x7f7e2de3b845) ok source "0x8(%rax)" (0x0008) not located in a known VMA region (needed readable region)! SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 g_simple_async_result_complete () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libpolkit-gobject-1.so.0 g_simple_async_result_complete () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libpolkit-gobject-1.so.0 Title: gnome-control-center crashed with SIGSEGV UpgradeStatus: Upgraded to bionic on 2018-02-21 (56 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1765353/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1766575] Re: Drop libnss-myhostname recommends
The dependency wasn't added so that gnome-control-center could resolve the hostname but so that everything else could resolve the hostname when gnome-control-center is used to change the hostname. Anyway, the dependency is already dropped in our bzr branch. This issue just didn't seem critical enough to try to get through Final Freeze since it was only identified today. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1766575 Title: Drop libnss-myhostname recommends Status in gnome-control-center package in Ubuntu: Fix Committed Status in gnome-control-center source package in Bionic: Fix Committed Bug description: gnome-control-center added a Recommends: libnss-myhostname years ago so that it was possible to easily change the hostname in the Details panel. That dependency no longer appears to be needed since we switched to systemd-resolved. Testing Done In both Debian Testing and Ubuntu 18.04 (Debian doesn't use systemd-resolved so seemed useful to try there too). sudo apt uninstall libnss-myhostname Restart Open the GNOME Settings app (gnome-control-center) In the left sidebar, click Devices Enter a different Device name in the block Open a terminal and verify that the hostname has been changed. In Debian, running `ping new-hostname` fails, but it works fine in Ubuntu. Other Info == There are concerns about having libnss-myhostname in the default install. See comment 5 at LP: #1741277. See also LP: #1162475 Note that /etc/hosts isn't updated regardless of whether libnss-myhostname is installed (I guess my bug description there was wrong but there was some kind of bug there.) Regression Potential To quote from the manpage: https://manpages.debian.org/unstable/nss-resolve "Note that systemd-resolved will synthesize DNS resource records in a few cases, for example for "localhost" and the current hostname, see systemd-resolved(8) for the full list. This duplicates the functionality of nss-myhostname(8), but it is still recommended (see examples below) to keep nss-myhostname configured in /etc/nsswitch.conf, to keep those names resolveable if systemd- resolved is not running." Ubuntu uses systemd-resolved by default and it's expected that users who don't want to use that will need to configure some things manually. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1766575/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1766020] Re: package python3 3.6.5-3 failed to install/upgrade: installed python3 package post-installation script subprocess returned error exit status 4
** Changed in: hplip (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1766020 Title: package python3 3.6.5-3 failed to install/upgrade: installed python3 package post-installation script subprocess returned error exit status 4 Status in hplip package in Ubuntu: Confirmed Bug description: Hello, error came up while updating. Paketmanager has canceled the update completely. Not yet analyzed for errors with console ... ProblemType: Package DistroRelease: Ubuntu 18.04 Package: python3 3.6.5-3 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu6 Architecture: amd64 Date: Sun Apr 22 00:01:23 2018 ErrorMessage: installed python3 package post-installation script subprocess returned error exit status 4 InstallationDate: Installed on 2018-04-04 (17 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) 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: python3-defaults Title: package python3 3.6.5-3 failed to install/upgrade: installed python3 package post-installation script subprocess returned error exit status 4 UpgradeStatus: Upgraded to bionic on 2018-04-04 (17 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1766020/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1766659] Re: pppoeconf should not be in Ubuntu Desktop
** Branch linked: lp:~xnox/ubuntu-seeds/drop-ppp-from-desktop -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pppoeconf in Ubuntu. https://bugs.launchpad.net/bugs/1766659 Title: pppoeconf should not be in Ubuntu Desktop Status in pppoeconf package in Ubuntu: New Status in ubuntu-meta package in Ubuntu: New Bug description: pppoeconf should not be in Ubuntu Desktop As network-manager on Ubuntu Desktop configures PPP connection all by itself, with ppp recommends and ppp-dev build-depends. pppoeconf should not ship in Ubuntu desktop in Bionic, and thus should not pull in ifupdown on Ubuntu Desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pppoeconf/+bug/1766659/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1766575] Re: Drop libnss-myhostname recommends
Every Ubuntu system is installed with an entry in /etc/hosts pointing to 127.0.1.1 for the hostname. gnome-control-center should be integrating with this, and not just relying on either libnss-myhostname or systemd- resolved to resolve the hostname. The local hostname should be resolvable without further moving parts at runtime - the software which manages the hostname should take care of updating the one additional config file. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1766575 Title: Drop libnss-myhostname recommends Status in gnome-control-center package in Ubuntu: Fix Committed Status in gnome-control-center source package in Bionic: Fix Committed Bug description: gnome-control-center added a Recommends: libnss-myhostname years ago so that it was possible to easily change the hostname in the Details panel. That dependency no longer appears to be needed since we switched to systemd-resolved. Testing Done In both Debian Testing and Ubuntu 18.04 (Debian doesn't use systemd-resolved so seemed useful to try there too). sudo apt uninstall libnss-myhostname Restart Open the GNOME Settings app (gnome-control-center) In the left sidebar, click Devices Enter a different Device name in the block Open a terminal and verify that the hostname has been changed. In Debian, running `ping new-hostname` fails, but it works fine in Ubuntu. Other Info == There are concerns about having libnss-myhostname in the default install. See comment 5 at LP: #1741277. See also LP: #1162475 Note that /etc/hosts isn't updated regardless of whether libnss-myhostname is installed (I guess my bug description there was wrong but there was some kind of bug there.) Regression Potential To quote from the manpage: https://manpages.debian.org/unstable/nss-resolve "Note that systemd-resolved will synthesize DNS resource records in a few cases, for example for "localhost" and the current hostname, see systemd-resolved(8) for the full list. This duplicates the functionality of nss-myhostname(8), but it is still recommended (see examples below) to keep nss-myhostname configured in /etc/nsswitch.conf, to keep those names resolveable if systemd- resolved is not running." Ubuntu uses systemd-resolved by default and it's expected that users who don't want to use that will need to configure some things manually. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1766575/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1765053] Re: Errors were encountered while processing: /tmp/apt-dpkg-install-x8YVfC/03-libnvidia-compute-390_390.48-0ubuntu2_i386.deb
** Changed in: nvidia-graphics-drivers-390 (Ubuntu Bionic) Status: In Progress => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1765053 Title: Errors were encountered while processing: /tmp/apt-dpkg-install- x8YVfC/03-libnvidia-compute-390_390.48-0ubuntu2_i386.deb Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in ubuntu-drivers-common package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 source package in Bionic: Confirmed Status in ubuntu-drivers-common source package in Bionic: Confirmed Bug description: Using Ubuntu MATE 18.04 daily ubuntu-drivers fails to install the nvidia 390 drivers. Here is what I captured on stdout. $ sudo ubuntu-drivers autoinstall Reading package lists... Done Building dependency tree Reading state information... Done The following package was automatically installed and is no longer required: gnome-session-common Use 'sudo apt autoremove' to remove it. The following additional packages will be installed: libnvidia-cfg1-390 libnvidia-common-390 libnvidia-compute-390 libnvidia-compute-390:i386 libnvidia-decode-390 libnvidia-decode-390:i386 libnvidia-encode-390 libnvidia-encode-390:i386 libnvidia-fbc1-390 libnvidia-fbc1-390:i386 libnvidia-gl-390 libnvidia-gl-390:i386 libnvidia-ifr1-390 libnvidia-ifr1-390:i386 libwayland-client0:i386 libwayland-server0:i386 libxnvctrl0 nvidia-compute-390 nvidia-compute-no-dkms-390 nvidia-compute-utils-390 nvidia-dkms-390 nvidia-kernel-source-390 nvidia-settings nvidia-utils-390 screen-resolution-extra xserver-xorg-video-nvidia-390 The following NEW packages will be installed libnvidia-cfg1-390 libnvidia-common-390 libnvidia-compute-390 libnvidia-compute-390:i386 libnvidia-decode-390 libnvidia-decode-390:i386 libnvidia-encode-390 libnvidia-encode-390:i386 libnvidia-fbc1-390 libnvidia-fbc1-390:i386 libnvidia-gl-390 libnvidia-gl-390:i386 libnvidia-ifr1-390 libnvidia-ifr1-390:i386 libwayland-client0:i386 libwayland-server0:i386 libxnvctrl0 nvidia-compute-390 nvidia-compute-no-dkms-390 nvidia-compute-utils-390 nvidia-dkms-390 nvidia-driver-390 nvidia-kernel-source-390 nvidia-settings nvidia-utils-390 screen-resolution-extra xserver-xorg-video-nvidia-390 0 to upgrade, 27 to newly install, 0 to remove and 0 not to upgrade. Need to get 0 B/85.3 MB of archives. After this operation, 365 MB of additional disk space will be used. Selecting previously unselected package libnvidia-cfg1-390:amd64. (Reading database ... 258596 files and directories currently installed.) Preparing to unpack .../00-libnvidia-cfg1-390_390.48-0ubuntu2_amd64.deb ... Unpacking libnvidia-cfg1-390:amd64 (390.48-0ubuntu2) ... Selecting previously unselected package libnvidia-common-390. Preparing to unpack .../01-libnvidia-common-390_390.48-0ubuntu2_all.deb ... Unpacking libnvidia-common-390 (390.48-0ubuntu2) ... Selecting previously unselected package libnvidia-compute-390:amd64. Preparing to unpack .../02-libnvidia-compute-390_390.48-0ubuntu2_amd64.deb ... Unpacking libnvidia-compute-390:amd64 (390.48-0ubuntu2) ... Selecting previously unselected package libnvidia-compute-390:i386. Preparing to unpack .../03-libnvidia-compute-390_390.48-0ubuntu2_i386.deb ... Unpacking libnvidia-compute-390:i386 (390.48-0ubuntu2) ... dpkg: error processing archive /tmp/apt-dpkg-install-x8YVfC/03-libnvidia-compute-390_390.48-0ubuntu2_i386.deb (--unpack): trying to overwrite shared '/etc/OpenCL/vendors/nvidia.icd', which is different from other instances of package libnvidia-compute-390:i386 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Selecting previously unselected package libnvidia-decode-390:amd64. Preparing to unpack .../04-libnvidia-decode-390_390.48-0ubuntu2_amd64.deb ... Unpacking libnvidia-decode-390:amd64 (390.48-0ubuntu2) ... Selecting previously unselected package libnvidia-decode-390:i386. Preparing to unpack .../05-libnvidia-decode-390_390.48-0ubuntu2_i386.deb ... Unpacking libnvidia-decode-390:i386 (390.48-0ubuntu2) ... Selecting previously unselected package libnvidia-encode-390:i386. Preparing to unpack .../06-libnvidia-encode-390_390.48-0ubuntu2_i386.deb ... Unpacking libnvidia-encode-390:i386 (390.48-0ubuntu2) ... Selecting previously unselected package libnvidia-encode-390:amd64. Preparing to unpack .../07-libnvidia-encode-390_390.48-0ubuntu2_amd64.deb ... Unpacking libnvidia-encode-390:amd64 (390.48-0ubuntu2) ... Selecting previously unselected package libnvidia-fbc1-390:amd64. Preparing to unpack .../08-libnvidia-fbc1-390_390.48-0ubuntu2_amd64.deb ... Unpacking libnvidia-fbc1-390:amd64 (390.48-0ubuntu2) ... Selecting previously unselected package libnvidia-fbc1-390:i386. Preparing to unpack .../09-libnvidia-fbc1-390_390.48
[Desktop-packages] [Bug 1766020] Re: package python3 3.6.5-3 failed to install/upgrade: installed python3 package post-installation script subprocess returned error exit status 4
running python rtupdate hooks for python3.6... E: py3compile:183: cannot create directory /usr/share/hplip/ui5/__pycache__: FileNotFoundError(2, 'No such file or directory') ... error running python rtupdate hook hplip-data dpkg: error processing package python3 (--configure): installed python3 package post-installation script subprocess returned error exit status 4 Seems like a bug in hplip-data. ** Package changed: python3-defaults (Ubuntu) => hplip (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1766020 Title: package python3 3.6.5-3 failed to install/upgrade: installed python3 package post-installation script subprocess returned error exit status 4 Status in hplip package in Ubuntu: Confirmed Bug description: Hello, error came up while updating. Paketmanager has canceled the update completely. Not yet analyzed for errors with console ... ProblemType: Package DistroRelease: Ubuntu 18.04 Package: python3 3.6.5-3 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu6 Architecture: amd64 Date: Sun Apr 22 00:01:23 2018 ErrorMessage: installed python3 package post-installation script subprocess returned error exit status 4 InstallationDate: Installed on 2018-04-04 (17 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) 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: python3-defaults Title: package python3 3.6.5-3 failed to install/upgrade: installed python3 package post-installation script subprocess returned error exit status 4 UpgradeStatus: Upgraded to bionic on 2018-04-04 (17 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1766020/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1754693] Re: Xwayland crashed with SIGABRT in st_renderbuffer_delete()
I can still reproduce this now on my T470 with fully up-to-date bionic (also tried the https://launchpad.net/~canonical-x/+archive/ubuntu/x-staging PPA) kwi 24 18:34:27 t470 org.gnome.Shell.desktop[6195]: (EE) kwi 24 18:34:27 t470 org.gnome.Shell.desktop[6195]: (EE) Backtrace: kwi 24 18:34:27 t470 org.gnome.Shell.desktop[6195]: (EE) 0: /usr/bin/Xwayland (xorg_backtrace+0x4d) [0x561ba663e6bd] kwi 24 18:34:27 t470 org.gnome.Shell.desktop[6195]: (EE) 1: /usr/bin/Xwayland (0x561ba6496000+0x1ac459) [0x561ba6642459] kwi 24 18:34:27 t470 org.gnome.Shell.desktop[6195]: (EE) 2: /lib/x86_64-linux-gnu/libpthread.so.0 (0x7ff68662b000+0x12890) [0x7ff68663d890] kwi 24 18:34:27 t470 org.gnome.Shell.desktop[6195]: (EE) 3: /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so (0x7ff67fed8000+0x24e9e3) [0x7ff6801269e3] kwi 24 18:34:27 t470 org.gnome.Shell.desktop[6195]: (EE) 4: /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so (0x7ff67fed8000+0x1b3ed4) [0x7ff68008bed4] kwi 24 18:34:27 t470 org.gnome.Shell.desktop[6195]: (EE) 5: /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so (0x7ff67fed8000+0x144c6a) [0x7ff68001cc6a] kwi 24 18:34:27 t470 org.gnome.Shell.desktop[6195]: (EE) 6: /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so (0x7ff67fed8000+0x144cae) [0x7ff68001ccae] kwi 24 18:34:27 t470 org.gnome.Shell.desktop[6195]: (EE) 7: /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so (0x7ff67fed8000+0x144d1c) [0x7ff68001cd1c] kwi 24 18:34:27 t470 org.gnome.Shell.desktop[6195]: (EE) 8: /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so (0x7ff67fed8000+0xad4b2) [0x7ff67ff854b2] kwi 24 18:34:27 t470 org.gnome.Shell.desktop[6195]: (EE) 9: /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so (0x7ff67fed8000+0x25b6db) [0x7ff6801336db] kwi 24 18:34:27 t470 org.gnome.Shell.desktop[6195]: (EE) 10: /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so (0x7ff67fed8000+0x3e2ae5) [0x7ff6802baae5] kwi 24 18:34:27 t470 org.gnome.Shell.desktop[6195]: (EE) 11: /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so (0x7ff67fed8000+0x3e1a13) [0x7ff6802b9a13] kwi 24 18:34:27 t470 org.gnome.Shell.desktop[6195]: (EE) 12: /usr/bin/Xwayland (0x561ba6496000+0xc8989) [0x561ba655e989] kwi 24 18:34:27 t470 org.gnome.Shell.desktop[6195]: (EE) 13: /usr/bin/Xwayland (0x561ba6496000+0xc7975) [0x561ba655d975] kwi 24 18:34:27 t470 org.gnome.Shell.desktop[6195]: (EE) 14: /usr/bin/Xwayland (0x561ba6496000+0x1969f2) [0x561ba662c9f2] kwi 24 18:34:27 t470 org.gnome.Shell.desktop[6195]: (EE) 15: /usr/bin/Xwayland (0x561ba6496000+0xcc5f7) [0x561ba65625f7] kwi 24 18:34:27 t470 org.gnome.Shell.desktop[6195]: (EE) 16: /usr/bin/Xwayland (0x561ba6496000+0xc7c3c) [0x561ba655dc3c] kwi 24 18:34:27 t470 org.gnome.Shell.desktop[6195]: (EE) 17: /usr/bin/Xwayland (0x561ba6496000+0x171ec8) [0x561ba6607ec8] kwi 24 18:34:27 t470 org.gnome.Shell.desktop[6195]: (EE) 18: /usr/bin/Xwayland (0x561ba6496000+0x175f10) [0x561ba660bf10] kwi 24 18:34:27 t470 org.gnome.Shell.desktop[6195]: (EE) 19: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xe7) [0x7ff68625bb97] kwi 24 18:34:27 t470 org.gnome.Shell.desktop[6195]: (EE) 20: /usr/bin/Xwayland (_start+0x2a) [0x561ba64d0ada] kwi 24 18:34:27 t470 org.gnome.Shell.desktop[6195]: (EE) kwi 24 18:34:27 t470 org.gnome.Shell.desktop[6195]: (EE) Segmentation fault at address 0x68 kwi 24 18:34:27 t470 org.gnome.Shell.desktop[6195]: (EE) kwi 24 18:34:27 t470 org.gnome.Shell.desktop[6195]: Fatal server error: kwi 24 18:34:27 t470 org.gnome.Shell.desktop[6195]: (EE) Caught signal 11 (Segmentation fault). Server aborting kwi 24 18:34:27 t470 org.gnome.Shell.desktop[6195]: (EE) Let me know if you need some interactive debugging on this. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1754693 Title: Xwayland crashed with SIGABRT in st_renderbuffer_delete() Status in mesa package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/01a80d2110a46f6b6d857ce814079646e695f4ca --- Steps to reproduce: Install 'slack' snap: sudo snap install slack --classic Run slack: slack Instacrash. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: xwayland 2:1.19.6-1ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CompizPlugins: [core,composite,opengl,decor,mousepoll,grid,vpswitch,compiztoolbox,imgpng,gnomecompat,regex,move,place,resize,snap,unitymtgrabhandles,wall,animation,session,expo,workarounds,fade,ezoom,scale,unityshell] CompositorRunning: None CurrentDesktop: GNOME Date: Fri Mar 9 10:31:06 2018 DistUpgraded: 2018-03-06 13:58:47,853 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu EcryptfsInUse: Yes ExecutablePath: /usr/bin/Xwayland ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCar
[Desktop-packages] [Bug 1766020] [NEW] package python3 3.6.5-3 failed to install/upgrade: installed python3 package post-installation script subprocess returned error exit status 4
You have been subscribed to a public bug: Hello, error came up while updating. Paketmanager has canceled the update completely. Not yet analyzed for errors with console ... ProblemType: Package DistroRelease: Ubuntu 18.04 Package: python3 3.6.5-3 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu6 Architecture: amd64 Date: Sun Apr 22 00:01:23 2018 ErrorMessage: installed python3 package post-installation script subprocess returned error exit status 4 InstallationDate: Installed on 2018-04-04 (17 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) 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: python3-defaults Title: package python3 3.6.5-3 failed to install/upgrade: installed python3 package post-installation script subprocess returned error exit status 4 UpgradeStatus: Upgraded to bionic on 2018-04-04 (17 days ago) ** Affects: hplip (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-package bionic -- package python3 3.6.5-3 failed to install/upgrade: installed python3 package post-installation script subprocess returned error exit status 4 https://bugs.launchpad.net/bugs/1766020 You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1744001] Re: Expanded panel menus don't fade out cleanly on close
** Description changed: + [ Impact ] + Expanded panel menus don't fade out cleanly on close. + + + [ Test case ] 1. Open the panel menu and expand any one of the submenus. 2. Click on the desktop to close the panel menu. Expected: Menu fades out cleanly like when it wasn't expanded. - Observed: Expanded part of the menu does not fade out cleanly. + Was: Expanded part of the menu does not fade out cleanly. - I've stumbled on a fix for this so a patch will follow soon. + [ Regression potential ] + + Shell items might be no properly be refreshed realtime or redrawn -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1744001 Title: Expanded panel menus don't fade out cleanly on close Status in GNOME Shell: Confirmed Status in gnome-shell package in Ubuntu: Fix Committed Bug description: [ Impact ] Expanded panel menus don't fade out cleanly on close. [ Test case ] 1. Open the panel menu and expand any one of the submenus. 2. Click on the desktop to close the panel menu. Expected: Menu fades out cleanly like when it wasn't expanded. Was: Expanded part of the menu does not fade out cleanly. [ Regression potential ] Shell items might be no properly be refreshed realtime or redrawn To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1744001/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1765053] Re: Errors were encountered while processing: /tmp/apt-dpkg-install-x8YVfC/03-libnvidia-compute-390_390.48-0ubuntu2_i386.deb
** Also affects: ubuntu-drivers-common (Ubuntu Bionic) Importance: Undecided Assignee: Alberto Milone (albertomilone) Status: Confirmed ** Also affects: nvidia-graphics-drivers-390 (Ubuntu Bionic) Importance: High Assignee: Alberto Milone (albertomilone) Status: In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1765053 Title: Errors were encountered while processing: /tmp/apt-dpkg-install- x8YVfC/03-libnvidia-compute-390_390.48-0ubuntu2_i386.deb Status in nvidia-graphics-drivers-390 package in Ubuntu: In Progress Status in ubuntu-drivers-common package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 source package in Bionic: In Progress Status in ubuntu-drivers-common source package in Bionic: Confirmed Bug description: Using Ubuntu MATE 18.04 daily ubuntu-drivers fails to install the nvidia 390 drivers. Here is what I captured on stdout. $ sudo ubuntu-drivers autoinstall Reading package lists... Done Building dependency tree Reading state information... Done The following package was automatically installed and is no longer required: gnome-session-common Use 'sudo apt autoremove' to remove it. The following additional packages will be installed: libnvidia-cfg1-390 libnvidia-common-390 libnvidia-compute-390 libnvidia-compute-390:i386 libnvidia-decode-390 libnvidia-decode-390:i386 libnvidia-encode-390 libnvidia-encode-390:i386 libnvidia-fbc1-390 libnvidia-fbc1-390:i386 libnvidia-gl-390 libnvidia-gl-390:i386 libnvidia-ifr1-390 libnvidia-ifr1-390:i386 libwayland-client0:i386 libwayland-server0:i386 libxnvctrl0 nvidia-compute-390 nvidia-compute-no-dkms-390 nvidia-compute-utils-390 nvidia-dkms-390 nvidia-kernel-source-390 nvidia-settings nvidia-utils-390 screen-resolution-extra xserver-xorg-video-nvidia-390 The following NEW packages will be installed libnvidia-cfg1-390 libnvidia-common-390 libnvidia-compute-390 libnvidia-compute-390:i386 libnvidia-decode-390 libnvidia-decode-390:i386 libnvidia-encode-390 libnvidia-encode-390:i386 libnvidia-fbc1-390 libnvidia-fbc1-390:i386 libnvidia-gl-390 libnvidia-gl-390:i386 libnvidia-ifr1-390 libnvidia-ifr1-390:i386 libwayland-client0:i386 libwayland-server0:i386 libxnvctrl0 nvidia-compute-390 nvidia-compute-no-dkms-390 nvidia-compute-utils-390 nvidia-dkms-390 nvidia-driver-390 nvidia-kernel-source-390 nvidia-settings nvidia-utils-390 screen-resolution-extra xserver-xorg-video-nvidia-390 0 to upgrade, 27 to newly install, 0 to remove and 0 not to upgrade. Need to get 0 B/85.3 MB of archives. After this operation, 365 MB of additional disk space will be used. Selecting previously unselected package libnvidia-cfg1-390:amd64. (Reading database ... 258596 files and directories currently installed.) Preparing to unpack .../00-libnvidia-cfg1-390_390.48-0ubuntu2_amd64.deb ... Unpacking libnvidia-cfg1-390:amd64 (390.48-0ubuntu2) ... Selecting previously unselected package libnvidia-common-390. Preparing to unpack .../01-libnvidia-common-390_390.48-0ubuntu2_all.deb ... Unpacking libnvidia-common-390 (390.48-0ubuntu2) ... Selecting previously unselected package libnvidia-compute-390:amd64. Preparing to unpack .../02-libnvidia-compute-390_390.48-0ubuntu2_amd64.deb ... Unpacking libnvidia-compute-390:amd64 (390.48-0ubuntu2) ... Selecting previously unselected package libnvidia-compute-390:i386. Preparing to unpack .../03-libnvidia-compute-390_390.48-0ubuntu2_i386.deb ... Unpacking libnvidia-compute-390:i386 (390.48-0ubuntu2) ... dpkg: error processing archive /tmp/apt-dpkg-install-x8YVfC/03-libnvidia-compute-390_390.48-0ubuntu2_i386.deb (--unpack): trying to overwrite shared '/etc/OpenCL/vendors/nvidia.icd', which is different from other instances of package libnvidia-compute-390:i386 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Selecting previously unselected package libnvidia-decode-390:amd64. Preparing to unpack .../04-libnvidia-decode-390_390.48-0ubuntu2_amd64.deb ... Unpacking libnvidia-decode-390:amd64 (390.48-0ubuntu2) ... Selecting previously unselected package libnvidia-decode-390:i386. Preparing to unpack .../05-libnvidia-decode-390_390.48-0ubuntu2_i386.deb ... Unpacking libnvidia-decode-390:i386 (390.48-0ubuntu2) ... Selecting previously unselected package libnvidia-encode-390:i386. Preparing to unpack .../06-libnvidia-encode-390_390.48-0ubuntu2_i386.deb ... Unpacking libnvidia-encode-390:i386 (390.48-0ubuntu2) ... Selecting previously unselected package libnvidia-encode-390:amd64. Preparing to unpack .../07-libnvidia-encode-390_390.48-0ubuntu2_amd64.deb ... Unpacking libnvidia-encode-390:amd64 (390.48-0ubuntu2) ... Selecting previously unselected package libnvidia-fbc1-390:amd64. Preparing to unpack .../08-libnvidia-fbc1-390
[Desktop-packages] [Bug 1765053] Re: Errors were encountered while processing: /tmp/apt-dpkg-install-x8YVfC/03-libnvidia-compute-390_390.48-0ubuntu2_i386.deb
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu-drivers-common (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1765053 Title: Errors were encountered while processing: /tmp/apt-dpkg-install- x8YVfC/03-libnvidia-compute-390_390.48-0ubuntu2_i386.deb Status in nvidia-graphics-drivers-390 package in Ubuntu: In Progress Status in ubuntu-drivers-common package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 source package in Bionic: In Progress Status in ubuntu-drivers-common source package in Bionic: Confirmed Bug description: Using Ubuntu MATE 18.04 daily ubuntu-drivers fails to install the nvidia 390 drivers. Here is what I captured on stdout. $ sudo ubuntu-drivers autoinstall Reading package lists... Done Building dependency tree Reading state information... Done The following package was automatically installed and is no longer required: gnome-session-common Use 'sudo apt autoremove' to remove it. The following additional packages will be installed: libnvidia-cfg1-390 libnvidia-common-390 libnvidia-compute-390 libnvidia-compute-390:i386 libnvidia-decode-390 libnvidia-decode-390:i386 libnvidia-encode-390 libnvidia-encode-390:i386 libnvidia-fbc1-390 libnvidia-fbc1-390:i386 libnvidia-gl-390 libnvidia-gl-390:i386 libnvidia-ifr1-390 libnvidia-ifr1-390:i386 libwayland-client0:i386 libwayland-server0:i386 libxnvctrl0 nvidia-compute-390 nvidia-compute-no-dkms-390 nvidia-compute-utils-390 nvidia-dkms-390 nvidia-kernel-source-390 nvidia-settings nvidia-utils-390 screen-resolution-extra xserver-xorg-video-nvidia-390 The following NEW packages will be installed libnvidia-cfg1-390 libnvidia-common-390 libnvidia-compute-390 libnvidia-compute-390:i386 libnvidia-decode-390 libnvidia-decode-390:i386 libnvidia-encode-390 libnvidia-encode-390:i386 libnvidia-fbc1-390 libnvidia-fbc1-390:i386 libnvidia-gl-390 libnvidia-gl-390:i386 libnvidia-ifr1-390 libnvidia-ifr1-390:i386 libwayland-client0:i386 libwayland-server0:i386 libxnvctrl0 nvidia-compute-390 nvidia-compute-no-dkms-390 nvidia-compute-utils-390 nvidia-dkms-390 nvidia-driver-390 nvidia-kernel-source-390 nvidia-settings nvidia-utils-390 screen-resolution-extra xserver-xorg-video-nvidia-390 0 to upgrade, 27 to newly install, 0 to remove and 0 not to upgrade. Need to get 0 B/85.3 MB of archives. After this operation, 365 MB of additional disk space will be used. Selecting previously unselected package libnvidia-cfg1-390:amd64. (Reading database ... 258596 files and directories currently installed.) Preparing to unpack .../00-libnvidia-cfg1-390_390.48-0ubuntu2_amd64.deb ... Unpacking libnvidia-cfg1-390:amd64 (390.48-0ubuntu2) ... Selecting previously unselected package libnvidia-common-390. Preparing to unpack .../01-libnvidia-common-390_390.48-0ubuntu2_all.deb ... Unpacking libnvidia-common-390 (390.48-0ubuntu2) ... Selecting previously unselected package libnvidia-compute-390:amd64. Preparing to unpack .../02-libnvidia-compute-390_390.48-0ubuntu2_amd64.deb ... Unpacking libnvidia-compute-390:amd64 (390.48-0ubuntu2) ... Selecting previously unselected package libnvidia-compute-390:i386. Preparing to unpack .../03-libnvidia-compute-390_390.48-0ubuntu2_i386.deb ... Unpacking libnvidia-compute-390:i386 (390.48-0ubuntu2) ... dpkg: error processing archive /tmp/apt-dpkg-install-x8YVfC/03-libnvidia-compute-390_390.48-0ubuntu2_i386.deb (--unpack): trying to overwrite shared '/etc/OpenCL/vendors/nvidia.icd', which is different from other instances of package libnvidia-compute-390:i386 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Selecting previously unselected package libnvidia-decode-390:amd64. Preparing to unpack .../04-libnvidia-decode-390_390.48-0ubuntu2_amd64.deb ... Unpacking libnvidia-decode-390:amd64 (390.48-0ubuntu2) ... Selecting previously unselected package libnvidia-decode-390:i386. Preparing to unpack .../05-libnvidia-decode-390_390.48-0ubuntu2_i386.deb ... Unpacking libnvidia-decode-390:i386 (390.48-0ubuntu2) ... Selecting previously unselected package libnvidia-encode-390:i386. Preparing to unpack .../06-libnvidia-encode-390_390.48-0ubuntu2_i386.deb ... Unpacking libnvidia-encode-390:i386 (390.48-0ubuntu2) ... Selecting previously unselected package libnvidia-encode-390:amd64. Preparing to unpack .../07-libnvidia-encode-390_390.48-0ubuntu2_amd64.deb ... Unpacking libnvidia-encode-390:amd64 (390.48-0ubuntu2) ... Selecting previously unselected package libnvidia-fbc1-390:amd64. Preparing to unpack .../08-libnvidia-fbc1-390_390.48-0ubuntu2_amd64.deb ... Unpacking libnvidia-fbc1-390:amd64 (390.48-0ubuntu2) ... Selecting previously unselected package libnvidia-fbc1-390:i386.
[Desktop-packages] [Bug 1766659] Re: pppoeconf should not be in Ubuntu Desktop
@ Will Cooke Please confirm. ** Also affects: pppoeconf (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pppoeconf in Ubuntu. https://bugs.launchpad.net/bugs/1766659 Title: pppoeconf should not be in Ubuntu Desktop Status in pppoeconf package in Ubuntu: New Status in ubuntu-meta package in Ubuntu: New Bug description: pppoeconf should not be in Ubuntu Desktop As network-manager on Ubuntu Desktop configures PPP connection all by itself, with ppp recommends and ppp-dev build-depends. pppoeconf should not ship in Ubuntu desktop in Bionic, and thus should not pull in ifupdown on Ubuntu Desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pppoeconf/+bug/1766659/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1758563] Re: Blocked at gdm login screen on 18.04 if user password has a circumflex accent
I am running the latest beta of 18.04 with upgrades. Since installation I try to log in the gdm screen and receive the message, "Sorry, that didn't work. Please try again." I get the same message when I try to log in to Update Manager. The app and gdm screen launch if I enter my password again. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1758563 Title: Blocked at gdm login screen on 18.04 if user password has a circumflex accent Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Triaged Bug description: Hi, I have a bug since the recent updates on Ubuntu 18.04 (post 10th March): when the user password contains a circumflex accent, like "û", access is denied even if password entered is correct and I stay blocked in a loop at gdm login screen - error message (translated from French): "Sorry, it doesn't work, please try again". Even after modifying it on recovery mode with passwd without û, it stays blocked. Only way to solve it is to reinstall. Graphic card: [AMD/ATI] Cape Verde XT [Radeon HD 7770/8760 / R7 250X] Kernel driver in use: radeon Kernel modules: radeon, amdgpu Steps to reproduce : I did a fresh and new install with 18.04 daily iso from 21st March, formatting / and /home with following user password: Ubuntu42 At startup, I could log successfully both on Xorg and Wayland sessions. Then I modified and tested those passwords, with all of them I could again boot and connect, on Xorg and Wayland: ArchLinux43 LinuxMint@28 KDENeon=51 Fedora_1984 But the last one made me blocked at the gdm login screen: Debianû74 Here unable to modify it on recovery session, error message in French: "erreur de manipulation du jeton d'authentification". Also unable to launch terminal: CTRl Alt F1 refreshes the screen, but F2, F3... F12 freezes it! I only can update in chroot with lie USB. I had to again format and reinstall, with a password without any circumflex accent. How and when I discovered it : On 10th March, I ran since many weeks the alpha version of Ubuntu 18.04, with a password having a "û" inside, which had always worked fine. I did an update, cumulating the last 3 weeks before. On next startup, when I typed my password, both on Xorg and Wayland sessions, no error message but no desktop, nothing appeared but a few seconds later I was back on login screen. I could well log in on terminal (Ctrl Alt F2) or chroot with a live USB, and do the last updates in the next days, but nothing changed. On console, if I ran "startx" I got the message "timeout in locking authority file" and "fatal server error: cannot open log file ./local/share/xorg/Xorg.0.log Both / and /home were not full - more than 60% space available, verified with df -Th ; echo ; df -Ti I tried to reinstall Ubuntu with daily live of 15th March, formatting / but not /home as it was protected by ecryptfs and I didn't save some files, using same user name and password, still blocked. So I copied the /home and .Private folders to another disk to try later recover them, reinstall again, formatting both / and /home, always with my usual password having a "û" (I verified French language, keyboard with French activated, upper case, symbols... OK). This time, again both for Xorg or Wayland sessions, at gdm login I did not success to connect, I got an error message "Désolé ça n'a pas fonctionné, veuillez réessayer", I tried to modify the password in recovery mode, with no special characters nor accents, but still blocked at gdm. And no terminal available with Ctrl Alt F2... On 23rd March, I re-reinstalled all Ubuntu, formatting / and /home, this time with daily iso from 21st March, but with a modification: to avoid any misconfiguration with languages on live USB, I chose a very easy password, only with normal letters and numbers. On startup, yes, finally I could log at gdm on default Xorg session and enter desktop ! I went to my user configuration, changed to put my usual password (with an "û"), and bam, back to the future, still blocked at gdm screen on restart, either on Xorg or Wayland, Ctr Alt F2 not working. It made me understand that the bug came from a special character in my password, then I tried the different ones explained on top of this report to discover it was "û". To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1758563/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1766575] Re: Drop libnss-myhostname recommends
** Also affects: gnome-control-center (Ubuntu Bionic) Importance: Low Status: New ** Changed in: gnome-control-center (Ubuntu Bionic) Status: New => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1766575 Title: Drop libnss-myhostname recommends Status in gnome-control-center package in Ubuntu: Fix Committed Status in gnome-control-center source package in Bionic: Fix Committed Bug description: gnome-control-center added a Recommends: libnss-myhostname years ago so that it was possible to easily change the hostname in the Details panel. That dependency no longer appears to be needed since we switched to systemd-resolved. Testing Done In both Debian Testing and Ubuntu 18.04 (Debian doesn't use systemd-resolved so seemed useful to try there too). sudo apt uninstall libnss-myhostname Restart Open the GNOME Settings app (gnome-control-center) In the left sidebar, click Devices Enter a different Device name in the block Open a terminal and verify that the hostname has been changed. In Debian, running `ping new-hostname` fails, but it works fine in Ubuntu. Other Info == There are concerns about having libnss-myhostname in the default install. See comment 5 at LP: #1741277. See also LP: #1162475 Note that /etc/hosts isn't updated regardless of whether libnss-myhostname is installed (I guess my bug description there was wrong but there was some kind of bug there.) Regression Potential To quote from the manpage: https://manpages.debian.org/unstable/nss-resolve "Note that systemd-resolved will synthesize DNS resource records in a few cases, for example for "localhost" and the current hostname, see systemd-resolved(8) for the full list. This duplicates the functionality of nss-myhostname(8), but it is still recommended (see examples below) to keep nss-myhostname configured in /etc/nsswitch.conf, to keep those names resolveable if systemd- resolved is not running." Ubuntu uses systemd-resolved by default and it's expected that users who don't want to use that will need to configure some things manually. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1766575/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1766638] [NEW] graphical
Public bug reported: problem during boot process ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44 Uname: Linux 4.4.0-66-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.16 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Tue Apr 24 17:14:29 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation 82945G/GZ Integrated Graphics Controller [8086:2772] (rev 02) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 82945G/GZ Integrated Graphics Controller [1043:817a] InstallationDate: Installed on 2016-06-15 (677 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1) MachineType: ASUSTek Computer INC. P5GZ-MX ProcEnviron: LANGUAGE=hu PATH=(custom, no user) LANG=hu_HU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-66-generic root=UUID=083e9287-55a1-422d-86ba-6839368c9db8 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/30/2006 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0601 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5GZ-MX dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: ASUSTek Computer INC. dmi.chassis.version: Rev 1.xx dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0601:bd11/30/2006:svnASUSTekComputerINC.:pnP5GZ-MX:pvrRev1.xx:rvnASUSTeKComputerINC.:rnP5GZ-MX:rvrRev1.xx:cvnASUSTekComputerINC.:ct3:cvrRev1.xx: dmi.product.name: P5GZ-MX dmi.product.version: Rev 1.xx dmi.sys.vendor: ASUSTek Computer INC. version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Tue Apr 24 17:10:36 2018 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputMicrosoft Microsoft 3-Button Mouse with IntelliEye(TM) MOUSE, id 8 inputAT Translated Set 2 keyboard KEYBOARD, id 9 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1825 vendor FUS xserver.version: 2:1.18.4-0ubuntu0.7 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug compiz-0.9 i386 ubuntu xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1766638 Title: graphical Status in xorg package in Ubuntu: New Bug description: problem during boot process ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44 Uname: Linux 4.4.0-66-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.16 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Tue Apr 24 17:14:29 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation 82945G/GZ Integrated Graphics Controller [8086:2772] (rev 02) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 82945G/GZ Integrated Graphics Controller [1043:817a] InstallationDate: Installed on 2016-06-15 (677 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1) MachineType: ASUSTek Computer INC. P5GZ-MX ProcEnviron: LANGUAGE=hu PATH=(custom, no user) LANG=hu_HU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-66-generic root=UUID=083e9287-55a1-422d-86ba-6839368c9db8 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/30/2006 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0601
[Desktop-packages] [Bug 1766575] Re: Drop libnss-myhostname recommends
** Description changed: gnome-control-center added a Recommends: libnss-myhostname years ago so that it was possible to easily change the hostname in the Details panel. That dependency no longer appears to be needed. Testing Done In both Debian Testing and Ubuntu 18.04 (Debian doesn't use systemd-resolved so seemed useful to try there too). sudo apt uninstall libnss-myhostname Restart Open the GNOME Settings app (gnome-control-center) In the left sidebar, click Devices Enter a different Device name in the block Open a terminal and verify that the hostname has been changed. Other Info == There are concerns about having libnss-myhostname in the default install. See comment 5 at LP: #1741277. See also LP: #1162475 Note that /etc/hosts isn't updated regardless of whether libnss-myhostname is installed (I guess my bug description there was wrong but there was some kind of bug there.) Regression Potential - I believe most distros do install libnss-myhostname as recommended by https://www.freedesktop.org/wiki/Software/systemd/hostnamed/ As long as things appear to work, maybe we can ignore that recommendation. + To quote from the manpage: + + https://manpages.debian.org/unstable/nss-resolve + + "Note that systemd-resolved will synthesize DNS resource records in a + few cases, for example for "localhost" and the current hostname, see + systemd-resolved(8) for the full list. This duplicates the functionality + of nss-myhostname(8), but it is still recommended (see examples below) + to keep nss-myhostname configured in /etc/nsswitch.conf, to keep those + names resolveable if systemd-resolved is not running." + + Ubuntu uses systemd-resolved by default and it's expected that users who + don't want to use that will need to configure some things manually. ** Description changed: gnome-control-center added a Recommends: libnss-myhostname years ago so that it was possible to easily change the hostname in the Details panel. - That dependency no longer appears to be needed. + That dependency no longer appears to be needed since we switched to + systemd-resolved. Testing Done In both Debian Testing and Ubuntu 18.04 (Debian doesn't use systemd-resolved so seemed useful to try there too). sudo apt uninstall libnss-myhostname Restart Open the GNOME Settings app (gnome-control-center) In the left sidebar, click Devices Enter a different Device name in the block Open a terminal and verify that the hostname has been changed. + + In Debian, running `ping new-hostname` fails, but it works fine in + UBuntu. Other Info == There are concerns about having libnss-myhostname in the default install. See comment 5 at LP: #1741277. See also LP: #1162475 Note that /etc/hosts isn't updated regardless of whether libnss-myhostname is installed (I guess my bug description there was wrong but there was some kind of bug there.) Regression Potential To quote from the manpage: https://manpages.debian.org/unstable/nss-resolve "Note that systemd-resolved will synthesize DNS resource records in a few cases, for example for "localhost" and the current hostname, see systemd-resolved(8) for the full list. This duplicates the functionality of nss-myhostname(8), but it is still recommended (see examples below) to keep nss-myhostname configured in /etc/nsswitch.conf, to keep those names resolveable if systemd-resolved is not running." Ubuntu uses systemd-resolved by default and it's expected that users who don't want to use that will need to configure some things manually. ** Description changed: gnome-control-center added a Recommends: libnss-myhostname years ago so that it was possible to easily change the hostname in the Details panel. That dependency no longer appears to be needed since we switched to systemd-resolved. Testing Done In both Debian Testing and Ubuntu 18.04 (Debian doesn't use systemd-resolved so seemed useful to try there too). sudo apt uninstall libnss-myhostname Restart Open the GNOME Settings app (gnome-control-center) In the left sidebar, click Devices Enter a different Device name in the block Open a terminal and verify that the hostname has been changed. In Debian, running `ping new-hostname` fails, but it works fine in - UBuntu. + Ubuntu. Other Info == There are concerns about having libnss-myhostname in the default install. See comment 5 at LP: #1741277. See also LP: #1162475 Note that /etc/hosts isn't updated regardless of whether libnss-myhostname is installed (I guess my bug description there was wrong but there was some kind of bug there.) Regression Potential To quote from the manpage: https://manpages.debian.org/unstable/nss-resolve "Note that systemd-resolved will synthesize DNS resourc
[Desktop-packages] [Bug 1766575] Re: Drop libnss-myhostname recommends
** Branch linked: lp:~ubuntu-desktop/gnome-control-center/ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1766575 Title: Drop libnss-myhostname recommends Status in gnome-control-center package in Ubuntu: Fix Committed Status in gnome-control-center source package in Bionic: Fix Committed Bug description: gnome-control-center added a Recommends: libnss-myhostname years ago so that it was possible to easily change the hostname in the Details panel. That dependency no longer appears to be needed since we switched to systemd-resolved. Testing Done In both Debian Testing and Ubuntu 18.04 (Debian doesn't use systemd-resolved so seemed useful to try there too). sudo apt uninstall libnss-myhostname Restart Open the GNOME Settings app (gnome-control-center) In the left sidebar, click Devices Enter a different Device name in the block Open a terminal and verify that the hostname has been changed. In Debian, running `ping new-hostname` fails, but it works fine in Ubuntu. Other Info == There are concerns about having libnss-myhostname in the default install. See comment 5 at LP: #1741277. See also LP: #1162475 Note that /etc/hosts isn't updated regardless of whether libnss-myhostname is installed (I guess my bug description there was wrong but there was some kind of bug there.) Regression Potential To quote from the manpage: https://manpages.debian.org/unstable/nss-resolve "Note that systemd-resolved will synthesize DNS resource records in a few cases, for example for "localhost" and the current hostname, see systemd-resolved(8) for the full list. This duplicates the functionality of nss-myhostname(8), but it is still recommended (see examples below) to keep nss-myhostname configured in /etc/nsswitch.conf, to keep those names resolveable if systemd- resolved is not running." Ubuntu uses systemd-resolved by default and it's expected that users who don't want to use that will need to configure some things manually. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1766575/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1762885] Re: SDDM starts to black screen on hybrid laptops withe modern NVidia cards
*** This bug is a duplicate of bug 1764005 *** https://bugs.launchpad.net/bugs/1764005 ** Also affects: nvidia-prime (Ubuntu) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-390 (Ubuntu) Status: Confirmed => Fix Released ** Changed in: nvidia-prime (Ubuntu) Status: New => Fix Released ** Changed in: sddm (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1762885 Title: SDDM starts to black screen on hybrid laptops withe modern NVidia cards Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-prime package in Ubuntu: Fix Released Status in sddm package in Ubuntu: Fix Released Bug description: Hybrid laptop with an NVidia 960M video card boots to a black SDDM screen when the NVidia card enabled (using the NVidia 384 and 390.xx drivers). Nouveau drivers fail to boot. Switching to Intel drivers (sudo prime-select intel), SDDM loads/runs just fine. Removing the "quiet" option from grub boot shows Simple Display Manager starting without error when NVidia is enabled. Unsure how to provide additional useful information. Ctrl-Alt-f1, logging in via the terminal, and startx enables normal desktop use. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: sddm 0.17.0-1ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CurrentDesktop: KDE Date: Tue Apr 10 19:15:16 2018 InstallationDate: Installed on 2018-03-14 (27 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180312) SourcePackage: sddm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1762885/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1731911] Re: Xwayland crashed with SIGABRT in OsAbort() from AbortServer() from FatalError() from xwl_read_events() from ospoll_wait()
I'm still seeing crashes under the exact same conditions as since October. When I do ubuntu-bug on the crash file it directs me here, so I think this bug may still be getting triggered for me at least. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1731911 Title: Xwayland crashed with SIGABRT in OsAbort() from AbortServer() from FatalError() from xwl_read_events() from ospoll_wait() Status in mutter package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Status in mutter package in Fedora: Fix Committed Bug description: https://errors.ubuntu.com/problem/c27f5c4fef272640ec1027318712f0434c7c8857 --- no idea how to reproduce ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: xwayland 2:1.19.5-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME-Greeter:GNOME Date: Mon Nov 13 13:55:16 2017 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.13.0-15-generic, x86_64: installed bbswitch, 0.8, 4.13.0-16-generic, x86_64: installed ExecutablePath: /usr/bin/Xwayland ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 3rd Gen Core processor Graphics Controller [1043:1507] InstallationDate: Installed on 2013-09-03 (1531 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902) MachineType: ASUSTeK COMPUTER INC. UX32VD ProcCmdline: /usr/bin/Xwayland :1024 -rootless -terminate -core -listen 4 -listen 5 -displayfd 6 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/false ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=1004226d-a9db-46c7-bd28-eca0806c12f2 ro pcie_aspm=force drm.vblankoffdelay=1 i915.semaphores=1 init=/lib/systemd/systemd-bootchart Signal: 6 SourcePackage: xorg-server StacktraceTop: OsAbort () ?? () FatalError () ?? () ?? () Title: Xwayland crashed with SIGABRT in OsAbort() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 01/29/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX32VD.214 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX32VD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX32VD.214:bd01/29/2013:svnASUSTeKCOMPUTERINC.:pnUX32VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX32VD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.85-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1731911/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1181666] Re: gnome-shell randomly blocks mouse clicks from working in app windows
Here is reported: https://github.com/passingthru67/workspaces-to- dock/issues/134 ** Bug watch added: github.com/passingthru67/workspaces-to-dock/issues #134 https://github.com/passingthru67/workspaces-to-dock/issues/134 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1181666 Title: gnome-shell randomly blocks mouse clicks from working in app windows Status in GNOME Shell: Confirmed Status in Ubuntu GNOME: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: Under GNOME 3, the use of the mouse-click stops occasionally, though I can still move the mouse around and can still click on items in the Activities screen and the top-bar. I can use alt-tab to cycle windows and can still type into already- active textboxes in windows, but I cannot click within the windows, and the mouse is not picked up at all by the windows. I can open the alt-f2 "run command" dialogue, but cannot type into it. The workaround I'm using is to open terminal (ctrl-alt-T) and run "gnome-shell -r", and restarting that command every time I have the problem again. Please ask if there's anything I forgot to mention. ADDITIONAL: The error tends to happen randomly, but it seems to happen upon opening a new window, changing windows, closing windows, or opening the activities pane (whether a change of window is thus instigated or not) ADDITIONAL 2: (sorry, it's early) The other workaround is to log out and to log in again, but that is also less than ideal ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: gnome-shell 3.6.3.1-0ubuntu6 ProcVersionSignature: Ubuntu 3.8.0-22.33-generic 3.8.11 Uname: Linux 3.8.0-22-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Sun May 19 07:02:18 2013 DisplayManager: gdm GsettingsChanges: b'org.gnome.desktop.interface' b'clock-show-date' b'true' b'org.gnome.desktop.interface' b'clock-show-seconds' b'true' b'org.gnome.desktop.interface' b'document-font-name' b"'Sans 10'" b'org.gnome.desktop.interface' b'font-name' b"'Cantarell 10'" b'org.gnome.desktop.interface' b'monospace-font-name' b"'Ubuntu Mono 12'" InstallationDate: Installed on 2013-05-04 (14 days ago) InstallationMedia: Ubuntu-GNOME 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1181666/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1181666] Re: gnome-shell randomly blocks mouse clicks from working in app windows
In my case the bug was on gnome-shell extension "workspaces-to- dock"(https://github.com/passingthru67/workspaces-to-dock). I found this log entry: Apr 24 10:33:35 hostname gnome-shell[2736]: JS ERROR: TypeError: this._porthole is undefined#012myThumbnailsBox<._getPreferredWidth@/home/username/.local/share /gnome-shell/extensions/workspaces-to- d...@passingthru67.gmail.com/myWorkspaceThumbnail.js:1065:17#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012ThumbnailsSlider<._getPreferredWidth@/home/username/.local/share /gnome-shell/extensions/workspaces-to- d...@passingthru67.gmail.com/dockedWorkspaces.js:194:37#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012_init/<@resource:///org/gnome/shell/ui/layout.js:209:17#012_loadBackground/signalId<@resource:///org/gnome/shell/ui/layout.js:593:13#012_emit@resource:///org/gnome/gjs/modules/signals.js:128:27#012_init/id<@resource:///org/gnome/shell/ui/background.js:523:17 After remove /home/username/.local/share/gnome-shell/extensions /workspaces-to-d...@passingthru67.gmail.com and restart session the behavior described here disappears. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1181666 Title: gnome-shell randomly blocks mouse clicks from working in app windows Status in GNOME Shell: Confirmed Status in Ubuntu GNOME: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: Under GNOME 3, the use of the mouse-click stops occasionally, though I can still move the mouse around and can still click on items in the Activities screen and the top-bar. I can use alt-tab to cycle windows and can still type into already- active textboxes in windows, but I cannot click within the windows, and the mouse is not picked up at all by the windows. I can open the alt-f2 "run command" dialogue, but cannot type into it. The workaround I'm using is to open terminal (ctrl-alt-T) and run "gnome-shell -r", and restarting that command every time I have the problem again. Please ask if there's anything I forgot to mention. ADDITIONAL: The error tends to happen randomly, but it seems to happen upon opening a new window, changing windows, closing windows, or opening the activities pane (whether a change of window is thus instigated or not) ADDITIONAL 2: (sorry, it's early) The other workaround is to log out and to log in again, but that is also less than ideal ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: gnome-shell 3.6.3.1-0ubuntu6 ProcVersionSignature: Ubuntu 3.8.0-22.33-generic 3.8.11 Uname: Linux 3.8.0-22-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Sun May 19 07:02:18 2013 DisplayManager: gdm GsettingsChanges: b'org.gnome.desktop.interface' b'clock-show-date' b'true' b'org.gnome.desktop.interface' b'clock-show-seconds' b'true' b'org.gnome.desktop.interface' b'document-font-name' b"'Sans 10'" b'org.gnome.desktop.interface' b'font-name' b"'Cantarell 10'" b'org.gnome.desktop.interface' b'monospace-font-name' b"'Ubuntu Mono 12'" InstallationDate: Installed on 2013-05-04 (14 days ago) InstallationMedia: Ubuntu-GNOME 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1181666/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1754693] Re: Xwayland crashed with SIGABRT in st_renderbuffer_delete()
I just ran updates on my 18.04 machine today also and can confirm Slack is working under Wayland Here is my Slack Snap Version: commands: - slack snap-id: JUJH91Ved74jd4ZgJCpzMBtYbPOzTlsD tracking: stable refreshed: 2018-03-30T18:45:51-04:00 installed: 3.1.1 (6) 98MB classic If someone can tell me how to print out the affected Wayland component version I can post that also. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1754693 Title: Xwayland crashed with SIGABRT in st_renderbuffer_delete() Status in mesa package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/01a80d2110a46f6b6d857ce814079646e695f4ca --- Steps to reproduce: Install 'slack' snap: sudo snap install slack --classic Run slack: slack Instacrash. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: xwayland 2:1.19.6-1ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CompizPlugins: [core,composite,opengl,decor,mousepoll,grid,vpswitch,compiztoolbox,imgpng,gnomecompat,regex,move,place,resize,snap,unitymtgrabhandles,wall,animation,session,expo,workarounds,fade,ezoom,scale,unityshell] CompositorRunning: None CurrentDesktop: GNOME Date: Fri Mar 9 10:31:06 2018 DistUpgraded: 2018-03-06 13:58:47,853 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu EcryptfsInUse: Yes ExecutablePath: /usr/bin/Xwayland ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1043:8534] MachineType: ASUS All Series ProcCmdline: /usr/bin/Xwayland :0 -rootless -terminate -accessx -core -listen 4 -listen 5 -displayfd 6 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic root=UUID=cd444f9d-672e-4d7b-aea8-657fff0ea1f4 ro quiet splash crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M vt.handoff=1 Signal: 6 SourcePackage: xorg-server StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so Title: Xwayland crashed with SIGABRT UpgradeStatus: Upgraded to bionic on 2018-03-06 (2 days ago) UserGroups: adm admin audio cdrom chroot-admin dialout dip egbuild fax floppy fuse libvirt libvirtd lpadmin lxd plugdev sambashare sudo tape video wireshark dmi.bios.date: 10/27/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2702 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2702:bd10/27/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-PRO:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.90-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Mon Oct 16 18:18:18 2017 xserver.configfi
[Desktop-packages] [Bug 1735929] Re: security problems with incorrect permissions for ubuntu 17.10
I tested the 2018-04-21 daily image, and the permissions on ~/.config and ~/.local are OK now. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1735929 Title: security problems with incorrect permissions for ubuntu 17.10 Status in dconf: Fix Released Status in gnome-session: Fix Released Status in d-conf package in Ubuntu: Fix Released Status in dconf package in Ubuntu: Triaged Status in gnome-session package in Ubuntu: Fix Released Status in session-migration package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Fix Released Status in d-conf source package in Bionic: Fix Released Status in dconf source package in Bionic: Triaged Status in gnome-session source package in Bionic: Fix Released Status in session-migration source package in Bionic: Fix Released Status in xorg-server source package in Bionic: Fix Released Bug description: The release of Ubuntu you are using (lsb_release -rd): Description: Ubuntu 17.10 Release: 17.10 This is a fresh installation of Ubuntu 17.10 from the mini.iso. I select only default options + [Ubuntu Desktop] installation. What you expected to happen: My home folder contains the following folders with correct and safe permissions after the first login: drwx-- 11 user user 4096 Dec 2 17:40 .config drwx-- 3 user user 4096 Dec 2 17:39 .local What happened instead: I received these folders after the first login: drwxr-xr-x 11 user user 4096 Dec 2 17:40 .config drwxr-xr-x 3 user user 4096 Dec 2 17:39 .local It is not safe. Any user can access to my .config folders and read for example my mail databases I'm trying to create a new user...: sudo useradd -m user2 sudo passwd user2 ... and login then. It has the same problem: drwxr-xr-x 10 user2 user2 4096 Dec 2 19:44 .config drwxr-xr-x 3 user2 user2 4096 Dec 2 19:44 .local To manage notifications about this bug go to: https://bugs.launchpad.net/dconf/+bug/1735929/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1766575] [NEW] Drop libnss-myhostname recommends
Public bug reported: gnome-control-center added a Recommends: libnss-myhostname years ago so that it was possible to easily change the hostname in the Details panel. That dependency no longer appears to be needed. Testing Done In both Debian Testing and Ubuntu 18.04 (Debian doesn't use systemd-resolved so seemed useful to try there too). sudo apt uninstall libnss-myhostname Restart Open the GNOME Settings app (gnome-control-center) In the left sidebar, click Devices Enter a different Device name in the block Open a terminal and verify that the hostname has been changed. Other Info == There are concerns about having libnss-myhostname in the default install. See comment 5 at LP: #1741277. See also LP: #1162475 Note that /etc/hosts isn't updated regardless of whether libnss-myhostname is installed (I guess my bug description there was wrong but there was some kind of bug there.) Regression Potential I believe most distros do install libnss-myhostname as recommended by https://www.freedesktop.org/wiki/Software/systemd/hostnamed/ As long as things appear to work, maybe we can ignore that recommendation. ** Affects: gnome-control-center (Ubuntu) Importance: Low Status: New ** Tags: bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1766575 Title: Drop libnss-myhostname recommends Status in gnome-control-center package in Ubuntu: New Bug description: gnome-control-center added a Recommends: libnss-myhostname years ago so that it was possible to easily change the hostname in the Details panel. That dependency no longer appears to be needed. Testing Done In both Debian Testing and Ubuntu 18.04 (Debian doesn't use systemd-resolved so seemed useful to try there too). sudo apt uninstall libnss-myhostname Restart Open the GNOME Settings app (gnome-control-center) In the left sidebar, click Devices Enter a different Device name in the block Open a terminal and verify that the hostname has been changed. Other Info == There are concerns about having libnss-myhostname in the default install. See comment 5 at LP: #1741277. See also LP: #1162475 Note that /etc/hosts isn't updated regardless of whether libnss-myhostname is installed (I guess my bug description there was wrong but there was some kind of bug there.) Regression Potential I believe most distros do install libnss-myhostname as recommended by https://www.freedesktop.org/wiki/Software/systemd/hostnamed/ As long as things appear to work, maybe we can ignore that recommendation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1766575/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [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()
I checked and I don't get this bug any longer 2018-04-18 23:41 GMT+02:00 Launchpad Bug Tracker <1724...@bugs.launchpad.net >: > This bug was fixed in the package mutter - 3.28.1-1 > > --- > mutter (3.28.1-1) unstable; urgency=medium > > [ Jeremy Bicha ] > * New upstream release > - Fix window button spacing when display is scaled (LP: #1725133) > * Bump Standards-Version to 4.1.4 > > [ Marco Trevisan (Treviño) ] > * Add patches proposed upstream: > * theme-frames-Use-surface-device-scale-instead-of-cairo_sc.patch: > - theme, frames: Use surface device scale instead of cairo_scale > (LP: #1764554) > * theme-use-gtk_render_icon_suface-to-paint-button-icon.patch: > - theme: use gtk_render_icon_suface to paint button icon > (LP: #1764558) > * theme-load-icons-as-Gtk-does-with-fallback-and-RTL-suppor.patch: > - theme: load icons as Gtk does with fallback and RTL support > * clutter-Smooth-out-master-clock-to-smooth-visuals.patch: > - clutter: Smooth out master clock to smooth visuals > * core-Return-1-if-meta_window_get_monitor-is-called-on-an-.patch: > - core: Return -1 if meta_window_get_monitor is called on an > unmanaged window (LP: #1724439) > * backends-Move-MetaOutput-crtc-field-into-private-struct.patch: > - backends: Move MetaOutput::crtc field into private struct > (LP: #1703668) > * backends-Add-logical-monitor-monitor-output-crtc-ref-chai.patch: > - backends: Add logical monitor -> monitor -> output -> crtc ref > chain (LP: #1703668) > > -- Jeremy Bicha Mon, 16 Apr 2018 22:35:14 -0400 > > ** Changed in: mutter (Ubuntu Bionic) >Status: In Progress => Fix Released > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1761149). > 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() > > Status in Mutter: > In Progress > Status in gnome-shell package in Ubuntu: > Fix Released > Status in mutter package in Ubuntu: > Fix Released > Status in gnome-shell source package in Bionic: > Fix Released > Status in mutter source package in Bionic: > Fix Released > > Bug description: > https://errors.ubuntu.com/problem/3e662975e4b7e6829b9d68d1c2b06f > 429e44c854 > > --- > > left virtual box to update win10 came back and got error message > > ProblemType: Crash > DistroRelease: Ubuntu 17.10 > Package: gnome-shell 3.26.1-0ubuntu3 > ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 > Uname: Linux 4.13.0-16-generic x86_64 > NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia > ApportVersion: 2.20.7-0ubuntu3 > Architecture: amd64 > CrashCounter: 1 > CurrentDesktop: ubuntu:GNOME > Date: Tue Oct 17 23:37:32 2017 > DisplayManager: gdm3 > ExecutablePath: /usr/bin/gnome-shell > InstallationDate: Installed on 2017-04-18 (182 days ago) > InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 > (20170412) > ProcCmdline: /usr/bin/gnome-shell > ProcEnviron: >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_US.UTF-8 >SHELL=/bin/bash > SegvAnalysis: >Segfault happened at: 0x7feb2ed42d94 : > mov0x18(%rax),%eax >PC (0x7feb2ed42d94) ok >source "0x18(%rax)" (0x0018) not located in a known VMA region > (needed readable region)! >destination "%eax" ok > SegvReason: reading NULL VMA > Signal: 11 > SourcePackage: gnome-shell > StacktraceTop: >meta_window_get_monitor () from /usr/lib/x86_64-linux-gnu/ > libmutter-1.so.0 >ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6 >ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6 >?? () from /usr/lib/libgjs.so.0 >?? () from /usr/lib/libgjs.so.0 > Title: gnome-shell crashed with SIGSEGV in meta_window_get_monitor() > UpgradeStatus: No upgrade log present (probably fresh install) > UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo > > To manage notifications about this bug go to: > https://bugs.launchpad.net/mutter/+bug/1724439/+subscriptions > -- Skickat från min nya mailadress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in 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() Status in Mutter: In Progress Status in gnome-shell package in Ubuntu: Fix Released Status in mutter package in Ubuntu: Fix Released Status in gnome-shell source package in Bionic: Fix Released Status in mutter source package in Bionic: Fix Released Bug description: https://errors.ubuntu.com/problem/3e662975e4b7e6829b9d68d1c2b06f429e44c854 --- left virtual box to update win10 came b
Re: [Desktop-packages] [Bug 1748450] Re: gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_default_handler() from default_log_handler(message="Connection to xwayland lost") from g_logv() f
I no longer get this error after update. On Sun, Apr 15, 2018, 11:56 PM Daniel van Vugt < daniel.van.v...@canonical.com> wrote: > This report: > > https://errors.ubuntu.com/problem/7576bbf83cb88a0b3a870e1371dd86416b23c4b3 > > suggests the wave of unreadable stack traces this week was perhaps due > to an update to glib2.0, because: > > /lib/x86_64-linux-gnu/libglib-2.0.so.0.5600.0 (deleted) > > So they are almost certainly all duplicates of this bug, unreadable due > to the upgrade procedure of glib2.0. The good news is that the wave > should stop after everyone has upgraded. > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1763917). > https://bugs.launchpad.net/bugs/1748450 > > Title: > gnome-shell crashed with SIGTRAP in _g_log_abort() from > g_log_default_handler() from default_log_handler(message="Connection > to xwayland lost") from g_logv() from g_log() from > > Status in gnome-shell package in Ubuntu: > Triaged > Status in gnome-shell source package in Bionic: > Triaged > > Bug description: > *** This is a duplicate of bug 1505409, but is being kept separate so > as to automatically collect duplicate reports since the stacktrace > signature has changed recently. Any resolution and discussion should > occur in bug 1505409. *** > > See also: > > https://errors.ubuntu.com/problem/8ef857b2fe07d60742cd02d7d8f988f78ecd0f95 > > ProblemType: Crash > DistroRelease: Ubuntu 18.04 > Package: gnome-shell 3.26.2-0ubuntu2 > ProcVersionSignature: Ubuntu 4.13.0-33.36-generic 4.13.13 > Uname: Linux 4.13.0-33-generic x86_64 > ApportVersion: 2.20.8-0ubuntu8 > Architecture: amd64 > CurrentDesktop: GNOME-Greeter:GNOME > Date: Thu Feb 8 23:50:23 2018 > DisplayManager: gdm3 > ExecutablePath: /usr/bin/gnome-shell > GsettingsChanges: > > InstallationDate: Installed on 2016-03-21 (690 days ago) > InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 > (20160307) > ProcCmdline: /usr/bin/gnome-shell > ProcEnviron: >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_US.UTF-8 >SHELL=/bin/false > Signal: 5 > SourcePackage: gnome-shell > StacktraceTop: >() at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 >_XIOError () at /usr/lib/x86_64-linux-gnu/libX11.so.6 >_XEventsQueued () at /usr/lib/x86_64-linux-gnu/libX11.so.6 >XPending () at /usr/lib/x86_64-linux-gnu/libX11.so.6 >() at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 > Title: gnome-shell crashed with signal 5 > UpgradeStatus: Upgraded to bionic on 2018-02-08 (0 days ago) > UserGroups: > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1748450/+subscriptions > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1748450 Title: gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_default_handler() from default_log_handler(message="Connection to xwayland lost") from g_logv() from g_log() from Status in gnome-shell package in Ubuntu: Triaged Status in gnome-shell source package in Bionic: Triaged Bug description: [Impact] * Xwayland is failing frequently (not crashing), which triggers a crash in gnome-shell because gnome-shell doesn't know how to survive after Xwayland has reset itself. * The frequent gnome-shell crashes create frequent problem reports and annoying dialogs for users, after they log in to an apparently working gnome-shell. * This affects Xorg sessions too, because the gdm login screen itself is a Wayland session. And Xorg users will see the problem dialog after they have logged into a Xorg session. * The fix simply converts the crash into a silent exit (as decided by Gnome upstream). This avoids the mountain of crash reports and annoying error dialogs at least. It does not fix the root causes that remain in Xwayland, but this is considered acceptable because there really isn't a bug in gnome-shell here other than it doesn't know how to survive without a connection to Xwayland. * For users of Xorg sessions, like bionic default, this is a full fix as Xorg users will never get an Xwayland instance after logging in. And hence the Xwayland bugs are irrelevant. [Test Case] * Just install bionic, use it lightly and reboot a few times. * Observe crash files are left in /var/crash and problem report dialogs after logging in. [Regression Potential] Medium. The fix does not really change the structure of the existing error handling, only changes it from a core dump into a silent exit. For Xorg users this should be invisible as the affected login screen restarts automatically. [Other Info] This is a whole class of gnome-shell crash which includes bug 1505409, bug 1748450 and bug 1556601. All three should be considered the same crash for the sake of this SRU. J
[Desktop-packages] [Bug 1766558] [NEW] Multiple Flashing Mouse Pointers
Public bug reported: When I move the mouse, multiple flashing mouse pointers appear on the display. Sometimes they disappear in a few seconds and sometimes they stay for minutes or until I've moved the proper pointer to another app. This only happens when I'm using a USB SSD to boot and start Ubuntu. I presume that the bug is in xorg. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-38.43~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-38-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Apr 24 12:16:00 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:22b1] (rev 21) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Device [8086:2060] InstallationDate: Installed on 2018-04-23 (1 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-38-generic.efi.signed root=UUID=60d11562-04a9-4e59-a472-fc95e75a2877 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/14/2018 dmi.bios.vendor: Intel Corp. dmi.bios.version: PYBSWCEL.86A.0069.2018.0314.1745 dmi.board.name: NUC5CPYB dmi.board.vendor: Intel Corporation dmi.board.version: H61145-404 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrPYBSWCEL.86A.0069.2018.0314.1745:bd03/14/2018:svn:pn:pvr:rvnIntelCorporation:rnNUC5CPYB:rvrH61145-404:cvn:ct3:cvr: version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Mon Apr 23 19:05:01 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.5-0ubuntu2~16.04.1 xserver.video_driver: modeset ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1766558 Title: Multiple Flashing Mouse Pointers Status in xorg package in Ubuntu: New Bug description: When I move the mouse, multiple flashing mouse pointers appear on the display. Sometimes they disappear in a few seconds and sometimes they stay for minutes or until I've moved the proper pointer to another app. This only happens when I'm using a USB SSD to boot and start Ubuntu. I presume that the bug is in xorg. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-38.43~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-38-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Apr 24 12:16:00 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:22b1] (rev 21) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Device [8086:2060] InstallationDate: Installed on 2018-04-23 (1 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-38-generic.efi.signed root=UUID=60d11562-04a9-4e59-a472-fc95e75a2877 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/14/2018 dmi.bios.vendor: Intel Corp. dmi.bios.version: PYBSWCEL.86A.0069.2018.0314.1745 dmi.board.name: NUC5CPYB dmi.board.vendor: Intel Corporation dmi.board.version: H61145-404 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrPYBSWCEL.86A.0069.2018.0314.1745:bd03/14/2018:svn:pn:pvr:rvnIntelCorporation:rnNUC5CPYB:rvrH61145-404:cv
[Desktop-packages] [Bug 1752053] Re: nvidia-390 fails to boot graphical display
Same issue with nvidia-396, I must config lightdm as default display manager. After that I can login to ubuntu and ubuntu-unity sessions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1752053 Title: nvidia-390 fails to boot graphical display Status in mesa package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Bug description: I'm using Bionic with the new 4.15 kernel. I've been using the nvidia-384 driver with no problem for a while. Today I issued "sudo apt-get upgrade" and I was prompted to upgrade the nvidia driver to the nvidia-390. After installing the driver and rebooting, I was only able to boot in to the tty terminal. The graphical display failed to boot. I have had similar problems with nvidia driver version 390 with Arch Linux and with Open Suse Tumbleweed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1766554] [NEW] tulip unicode symbols in subject escape dedicated place in the message list
Public bug reported:
Received message with Subject header as following:
Subject:
=?utf-8?Q?=F0=9F=8C=B7=F0=9F=8C=B7=F0=9F=8C=B7Pasir=C5=ABpink_dovana_MAMAI_i=C5=A1anksto=F0=9F=8C=B7=F0=9F=8C=B7=C2=A0=F0=9F=8C=B7?=
Got screwed message list as shown in screenshot attached
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: thunderbird 1:52.7.0+build1-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
Uname: Linux 4.15.0-15-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.9-0ubuntu6
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: kaspar 1812 F pulseaudio
BuildID: 20180416164209
Channel: Unavailable
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr 24 13:48:14 2018
ForcedLayersAccel: False
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
IncompatibleExtensions: Thunderbird (default) -
{972ce4c6-7e08-4474-a285-3208198ce6fd}
InstallationDate: Installed on 2018-04-11 (13 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180409)
IpRoute:
default via 172.17.2.254 dev wlp4s0
default via 172.17.2.254 dev wlp4s0 proto dhcp metric 600
172.17.2.0/24 dev wlp4s0 proto kernel scope link src 172.17.2.83
172.17.2.0/24 dev wlp4s0 proto kernel scope link src 172.17.2.83 metric 600
PrefSources: prefs.js
Profiles: Profile0 (Default) - LastVersion=52.7.0/20180416164209 (In use)
RunningIncompatibleAddons: True
SourcePackage: thunderbird
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/05/2018
dmi.bios.vendor: LENOVO
dmi.bios.version: N27ET23W (1.09 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20L9002GMH
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias:
dmi:bvnLENOVO:bvrN27ET23W(1.09):bd03/05/2018:svnLENOVO:pn20L9002GMH:pvrThinkPadT580:rvnLENOVO:rn20L9002GMH:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad T580
dmi.product.name: 20L9002GMH
dmi.product.version: ThinkPad T580
dmi.sys.vendor: LENOVO
** Affects: thunderbird (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug bionic
** Attachment added: "Screenshot"
https://bugs.launchpad.net/bugs/1766554/+attachment/5126450/+files/thunderbird-bug.png
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to thunderbird in Ubuntu.
https://bugs.launchpad.net/bugs/1766554
Title:
tulip unicode symbols in subject escape dedicated place in the message
list
Status in thunderbird package in Ubuntu:
New
Bug description:
Received message with Subject header as following:
Subject:
=?utf-8?Q?=F0=9F=8C=B7=F0=9F=8C=B7=F0=9F=8C=B7Pasir=C5=ABpink_dovana_MAMAI_i=C5=A1anksto=F0=9F=8C=B7=F0=9F=8C=B7=C2=A0=F0=9F=8C=B7?=
Got screwed message list as shown in screenshot attached
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: thunderbird 1:52.7.0+build1-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
Uname: Linux 4.15.0-15-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.9-0ubuntu6
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: kaspar 1812 F pulseaudio
BuildID: 20180416164209
Channel: Unavailable
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr 24 13:48:14 2018
ForcedLayersAccel: False
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
IncompatibleExtensions: Thunderbird (default) -
{972ce4c6-7e08-4474-a285-3208198ce6fd}
InstallationDate: Installed on 2018-04-11 (13 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180409)
IpRoute:
default via 172.17.2.254 dev wlp4s0
default via 172.17.2.254 dev wlp4s0 proto dhcp metric 600
172.17.2.0/24 dev wlp4s0 proto kernel scope link src 172.17.2.83
172.17.2.0/24 dev wlp4s0 proto kernel scope link src 172.17.2.83 metric 600
PrefSources: prefs.js
Profiles: Profile0 (Default) - LastVersion=52.7.0/20180416164209 (In use)
RunningIncompatibleAddons: True
SourcePackage: thunderbird
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/05/2018
dmi.bios.vendor: LENOVO
dmi.bios.version: N27ET23W (1.09 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20L9002GMH
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias:
dmi:bvnLENOVO:bvrN27ET23W(1.09):bd03/05/2018:svnLENOVO:pn20L9002GMH:pvrThinkPadT580:rvnLENOVO:rn20L9002GMH:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad T580
dmi.product.name: 20L9002GMH
dmi.product.version: ThinkPad T580
dmi.sys.
[Desktop-packages] [Bug 1752053] Re: nvidia-390 fails to boot graphical display
I still encounter this issue after upgrade my bionic to the latest update. The only way to boot to graphic shell is config to using lightdm as default. Now I'm in unity session and try to install nvidia-396 to see if it fix this issue. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1752053 Title: nvidia-390 fails to boot graphical display Status in mesa package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Bug description: I'm using Bionic with the new 4.15 kernel. I've been using the nvidia-384 driver with no problem for a while. Today I issued "sudo apt-get upgrade" and I was prompted to upgrade the nvidia driver to the nvidia-390. After installing the driver and rebooting, I was only able to boot in to the tty terminal. The graphical display failed to boot. I have had similar problems with nvidia driver version 390 with Arch Linux and with Open Suse Tumbleweed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1766307] Re: Crash low-graphics mode
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xorg (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1766307 Title: Crash low-graphics mode Status in xorg package in Ubuntu: Confirmed Bug description: Since friday, 4/20/2018, when I did an upgrade in Ubuntu, I receive an error message: The system is running in low-graphics mode Your screen, graphics cards, and input device settings could not be detected correctly. You will need to configure these yourself. Then, using tab key, I press OK, then I choose try the default, and everything works fine after this. But this is very annoying. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-39-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Mon Apr 23 13:54:49 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: nvidia-304, 304.135, 4.13.0-38-generic, x86_64: installed nvidia-304, 304.135, 4.13.0-39-generic, x86_64: installed GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] 2nd Generation Core Processor Family Integrated Graphics Controller [1462:7788] InstallationDate: Installed on 2017-09-14 (221 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Lsusb: Bus 002 Device 003: ID 04b3:310c IBM Corp. Wheel Mouse Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: MSI MS-7788 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-39-generic root=UUID=2f8e3cb0-6af1-44b7-b3fa-ea29171c708d ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/18/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V2.3 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H61M-P31 (G3) (MS-7788) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV2.3:bd01/18/2012:svnMSI:pnMS-7788:pvr1.0:rvnMSI:rnH61M-P31(G3)(MS-7788):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7788 dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Mon Apr 23 12:51:59 2018 xserver.configfile: default xserver.devices: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.5-0ubuntu2~16.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1766307/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1766137] Re: [regression] Password accepted but login fails (blank purple screen and mouse pointer only)
Hi, As discussed with duflu on irc, here are the steps I took to reproduce and produce a log: 1. Enable debug in /etc/gdm3/custom.conf 2. Reboot 3. From other laptop; ssh wendigo journalctl -f 4. Intentially login with a faulty password first, which made GDM just prompt as normal 5. Login with the correct password, which caused the purple screen + mouse 6. Copy the log up to this point 7. Press a bunch of ctrl+alt+fn+f-key combos until I got back to login screen 8. Login as normal, ctrl+c the SSH session and scp the file. ** Attachment added: "wendigo journalctl" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1766137/+attachment/5126446/+files/journalctl -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1766137 Title: [regression] Password accepted but login fails (blank purple screen and mouse pointer only) Status in gdm3 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Bug description: Trying to log into my session (Gnome, Xorg), if I enter the wrong password before entering it correctly, the session doesn't load and I get a purple screen, a mouse cursor, and an invisible but clickable menu in the top right. If I enter it correctly the first time, there is no problem. I've replicated this from a fresh boot, after logging out and after 'sudo service gdm restart' from the Ctrl-Alt-F4 console. This is a fresh install, and didn't occur when I was using a previous install of 18.04 (until Friday). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Apr 22 20:31:13 2018 InstallationDate: Installed on 2018-04-22 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180421.1) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1766137/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1763751] Re: Poor performance of the Wayland session in Ubuntu 18.04
** Package changed: mesa (Ubuntu) => gnome-shell (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1763751 Title: Poor performance of the Wayland session in Ubuntu 18.04 Status in gnome-shell package in Ubuntu: Confirmed Bug description: Poor performance of the Wayland session in Ubuntu 18.04 with AMD A10-7300 in Acer E5-551G. No problems with Xorg session. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1763751/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1707352] Re: the change from libsane to libsane1 broke many (all?) 3rd party plug-ins for sane
I confirm that the workaround worked for my Bionic with an Epson V300, having finally found this thread after a week's agony. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1707352 Title: the change from libsane to libsane1 broke many (all?) 3rd party plug- ins for sane Status in sane-backends package in Ubuntu: Fix Released Status in sane-backends source package in Artful: Fix Released Status in sane-backends package in Debian: New Bug description: Note to SRU Team The first proposed fix (1.0.27-1~experimental2ubuntu2) failed because it needed to be a versioned Provides, not just a Provides. Impact == 1) The Debian maintainer renamed libsane to libsane1-experimental "to match with the soname". This apparently fixes a Lintian warning, but makes installing 3rd-party plug-ins hard, as they typically depend on "libsane", not on "libsane1". The first try to add a "Provides: libsane" to libsane1 (which created a virtual package) didn't make drivers installable that claim to depend on a minimum version of libsane as virtual packages are ignored in this case. 2) The soname change might be justified by the new version breaking (several? most?) 3rd party plug-ins even if the library version number doesn't indicate any bigger change than any ordinary new version of the library - which might indicate that this phenomenon might be an upstream bug. libsane 1.0.25 in zesty includes libsane.so.1.25 libsane1 1.0.27 in artful includes libsane.so.1.27 It is to note that depending on the manufacturer for many old scanners there won't be new versions of the plug-ins that are recompiled like this. Test Case = Visit http://support.epson.net/linux/en/iscan_c.html Download the amd64 deb .tar.gz Unzip it. Install the iscan .deb from the core folder. It won't install before this SRU because it Depends: libsane Regression Potential The fix here was proposed to the Debian maintainer in July but there's been virtually zero response on it. In the meantime the workaround that was proposed initially has started to result in automatically uninstalling gtk - which makes the system basically useless. It doesn't seem like adding the Provides will make things any worse for third-party drivers but it has a goodme chance of making things better for some. Original Bug Report === I don't know if that can be prevented in the long run. But both brscan (for my brother scanner) and iscan (for my epson scanners) have been broken by the change from libsane to libsane1. For iscan I have unpackaged the debian package, changed the dependency it contains from libsane to libsane1 and installed the changed package. But even then my epson scanners no more work leaving me without any scanner => Reporting a bug. Impossibility of workarounds Just installing an old version of libsane is impossible as it uninstalls libgtk (which depends on libsane1 which conflicts with libsane) making the system basically useless. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: libsane1 1.0.27-1~experimental1ubuntu2 Uname: Linux 4.13.0-041300rc2-lowlatency x86_64 ApportVersion: 2.20.6-0ubuntu4 Architecture: amd64 Date: Sat Jul 29 08:38:15 2017 EcryptfsInUse: Yes SourcePackage: sane-backends UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1707352/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1754693] Re: Xwayland crashed with SIGABRT in st_renderbuffer_delete()
On an up-to-date 18.04 machine today I can no longer reproduce this crash. Could someone else confirm the same? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1754693 Title: Xwayland crashed with SIGABRT in st_renderbuffer_delete() Status in mesa package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/01a80d2110a46f6b6d857ce814079646e695f4ca --- Steps to reproduce: Install 'slack' snap: sudo snap install slack --classic Run slack: slack Instacrash. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: xwayland 2:1.19.6-1ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CompizPlugins: [core,composite,opengl,decor,mousepoll,grid,vpswitch,compiztoolbox,imgpng,gnomecompat,regex,move,place,resize,snap,unitymtgrabhandles,wall,animation,session,expo,workarounds,fade,ezoom,scale,unityshell] CompositorRunning: None CurrentDesktop: GNOME Date: Fri Mar 9 10:31:06 2018 DistUpgraded: 2018-03-06 13:58:47,853 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu EcryptfsInUse: Yes ExecutablePath: /usr/bin/Xwayland ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1043:8534] MachineType: ASUS All Series ProcCmdline: /usr/bin/Xwayland :0 -rootless -terminate -accessx -core -listen 4 -listen 5 -displayfd 6 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic root=UUID=cd444f9d-672e-4d7b-aea8-657fff0ea1f4 ro quiet splash crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M vt.handoff=1 Signal: 6 SourcePackage: xorg-server StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so Title: Xwayland crashed with SIGABRT UpgradeStatus: Upgraded to bionic on 2018-03-06 (2 days ago) UserGroups: adm admin audio cdrom chroot-admin dialout dip egbuild fax floppy fuse libvirt libvirtd lpadmin lxd plugdev sambashare sudo tape video wireshark dmi.bios.date: 10/27/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2702 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2702:bd10/27/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-PRO:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.90-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Mon Oct 16 18:18:18 2017 xserver.configfile: default xserver.devices: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.3-1ubuntu1.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1754693/+subscriptions -- Mailing list: htt
[Desktop-packages] [Bug 1766137] Re: [regression] Password accepted but login fails (blank purple screen and mouse pointer only)
Daniel thanks for your work here to try and get this filed correctly. If the logs are different for me and for this bug then perhaps my bug is different? Ray Strode (upstream) thinks the key part of my log is ``` Apr 23 17:43:40 adam-thinkpad-t430 gdm3[2997]: GdmSession: Emitting 'session-opened' signal [...] Apr 23 17:43:40 adam-thinkpad-t430 gdm3[2997]: GdmSession: external connection closed ``` Chris A, please could you (as Ray suggested to me) put `Enable=true` (without backticks (``)) in the `[debug]` section of `/etc/gdm/custom.conf`, reboot, reproduce and post the updated logs? Maybe then we'll be able to see if this issue is the same as mine or not (and if not then maybe Chris A's problem needs a separate upstream bug). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1766137 Title: [regression] Password accepted but login fails (blank purple screen and mouse pointer only) Status in gdm3 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Bug description: Trying to log into my session (Gnome, Xorg), if I enter the wrong password before entering it correctly, the session doesn't load and I get a purple screen, a mouse cursor, and an invisible but clickable menu in the top right. If I enter it correctly the first time, there is no problem. I've replicated this from a fresh boot, after logging out and after 'sudo service gdm restart' from the Ctrl-Alt-F4 console. This is a fresh install, and didn't occur when I was using a previous install of 18.04 (until Friday). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Apr 22 20:31:13 2018 InstallationDate: Installed on 2018-04-22 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180421.1) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1766137/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1683383] Re: Keyboard layout change on hotkeys press instead of release and do not work well with shortcuts (reopen)
@nrbrtx It seems that the patch don't work with the french layouts. It work fine with all the other layouts i tested. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1683383 Title: Keyboard layout change on hotkeys press instead of release and do not work well with shortcuts (reopen) Status in X.Org X server: Confirmed Status in xorg-server package in Ubuntu: Confirmed Status in xorg package in Debian: New Bug description: From duplicate bug 1720364 report. Steps to reproduce: 1. Install ubuntu-mate-desktop on Ubuntu 16.04 LTS with HWE (Xorg 1.19.5), or 17.10 or 18.04 LTS. 2. Set-up two keyboard layouts - English and Russian 3. Set as keyboard layout switcher in mate-control-center 4. Try to use shortcuts starting from : 4.1. Open Firefox, open new tab, go to some site in it, close tab, try to click to restore closed tab. 4.2. Open mate-terminal, try to open new tab with , or copy (), or paste (). 4.3. Open pluma, write some text, try to navigate in it with . Expected results: switches keyboard layout, shortcuts starting from work normally. Actual results: switches keyboard layout, shortcuts starting from do not work. Notes: 1. Ubuntu 16.04 LTS (Xorg 1.18.4) with Marco and Compton work normally with keyboard layout switcher. 2. This problem was discovered before on 13.10, 14.04 and other modern versions with GNOME desktop (Metacity and Compiz) - see bug 1245473. --- Original description below: This is a reopen of bug #36812, which has reappeared in Kubuntu 17.04 Zesty Zapus. This is a bug about shortcuts mapped to combinations which include each other. For example, if we have Ctrl+Shift (for keyboard layout) and Ctrl+Shift+N (to open a new terminal), then we are practically unable to use the second shortcut; this is what happens: Ctrl press (nothing happens) Shift press (keyboard layout change) N (a simple N appears, since a shortcut has already fired) The expected behavior is to fire shortcuts on the release (not on press) of the special keys (ctrl,shift,alt, etc) which is also how Windows behave. This is a serious problem for bilingual layouts, typically using Alt+Shift or Ctrl+Shift for keyboard layout change. Apparently, the bug has reappeared after the patch that used to fix the problem (208_switch_on_release.diff) has been removed from X.Org 1.19 packages. There is an updated patch in the upstream ticket https://bugs.freedesktop.org/show_bug.cgi?id=865 (link to the attachment: https://bugs.freedesktop.org/attachment.cgi?id=129861). ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: xserver-xorg-core 2:1.19.3-1ubuntu1 Uname: Linux 4.9.0-22.1-liquorix-amd64 x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 CurrentDesktop: KDE Date: Mon Apr 17 17:46:35 2017 InstallationDate: Installed on 2015-05-01 (716 days ago) InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: xorg-server UpgradeStatus: Upgraded to zesty on 2017-04-16 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1683383/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1763157] Re: Network manager PPTP VPN connection very unstable, connection breaks (lost packets)
To further proof the issue I now tested the same scenario with another wifi usb module in the same network/router setup, this time the driver module was rt2800usb. Same result. Before using a vpn (pppt) connection my network connection seemed very stable, I had no connection losses and performance was quite good. Again establishing the vpn-ppt-connection with network manager (like above) works basically, I can open a few websites successfully for instance, but after a very short time the connection is completely faulty. This time the connection stayed functional about 30 seconds, then I got packet loss and no more network connections worked anymore. Like before though, network manager showed the vpn connection is still "active" (established) albeit no more packets were transferred. I attached the new error/debug log for this test. ** Attachment added: "syslog_pptp_vpn_debug_rt2800usb" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1763157/+attachment/5126432/+files/syslog_pptp_vpn_debug_rt2800usb -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1763157 Title: Network manager PPTP VPN connection very unstable, connection breaks (lost packets) Status in network-manager package in Ubuntu: New Bug description: The PPTP-VPN connection over WiFi of my Ubuntu Xenial installation is extremely unstable, repeated loss of connection (100% packet loss), easily reproducible using network manager. The wlan module is r8712u (Realtek Semiconductor Corp. RTL8191SU 802.11n WLAN Adapter). (System: Linux Mint 18.3 Sylvia, xenial, linux 4.13.0-38-generic #43~16.04.1-Ubuntu SMP, x86_64) Wlan connection seems very stable basically but as soon as I start using vpn it quickly is broken after a very short time. Example pptp vpn is ca.hide.me but I tested other connections as well with the same result. Network manager does not show a no-more-working connection visually (regarding the symbols all looks good) but it is quickly noticeable that no more internet sites are reacting as soon as the bug situation occurs (which is very often, normally only after a few seconds!). The vpn sites are working good with other clients, also the wlan (WPA2) and wlan router itself at my home are working fine, several other client system (Windows, Mobile, another Linux) are working without any issue, thus it is definitely this specific network manager wlan/pptp-vpn client with the r8712u module causing the trouble. ### here I try to demonstrate a typical situation, first stable later the error I start with resetting wlan module r8712u first, letting network manager establish a new connection to my wireless lan at 20:50-20:51h. Connection is working fine so far. (Module output: insmod /lib/modules/4.13.0-38-generic/kernel/drivers/staging/rtl8712/r8712u.ko) Making a lot of traffic, parallel download etc. stress test, everything is stable so it does not seem that the wireless lan has issues but only the vpn client on top of it... After disconnecting the broken vpn, the normal wlan traffic (internet sites etc.) are working again. But to show the case here I demonstrate first the working base scenario and then the occuring bug situation. First working situation before the bug occurs (starting with wlan reset first): $ dmesg |tail -n20 [ 4869.764646] usbcore: deregistering interface driver r8712u [ 4870.152409] usb 3-2: reset high-speed USB device number 2 using ehci-pci [ 4871.333150] r8712u: module is from the staging directory, the quality is unknown, you have been warned. [ 4871.334319] r8712u: register rtl8712_netdev_ops to netdev_ops [ 4871.334324] usb 3-2: r8712u: USB_SPEED_HIGH with 4 endpoints [ 4871.334830] usb 3-2: r8712u: Boot from EFUSE: Autoload OK [ 4871.873153] usb 3-2: r8712u: CustomerID = 0x [ 4871.873158] usb 3-2: r8712u: MAC Address from efuse = 00:0d:81:af:00:fb [ 4871.873161] usb 3-2: r8712u: Loading firmware from "rtlwifi/rtl8712u.bin" [ 4871.873713] usbcore: registered new interface driver r8712u [ 4871.877915] r8712u 3-2:1.0 wlx000d81af00fb: renamed from wlan0 [ 4871.907478] IPv6: ADDRCONF(NETDEV_UP): wlx000d81af00fb: link is not ready [ 4872.652953] r8712u 3-2:1.0 wlx000d81af00fb: 1 RCR=0x153f00e [ 4872.653709] r8712u 3-2:1.0 wlx000d81af00fb: 2 RCR=0x553f00e [ 4874.164838] IPv6: ADDRCONF(NETDEV_UP): wlx000d81af00fb: link is not ready [ 4874.206830] IPv6: ADDRCONF(NETDEV_UP): wlx000d81af00fb: link is not ready [ 4887.083087] IPv6: ADDRCONF(NETDEV_UP): enp3s0: link is not ready [ 4887.088383] IPv6: ADDRCONF(NETDEV_UP): wlx000d81af00fb: link is not ready [ 4887.121475] IPv6: ADDRCONF(NETDEV_UP): wlx000d81af00fb: link is not ready [ 4895.089398] IPv6: ADDRCONF(NETDEV_CHANGE): wlx000d81af00fb: link becomes ready $ nmcli d DEVICE TYPE
[Desktop-packages] [Bug 1762952] Re: Alternative shortcut for layout switching Alt+Shift unexpectedly set by default
@Jeremy: Since you maintain Tweaks, does it possibly ring a bell? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1762952 Title: Alternative shortcut for layout switching Alt+Shift unexpectedly set by default Status in gnome-control-center package in Ubuntu: New Status in gnome-shell package in Ubuntu: Confirmed Bug description: Version: Ubuntu 18.04 Final Beta with default Gnome Shell included in 18.04 Steps to reproduce: 1. Define two keyboard input methods in Settings -> Region & Language -> Input Sources 2. Open several applications 3. Observe that application windows can be iterated with Alt + Tab 4. Once application window iteration was begun with Alt + Tab, try to iterate backwards with Alt + Shift + Tab. 5. Try to change keyboard input method switching hotkeys in Settings -> Region & Language -> Input Sources -> Options. 6. Observe that Keyboard shortcut for "Alternative switch to next source" is set to "Alt + Shift" and that keyboard shortcuts can only be changed in Settings -> Devices -> Keyboard -> Keyboard Shortcuts. 7. Observe that the shortcut for "Alternative switch to next source" is not available for configuration in Settings -> Devices -> Keyboard -> Keyboard Shortcuts. Actual state: * Performing step 4 does not select the previous app in application switcher but instead changes keyboard input method. Expected state: * The shortcut for "Alternative switch to next source" can be changed and / or deactivated in Settings -> Devices -> Keyboard -> Keyboard Shortcuts. Notes: * The above was working fine in Ubuntu 17.10. I assume "Alternative switch to next source" did not exist in that version of Gnome Shell. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1762952/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
