[Desktop-packages] [Bug 1852183] Re: [X11] copy/paste (clipboard) is broken in Ubuntu 19.10
I experience this problem only with WPS office under Ubuntu 19.10. I usually need to copy text twice in order to send it to clipboard. Because copy option is actually broken, it happens that the previous text is pasted (not the one I copied). However, other programs work just fine most of the time. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1852183 Title: [X11] copy/paste (clipboard) is broken in Ubuntu 19.10 Status in LibreOffice: Confirmed Status in Mutter: New Status in libreoffice package in Ubuntu: Triaged Status in mutter package in Ubuntu: Triaged Status in libreoffice source package in Eoan: Triaged Status in mutter source package in Eoan: Triaged Bug description: I'm running LibreOffice 6.3.2.2 on Ubuntu 19.10. In this environment, copy/cut/paste often fails. Specifically, the paste command sometimes does not paste the text that was cut/copied most recently. Instead, it pastes text that was cut/copied at some prior time. I use LibreOffice Writer a lot, and I now see this problem very often, i.e. many times every day. There is some discussion of the problem here: https://ask.libreoffice.org/en/question/213510/copypaste-issues- libreoffice-calc/ Several posters there say that they are also using Ubuntu 19.10. Ubuntu 19.10 includes Mutter 3.34, which has a new clipboard manager: https://www.phoronix.com/scan.php?page=news_item=GNOME-3.34 -Clipboard-Manager It seems like that could be related. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1852183/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1845046] Re: Bluetooth headphones/speaker default to low quality headset mode and fails to switch to A2DP when selected
** Also affects: bluez (Ubuntu) Importance: Undecided Status: New ** Changed in: bluez (Ubuntu) Importance: Undecided => High ** Changed in: bluez (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1845046 Title: Bluetooth headphones/speaker default to low quality headset mode and fails to switch to A2DP when selected Status in bluez package in Ubuntu: Confirmed Status in gnome-control-center package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: Whenever I turn on my headphones theyll connect to my computer but im able to hear the input audio from my microphone and low quality output audio. I have to disconnect the headphones in the bluetooth devices and reconnect for it to fix the problem. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.2 ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: litleck1398 F pulseaudio /dev/snd/controlC0: litleck1398 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Sep 23 17:07:59 2019 InstallationDate: Installed on 2019-09-22 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_Card: WH-1000XM3 Symptom_Type: High background noise, or volume is too low Title: [WH-1000XM3, playback] Background noise or low volume UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/12/2019 dmi.bios.vendor: Alienware dmi.bios.version: 1.0.19 dmi.board.name: 01NYPT dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.0.19:bd02/12/2019:svnAlienware:pnAlienwareAuroraR5:pvr1.0.19:rvnAlienware:rn01NYPT:rvrA00:cvnAlienware:ct3:cvrNotSpecified: dmi.product.family: Alienware dmi.product.name: Alienware Aurora R5 dmi.product.sku: 0729 dmi.product.version: 1.0.19 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1845046/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1853768] Re: Qt apps, like kid3-qt, which uses legacy icons "document-*.png", show them as normal document icon under Yaru theme
** Changed in: yaru Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/1853768 Title: Qt apps, like kid3-qt, which uses legacy icons "document-*.png", show them as normal document icon under Yaru theme Status in Yaru Theme: Fix Released Status in qtbase-opensource-src package in Ubuntu: Confirmed Status in yaru-theme package in Ubuntu: Confirmed Bug description: Qt apps, like kid3-qt, which uses these legacy icons: document-open.png document-open-recent.png document-save.png document-save-as.png document-revert.png document-import.png document-export.png The icons are all shown as the same normal document icon under Yaru. Qt apps only have a problem with legacy icons starting with "document-*" and all other legacy icons are inherited from Humanity under Yaru. Is there a general solution to force Qt apps to choose the closest icon name from Yaru or Humanity? Should this bug be issued against upstream Qt? To manage notifications about this bug go to: https://bugs.launchpad.net/yaru/+bug/1853768/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1844906] Re: gnome-shell crash after suspend
[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1844906 Title: gnome-shell crash after suspend Status in gnome-shell package in Ubuntu: Expired Bug description: gnome-shell doesn't load correctly the theme after suspend I need to restart systematically gnome-shell ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.32.2-2ubuntu1~ubuntu19.04.1 ProcVersionSignature: Ubuntu 5.0.0-29.31-lowlatency 5.0.21 Uname: Linux 5.0.0-29-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 Date: Sun Sep 22 07:36:14 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-12-29 (266 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: LANG=fr_FR.UTF-8 TERM=xterm-256color PATH=(custom, no user) SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.32.2+git20190711-2ubuntu1~19.04.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to disco on 2019-04-30 (144 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1844906/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1845076] Re: [nouveau] Gnome shell/Xorg freeze after remote connection with monitor unplugged
[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1845076 Title: [nouveau] Gnome shell/Xorg freeze after remote connection with monitor unplugged Status in gnome-shell package in Ubuntu: Expired Status in mutter package in Ubuntu: Expired Bug description: I was trying to have a remote connection on a Ubuntu 18.04 pc with nomachine (but the behavior with Anydesk is the same) AFTER I unplugged the monitor form that pc. Once connected the output on the client freeze by just opening the Activities panel. If I plug the monitor back in on the server, the gnome shell is glitched and the only way to gain back control is by doing ALT F2 and then r. If I keep the monitor plugged in but turned off everything will work as it should. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Sep 24 00:24:03 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] [10de:1c82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. GP107 [GeForce GTX 1050 Ti] [19da:2454] InstallationDate: Installed on 2019-07-16 (69 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Gigabyte Technology Co., Ltd. GA-78LMT-USB3 6.0 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-29-generic root=UUID=dfa66545-9ac3-41fa-817b-433d8a61bd78 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/25/2014 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F2 dmi.board.name: GA-78LMT-USB3 6.0 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd11/25/2014:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-USB36.0:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-USB36.0:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-78LMT-USB3 6.0 dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1845076/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1845076] Re: [nouveau] Gnome shell/Xorg freeze after remote connection with monitor unplugged
[Expired for mutter (Ubuntu) because there has been no activity for 60 days.] ** Changed in: mutter (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1845076 Title: [nouveau] Gnome shell/Xorg freeze after remote connection with monitor unplugged Status in gnome-shell package in Ubuntu: Expired Status in mutter package in Ubuntu: Expired Bug description: I was trying to have a remote connection on a Ubuntu 18.04 pc with nomachine (but the behavior with Anydesk is the same) AFTER I unplugged the monitor form that pc. Once connected the output on the client freeze by just opening the Activities panel. If I plug the monitor back in on the server, the gnome shell is glitched and the only way to gain back control is by doing ALT F2 and then r. If I keep the monitor plugged in but turned off everything will work as it should. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Sep 24 00:24:03 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] [10de:1c82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. GP107 [GeForce GTX 1050 Ti] [19da:2454] InstallationDate: Installed on 2019-07-16 (69 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Gigabyte Technology Co., Ltd. GA-78LMT-USB3 6.0 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-29-generic root=UUID=dfa66545-9ac3-41fa-817b-433d8a61bd78 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/25/2014 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F2 dmi.board.name: GA-78LMT-USB3 6.0 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd11/25/2014:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-USB36.0:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-USB36.0:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-78LMT-USB3 6.0 dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1845076/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1846006] Re: package ibus-gtk3:amd64 1.5.11-1ubuntu2 failed to install/upgrade: package ibus-gtk3:amd64 is not ready for configuration cannot configure (current status 'half-in
[Expired for ibus (Ubuntu) because there has been no activity for 60 days.] ** Changed in: ibus (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1846006 Title: package ibus-gtk3:amd64 1.5.11-1ubuntu2 failed to install/upgrade: package ibus-gtk3:amd64 is not ready for configuration cannot configure (current status 'half-installed') Status in ibus package in Ubuntu: Expired Bug description: The PC keeps giving that there is a bug and tells to report it ProblemType: Package DistroRelease: Ubuntu 16.04 Package: ibus-gtk3:amd64 1.5.11-1ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-62.69~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-62-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.19 Architecture: amd64 Date: Mon Sep 30 22:50:47 2019 DuplicateSignature: package:ibus-gtk3:amd64:1.5.11-1ubuntu2 Processing triggers for mime-support (3.59ubuntu1) ... dpkg: error processing package ibus-gtk3:amd64 (--configure): package ibus-gtk3:amd64 is not ready for configuration ErrorMessage: package ibus-gtk3:amd64 is not ready for configuration cannot configure (current status 'half-installed') InstallationDate: Installed on 2018-03-28 (551 days ago) InstallationMedia: Ubuntu-GNOME 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.29ubuntu0.1 SourcePackage: ibus Title: package ibus-gtk3:amd64 1.5.11-1ubuntu2 failed to install/upgrade: package ibus-gtk3:amd64 is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1846006/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1791981] Re: X Server session crash for "No space left on device"
Filed a question within nvidia forum: https://devtalk.nvidia.com/default/topic/1066963/linux/if-laptop-lid-is- closed-during-suspend-quot-failed-to-set-mode-no-space-left-on-device- quot-upon-resume/post/5406357/ so far no closure -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1791981 Title: X Server session crash for "No space left on device" Status in xorg-server package in Ubuntu: Confirmed Bug description: Ubuntu Release: Ubuntu 18.04.1 LTS Package version: xserver-xorg: 1:7.7+19ubuntu7.1 When my laptop resumes after suspend, the desktop session crashes and a new one is started. So each time I lose all open applications and unsaved data! The expected behavior would be obviously to restore the suspended session. I had a look through log files and found that Xorg.0.log ends with the following error lines: [ 6004.019] (II) NVIDIA(0): Setting mode "NULL" [ 6004.026] (EE) modeset(G0): failed to set mode: No space left on device [ 6004.026] (EE) Fatal server error: [ 6004.026] (EE) EnterVT failed for gpu screen 0 [ 6004.027] (EE) [ 6004.027] (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help. [ 6004.027] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information. [ 6004.027] (EE) [ 6004.065] (EE) Server terminated with error (1). Closing log file. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1791981/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1843695] Re: Freeze after suspend to RAM nvidia kernel 5.0.0.x
@gregordarius is it possible to apply this patch on your own? could you post more detailed instructions? I am having exactly the same error as you and I can solve it with all the ways you mentioned before. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-430 in Ubuntu. https://bugs.launchpad.net/bugs/1843695 Title: Freeze after suspend to RAM nvidia kernel 5.0.0.x Status in nvidia-graphics-drivers-430 package in Ubuntu: Confirmed Bug description: The computer is a notebook model PB71RD from Clevo. The problem happens in all Clevo models: P960E*, P970E*, P960R*, P970R*, P960RC*, P970RC, PB51E*, PB71E*, PB51R*, PB71R* with mainboard identifiers (cat /sys/devices/virtual/dmi/id/board_name): - P95_96_97Ex_Rx - PB50_70EF_ED_EC - PB50_70RF_RD_RC - P9XXRC and NVIDIA GPU (in this case: GeForce RTX 2060 and also on GeForce GTX 1660 Ti). The problem only happens with kernel >= 5.0.0 and using the NVIDIA proprietary driver. On kernel 4.18 suspend works without problems on both GPU's (NVIDIA and Intel) When using the Intel GPU or the nouveau driver then suspend works without problems. With kernel 4.18 suspend works without problems on both GPU's. | NVIDIA proprietary | Intel GPU | nouveau | | kernel 4.18| works | works | works | | kernel 5.0.0.x | no suspend | works | works | I have tried different proprietary drivers, official Ubuntu Versions and from PPA: 418 430.26 435.21 The notebook has a hybrid GPU configuration with NVIDIA and Intel GPUs. The notebook goes into suspend when pressing the suspend button (Fn- suspend). When pressing the suspend button again, the power button light goes on and nothing else happens. | power button | power LED | Battery LED | HD LED Notebook on | on | on| on | sporadic suspend | off | blinking | on | off freeze after | on | on| on | off activated from STR The system is a Ubuntu 18.04.3 cat /etc/issue: Ubuntu 18.04.3 LTS \n \l uname -a: Linux test-notebook 5.0.0-27-generic #28~18.04.1-Ubuntu SMP Thu Aug 22 03:00:32 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux I first thought that it could be an ACPI-Problem. I reluctantly tried acpi_osi=linux and all other OS's (as listed in: strings /sys/firmware/acpi/tables/DSDT | grep -i windows | sort) for GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub Also acpi_os_name=linux Also tried to blacklist the nouveau driver. Nothing helped. Then i found out that a driver from pop-os launchpad worked. I posted a possible solution on the button of this message. LOGFILES: I will attach now the logfiles as required on the Ubuntu Website DebuggingKernelSuspend (https://wiki.ubuntu.com/DebuggingKernelSuspend) dmesg.txt from: sh -c "sync && echo 1 > /sys/power/pm_trace && pm- suspend" I think the problem might be this: [2.797119] Magic number: 2:1:0 [2.797623] memory memory48: hash matches Answers to DebuggingKernelSuspend: 1. the system freezes when comming back from STR 2. suspend was activated by pressing: Fn+suspendButton 3. resume was activated by pressing: Fn+suspendButton 4. As required i installed the newest non-daily mainline kernel (v5.3-rc8) now the notebook refuses to go into freeze at all, it just returns to the desktop As the fix described below works only on kernel 5.0.0.x i will continue with information gathered with the kernel 5.0.0.27-generic The logs are all attached to this message. POSSIBLE SOLUTION: The solution i found was a patch for nvidia-kernel-source-435 pop-os included the patch into nvidia-dkms-435: diff --git a/nvidia/nv.c b/nvidia/nv.c index b6dc6f3..ed250c8 100644 --- a/nvidia/nv.c +++ b/nvidia/nv.c @@ -4200,8 +4200,6 @@ nv_power_management( nv_kthread_q_stop(>bottom_half_q); nv_disable_pat_support(); - -pci_save_state(nvl->pci_dev); break; } case NV_PM_ACTION_RESUME: I testet it with different notebook models from Clevo with a different hardware than mentioned above . It had no adverse effects so far. Is this a possible solution? Could this be sent upstream? I would gladly provide more information if necessary. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nvidia-driver-430 430.26-0ubuntu0.18.04.2 ProcVersionSignature: Ubuntu 5.0.0-27.28~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Sep 12 11:52:09 2019 InstallationDate: Installed on 2019-09-12 (0 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
[Desktop-packages] [Bug 997934]
Changing priority back to 'medium' since the number of duplicates is lower than 5 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/997934 Title: [Upstream] Spell checking doesn't warn users if the selected dictionary isn't installed, but rather returns a potentially incorrect result Status in LibreOffice: Confirmed Status in libreoffice package in Ubuntu: Confirmed Bug description: This has been the case since Beta 2. To reproduce: 1) Type out a load of rubbish on the keyboard as well as a few correctly spelled words. I used "vmw;qbjk aoeuasnth aoeu house in the street" 2) Press F7 to initiate the spell check. Actual Result: The spell check notifies the user of completion without any recognition of errors. Expected Result: The spell check should highlight each misspelled word and offer alternatives. WORKAROUND: Open the dash and run Language Support 2) Under the 'Language' tab, choose another variant of English and drag it above the US English so it takes precedence. 3) Click "Apply System-wide" and log out. On logging back in, spell check will work. Not reproducible in Xubuntu 32-bit. lsb_release -rd Description: Ubuntu 12.04 LTS Release: 12.04 apt-cache policy libreoffice-writer libreoffice-writer: Installed: 1:3.5.3-0ubuntu1 Candidate: 1:3.5.3-0ubuntu1 Version table: *** 1:3.5.3-0ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ precise-updates/main i386 Packages 100 /var/lib/dpkg/status 1:3.5.2-2ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ precise/main i386 Packages ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: libreoffice-writer 1:3.5.3-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-24.37-generic-pae 3.2.14 Uname: Linux 3.2.0-24-generic-pae i686 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu7 Architecture: i386 Date: Fri May 11 08:53:51 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta i386 (20120328) ProcEnviron: LANGUAGE=en_IE:en TERM=xterm PATH=(custom, no user) LANG=en_IE.UTF-8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/997934/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1421575] Re: Desktop corruption when changing monitor config
** Changed in: xserver-xorg-video-intel Status: Confirmed => Unknown ** Bug watch added: gitlab.freedesktop.org/xorg/driver/xf86-video-intel/issues #67 https://gitlab.freedesktop.org/xorg/driver/xf86-video-intel/issues/67 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1421575 Title: Desktop corruption when changing monitor config Status in xf86-video-intel: Unknown Status in xserver-xorg-video-intel package in Ubuntu: Incomplete Bug description: Thinkpad X220 running vivid up to date. Usually sits in docking station with external monitor. Today I ran the laptop outside the docking station, and plugged it into the dock while running (which worked fine forever on utopic) but today it now freaks out. I deleted ~/.config/monitors.xml to reset my display config I restarted and logged in with both monitors active. As soon as I change the display config doing the display corrupts, flickers and becomes unusable. Here's a photo:- http://imgur.com/80LcmgV ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2 Uname: Linux 3.19.0-031900rc7-generic x86_64 ApportVersion: 2.16.1-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Fri Feb 13 08:58:00 2015 DistUpgraded: 2015-02-05 11:21:00,051 DEBUG enabling apt cron job DistroCodename: vivid DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:21da] InstallationDate: Installed on 2014-06-16 (241 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: LENOVO 4287CTO ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-031900rc7-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-video-intel UpgradeStatus: Upgraded to vivid on 2015-02-05 (7 days ago) dmi.bios.date: 07/18/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET69WW (1.39 ) dmi.board.asset.tag: Not Available dmi.board.name: 4287CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8DET69WW(1.39):bd07/18/2013:svnLENOVO:pn4287CTO:pvrThinkPadX220:rvnLENOVO:rn4287CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4287CTO dmi.product.version: ThinkPad X220 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.0+15.04.20150202-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.58-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.4.2-2ubuntu5 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.4.2-2ubuntu5 version.xserver-xorg-core: xserver-xorg-core 2:1.16.2.901-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Fri Feb 13 08:53:15 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 728 vendor LGD xserver.version: 2:1.16.2.901-1ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/1421575/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1421575]
-- 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/xorg/driver/xf86-video-intel/issues/67. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1421575 Title: Desktop corruption when changing monitor config Status in xf86-video-intel: Unknown Status in xserver-xorg-video-intel package in Ubuntu: Incomplete Bug description: Thinkpad X220 running vivid up to date. Usually sits in docking station with external monitor. Today I ran the laptop outside the docking station, and plugged it into the dock while running (which worked fine forever on utopic) but today it now freaks out. I deleted ~/.config/monitors.xml to reset my display config I restarted and logged in with both monitors active. As soon as I change the display config doing the display corrupts, flickers and becomes unusable. Here's a photo:- http://imgur.com/80LcmgV ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2 Uname: Linux 3.19.0-031900rc7-generic x86_64 ApportVersion: 2.16.1-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Fri Feb 13 08:58:00 2015 DistUpgraded: 2015-02-05 11:21:00,051 DEBUG enabling apt cron job DistroCodename: vivid DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:21da] InstallationDate: Installed on 2014-06-16 (241 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: LENOVO 4287CTO ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-031900rc7-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-video-intel UpgradeStatus: Upgraded to vivid on 2015-02-05 (7 days ago) dmi.bios.date: 07/18/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET69WW (1.39 ) dmi.board.asset.tag: Not Available dmi.board.name: 4287CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8DET69WW(1.39):bd07/18/2013:svnLENOVO:pn4287CTO:pvrThinkPadX220:rvnLENOVO:rn4287CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4287CTO dmi.product.version: ThinkPad X220 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.0+15.04.20150202-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.58-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.4.2-2ubuntu5 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.4.2-2ubuntu5 version.xserver-xorg-core: xserver-xorg-core 2:1.16.2.901-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Fri Feb 13 08:53:15 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 728 vendor LGD xserver.version: 2:1.16.2.901-1ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/1421575/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1794478] Re: Automatic ipv4 not assigned to bond interface is manual ipv6 is assigned to it
Hi, all. I'm afraid I'll need to reopen this bug. I was able to reproduce the issue on Bionic, using network-manager 1.10.6-2ubuntu1.2. However, when testing this on Eoan, using network- manager 1.20.4-2ubuntu2, I didn't reproduce the behaviour. The steps one takes to reproduce the issue, either on a s390 system or x86 (the issue is reproducible regardless of the platform) is: 1.) Create the bond interface with: nmcli conn add type bond con-name ifname ipv4.method disabled ipv6.method ignore 2.) Modify it to so set a manual IPv6 Address and auto-assign IPv4: nmcli c m bond.options " mode=active-backup, downdelay=0 , miimon=100 , updelay=0 , fail_over_mac=none , num_grat_arp=0 , primary_reselect=always " connection.interface-name ipv4.method auto ipv4.gateway "" ipv6.method manual 802-3-ethernet.mac-address "" ipv4.routes "" connection.id ipv6.never-default no ipv4.addresses "" ipv6.addresses 3.) Add the two slave ethernet devices, and change them with: nmcli c m connection.id connection .interface-name 802-3-ethernet.s390-subchannels 802-3-ethernet.s390-nettype qeth connection.autoconnect yes 802-3-ethernet.mac-address "" ipv4.method disabled ipv6.method ignore 802-3-ethernet.s390-options portno= ^ For repro steps on amd64 or ppc64, the s390-* parameters can be removed from the command. 4.) Add the two slave ethernet devices to the bond: nmcli c m 802-3-ethernet.mac-address "" connection.master connection.slave-type bond [ . . . ] You'll see that, on Bionic, the bond interface isn't assigned an IPv4 address. On Eoan, an IPv4 address is assigned as expected. I have reviewed network-manager's changelog [1], but I didn't find any smoking guns that could've solved the issue, hence the re-opening of the bug. Let me know if further evidence is needed to proceed. Thanks! [1] https://changelogs.ubuntu.com/changelogs/pool/main/n/network-manager /network-manager_1.20.4-2ubuntu2/changelog -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1794478 Title: Automatic ipv4 not assigned to bond interface is manual ipv6 is assigned to it Status in Ubuntu on IBM z Systems: Fix Released Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Bionic: Fix Released Bug description: ---Problem Description--- Bond interface with automatic ipv4 mode and manual ipv6 mode fails to get automatic ipv4 assigned from dhcp server. ---uname output--- Linux NetworkTest 4.15.0-33-generic #36-Ubuntu SMP Wed Aug 15 13:42:17 UTC 2018 s390x s390x s390x GNU/Linux Machine Type = s390x ---Debugger--- A debugger is not configured ---Steps to Reproduce--- When user configures ipv4 as automatic and ipv6 as manual for bond interface automatic ipv4 is not getting assigned. Looks like dhcp client request for ipv4 is not done to dhcp server after maunal ipv6 is assigned quickly to bond interface This issue will not happen in below cases: 1)with ipv4 automatic and ipv6 manual configuration for ethernet or vlan interface. 2)with ipv4 automatic and ipv6 automatic configuration for bond interface 3)with ipv4 automatic and ipv6 disabled configuration for bond interface Configuration: Bond interface, ipv4 automatic mode and ipv6 automatic mode root@NetworkTest:/etc/NetworkManager/system-connections# cat test_bond [connection] id=test_bond uuid=63e54542-5135-47ac-a954-b861c3937be2 type=bond interface-name=test_bond permissions= timestamp=1537944121 [ethernet] mac-address-blacklist= [bond] downdelay=0 fail_over_mac=none miimon=100 mode=active-backup num_grat_arp=0 primary_reselect=always updelay=0 [ipv4] dns-search= method=auto [ipv6] addr-gen-mode=stable-privacy dns-search= method=auto From /var/log/syslog, we can see ip got assigned: Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPDISCOVER on test_bond to 255.255.255.255 port 67 interval 3 (xid=0x5e04bf1e) Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPREQUEST of 10.2.3.55 on test_bond to 255.255.255.255 port 67 (xid=0x5e04bf1e) Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPOFFER of 10.2.3.55 from 10.2.3.1 Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPACK of 10.2.3.55 from 10.2.3.1 root@NetworkTest:/etc/NetworkManager/system-connections# ip a s test_bond 28: test_bond: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 02:00:00:b3:b5:22 brd ff:ff:ff:ff:ff:ff inet 10.2.3.55/24 brd 10.2.3.255 scope global dynamic noprefixroute test_bond valid_lft 353sec preferred_lft 353sec inet6 fe80::ff:feb3:b522/64 scope link valid_lft forever preferred_lft forever +++ Bond interface, ipv4
[Desktop-packages] [Bug 1854537] [NEW] When I ran "update-grub" after editing the grub.conf file to have GRUB_CMDLINE_LINUX="nomodeset" written in it, the screen turned to black and displayed the runn
Public bug reported: When I ran "sudo update-grub" after changing the line in grub.conf to be "GRUB_CMDLINE_LINUX="nomodeset", the screen turned to black and the windows would not appear. I was forced to open a tty session and reboot. Expected Results: The command runs but the screen does not turn black until I initiate a shutdown/reboot Actual Results: The screen turns black and the startup tasks and status appear over a black background, as it would when I push the up key when ubuntu starts up. This issue occurred at around 3:47 PM, EDT, on November 29, 2019. Description: Ubuntu 18.04.3 LTS Release: 18.04 mutter: Installed: 3.28.4-0ubuntu18.04.2 Candidate: 3.28.4-0ubuntu18.04.2 Version table: *** 3.28.4-0ubuntu18.04.2 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.28.1-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages xorg: Installed: 1:7.7+19ubuntu7.1 Candidate: 1:7.7+19ubuntu7.1 Version table: *** 1:7.7+19ubuntu7.1 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:7.7+19ubuntu7 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18 Uname: Linux 4.15.0-70-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 Date: Fri Nov 29 15:40:27 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM] [1002:6779] (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM] [1682:3207] MachineType: Gateway DX4860 ProcEnviron: TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-70-generic root=UUID=751019b9-8693-494c-ad69-17ddf9e51235 ro radeon.modeset=0 splash quiet vt.handoff=1 Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/01/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P02-A1 dmi.board.name: IPISB-VR dmi.board.vendor: Gateway dmi.board.version: 1.01 dmi.chassis.type: 3 dmi.chassis.vendor: Gateway dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP02-A1:bd08/01/2011:svnGateway:pnDX4860:pvr:rvnGateway:rnIPISB-VR:rvr1.01:cvnGateway:ct3:cvr: dmi.product.family: Gateway Desktop dmi.product.name: DX4860 dmi.sys.vendor: Gateway version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 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 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1854537 Title: When I ran "update-grub" after editing the grub.conf file to have GRUB_CMDLINE_LINUX="nomodeset" written in it, the screen turned to black and displayed the running taks with the green "OK" letters next to them Status in xorg package in Ubuntu: New Bug description: When I ran "sudo update-grub" after changing the line in grub.conf to be "GRUB_CMDLINE_LINUX="nomodeset", the screen turned to black and the windows would not appear. I was forced to open a tty session and reboot. Expected Results: The command runs but the screen does not turn black until I initiate a shutdown/reboot Actual Results: The screen turns black and the startup tasks and status appear over a black background, as it would when I push the up key when ubuntu starts up. This issue occurred at around 3:47 PM, EDT, on November 29, 2019. Description: Ubuntu 18.04.3 LTS Release: 18.04 mutter: Installed: 3.28.4-0ubuntu18.04.2 Candidate: 3.28.4-0ubuntu18.04.2 Version table: *** 3.28.4-0ubuntu18.04.2 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.28.1-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages xorg: Installed: 1:7.7+19ubuntu7.1 Candidate: 1:7.7+19ubuntu7.1 Version table: *** 1:7.7+19ubuntu7.1 500 500
[Desktop-packages] [Bug 1854536] [NEW] When I ran "update-grub" after editing the grub.conf file to have GRUB_CMDLINE_LINUX="nomodeset" written in it, the screen turned to black and displayed the runn
Public bug reported: When I ran "sudo update-grub" after changing the line in grub.conf to be "GRUB_CMDLINE_LINUX="nomodeset", the screen turned to black and the windows would not appear. I was forced to open a tty session and reboot. Expected Results: The command runs but the screen does not turn black until I initiate a shutdown/reboot Actual Results: The screen turns black and the startup tasks and status appear over a black background, as it would when I push the up key when ubuntu starts up. This issue occurred at around 3:47 PM, EDT, on November 29, 2019. Description:Ubuntu 18.04.3 LTS Release:18.04 mutter: Installed: 3.28.4-0ubuntu18.04.2 Candidate: 3.28.4-0ubuntu18.04.2 Version table: *** 3.28.4-0ubuntu18.04.2 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.28.1-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages xorg: Installed: 1:7.7+19ubuntu7.1 Candidate: 1:7.7+19ubuntu7.1 Version table: *** 1:7.7+19ubuntu7.1 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:7.7+19ubuntu7 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: mutter 3.28.4-0ubuntu18.04.2 ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18 Uname: Linux 4.15.0-70-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Nov 29 15:45:03 2019 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1854536 Title: When I ran "update-grub" after editing the grub.conf file to have GRUB_CMDLINE_LINUX="nomodeset" written in it, the screen turned to black and displayed the running taks with the green "OK" letters next to them Status in mutter package in Ubuntu: New Bug description: When I ran "sudo update-grub" after changing the line in grub.conf to be "GRUB_CMDLINE_LINUX="nomodeset", the screen turned to black and the windows would not appear. I was forced to open a tty session and reboot. Expected Results: The command runs but the screen does not turn black until I initiate a shutdown/reboot Actual Results: The screen turns black and the startup tasks and status appear over a black background, as it would when I push the up key when ubuntu starts up. This issue occurred at around 3:47 PM, EDT, on November 29, 2019. Description: Ubuntu 18.04.3 LTS Release: 18.04 mutter: Installed: 3.28.4-0ubuntu18.04.2 Candidate: 3.28.4-0ubuntu18.04.2 Version table: *** 3.28.4-0ubuntu18.04.2 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.28.1-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages xorg: Installed: 1:7.7+19ubuntu7.1 Candidate: 1:7.7+19ubuntu7.1 Version table: *** 1:7.7+19ubuntu7.1 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:7.7+19ubuntu7 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: mutter 3.28.4-0ubuntu18.04.2 ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18 Uname: Linux 4.15.0-70-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Nov 29 15:45:03 2019 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1854536/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1496542] Re: Running processes left after disabling screen reader
Howdy, also seeing speech-dispatcher running on 19.10. Some anecdotal info is that I restarted and tried enabling and then disabling Screen Reader on the login screen and it hasn't appeared in my sessions today since, including a few more restarts. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to speech-dispatcher in Ubuntu. https://bugs.launchpad.net/bugs/1496542 Title: Running processes left after disabling screen reader Status in speech-dispatcher package in Ubuntu: Triaged Bug description: After I disabled my screen reader, I noticed that when running "ps xa | grep -P 'speech-dispatcher.*\.conf'" I get: 17906 tty2 Sl+0:09 /usr/lib/speech-dispatcher-modules/sd_espeak /etc/speech-dispatcher/modules/espeak.conf 17911 tty2 Sl+0:01 /usr/lib/speech-dispatcher-modules/sd_cicero /etc/speech-dispatcher/modules/cicero.conf 17915 tty2 Sl+0:01 /usr/lib/speech-dispatcher-modules/sd_generic /etc/speech-dispatcher/modules/generic.conf 17918 tty2 Sl+0:01 /usr/lib/speech-dispatcher-modules/sd_dummy /etc/speech-dispatcher/modules/dummy.conf 24407 pts/0S+ 0:00 grep --color=auto -P speech-dispatcher.*\.conf So it seems as though it left some running processes behind after I disabled it. I have also attached a screenshot of my Sound settings which show that they are still running (Sound_Application_List2.png). --- OS Information: No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 15.04 Release: 15.04 Codename: vivid Package Information: speech-dispatcher: Installed: 0.8.1-0ubuntu1 Candidate: 0.8.1-0ubuntu1 Version table: *** 0.8.1-0ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: speech-dispatcher 0.8.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5 Uname: Linux 3.19.0-28-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.4 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Sep 16 20:27:00 2015 InstallationDate: Installed on 2015-07-29 (49 days ago) InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: speech-dispatcher UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/speech-dispatcher/+bug/1496542/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 749443] Re: LAME 3.98.4 wrong tagged as 3.98.2 | Meerkat 64bit
This issue has been fixed. ** Changed in: lame (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lame in Ubuntu. https://bugs.launchpad.net/bugs/749443 Title: LAME 3.98.4 wrong tagged as 3.98.2 | Meerkat 64bit Status in lame package in Ubuntu: Fix Released Bug description: Binary package hint: lame If i start encoding a wave file in shell, i got this "LAME 3.98.2 64bits (http://www.mp3dev.org/)" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lame/+bug/749443/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1775881] Re: [radeon] Wayland sessions including the login screen are just static noise
New Report: 1854534 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1775881 Title: [radeon] Wayland sessions including the login screen are just static noise Status in gdm3 package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: Ubuntu Version 18.04 LTS gdm3: Installed: 3.28.0-0ubuntu1 500 Package name: /etc/gdm3 Whenever I boot Ubuntu following installation from the official install ISO, the boot screen appears, but the login manager appears as static, scrambled graphics, making me unable to login without opening the VT and installing lightdm and switching to that login manager. Expected Results: Login manager appears with login field, background, and menu while I am able to find, click, and enter information into the login text fields. Actual Results: Scrambled noise appeared on my screen and I am unable to leave without force-shutting down my Gateway PC, or opening a VT and installing lightdm, rebooting afterwards. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Fri Jun 8 11:41:23 2018 InstallationDate: Installed on 2018-06-07 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 Package: mutter PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-70-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.gdm3.custom.conf: 2019-11-29T12:32:53.022462 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 DistroRelease: Ubuntu 18.04 Package: mutter PackageArchitecture: amd64 ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-70-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.gdm3.custom.conf: 2019-11-29T13:14:23.686888 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1775881/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1854534] Re: [radeon] Wayland sessions including the login screen are just static noise
** Attachment added: "xdpyinfo.txt" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1854534/+attachment/5308810/+files/xdpyinfo.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1854534 Title: [radeon] Wayland sessions including the login screen are just static noise Status in xorg-server package in Ubuntu: New Bug description: Whenever I boot Ubuntu following installation from the official install ISO, the boot screen appears, but the login manager appears as static, scrambled graphics, making me unable to login without opening the VT and installing lightdm and switching to that login manager. Expected Results: Login manager appears with login field, background, and menu while I am able to find, click, and enter information into the login text fields. Actual Results: Scrambled noise appeared on my screen and I am unable to leave without force-shutting down my Gateway PC, or opening a VT and disabling Wayland via editing GDM's custom.conf file. Description: Ubuntu 18.04.3 LTS Release: 18.04 xwayland: Installed: 2:1.19.6-1ubuntu4.3 Candidate: 2:1.19.6-1ubuntu4.3 Version table: *** 2:1.19.6-1ubuntu4.3 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 2:1.19.6-1ubuntu4.2 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 2:1.19.6-1ubuntu4 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xwayland 2:1.19.6-1ubuntu4.3 ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18 Uname: Linux 4.15.0-70-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 Date: Fri Nov 29 13:26:56 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM] [1002:6779] (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM] [1682:3207] MachineType: Gateway DX4860 ProcEnviron: TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-70-generic root=UUID=751019b9-8693-494c-ad69-17ddf9e51235 ro splash quiet vt.handoff=1 SourcePackage: xorg-server UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/01/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P02-A1 dmi.board.name: IPISB-VR dmi.board.vendor: Gateway dmi.board.version: 1.01 dmi.chassis.type: 3 dmi.chassis.vendor: Gateway dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP02-A1:bd08/01/2011:svnGateway:pnDX4860:pvr:rvnGateway:rnIPISB-VR:rvr1.01:cvnGateway:ct3:cvr: dmi.product.family: Gateway Desktop dmi.product.name: DX4860 dmi.sys.vendor: Gateway version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1854534/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1851910] Re: Display does not show up (short flashes)
** Description changed: This issue started recently (I think it could be related to some package update. Steps to reproduce: - Power the PC on; - BIOS Boot screen (not visible, the display is off); - GRUB screen (not visible, the display is off); - Gnome Login screen (not visible, the display is off). Workaround: - - after a reasonable time for the Gnome Login Screen to be reached, inserting my user password starts the desktop session. Screen is never shown on first try (the best is to see short flashes of the desktop in the screen). The display keeps on trying to start. - - long press the power button to force power down and immedeately switch the PC back on --> after 1 or more workaround cycles the screen is shown (sometimes with wrong horizontal placement). + - after a reasonable time for the Gnome Login Screen to be reached, inserting my user password starts the desktop session. Screen is never shown on first try (the best I can get are short flashes of the desktop in the screen). The display keeps on trying to start. + - long press the power button to force power down and immediately switch the PC back on --> after 1 or more workaround cycles the screen is shown (sometimes with wrong horizontal placement). After the display is working, it works smoothly until the next power down (i.e. if I reboot the PC everything is visible from the BIOS Boot screen onward. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18 Uname: Linux 4.15.0-39-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..09.00.0: Error: [Errno 21] È una directory: '/proc/driver/nvidia/gpus/:09:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 430.50 Thu Sep 5 22:36:31 CDT 2019 GCC version: gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1) ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 BootLog: Error: [Errno 13] Permesso negato: '/var/log/boot.log' CompizPlugins: [core,composite,opengl,decor,regex,compiztoolbox,move,resize,imgpng,place,animation,expo,grid,vpswitch,mousepoll,workarounds,snap,gnomecompat,unitymtgrabhandles,session,ezoom,wall,fade,scale,unityshell] CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Nov 9 09:20:50 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 430.50, 4.15.0-39-generic, x86_64: installed nvidia, 430.50, 4.15.0-66-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] [10de:1c82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP107 [GeForce GTX 1050 Ti] [1043:8613] MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-39-generic root=UUID=0c1fbe60-f395-4935-a4dc-eaea4ee92682 ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/07/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4024 dmi.board.asset.tag: Default string dmi.board.name: PRIME X370-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4024:bd09/07/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX370-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 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 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1851910 Title: Display does not show up (short flashes) Status in xorg package in Ubuntu: New Bug description: This issue started recently (I think it could be
[Desktop-packages] [Bug 1854534] Re: [radeon] Wayland sessions including the login screen are just static noise
** Attachment added: "xrandr from when I run xorg instead of wayland (despite the bug being for wayland)" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1854534/+attachment/5308809/+files/Xrandr.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1854534 Title: [radeon] Wayland sessions including the login screen are just static noise Status in xorg-server package in Ubuntu: New Bug description: Whenever I boot Ubuntu following installation from the official install ISO, the boot screen appears, but the login manager appears as static, scrambled graphics, making me unable to login without opening the VT and installing lightdm and switching to that login manager. Expected Results: Login manager appears with login field, background, and menu while I am able to find, click, and enter information into the login text fields. Actual Results: Scrambled noise appeared on my screen and I am unable to leave without force-shutting down my Gateway PC, or opening a VT and disabling Wayland via editing GDM's custom.conf file. Description: Ubuntu 18.04.3 LTS Release: 18.04 xwayland: Installed: 2:1.19.6-1ubuntu4.3 Candidate: 2:1.19.6-1ubuntu4.3 Version table: *** 2:1.19.6-1ubuntu4.3 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 2:1.19.6-1ubuntu4.2 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 2:1.19.6-1ubuntu4 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xwayland 2:1.19.6-1ubuntu4.3 ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18 Uname: Linux 4.15.0-70-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 Date: Fri Nov 29 13:26:56 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM] [1002:6779] (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM] [1682:3207] MachineType: Gateway DX4860 ProcEnviron: TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-70-generic root=UUID=751019b9-8693-494c-ad69-17ddf9e51235 ro splash quiet vt.handoff=1 SourcePackage: xorg-server UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/01/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P02-A1 dmi.board.name: IPISB-VR dmi.board.vendor: Gateway dmi.board.version: 1.01 dmi.chassis.type: 3 dmi.chassis.vendor: Gateway dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP02-A1:bd08/01/2011:svnGateway:pnDX4860:pvr:rvnGateway:rnIPISB-VR:rvr1.01:cvnGateway:ct3:cvr: dmi.product.family: Gateway Desktop dmi.product.name: DX4860 dmi.sys.vendor: Gateway version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1854534/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1854534] [NEW] [radeon] Wayland sessions including the login screen are just static noise
Public bug reported: Whenever I boot Ubuntu following installation from the official install ISO, the boot screen appears, but the login manager appears as static, scrambled graphics, making me unable to login without opening the VT and installing lightdm and switching to that login manager. Expected Results: Login manager appears with login field, background, and menu while I am able to find, click, and enter information into the login text fields. Actual Results: Scrambled noise appeared on my screen and I am unable to leave without force-shutting down my Gateway PC, or opening a VT and disabling Wayland via editing GDM's custom.conf file. Description:Ubuntu 18.04.3 LTS Release:18.04 xwayland: Installed: 2:1.19.6-1ubuntu4.3 Candidate: 2:1.19.6-1ubuntu4.3 Version table: *** 2:1.19.6-1ubuntu4.3 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 2:1.19.6-1ubuntu4.2 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 2:1.19.6-1ubuntu4 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xwayland 2:1.19.6-1ubuntu4.3 ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18 Uname: Linux 4.15.0-70-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 Date: Fri Nov 29 13:26:56 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM] [1002:6779] (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM] [1682:3207] MachineType: Gateway DX4860 ProcEnviron: TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-70-generic root=UUID=751019b9-8693-494c-ad69-17ddf9e51235 ro splash quiet vt.handoff=1 SourcePackage: xorg-server UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/01/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P02-A1 dmi.board.name: IPISB-VR dmi.board.vendor: Gateway dmi.board.version: 1.01 dmi.chassis.type: 3 dmi.chassis.vendor: Gateway dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP02-A1:bd08/01/2011:svnGateway:pnDX4860:pvr:rvnGateway:rnIPISB-VR:rvr1.01:cvnGateway:ct3:cvr: dmi.product.family: Gateway Desktop dmi.product.name: DX4860 dmi.sys.vendor: Gateway version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 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 ** Affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1854534 Title: [radeon] Wayland sessions including the login screen are just static noise Status in xorg-server package in Ubuntu: New Bug description: Whenever I boot Ubuntu following installation from the official install ISO, the boot screen appears, but the login manager appears as static, scrambled graphics, making me unable to login without opening the VT and installing lightdm and switching to that login manager. Expected Results: Login manager appears with login field, background, and menu while I am able to find, click, and enter information into the login text fields. Actual Results: Scrambled noise appeared on my screen and I am unable to leave without force-shutting down my Gateway PC, or opening a VT and disabling Wayland via editing GDM's custom.conf file. Description: Ubuntu 18.04.3 LTS Release: 18.04 xwayland: Installed: 2:1.19.6-1ubuntu4.3 Candidate: 2:1.19.6-1ubuntu4.3 Version table: *** 2:1.19.6-1ubuntu4.3 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 2:1.19.6-1ubuntu4.2 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 2:1.19.6-1ubuntu4 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xwayland 2:1.19.6-1ubuntu4.3 ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18 Uname: Linux 4.15.0-70-generic x86_64 ApportVersion:
[Desktop-packages] [Bug 1775881] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1775881/+attachment/5308797/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1775881 Title: [radeon] Wayland sessions including the login screen are just static noise Status in gdm3 package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: Ubuntu Version 18.04 LTS gdm3: Installed: 3.28.0-0ubuntu1 500 Package name: /etc/gdm3 Whenever I boot Ubuntu following installation from the official install ISO, the boot screen appears, but the login manager appears as static, scrambled graphics, making me unable to login without opening the VT and installing lightdm and switching to that login manager. Expected Results: Login manager appears with login field, background, and menu while I am able to find, click, and enter information into the login text fields. Actual Results: Scrambled noise appeared on my screen and I am unable to leave without force-shutting down my Gateway PC, or opening a VT and installing lightdm, rebooting afterwards. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Fri Jun 8 11:41:23 2018 InstallationDate: Installed on 2018-06-07 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 Package: mutter PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-70-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.gdm3.custom.conf: 2019-11-29T12:32:53.022462 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 DistroRelease: Ubuntu 18.04 Package: mutter PackageArchitecture: amd64 ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-70-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.gdm3.custom.conf: 2019-11-29T13:14:23.686888 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1775881/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1775881] modified.conffile..etc.gdm3.custom.conf.txt
apport information ** Attachment added: "modified.conffile..etc.gdm3.custom.conf.txt" https://bugs.launchpad.net/bugs/1775881/+attachment/5308798/+files/modified.conffile..etc.gdm3.custom.conf.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1775881 Title: [radeon] Wayland sessions including the login screen are just static noise Status in gdm3 package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: Ubuntu Version 18.04 LTS gdm3: Installed: 3.28.0-0ubuntu1 500 Package name: /etc/gdm3 Whenever I boot Ubuntu following installation from the official install ISO, the boot screen appears, but the login manager appears as static, scrambled graphics, making me unable to login without opening the VT and installing lightdm and switching to that login manager. Expected Results: Login manager appears with login field, background, and menu while I am able to find, click, and enter information into the login text fields. Actual Results: Scrambled noise appeared on my screen and I am unable to leave without force-shutting down my Gateway PC, or opening a VT and installing lightdm, rebooting afterwards. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Fri Jun 8 11:41:23 2018 InstallationDate: Installed on 2018-06-07 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 Package: mutter PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-70-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.gdm3.custom.conf: 2019-11-29T12:32:53.022462 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 DistroRelease: Ubuntu 18.04 Package: mutter PackageArchitecture: amd64 ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-70-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.gdm3.custom.conf: 2019-11-29T13:14:23.686888 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1775881/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1775881] Re: [radeon] Wayland sessions including the login screen are just static noise
apport information ** Description changed: Ubuntu Version 18.04 LTS gdm3: Installed: 3.28.0-0ubuntu1 500 Package name: /etc/gdm3 Whenever I boot Ubuntu following installation from the official install ISO, the boot screen appears, but the login manager appears as static, scrambled graphics, making me unable to login without opening the VT and installing lightdm and switching to that login manager. Expected Results: Login manager appears with login field, background, and menu while I am able to find, click, and enter information into the login text fields. Actual Results: Scrambled noise appeared on my screen and I am unable to leave without force-shutting down my Gateway PC, or opening a VT and installing lightdm, rebooting afterwards. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Fri Jun 8 11:41:23 2018 InstallationDate: Installed on 2018-06-07 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 Package: mutter PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-70-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.gdm3.custom.conf: 2019-11-29T12:32:53.022462 + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.9 + Architecture: amd64 + DistroRelease: Ubuntu 18.04 + Package: mutter + PackageArchitecture: amd64 + ProcEnviron: + TERM=linux + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18 + Tags: bionic + Uname: Linux 4.15.0-70-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + mtime.conffile..etc.gdm3.custom.conf: 2019-11-29T13:14:23.686888 ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1775881/+attachment/5308796/+files/Dependencies.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1775881 Title: [radeon] Wayland sessions including the login screen are just static noise Status in gdm3 package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: Ubuntu Version 18.04 LTS gdm3: Installed: 3.28.0-0ubuntu1 500 Package name: /etc/gdm3 Whenever I boot Ubuntu following installation from the official install ISO, the boot screen appears, but the login manager appears as static, scrambled graphics, making me unable to login without opening the VT and installing lightdm and switching to that login manager. Expected Results: Login manager appears with login field, background, and menu while I am able to find, click, and enter information into the login text fields. Actual Results: Scrambled noise appeared on my screen and I am unable to leave without force-shutting down my Gateway PC, or opening a VT and installing lightdm, rebooting afterwards. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Fri Jun 8 11:41:23 2018 InstallationDate: Installed on 2018-06-07 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 Package: mutter PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-70-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install)
[Desktop-packages] [Bug 1775881] Re: [radeon] Wayland sessions including the login screen are just static noise
** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1775881/+attachment/5308789/+files/Lsusb.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1775881 Title: [radeon] Wayland sessions including the login screen are just static noise Status in gdm3 package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: Ubuntu Version 18.04 LTS gdm3: Installed: 3.28.0-0ubuntu1 500 Package name: /etc/gdm3 Whenever I boot Ubuntu following installation from the official install ISO, the boot screen appears, but the login manager appears as static, scrambled graphics, making me unable to login without opening the VT and installing lightdm and switching to that login manager. Expected Results: Login manager appears with login field, background, and menu while I am able to find, click, and enter information into the login text fields. Actual Results: Scrambled noise appeared on my screen and I am unable to leave without force-shutting down my Gateway PC, or opening a VT and installing lightdm, rebooting afterwards. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Fri Jun 8 11:41:23 2018 InstallationDate: Installed on 2018-06-07 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 Package: mutter PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-70-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.gdm3.custom.conf: 2019-11-29T12:32:53.022462 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 DistroRelease: Ubuntu 18.04 Package: mutter PackageArchitecture: amd64 ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-70-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.gdm3.custom.conf: 2019-11-29T13:14:23.686888 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1775881/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1775881] Re: [radeon] Wayland sessions including the login screen are just static noise
** Attachment added: "Lspci.txt" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1775881/+attachment/5308788/+files/Lspci.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1775881 Title: [radeon] Wayland sessions including the login screen are just static noise Status in gdm3 package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: Ubuntu Version 18.04 LTS gdm3: Installed: 3.28.0-0ubuntu1 500 Package name: /etc/gdm3 Whenever I boot Ubuntu following installation from the official install ISO, the boot screen appears, but the login manager appears as static, scrambled graphics, making me unable to login without opening the VT and installing lightdm and switching to that login manager. Expected Results: Login manager appears with login field, background, and menu while I am able to find, click, and enter information into the login text fields. Actual Results: Scrambled noise appeared on my screen and I am unable to leave without force-shutting down my Gateway PC, or opening a VT and installing lightdm, rebooting afterwards. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Fri Jun 8 11:41:23 2018 InstallationDate: Installed on 2018-06-07 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 Package: mutter PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-70-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.gdm3.custom.conf: 2019-11-29T12:32:53.022462 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 DistroRelease: Ubuntu 18.04 Package: mutter PackageArchitecture: amd64 ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-70-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.gdm3.custom.conf: 2019-11-29T13:14:23.686888 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1775881/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1775881] Re: [radeon] Wayland sessions including the login screen are just static noise
** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1775881/+attachment/5308793/+files/UdevDb.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1775881 Title: [radeon] Wayland sessions including the login screen are just static noise Status in gdm3 package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: Ubuntu Version 18.04 LTS gdm3: Installed: 3.28.0-0ubuntu1 500 Package name: /etc/gdm3 Whenever I boot Ubuntu following installation from the official install ISO, the boot screen appears, but the login manager appears as static, scrambled graphics, making me unable to login without opening the VT and installing lightdm and switching to that login manager. Expected Results: Login manager appears with login field, background, and menu while I am able to find, click, and enter information into the login text fields. Actual Results: Scrambled noise appeared on my screen and I am unable to leave without force-shutting down my Gateway PC, or opening a VT and installing lightdm, rebooting afterwards. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Fri Jun 8 11:41:23 2018 InstallationDate: Installed on 2018-06-07 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 Package: mutter PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-70-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.gdm3.custom.conf: 2019-11-29T12:32:53.022462 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 DistroRelease: Ubuntu 18.04 Package: mutter PackageArchitecture: amd64 ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-70-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.gdm3.custom.conf: 2019-11-29T13:14:23.686888 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1775881/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1775881] Re: [radeon] Wayland sessions including the login screen are just static noise
** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1775881/+attachment/5308790/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1775881 Title: [radeon] Wayland sessions including the login screen are just static noise Status in gdm3 package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: Ubuntu Version 18.04 LTS gdm3: Installed: 3.28.0-0ubuntu1 500 Package name: /etc/gdm3 Whenever I boot Ubuntu following installation from the official install ISO, the boot screen appears, but the login manager appears as static, scrambled graphics, making me unable to login without opening the VT and installing lightdm and switching to that login manager. Expected Results: Login manager appears with login field, background, and menu while I am able to find, click, and enter information into the login text fields. Actual Results: Scrambled noise appeared on my screen and I am unable to leave without force-shutting down my Gateway PC, or opening a VT and installing lightdm, rebooting afterwards. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Fri Jun 8 11:41:23 2018 InstallationDate: Installed on 2018-06-07 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 Package: mutter PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-70-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.gdm3.custom.conf: 2019-11-29T12:32:53.022462 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 DistroRelease: Ubuntu 18.04 Package: mutter PackageArchitecture: amd64 ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-70-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.gdm3.custom.conf: 2019-11-29T13:14:23.686888 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1775881/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1775881] Re: [radeon] Wayland sessions including the login screen are just static noise
** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1775881/+attachment/5308786/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1775881 Title: [radeon] Wayland sessions including the login screen are just static noise Status in gdm3 package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: Ubuntu Version 18.04 LTS gdm3: Installed: 3.28.0-0ubuntu1 500 Package name: /etc/gdm3 Whenever I boot Ubuntu following installation from the official install ISO, the boot screen appears, but the login manager appears as static, scrambled graphics, making me unable to login without opening the VT and installing lightdm and switching to that login manager. Expected Results: Login manager appears with login field, background, and menu while I am able to find, click, and enter information into the login text fields. Actual Results: Scrambled noise appeared on my screen and I am unable to leave without force-shutting down my Gateway PC, or opening a VT and installing lightdm, rebooting afterwards. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Fri Jun 8 11:41:23 2018 InstallationDate: Installed on 2018-06-07 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 Package: mutter PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-70-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.gdm3.custom.conf: 2019-11-29T12:32:53.022462 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 DistroRelease: Ubuntu 18.04 Package: mutter PackageArchitecture: amd64 ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-70-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.gdm3.custom.conf: 2019-11-29T13:14:23.686888 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1775881/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1775881] Re: [radeon] Wayland sessions including the login screen are just static noise
** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1775881/+attachment/5308791/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1775881 Title: [radeon] Wayland sessions including the login screen are just static noise Status in gdm3 package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: Ubuntu Version 18.04 LTS gdm3: Installed: 3.28.0-0ubuntu1 500 Package name: /etc/gdm3 Whenever I boot Ubuntu following installation from the official install ISO, the boot screen appears, but the login manager appears as static, scrambled graphics, making me unable to login without opening the VT and installing lightdm and switching to that login manager. Expected Results: Login manager appears with login field, background, and menu while I am able to find, click, and enter information into the login text fields. Actual Results: Scrambled noise appeared on my screen and I am unable to leave without force-shutting down my Gateway PC, or opening a VT and installing lightdm, rebooting afterwards. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Fri Jun 8 11:41:23 2018 InstallationDate: Installed on 2018-06-07 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 Package: mutter PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-70-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.gdm3.custom.conf: 2019-11-29T12:32:53.022462 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 DistroRelease: Ubuntu 18.04 Package: mutter PackageArchitecture: amd64 ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-70-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.gdm3.custom.conf: 2019-11-29T13:14:23.686888 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1775881/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1775881] Re: [radeon] Wayland sessions including the login screen are just static noise
** Attachment added: "xdpyinfo.txt" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1775881/+attachment/5308794/+files/xdpyinfo.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1775881 Title: [radeon] Wayland sessions including the login screen are just static noise Status in gdm3 package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: Ubuntu Version 18.04 LTS gdm3: Installed: 3.28.0-0ubuntu1 500 Package name: /etc/gdm3 Whenever I boot Ubuntu following installation from the official install ISO, the boot screen appears, but the login manager appears as static, scrambled graphics, making me unable to login without opening the VT and installing lightdm and switching to that login manager. Expected Results: Login manager appears with login field, background, and menu while I am able to find, click, and enter information into the login text fields. Actual Results: Scrambled noise appeared on my screen and I am unable to leave without force-shutting down my Gateway PC, or opening a VT and installing lightdm, rebooting afterwards. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Fri Jun 8 11:41:23 2018 InstallationDate: Installed on 2018-06-07 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 Package: mutter PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-70-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.gdm3.custom.conf: 2019-11-29T12:32:53.022462 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 DistroRelease: Ubuntu 18.04 Package: mutter PackageArchitecture: amd64 ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-70-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.gdm3.custom.conf: 2019-11-29T13:14:23.686888 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1775881/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1775881] Re: [radeon] Wayland sessions including the login screen are just static noise
** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1775881/+attachment/5308792/+files/ProcModules.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1775881 Title: [radeon] Wayland sessions including the login screen are just static noise Status in gdm3 package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: Ubuntu Version 18.04 LTS gdm3: Installed: 3.28.0-0ubuntu1 500 Package name: /etc/gdm3 Whenever I boot Ubuntu following installation from the official install ISO, the boot screen appears, but the login manager appears as static, scrambled graphics, making me unable to login without opening the VT and installing lightdm and switching to that login manager. Expected Results: Login manager appears with login field, background, and menu while I am able to find, click, and enter information into the login text fields. Actual Results: Scrambled noise appeared on my screen and I am unable to leave without force-shutting down my Gateway PC, or opening a VT and installing lightdm, rebooting afterwards. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Fri Jun 8 11:41:23 2018 InstallationDate: Installed on 2018-06-07 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 Package: mutter PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-70-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.gdm3.custom.conf: 2019-11-29T12:32:53.022462 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 DistroRelease: Ubuntu 18.04 Package: mutter PackageArchitecture: amd64 ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-70-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.gdm3.custom.conf: 2019-11-29T13:14:23.686888 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1775881/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1775881] Re: [radeon] Wayland sessions including the login screen are just static noise
** Attachment added: "Xrandr.txt" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1775881/+attachment/5308795/+files/Xrandr.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1775881 Title: [radeon] Wayland sessions including the login screen are just static noise Status in gdm3 package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: Ubuntu Version 18.04 LTS gdm3: Installed: 3.28.0-0ubuntu1 500 Package name: /etc/gdm3 Whenever I boot Ubuntu following installation from the official install ISO, the boot screen appears, but the login manager appears as static, scrambled graphics, making me unable to login without opening the VT and installing lightdm and switching to that login manager. Expected Results: Login manager appears with login field, background, and menu while I am able to find, click, and enter information into the login text fields. Actual Results: Scrambled noise appeared on my screen and I am unable to leave without force-shutting down my Gateway PC, or opening a VT and installing lightdm, rebooting afterwards. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Fri Jun 8 11:41:23 2018 InstallationDate: Installed on 2018-06-07 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 Package: mutter PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-70-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.gdm3.custom.conf: 2019-11-29T12:32:53.022462 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 DistroRelease: Ubuntu 18.04 Package: mutter PackageArchitecture: amd64 ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-70-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.gdm3.custom.conf: 2019-11-29T13:14:23.686888 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1775881/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1775881] Re: [radeon] Wayland sessions including the login screen are just static noise
** Attachment added: "DpkgLog.txt" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1775881/+attachment/5308787/+files/DpkgLog.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1775881 Title: [radeon] Wayland sessions including the login screen are just static noise Status in gdm3 package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: Ubuntu Version 18.04 LTS gdm3: Installed: 3.28.0-0ubuntu1 500 Package name: /etc/gdm3 Whenever I boot Ubuntu following installation from the official install ISO, the boot screen appears, but the login manager appears as static, scrambled graphics, making me unable to login without opening the VT and installing lightdm and switching to that login manager. Expected Results: Login manager appears with login field, background, and menu while I am able to find, click, and enter information into the login text fields. Actual Results: Scrambled noise appeared on my screen and I am unable to leave without force-shutting down my Gateway PC, or opening a VT and installing lightdm, rebooting afterwards. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Fri Jun 8 11:41:23 2018 InstallationDate: Installed on 2018-06-07 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 Package: mutter PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-70-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.gdm3.custom.conf: 2019-11-29T12:32:53.022462 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 DistroRelease: Ubuntu 18.04 Package: mutter PackageArchitecture: amd64 ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-70-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.gdm3.custom.conf: 2019-11-29T13:14:23.686888 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1775881/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1775881] Re: [radeon] Wayland sessions including the login screen are just static noise
I am still seeing this problem as of Ubuntu 18.04.3 LTS. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1775881 Title: [radeon] Wayland sessions including the login screen are just static noise Status in gdm3 package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: Ubuntu Version 18.04 LTS gdm3: Installed: 3.28.0-0ubuntu1 500 Package name: /etc/gdm3 Whenever I boot Ubuntu following installation from the official install ISO, the boot screen appears, but the login manager appears as static, scrambled graphics, making me unable to login without opening the VT and installing lightdm and switching to that login manager. Expected Results: Login manager appears with login field, background, and menu while I am able to find, click, and enter information into the login text fields. Actual Results: Scrambled noise appeared on my screen and I am unable to leave without force-shutting down my Gateway PC, or opening a VT and installing lightdm, rebooting afterwards. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Fri Jun 8 11:41:23 2018 InstallationDate: Installed on 2018-06-07 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 Package: mutter PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-70-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.gdm3.custom.conf: 2019-11-29T12:32:53.022462 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1775881/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1854532] [NEW] Gnome Display Manager 3 fails to run Xorg the first reboot after I set WaylandEnabled to false in gdm3's custom.conf file
Public bug reported: Whenever I set Wayland to false in Gnome Display Manager's custom.conf file and then reboot, I still see the same scrambled graphics on the machine as if it were using Wayland. Rebooting the machine a SECOND time resolves the issue. However, I should not have to reboot twice for the new setting to take effect. Steps to Reproduce: 1. When the machine boots up with scrambled graphics, press Control+Alt+F3 2. Log into the machine using the tty session and run "sudo editor /etc/gdm3/custom.conf 3. Set Wayland to false and reboot 4. Notice after reboot the same scrambled graphics appear until the user reboots again Expected Results: Gnome Display Manager runs xorg and xorg shows the correct graphics for the machine. Actual Results: Graphics are scrambled and settings do not appear to take effect until next reboot. This issue occurred right before 12:45 PM, EDT, on November 29, 2019. Description: Ubuntu 18.04.3 LTS Release: 18.04 xorg: Installed: 1:7.7+19ubuntu7.1 Candidate: 1:7.7+19ubuntu7.1 Version table: *** 1:7.7+19ubuntu7.1 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:7.7+19ubuntu7 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages gdm3: Installed: 3.28.3-0ubuntu18.04.4 Candidate: 3.28.3-0ubuntu18.04.4 Version table: *** 3.28.3-0ubuntu18.04.4 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 3.28.0-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.3-0ubuntu18.04.4 ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18 Uname: Linux 4.15.0-70-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Nov 29 12:54:00 2019 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.custom.conf: 2019-11-29T12:32:53.022462 ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1854532 Title: Gnome Display Manager 3 fails to run Xorg the first reboot after I set WaylandEnabled to false in gdm3's custom.conf file Status in gdm3 package in Ubuntu: New Bug description: Whenever I set Wayland to false in Gnome Display Manager's custom.conf file and then reboot, I still see the same scrambled graphics on the machine as if it were using Wayland. Rebooting the machine a SECOND time resolves the issue. However, I should not have to reboot twice for the new setting to take effect. Steps to Reproduce: 1. When the machine boots up with scrambled graphics, press Control+Alt+F3 2. Log into the machine using the tty session and run "sudo editor /etc/gdm3/custom.conf 3. Set Wayland to false and reboot 4. Notice after reboot the same scrambled graphics appear until the user reboots again Expected Results: Gnome Display Manager runs xorg and xorg shows the correct graphics for the machine. Actual Results: Graphics are scrambled and settings do not appear to take effect until next reboot. This issue occurred right before 12:45 PM, EDT, on November 29, 2019. Description: Ubuntu 18.04.3 LTS Release: 18.04 xorg: Installed: 1:7.7+19ubuntu7.1 Candidate: 1:7.7+19ubuntu7.1 Version table: *** 1:7.7+19ubuntu7.1 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:7.7+19ubuntu7 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages gdm3: Installed: 3.28.3-0ubuntu18.04.4 Candidate: 3.28.3-0ubuntu18.04.4 Version table: *** 3.28.3-0ubuntu18.04.4 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 3.28.0-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.3-0ubuntu18.04.4 ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18 Uname: Linux 4.15.0-70-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Nov 29 12:54:00 2019 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: No upgrade
[Desktop-packages] [Bug 1854533] [NEW] Gnome Display Manager 3 fails to run Xorg the first reboot after I set WaylandEnabled to false in gdm3's custom.conf file
Public bug reported: Whenever I set Wayland to false in Gnome Display Manager's custom.conf file and then reboot, I still see the same scrambled graphics on the machine as if it were using Wayland. Rebooting the machine a SECOND time resolves the issue. However, I should not have to reboot twice for the new setting to take effect. Steps to Reproduce: 1. When the machine boots up with scrambled graphics, press Control+Alt+F3 2. Log into the machine using the tty session and run "sudo editor /etc/gdm3/custom.conf 3. Set Wayland to false and reboot 4. Notice after reboot the same scrambled graphics appear until the user reboots again Expected Results: Gnome Display Manager runs xorg and xorg shows the correct graphics for the machine. Actual Results: Graphics are scrambled and settings do not appear to take effect until next reboot. This issue occurred right before 12:45 PM, EDT, on November 29, 2019. Description: Ubuntu 18.04.3 LTS Release: 18.04 mutter: Installed: 3.28.4-0ubuntu18.04.2 Candidate: 3.28.4-0ubuntu18.04.2 Version table: *** 3.28.4-0ubuntu18.04.2 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.28.1-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages xorg: Installed: 1:7.7+19ubuntu7.1 Candidate: 1:7.7+19ubuntu7.1 Version table: *** 1:7.7+19ubuntu7.1 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:7.7+19ubuntu7 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages gdm3: Installed: 3.28.3-0ubuntu18.04.4 Candidate: 3.28.3-0ubuntu18.04.4 Version table: *** 3.28.3-0ubuntu18.04.4 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 3.28.0-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: mutter 3.28.4-0ubuntu18.04.2 ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18 Uname: Linux 4.15.0-70-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Nov 29 12:59:16 2019 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1854533 Title: Gnome Display Manager 3 fails to run Xorg the first reboot after I set WaylandEnabled to false in gdm3's custom.conf file Status in mutter package in Ubuntu: New Bug description: Whenever I set Wayland to false in Gnome Display Manager's custom.conf file and then reboot, I still see the same scrambled graphics on the machine as if it were using Wayland. Rebooting the machine a SECOND time resolves the issue. However, I should not have to reboot twice for the new setting to take effect. Steps to Reproduce: 1. When the machine boots up with scrambled graphics, press Control+Alt+F3 2. Log into the machine using the tty session and run "sudo editor /etc/gdm3/custom.conf 3. Set Wayland to false and reboot 4. Notice after reboot the same scrambled graphics appear until the user reboots again Expected Results: Gnome Display Manager runs xorg and xorg shows the correct graphics for the machine. Actual Results: Graphics are scrambled and settings do not appear to take effect until next reboot. This issue occurred right before 12:45 PM, EDT, on November 29, 2019. Description: Ubuntu 18.04.3 LTS Release: 18.04 mutter: Installed: 3.28.4-0ubuntu18.04.2 Candidate: 3.28.4-0ubuntu18.04.2 Version table: *** 3.28.4-0ubuntu18.04.2 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.28.1-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages xorg: Installed: 1:7.7+19ubuntu7.1 Candidate: 1:7.7+19ubuntu7.1 Version table: *** 1:7.7+19ubuntu7.1 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:7.7+19ubuntu7 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages gdm3: Installed: 3.28.3-0ubuntu18.04.4 Candidate: 3.28.3-0ubuntu18.04.4 Version table: *** 3.28.3-0ubuntu18.04.4 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu
[Desktop-packages] [Bug 1775881] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1775881/+attachment/5308779/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1775881 Title: [radeon] Wayland sessions including the login screen are just static noise Status in gdm3 package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: Ubuntu Version 18.04 LTS gdm3: Installed: 3.28.0-0ubuntu1 500 Package name: /etc/gdm3 Whenever I boot Ubuntu following installation from the official install ISO, the boot screen appears, but the login manager appears as static, scrambled graphics, making me unable to login without opening the VT and installing lightdm and switching to that login manager. Expected Results: Login manager appears with login field, background, and menu while I am able to find, click, and enter information into the login text fields. Actual Results: Scrambled noise appeared on my screen and I am unable to leave without force-shutting down my Gateway PC, or opening a VT and installing lightdm, rebooting afterwards. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Fri Jun 8 11:41:23 2018 InstallationDate: Installed on 2018-06-07 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 Package: mutter PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-70-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.gdm3.custom.conf: 2019-11-29T12:32:53.022462 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1775881/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1775881] modified.conffile..etc.gdm3.custom.conf.txt
apport information ** Attachment added: "modified.conffile..etc.gdm3.custom.conf.txt" https://bugs.launchpad.net/bugs/1775881/+attachment/5308780/+files/modified.conffile..etc.gdm3.custom.conf.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1775881 Title: [radeon] Wayland sessions including the login screen are just static noise Status in gdm3 package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: Ubuntu Version 18.04 LTS gdm3: Installed: 3.28.0-0ubuntu1 500 Package name: /etc/gdm3 Whenever I boot Ubuntu following installation from the official install ISO, the boot screen appears, but the login manager appears as static, scrambled graphics, making me unable to login without opening the VT and installing lightdm and switching to that login manager. Expected Results: Login manager appears with login field, background, and menu while I am able to find, click, and enter information into the login text fields. Actual Results: Scrambled noise appeared on my screen and I am unable to leave without force-shutting down my Gateway PC, or opening a VT and installing lightdm, rebooting afterwards. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Fri Jun 8 11:41:23 2018 InstallationDate: Installed on 2018-06-07 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 Package: mutter PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-70-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.gdm3.custom.conf: 2019-11-29T12:32:53.022462 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1775881/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1775881] Re: [radeon] Wayland sessions including the login screen are just static noise
apport information ** Tags added: apport-collected ** Description changed: Ubuntu Version 18.04 LTS gdm3: Installed: 3.28.0-0ubuntu1 500 Package name: /etc/gdm3 Whenever I boot Ubuntu following installation from the official install ISO, the boot screen appears, but the login manager appears as static, scrambled graphics, making me unable to login without opening the VT and installing lightdm and switching to that login manager. Expected Results: Login manager appears with login field, background, and menu while I am able to find, click, and enter information into the login text fields. Actual Results: Scrambled noise appeared on my screen and I am unable to leave without force-shutting down my Gateway PC, or opening a VT and installing lightdm, rebooting afterwards. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Fri Jun 8 11:41:23 2018 InstallationDate: Installed on 2018-06-07 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.9 + Architecture: amd64 + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 18.04 + Package: mutter + PackageArchitecture: amd64 + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18 + Tags: bionic + Uname: Linux 4.15.0-70-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + mtime.conffile..etc.gdm3.custom.conf: 2019-11-29T12:32:53.022462 ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1775881/+attachment/5308778/+files/Dependencies.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1775881 Title: [radeon] Wayland sessions including the login screen are just static noise Status in gdm3 package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: Ubuntu Version 18.04 LTS gdm3: Installed: 3.28.0-0ubuntu1 500 Package name: /etc/gdm3 Whenever I boot Ubuntu following installation from the official install ISO, the boot screen appears, but the login manager appears as static, scrambled graphics, making me unable to login without opening the VT and installing lightdm and switching to that login manager. Expected Results: Login manager appears with login field, background, and menu while I am able to find, click, and enter information into the login text fields. Actual Results: Scrambled noise appeared on my screen and I am unable to leave without force-shutting down my Gateway PC, or opening a VT and installing lightdm, rebooting afterwards. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Fri Jun 8 11:41:23 2018 InstallationDate: Installed on 2018-06-07 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 Package: mutter PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-70-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.gdm3.custom.conf: 2019-11-29T12:32:53.022462 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1775881/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1854531] [NEW] Ubuntu fails to run Xorg the first reboot after I set WaylandEnabled to false in gdm3's custom.conf
Public bug reported: Whenever I set Wayland to false in Gnome Display Manager's custom.conf file and then reboot, I still see the same scrambled graphics on the machine as if it were using Wayland. Rebooting the machine a SECOND time resolves the issue. However, I should not have to reboot twice for the new setting to take effect. Steps to Reproduce: 1. When the machine boots up with scrambled graphics, press Control+Alt+F3 2. Log into the machine using the tty session and run "sudo editor /etc/gdm3/custom.conf 3. Set Wayland to false and reboot 4. Notice after reboot the same scrambled graphics appear until the user reboots again Expected Results: Gnome Display Manager runs xorg and xorg shows the correct graphics for the machine. Actual Results: Graphics are scrambled and settings do not appear to take effect until next reboot. This issue occurred right before 12:45 PM, EDT, on November 29, 2019. Description:Ubuntu 18.04.3 LTS Release:18.04 xorg: Installed: 1:7.7+19ubuntu7.1 Candidate: 1:7.7+19ubuntu7.1 Version table: *** 1:7.7+19ubuntu7.1 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:7.7+19ubuntu7 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages gdm3: Installed: 3.28.3-0ubuntu18.04.4 Candidate: 3.28.3-0ubuntu18.04.4 Version table: *** 3.28.3-0ubuntu18.04.4 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 3.28.0-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18 Uname: Linux 4.15.0-70-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Nov 29 12:39:33 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM] [1002:6779] (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM] [1682:3207] MachineType: Gateway DX4860 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-70-generic root=UUID=751019b9-8693-494c-ad69-17ddf9e51235 ro splash quiet vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/01/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P02-A1 dmi.board.name: IPISB-VR dmi.board.vendor: Gateway dmi.board.version: 1.01 dmi.chassis.type: 3 dmi.chassis.vendor: Gateway dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP02-A1:bd08/01/2011:svnGateway:pnDX4860:pvr:rvnGateway:rnIPISB-VR:rvr1.01:cvnGateway:ct3:cvr: dmi.product.family: Gateway Desktop dmi.product.name: DX4860 dmi.sys.vendor: Gateway version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 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 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1854531 Title: Ubuntu fails to run Xorg the first reboot after I set WaylandEnabled to false in gdm3's custom.conf Status in xorg package in Ubuntu: New Bug description: Whenever I set Wayland to false in Gnome Display Manager's custom.conf file and then reboot, I still see the same scrambled graphics on the machine as if it were using Wayland. Rebooting the machine a SECOND time resolves the issue. However, I should not have to reboot twice for the new setting to take effect. Steps to Reproduce: 1. When the machine boots up with scrambled graphics, press Control+Alt+F3 2. Log into the machine using the tty session and run "sudo editor /etc/gdm3/custom.conf 3. Set Wayland to false and reboot 4. Notice after reboot the same scrambled graphics appear until the user reboots again Expected Results: Gnome Display Manager runs xorg and xorg shows the correct graphics for the machine.
[Desktop-packages] [Bug 1804280] Re: intermittent periods of packet loss and high latency
The problem continues with 4.15.0-65-generic. This is a ping summary coming into the affected system from another host on the same network segment with no connectivity problems, reflecting a four-minute period of recurrence (ping times were <1ms for the last 20 seconds or so, but while the problem was occurring, there was ~50% packet loss and >200ms response times for the packets that did get through): --- [host] ping statistics --- 258 packets transmitted, 146 received, 43.4109% packet loss, time 259396ms rtt min/avg/max/mdev = 0.109/377.848/641.641/190.332 ms Note that network-manager has been purged from this system, so this is not a network-manager issue. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1804280 Title: intermittent periods of packet loss and high latency Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: Intermittently and unpredictably, ping response times and packet loss will spike to unusable levels. Normal ping times are about .25 ms for other hosts on the local network, with essentially no packet loss. During the problematic periods (usually lasting 2-10 minutes), packet loss jumps to about 50% and ping response times on the packets that aren't dropped jump to between 250 and 750 ms. This behavior started when I upgraded from Kubuntu 16.04 to Kubuntu 18.04. Changing which host on the network I test this with has no effect (and during this, those other hosts are able to use the network without any problem). Replacing the cable changes nothing. Using a different Ethernet interface changes nothing. Replacing the switch changes nothing. This is almost certainly not a hardware problem. There is a chance that using wireless instead of Ethernet would fix the issue, but I have been avoiding that since the wired connection is much faster when Kubuntu is not malfunctioning. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1.1 ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18 Uname: Linux 4.15.0-39-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: KDE Date: Tue Nov 20 12:48:05 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-12-09 (711 days ago) InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IpRoute: default via [removed] dev enp0s31f6 proto dhcp metric 100 169.254.0.0/16 dev enp0s31f6 scope link metric 1000 [removed]/24 dev enp0s31f6 proto kernel scope link src [removed] metric 100 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to bionic on 2018-08-19 (92 days ago) nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH enp0s31f6 ethernet connected /org/freedesktop/NetworkManager/Devices/2 Wired connection 1 2e0d0ce3-8ee2-3c06-815d-eb9a42873b3b /org/freedesktop/NetworkManager/ActiveConnection/5 [removed] btdisconnected /org/freedesktop/NetworkManager/Devices/5 -- ---- wlp3s0 wifi disconnected /org/freedesktop/NetworkManager/Devices/4 -- -- -- lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected started full enabled enabled enabled enabled enabled --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dan2053 F pulseaudio /dev/snd/pcmC1D0c: dan2053 F...m pulseaudio /dev/snd/controlC1: dan2053 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=4eadd7fe-e046-471d-b0ee-f1c85365411e IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-12-09 (712 days ago) InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IpRoute: default via 192.168.4.1 dev enp0s31f6 proto dhcp metric 100 169.254.0.0/16 dev enp0s31f6 scope link metric 1000 192.168.4.0/24 dev enp0s31f6 proto kernel scope link src 192.168.4.42 metric 100 MachineType: Dell Inc. Precision Tower 3420
[Desktop-packages] [Bug 1809685] Re: The evince application often freezes
I also see this happen quite often. The User Manual link posted here will trigger it when you open the link with Document Viewer. https://www.star-cooperation.com/de/kompetenzen/elektronik/produkte/vernetzungstechnik/hardware/vernetzungszubehoer/flexmedia-100base-t1/ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1809685 Title: The evince application often freezes Status in evince package in Ubuntu: Expired Bug description: Hi! The evince application (pdf document viewer) often freezes. Thanks. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: evince 3.28.4-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Dec 25 07:12:13 2018 InstallationDate: Installed on 2018-05-06 (232 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1809685/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1838154] Re: Something hinders XFCE performance. >:]
Speed difference is incredible. If you find what is causing this, let me know! ;-) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1838154 Title: Something hinders XFCE performance. >:] Status in wayland: New Status in Xfce4 Desktop: New Status in Xfwm4: New Status in X.Org X server: New Status in xorg package in Ubuntu: New Status in xfwm4 package in Fedora: Unknown Bug description: The following settings get rid of some kind of flickering or slow-down during typing and so on. 1. Snapping settings: 1 (top) 1 (bottom) 0 (left) 2 (right) 2. Send message trick lowers temperature. :-) 3. Avoid alt-tabbing. >:] 4. Rename Templates to "# Templates". __ Additional info: two spaces bug - https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1839716 https://bugzilla.redhat.com/show_bug.cgi?id=1754300#c2 Templates bug - https://bugs.launchpad.net/ubuntu/+source/xdg-user-dirs/+bug/1836462 https://bugzilla.redhat.com/show_bug.cgi?id=1729666 :-) To manage notifications about this bug go to: https://bugs.launchpad.net/wayland/+bug/1838154/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1836462] Re: Renaming Templates to # Templates fixes speed issues present in wide range of desktop applications
Everything is close to default, I discovered this by accident rly. :-) XDG_TEMPLATES_DIR="$HOME/" -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-user-dirs in Ubuntu. https://bugs.launchpad.net/bugs/1836462 Title: Renaming Templates to # Templates fixes speed issues present in wide range of desktop applications Status in xdg-user-dirs package in Ubuntu: Incomplete Status in xdg-user-dirs package in Fedora: Unknown Bug description: Renaming "Templates" to "# Templates" fixes a lot of speed issues in a range of desktop applications, e.g. file managers, text editors, etc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-user-dirs/+bug/1836462/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1795021] Re: gsd-xsettings high memory usage
Same here. The memory usage grows and grows. Currently it's at 1,4 GB but yesterday I had about 3,4 GB. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1795021 Title: gsd-xsettings high memory usage Status in gnome-settings-daemon package in Ubuntu: Confirmed Bug description: gsd-xsettings is using ~700MB of memory. I think there could be some memory leak because I don't remember it ever happening before. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-settings-daemon 3.28.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: communitheme:ubuntu:GNOME Date: Fri Sep 28 18:42:46 2018 InstallationDate: Installed on 2017-08-21 (403 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170820) SourcePackage: gnome-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1795021/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1854472] Re: ubuntu-drivers-common fails when no PATH environment variable is passed
This bug was fixed in the package ubuntu-drivers-common - 1:0.7.6.1 --- ubuntu-drivers-common (1:0.7.6.1) focal; urgency=medium * Make sure that the PATH environment variable is set (LP: #1854472). -- Alberto Milone Fri, 29 Nov 2019 11:06:12 +0100 ** Changed in: ubuntu-drivers-common (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1854472 Title: ubuntu-drivers-common fails when no PATH environment variable is passed Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Bionic: In Progress Status in ubuntu-drivers-common source package in Eoan: In Progress Bug description: ubuntu-drivers-common fails when no PATH environment variable is passed: https://errors.ubuntu.com/problem/52d04f39f8cbdb77d65ec57f19a5801284c1e2b0 While the reasons why the PATH variable is empty are unknown, the ubuntu-drivers tools should not fail, and we can assume that a minimal PATH (such as /sbin:/usr/sbin:/bin:/usr/bin) would apply to the system. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1854472/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1850651] Re: [SRU] Authentication constantly re-requested for Google
But I wrote that I downloaded the newest version and that is working. Just i need to open from extracted folder. I wrote for the Ubuntu replace this version in 20.04 because this builded version is wrong. So now I need to download and try an older version too? 2019. 11. 29. 12:52 keltezéssel, Timo Aaltonen írta:. > Hello Ads2, or anyone else affected, > > Accepted thunderbird into xenial-proposed. The package will build now > and be available at > https://launchpad.net/ubuntu/+source/thunderbird/1:60.9.1+build1-0ubuntu0.16.04.1 > 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 for helping! > > N.B. The updated package will be released to -updates after the bug(s) > fixed by this package have been verified and the package has been in > -proposed for a minimum of 7 days. > > ** Changed in: thunderbird (Ubuntu Xenial) > Status: In Progress => Fix Committed > > ** Tags added: verification-needed-xenial > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1850651 Title: [SRU] Authentication constantly re-requested for Google Status in Mozilla Thunderbird: Fix Released Status in thunderbird package in Ubuntu: Fix Released Status in thunderbird source package in Xenial: Fix Committed Status in thunderbird source package in Bionic: Fix Committed Status in thunderbird source package in Disco: Fix Committed Status in thunderbird source package in Eoan: Fix Committed Status in thunderbird source package in Focal: Fix Released Bug description: [Impact] A recent server-side change with google e-mail accounts (gmail) means that thunderbird consistently fails to authenticate, prompting for the user's e-mail address and password over and over, without ever succeeding. This has been fixed upstream and is tracked by https://bugzilla.mozilla.org/show_bug.cgi?id=1592407. [Test Case] In a clean environment, launch thunderbird and add an existing gmail account. Thunderbird should auto-detect all the relevant parameters, and then an external webview should pop up to prompt for your e-mail address (it's not auto-filled, that's a separate issue that's also known upstream) and your password. After filling this in and authorizing thunderbird to access your e-mails, your account should be set up and thunderbird should start fetching e-mails from your inbox. Instead it fails to authenticate and displays the authentication pop up again. [Regression Potential] Low, as this is an official upstream point release that addresses only this regression (see https://www.thunderbird.net/en-US/thunderbird/60.9.1/releasenotes/). The fix is minimal and self-contained (https://hg.mozilla.org/releases/comm-esr60/rev/56b6d1b50647143c25efe642b37b02f65f9c4343), if the bug is indeed confirmed to be fixed then it should be safe. [Original Bug Description] When I use Thunderbird, it keeps failing to connect with my Google (Gmail) accounts. It keeps asking for authentication via the web portal, I seem to successfully give Thunderbird authentication, but no messages come in and, soon afterwards, the web portal comes up asking for login again. I am using OAuth2 (so this ( https://support.mozilla.org/en- US/questions/1201406 ) doesn't help. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: thunderbird 1:60.9.0+build1-0ubuntu0.19.04.1 ProcVersionSignature: Ubuntu 5.0.0-32.34-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: adam 3444 F pulseaudio /dev/snd/pcmC0D0p: adam 3444 F...m pulseaudio BuildID: 20191007090404 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Wed Oct 30 14:56:50 2019 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant
[Desktop-packages] [Bug 1850651] Re: [SRU] Authentication constantly re-requested for Google
Hello Ads2, or anyone else affected, Accepted thunderbird into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/thunderbird/1:60.9.1+build1-0ubuntu0.16.04.1 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 for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: thunderbird (Ubuntu Xenial) Status: In Progress => Fix Committed ** Tags added: verification-needed-xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1850651 Title: [SRU] Authentication constantly re-requested for Google Status in Mozilla Thunderbird: Fix Released Status in thunderbird package in Ubuntu: Fix Released Status in thunderbird source package in Xenial: Fix Committed Status in thunderbird source package in Bionic: Fix Committed Status in thunderbird source package in Disco: Fix Committed Status in thunderbird source package in Eoan: Fix Committed Status in thunderbird source package in Focal: Fix Released Bug description: [Impact] A recent server-side change with google e-mail accounts (gmail) means that thunderbird consistently fails to authenticate, prompting for the user's e-mail address and password over and over, without ever succeeding. This has been fixed upstream and is tracked by https://bugzilla.mozilla.org/show_bug.cgi?id=1592407. [Test Case] In a clean environment, launch thunderbird and add an existing gmail account. Thunderbird should auto-detect all the relevant parameters, and then an external webview should pop up to prompt for your e-mail address (it's not auto-filled, that's a separate issue that's also known upstream) and your password. After filling this in and authorizing thunderbird to access your e-mails, your account should be set up and thunderbird should start fetching e-mails from your inbox. Instead it fails to authenticate and displays the authentication pop up again. [Regression Potential] Low, as this is an official upstream point release that addresses only this regression (see https://www.thunderbird.net/en-US/thunderbird/60.9.1/releasenotes/). The fix is minimal and self-contained (https://hg.mozilla.org/releases/comm-esr60/rev/56b6d1b50647143c25efe642b37b02f65f9c4343), if the bug is indeed confirmed to be fixed then it should be safe. [Original Bug Description] When I use Thunderbird, it keeps failing to connect with my Google (Gmail) accounts. It keeps asking for authentication via the web portal, I seem to successfully give Thunderbird authentication, but no messages come in and, soon afterwards, the web portal comes up asking for login again. I am using OAuth2 (so this ( https://support.mozilla.org/en- US/questions/1201406 ) doesn't help. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: thunderbird 1:60.9.0+build1-0ubuntu0.19.04.1 ProcVersionSignature: Ubuntu 5.0.0-32.34-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: adam 3444 F pulseaudio /dev/snd/pcmC0D0p: adam 3444 F...m pulseaudio BuildID: 20191007090404 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Wed Oct 30 14:56:50 2019 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2017-08-03 (817 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) IpRoute: default via 192.168.1.1 dev wlp3s0 proto dhcp metric 600 10.0.3.0/24 dev lxcbr0 proto kernel scope link src 10.0.3.1 linkdown 169.254.0.0/16 dev lxcbr0 scope link metric 1000
[Desktop-packages] [Bug 1850651] Re: [SRU] Authentication constantly re-requested for Google
Hello Ads2, or anyone else affected, Accepted thunderbird into disco-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/thunderbird/1:60.9.1+build1-0ubuntu0.19.04.1 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-disco to verification-done-disco. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-disco. 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 for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: thunderbird (Ubuntu Disco) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-disco -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1850651 Title: [SRU] Authentication constantly re-requested for Google Status in Mozilla Thunderbird: Fix Released Status in thunderbird package in Ubuntu: Fix Released Status in thunderbird source package in Xenial: Fix Committed Status in thunderbird source package in Bionic: Fix Committed Status in thunderbird source package in Disco: Fix Committed Status in thunderbird source package in Eoan: Fix Committed Status in thunderbird source package in Focal: Fix Released Bug description: [Impact] A recent server-side change with google e-mail accounts (gmail) means that thunderbird consistently fails to authenticate, prompting for the user's e-mail address and password over and over, without ever succeeding. This has been fixed upstream and is tracked by https://bugzilla.mozilla.org/show_bug.cgi?id=1592407. [Test Case] In a clean environment, launch thunderbird and add an existing gmail account. Thunderbird should auto-detect all the relevant parameters, and then an external webview should pop up to prompt for your e-mail address (it's not auto-filled, that's a separate issue that's also known upstream) and your password. After filling this in and authorizing thunderbird to access your e-mails, your account should be set up and thunderbird should start fetching e-mails from your inbox. Instead it fails to authenticate and displays the authentication pop up again. [Regression Potential] Low, as this is an official upstream point release that addresses only this regression (see https://www.thunderbird.net/en-US/thunderbird/60.9.1/releasenotes/). The fix is minimal and self-contained (https://hg.mozilla.org/releases/comm-esr60/rev/56b6d1b50647143c25efe642b37b02f65f9c4343), if the bug is indeed confirmed to be fixed then it should be safe. [Original Bug Description] When I use Thunderbird, it keeps failing to connect with my Google (Gmail) accounts. It keeps asking for authentication via the web portal, I seem to successfully give Thunderbird authentication, but no messages come in and, soon afterwards, the web portal comes up asking for login again. I am using OAuth2 (so this ( https://support.mozilla.org/en- US/questions/1201406 ) doesn't help. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: thunderbird 1:60.9.0+build1-0ubuntu0.19.04.1 ProcVersionSignature: Ubuntu 5.0.0-32.34-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: adam 3444 F pulseaudio /dev/snd/pcmC0D0p: adam 3444 F...m pulseaudio BuildID: 20191007090404 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Wed Oct 30 14:56:50 2019 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2017-08-03 (817 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) IpRoute: default via 192.168.1.1 dev wlp3s0 proto dhcp metric 600 10.0.3.0/24 dev lxcbr0 proto kernel scope link src 10.0.3.1 linkdown 169.254.0.0/16 dev lxcbr0 scope link
[Desktop-packages] [Bug 1854179] Re: Battery icon is red when the laptop has 30% battery left; it should only turn red when it hits 10%
The icon is not red with Adwaita/in a GNOME session, assuming it's yaru specific ** Package changed: gnome-shell (Ubuntu) => yaru-theme (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1854179 Title: Battery icon is red when the laptop has 30% battery left; it should only turn red when it hits 10% Status in yaru-theme package in Ubuntu: New Bug description: Whenever the laptop is running on battery power, and the battery remaining is less than 50%, the battery icon on the Gnome Status Bar turns red. This should only happen if there is critically low battery; the red icon is a misnomer Expected results: Battery icon remains white until the battery hits 10% or lower Actual Results: Battery icon is red whenever the battery life is less than 50% or 30%. Description: Ubuntu 19.10 Release: 19.10 Installed: 3.34.1+git20191024-1ubuntu1~19.10.1 Candidate: 3.34.1+git20191024-1ubuntu1~19.10.1 Version table: *** 3.34.1+git20191024-1ubuntu1~19.10.1 500 500 http://us.archive.ubuntu.com/ubuntu eoan-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.34.1-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Nov 27 11:14:09 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-11-20 (6 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.apport.crashdb.conf: 2019-11-24T17:17:29.098099 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1854179/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1854485] [NEW] Introduce the new NVIDIA 440 series, and add 5.4 Linux compatibility to the 340 and 390 series
Public bug reported: [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] 440.36: * New upstream release: - Added support for the following GPUs: o GeForce GTX 1650 SUPER o GeForce GTX 1660 SUPER - Fixed graphical corruption that can occur when using glslang SPIR-V Generator Version <= 2. - Fixed a bug that could cause the X server to crash when running applications using GLX indirect rendering. - Updated the Module.symvers sanity check, which is part of the NVIDIA kernel module build process, to accommodate the recent addition of a new field in the Module.symvers file format. This fixes the error "The Module.symvers file is missing [...]" seen during driver installation or DKMS rebuilds with Linux 5.4 RC kernels. - Fixed kernel module build problems with Linux kernel 5.4.0 release candidates. - Updated nvidia-bug-report.sh to collect information about X server crashes from coredumpctl, when available. - Updated the nvidia-drm kernel module for compatibility with the removal of the DRIVER_PRIME flag in recent Linux kernel versions. - Enabled parallel GLSL shader linking by default; i.e., allow GL_ARB_parallel_shader_compile to work without first calling glMaxShaderCompilerThreadsARB(). - Added support for HDMI 2.1 variable refresh rate (VRR) G-SYNC Compatible monitors on supported GPUs.For more details, see "Configuring Multiple Display Devices on One X Screen" in the README. Added support for the GLX_NV_multigpu_context and GL_NV_gpu_multicast extensions.For more details, see the "Configuring SLI and Multi-GPU FrameRendering" chapter of the README, and the extension specifications: https://www.khronos.org/registry/OpenGL/extensions/NV/GLX_NV_multigpu_context.txt https://www.khronos.org/registry/OpenGL/extensions/NV/NV_gpu_multicast.txt - Fixed a bug that prevented Vulkan applications running on systems configured for SLI. Vulkan applications can now run while SLI is enabled; however, they will only be able to use a single GPU. - Simplified the nvidia-sleep.sh sample script to no longer depend on unreliable detection of the current VT through X server logs. - Added EGL support for PRIME render offload. Please see the PRIME Render Offload chapter in the README for configuration details. - Fixed a regression introduced in 435.19.02 that would cause some applications which use the VK_KHR_DISPLAY extension to result in a segmentation fault. - Enabled HardDPMS by default. See the README entry on the X configuration option "HardDPMS" for more information. - Fixed a bug which caused corruption in the following DXVK titles: Saints Row IV Saints Row: The Third - Added VP9 decode support to the NVIDIA VDPAU driver. See the VDPAU Support appendix in the README for supported VP9 decoder profiles. - Fixed a bug that could cause heapUsage values reported by VK_EXT_memory_budget to not immediately update after vkFreeMemory was called. - Changed GPU clock management strategy to more quickly ramp down clocks after a drop in GPU utilization. - Added X configuration option, "SidebandSocketPath", which controls the directory in which the X driver will create a pathname UNIX domain socket used to communicate with the NVIDIA OpenGL, Vulkan and VDPAU driver components. - The X driver will now create a fallback pathname UNIX domain socket in the directory specified by the "SidebandSocketPath" option, or /var/run by default, which will be used by other NVIDIA driver components if they are unable to connect to the default abstract socket.This fixes a bug where graphics applications run within a network namespace (which prevents the use of abstract sockets) were unable to take advantage of some driver features, such as G-Sync. - Fall back to system memory when video memory is full for some driver-internal allocations. This can help fix Xid 13 and Xid 31 cases in Vulkan applications when video memory is full.
[Desktop-packages] [Bug 1854486] [NEW] cannot build with jhbuild due to libxml2
Public bug reported: I have ubuntu 19.10 If I do: jhbuild build yelp-xsl I get "ModuleNotFoundError: No module named 'libxml2' thanks itstool -o "yelp-xsl.xml" -j "/home/dani/jhbuild/checkout/yelp-xsl/xslt/common/domains/yelp-xsl.xml.in" af.mo ar.mo as.mo ast.mo be.mo b...@latin.mo bg.mo bn.mo bn_IN.mo bs.mo ca.mo c...@valencia.mo cs.mo cy.mo da.mo de.mo dz.mo el.mo en_CA.mo en_GB.mo e...@shaw.mo eo.mo es.mo et.mo eu.mo fa.mo fi.mo fr.mo fur.mo ga.mo gd.mo gl.mo gu.mo he.mo hi.mo hr.mo hu.mo id.mo is.mo it.mo ja.mo ka.mo kk.mo km.mo kn.mo ko.mo ky.mo lt.mo lv.mo mai.mo mg.mo mk.mo ml.mo mn.mo mr.mo nb.mo ne.mo nl.mo nn.mo oc.mo or.mo pa.mo pl.mo pt.mo pt_BR.mo ro.mo ru.mo rw.mo si.mo sk.mo sl.mo sq.mo sr.mo s...@latin.mo sv.mo ta.mo te.mo tg.mo th.mo tr.mo ug.mo uk.mo uz.mo u...@cyrillic.mo vi.mo wa.mo zh_CN.mo zh_HK.mo zh_TW.mo; \ rm af.mo ar.mo as.mo ast.mo be.mo b...@latin.mo bg.mo bn.mo bn_IN.mo bs.mo ca.mo c...@valencia.mo cs.mo cy.mo da.mo de.mo dz.mo el.mo en_CA.mo en_GB.mo e...@shaw.mo eo.mo es.mo et.mo eu.mo fa.mo fi.mo fr.mo fur.mo ga.mo gd.mo gl.mo gu.mo he.mo hi.mo hr.mo hu.mo id.mo is.mo it.mo ja.mo ka.mo kk.mo km.mo kn.mo ko.mo ky.mo lt.mo lv.mo mai.mo mg.mo mk.mo ml.mo mn.mo mr.mo nb.mo ne.mo nl.mo nn.mo oc.mo or.mo pa.mo pl.mo pt.mo pt_BR.mo ro.mo ru.mo rw.mo si.mo sk.mo sl.mo sq.mo sr.mo s...@latin.mo sv.mo ta.mo te.mo tg.mo th.mo tr.mo ug.mo uk.mo uz.mo u...@cyrillic.mo vi.mo wa.mo zh_CN.mo zh_HK.mo zh_TW.mo) Traceback (most recent call last): File "/usr/bin/itstool", line 27, in import libxml2 ModuleNotFoundError: No module named 'libxml2' ** Affects: yelp-xsl (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yelp-xsl in Ubuntu. https://bugs.launchpad.net/bugs/1854486 Title: cannot build with jhbuild due to libxml2 Status in yelp-xsl package in Ubuntu: New Bug description: I have ubuntu 19.10 If I do: jhbuild build yelp-xsl I get "ModuleNotFoundError: No module named 'libxml2' thanks itstool -o "yelp-xsl.xml" -j "/home/dani/jhbuild/checkout/yelp-xsl/xslt/common/domains/yelp-xsl.xml.in" af.mo ar.mo as.mo ast.mo be.mo b...@latin.mo bg.mo bn.mo bn_IN.mo bs.mo ca.mo c...@valencia.mo cs.mo cy.mo da.mo de.mo dz.mo el.mo en_CA.mo en_GB.mo e...@shaw.mo eo.mo es.mo et.mo eu.mo fa.mo fi.mo fr.mo fur.mo ga.mo gd.mo gl.mo gu.mo he.mo hi.mo hr.mo hu.mo id.mo is.mo it.mo ja.mo ka.mo kk.mo km.mo kn.mo ko.mo ky.mo lt.mo lv.mo mai.mo mg.mo mk.mo ml.mo mn.mo mr.mo nb.mo ne.mo nl.mo nn.mo oc.mo or.mo pa.mo pl.mo pt.mo pt_BR.mo ro.mo ru.mo rw.mo si.mo sk.mo sl.mo sq.mo sr.mo s...@latin.mo sv.mo ta.mo te.mo tg.mo th.mo tr.mo ug.mo uk.mo uz.mo u...@cyrillic.mo vi.mo wa.mo zh_CN.mo zh_HK.mo zh_TW.mo; \ rm af.mo ar.mo as.mo ast.mo be.mo b...@latin.mo bg.mo bn.mo bn_IN.mo bs.mo ca.mo c...@valencia.mo cs.mo cy.mo da.mo de.mo dz.mo el.mo en_CA.mo en_GB.mo e...@shaw.mo eo.mo es.mo et.mo eu.mo fa.mo fi.mo fr.mo fur.mo ga.mo gd.mo gl.mo gu.mo he.mo hi.mo hr.mo hu.mo id.mo is.mo it.mo ja.mo ka.mo kk.mo km.mo kn.mo ko.mo ky.mo lt.mo lv.mo mai.mo mg.mo mk.mo ml.mo mn.mo mr.mo nb.mo ne.mo nl.mo nn.mo oc.mo or.mo pa.mo pl.mo pt.mo pt_BR.mo ro.mo ru.mo rw.mo si.mo sk.mo sl.mo sq.mo sr.mo s...@latin.mo sv.mo ta.mo te.mo tg.mo th.mo tr.mo ug.mo uk.mo uz.mo u...@cyrillic.mo vi.mo wa.mo zh_CN.mo zh_HK.mo zh_TW.mo) Traceback (most recent call last): File "/usr/bin/itstool", line 27, in import libxml2 ModuleNotFoundError: No module named 'libxml2' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yelp-xsl/+bug/1854486/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1854472] [NEW] ubuntu-drivers-common fails when no PATH environment variable is passed
Public bug reported: ubuntu-drivers-common fails when no PATH environment variable is passed: https://errors.ubuntu.com/problem/52d04f39f8cbdb77d65ec57f19a5801284c1e2b0 While the reasons why the PATH variable is empty are unknown, the ubuntu-drivers tools should not fail, and we can assume that a minimal PATH (such as /sbin:/usr/sbin:/bin:/usr/bin) would apply to the system. ** Affects: ubuntu-drivers-common (Ubuntu) Importance: Medium Assignee: Alberto Milone (albertomilone) Status: In Progress ** Affects: ubuntu-drivers-common (Ubuntu Bionic) Importance: Medium Assignee: Alberto Milone (albertomilone) Status: In Progress ** Affects: ubuntu-drivers-common (Ubuntu Eoan) Importance: Medium Assignee: Alberto Milone (albertomilone) Status: In Progress ** Also affects: ubuntu-drivers-common (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: ubuntu-drivers-common (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: ubuntu-drivers-common (Ubuntu Bionic) Status: New => In Progress ** Changed in: ubuntu-drivers-common (Ubuntu Eoan) Status: New => In Progress ** Changed in: ubuntu-drivers-common (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: ubuntu-drivers-common (Ubuntu Eoan) Importance: Undecided => Medium ** Changed in: ubuntu-drivers-common (Ubuntu Bionic) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: ubuntu-drivers-common (Ubuntu Eoan) Assignee: (unassigned) => Alberto Milone (albertomilone) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1854472 Title: ubuntu-drivers-common fails when no PATH environment variable is passed Status in ubuntu-drivers-common package in Ubuntu: In Progress Status in ubuntu-drivers-common source package in Bionic: In Progress Status in ubuntu-drivers-common source package in Eoan: In Progress Bug description: ubuntu-drivers-common fails when no PATH environment variable is passed: https://errors.ubuntu.com/problem/52d04f39f8cbdb77d65ec57f19a5801284c1e2b0 While the reasons why the PATH variable is empty are unknown, the ubuntu-drivers tools should not fail, and we can assume that a minimal PATH (such as /sbin:/usr/sbin:/bin:/usr/bin) would apply to the system. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1854472/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1854440] Re: Thunderbird can't sign in gmail in U20.04
*** This bug is a duplicate of bug 1850651 *** https://bugs.launchpad.net/bugs/1850651 ** This bug has been marked a duplicate of bug 1850651 [SRU] Authentication constantly re-requested for Google -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1854440 Title: Thunderbird can't sign in gmail in U20.04 Status in thunderbird package in Ubuntu: New Bug description: I have Ubuntu 20.04 Hu and Thunderbird 60.3.0 (64-bit) En. When I fill in the data, the net window pops up and then I fill in and then a window pops up to enable Thunderbird and then prints Thunderbird that the username or password invalid. I see the 68.2.2. I try this new hungarian version, and it's working. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1854440/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1854440] Re: Thunderbird can't sign in gmail in U20.04
** Project changed: launchpad => thunderbird (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1854440 Title: Thunderbird can't sign in gmail in U20.04 Status in thunderbird package in Ubuntu: New Bug description: I have Ubuntu 20.04 Hu and Thunderbird 60.3.0 (64-bit) En. When I fill in the data, the net window pops up and then I fill in and then a window pops up to enable Thunderbird and then prints Thunderbird that the username or password invalid. I see the 68.2.2. I try this new hungarian version, and it's working. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1854440/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1854440] [NEW] Thunderbird can't sign in gmail in U20.04
You have been subscribed to a public bug: I have Ubuntu 20.04 Hu and Thunderbird 60.3.0 (64-bit) En. When I fill in the data, the net window pops up and then I fill in and then a window pops up to enable Thunderbird and then prints Thunderbird that the username or password invalid. I see the 68.2.2. I try this new hungarian version, and it's working. ** Affects: thunderbird (Ubuntu) Importance: Undecided Status: New -- Thunderbird can't sign in gmail in U20.04 https://bugs.launchpad.net/bugs/1854440 You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1764417] Re: Unrecoverable failure in required component org.gnome.SettingsDaemon.Color.desktop
Same bug ('org.gnome.SettingsDaemon.Color.desktop' failed to register) for me, but no NVIDIA card involved : VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller (rev 09) I'm using Ubuntu 18.04.3, and it happens randomly, but only since a few weeks... -- You received this bug notification because you are a member of Desktop Packages, 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 Status in gnome-settings-daemon package in Ubuntu: Confirmed Bug description: I've had this happen a couple of times now since upgrading to 18.04: soon (perhaps within a minute) after logging in, Gnome session ends abruptly and I'm thrown back to the login screen. IIRC, in both instances this occurred on the first login after boot, so it does not reoccur on the subsequent re-login, and not on every login (very rarely in fact), and for now I have no better steps to reproduce this other than "boot, log in". Bug #1663839 (reported against 17.04) seems similar, as does bug #1731428 (reported against 17.10). journalctl output during the issue: Apr 16 07:00:30 saegusa gnome-session[4342]: gnome-session-binary[4342]: WARNING: Application 'org.gnome.SettingsDaemon.Color.desktop' failed to register before timeout Apr 16 07:00:30 saegusa gnome-session-binary[4342]: WARNING: Application 'org.gnome.SettingsDaemon.Color.desktop' failed to register before timeout Apr 16 07:00:30 saegusa gnome-session-binary[4342]: Unrecoverable failure in required component org.gnome.SettingsDaemon.Color.desktop Apr 16 07:00:30 saegusa gnome-session[4342]: gnome-session-binary[4342]: CRITICAL: We failed, but the fail whale is dead. Sorry Apr 16 07:00:30 saegusa gnome-session-binary[4342]: CRITICAL: We failed, but the fail whale is dead. Sorry ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-settings-daemon 3.28.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 16 17:07:14 2018 InstallationDate: Installed on 2016-10-13 (550 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash SourcePackage: gnome-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1764417/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp