[Bug 1775329] Re: Feature request: Add a handler for CVE URLs
Ok so any guidance as to how to proceed - Jeremy do you have a preference for how this should work? Would you like it to also support Debian in a similar manner and link to the Debian CVE tracker? In this case would you prefer runtime detection (via say /etc/os-release) or compile-time selection of which CVE tracker to link to? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1775329 Title: Feature request: Add a handler for CVE URLs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1775329/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1784473] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1784473/+attachment/5169831/+files/RfKill.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1784473 Title: [radeon] Ubuntu boots to a black screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784473/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1784473] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1784473/+attachment/5169825/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1784473 Title: [radeon] Ubuntu boots to a black screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784473/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1784473] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1784473/+attachment/5169826/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1784473 Title: [radeon] Ubuntu boots to a black screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784473/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1784473] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1784473/+attachment/5169829/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1784473 Title: [radeon] Ubuntu boots to a black screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784473/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1784473] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1784473/+attachment/5169833/+files/WifiSyslog.txt ** Attachment removed: "WifiSyslog.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784473/+attachment/5169833/+files/WifiSyslog.txt ** Attachment removed: "AlsaInfo.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784473/+attachment/5169820/+files/AlsaInfo.txt ** Attachment removed: "CRDA.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784473/+attachment/5169821/+files/CRDA.txt ** Attachment removed: "UdevDb.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784473/+attachment/5169832/+files/UdevDb.txt ** Attachment removed: "RfKill.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784473/+attachment/5169831/+files/RfKill.txt ** Attachment removed: "PulseList.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784473/+attachment/5169830/+files/PulseList.txt ** Attachment removed: "ProcModules.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784473/+attachment/5169829/+files/ProcModules.txt ** Attachment removed: "ProcInterrupts.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784473/+attachment/5169828/+files/ProcInterrupts.txt ** Attachment removed: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784473/+attachment/5169827/+files/ProcCpuinfoMinimal.txt ** Attachment removed: "Lsusb.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784473/+attachment/5169826/+files/Lsusb.txt ** Attachment removed: "Lspci.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784473/+attachment/5169825/+files/Lspci.txt ** Attachment removed: "CurrentDmesg.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784473/+attachment/5169822/+files/CurrentDmesg.txt ** Attachment removed: "Dependencies.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784473/+attachment/5169823/+files/Dependencies.txt ** Attachment removed: "IwConfig.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784473/+attachment/5169824/+files/IwConfig.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1784473 Title: [radeon] Ubuntu boots to a black screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784473/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1784473] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1784473/+attachment/5169830/+files/PulseList.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1784473 Title: [radeon] Ubuntu boots to a black screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784473/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1784473] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1784473/+attachment/5169832/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1784473 Title: [radeon] Ubuntu boots to a black screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784473/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1784473] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1784473/+attachment/5169827/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1784473 Title: [radeon] Ubuntu boots to a black screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784473/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1784473] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1784473/+attachment/5169828/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1784473 Title: [radeon] Ubuntu boots to a black screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784473/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1784473] Re: [radeon] Ubuntu boots to a black screen
apport information ** Description changed: After a fresh install of ubuntu 18.04LTS(dual booted with windows 7) when I selected ubuntu from the grub menu to boot into the OS. But I got a black screen I waited for few seconds but I was still at black screen. So, I forced shutdown the laptop. Again in second attempt to login I got black screen this time I waited for more than a minute and pressed power button once which suspended the pc then I pressed enter and I was presented with login screen. To solve the problem I followed this guide https://askubuntu.com/questions/1029624/ubuntu-18-04-live-boot-leads-to- blank-screen and changed quiet splash to nomodeset quiet splash. After applying this fix there was no black screen at the time of login, but the laptop started to freeze randomly even when left idle for more than 30 mins it would freeze. I had force shutdown each time and this happened very frequently. I again changed nomodeset quiet splash to quiet splash, which again leads to black screen after selecting ubuntu from the grub menu. I also did RAM test using Memtest86 from GRUB and everything was fine systemd-analyze time Startup finished in 6.015s (kernel) + 1min 26.820s (userspace) = 1min 32.836s graphical.target reached after 1min 25.472s in userspace ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jul 31 00:17:48 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.10, 4.15.0-29-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Sumo [Radeon HD 6480G] [1002:9648] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Sumo [Radeon HD 6480G] [103c:3564] InstallationDate: Installed on 2018-07-26 (4 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Hewlett-Packard HP Pavilion g4 Notebook PC ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic root=UUID=007c6619-ca84-4c0f-8b16-7fa740dc0c3e ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/24/2014 dmi.bios.vendor: Insyde dmi.bios.version: F.6D dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 3564 dmi.board.vendor: Hewlett-Packard dmi.board.version: 21.47 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.6D:bd01/24/2014:svnHewlett-Packard:pnHPPaviliong4NotebookPC:pvr06911320461610100:rvnHewlett-Packard:rn3564:rvr21.47:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP Pavilion g4 Notebook PC dmi.product.version: 06911320461610100 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-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 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: amit 2479 F pulseaudio /dev/snd/controlC0: amit 2479 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-07-26 (4 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Hewlett-Packard HP Pavilion g4 Notebook PC Package: mutter 3.28.2-2~ubuntu18.04.1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic root=UUID=007c6619-ca84-4c0f-8b16-7fa740dc0c3e ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
[Bug 1784473] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1784473/+attachment/5169821/+files/CRDA.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1784473 Title: [radeon] Ubuntu boots to a black screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784473/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1784473] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1784473/+attachment/5169823/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1784473 Title: [radeon] Ubuntu boots to a black screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784473/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1784473] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1784473/+attachment/5169824/+files/IwConfig.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1784473 Title: [radeon] Ubuntu boots to a black screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784473/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1784473] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1784473/+attachment/5169822/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1784473 Title: [radeon] Ubuntu boots to a black screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784473/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1784473] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1784473/+attachment/5169818/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1784473 Title: [radeon] Ubuntu boots to a black screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784473/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1784473] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1784473/+attachment/5169819/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1784473 Title: [radeon] Ubuntu boots to a black screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784473/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1784473] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1784473/+attachment/5169813/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1784473 Title: [radeon] Ubuntu boots to a black screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784473/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1784473] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1784473/+attachment/5169817/+files/RfKill.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1784473 Title: [radeon] Ubuntu boots to a black screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784473/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1784473] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1784473/+attachment/5169812/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1784473 Title: [radeon] Ubuntu boots to a black screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784473/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1784473] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1784473/+attachment/5169815/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1784473 Title: [radeon] Ubuntu boots to a black screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784473/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1784473] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1784473/+attachment/5169814/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1784473 Title: [radeon] Ubuntu boots to a black screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784473/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1784473] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1784473/+attachment/5169816/+files/PulseList.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1784473 Title: [radeon] Ubuntu boots to a black screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784473/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1784473] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1784473/+attachment/5169807/+files/CRDA.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1784473 Title: [radeon] Ubuntu boots to a black screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784473/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1784473] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1784473/+attachment/5169810/+files/IwConfig.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1784473 Title: [radeon] Ubuntu boots to a black screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784473/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1784473] Re: [radeon] Ubuntu boots to a black screen
I think they are not same. In bug https://bugs.launchpad.net/bugs/1782347 the user says he needs to boot with nomodeset for both the installed and liveCD. I can boot with bootable pendrive just fine without using nomodeset. Also the user says "GDM3 will not boot (the screen will keep on flashing in semi-textual mode, with a white mouse arrow stuck)." I on the other hand get a black screen(no mouse cursor or flashing) after selecting ubuntu from grub menu. Work-around for this is that I wait for a minute and press the power button to suspend and press any key to get to the login screen. So I think GDM3 Boots. I aslo tried your advice "Please edit your /etc/gdm3/custom.conf and comment out: WaylandEnable=false" but it didn't work and had to boot with work-around I mentioned above. Also adding nomodeset allowed me to boot without black screen, but it randomly froze the laptop forcing to do a force shutdown. So I removed nomodeset. ** Tags added: apport-collected ** Description changed: After a fresh install of ubuntu 18.04LTS(dual booted with windows 7) when I selected ubuntu from the grub menu to boot into the OS. But I got a black screen I waited for few seconds but I was still at black screen. So, I forced shutdown the laptop. Again in second attempt to login I got black screen this time I waited for more than a minute and pressed power button once which suspended the pc then I pressed enter and I was presented with login screen. To solve the problem I followed this guide https://askubuntu.com/questions/1029624/ubuntu-18-04-live-boot-leads-to- blank-screen and changed quiet splash to nomodeset quiet splash. After applying this fix there was no black screen at the time of login, but the laptop started to freeze randomly even when left idle for more than 30 mins it would freeze. I had force shutdown each time and this happened very frequently. I again changed nomodeset quiet splash to quiet splash, which again leads to black screen after selecting ubuntu from the grub menu. I also did RAM test using Memtest86 from GRUB and everything was fine systemd-analyze time Startup finished in 6.015s (kernel) + 1min 26.820s (userspace) = 1min 32.836s graphical.target reached after 1min 25.472s in userspace ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jul 31 00:17:48 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.10, 4.15.0-29-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Sumo [Radeon HD 6480G] [1002:9648] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Sumo [Radeon HD 6480G] [103c:3564] InstallationDate: Installed on 2018-07-26 (4 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Hewlett-Packard HP Pavilion g4 Notebook PC ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic root=UUID=007c6619-ca84-4c0f-8b16-7fa740dc0c3e ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/24/2014 dmi.bios.vendor: Insyde dmi.bios.version: F.6D dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 3564 dmi.board.vendor: Hewlett-Packard dmi.board.version: 21.47 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.6D:bd01/24/2014:svnHewlett-Packard:pnHPPaviliong4NotebookPC:pvr06911320461610100:rvnHewlett-Packard:rn3564:rvr21.47:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP Pavilion g4 Notebook PC dmi.product.version: 06911320461610100 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1
[Bug 1784473] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1784473/+attachment/5169811/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1784473 Title: [radeon] Ubuntu boots to a black screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784473/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1784473] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1784473/+attachment/5169808/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1784473 Title: [radeon] Ubuntu boots to a black screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784473/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1784473] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1784473/+attachment/5169809/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1784473 Title: [radeon] Ubuntu boots to a black screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784473/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1784473] AlsaInfo.txt
apport information ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1784473/+attachment/5169806/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1784473 Title: [radeon] Ubuntu boots to a black screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784473/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1710637] Re: Input falls through to gdm3 and terminates the session on Ctrl+C after udevadm trigger is executed under wayland
I have this bug on 18.04 with alt+left. After executing the dumpkeys/loadkeys workaround, then alt+left stops doing strange things but now, alt+F4 drops me to console 4 which is even worse. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1710637 Title: Input falls through to gdm3 and terminates the session on Ctrl+C after udevadm trigger is executed under wayland To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1710637/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1710637] Re: Input falls through to gdm3 and terminates the session on Ctrl+C after udevadm trigger is executed under wayland
Extended the workaround to read dumpkeys |grep -v cr_Console | grep -v -E '^\s+alt\s+keycode.*Console_' |loadkeys -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1710637 Title: Input falls through to gdm3 and terminates the session on Ctrl+C after udevadm trigger is executed under wayland To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1710637/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1784065] Re: upgrade from 14.04 to 16.04 fails due to `interest-await' in trigger
Hello Yan, or anyone else affected, Accepted glib2.0 into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/glib2.0/2.48.2-0ubuntu4 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Description changed: + [Test case] + Verify that a release-upgrade of an Ubuntu desktop works from trusty to xenial with -proposed enabled. + Package failed to install. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libglib2.0-0 2.48.2-0ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-131.157-generic 4.4.134 Uname: Linux 4.4.0-131-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Fri Jul 27 18:31:08 2018 DuplicateSignature: - package:libglib2.0-0:2.48.2-0ubuntu3 - Preparing to unpack .../libglib2.0-0_2.48.2-0ubuntu3_amd64.deb ... - dpkg: error processing archive /var/cache/apt/archives/libglib2.0-0_2.48.2-0ubuntu3_amd64.deb (--unpack): - triggers ci file contains unknown directive `interest-await' + package:libglib2.0-0:2.48.2-0ubuntu3 + Preparing to unpack .../libglib2.0-0_2.48.2-0ubuntu3_amd64.deb ... + dpkg: error processing archive /var/cache/apt/archives/libglib2.0-0_2.48.2-0ubuntu3_amd64.deb (--unpack): + triggers ci file contains unknown directive `interest-await' ErrorMessage: triggers ci file contains unknown directive `interest-await' InstallationDate: Installed on 2015-03-31 (1213 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) RelatedPackageVersions: - dpkg 1.18.4ubuntu1.4 - apt 1.2.27 + dpkg 1.18.4ubuntu1.4 + apt 1.2.27 SourcePackage: glib2.0 Title: package libglib2.0-0 2.48.2-0ubuntu3 failed to install/upgrade: triggers ci file contains unknown directive `interest-await' UpgradeStatus: Upgraded to xenial on 2018-07-27 (0 days ago) ** Changed in: glib2.0 (Ubuntu Xenial) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-xenial -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1784065 Title: upgrade from 14.04 to 16.04 fails due to `interest-await' in trigger To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1784065/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1763940] Re: Pressing Print Screen in keyboard makes Rhythmbox go to sleep
Launchpad has imported 3 comments from the remote bug at https://bugs.freedesktop.org/show_bug.cgi?id=106138. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2018-04-19T16:47:26+00:00 Amr Ibrahim wrote: Created attachment 138931 daemon.conf Steps: 1. Start Rhythmbox and play music 2. Press Print Screen in keyboard 3. Music stops and cannot be played again in Rhythmbox 4. If the music does not stop from the first time try step 2 again and again until it stops I can navigate the UI of Rhythmbox, but I cannot play music. I have to kill the sleeping process in order to play music from Rhythmbox again. I can reproduce this bug in Totem and Clementine too. They present this error: pa_stream_writable_size() failed: Connection terminated I have attached my daemon.conf file. Reply at: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1763940/comments/3 On 2018-04-26T11:26:39+00:00 Tanu Kaskinen wrote: I can't reproduce this... Can you provide the pulseaudio server log? Instructions: 1. Disable automatic starting of PulseAudio. If your distro uses systemd's socket activation to start PulseAudio, run systemctl --user --now mask pulseaudio.service pulseaudio.socket If your distro doesn't do that, put "autospawn = no" to ~/.config/pulse/client.conf. 2. Stop pulseaudio with "killall pulseaudio" (the previous systemctl command might have stopped it already, though). 3. Start pulseaudio in a terminal with verbose logging: pulseaudio -vv 4. Once the initial burst of logging has stopped, hit enter a few times to add some empty lines in the log. The empty lines mark the beginning of the interesting part. 5. Start playing music with Rhythmbox, and try to reproduce the problem. 6. Once the music stops, hit enter again a few times in the terminal window where pulseaudio is running, to make it easy to find the place where something went wrong. (The "Connection terminated" error suggests that PulseAudio might have crashed, though. In that case adding this step can be skipped.) 7. Stop pulseaudio with Ctrl-C. 8. Copy the full log from the terminal and attach it to this bug. 9. To return things back to normal, run systemctl --user unmask pulseaudio.service pulseaudio.socket if you masked the service before. And remove the "autospawn = no" line from client.conf if you added it there. Reply at: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1763940/comments/4 On 2018-07-30T09:33:17+00:00 Gitlab-migration wrote: -- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/8. Reply at: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1763940/comments/5 ** Changed in: pulseaudio Status: Confirmed => Unknown -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1763940 Title: Pressing Print Screen in keyboard makes Rhythmbox go to sleep To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1763940/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1784514] Re: Update evolution-data-server to 3.28.5
** Description changed: Impact == 3.28.5 is the final scheduled bug fix release in the 3.28 series. - Updating e-d-s is required to update evolution to 3.28.5 (LP: #) + Updating e-d-s is required to update evolution to 3.28.5 (LP: #1784522) https://gitlab.gnome.org/GNOME/evolution-data-server/blob/gnome-3-28/NEWS https://gitlab.gnome.org/GNOME/evolution-data-server/commits/gnome-3-28 Test Case = After installing the update, restart your computer. Run several eds-using apps like Evolution, GNOME Calendar and verify that they continue to run at least as well as before this update. Regression Potential GNOME 3.28 distros will be shipping this update. There is a micro-release exception for GNOME: https://wiki.ubuntu.com/StableReleaseUpdates#GNOME 3.22.6 introduced a regression in pop3 support that was fixed within a week by 3.22.7. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1784514 Title: Update evolution-data-server to 3.28.5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1784514/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1784522] [NEW] Update evolution to 3.28.5
Public bug reported: Impact == evolution 3.28.5 is the final scheduled bug fix release in the 3.28 series. https://gitlab.gnome.org/GNOME/evolution/blob/gnome-3-28/NEWS https://gitlab.gnome.org/GNOME/evolution/commits/gnome-3-28 Test Case = After installing this update, please restart your computer. Verify that evolution still works as well as it did before. Optionally, you can go through some of the fixed bugs to verify the bug and the fix. Regression Potential GNOME 3.28 distros will be shipping this update. There is a micro-release exception for GNOME: https://wiki.ubuntu.com/StableReleaseUpdates#GNOME Ubuntu GNOME stopped including Evolution by default in 17.04. Upgraders may still have Evolution installed and it's a popular app. (It was demoted to universe before 16.04 LTS.) Other Info == This update depends on evolution-data-server 3.28.5 (LP: #1784514) ** Affects: evolution (Ubuntu) Importance: Undecided Status: Fix Committed ** Affects: evolution (Ubuntu Bionic) Importance: Undecided Status: Triaged ** Tags: bionic upgrade-software-version ** Also affects: evolution (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: evolution (Ubuntu Bionic) Status: New => Triaged ** Tags added: upgrade-software-version -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1784522 Title: Update evolution to 3.28.5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1784522/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1784486] Re: package gdm3 3.28.2-0ubuntu1.3 failed to install/upgrade: installed gdm3 package post-installation script subprocess returned error exit status 10
*** This bug is a duplicate of bug 1774039 *** https://bugs.launchpad.net/bugs/1774039 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1774039, so it 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. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1774039 package gdm3 failed to install/upgrade: installed gdm3 package post-installation script subprocess returned error exit status 10 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1784486 Title: package gdm3 3.28.2-0ubuntu1.3 failed to install/upgrade: installed gdm3 package post-installation script subprocess returned error exit status 10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1784486/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1774039] Re: package gdm3 failed to install/upgrade: installed gdm3 package post-installation script subprocess returned error exit status 10
** Summary changed: - package gdm3 3.28.2-0ubuntu1.1 failed to install/upgrade: installed gdm3 package post-installation script subprocess returned error exit status 10 + package gdm3 failed to install/upgrade: installed gdm3 package post-installation script subprocess returned error exit status 10 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1774039 Title: package gdm3 failed to install/upgrade: installed gdm3 package post- installation script subprocess returned error exit status 10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1774039/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1772831] Re: gnome-control-center does not respond after we set the resolution 320x180
** Changed in: oem-priority Assignee: (unassigned) => Leon Liao (lihow731) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1772831 Title: gnome-control-center does not respond after we set the resolution 320x180 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1772831/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1784473] Re: Xorg freeze
I think this might be the same as bug 1782347. What do you think? ** Tags added: black-screen radeon ** Summary changed: - Xorg freeze + [radeon] Ubuntu boots to a black screen ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New ** Changed in: mutter (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1784473 Title: [radeon] Ubuntu boots to a black screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784473/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1782347] Re: [radeon] GDM3 fails to load without nomodeset
** Also affects: mutter (Ubuntu) Importance: Undecided Status: New ** Changed in: mutter (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1782347 Title: [radeon] GDM3 fails to load without nomodeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1782347/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1784398] Re: Changing monitor settings crashes on meta_window_wayland_move_resize_internal
** Tags added: multi-monitor ** Tags removed: multi-monitor ** Tags added: multimonitor -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1784398 Title: Changing monitor settings crashes on meta_window_wayland_move_resize_internal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1784398/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1705369] Re: Ubuntu 17.10/18.04 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU)
Eduardo, please log a separate bug for that. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1705369 Title: Ubuntu 17.10/18.04 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1705369/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1784489] Re: nautilus-desktop crashed with SIGSEGV in discovered_cb()
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1784489 Title: nautilus-desktop crashed with SIGSEGV in discovered_cb() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1784489/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1784514] [NEW] Update evolution-data-server to 3.28.5
Public bug reported: Impact == 3.28.5 is the final scheduled bug fix release in the 3.28 series. Updating e-d-s is required to update evolution to 3.28.5 (LP: #) https://gitlab.gnome.org/GNOME/evolution-data-server/blob/gnome-3-28/NEWS https://gitlab.gnome.org/GNOME/evolution-data-server/commits/gnome-3-28 Test Case = After installing the update, restart your computer. Run several eds-using apps like Evolution, GNOME Calendar and verify that they continue to run at least as well as before this update. Regression Potential GNOME 3.28 distros will be shipping this update. There is a micro-release exception for GNOME: https://wiki.ubuntu.com/StableReleaseUpdates#GNOME 3.22.6 introduced a regression in pop3 support that was fixed within a week by 3.22.7. ** Affects: evolution-data-server (Ubuntu) Importance: Medium Status: Fix Committed ** Affects: evolution-data-server (Ubuntu Bionic) Importance: Medium Status: Triaged ** Tags: bionic upgrade-software-version ** Also affects: evolution-data-server (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: evolution-data-server (Ubuntu Bionic) Status: New => Triaged ** Changed in: evolution-data-server (Ubuntu Bionic) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1784514 Title: Update evolution-data-server to 3.28.5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1784514/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1784454] Re: kernel panic on booting kernel 4.4 based d-i from 16.04.5 RC image
This bug was fixed in the package debian-installer - 20101020ubuntu451.26 --- debian-installer (20101020ubuntu451.26) xenial; urgency=medium * Rebuild against new systemd for the 4.4 kernel regression fix (LP: #1784454) -- Łukasz 'sil2100' Zemczak Mon, 30 Jul 2018 22:26:39 +0200 ** Changed in: debian-installer (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1784454 Title: kernel panic on booting kernel 4.4 based d-i from 16.04.5 RC image To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1784454/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1784454] Re: kernel panic on booting kernel 4.4 based d-i from 16.04.5 RC image
This bug was fixed in the package systemd - 229-4ubuntu21.4 --- systemd (229-4ubuntu21.4) xenial; urgency=medium * debian/extra/start-udev: test that sync parameters file is writable, before writing to it. On old kernels (e.g. v4.4) the file is available but is read-only, thus writing to it causes init to fail and thus raise a kernel panic. As an extra caution ignore failures to write into that file anyway, since synchronous scsi probing is not critical enough to prevent starting d-i. LP: #1784454 -- Dimitri John Ledkov Mon, 30 Jul 2018 19:58:15 +0100 ** Changed in: systemd (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1784454 Title: kernel panic on booting kernel 4.4 based d-i from 16.04.5 RC image To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1784454/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1772831] Re: gnome-control-center does not respond after we set the resolution 320x180
** Changed in: gnome-control-center Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1772831 Title: gnome-control-center does not respond after we set the resolution 320x180 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1772831/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1784028] Re: package libglib2.0-0 2.40.2-0ubuntu1 failed to install/upgrade: triggers ci file contains unknown directive `interest-await'
*** This bug is a duplicate of bug 1784065 *** https://bugs.launchpad.net/bugs/1784065 ** This bug has been marked a duplicate of bug 1784065 upgrade from 14.04 to 16.04 fails due to `interest-await' in trigger -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1784028 Title: package libglib2.0-0 2.40.2-0ubuntu1 failed to install/upgrade: triggers ci file contains unknown directive `interest-await' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1784028/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1784454] Re: kernel panic on booting kernel 4.4 based d-i from 16.04.5 RC image
** Changed in: linux (Ubuntu) Status: Triaged => Invalid ** No longer affects: ubuntu-z-systems -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1784454 Title: kernel panic on booting kernel 4.4 based d-i from 16.04.5 RC image To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1784454/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1784486] [NEW] package gdm3 3.28.2-0ubuntu1.3 failed to install/upgrade: installed gdm3 package post-installation script subprocess returned error exit status 10
Public bug reported: gdm3 ProblemType: Package DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.2-0ubuntu1.3 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 Uname: Linux 4.15.0-24-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 AptOrdering: python-cryptography:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Mon Jul 30 12:08:08 2018 ErrorMessage: installed gdm3 package post-installation script subprocess returned error exit status 10 Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, unpackaged RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3 SourcePackage: gdm3 Title: package gdm3 3.28.2-0ubuntu1.3 failed to install/upgrade: installed gdm3 package post-installation script subprocess returned error exit status 10 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1784486 Title: package gdm3 3.28.2-0ubuntu1.3 failed to install/upgrade: installed gdm3 package post-installation script subprocess returned error exit status 10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1784486/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1705369] Re: Ubuntu 17.10/18.04 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU)
Hi, this is the basic configuration of my desktop: -Motherboard: ROG STRIX X370-F GAMING. -CPU: Ryzen 7 1700. -GPU: GTX 1050 2GB from MSI. I don't know if the bug I have is this one, but sometimes, after successfully login, the screen goes black in the first 10 minutes. On Ubuntu 17.10 I could see a message about "stopping user manager for uid", but on 18.04 I only see information about storage I always get in the boot process, nothing apparently bad. I used different versions of the NVIDIA blob driver without getting different results, but the error didn't appear in almost one month using Linux Mint, so I think the problem is from Ubuntu's stack. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1705369 Title: Ubuntu 17.10/18.04 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1705369/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1705369] Re: Ubuntu 17.10/18.04 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU)
I forgot to say I will try with nomodeset in my Grub config first. If that doesn't work, I will switch from GDM to LightDM. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1705369 Title: Ubuntu 17.10/18.04 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1705369/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1723615] Re: gnome-shell crashed with SIGSEGV in meta_monitor_mode_get_resolution()
It looks like we're still seeing some crash for this, I've doing some more debugging at https://gitlab.gnome.org/GNOME/mutter/issues/130#note_278690 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1723615 Title: gnome-shell crashed with SIGSEGV in meta_monitor_mode_get_resolution() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1723615/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1784454] Re: kernel panic on booting kernel 4.4 based d-i from 16.04.5 RC image
** Tags added: kernel-key ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Triaged ** Changed in: linux (Ubuntu) Importance: Undecided => Critical ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1784454 Title: kernel panic on booting kernel 4.4 based d-i from 16.04.5 RC image To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1784454/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1784454] Re: kernel panic on booting kernel 4.4 based d-i from 16.04.5 RC image
13: if [ -f /sys/module/scsi_mod/parameters/scan ]; then 14:echo sync > /sys/module/scsi_mod/parameters/scan 15: fi Not sure how come the file is there, yet "cannot be created" when we try to echo into it... maybe it's not writable or disappears. I think the quickest botch that i can think of is: echo sync > /sys/module/scsi_mod/parameters/scan 2>/dev/null || : to redirect errors to oblivion, and to ignore errors from this action ** Also affects: debian-installer (Ubuntu) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu) Importance: Undecided Status: New ** Changed in: debian-installer (Ubuntu) Assignee: (unassigned) => Canonical Foundations Team (canonical-foundations) ** Changed in: systemd (Ubuntu) Assignee: (unassigned) => Canonical Foundations Team (canonical-foundations) ** Changed in: debian-installer (Ubuntu) Importance: Undecided => Critical ** Changed in: systemd (Ubuntu) Importance: Undecided => Critical -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1784454 Title: kernel panic on booting kernel 4.4 based d-i from 16.04.5 RC image To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1784454/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1780996] Re: Convert triggers to noawait
This bug was fixed in the package guile-2.0 - 2.0.13+1-5ubuntu0.1 --- guile-2.0 (2.0.13+1-5ubuntu0.1) bionic; urgency=medium * Convert triggers to noawait (LP: #1780996) (Closes: #903915) - the trigger is supposed to register slib with guile-2.0 but the registration is a no-op, so it's completely safe to make it noawait. -- Julian Andres Klode Tue, 17 Jul 2018 12:14:45 +0200 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to shared-mime-info in Ubuntu. https://bugs.launchpad.net/bugs/1780996 Title: Convert triggers to noawait To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1780996/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1780996] Re: Convert triggers to noawait
This bug was fixed in the package nevow - 0.14.2-1ubuntu2 --- nevow (0.14.2-1ubuntu2) bionic; urgency=medium * use pybuild --print build_dir instead of hadrcoding pybuild's internal paths, fixes FTBFS. nevow (0.14.2-1ubuntu1) bionic; urgency=medium * Convert trigger to noawait (LP: #1780996) -- Brian Murray Tue, 17 Jul 2018 09:15:21 -0700 ** Changed in: guile-2.0 (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to shared-mime-info in Ubuntu. https://bugs.launchpad.net/bugs/1780996 Title: Convert triggers to noawait To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1780996/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1780996] Re: Convert triggers to noawait
This bug was fixed in the package wokkel - 0.7.1-1ubuntu0.18.04.1 --- wokkel (0.7.1-1ubuntu0.18.04.1) bionic; urgency=medium * Convert trigger to noawait (LP: #1780996) -- Brian Murray Wed, 11 Jul 2018 13:59:50 -0700 ** Changed in: wokkel (Ubuntu Bionic) Status: Fix Committed => Fix Released ** Changed in: nevow (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to shared-mime-info in Ubuntu. https://bugs.launchpad.net/bugs/1780996 Title: Convert triggers to noawait To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1780996/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1780996] Re: Convert triggers to noawait
This bug was fixed in the package fusiondirectory - 1.0.19-1ubuntu0.18.04.1 --- fusiondirectory (1.0.19-1ubuntu0.18.04.1) bionic; urgency=medium * debian/fusiondirectory.triggers: Be specific about using interest-noawait for the triggers -- there's no need to block in awaiting the triggers for locale, plugins updates. (LP: #1780996) -- Mathieu Trudel-Lapierre Thu, 12 Jul 2018 16:55:25 -0400 ** Changed in: fusiondirectory (Ubuntu Bionic) Status: Fix Committed => Fix Released ** Changed in: guile-2.2 (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to shared-mime-info in Ubuntu. https://bugs.launchpad.net/bugs/1780996 Title: Convert triggers to noawait To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1780996/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1780996] Re: Convert triggers to noawait
This bug was fixed in the package guile-2.2 - 2.2.3+1-3ubuntu0.1 --- guile-2.2 (2.2.3+1-3ubuntu0.1) bionic; urgency=medium * Convert triggers to noawait (LP: #1780996) (Closes: #903915) - the trigger is supposed to register slib with guile-2.0 but the registration is a no-op, so it's completely safe to make it noawait. -- Julian Andres Klode Tue, 17 Jul 2018 15:42:59 +0200 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to shared-mime-info in Ubuntu. https://bugs.launchpad.net/bugs/1780996 Title: Convert triggers to noawait To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1780996/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1784065] Re: upgrade from 14.04 to 16.04 fails due to `interest-await' in trigger
** Also affects: glib2.0 (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: glib2.0 (Ubuntu Xenial) Importance: Undecided => High ** Changed in: glib2.0 (Ubuntu Xenial) Status: New => In Progress ** Changed in: glib2.0 (Ubuntu Xenial) Assignee: (unassigned) => Brian Murray (brian-murray) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1784065 Title: upgrade from 14.04 to 16.04 fails due to `interest-await' in trigger To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1784065/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1784065] Re: upgrade from 14.04 to 16.04 fails due to `interest-await' in trigger
** Changed in: glib2.0 (Ubuntu) Assignee: Julian Andres Klode (juliank) => Brian Murray (brian-murray) ** Changed in: glib2.0 (Ubuntu) Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1784065 Title: upgrade from 14.04 to 16.04 fails due to `interest-await' in trigger To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1784065/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1560286] Re: Evince displays pdf file fine, but prints colors inverted
Same here with 18.04. Evince prints some PDF images in inverted colors, while Firefox would print them just fine. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1560286 Title: Evince displays pdf file fine, but prints colors inverted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1560286/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1784398] [NEW] Changing monitor settings crashes on meta_window_wayland_move_resize_internal
Public bug reported: Under wayland: 1. Attach another monitor 2. Mark as cloned display 3. Gnome-shell should not crash See upstream bug: https://gitlab.gnome.org/GNOME/mutter/issues/248 ** Affects: gnome-shell (Ubuntu) Importance: Medium Assignee: Marco Trevisan (Treviño) (3v1n0) Status: In Progress ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1784398 Title: Changing monitor settings crashes on meta_window_wayland_move_resize_internal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1784398/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1784396] [NEW] Update to 3.29.4
Public bug reported: Do it ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Assignee: Iain Lane (laney) Status: In Progress ** Tags: upgrade-software-version ** Changed in: gnome-control-center (Ubuntu) Status: New => In Progress ** Changed in: gnome-control-center (Ubuntu) Assignee: (unassigned) => Iain Lane (laney) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1784396 Title: Update to 3.29.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1784396/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1663839] Re: gnome-session-binary[1676]: Unrecoverable failure in required component org.gnome.SettingsDaemon.Color.desktop
Seems like this is the newer version of this bug for 18.04 if folks want to follow up there: https://bugs.launchpad.net/ubuntu/+source/gnome- settings-daemon/+bug/1764417 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1663839 Title: gnome-session-binary[1676]: Unrecoverable failure in required component org.gnome.SettingsDaemon.Color.desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1663839/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1764417] Re: Unrecoverable failure in required component org.gnome.SettingsDaemon.Color.desktop
I'm seeing this on 18.04 as well, gnome-settings-daemon 3.28.1-0ubuntu1. Jul 30 06:52:10 bean gnome-session[1964]: gnome-session-binary[1964]: WARNING: Application 'org.gnome.SettingsDaemon.Keyboard.desktop' failed to register before timeout Jul 30 06:52:10 bean gnome-session-binary[1964]: WARNING: Application 'org.gnome.SettingsDaemon.Keyboard.desktop' failed to register before timeout Jul 30 06:52:10 bean gnome-session-binary[1964]: Unrecoverable failure in required component org.gnome.SettingsDaemon.Keyboard.desktop Jul 30 06:52:10 bean gnome-session[1964]: gnome-session-binary[1964]: CRITICAL: We failed, but the fail whale is dead. Sorry Jul 30 06:52:10 bean gnome-session-binary[1964]: CRITICAL: We failed, but the fail whale is dead. Sorry Additionally, after this happens it seems like Gnome Tweak Tools loses all of my keyboard customizations (such as switching ctrl-caps). -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1764417 Title: Unrecoverable failure in required component org.gnome.SettingsDaemon.Color.desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1764417/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1703415] Re: Bluetooth audio devices/profiles are missing after logging in from GDM
Launchpad has imported 3 comments from the remote bug at
https://bugs.freedesktop.org/show_bug.cgi?id=57167.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.
On 2012-11-15T19:31:15+00:00 Tanu Kaskinen wrote:
In module-bluetooth-device.c in filter_cb() there's this piece of code:
if (acquire)
if (bt_transport_acquire(u, FALSE) >= 0) {
if (u->source)
pa_source_suspend(u->source, FALSE,
PA_SUSPEND_IDLE|PA_SUSPEND_USER);
if (u->sink)
pa_sink_suspend(u->sink, FALSE,
PA_SUSPEND_IDLE|PA_SUSPEND_USER);
}
The acquire variable is set to true if the bluetooth audio state changed
to "playing". This can happen without pulseaudio requesting it, so if we
want to have strict equivalence "sink/source suspended" == "audio state
is 'playing'" (and I think we want that), then it makes sense that
module-bluetooth-device unsuspends the sink/source. The problem here is
that there's no clean "force unsuspend" mechanism in pulseaudio.
pa_sink_suspend(u->sink, FALSE, PA_SUSPEND_IDLE|PA_SUSPEND_USER) may not
actually unsuspend the sink, because there are also other suspend
reasons than just IDLE and USER. So, depending on the situation, the
sink may or may not get unsuspended.
module-bluetooth-device could list all possible reasons in the
pa_sink_suspend() call, but that would be ugly. When adding new suspend
reasons, it would be very easy to forget to update the pa_sink_suspend()
call in module-bluetooth-device, and besides, if those suspend reasons
are originally set by some other code, the original reasons to suspend
don't really disappear when module-bluetooth-device unsuspends the sink,
the old reasons are just overridden.
I think there should be a function for forcing unsuspending. The
semantics would be such that the sink gets unsuspended regardless of any
standing suspend reasons, but all standing suspend reasons would be
remembered, and once a new suspend request would be made, the forced
unsuspend would cease to have effect, the sink would suspend and things
would return to normal.
A related thing is that I would like to replace the single suspend
reason bitfield in pa_sink with an individual suspend request object for
each suspend request. The single suspend reason bitfield is prone to
conflicts if multiple places use the same reason (for example, module-
bluetooth-device uses the USER reason which is also used for other
purposes).
Reply at:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1703415/comments/0
On 2012-11-15T20:44:28+00:00 Tanu Kaskinen wrote:
(In reply to comment #0)
> The problem here is that
> there's no clean "force unsuspend" mechanism in pulseaudio.
> pa_sink_suspend(u->sink, FALSE, PA_SUSPEND_IDLE|PA_SUSPEND_USER) may not
> actually unsuspend the sink, because there are also other suspend reasons
> than just IDLE and USER. So, depending on the situation, the sink may or may
> not get unsuspended.
>
> module-bluetooth-device could list all possible reasons in the
> pa_sink_suspend() call, but that would be ugly. When adding new suspend
> reasons, it would be very easy to forget to update the pa_sink_suspend()
> call in module-bluetooth-device, and besides, if those suspend reasons are
> originally set by some other code, the original reasons to suspend don't
> really disappear when module-bluetooth-device unsuspends the sink, the old
> reasons are just overridden.
Correction: there is the PA_SUSPEND_ALL suspend cause. That looks like a
good simple solution to this bug, even though it doesn't solve all the
described problems. But at least it will reliably unsuspend the sink.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1703415/comments/1
On 2018-07-30T10:19:12+00:00 Gitlab-migration wrote:
-- GitLab Migration Automatic Message --
This bug has been migrated to freedesktop.org's GitLab instance and has
been closed from further activity.
You can subscribe and participate further through the new bug through
this link to our GitLab instance:
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/340.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1703415/comments/16
** Changed in: pulseaudio
Status: Confirmed => Unknown
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1703415
Title:
Bluetooth audio devices/profiles are missing after logging in from GDM
To manage notifications about this bug go to:
https://bugs.launchpad.net/gdm/+bug/1703415/+subscriptions
--
[Bug 1663839] Re: gnome-session-binary[1676]: Unrecoverable failure in required component org.gnome.SettingsDaemon.Color.desktop
I'm seeing this on 18.04 as well, gnome-settings-daemon 3.28.1-0ubuntu1. Can we get this reopened? Jul 30 06:52:10 bean gnome-session[1964]: gnome-session-binary[1964]: WARNING: Application 'org.gnome.SettingsDaemon.Keyboard.desktop' failed to register before timeout Jul 30 06:52:10 bean gnome-session-binary[1964]: WARNING: Application 'org.gnome.SettingsDaemon.Keyboard.desktop' failed to register before timeout Jul 30 06:52:10 bean gnome-session-binary[1964]: Unrecoverable failure in required component org.gnome.SettingsDaemon.Keyboard.desktop Jul 30 06:52:10 bean gnome-session[1964]: gnome-session-binary[1964]: CRITICAL: We failed, but the fail whale is dead. Sorry Jul 30 06:52:10 bean gnome-session-binary[1964]: CRITICAL: We failed, but the fail whale is dead. Sorry -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1663839 Title: gnome-session-binary[1676]: Unrecoverable failure in required component org.gnome.SettingsDaemon.Color.desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1663839/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1782152] Re: GDM blocks SIGUSR1 used in PAM scripts
** Also affects: gdm3 (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: gdm3 (Ubuntu Cosmic) Importance: Medium Assignee: Dariusz Gadomski (dgadomski) Status: In Progress ** Also affects: gdm3 (Ubuntu Xenial) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1782152 Title: GDM blocks SIGUSR1 used in PAM scripts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1782152/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1784289] Re: package systemd 229-4ubuntu21.2 [modified: usr/share/dbus-1/system-services/org.freedesktop.systemd1.service] failed to install/upgrade: subprocess installed pre-removal script retur
Reinstalled mysql to fix the issue ** Changed in: systemd (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1784289 Title: package systemd 229-4ubuntu21.2 [modified: usr/share/dbus-1/system- services/org.freedesktop.systemd1.service] failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1784289/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1779815] Re: [Ubuntu 18.04.01][BostonLC][mpt3sas] installer does not detect any LSI based SAS/md raid device
** Changed in: ubuntu-power-systems Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1779815 Title: [Ubuntu 18.04.01][BostonLC][mpt3sas] installer does not detect any LSI based SAS/md raid device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1779815/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1767918] Re: Login password is shown in plain text on VT1 when shutting down
In general I can confirm the above described behaviour for my fresh Ubuntu 18.04 upgrade: - shortly after reboot I can't reproduce the problem too - after a couple of days of notebook standby/wakeup you suddenly see during reboot or switch user the tty1 screen with all typed usernames/password since last reboot -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1767918 Title: Login password is shown in plain text on VT1 when shutting down To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1767918/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1726355] Re: Files cannot be moved from the desktop.
** Package changed: ubuntu => nautilus (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1726355 Title: Files cannot be moved from the desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1726355/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1726355] [NEW] Files cannot be moved from the desktop.
You have been subscribed to a public bug: PROBLEM 1 I'm selecting a file on the desktop. I'm moving it to an open nautilus window. The cursor takes the form of a hand. The file is not moved. The cursor retains its hand shape. Nautilus remains usable. Firefox is no longer usable (the cursor is no longer present). PROBLEM 2 Similar actions, alternative results. The file move behind the Nautilus windows, staying on desktop, but at a different location. Solution for unlocking problem 1: use gnome-tweak, desktop parameters deactivate icon on desktop. reactivate icon on desktop. Problem solved Behavioral solution: Use the Nautilus tree structure to move files from the desktop to other folders. ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- Files cannot be moved from the desktop. https://bugs.launchpad.net/bugs/1726355 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1775329] Re: Feature request: Add a handler for CVE URLs
Haha, indeed. Thanks! It's been inactive for 9 years, though. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1775329 Title: Feature request: Add a handler for CVE URLs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1775329/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1764779] Re: Nautilus crashed open Windows-partition
** Also affects: glib (Ubuntu) Importance: Undecided Status: New ** Changed in: glib (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1764779 Title: Nautilus crashed open Windows-partition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib/+bug/1764779/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1775329] Re: Feature request: Add a handler for CVE URLs
The upstream bug is https://bugzilla.gnome.org/show_bug.cgi?id=579859 ** Bug watch added: GNOME Bug Tracker #579859 https://bugzilla.gnome.org/show_bug.cgi?id=579859 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1775329 Title: Feature request: Add a handler for CVE URLs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1775329/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1779815] Re: [Ubuntu 18.04.01][BostonLC][mpt3sas] installer does not detect any LSI based SAS/md raid device
This bug was fixed in the package systemd - 229-4ubuntu21.3 --- systemd (229-4ubuntu21.3) xenial; urgency=medium [ Dimitri John Ledkov ] * udev-udeb: ship modprobe.d snippet to force scsi_mod.scan=sync in d-i. [ Adam Conrad ] * debian/extra/start-udev: Set scsi_mod scan=sync even if it's builtin to the kernel (we previously only set it in modprobe.d) LP: #1779815 -- Adam Conrad Thu, 26 Jul 2018 04:00:09 -0600 ** Changed in: systemd (Ubuntu Xenial) Status: Fix Committed => Fix Released ** Changed in: debian-installer (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1779815 Title: [Ubuntu 18.04.01][BostonLC][mpt3sas] installer does not detect any LSI based SAS/md raid device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1779815/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1775329] Re: Feature request: Add a handler for CVE URLs
I wanted to say "Jeremy is maintaining both the Debian and Ubuntu *packages* ..." -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1775329 Title: Feature request: Add a handler for CVE URLs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1775329/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1775329] Re: Feature request: Add a handler for CVE URLs
> The other option would be to do it "properly" the way upstream want I can't recall/find such a request in upstream gnome-terminal's tracker, I don't think we (gnome-terminal upstream developers) have any plans on adding this feature. IMHO downstream distro-specific patches are fine here. > Also do we know if Debian are interested Jeremy is maintaining both the Debian and Ubuntu patches, that why I thought he might want to do it this way. Anyway, I leave this up to you guys to figure out. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1775329 Title: Feature request: Add a handler for CVE URLs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1775329/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1784332] Re: Super+ shortcuts stop working after locking the screen
Well... I wanted to try disabling my extensions to see whether I could get the Wayland session to work, when I noticed that Dash to dock was enabled - it was still left there after my upgrade from 16.04. After disabling it, Ubuntu Dock (if that was even what was running) appears to work fine. So I'm guessing it might be a bug in Dash to dock, so I'm closing this - unless the bug originated in the interaction between the two, and some action still needs to be undertaken? ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1784332 Title: Super+ shortcuts stop working after locking the screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1784332/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1782893] Re: Bluetooth not working on Dell XPS 15
Ubuntu does those steps out-of-the-box already. You will find pulseaudio-module-bluetooth installed by default, and module-bluetooth- discover is loaded by default. So if the steps in comment #28 helped then I imagine that maybe module- bluetooth-discover is not searching often enough. That may be a bug in PulseAudio (module-bluetooth-discover), or it may be a bug in BlueZ. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/1782893 Title: Bluetooth not working on Dell XPS 15 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1782893/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1772677] Re: gnome-shell filling up syslog with thousands of entries (stack traces ending in osdWindow.js:206/207)
Gijs, Yours seems to be a different bug (mostly ending at messageList.js), so please open a new bug for that. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1772677 Title: gnome-shell filling up syslog with thousands of entries (stack traces ending in osdWindow.js:206/207) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1772677/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1784332] [NEW] Super+ shortcuts stop working after locking the screen
Public bug reported: When I lock the screen, Ubuntu Dock is visible on the lock screen as well. I'm not sure if that is desired behaviour, as clicking it doesn't appear to do anything, although the selecteyd application is focused after unlocking the screen. Anyway, after than unlocking the screen, pressing Super+ no longer switches applications. Instead, nothing happens at all. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell-extension-ubuntu-dock 0.9.1 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: communitheme:ubuntu:GNOME Date: Mon Jul 30 10:07:16 2018 InstallationDate: Installed on 2017-07-13 (381 days ago) InstallationMedia: Ubuntu-GNOME 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: Upgraded to bionic on 2018-07-28 (1 days ago) ** Affects: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1784332 Title: Super+ shortcuts stop working after locking the screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1784332/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1784330] [NEW] Super+ shortcuts stop working after locking the screen
Public bug reported: When I lock the screen, Ubuntu Dock is visible on the lock screen as well. I'm not sure if that is desired behaviour, as clicking it doesn't appear to do anything, although the selecteyd application is focused after unlocking the screen. Anyway, after than unlocking the screen, pressing Super+ no longer switches applications. Instead, nothing happens at all. ** Affects: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1784330 Title: Super+ shortcuts stop working after locking the screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1784330/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1772677] Re: gnome-shell filling up syslog with thousands of entries (stack traces ending in osdWindow.js:206/207)
Confirming this bug, also affects me. We need an hotfix ASAP as this also leads to unbootable computers if root fs fills up (boot process hangs on starting of GDM, which might need to create some files). Had system locked from thursday afternoon till this morning, 38 gig syslog, completely filling the root partition. root@gijs-desktop:/var/log# tail -n60 syslog Jul 30 03:35:45 gijs-desktop org.gnome.Shell.desktop[1949]: #4 0x7ffe182c1770 b resource:///org/gnome/shell/ui/layout.js:531 (0x7fd5e05042b8 @ 127) Jul 30 03:35:45 gijs-desktop org.gnome.Shell.desktop[1949]: #5 0x7ffe182c17e0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7fd5e06b5de0 @ 71) Jul 30 03:35:45 gijs-desktop org.gnome.Shell.desktop[1949]: #6 0x7ffe182c17e0 I self-hosted:915 (0x7fd5e06f12b8 @ 367) Jul 30 03:35:45 gijs-desktop org.gnome.Shell.desktop[1949]: == Stack trace for context 0x5570af9fa320 == Jul 30 03:35:45 gijs-desktop org.gnome.Shell.desktop[1949]: #0 Jul 30 08:55:54 gijs-desktop gnome-shell[1949]: Object St.Button (0x5570b37372f0), has been already finalized. Impossible to set any property to it. Jul 30 08:55:54 gijs-desktop gnome-shell[1949]: Object St.Button (0x5570b37372f0), has been already finalized. Impossible to set any property to it. Jul 30 08:55:54 gijs-desktop org.gnome.Shell.desktop[1949]: == Stack trace for context 0x5570af9fa320 == Jul 30 08:55:54 gijs-desktop org.gnome.Shell.desktop[1949]: #0 0x5570afe1a580 i resource:///org/gnome/shell/ui/messageList.js:504 (0x7fd5e05b4de0 @ 83) Jul 30 08:55:54 gijs-desktop org.gnome.Shell.desktop[1949]: #1 0x7ffe182b8480 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7fd5e06b5de0 @ 71) Jul 30 08:55:54 gijs-desktop org.gnome.Shell.desktop[1949]: #2 0x7ffe182b8550 b self-hosted:917 (0x7fd5e06f12b8 @ 394) Jul 30 08:55:54 gijs-desktop org.gnome.Shell.desktop[1949]: #3 0x5570afe1a4f0 i resource:///org/gnome/shell/ui/messageTray.js:1461 (0x7fd5e05a2a28 @ 121) Jul 30 08:55:54 gijs-desktop org.gnome.Shell.desktop[1949]: #4 0x7ffe182ba4d0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7fd5e06b5de0 @ 71) Jul 30 08:55:54 gijs-desktop org.gnome.Shell.desktop[1949]: #5 0x5570afe1a448 i resource:///org/gnome/shell/ui/messageTray.js:1448 (0x7fd5e05a29a0 @ 406) Jul 30 08:55:54 gijs-desktop org.gnome.Shell.desktop[1949]: #6 0x7ffe182bb0b0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7fd5e06b5de0 @ 71) Jul 30 08:55:54 gijs-desktop org.gnome.Shell.desktop[1949]: #7 0x5570afe1a390 i resource:///org/gnome/shell/ui/messageTray.js:1249 (0x7fd5e05a2340 @ 729) Jul 30 08:55:54 gijs-desktop org.gnome.Shell.desktop[1949]: #8 0x7ffe182bbc90 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7fd5e06b5de0 @ 71) Jul 30 08:55:54 gijs-desktop org.gnome.Shell.desktop[1949]: #9 0x5570afe1a2f8 i resource:///org/gnome/shell/ui/messageTray.js:1067 (0x7fd5e05a0e68 @ 124) Jul 30 08:55:54 gijs-desktop org.gnome.Shell.desktop[1949]: #10 0x7ffe182bc880 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7fd5e06b5de0 @ 71) Jul 30 08:55:54 gijs-desktop org.gnome.Shell.desktop[1949]: #11 0x7ffe182bc950 b self-hosted:917 (0x7fd5e06f12b8 @ 394) Jul 30 08:55:54 gijs-desktop org.gnome.Shell.desktop[1949]: #12 0x7ffe182bca40 b resource:///org/gnome/gjs/modules/signals.js:128 (0x7fd5e06d3230 @ 386) Jul 30 08:55:54 gijs-desktop org.gnome.Shell.desktop[1949]: #13 0x5570afe1a268 i resource:///org/gnome/shell/ui/messageTray.js:487 (0x7fd5e059dc48 @ 50) Jul 30 08:55:54 gijs-desktop org.gnome.Shell.desktop[1949]: #14 0x7ffe182bd6a0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7fd5e06b5de0 @ 71) Jul 30 08:55:54 gijs-desktop org.gnome.Shell.desktop[1949]: #15 0x5570afe1a1e8 i resource:///org/gnome/shell/ui/calendar.js:775 (0x7fd5e05aad58 @ 44) Jul 30 08:55:54 gijs-desktop org.gnome.Shell.desktop[1949]: #16 0x7ffe182be9b0 b resource:///org/gnome/gjs/modules/signals.js:128 (0x7fd5e06d3230 @ 386) Jul 30 08:55:54 gijs-desktop org.gnome.Shell.desktop[1949]: #17 0x5570afe1a160 i resource:///org/gnome/shell/ui/messageList.js:372 (0x7fd5e05b4670 @ 22) Jul 30 08:55:54 gijs-desktop org.gnome.Shell.desktop[1949]: #18 0x7ffe182bf600 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7fd5e06b5de0 @ 71) Jul 30 08:55:54 gijs-desktop org.gnome.Shell.desktop[1949]: #19 0x5570afe1a0e8 i resource:///org/gnome/shell/ui/calendar.js:779 (0x7fd5e05aade0 @ 29) Jul 30 08:55:54 gijs-desktop org.gnome.Shell.desktop[1949]: #20 0x7ffe182c0910 b resource:///org/gnome/gjs/modules/signals.js:128 (0x7fd5e06d3230 @ 386) Jul 30 08:55:54 gijs-desktop org.gnome.Shell.desktop[1949]: #21 0x5570afe1a058 i resource:///org/gnome/shell/ui/messageTray.js:487 (0x7fd5e059dc48 @ 50) Jul 30 08:55:54 gijs-desktop org.gnome.Shell.desktop[1949]: #22 0x7ffe182c1570 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7fd5e06b5de0 @ 71) Jul 30 08:55:54 gijs-desktop org.gnome.Shell.desktop[1949]: #23 0x5570afe19fc0 i
[Bug 1782893] Re: Bluetooth not working on Dell XPS 15
thanks, this seems to make it work now the only strange thing seems to be that the volume control doesn't work, but I guess that's a different issue / topic so: why did this not work out of the box? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/1782893 Title: Bluetooth not working on Dell XPS 15 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1782893/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1784289] [NEW] package systemd 229-4ubuntu21.2 [modified: usr/share/dbus-1/system-services/org.freedesktop.systemd1.service] failed to install/upgrade: subprocess installed pre-removal script ret
Public bug reported: I had to completely remove mysql server after an upgrade to 16.04 which installed upstart. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: systemd 229-4ubuntu21.2 [modified: usr/share/dbus-1/system-services/org.freedesktop.systemd1.service] ProcVersionSignature: Ubuntu 4.15.0-29.31~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Mon Jul 30 11:01:38 2018 DpkgTerminalLog: Removing systemd (229-4ubuntu21.2) ... systemd is the active init system, please switch to another before removing systemd. dpkg: error processing package systemd (--purge): subprocess installed pre-removal script returned error exit status 1 DuplicateSignature: package:systemd:229-4ubuntu21.2 [modified: usr/share/dbus-1/system-services/org.freedesktop.systemd1.service] Removing systemd (229-4ubuntu21.2) ... systemd is the active init system, please switch to another before removing systemd. dpkg: error processing package systemd (--purge): subprocess installed pre-removal script returned error exit status 1 ErrorMessage: subprocess installed pre-removal script returned error exit status 1 InstallationDate: Installed on 2018-05-29 (61 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) MachineType: Dell Inc. Latitude 3460 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic root=UUID=2f7bff7f-36fa-4631-b297-9ca03f7ed302 ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.27 SourcePackage: systemd Title: package systemd 229-4ubuntu21.2 [modified: usr/share/dbus-1/system-services/org.freedesktop.systemd1.service] failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/23/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A13 dmi.board.name: 09CGMV dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA13:bd01/23/2018:svnDellInc.:pnLatitude3460:pvr:rvnDellInc.:rn09CGMV:rvrA03:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude 3460 dmi.sys.vendor: Dell Inc. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1784289 Title: package systemd 229-4ubuntu21.2 [modified: usr/share/dbus-1/system- services/org.freedesktop.systemd1.service] failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1784289/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
