[Desktop-packages] [Bug 1810316] Re: gnome-control-center SIGABRT when n-m is not working (G_IS_OBJECT (object))
** Changed in: gnome-control-center (Ubuntu) Importance: Medium => Low -- 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/1810316 Title: gnome-control-center SIGABRT when n-m is not working (G_IS_OBJECT (object)) Status in gnome-control-center: New Status in NetworkManager: New Status in gnome-control-center package in Ubuntu: Triaged Status in network-manager package in Ubuntu: Incomplete Bug description: https://gitlab.gnome.org/GNOME/gnome-control-center/issues/342 https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/143 --- [Impact] gnome-control-center goes crash when I try to work with two USB WiFi cards. [Test Case] I have a wireless card connected and then I connect 'another' wireless card and the network module starts to malfunction in the gnome-control-center. [Potential Regression] I think it's not a potential regression. Original Description * I was trying to open wifi settings * I'm connecting 2 WiFi USB in ubuntu disk ProblemType: Crash DistroRelease: Ubuntu 18.10 Package: gnome-control-center 1:3.30.2-1ubuntu0.18.10.1 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Wed Jan 2 09:54:42 2019 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2018-09-27 (97 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: gnome-control-center wifi ProcEnviron: LC_COLLATE=C PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: gnome-control-center StacktraceTop: () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 cc_object_storage_add_object () cc_wifi_panel_static_init_func () cc_panel_loader_fill_model () Title: gnome-control-center crashed with SIGABRT UpgradeStatus: Upgraded to cosmic on 2018-11-08 (54 days ago) UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo vboxusers wireshark modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2018-10-04T06:36:50.792292 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1810316/+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 1809856] Re: [XPS 13 9370, Realtek ALC3271, Headphone Out, Right] Static/Electric background noise when volume is not muted
Seems like it goes away as soon as the audio gets runtime suspended. Is the original issue solved or somewhat alleviated? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1809856 Title: [XPS 13 9370, Realtek ALC3271, Headphone Out, Right] Static/Electric background noise when volume is not muted Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: Whenever I plug in my Sennheiser HD1 Wired headphones with mic, I start hearing a static/electric (some internal?) sound if the volume isn't muted. Something similar occurs with my other earbuds with mic, just much quieter and less noticable. It works fine on Windows 10 running on the same machine, and on my Android phone. I don't notice is when something is playing, but the frequency of the sound changes when I play something, then pause it, the background noise will sound slightly different. This is from an installed Ubuntu 18.10. I have tried booting 18.10 Live USB and 18.04.1 LTS Live USB, and the issue still occurs. I have tried playing with alsamixer and pavucontrol settings, and nothing fixed this background noise. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: davidkoplik 1891 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Dec 26 20:17:59 2018 InstallationDate: Installed on 2018-12-26 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Headphone Out, Right Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: High background noise, or volume is too low Title: [XPS 13 9370, Realtek ALC3271, Black Headphone Out, Right] Background noise or low volume UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/04/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.3 dmi.board.name: 0F6P3V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.3:bd11/04/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1809856/+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 1824755] Re: package install-info 6.5.0.dfsg.1-2 failed to install/upgrade: installed install-info package post-installation script subprocess returned error exit status 1
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to texinfo in Ubuntu. https://bugs.launchpad.net/bugs/1824755 Title: package install-info 6.5.0.dfsg.1-2 failed to install/upgrade: installed install-info package post-installation script subprocess returned error exit status 1 Status in texinfo package in Ubuntu: New Bug description: package install-info 6.5.0.dfsg.1-2 failed to install/upgrade: installed install-info package post-installation script subprocess returned error exit status 1 ProblemType: Package DistroRelease: Ubuntu 18.04 Package: install-info 6.5.0.dfsg.1-2 ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_4_15_0_46_49_generic_49 nvidia ApportVersion: 2.20.9-0ubuntu7.2 AptOrdering: install-info:amd64: Configure google-chrome-stable:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Sat Apr 13 17:49:40 2019 ErrorMessage: installed install-info package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2019-03-13 (32 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.6ubuntu0.1 SourcePackage: texinfo Title: package install-info 6.5.0.dfsg.1-2 failed to install/upgrade: installed install-info package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/texinfo/+bug/1824755/+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 1824755] [NEW] package install-info 6.5.0.dfsg.1-2 failed to install/upgrade: installed install-info package post-installation script subprocess returned error exit status 1
Public bug reported: package install-info 6.5.0.dfsg.1-2 failed to install/upgrade: installed install-info package post-installation script subprocess returned error exit status 1 ProblemType: Package DistroRelease: Ubuntu 18.04 Package: install-info 6.5.0.dfsg.1-2 ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_4_15_0_46_49_generic_49 nvidia ApportVersion: 2.20.9-0ubuntu7.2 AptOrdering: install-info:amd64: Configure google-chrome-stable:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Sat Apr 13 17:49:40 2019 ErrorMessage: installed install-info package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2019-03-13 (32 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.6ubuntu0.1 SourcePackage: texinfo Title: package install-info 6.5.0.dfsg.1-2 failed to install/upgrade: installed install-info package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: texinfo (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to texinfo in Ubuntu. https://bugs.launchpad.net/bugs/1824755 Title: package install-info 6.5.0.dfsg.1-2 failed to install/upgrade: installed install-info package post-installation script subprocess returned error exit status 1 Status in texinfo package in Ubuntu: New Bug description: package install-info 6.5.0.dfsg.1-2 failed to install/upgrade: installed install-info package post-installation script subprocess returned error exit status 1 ProblemType: Package DistroRelease: Ubuntu 18.04 Package: install-info 6.5.0.dfsg.1-2 ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_4_15_0_46_49_generic_49 nvidia ApportVersion: 2.20.9-0ubuntu7.2 AptOrdering: install-info:amd64: Configure google-chrome-stable:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Sat Apr 13 17:49:40 2019 ErrorMessage: installed install-info package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2019-03-13 (32 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.6ubuntu0.1 SourcePackage: texinfo Title: package install-info 6.5.0.dfsg.1-2 failed to install/upgrade: installed install-info package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/texinfo/+bug/1824755/+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 1629558] Re: Chromium sync says service unavailible
[Expired for chromium-browser (Ubuntu) because there has been no activity for 60 days.] ** Changed in: chromium-browser (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1629558 Title: Chromium sync says service unavailible Status in chromium-browser package in Ubuntu: Expired Bug description: Hello. I'm building the packages for the Raspberry Pi and currently, I'm building from upstream, but using your options. It seems like the API keys are not working. I built a version and then tried my own keys and the new keys you supplied in v52, but the same issue persists. This is using v51. I've attached the network log and it seems like it's getting a 404 for some reason. Any assistance is appreciated! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1629558/+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 1643208] Re: Chrome/Chromium glitch in Ubuntu 16.04
[Expired for chromium-browser (Ubuntu) because there has been no activity for 60 days.] ** Changed in: chromium-browser (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1643208 Title: Chrome/Chromium glitch in Ubuntu 16.04 Status in chromium-browser package in Ubuntu: Expired Bug description: I am experiencing glithces in Chrome and Chromium browsers under Ubuntu 16.04 (64 bit), as shown in the picture: https://i.stack.imgur.com/zYap0.png My browser versions are - Chromium 53.0.2785.143 Built on Ubuntu - Chrome 54.0.2840.100 (64-bit) - Firefox 49.02 Firefox does not present this issue. I have a VGA compatible controller: Intel Corporation Broadwell-U Integrated Graphics (rev 09) on a Thinkpad X250. Solutions provided in http://askubuntu.com/questions/766725/annoying- flickering-in-16-04-lts-chrome (disable GPU acceleration) do not work. The kind of glithces are *not* like this https://www.youtube.com/watch?v=l21WsKz3fZc=youtu.be=45s Very rarely, the same effect appears while zooming FITS images using the saods9 package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1643208/+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 1815523] Re: The last MESA updates (02/07/19) corrupted output to DisplayLink
[Expired for mesa (Ubuntu) because there has been no activity for 60 days.] ** Changed in: mesa (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1815523 Title: The last MESA updates (02/07/19) corrupted output to DisplayLink Status in mesa package in Ubuntu: Expired Bug description: Prior to Thursday's "update" from Bionic-Proposed, the MESA was working fine; afterwards, gameplay on STEAM has become choppy and staccato; secondary display via a USB-C through DisplayPort UD3900 (Pluggable) is completely corrupted. See attached picture. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-15-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity:Unity7:ubuntu Date: Mon Feb 11 16:50:58 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: acpi-call, 1.1.0, 4.18.0-15-generic, x86_64: installedError! Could not locate dkms.conf file. File: does not exist. ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Device [1558:1323] InstallationDate: Installed on 2019-01-15 (27 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: System76 Galago Pro ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-15-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/05/2018 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.03 dmi.board.asset.tag: Tag 12345 dmi.board.name: Galago Pro dmi.board.vendor: System76 dmi.board.version: galp3-c dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76 dmi.chassis.version: galp3-c dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.03:bd12/05/2018:svnSystem76:pnGalagoPro:pvrgalp3-c:rvnSystem76:rnGalagoPro:rvrgalp3-c:cvnSystem76:ct10:cvrgalp3-c: dmi.product.family: Not Applicable dmi.product.name: Galago Pro dmi.product.sku: Not Applicable dmi.product.version: galp3-c dmi.sys.vendor: System76 version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 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/mesa/+bug/1815523/+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 1821439] Re: speech-dispatcher produces sound errors in Firefox
*** This bug is a duplicate of bug 1736222 *** https://bugs.launchpad.net/bugs/1736222 ** This bug has been marked a duplicate of bug 1736222 speech-dispatcher distorts all sound -- 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/1821439 Title: speech-dispatcher produces sound errors in Firefox Status in speech-dispatcher package in Ubuntu: New Bug description: Ubuntu Gnome 18.10 Expected behaviour: Play media content in different tab in Firefox while viewing a page in Firefox' readingview (that option given in the URL-bar for a text version of a site) What happens: As soon as i open the website in Firefox special readingview, all sounds from the media tab starts to make crackling sounds. Workaround: Close Firefox and don't use reading view. Second workaround: Removing packet "speech-dispatcher" completly remove this issue. This issue is extra annoying in Kubuntu as it starts as soon as i open one of the PIM applications, i.e. kmail or akkregator. Seems to be cross-distribution as i experienced it on OpenSUSE Leap 15 / Tumbleweed KDE and could be resolved by removing speech-dispatcher packet. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: speech-dispatcher (not installed) ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20 Uname: Linux 4.18.0-16-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Mar 23 09:09:17 2019 InstallationDate: Installed on 2019-03-17 (5 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash 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/1821439/+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 1804742] Re: package gnome-shell-common 3.28.3-0ubuntu0.18.04.3 failed to install/upgrade: installed gnome-shell-common package post-installation script subprocess returned err
** Tags added: cosmic ** Summary changed: - package gnome-shell-common 3.28.3-0ubuntu0.18.04.3 failed to install/upgrade: installed gnome-shell-common package post-installation script subprocess returned error exit status 2 + package gnome-shell-common ... failed to install/upgrade: installed gnome-shell-common package post-installation script subprocess returned error exit status 2 -- 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/1804742 Title: package gnome-shell-common ... failed to install/upgrade: installed gnome-shell-common package post-installation script subprocess returned error exit status 2 Status in gnome-shell package in Ubuntu: Confirmed Bug description: dpkg: dependency problems prevent configuration of gnome-shell: gnome-shell depends on gnome-shell-common (= 3.28.3-0ubuntu0.18.04.3); however: Package gnome-shell-common is not configured yet. dpkg: error processing package gnome-shell (--configure): dependency problems - leaving unconfigured No apport report written because the error message indicates its a followup error from a previous failure. Setting up libpython3.6-dev:amd64 (3.6.7-1~18.04) ... Setting up libsmbclient:amd64 (2:4.7.6+dfsg~ubuntu-0ubuntu2.4) ... Setting up libisccfg160:amd64 (1:9.11.3+dfsg-1ubuntu1.3) ... Setting up gir1.2-mutter-2:amd64 (3.28.3-2~ubuntu18.04.2) ... dpkg: dependency problems prevent configuration of update-manager: update-manager depends on policykit-1-gnome | polkit-kde-agent-1 | lxpolkit | lxqt-policykit | mate-polkit | polkit-1-auth-agent; however: Package policykit-1-gnome is not installed. Package polkit-kde-agent-1 is not installed. Package lxpolkit is not installed. Package lxqt-policykit is not installed. Package mate-polkit is not installed. Package polkit-1-auth-agent is not installed. Package gnome-shell which provides polkit-1-auth-agent is not configured yet. dpkg: error processing package update-manager (--configure): dependency problems - leaving unconfigured Setting up python3-gdbm:amd64 (3.6.7-1~18.04) ... No apport report written because the error message indicates its a followup error from a previous failure. Setting up packagekit-tools (1.1.9-1ubuntu2.18.04.4) ... ProblemType: Package DistroRelease: Ubuntu 18.04 Package: gnome-shell-common 3.28.3-0ubuntu0.18.04.3 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Fri Nov 23 10:56:40 2018 DisplayManager: gdm3 ErrorMessage: installed gnome-shell-common package post-installation script subprocess returned error exit status 2 GsettingsChanges: InstallationDate: Installed on 2018-08-21 (93 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python3.6, Python 3.6.7, unpackaged RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.6 SourcePackage: gnome-shell Title: package gnome-shell-common 3.28.3-0ubuntu0.18.04.3 failed to install/upgrade: installed gnome-shell-common package post-installation script subprocess returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1804742/+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 1824739] Re: The computer is not able to resume after suspend.
Please: 1. Reproduce the freeze, and then reboot. 2. Run: journalctl -b-1 > prevboot.txt and send us the file 'prevboot.txt'. ** Summary changed: - Xorg freeze + The computer is not able to resume after suspend. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- 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/1824739 Title: The computer is not able to resume after suspend. Status in Ubuntu: Incomplete Bug description: The computer is not able to resume after suspend. The screen brightness is not able to be adjusted ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 Uname: Linux 5.0.0-05-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Apr 15 06:18:34 2019 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GpuHangFrequency: Several times a week GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: I don't know GraphicsCard: Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:15e0] Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Mobile] [1043:15e0] InstallationDate: Installed on 2018-06-27 (291 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:b718 Realtek Semiconductor Corp. Bus 001 Device 002: ID 13d3:5654 IMC Networks Bus 001 Device 004: ID 0b05:1854 ASUSTek Computer, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. GL553VD ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-05-generic root=UUID=efd91b16-1bc9-46b5-805f-5994b58f82f6 ro nouveau.modeset=0 nouveau.blacklist=1 quiet splash nomodeset acpi_backlight=vendor nouveau.modeset=0 nouveau.blacklist=1 vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/02/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GL553VD.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GL553VD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGL553VD.306:bd01/02/2018:svnASUSTeKCOMPUTERINC.:pnGL553VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL553VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: GL dmi.product.name: GL553VD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.10.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.10.2 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1824739/+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 1722256] Re: Wifi connection status icon shows a "?" question mark when connected
** Description changed: + https://bugzilla.gnome.org/show_bug.cgi?id=750260 + Wifi connection status icon on the top bar shows a "?" even when connected to a wifi network. - --- + --- ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-09-28 (11 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) Package: gnome-shell 3.26.1-0ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Tags: artful wayland-session Uname: Linux 4.13.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True ** Bug watch added: GNOME Bug Tracker #750260 https://gitlab.gnome.org/750260 ** No longer affects: gnome-shell ** Tags removed: artful ** Tags added: disco -- 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/1722256 Title: Wifi connection status icon shows a "?" question mark when connected Status in OEM Priority Project: Confirmed Status in gnome-shell package in Ubuntu: Triaged Bug description: https://bugzilla.gnome.org/show_bug.cgi?id=750260 Wifi connection status icon on the top bar shows a "?" even when connected to a wifi network. --- ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-09-28 (11 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) Package: gnome-shell 3.26.1-0ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Tags: artful wayland-session Uname: Linux 4.13.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1722256/+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 1824752] Re: package gnome-shell-common 3.30.2-0ubuntu1.18.10.1 failed to install/upgrade: installed gnome-shell-common package post-installation script subprocess returned err
*** This bug is a duplicate of bug 1804742 *** https://bugs.launchpad.net/bugs/1804742 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1804742, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1804742 package gnome-shell-common 3.28.3-0ubuntu0.18.04.3 failed to install/upgrade: installed gnome-shell-common package post-installation script subprocess returned error exit status 2 -- 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/1824752 Title: package gnome-shell-common 3.30.2-0ubuntu1.18.10.1 failed to install/upgrade: installed gnome-shell-common package post- installation script subprocess returned error exit status 2 Status in gnome-shell package in Ubuntu: New Bug description: When trying to update , reinstall , purge or whatever command it does this : E: gnome-shell-common: installed gnome-shell-common package post- installation script subprocess returned error exit status 2 ProblemType: Package DistroRelease: Ubuntu 18.10 Package: gnome-shell-common 3.30.2-0ubuntu1.18.10.1 ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20 Uname: Linux 4.18.0-17-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 AptOrdering: gnome-shell:amd64: Install ubuntu-session:amd64: Install gdm3:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Sun Apr 14 23:07:24 2019 DisplayManager: gdm3 DuplicateSignature: package:gnome-shell-common:3.30.2-0ubuntu1.18.10.1 Setting up gnome-shell-common (3.30.2-0ubuntu1.18.10.1) ... update-alternatives: error: cannot stat file '/etc/alternatives/gdm3.css': Invalid argument dpkg: error processing package gnome-shell-common (--configure): installed gnome-shell-common package post-installation script subprocess returned error exit status 2 ErrorMessage: installed gnome-shell-common package post-installation script subprocess returned error exit status 2 GsettingsChanges: InstallationDate: Installed on 2019-04-13 (1 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.10 PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3 RelatedPackageVersions: dpkg 1.19.0.5ubuntu5 apt 1.7.4 SourcePackage: gnome-shell Title: package gnome-shell-common 3.30.2-0ubuntu1.18.10.1 failed to install/upgrade: installed gnome-shell-common package post-installation script subprocess returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1824752/+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 1824692] Re: Question mark within the Wi-Fi icon
*** This bug is a duplicate of bug 1722256 *** https://bugs.launchpad.net/bugs/1722256 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1722256, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1722256 Wifi connection status icon shows a "?" question mark when connected -- 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/1824692 Title: Question mark within the Wi-Fi icon Status in gnome-shell package in Ubuntu: New Bug description: Question mark within the Wi-Fi icon after connecting to the internet. It should be noted that there is no problem with connecting to the Internet, and I have full Internet access and there is only a question mark within the Wi-Fi icon. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-11.12-generic 5.0.6 Uname: Linux 5.0.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperVersion: 1.403 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Apr 14 10:48:29 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 5500 [1043:194d] Subsystem: ASUSTeK Computer Inc. GK208BM [GeForce 920M] [1043:232a] LiveMediaBuild: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190413.2) MachineType: ASUSTeK COMPUTER INC. TP300LJ ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed boot=casper quiet splash --- SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/05/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: TP300LJ.206 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: TP300LJ dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrTP300LJ.206:bd08/05/2015:svnASUSTeKCOMPUTERINC.:pnTP300LJ:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnTP300LJ:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: TP dmi.product.name: TP300LJ dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1824692/+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 1824670] Re: Boot to black screen after Kubuntu 19.04 install
There are one or two issues here. The second one at least shows a problem in the Nvidia kernel driver: [ 11.094895] NVRM: Your system is not currently configured to drive a VGA console [ 11.094899] NVRM: on the primary VGA device. The NVIDIA Linux graphics driver [ 11.094900] NVRM: requires the use of a text-mode VGA console. Use of other console [ 11.094901] NVRM: drivers including, but not limited to, vesafb, may result in [ 11.094902] NVRM: corruption and stability problems, and is not supported. [ 11.132280] [ cut here ] [ 11.132285] Bad or missing usercopy whitelist? Kernel memory exposure attempt detected from SLUB object 'nvidia_stack_t' (offset 11864, size 3)! [ 11.132303] WARNING: CPU: 0 PID: 704 at mm/usercopy.c:83 usercopy_warn+0x81/0xa0 [ 11.132304] Modules linked in: nvidia_uvm(POE) dell_laptop dell_smbios dell_wmi_descriptor coretemp wmi dcdbas dell_smm_hwmon kvm_intel kvm irqbypass arc4 uvcvideo iwldvm videobuf2_vmalloc videobuf2_memops mac80211 videobuf2_v4l2 videobuf2_common joydev videodev input_leds media iwlwifi snd_hda_codec_idt snd_hda_codec_generic ledtrig_audio cfg80211 snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq nvidia(POE) snd_seq_device snd_timer snd drm mac_hid serio_raw soundcore sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 hid_generic usbhid hid i2c_i801 psmouse ahci libahci lpc_ich r8169 realtek video [ 11.132342] CPU: 0 PID: 704 Comm: Xorg Tainted: P OE 5.0.0-11-generic #12-Ubuntu [ 11.132343] Hardware name: Dell Inc. Vostro 1720/0P369J, BIOS A05 10/27/2009 [ 11.132345] RIP: 0010:usercopy_warn+0x81/0xa0 [ 11.132347] Code: 0f a8 41 51 4d 89 d8 48 c7 c0 98 a1 0e a8 49 89 f1 48 89 f9 48 0f 45 c2 48 c7 c7 28 c2 0f a8 4c 89 d2 48 89 c6 e8 11 03 df ff <0f> 0b 48 83 c4 18 c9 c3 48 c7 c6 e2 ae 11 a8 49 89 f1 49 89 f3 eb [ 11.132349] RSP: 0018:a3ff8191bb58 EFLAGS: 00010282 [ 11.132350] RAX: RBX: 902ff2a82e58 RCX: 0006 [ 11.132352] RDX: 0007 RSI: 0092 RDI: 902ffba16440 [ 11.132353] RBP: a3ff8191bb70 R08: 0001 R09: 036c [ 11.132354] R10: 0004 R11: R12: 0003 [ 11.132355] R13: 0001 R14: 902ff2a82e5b R15: 902ff2a82ea0 [ 11.132357] FS: 7fc7286eca80() GS:902ffba0() knlGS: [ 11.132359] CS: 0010 DS: ES: CR0: 80050033 [ 11.132360] CR2: 7fc723cce160 CR3: 00013346a000 CR4: 000406f0 [ 11.132361] Call Trace: [ 11.132369] __check_heap_object+0xc2/0x110 [ 11.132371] __check_object_size+0x166/0x192 [ 11.132565] os_memcpy_to_user+0x26/0x50 [nvidia] [ 11.132675] _nv001372rm+0xa5/0x260 [nvidia] ** Tags added: nvidia ** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-340 (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/1824670 Title: Boot to black screen after Kubuntu 19.04 install Status in nvidia-graphics-drivers-340 package in Ubuntu: New Bug description: Legacy laptop, Dell Vostro 1720, booted to black screen after fresh full disk install. Using ctrl-alt-f2 to drop to a terminal and issuing "startx" completed the boot process. Installed NVidia 340 driver which crashed the current session and sent me to an endless GUI (sddm?) login loop where login immediately crashed back to the GUI login. Rebooting from the login screen worked as expected and system is running fine now. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-11.12-generic 5.0.6 Uname: Linux 5.0.0-11-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.107 Thu May 24 21:54:01 PDT 2018 GCC version: gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: KDE Date: Sat Apr 13 21:03:41 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu DkmsStatus: nvidia-340, 340.107, 5.0.0-11-generic, x86_64: installed GraphicsCard:
[Desktop-packages] [Bug 1824692] Re: Question mark within the Wi-Fi icon
*** This bug is a duplicate of bug 1722256 *** https://bugs.launchpad.net/bugs/1722256 The problem with the battery icon was possibly bug 1823175 (now fixed). ** Description changed: - I had two problems with Ubuntu 18.04 and earlier. - 1. Question mark within the Wi-Fi icon after connecting to the internet. - 2. Question mark within the battery icon after the battery is fully charged. - - I tested the 19.04 version right now and realized that my problem with the battery icon was fixed. - But my problem with Wi-Fi icon is still there. + Question mark within the Wi-Fi icon after connecting to the internet. It should be noted that there is no problem with connecting to the Internet, and I have full Internet access and there is only a question mark within the Wi-Fi icon. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-11.12-generic 5.0.6 Uname: Linux 5.0.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperVersion: 1.403 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Apr 14 10:48:29 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: - Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) -Subsystem: ASUSTeK Computer Inc. HD Graphics 5500 [1043:194d] -Subsystem: ASUSTeK Computer Inc. GK208BM [GeForce 920M] [1043:232a] + Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) + Subsystem: ASUSTeK Computer Inc. HD Graphics 5500 [1043:194d] + Subsystem: ASUSTeK Computer Inc. GK208BM [GeForce 920M] [1043:232a] LiveMediaBuild: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190413.2) MachineType: ASUSTeK COMPUTER INC. TP300LJ ProcEnviron: - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=C.UTF-8 - SHELL=/bin/bash + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=C.UTF-8 + SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed boot=casper quiet splash --- SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/05/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: TP300LJ.206 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: TP300LJ dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrTP300LJ.206:bd08/05/2015:svnASUSTeKCOMPUTERINC.:pnTP300LJ:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnTP300LJ:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: TP dmi.product.name: TP300LJ dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Package changed: xorg (Ubuntu) => gnome-shell (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/1824692 Title: Question mark within the Wi-Fi icon Status in gnome-shell package in Ubuntu: New Bug description: Question mark within the Wi-Fi icon after connecting to the internet. It should be noted that there is no problem with connecting to the Internet, and I have full Internet access and there is only a question mark within the Wi-Fi icon. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-11.12-generic 5.0.6 Uname: Linux 5.0.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperVersion: 1.403 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Apr 14 10:48:29 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 5500 [1043:194d] Subsystem: ASUSTeK Computer Inc. GK208BM [GeForce 920M] [1043:232a] LiveMediaBuild:
[Desktop-packages] [Bug 1824661] Re: Nvidia issues with 19.04 and XPS 15 9750 GTX 1050 Ti Mobile: Boots to blank screen that flashes a couple times. Can't get to tty.
Please: 1. Remove 'nomodeset' and reproduce the problem at least once. 2. Reintroduce 'nomodeset', reboot and then immediately run: journalctl -b-1 > prevboot and send us the file 'prevboot.txt'. ** Summary changed: - Nvidia issues with 19.04 and XPS 15 9750 GTX 1050 Ti Mobile + Nvidia issues with 19.04 and XPS 15 9750 GTX 1050 Ti Mobile: Boots to blank screen that flashes a couple times. Can't get to tty. ** Tags added: nvidia ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- 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/1824661 Title: Nvidia issues with 19.04 and XPS 15 9750 GTX 1050 Ti Mobile: Boots to blank screen that flashes a couple times. Can't get to tty. Status in Ubuntu: Incomplete Bug description: Hello. I am having issues consistently with this laptop and the Nvidia drivers in 19.04. I have tested this on Ubuntu, Kubuntu, Ubuntu Budgie, and Ubuntu MATE. This is with both the recommended 418 driver as well as 390. Today I tried installing the latest daily of Ubuntu MATE with the proprietary driver option on my Dell XPS 15 9570 with Nvidia GP107M (GeForce GRX 1050 Time Mobile). Boots to blank screen that flashes a couple times. Can't get to tty. Reboot, editing grub to include nomodeset. Boots to underscore character in the top left. I can get tty at least. 418 driver is installed. Looking at logs but nothing seems obvious. If there's anything I can do to help with this please let me know. Thanks! ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-11.12-generic 5.0.6 Uname: Linux 5.0.0-11-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 418.56 Fri Mar 15 12:59:26 CDT 2019 GCC version: gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1) ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' Date: Sat Apr 13 18:27:12 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu DkmsStatus: nvidia, 418.56, 5.0.0-11-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 630 (Mobile) [1028:087c] Subsystem: Dell GP107M [GeForce GTX 1050 Ti Mobile] [1028:087c] InstallationDate: Installed on 2019-04-13 (0 days ago) InstallationMedia: Ubuntu-MATE 19.04 "Disco Dingo" - Alpha amd64 (20190413.2) MachineType: Dell Inc. XPS 15 9570 ProcEnviron: TERM=cygwin PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-11-generic root=UUID=add8471d-1273-4547-aef3-4be006f9eb9c ro quiet splash nomodeset vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/01/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.1 dmi.board.name: 0D0T05 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.1:bd02/01/2019:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9570 dmi.product.sku: 087C dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.14.0+19.04.20190223.1-0ubuntu1 version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1824661/+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 1824657] Re: GNOME shell crash
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- 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/1824657 Title: GNOME shell crash Status in gnome-shell package in Ubuntu: Incomplete Bug description: I was watching a video on youtube with the Chromium snap browser, suddenly the GNOME shell crashed, no possibility to click for Chromium or other closure, but I managed to access a tty4 session, by pressing the keys: ctrl + alt + f4. Using Ubuntu 19.04 from the beginning of development, first with KDE, after I install GNOME with the metapackage: sudo apt install ubuntu-desktop, eliminating any KDE package, until now I have had no problem. full update, proposed repository disabled. I attach the logs from the time I had the problem, about 10:50 pm, I started with the logs at 10:40 pm with this command: journalctl --since "2019-04-13 22:40:00" ( if it is wrong, let him know) From the logs I see many gnome-shell errors, but obviously I can't decipher them if it was the cause of the problem. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.32.0+git20190410-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-11.12-generic 5.0.6 Uname: Linux 5.0.0-11-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 13 23:07:59 2019 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.shell' b'enabled-extensions' b"['move_cl...@jonathan.bluemosh.com', 'openweather-extens...@jenslody.de', 'sound-output-device-choo...@kgshank.net', 'apps-m...@gnome-shell-extensions.gcampax.github.com', 'applications_m...@rmy.pobox.com', 'gsconn...@andyholmes.github.io', 'move_cl...@rmy.pobox.com', 'desktop-icons@csoriano']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'enable-animations' b'false' InstallationDate: Installed on 2019-02-18 (53 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190130) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1824657/+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 1821863] Re: Need to add Intel CML related pci-id's
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed- bionic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1821863 Title: Need to add Intel CML related pci-id's Status in libdrm package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem package in Ubuntu: Fix Committed Status in mesa package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Fix Released Status in libdrm source package in Bionic: New Status in linux source package in Bionic: Invalid Status in linux-oem source package in Bionic: Fix Committed Status in mesa source package in Bionic: New Status in xorg-server source package in Bionic: New Status in libdrm source package in Disco: Fix Released Status in linux source package in Disco: Fix Released Status in linux-oem source package in Disco: Fix Committed Status in mesa source package in Disco: Fix Released Status in xorg-server source package in Disco: Fix Released Bug description: [Impact] Please make it happen in the coming oem-kernel as there will be a flood of Intel Comet Lake (CML) platforms that would need it. Thank you. The same is needed for the rest of the stack. CML is basically another iteration of Skylake/Kabylake/Coffee Lake, and doesn't need other changes than pci-id's and support for the PCH (similar to Cannon point, already supported by the kernel). [Test case] Test that i915 graphics works on CML. [Regression potential] None really, these only add a bunch of new pci-id's across the stack. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1821863/+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 1824641] Re: Blank screen after booting 4.4.0-145
** Tags added: regression-update xenial -- 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/1824641 Title: Blank screen after booting 4.4.0-145 Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Invalid Bug description: Having run update on my i386 Asus Eee PC with Intel Atom N550 Dual core CPU running 16.04.06 LTS, it installed linux 4.4.0-145. If I boot this kernel everything is blank. Just a black screen. If I change to a terminal using Ctrl Alt F4 it is still a black screen but I can carefully type in my user name and password and then the shutdown command and it shuts down Using Advanced options in grub neither the upstart or the recovery option work. The screen is still black. The recovery option does, however, display the boot sequence before going black. I can boot the previous kernel 4.4.0-143 and all is OK. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824641/+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 1824602] Re: Screen pixelation with linux kernel > 4.17.19-041719
Can you please provide a photo or video of the problem? ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: New => Incomplete -- 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/1824602 Title: Screen pixelation with linux kernel > 4.17.19-041719 Status in linux package in Ubuntu: Invalid Bug description: At random intervals the screen suddenly pixelates. The issue does not happen when using the linux kernel v4.17.19-041719 but happens when using other kernels greater than v4.17.19-041719 upto and including 5.0.0-8.9 Please let me know if you need any other logs and I can provide the same. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CompositorRunning: None Date: Fri Apr 12 21:25:09 2019 DistUpgraded: 2019-02-16 12:12:04,532 DEBUG confirmRestart() called DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Haswell-ULT Integrated Graphics Controller [103c:198f] InstallationDate: Installed on 2018-11-07 (156 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Hewlett-Packard HP EliteBook 840 G1 ProcEnviron: LC_CTYPE=en_US.UTF-8 TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-8-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to disco on 2019-02-16 (55 days ago) dmi.bios.date: 01/24/2014 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L71 Ver. 01.06 dmi.board.name: 198F dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 15.52 dmi.chassis.asset.tag: CNU4079SS2 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrL71Ver.01.06:bd01/24/2014:svnHewlett-Packard:pnHPEliteBook840G1:pvrA3009DD10303:rvnHewlett-Packard:rn198F:rvrKBCVersion15.52:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI dmi.product.name: HP EliteBook 840 G1 dmi.product.sku: G3C37US#ABA dmi.product.version: A3009DD10303 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97+git1904121830.210bfd~oibaf~d version.libgl1-mesa-dri: libgl1-mesa-dri 19.1~git1904121930.f4fc2e~oibaf~d version.libgl1-mesa-glx: libgl1-mesa-glx 19.1~git1904121930.f4fc2e~oibaf~d version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824602/+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 1824605] Re: bug after system check
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Thanks! ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- 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/1824605 Title: bug after system check Status in Ubuntu: Incomplete Bug description: found by system ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18 Uname: Linux 4.15.0-47-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sat Apr 13 10:35:16 2019 DistUpgraded: 2019-03-22 00:19:00,585 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation HD Graphics 620 [8086:2070] InstallationDate: Installed on 2018-03-31 (377 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) MachineType: Intel Corporation NUC7i5DNHE ProcEnviron: LANGUAGE=zh_TW:zh PATH=(custom, no user) LANG=zh_TW.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-47-generic root=UUID=6cfcf0bf-8dcd-4a3b-882a-a01eb3bc3bdd ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2019-03-21 (22 days ago) dmi.bios.date: 03/15/2018 dmi.bios.vendor: Intel Corp. dmi.bios.version: DNKBLi5v.86A.0040.2018.0315.1451 dmi.board.name: NUC7i5DNB dmi.board.vendor: Intel Corporation dmi.board.version: J57626-401 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2 dmi.modalias: dmi:bvnIntelCorp.:bvrDNKBLi5v.86A.0040.2018.0315.1451:bd03/15/2018:svnIntelCorporation:pnNUC7i5DNHE:pvrJ71739-401:rvnIntelCorporation:rnNUC7i5DNB:rvrJ57626-401:cvnIntelCorporation:ct35:cvr2: dmi.product.family: Intel NUC dmi.product.name: NUC7i5DNHE dmi.product.version: J71739-401 dmi.sys.vendor: Intel Corporation version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 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 xserver.bootTime: Thu Mar 21 22:13:58 2019 xserver.configfile: default xserver.errors: open /dev/fb0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.outputs: OutputDP-1 DP-2 xserver.version: 2:1.19.6-1ubuntu4.1~16.04.2 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1824605/+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 1814169] Re: Mutter upsteam bug: cannot overwrite workspaces layout
** Changed in: mutter
Status: Unknown => New
--
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/1814169
Title:
Mutter upsteam bug: cannot overwrite workspaces layout
Status in Mutter:
New
Status in mutter package in Ubuntu:
Fix Released
Status in mutter source package in Bionic:
New
Status in mutter source package in Cosmic:
New
Status in mutter source package in Disco:
Fix Released
Bug description:
Running up-to-date Ubuntu Cosmic. Since I am running a version with
manually applied patched from below, I couldn't use the ubuntu-bug
helper.
Bug: When using GNOME extension “Workspace grid” that arranges
workspaces in a grid, one can find that horizontal switch animation is
replaced with a vertical one. This is caused by a bug in mutter
itself, it's acknowledged and fixed in upsteam. Applying the patch for
the current version in Ubuntu solves the issue as well.
GIFs of the issue could be found here: https://medium.com/@hkdb/patch-
gnome-3-30-for-workspace-grid-1ee8b1dd92f9.
Upstream bug: https://gitlab.gnome.org/GNOME/mutter/issues/270.
Upsteam fix:
https://gitlab.gnome.org/rmyorston/mutter/commit/97a3a9b24b3655003467d5fac6bb1ec1c60e
(merged into master 3 months ago).
The patch to fix is, literally, adding 1 meaningful line:
From 86a719cc78149b7db189ff7e5d1f16418d257e9e Mon Sep 17 00:00:00 2001
From: Ron Yorston
Date: Tue, 2 Oct 2018 12:47:05 +0100
Subject: [PATCH] Allow workspace layout to be overridden
meta_workspace_manager_override_workspace_layout is implemented by
calling meta_workspace_manager_update_workspace_layout which
respects the workspace_layout_overridden flag. After the first call
to meta_workspace_manager_override_workspace_layout all subsequent
calls fail silently.
Reset workspace_layout_overridden to FALSE before calling
meta_workspace_manager_update_workspace_layout.
Signed-off-by: Ron Yorston
---
src/core/meta-workspace-manager.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/src/core/meta-workspace-manager.c
b/src/core/meta-workspace-manager.c
index 2670f4938..abc819db0 100644
--- a/src/core/meta-workspace-manager.c
+++ b/src/core/meta-workspace-manager.c
@@ -496,6 +496,8 @@ meta_workspace_manager_override_workspace_layout
(MetaWorkspaceManager *workspac
int
n_rows,
int
n_columns)
{
+ workspace_manager->workspace_layout_overridden = FALSE;
+
meta_workspace_manager_update_workspace_layout (workspace_manager,
starting_corner,
vertical_layout,
--
2.17.1
Hopefully this one is fast to test and apply ;)
To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1814169/+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 1824752] Re: package gnome-shell-common 3.30.2-0ubuntu1.18.10.1 failed to install/upgrade: installed gnome-shell-common package post-installation script subprocess returned err
** Tags removed: need-duplicate-check -- 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/1824752 Title: package gnome-shell-common 3.30.2-0ubuntu1.18.10.1 failed to install/upgrade: installed gnome-shell-common package post- installation script subprocess returned error exit status 2 Status in gnome-shell package in Ubuntu: New Bug description: When trying to update , reinstall , purge or whatever command it does this : E: gnome-shell-common: installed gnome-shell-common package post- installation script subprocess returned error exit status 2 ProblemType: Package DistroRelease: Ubuntu 18.10 Package: gnome-shell-common 3.30.2-0ubuntu1.18.10.1 ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20 Uname: Linux 4.18.0-17-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 AptOrdering: gnome-shell:amd64: Install ubuntu-session:amd64: Install gdm3:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Sun Apr 14 23:07:24 2019 DisplayManager: gdm3 DuplicateSignature: package:gnome-shell-common:3.30.2-0ubuntu1.18.10.1 Setting up gnome-shell-common (3.30.2-0ubuntu1.18.10.1) ... update-alternatives: error: cannot stat file '/etc/alternatives/gdm3.css': Invalid argument dpkg: error processing package gnome-shell-common (--configure): installed gnome-shell-common package post-installation script subprocess returned error exit status 2 ErrorMessage: installed gnome-shell-common package post-installation script subprocess returned error exit status 2 GsettingsChanges: InstallationDate: Installed on 2019-04-13 (1 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.10 PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3 RelatedPackageVersions: dpkg 1.19.0.5ubuntu5 apt 1.7.4 SourcePackage: gnome-shell Title: package gnome-shell-common 3.30.2-0ubuntu1.18.10.1 failed to install/upgrade: installed gnome-shell-common package post-installation script subprocess returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1824752/+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 1824578] Re: Screen lock doesn't lock Launcher (left-sidebar) and Status Menus (Indicators)
Sounds a little like bug 1769383, but you would have the fix for that already. Please try uninstalling all gnome-shell extensions, since we find third party extensions tend to cause the majority of such gnome-shell bugs. ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- 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/1824578 Title: Screen lock doesn't lock Launcher (left-sidebar) and Status Menus (Indicators) Status in gnome-shell package in Ubuntu: Incomplete Bug description: After I lock the screen with SUPER+L I can still see the (left- sidebar) and Status Menus (Indicators) and click items. One of the indicators is the Clipboard indicator and it shows me the clipboard items... not good. I can also start or quit running apps from the Launcher. One suspicion I have is the "Keep Awake!" gnome extension I have. See screenshot attached. Also, sometimes (after many locks and unlocks) it get's messier - SUPER+L doesn't lock immediately but gets the desktop in some stuck mode, and I need to click a sort of PAUSE (II) button that appears (usually not there) on the little menu in the top right when I click the small down arrow. This will complete the locking, sometimes, and the laptop goes into some weird sleep mode, where the only option to wake it up is the power button. Then it starts in a split-second. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1824578/+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 1824752] [NEW] package gnome-shell-common 3.30.2-0ubuntu1.18.10.1 failed to install/upgrade: installed gnome-shell-common package post-installation script subprocess returned e
Public bug reported: When trying to update , reinstall , purge or whatever command it does this : E: gnome-shell-common: installed gnome-shell-common package post- installation script subprocess returned error exit status 2 ProblemType: Package DistroRelease: Ubuntu 18.10 Package: gnome-shell-common 3.30.2-0ubuntu1.18.10.1 ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20 Uname: Linux 4.18.0-17-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 AptOrdering: gnome-shell:amd64: Install ubuntu-session:amd64: Install gdm3:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Sun Apr 14 23:07:24 2019 DisplayManager: gdm3 DuplicateSignature: package:gnome-shell-common:3.30.2-0ubuntu1.18.10.1 Setting up gnome-shell-common (3.30.2-0ubuntu1.18.10.1) ... update-alternatives: error: cannot stat file '/etc/alternatives/gdm3.css': Invalid argument dpkg: error processing package gnome-shell-common (--configure): installed gnome-shell-common package post-installation script subprocess returned error exit status 2 ErrorMessage: installed gnome-shell-common package post-installation script subprocess returned error exit status 2 GsettingsChanges: InstallationDate: Installed on 2019-04-13 (1 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.10 PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3 RelatedPackageVersions: dpkg 1.19.0.5ubuntu5 apt 1.7.4 SourcePackage: gnome-shell Title: package gnome-shell-common 3.30.2-0ubuntu1.18.10.1 failed to install/upgrade: installed gnome-shell-common package post-installation script subprocess returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package cosmic -- 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/1824752 Title: package gnome-shell-common 3.30.2-0ubuntu1.18.10.1 failed to install/upgrade: installed gnome-shell-common package post- installation script subprocess returned error exit status 2 Status in gnome-shell package in Ubuntu: New Bug description: When trying to update , reinstall , purge or whatever command it does this : E: gnome-shell-common: installed gnome-shell-common package post- installation script subprocess returned error exit status 2 ProblemType: Package DistroRelease: Ubuntu 18.10 Package: gnome-shell-common 3.30.2-0ubuntu1.18.10.1 ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20 Uname: Linux 4.18.0-17-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 AptOrdering: gnome-shell:amd64: Install ubuntu-session:amd64: Install gdm3:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Sun Apr 14 23:07:24 2019 DisplayManager: gdm3 DuplicateSignature: package:gnome-shell-common:3.30.2-0ubuntu1.18.10.1 Setting up gnome-shell-common (3.30.2-0ubuntu1.18.10.1) ... update-alternatives: error: cannot stat file '/etc/alternatives/gdm3.css': Invalid argument dpkg: error processing package gnome-shell-common (--configure): installed gnome-shell-common package post-installation script subprocess returned error exit status 2 ErrorMessage: installed gnome-shell-common package post-installation script subprocess returned error exit status 2 GsettingsChanges: InstallationDate: Installed on 2019-04-13 (1 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.10 PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3 RelatedPackageVersions: dpkg 1.19.0.5ubuntu5 apt 1.7.4 SourcePackage: gnome-shell Title: package gnome-shell-common 3.30.2-0ubuntu1.18.10.1 failed to install/upgrade: installed gnome-shell-common package post-installation script subprocess returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1824752/+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 1814169] Re: Mutter upsteam bug: cannot overwrite workspaces layout
** Also affects: mutter (Ubuntu Disco)
Importance: Medium
Status: Fix Released
** Also affects: mutter (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Also affects: mutter (Ubuntu Bionic)
Importance: Undecided
Status: New
** Bug watch added: gitlab.gnome.org/GNOME/mutter/issues #270
https://gitlab.gnome.org/GNOME/mutter/issues/270
** Also affects: mutter via
https://gitlab.gnome.org/GNOME/mutter/issues/270
Importance: Unknown
Status: Unknown
--
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/1814169
Title:
Mutter upsteam bug: cannot overwrite workspaces layout
Status in Mutter:
Unknown
Status in mutter package in Ubuntu:
Fix Released
Status in mutter source package in Bionic:
New
Status in mutter source package in Cosmic:
New
Status in mutter source package in Disco:
Fix Released
Bug description:
Running up-to-date Ubuntu Cosmic. Since I am running a version with
manually applied patched from below, I couldn't use the ubuntu-bug
helper.
Bug: When using GNOME extension “Workspace grid” that arranges
workspaces in a grid, one can find that horizontal switch animation is
replaced with a vertical one. This is caused by a bug in mutter
itself, it's acknowledged and fixed in upsteam. Applying the patch for
the current version in Ubuntu solves the issue as well.
GIFs of the issue could be found here: https://medium.com/@hkdb/patch-
gnome-3-30-for-workspace-grid-1ee8b1dd92f9.
Upstream bug: https://gitlab.gnome.org/GNOME/mutter/issues/270.
Upsteam fix:
https://gitlab.gnome.org/rmyorston/mutter/commit/97a3a9b24b3655003467d5fac6bb1ec1c60e
(merged into master 3 months ago).
The patch to fix is, literally, adding 1 meaningful line:
From 86a719cc78149b7db189ff7e5d1f16418d257e9e Mon Sep 17 00:00:00 2001
From: Ron Yorston
Date: Tue, 2 Oct 2018 12:47:05 +0100
Subject: [PATCH] Allow workspace layout to be overridden
meta_workspace_manager_override_workspace_layout is implemented by
calling meta_workspace_manager_update_workspace_layout which
respects the workspace_layout_overridden flag. After the first call
to meta_workspace_manager_override_workspace_layout all subsequent
calls fail silently.
Reset workspace_layout_overridden to FALSE before calling
meta_workspace_manager_update_workspace_layout.
Signed-off-by: Ron Yorston
---
src/core/meta-workspace-manager.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/src/core/meta-workspace-manager.c
b/src/core/meta-workspace-manager.c
index 2670f4938..abc819db0 100644
--- a/src/core/meta-workspace-manager.c
+++ b/src/core/meta-workspace-manager.c
@@ -496,6 +496,8 @@ meta_workspace_manager_override_workspace_layout
(MetaWorkspaceManager *workspac
int
n_rows,
int
n_columns)
{
+ workspace_manager->workspace_layout_overridden = FALSE;
+
meta_workspace_manager_update_workspace_layout (workspace_manager,
starting_corner,
vertical_layout,
--
2.17.1
Hopefully this one is fast to test and apply ;)
To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1814169/+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 1824565] Re: I'm just trying to make my compouter more stable.
** Package changed: xorg (Ubuntu) => 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/1824565 Title: I'm just trying to make my compouter more stable. Status in Ubuntu: Invalid Bug description: My computer keeps changing. Sometimes my add ons on firefox are gone, and I have many programs I do not want on MY computer! I have very little control over my own property. Why can't I remove the programs I do not want, like the games and all the log files and analyzers and remote desktop crap I never downloaded.??? Microshaft does the same thing that is why I switched to linux. Are there any lenox programs that are private? ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-46.49~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 BootLog: [[0;32m OK [0m] Started LSB: Speech Dispatcher. [[0;32m OK [0m] Started LSB: Set the CPU Frequency Scaling governor to "ondemand". CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Fri Apr 12 10:21:46 2019 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GF108M [GeForce GT 540M] [10de:0df4] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Sony Corporation GF108M [GeForce GT 540M] [104d:9089] InstallationDate: Installed on 2019-03-15 (28 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) MachineType: Sony Corporation VPCF22SFX ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic root=UUID=0e73d203-aa1a-40f8-ab34-0abfb2d5d2e8 ro plymouth:debug vesafb.invalid=1 drm.debug=0xe nopat SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/05/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R1190V3 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR1190V3:bd09/05/2011:svnSonyCorporation:pnVPCF22SFX:pvrC609T4GV:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.family: VAIO dmi.product.name: VPCF22SFX dmi.product.version: C609T4GV dmi.sys.vendor: Sony Corporation version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Fri Apr 12 07:42:00 2019 xserver.configfile: default xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.1~16.04.2 xserver.video_driver: nouveau To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1824565/+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 1814169] Re: Mutter upsteam bug: cannot overwrite workspaces layout
Can this be incorporated into the Ubuntu 18.04 version? I manually
patched 3.30.2-1~ubuntu18.10.3, but was overwritten by an update to
3.30.2-1~ubuntu18.10.4.
--
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/1814169
Title:
Mutter upsteam bug: cannot overwrite workspaces layout
Status in mutter package in Ubuntu:
Fix Released
Bug description:
Running up-to-date Ubuntu Cosmic. Since I am running a version with
manually applied patched from below, I couldn't use the ubuntu-bug
helper.
Bug: When using GNOME extension “Workspace grid” that arranges
workspaces in a grid, one can find that horizontal switch animation is
replaced with a vertical one. This is caused by a bug in mutter
itself, it's acknowledged and fixed in upsteam. Applying the patch for
the current version in Ubuntu solves the issue as well.
GIFs of the issue could be found here: https://medium.com/@hkdb/patch-
gnome-3-30-for-workspace-grid-1ee8b1dd92f9.
Upstream bug: https://gitlab.gnome.org/GNOME/mutter/issues/270.
Upsteam fix:
https://gitlab.gnome.org/rmyorston/mutter/commit/97a3a9b24b3655003467d5fac6bb1ec1c60e
(merged into master 3 months ago).
The patch to fix is, literally, adding 1 meaningful line:
From 86a719cc78149b7db189ff7e5d1f16418d257e9e Mon Sep 17 00:00:00 2001
From: Ron Yorston
Date: Tue, 2 Oct 2018 12:47:05 +0100
Subject: [PATCH] Allow workspace layout to be overridden
meta_workspace_manager_override_workspace_layout is implemented by
calling meta_workspace_manager_update_workspace_layout which
respects the workspace_layout_overridden flag. After the first call
to meta_workspace_manager_override_workspace_layout all subsequent
calls fail silently.
Reset workspace_layout_overridden to FALSE before calling
meta_workspace_manager_update_workspace_layout.
Signed-off-by: Ron Yorston
---
src/core/meta-workspace-manager.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/src/core/meta-workspace-manager.c
b/src/core/meta-workspace-manager.c
index 2670f4938..abc819db0 100644
--- a/src/core/meta-workspace-manager.c
+++ b/src/core/meta-workspace-manager.c
@@ -496,6 +496,8 @@ meta_workspace_manager_override_workspace_layout
(MetaWorkspaceManager *workspac
int
n_rows,
int
n_columns)
{
+ workspace_manager->workspace_layout_overridden = FALSE;
+
meta_workspace_manager_update_workspace_layout (workspace_manager,
starting_corner,
vertical_layout,
--
2.17.1
Hopefully this one is fast to test and apply ;)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1814169/+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 1814169] Re: Mutter upsteam bug: cannot overwrite workspaces layout
Correction, I am running Ubuntu 18.10, not 18.04.
--
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/1814169
Title:
Mutter upsteam bug: cannot overwrite workspaces layout
Status in mutter package in Ubuntu:
Fix Released
Bug description:
Running up-to-date Ubuntu Cosmic. Since I am running a version with
manually applied patched from below, I couldn't use the ubuntu-bug
helper.
Bug: When using GNOME extension “Workspace grid” that arranges
workspaces in a grid, one can find that horizontal switch animation is
replaced with a vertical one. This is caused by a bug in mutter
itself, it's acknowledged and fixed in upsteam. Applying the patch for
the current version in Ubuntu solves the issue as well.
GIFs of the issue could be found here: https://medium.com/@hkdb/patch-
gnome-3-30-for-workspace-grid-1ee8b1dd92f9.
Upstream bug: https://gitlab.gnome.org/GNOME/mutter/issues/270.
Upsteam fix:
https://gitlab.gnome.org/rmyorston/mutter/commit/97a3a9b24b3655003467d5fac6bb1ec1c60e
(merged into master 3 months ago).
The patch to fix is, literally, adding 1 meaningful line:
From 86a719cc78149b7db189ff7e5d1f16418d257e9e Mon Sep 17 00:00:00 2001
From: Ron Yorston
Date: Tue, 2 Oct 2018 12:47:05 +0100
Subject: [PATCH] Allow workspace layout to be overridden
meta_workspace_manager_override_workspace_layout is implemented by
calling meta_workspace_manager_update_workspace_layout which
respects the workspace_layout_overridden flag. After the first call
to meta_workspace_manager_override_workspace_layout all subsequent
calls fail silently.
Reset workspace_layout_overridden to FALSE before calling
meta_workspace_manager_update_workspace_layout.
Signed-off-by: Ron Yorston
---
src/core/meta-workspace-manager.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/src/core/meta-workspace-manager.c
b/src/core/meta-workspace-manager.c
index 2670f4938..abc819db0 100644
--- a/src/core/meta-workspace-manager.c
+++ b/src/core/meta-workspace-manager.c
@@ -496,6 +496,8 @@ meta_workspace_manager_override_workspace_layout
(MetaWorkspaceManager *workspac
int
n_rows,
int
n_columns)
{
+ workspace_manager->workspace_layout_overridden = FALSE;
+
meta_workspace_manager_update_workspace_layout (workspace_manager,
starting_corner,
vertical_layout,
--
2.17.1
Hopefully this one is fast to test and apply ;)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1814169/+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 1726160] Re: On login, display rotates to wrong orientation [HP laptops]
** Summary changed: - On login, display rotates to wrong orientation [HP Pavilion] + On login, display rotates to wrong orientation [HP laptops] -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to iio-sensor-proxy in Ubuntu. https://bugs.launchpad.net/bugs/1726160 Title: On login, display rotates to wrong orientation [HP laptops] Status in IIO Sensor Proxy: Fix Released Status in systemd: Unknown Status in iio-sensor-proxy package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in iio-sensor-proxy source package in Bionic: Confirmed Status in systemd source package in Bionic: Triaged Status in iio-sensor-proxy source package in Cosmic: Confirmed Status in systemd source package in Cosmic: Triaged Status in iio-sensor-proxy source package in Disco: Invalid Status in systemd source package in Disco: Fix Released Bug description: I'm using a laptop, and on 17.04 the display always showed correctly, but after upgrading to 17.10, when I log in the display rotates to the right (portrait), and I have to open a terminal and run 'xrandr -o 1' to get it back to the correct (landscape) orientation. In previous versions 'xrandr -o 0' was landscape, and '1' was portrait the other way. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.104 Thu Sep 14 17:13:13 PDT 2017 GCC version: gcc version 7.2.0 (Ubuntu 7.2.0-8ubuntu3) .tmp.unity_support_test.0: ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Oct 22 15:15:08 2017 DistUpgraded: 2017-10-22 14:17:00,381 DEBUG icon theme changed, re-reading DistroCodename: artful DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.10.0-37-generic, x86_64: installed bbswitch, 0.8, 4.13.0-16-generic, x86_64: installed nvidia-340, 340.104, 4.10.0-37-generic, x86_64: installed nvidia-340, 340.104, 4.13.0-16-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GT216M [GeForce GT 230M] [10de:0a28] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company GT216M [GeForce GT 230M] [103c:363c] InstallationDate: Installed on 2017-01-11 (284 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) LightdmDisplayLog: (II) Server terminated successfully (0). Closing log file. MachineType: Hewlett-Packard HP Pavilion dv7 Notebook PC ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to artful on 2017-10-22 (0 days ago) dmi.bios.date: 10/05/2010 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.1D dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 363C dmi.board.vendor: Hewlett-Packard dmi.board.version: 32.25 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.1D:bd10/05/2010:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvr039D222412102:rvnHewlett-Packard:rn363C:rvr32.25:cvnHewlett-Packard:ct10:cvrN/A: dmi.product.family: 103C_5335KV dmi.product.name: HP Pavilion dv7 Notebook PC dmi.product.version: 039D222412102 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1 version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/iio-sensor-proxy/+bug/1726160/+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 1824541] Re: screen flips itself
*** This bug is a duplicate of bug 1726160 *** https://bugs.launchpad.net/bugs/1726160 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1726160, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1726160 On login, display rotates to wrong orientation [HP Pavilion] -- 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/1824541 Title: screen flips itself Status in mutter package in Ubuntu: New Bug description: Hi developers,I'm facing a problem of inverted or flipped screen. At first it flipped to 180 degree and after researching i got a solution but this solution is not permanent and now it flips to 90 degree. I even tried orientation applet locked it too but it does not matter screen still flips on its own. I want you to know that my laptop stays on table all the time, no movement at all but screen flips itself . It also happens even when I'm watching videos. I even asked about this on ask ubuntu forums and someone gave me idea of letting you guys know because developers know better. So in short, I constantly need to use terminal command to switch it back to normal and the command I use I think I should mention it too so here it is: < xrandr -o normal > i'm using Ubuntu Budgie 18.04.2 LTS 64-bit Hp laptop Intel processor Core i5 3rd generation ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: mutter (not installed) ProcVersionSignature: Ubuntu 4.18.0-17.18~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-17-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Fri Apr 12 19:08:23 2019 InstallationDate: Installed on 2019-04-08 (3 days ago) InstallationMedia: Ubuntu-Budgie 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) 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/1824541/+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 1726160] Re: On login, display rotates to wrong orientation [HP Pavilion]
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: iio-sensor-proxy (Ubuntu Bionic) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to iio-sensor-proxy in Ubuntu. https://bugs.launchpad.net/bugs/1726160 Title: On login, display rotates to wrong orientation [HP laptops] Status in IIO Sensor Proxy: Fix Released Status in systemd: Unknown Status in iio-sensor-proxy package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in iio-sensor-proxy source package in Bionic: Confirmed Status in systemd source package in Bionic: Triaged Status in iio-sensor-proxy source package in Cosmic: Confirmed Status in systemd source package in Cosmic: Triaged Status in iio-sensor-proxy source package in Disco: Invalid Status in systemd source package in Disco: Fix Released Bug description: I'm using a laptop, and on 17.04 the display always showed correctly, but after upgrading to 17.10, when I log in the display rotates to the right (portrait), and I have to open a terminal and run 'xrandr -o 1' to get it back to the correct (landscape) orientation. In previous versions 'xrandr -o 0' was landscape, and '1' was portrait the other way. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.104 Thu Sep 14 17:13:13 PDT 2017 GCC version: gcc version 7.2.0 (Ubuntu 7.2.0-8ubuntu3) .tmp.unity_support_test.0: ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Oct 22 15:15:08 2017 DistUpgraded: 2017-10-22 14:17:00,381 DEBUG icon theme changed, re-reading DistroCodename: artful DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.10.0-37-generic, x86_64: installed bbswitch, 0.8, 4.13.0-16-generic, x86_64: installed nvidia-340, 340.104, 4.10.0-37-generic, x86_64: installed nvidia-340, 340.104, 4.13.0-16-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GT216M [GeForce GT 230M] [10de:0a28] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company GT216M [GeForce GT 230M] [103c:363c] InstallationDate: Installed on 2017-01-11 (284 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) LightdmDisplayLog: (II) Server terminated successfully (0). Closing log file. MachineType: Hewlett-Packard HP Pavilion dv7 Notebook PC ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to artful on 2017-10-22 (0 days ago) dmi.bios.date: 10/05/2010 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.1D dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 363C dmi.board.vendor: Hewlett-Packard dmi.board.version: 32.25 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.1D:bd10/05/2010:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvr039D222412102:rvnHewlett-Packard:rn363C:rvr32.25:cvnHewlett-Packard:ct10:cvrN/A: dmi.product.family: 103C_5335KV dmi.product.name: HP Pavilion dv7 Notebook PC dmi.product.version: 039D222412102 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1 version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/iio-sensor-proxy/+bug/1726160/+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 1726160] Re: On login, display rotates to wrong orientation [HP Pavilion]
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: iio-sensor-proxy (Ubuntu Cosmic) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to iio-sensor-proxy in Ubuntu. https://bugs.launchpad.net/bugs/1726160 Title: On login, display rotates to wrong orientation [HP laptops] Status in IIO Sensor Proxy: Fix Released Status in systemd: Unknown Status in iio-sensor-proxy package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in iio-sensor-proxy source package in Bionic: Confirmed Status in systemd source package in Bionic: Triaged Status in iio-sensor-proxy source package in Cosmic: Confirmed Status in systemd source package in Cosmic: Triaged Status in iio-sensor-proxy source package in Disco: Invalid Status in systemd source package in Disco: Fix Released Bug description: I'm using a laptop, and on 17.04 the display always showed correctly, but after upgrading to 17.10, when I log in the display rotates to the right (portrait), and I have to open a terminal and run 'xrandr -o 1' to get it back to the correct (landscape) orientation. In previous versions 'xrandr -o 0' was landscape, and '1' was portrait the other way. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.104 Thu Sep 14 17:13:13 PDT 2017 GCC version: gcc version 7.2.0 (Ubuntu 7.2.0-8ubuntu3) .tmp.unity_support_test.0: ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Oct 22 15:15:08 2017 DistUpgraded: 2017-10-22 14:17:00,381 DEBUG icon theme changed, re-reading DistroCodename: artful DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.10.0-37-generic, x86_64: installed bbswitch, 0.8, 4.13.0-16-generic, x86_64: installed nvidia-340, 340.104, 4.10.0-37-generic, x86_64: installed nvidia-340, 340.104, 4.13.0-16-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GT216M [GeForce GT 230M] [10de:0a28] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company GT216M [GeForce GT 230M] [103c:363c] InstallationDate: Installed on 2017-01-11 (284 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) LightdmDisplayLog: (II) Server terminated successfully (0). Closing log file. MachineType: Hewlett-Packard HP Pavilion dv7 Notebook PC ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to artful on 2017-10-22 (0 days ago) dmi.bios.date: 10/05/2010 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.1D dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 363C dmi.board.vendor: Hewlett-Packard dmi.board.version: 32.25 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.1D:bd10/05/2010:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvr039D222412102:rvnHewlett-Packard:rn363C:rvr32.25:cvnHewlett-Packard:ct10:cvrN/A: dmi.product.family: 103C_5335KV dmi.product.name: HP Pavilion dv7 Notebook PC dmi.product.version: 039D222412102 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1 version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/iio-sensor-proxy/+bug/1726160/+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 1823550] Re: GtkSourceView (gedit - Text Editor and others) wrongly has monospaced font in dropdown (context) menu
** Summary changed: - GtkSourceView wrongly has monospaced font in dropdown (context) menu + GtkSourceView (gedit - Text Editor and others) wrongly has monospaced font in dropdown (context) menu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtksourceview3 in Ubuntu. https://bugs.launchpad.net/bugs/1823550 Title: GtkSourceView (gedit - Text Editor and others) wrongly has monospaced font in dropdown (context) menu Status in GtkSourceView: Fix Released Status in gtk+3.0 package in Ubuntu: Invalid Status in gtksourceview3 package in Ubuntu: Invalid Status in mate-themes package in Ubuntu: Confirmed Status in pluma package in Ubuntu: Invalid Status in ubuntu-themes package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Have Ubuntu 17.04 or later installed 2. Open any application with GtkSourceView component - such as Pluma, Gedit, Giggle, Gitg, gnome-builder and maybe others (see complete list with `apt-cache rdepends libgtksourceview-3.0-1`) 3. Click right mouse button on text zone Expected result: * dropdown menu has normal font as all other interface elements Actual result: * dropdwon menu wrongly has monospaced font Notes: * first seen in 17.04, but persists in 17.10, 18.04 LTS, 18.10, 19.04 releases. * seems to be caused by GTK3 library ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: pluma 1.18.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-42.46-generic 4.10.17 Uname: Linux 4.10.0-42-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.10 Architecture: amd64 CurrentDesktop: MATE Date: Sun Apr 7 20:13:24 2019 InstallationDate: Installed on 2018-08-07 (243 days ago) InstallationMedia: Ubuntu-MATE 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: pluma UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gtksourceview/+bug/1823550/+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 1822846] Re: Icon disappears from favorites in gnome-shell 3.32 (upstream dock, not the ubuntu-dock)
** Summary changed: - Icon disappears from favorites in gnome-shell 3.32 + Icon disappears from favorites in gnome-shell 3.32 (upstream dock, not the ubuntu-dock) -- 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/1822846 Title: Icon disappears from favorites in gnome-shell 3.32 (upstream dock, not the ubuntu-dock) Status in GNOME Shell: Fix Released Status in gnome-shell package in Ubuntu: Triaged Bug description: From time to time, my chrome icon disappears in gnome shell 3.32, leaving only the "open window indicator" below it. It's the first of my icons, and this is running a vanilla gnome session. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Apr 2 17:44:52 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-03-14 (383 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313) SourcePackage: gnome-shell UpgradeStatus: Upgraded to disco on 2018-11-20 (133 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1822846/+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 1726160] Re: On login, display rotates to wrong orientation [HP Pavilion]
It looks like the fix went into systemd version 240, so it should be fixed in Ubuntu 19.04 now if you update your system... commit 0d1a2be93e16aa03026f1c36e81951097e8dad2c Author: Bastien Nocera Date: Mon Oct 29 13:31:39 2018 + hwdb: Apply the same quirk to all the lis3lv02d devices HP laptops and desktop containing the lis3lv02d device (as supported by the drivers/platform/x86/hp_accel.c driver) are supposed to output their values according to their "standard" orientation, one that corresponds to "can play neverball". For all those devices, we need to convert that "neverball" orientation to a "Windows 8" orientation. We will not accept quirks for HP machines that use the lis3lv02d device, they should go in the hp_accel.c driver instead. Closes: #5160 ** Changed in: linux (Ubuntu) Status: Confirmed => Won't Fix ** Changed in: systemd (Ubuntu) Status: Confirmed => Fix Released ** Also affects: linux (Ubuntu Disco) Importance: Undecided Status: Won't Fix ** Also affects: systemd (Ubuntu Disco) Importance: High Status: Fix Released ** Also affects: iio-sensor-proxy (Ubuntu Disco) Importance: High Status: Invalid ** Also affects: linux (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: iio-sensor-proxy (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: iio-sensor-proxy (Ubuntu Bionic) Importance: Undecided Status: New ** No longer affects: linux (Ubuntu) ** No longer affects: linux (Ubuntu Bionic) ** No longer affects: linux (Ubuntu Cosmic) ** No longer affects: linux (Ubuntu Disco) ** Changed in: systemd (Ubuntu Cosmic) Importance: Undecided => High ** Changed in: systemd (Ubuntu Cosmic) Status: New => Triaged ** Changed in: systemd (Ubuntu Bionic) Importance: Undecided => High ** Changed in: systemd (Ubuntu Bionic) Status: New => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to iio-sensor-proxy in Ubuntu. https://bugs.launchpad.net/bugs/1726160 Title: On login, display rotates to wrong orientation [HP Pavilion] Status in IIO Sensor Proxy: Fix Released Status in systemd: Unknown Status in iio-sensor-proxy package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in iio-sensor-proxy source package in Bionic: New Status in systemd source package in Bionic: Triaged Status in iio-sensor-proxy source package in Cosmic: New Status in systemd source package in Cosmic: Triaged Status in iio-sensor-proxy source package in Disco: Invalid Status in systemd source package in Disco: Fix Released Bug description: I'm using a laptop, and on 17.04 the display always showed correctly, but after upgrading to 17.10, when I log in the display rotates to the right (portrait), and I have to open a terminal and run 'xrandr -o 1' to get it back to the correct (landscape) orientation. In previous versions 'xrandr -o 0' was landscape, and '1' was portrait the other way. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.104 Thu Sep 14 17:13:13 PDT 2017 GCC version: gcc version 7.2.0 (Ubuntu 7.2.0-8ubuntu3) .tmp.unity_support_test.0: ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Oct 22 15:15:08 2017 DistUpgraded: 2017-10-22 14:17:00,381 DEBUG icon theme changed, re-reading DistroCodename: artful DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.10.0-37-generic, x86_64: installed bbswitch, 0.8, 4.13.0-16-generic, x86_64: installed nvidia-340, 340.104, 4.10.0-37-generic, x86_64: installed nvidia-340, 340.104, 4.13.0-16-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GT216M [GeForce GT 230M] [10de:0a28] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company GT216M [GeForce GT 230M] [103c:363c] InstallationDate: Installed on 2017-01-11 (284 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) LightdmDisplayLog: (II) Server terminated successfully (0). Closing log file. MachineType: Hewlett-Packard HP Pavilion dv7 Notebook PC
[Desktop-packages] [Bug 1726160] Re: On login, display rotates to wrong orientation [HP Pavilion]
** Bug watch added: github.com/systemd/systemd/issues #5160 https://github.com/systemd/systemd/issues/5160 ** Changed in: systemd Status: New => Unknown ** Changed in: systemd Remote watch: github.com/systemd/systemd/issues #7151 => github.com/systemd/systemd/issues #5160 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to iio-sensor-proxy in Ubuntu. https://bugs.launchpad.net/bugs/1726160 Title: On login, display rotates to wrong orientation [HP Pavilion] Status in IIO Sensor Proxy: Fix Released Status in systemd: Unknown Status in iio-sensor-proxy package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: I'm using a laptop, and on 17.04 the display always showed correctly, but after upgrading to 17.10, when I log in the display rotates to the right (portrait), and I have to open a terminal and run 'xrandr -o 1' to get it back to the correct (landscape) orientation. In previous versions 'xrandr -o 0' was landscape, and '1' was portrait the other way. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.104 Thu Sep 14 17:13:13 PDT 2017 GCC version: gcc version 7.2.0 (Ubuntu 7.2.0-8ubuntu3) .tmp.unity_support_test.0: ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Oct 22 15:15:08 2017 DistUpgraded: 2017-10-22 14:17:00,381 DEBUG icon theme changed, re-reading DistroCodename: artful DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.10.0-37-generic, x86_64: installed bbswitch, 0.8, 4.13.0-16-generic, x86_64: installed nvidia-340, 340.104, 4.10.0-37-generic, x86_64: installed nvidia-340, 340.104, 4.13.0-16-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GT216M [GeForce GT 230M] [10de:0a28] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company GT216M [GeForce GT 230M] [103c:363c] InstallationDate: Installed on 2017-01-11 (284 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) LightdmDisplayLog: (II) Server terminated successfully (0). Closing log file. MachineType: Hewlett-Packard HP Pavilion dv7 Notebook PC ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to artful on 2017-10-22 (0 days ago) dmi.bios.date: 10/05/2010 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.1D dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 363C dmi.board.vendor: Hewlett-Packard dmi.board.version: 32.25 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.1D:bd10/05/2010:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvr039D222412102:rvnHewlett-Packard:rn363C:rvr32.25:cvnHewlett-Packard:ct10:cvrN/A: dmi.product.family: 103C_5335KV dmi.product.name: HP Pavilion dv7 Notebook PC dmi.product.version: 039D222412102 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1 version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/iio-sensor-proxy/+bug/1726160/+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 1811900] Re: SRU 3.28 latest git to bionic
** Also affects: mutter (Ubuntu Disco) Importance: Medium Assignee: Marco Trevisan (Treviño) (3v1n0) Status: Fix Released ** Also affects: gnome-shell (Ubuntu Disco) Importance: Medium Assignee: Marco Trevisan (Treviño) (3v1n0) Status: Fix Released ** Also affects: mutter (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: gnome-shell (Ubuntu Cosmic) Importance: Undecided Status: New ** Changed in: gnome-shell (Ubuntu Disco) Status: Fix Released => Invalid ** Changed in: gnome-shell (Ubuntu Cosmic) Status: New => Invalid ** Changed in: mutter (Ubuntu Cosmic) Status: New => Invalid ** Changed in: mutter (Ubuntu Disco) Status: Fix Released => Invalid ** No longer affects: gnome-shell (Ubuntu Cosmic) ** No longer affects: gnome-shell (Ubuntu Disco) ** No longer affects: mutter (Ubuntu Cosmic) ** No longer affects: mutter (Ubuntu Disco) -- 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/1811900 Title: SRU 3.28 latest git to bionic Status in gnome-shell package in Ubuntu: Invalid Status in mutter package in Ubuntu: Invalid Status in gnome-shell source package in Bionic: Fix Committed Status in mutter source package in Bionic: Fix Committed Bug description: [ Description ] 3.28 gnome git branch has various upstream approved fixes for many months now, but no release has been done yet, thus we're releasing a git snapshot of the latest approved fixes. [ QA ] Run Ubuntu session, expect the shell to work normally with various setups https://wiki.ubuntu.com/StableReleaseUpdates/GNOME [ Regresison potential ] Many patches we were including already have been included in upstream git now, various optimizations to clutter actors could cause drawing issues. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1811900/+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 1821494] Re: Sennheiser GSX 1000/1200: only one subdevice exposed by Pulse & incorrect channel mapping
Thanks Ben.
Could you please propose that fix to the PulseAudio developers at
https://gitlab.freedesktop.org/groups/pulseaudio/-/merge_requests
?
** Changed in: pulseaudio (Ubuntu)
Status: Confirmed => Triaged
** Changed in: pulseaudio (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1821494
Title:
Sennheiser GSX 1000/1200: only one subdevice exposed by Pulse &
incorrect channel mapping
Status in pulseaudio package in Ubuntu:
Triaged
Bug description:
Similar to the Steelseries Arctis headphones, these sound "cards"
present as two output devices, one intended for voice chat and one for
everything else. As a result they also need a special profile.
But there's another complication. They also have hardware HRTF that
requires no special driver logic; instead, the "everything else"
output pretends to be 7.1, and simply applies the HRTF to the streams
sent by the host. However, the channel mappings picked up by ALSA are
wrong -- the rear speakers and center/LFE are swapped.
I know, technically this is two bugs, but they have the same fix which
is impractical to separate. I'm attaching a "sennheiser-gsx.conf"
based on the Arctis 7 profile that both corrects the channel mapping
and exposes both output subdevices. A simple udev rule seals the deal:
ATTRS{idVendor}=="1395", ATTRS{idProduct}=="005e",
ENV{PULSE_PROFILE_SET}="sennheiser-gsx.conf"
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: pulseaudio 1:11.1-1ubuntu7.2
ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20
Uname: Linux 4.18.0-16-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC3: roothorick 7548 F pulseaudio
/dev/snd/controlC2: roothorick 7548 F pulseaudio
/dev/snd/controlC0: roothorick 7548 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Sat Mar 23 23:09:21 2019
InstallationDate: Installed on 2018-09-12 (193 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64
(20180725)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: pulseaudio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/07/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2004
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: H87M-E
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr2004:bd08/07/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH87M-E:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.family: ASUS MB
dmi.product.name: All Series
dmi.product.sku: All
dmi.product.version: System Version
dmi.sys.vendor: ASUS
modified.conffile..etc.pulse.daemon.conf: [modified]
modified.conffile..etc.pulse.default.pa: [modified]
mtime.conffile..etc.pulse.daemon.conf: 2019-03-23T20:51:33.488207
mtime.conffile..etc.pulse.default.pa: 2019-03-23T23:03:49.029912
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1821494/+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 1724350] Re: USB Sound not working after upgrade to 17.10
Thank you for reporting this bug to Ubuntu. Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: alsa-driver (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1724350 Title: USB Sound not working after upgrade to 17.10 Status in alsa-driver package in Ubuntu: Won't Fix Bug description: I have a sennheiser USB audio headset connected. In 17.04 it was working fine. Now after upgrade to 17.10 no sound. Device is shown but no sound. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1724350/+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 1820423] Re: monitors.xml is not parsed or applied correctly during login after reboot or shutdown
** Project changed: gnome-shell => mutter -- 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/1820423 Title: monitors.xml is not parsed or applied correctly during login after reboot or shutdown Status in gdm: New Status in Mutter: New Status in gdm3 package in Ubuntu: Triaged Status in mutter package in Ubuntu: Incomplete Bug description: WORKAROUND Replace gdm3 with slick-greeter + lightdm-settings + gnome-screensaver + numlockx(optionally) TL;DR Correct positioning and working of multiple displays until reboot or shutdown and then subsequent login from gdm3. HDMI monitor(projector) goes blank and the VGA monitor only shows 'Secondary' monitor screen without any user visible controls or windows as they are all being painted to the now blanked 'Primary' HDMI connected display. REPRODUCTION After a clean install of Ubuntu 18.10, connecting a FHD(1920x1080) LED monitor to the VGA port of a DELL Optiplex 390 desktop tower, connecting a wireless HDMI Tx/Rx(LKV HDbitT-4K) to the HDMI port with a FHD projector and then configuring the logical monitor layout in the "Displays" settings dialog, I can successfully create and use a multi monitor setup in my current session. However, after a reboot or power cycle of the computer and a successful login from GDM(gdm3), the HDMI goes dark(blank?) and the VGA monitor shows as 'Secondary' monitor even though I set it as 'Primary' in the "Displays" dialog. The monitors.xml file, attached, shows the correct layout and survives the reboot without alteration. I am unable to see anything on the 'Primary' display, which has incorrectly been given to the HDMI projector. Unseating the HDMI cable does not restore the VGA to 'Primary' display automatically and I must reboot the computer while leaving the HDMI unplugged in order to restore my ability to see the 'Primary' display on the VGA connection. Replacing GDM(gdm3) with LightDM(slick-greeter) fixes the issue and is repeatedly provable through multiple reboots or changes to the logical layout of the screens in the 'Displays' settings of gnome-control- center. ERRORS(syslog) "Failed to get current display configuration state: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.gnome.Mutter.DisplayConfig" does not exist" gnome-shell[3007]: JS ERROR: Exception in callback for signal: loaded: TypeError: monitor is null#012_prepareStartupAnimation@resource:///org/gnome/shell/ui/layout.js:653:17#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012_loadBackground/signalId<@resource:///org/gnome/shell/ui/layout.js:608:13#012_emit@resource:///org/gnome/gjs/modules/signals.js:128:27#012_init/id<@resource:///org/gnome/shell/ui/background.js:512:17 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gdm3 3.30.1-1ubuntu5.1 ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20 Uname: Linux 4.18.0-16-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Mar 16 13:50:52 2019 InstallationDate: Installed on 2019-03-07 (8 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1820423/+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 1822846] Re: Icon disappears from favorites in gnome-shell 3.32
** Tags added: fixed-in-3.32.1 fixed-upstream -- 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/1822846 Title: Icon disappears from favorites in gnome-shell 3.32 Status in GNOME Shell: Fix Released Status in gnome-shell package in Ubuntu: Triaged Bug description: From time to time, my chrome icon disappears in gnome shell 3.32, leaving only the "open window indicator" below it. It's the first of my icons, and this is running a vanilla gnome session. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Apr 2 17:44:52 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-03-14 (383 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313) SourcePackage: gnome-shell UpgradeStatus: Upgraded to disco on 2018-11-20 (133 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1822846/+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 1824743] Re: Fonts look bad after scaling display in Kubuntu Disco
Also, the fonts do look ok at 1.0 scaling, but I can't really read them that small. They appear to be similarly broken on any factor above 1.0. -- 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/1824743 Title: Fonts look bad after scaling display in Kubuntu Disco Status in libreoffice package in Ubuntu: New Bug description: Hi, I'm trying out the kubuntu Disco beta. I have 4k displays, so I went into the KDE System Settings and changed my screen scaling value to 1.4. After doing this, all of the fonts in all of the LibreOffice applications looked really bad, to the point of being nearly unreadable. I eventually removed libreoffice-kde5 and libreoffice-qt5 and confirmed that the fonts were fixed, but that has obvious negative consequences. Installing libreoffice-gtk3 helped, and the fonts still look ok. This doesn't appear to happen in Kubuntu 18.10. Not sure what else to do to help diagnose this but I'm glad to have a look. Nate To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1824743/+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 1824743] [NEW] Fonts look bad after scaling display in Kubuntu Disco
Public bug reported: Hi, I'm trying out the kubuntu Disco beta. I have 4k displays, so I went into the KDE System Settings and changed my screen scaling value to 1.4. After doing this, all of the fonts in all of the LibreOffice applications looked really bad, to the point of being nearly unreadable. I eventually removed libreoffice-kde5 and libreoffice-qt5 and confirmed that the fonts were fixed, but that has obvious negative consequences. Installing libreoffice-gtk3 helped, and the fonts still look ok. This doesn't appear to happen in Kubuntu 18.10. Not sure what else to do to help diagnose this but I'm glad to have a look. Nate ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Attachment added: "screenshot.png" https://bugs.launchpad.net/bugs/1824743/+attachment/5255795/+files/screenshot.png -- 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/1824743 Title: Fonts look bad after scaling display in Kubuntu Disco Status in libreoffice package in Ubuntu: New Bug description: Hi, I'm trying out the kubuntu Disco beta. I have 4k displays, so I went into the KDE System Settings and changed my screen scaling value to 1.4. After doing this, all of the fonts in all of the LibreOffice applications looked really bad, to the point of being nearly unreadable. I eventually removed libreoffice-kde5 and libreoffice-qt5 and confirmed that the fonts were fixed, but that has obvious negative consequences. Installing libreoffice-gtk3 helped, and the fonts still look ok. This doesn't appear to happen in Kubuntu 18.10. Not sure what else to do to help diagnose this but I'm glad to have a look. Nate To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1824743/+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 1810316] Re: gnome-control-center SIGABRT when n-m is not working (G_IS_OBJECT (object))
** Changed in: gnome-control-center Status: Unknown => New -- 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/1810316 Title: gnome-control-center SIGABRT when n-m is not working (G_IS_OBJECT (object)) Status in gnome-control-center: New Status in NetworkManager: New Status in gnome-control-center package in Ubuntu: Triaged Status in network-manager package in Ubuntu: Incomplete Bug description: https://gitlab.gnome.org/GNOME/gnome-control-center/issues/342 https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/143 --- [Impact] gnome-control-center goes crash when I try to work with two USB WiFi cards. [Test Case] I have a wireless card connected and then I connect 'another' wireless card and the network module starts to malfunction in the gnome-control-center. [Potential Regression] I think it's not a potential regression. Original Description * I was trying to open wifi settings * I'm connecting 2 WiFi USB in ubuntu disk ProblemType: Crash DistroRelease: Ubuntu 18.10 Package: gnome-control-center 1:3.30.2-1ubuntu0.18.10.1 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Wed Jan 2 09:54:42 2019 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2018-09-27 (97 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: gnome-control-center wifi ProcEnviron: LC_COLLATE=C PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: gnome-control-center StacktraceTop: () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 cc_object_storage_add_object () cc_wifi_panel_static_init_func () cc_panel_loader_fill_model () Title: gnome-control-center crashed with SIGABRT UpgradeStatus: Upgraded to cosmic on 2018-11-08 (54 days ago) UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo vboxusers wireshark modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2018-10-04T06:36:50.792292 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1810316/+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 1824739] [NEW] Xorg freeze
Public bug reported: The computer is not able to resume after suspend. The screen brightness is not able to be adjusted ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 Uname: Linux 5.0.0-05-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Apr 15 06:18:34 2019 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GpuHangFrequency: Several times a week GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: I don't know GraphicsCard: Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:15e0] Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Mobile] [1043:15e0] InstallationDate: Installed on 2018-06-27 (291 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:b718 Realtek Semiconductor Corp. Bus 001 Device 002: ID 13d3:5654 IMC Networks Bus 001 Device 004: ID 0b05:1854 ASUSTek Computer, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. GL553VD ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-05-generic root=UUID=efd91b16-1bc9-46b5-805f-5994b58f82f6 ro nouveau.modeset=0 nouveau.blacklist=1 quiet splash nomodeset acpi_backlight=vendor nouveau.modeset=0 nouveau.blacklist=1 vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/02/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GL553VD.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GL553VD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGL553VD.306:bd01/02/2018:svnASUSTeKCOMPUTERINC.:pnGL553VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL553VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: GL dmi.product.name: GL553VD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.10.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.10.2 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic freeze possible-manual-nvidia-install 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/1824739 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: The computer is not able to resume after suspend. The screen brightness is not able to be adjusted ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 Uname: Linux 5.0.0-05-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Apr 15 06:18:34 2019 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GpuHangFrequency: Several times a week GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: I don't know GraphicsCard: Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:15e0] Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Mobile] [1043:15e0] InstallationDate: Installed on 2018-06-27 (291 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:b718 Realtek Semiconductor Corp. Bus 001 Device 002: ID 13d3:5654 IMC Networks Bus 001 Device 004: ID 0b05:1854 ASUSTek Computer, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. GL553VD ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-05-generic root=UUID=efd91b16-1bc9-46b5-805f-5994b58f82f6 ro nouveau.modeset=0
[Desktop-packages] [Bug 1824641] Re: Blank screen after booting 4.4.0-145
Sorry I cannot collect log files for the kernel giving the bug. If I can collect any useful information using the kernel that does work, please let me know ** Changed in: mutter (Ubuntu) Status: Incomplete => Invalid -- 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/1824641 Title: Blank screen after booting 4.4.0-145 Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Invalid Bug description: Having run update on my i386 Asus Eee PC with Intel Atom N550 Dual core CPU running 16.04.06 LTS, it installed linux 4.4.0-145. If I boot this kernel everything is blank. Just a black screen. If I change to a terminal using Ctrl Alt F4 it is still a black screen but I can carefully type in my user name and password and then the shutdown command and it shuts down Using Advanced options in grub neither the upstart or the recovery option work. The screen is still black. The recovery option does, however, display the boot sequence before going black. I can boot the previous kernel 4.4.0-143 and all is OK. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824641/+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 1810316] Re: gnome-control-center SIGABRT when n-m is not working (G_IS_OBJECT (object))
https://gitlab.gnome.org/GNOME/gnome-control-center/issues/342 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/issues #342 https://gitlab.gnome.org/GNOME/gnome-control-center/issues/342 ** Description changed: - https://gitlab.gnome.org/GNOME/gnome-control-center/issues/432 + https://gitlab.gnome.org/GNOME/gnome-control-center/issues/342 https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/143 --- [Impact] gnome-control-center goes crash when I try to work with two USB WiFi cards. [Test Case] I have a wireless card connected and then I connect 'another' wireless card and the network module starts to malfunction in the gnome-control-center. [Potential Regression] I think it's not a potential regression. Original Description * I was trying to open wifi settings * I'm connecting 2 WiFi USB in ubuntu disk ProblemType: Crash DistroRelease: Ubuntu 18.10 Package: gnome-control-center 1:3.30.2-1ubuntu0.18.10.1 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Wed Jan 2 09:54:42 2019 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2018-09-27 (97 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: gnome-control-center wifi ProcEnviron: LC_COLLATE=C PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: gnome-control-center StacktraceTop: () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 cc_object_storage_add_object () cc_wifi_panel_static_init_func () cc_panel_loader_fill_model () Title: gnome-control-center crashed with SIGABRT UpgradeStatus: Upgraded to cosmic on 2018-11-08 (54 days ago) UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo vboxusers wireshark modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2018-10-04T06:36:50.792292 ** No longer affects: gnome-control-center ** Also affects: gnome-control-center via https://gitlab.gnome.org/GNOME/gnome-control-center/issues/342 Importance: Unknown Status: Unknown -- 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/1810316 Title: gnome-control-center SIGABRT when n-m is not working (G_IS_OBJECT (object)) Status in gnome-control-center: Unknown Status in NetworkManager: New Status in gnome-control-center package in Ubuntu: Triaged Status in network-manager package in Ubuntu: Incomplete Bug description: https://gitlab.gnome.org/GNOME/gnome-control-center/issues/342 https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/143 --- [Impact] gnome-control-center goes crash when I try to work with two USB WiFi cards. [Test Case] I have a wireless card connected and then I connect 'another' wireless card and the network module starts to malfunction in the gnome-control-center. [Potential Regression] I think it's not a potential regression. Original Description * I was trying to open wifi settings * I'm connecting 2 WiFi USB in ubuntu disk ProblemType: Crash DistroRelease: Ubuntu 18.10 Package: gnome-control-center 1:3.30.2-1ubuntu0.18.10.1 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Wed Jan 2 09:54:42 2019 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2018-09-27 (97 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: gnome-control-center wifi ProcEnviron: LC_COLLATE=C PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: gnome-control-center StacktraceTop: () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 cc_object_storage_add_object () cc_wifi_panel_static_init_func () cc_panel_loader_fill_model () Title: gnome-control-center crashed with SIGABRT UpgradeStatus: Upgraded to cosmic on 2018-11-08 (54 days ago) UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo vboxusers wireshark modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2018-10-04T06:36:50.792292 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1810316/+subscriptions -- Mailing list:
[Desktop-packages] [Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding
I wonder if my problem may be related to this error in the chrome://gpu log: - [20257:20257:0414/133034.932196:ERROR:gl_implementation.cc(280)] : Failed to load /snap/chromium/686/usr/lib/chromium-browser/libGLESv2.so: /snap/chromium/686/usr/lib/chromium-browser/libGLESv2.so: cannot open shared object file: No such file or directory Oddly I get this bug in both the main chromium snap and the vaapi candidate snap. No problems in Chromium when installed via apt. Since I'm not able to update the snap file, I can't correct this issue unfortunately. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1816497 Title: [snap] vaapi chromium no video hardware decoding Status in chromium-browser package in Ubuntu: Confirmed Bug description: Libva is no longer working for snap installed chromium 72.0.3626.109 (Official Build) snap (64-bit) I followed this instruction sudo snap install --channel=candidate/vaapi chromium My amdgpu can use libva `vainfo: Driver version: Mesa Gallium driver 18.3.3 for AMD STONEY (DRM 3.27.0, 4.20.0-10.1-liquorix-amd64, LLVM 7.0.1) vainfo: Supported profile and entrypoints VAProfileMPEG2Simple: VAEntrypointVLD VAProfileMPEG2Main : VAEntrypointVLD VAProfileVC1Simple : VAEntrypointVLD VAProfileVC1Main: VAEntrypointVLD VAProfileVC1Advanced: VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice VAProfileH264Main : VAEntrypointVLD VAProfileH264Main : VAEntrypointEncSlice VAProfileH264High : VAEntrypointVLD VAProfileH264High : VAEntrypointEncSlice VAProfileHEVCMain : VAEntrypointVLD VAProfileHEVCMain10 : VAEntrypointVLD VAProfileJPEGBaseline : VAEntrypointVLD VAProfileNone : VAEntrypointVideoProc` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1816497/+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 1809856] Re: [XPS 13 9370, Realtek ALC3271, Headphone Out, Right] Static/Electric background noise when volume is not muted
Hi Kai-Heng Feng, I successfully applied the patch, thanks. Now when the headphones are plugged in there are a few seconds of hissing before it goes quiet. If I change the volume, the hissing returns and stops after around 3-5s. If I play some music and then stop the music, the hissing returns and eventually stops after around 10s. Is this the expected behaviour? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1809856 Title: [XPS 13 9370, Realtek ALC3271, Headphone Out, Right] Static/Electric background noise when volume is not muted Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: Whenever I plug in my Sennheiser HD1 Wired headphones with mic, I start hearing a static/electric (some internal?) sound if the volume isn't muted. Something similar occurs with my other earbuds with mic, just much quieter and less noticable. It works fine on Windows 10 running on the same machine, and on my Android phone. I don't notice is when something is playing, but the frequency of the sound changes when I play something, then pause it, the background noise will sound slightly different. This is from an installed Ubuntu 18.10. I have tried booting 18.10 Live USB and 18.04.1 LTS Live USB, and the issue still occurs. I have tried playing with alsamixer and pavucontrol settings, and nothing fixed this background noise. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: davidkoplik 1891 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Dec 26 20:17:59 2018 InstallationDate: Installed on 2018-12-26 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Headphone Out, Right Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: High background noise, or volume is too low Title: [XPS 13 9370, Realtek ALC3271, Black Headphone Out, Right] Background noise or low volume UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/04/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.3 dmi.board.name: 0F6P3V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.3:bd11/04/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1809856/+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 1760068] Re: Wrong resolution at unlock screen
With Xubuntu 19.04 Disco Dingo and the 418.56 nvidia drivers it appears now my system has: /usr/lib/x86_64-linux-gnu/nvidia-418/xorg So added the below options to /etc/X11/xorg.conf fixes the issue: Section "Files" ModulePath "/usr/lib/x86_64-linux-gnu/nvidia-418/xorg" ModulePath "/usr/lib/xorg/modules" EndSection I'm not sure why the file/folder structure differed with Xubuntu 18.10 and 415.xx nvidia drivers. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1760068 Title: Wrong resolution at unlock screen Status in light-locker package in Ubuntu: Invalid Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Bug description: After coming out of suspend - the unlock screen is at 640x480 resolution. Expect to see unlock screen at 1920x1080 resolution. Using nvidia-340. Previously tested using nouveau driver where resolution at unlock screen was correct. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: light-locker 1.8.0-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Mar 30 11:31:20 2018 InstallationDate: Installed on 2017-09-02 (209 days ago) InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902) SourcePackage: light-locker UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/light-locker/+bug/1760068/+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 1802105] Re: Zenity crashes when --add-list field duplicated
Hello, Just push the patch, can someone please confirm and close the bug? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to zenity in Ubuntu. https://bugs.launchpad.net/bugs/1802105 Title: Zenity crashes when --add-list field duplicated Status in Zenity: Confirmed Status in zenity package in Ubuntu: Triaged Bug description: Ubuntu 18.04.1 Zenity 3.28.1 $ zenity --forms --add-list='1' --add-list='2' Segmentation fault (core dumped) segfault at 0 ip 7f16f196f690 sp 7fff5a0e0ba0 error 4 in libgtk-3.so.0.2200.30[7f16f1744000+6f1000] To manage notifications about this bug go to: https://bugs.launchpad.net/zenity/+bug/1802105/+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 1766063] Re: mm (Myanmar / Burmese) for zawgyi keyboard layout
https://bugs.freedesktop.org/show_bug.cgi?id=106169 is done all of CentOS, Fedora, Arch, Debian is include but still not include in 19.04 ** Changed in: xkeyboard-config (Arch Linux) Assignee: (unassigned) => kokoye2007 (kokoye2007) ** Changed in: xkeyboard-config (CentOS) Assignee: (unassigned) => kokoye2007 (kokoye2007) ** Changed in: xkeyboard-config (Fedora) Assignee: (unassigned) => kokoye2007 (kokoye2007) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1766063 Title: mm (Myanmar / Burmese) for zawgyi keyboard layout Status in xkeyboard-config: Fix Released Status in xkeyboard-config package in Ubuntu: Triaged Status in xkeyboard-config package in Arch Linux: New Status in xkeyboard-config package in CentOS: New Status in xkeyboard-config package in Debian: Fix Released Status in xkeyboard-config package in Fedora: New Status in xkeyboard-config package in Gentoo Linux: New Status in xkeyboard-config package in Unity Linux: New Bug description: https://bugs.freedesktop.org/show_bug.cgi?id=106169 New Keyboard Layout addition in Myanmar / Burmese --- New Keyboard Layout --- Added New Keyboard Layout - Burmese Zawgyi Keyboard This is similar to Burmese MM. Its most popular keyboard in Burmese. To manage notifications about this bug go to: https://bugs.launchpad.net/xkeyboard-config/+bug/1766063/+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 1638842] Re: network-manager does not manage ethernet and bluetooth interfaces when Ubuntu 16.10 is installed using chroot/netboot method
*** This bug is a duplicate of bug 1676547 *** https://bugs.launchpad.net/bugs/1676547 actually this is what fixed this problem for me. In the file /etc/NetworkManager/NetworkManager.conf I changed managed=false to managed=true -- 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/1638842 Title: network-manager does not manage ethernet and bluetooth interfaces when Ubuntu 16.10 is installed using chroot/netboot method Status in network-manager package in Ubuntu: Won't Fix Bug description: Hello, I installed Ubuntu 16.10 using a chroot. I use network-manager to manage connections. My system is up-to-date (so I use network-manager 1.2.4-0ubuntu1). Wifi works perfectly but I cannot connect to wired networks and using my phone's Bluetooth connection. Corresponding devices are said to be unmanaged by network-manager. nmcli dev outputs: DEVICETYPE STATE CONNECTION enp1s0ethernet unmanaged -- wlp2s0wifi disconnected -- 6C:9B:02:2C:EE:2C btunmanaged -- hfp/org/bluez/hci0/dev_6C_9B_02_2C_EE_2C gsm unmanaged -- loloopback unmanaged -- The following command has no effect: sudo nmcli dev set enp1s0 managed yes I can connect to a wired connection by doing: ifconfig enp1s0 up dhclient enp1s0 There is nothing in the file /etc/network/interfaces. Everything works perfectly if I downgrade network-manager to this version: network-manager_1.2.2-0ubuntu0.16.04.3_amd64.deb (http://packages.ubuntu.com/xenial-updates/amd64/network- manager/download). I had to install libreadline6 and downgrade nplan to meet dependencies. I don't know what to join to this bug report so please ask in case anything is needed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1638842/+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 1816205] Re: [disco-proposed] When using the Gedit icons they disappear from the desktop
Hello guys Ubuntu is on the finishing line and I think you can not continue with these errors, see attachment. Sorry for the poor quality of the video, but to see the kind of error that occurs when removing icons from the desktop to any folder or saving anything on gedit. The icons simply disappear from the desktop by slaving anything with GEDIT and return by clicking save in Gedit again. Thank you Edson > Olá Pessoal O Ubuntu está na reta de chegada e creio que não pode continuar com estes erros, vide anexo. Perdão pela má qualidade do vídeo, mas da para ver o tipo de erro que ocorre ao remover ícones da área de trabalho para qualquer pasta ou salvar qualquer coisa no gedit. Os ícones simplesmente somem da área de trabalho ao slvar qualquer coisa com GEDIT e retornam ao clicar em salvar em Gedit novamente. Obrigado Edson ** Attachment added: "Look at the bugs in this simple video" https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1816205/+attachment/5255712/+files/2019-04-14-122041.webm -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1816205 Title: [disco-proposed] When using the Gedit icons they disappear from the desktop Status in gnome-shell-extension-desktop-icons package in Ubuntu: New Bug description: Hello guys When you open Gedit and edit any text or not, and click save, the desktop icons disappear, disappear, and move from side to side. After you click save the icons reappear again. The following images are attached: * Olá Pessoal Ao abrir o Gedit e editar qualquer texto ou não, e clicarmos em salvar, os ícones da área de trabalho desaparecem, somem e se movem de um lado para o outro. Após clicar em salvar os ícones reaparecem novamente. Segue imagens em anexo: ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gedit 3.31.90-1build1 ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20 Uname: Linux 4.19.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Feb 15 21:46:27 2019 ExecutablePath: /usr/bin/gedit InstallationDate: Installed on 2019-02-11 (4 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203) SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1816205/+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 1638842] Re: network-manager does not manage ethernet and bluetooth interfaces when Ubuntu 16.10 is installed using chroot/netboot method
*** This bug is a duplicate of bug 1676547 *** https://bugs.launchpad.net/bugs/1676547 So I created a network bootable installation based on the 18.04.2 LTS desktop download and I have the exact same problem. However none of the workarounds are working for me. I have tried emptying the 10-globally- managed-devices.conf file in both locations, included the "unmanaged- devices=none" in one or the other or both locations and also tried the workaround described in comment #43 but none of this is working. I'm thinking there's something else we might be missing... Also manually using nmcli to set the device to managed doesn't work. -- 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/1638842 Title: network-manager does not manage ethernet and bluetooth interfaces when Ubuntu 16.10 is installed using chroot/netboot method Status in network-manager package in Ubuntu: Won't Fix Bug description: Hello, I installed Ubuntu 16.10 using a chroot. I use network-manager to manage connections. My system is up-to-date (so I use network-manager 1.2.4-0ubuntu1). Wifi works perfectly but I cannot connect to wired networks and using my phone's Bluetooth connection. Corresponding devices are said to be unmanaged by network-manager. nmcli dev outputs: DEVICETYPE STATE CONNECTION enp1s0ethernet unmanaged -- wlp2s0wifi disconnected -- 6C:9B:02:2C:EE:2C btunmanaged -- hfp/org/bluez/hci0/dev_6C_9B_02_2C_EE_2C gsm unmanaged -- loloopback unmanaged -- The following command has no effect: sudo nmcli dev set enp1s0 managed yes I can connect to a wired connection by doing: ifconfig enp1s0 up dhclient enp1s0 There is nothing in the file /etc/network/interfaces. Everything works perfectly if I downgrade network-manager to this version: network-manager_1.2.2-0ubuntu0.16.04.3_amd64.deb (http://packages.ubuntu.com/xenial-updates/amd64/network- manager/download). I had to install libreadline6 and downgrade nplan to meet dependencies. I don't know what to join to this bug report so please ask in case anything is needed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1638842/+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 1823722] Re: keyboard shortcuts are displayed not translated
I've uploaded that to experimental, thanks! Not sure how to handle the Ubuntu side. -- 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/1823722 Title: keyboard shortcuts are displayed not translated Status in Ubuntu Translations: New Status in language-support-translations-fr package in Ubuntu: New Status in mutter package in Ubuntu: In Progress Bug description: Can't translate some keyboard shortcuts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/1823722/+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 1811596] Re: Ubuntu Single Sign-On GUI not showing login button
I'm a new Linux user, but I started with Fortran in 1968. I don't usually get this stumped. I just signed in here to ubuntu single sign on with no problem. When I try to sign in through settings, I get a pop-up asking for authentication for Snap Daemon (it accepts my password) then there is a pop-up asking for authentication for keyring "Default. . . I don't recall being asked to set a password for this, but log in to ubuntu single sign on fails. In Windows I would scan the disk for errors, but I can't seem to find the right commands. I would appreciate any suggestions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1811596 Title: Ubuntu Single Sign-On GUI not showing login button Status in gnome-online-accounts package in Ubuntu: Confirmed Status in unity-control-center package in Ubuntu: Invalid Bug description: System Settings->Online Accounts->Ubuntu Single Sign-On I can enter my email address and password abd select "I have an Ubuntu Single Sign-On account". But there is no "Save" or "Login" or any other button. I can only close the window. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1811596/+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 1786495] Re: [Precision M4800, Realtek ALC3226, Green Headphone Out, Front] No sound at all
I found the fix. It seems funny but it is really fault of nvidia-driver- xxx. It somehow modifies power settings of the system. I am using latest Ubuntu 19.04 with 5.0.0-11-generic kernel but exactly same problem did happen wit any previous Ubuntu version and also with recent versions of Fedora. I added the following line to /etc/modprobe.d/alsa-base.conf options snd-hda-intel enable_msi=1 enable=0,1 model=dell-headset-multi power_save=0 power_save_controller=N # note that pulseaudio -k && sudo alsa force-reload was not sufficient I had to reboot system because the modules were in some wrong state and they did not unload successfully 1. the enable_msi=1 : interupt setting is there because there is no sound after suspend 2. enable=0,1 : I did disabled the intel hdmi, spdif (non PCM) sound cards because some programs just used the diferent card no matter what was selected in ubuntu desktop controls/alsa mixer and this was the most simple method to get it working (you can list your cards by aplay -l) 3. model=dell-headset-multi this is required otherwise you will hear only cracking if you play something 4. power_save=0 without this you will hear nothing or cracking Note: You may also need to run sudo apt-get install --reinstall dkms alsa-base pulseaudio to get the system in to initial state if you modified something recently. Note: Out of the box ubuntu installation worked just fine, but after reinstall of nvidia-driver-XXX (415->418) / kernel (if the nvidia driver is installed) the sound just stops working and there is no error msg anywhere (dmesg, syslog) and the output is seems to selected properly and the mute etc is set properly in alsamixer. The problem is that the nvidia drivers somehow modifies the power settings and this breaks the audio. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1786495 Title: [Precision M4800, Realtek ALC3226, Green Headphone Out, Front] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Bug description: I am head no sound from my headphone jack. Laptop speaker work fine. Tried 2 different headphones and still no sound. pavucontrol can see my headphone and I see the sound bar move but no sound comes out. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 Uname: Linux 4.15.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: hhernandez 2083 F...m pulseaudio /dev/snd/controlC1: hhernandez 2083 F pulseaudio /dev/snd/controlC0: hhernandez 2083 F pulseaudio CurrentDesktop: MATE Date: Fri Aug 10 07:59:09 2018 PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: hhernandez 2083 F pulseaudio /dev/snd/controlC0: hhernandez 2083 F pulseaudio Symptom_Jack: Green Headphone Out, Front Symptom_Type: No sound at all Title: [Precision M4800, Realtek ALC3226, Green Headphone Out, Front] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/19/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A14 dmi.board.name: 0V5GVY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA14:bd05/19/2015:svnDellInc.:pnPrecisionM4800:pvr01:rvnDellInc.:rn0V5GVY:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Precision M4800 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1786495/+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 1821870] Re: gnome-shell segfault libmutter-clutter-2
I keep getting: [ 8831.746466] gnome-shell[3678]: segfault at 0 ip 7f02a52a2021 sp 7ffd231b8f10 error 4 in libmutter-clutter-2.so[7f02a5222000+161000] multiple times a day. There is nothing in /var/crash and nothing in /var/lib/whoopsie/ -- 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/1821870 Title: gnome-shell segfault libmutter-clutter-2 Status in gnome-shell package in Ubuntu: Incomplete Bug description: Gnome Shell restarts multiple times a day, after the crash I see this error in dmesg: [195984.712376] gnome-shell[5769]: segfault at 0 ip 7f662716e021 sp 7fffbf225760 error 4 in libmutter- clutter-2.so[7f66270ee000+161000] Description:Ubuntu 18.04.2 LTS Release:18.04 gnome-shell: Installed: 3.28.3-0ubuntu0.18.04.4 Candidate: 3.28.3-0ubuntu0.18.04.4 libmutter-2-0: Installed: 3.28.3-2~ubuntu18.04.2 Candidate: 3.28.3-2~ubuntu18.04.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1821870/+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 1822846] Re: Icon disappears from favorites in gnome-shell 3.32
** Changed in: gnome-shell Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1822846 Title: Icon disappears from favorites in gnome-shell 3.32 Status in GNOME Shell: Fix Released Status in gnome-shell package in Ubuntu: Triaged Bug description: From time to time, my chrome icon disappears in gnome shell 3.32, leaving only the "open window indicator" below it. It's the first of my icons, and this is running a vanilla gnome session. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Apr 2 17:44:52 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-03-14 (383 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313) SourcePackage: gnome-shell UpgradeStatus: Upgraded to disco on 2018-11-20 (133 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1822846/+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 1824677] Re: Display only has 640x480
well, maybe the disabling could be limited to known 'bad' hw with buggy firmware, which usually means fairly new hw ** Changed in: xserver-xorg-video-nouveau (Ubuntu) Status: Won't Fix => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1824677 Title: Display only has 640x480 Status in xserver-xorg-video-nouveau package in Ubuntu: Confirmed Bug description: Upgraded kernel available. Restarted to 640x480 display. No other resolutions apparently available. Rebooted to previous kernel - display resolution now correct. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xserver-xorg-video-nouveau 1:1.0.16-1 ProcVersionSignature: Ubuntu 5.0.0-11.12-generic 5.0.6 Uname: Linux 5.0.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: XFCE Date: Sun Apr 14 06:20:02 2019 DistUpgraded: 2018-10-14 15:47:40,052 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GT218 [GeForce 210] [10de:0a65] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. GT218 [GeForce 210] [19da:1160] InstallationDate: Installed on 2018-08-27 (229 days ago) InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180824) MachineType: NOVATECH LTD MBB-44608 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-11-generic root=UUID=5ea4b063-e7d4-43c8-8d9a-5c5f89fa3a3f ro quiet splash vt.handoff=1 SourcePackage: xserver-xorg-video-nouveau UpgradeStatus: Upgraded to disco on 2018-10-14 (181 days ago) dmi.bios.date: 06/19/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-DS2V dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: 7383241-001 dmi.chassis.type: 3 dmi.chassis.vendor: NOVATECH LTD dmi.chassis.version: V1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd06/19/2014:svnNOVATECHLTD:pnMBB-44608:pvrV1.0:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-DS2V:rvrTobefilledbyO.E.M.:cvnNOVATECHLTD:ct3:cvrV1.0: dmi.product.family: AMI PLATFORM dmi.product.name: MBB-44608 dmi.product.sku: MBB-44608 dmi.product.version: V1.0 dmi.sys.vendor: NOVATECH LTD modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2018-09-21T16:30:23.845026 version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1824677/+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 1821820] Re: Cannot boot or install - have to use nomodeset
** Changed in: xorg-server (Ubuntu) Status: Fix Committed => Invalid -- 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/1821820 Title: Cannot boot or install - have to use nomodeset Status in linux package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Invalid Bug description: On this 19.04 beta I have to use nomodeset to boot & install Ubuntu Budgie. This is different behaviour from 18.04 and 18.10 where it booted and installed just fine without nomodeset. Without nomodeset, grub/efi disappears, and after a while a solid rather than blinking cursor on a black screen is seen. It does not boot into a live session, nor displays the ubiquity window ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xserver-xorg-video-intel 2:2.99.917+git20180925-2 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: Budgie:GNOME Date: Tue Mar 26 23:40:49 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b1] (rev 21) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [103c:80bf] InstallationDate: Installed on 2019-03-26 (0 days ago) InstallationMedia: Ubuntu-Budgie 19.04 "Disco Dingo" - Alpha amd64 (20190326.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0a5c:216d Broadcom Corp. BCM43142A0 Bluetooth 4.0 Bus 001 Device 003: ID 05c8:022a Cheng Uei Precision Industry Co., Ltd (Foxlink) Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Notebook ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic root=UUID=62ab7c7b-50c8-4719-98c6-55991179ff20 ro nomodeset quiet splash SourcePackage: xserver-xorg-video-intel UpgradeStatus: No upgrade log present (probably fresh install) XorgLogOld: dmi.bios.date: 02/15/2016 dmi.bios.vendor: Insyde dmi.bios.version: F.1F dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80BF dmi.board.vendor: HP dmi.board.version: 95.16 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.1F:bd02/15/2016:svnHP:pnHPNotebook:pvr:rvnHP:rn80BF:rvr95.16:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.sku: N9S73EA#ABU dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821820/+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 1824677] Re: Display only has 640x480
Nouveau modeset is now disabled by default, because the driver is buggy and can prevent installation. You can re-enable it by adding 'nouveau.modeset=1' to 'GRUB_CMDLINE_LINUX' on /etc/default/grub, and running update-grub after that. ** Changed in: xserver-xorg-video-nouveau (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1824677 Title: Display only has 640x480 Status in xserver-xorg-video-nouveau package in Ubuntu: Won't Fix Bug description: Upgraded kernel available. Restarted to 640x480 display. No other resolutions apparently available. Rebooted to previous kernel - display resolution now correct. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xserver-xorg-video-nouveau 1:1.0.16-1 ProcVersionSignature: Ubuntu 5.0.0-11.12-generic 5.0.6 Uname: Linux 5.0.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: XFCE Date: Sun Apr 14 06:20:02 2019 DistUpgraded: 2018-10-14 15:47:40,052 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GT218 [GeForce 210] [10de:0a65] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. GT218 [GeForce 210] [19da:1160] InstallationDate: Installed on 2018-08-27 (229 days ago) InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180824) MachineType: NOVATECH LTD MBB-44608 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-11-generic root=UUID=5ea4b063-e7d4-43c8-8d9a-5c5f89fa3a3f ro quiet splash vt.handoff=1 SourcePackage: xserver-xorg-video-nouveau UpgradeStatus: Upgraded to disco on 2018-10-14 (181 days ago) dmi.bios.date: 06/19/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-DS2V dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: 7383241-001 dmi.chassis.type: 3 dmi.chassis.vendor: NOVATECH LTD dmi.chassis.version: V1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd06/19/2014:svnNOVATECHLTD:pnMBB-44608:pvrV1.0:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-DS2V:rvrTobefilledbyO.E.M.:cvnNOVATECHLTD:ct3:cvrV1.0: dmi.product.family: AMI PLATFORM dmi.product.name: MBB-44608 dmi.product.sku: MBB-44608 dmi.product.version: V1.0 dmi.sys.vendor: NOVATECH LTD modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2018-09-21T16:30:23.845026 version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1824677/+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 1821494] Re: Sennheiser GSX 1000/1200: only one subdevice exposed by Pulse & incorrect channel mapping
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: pulseaudio (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1821494
Title:
Sennheiser GSX 1000/1200: only one subdevice exposed by Pulse &
incorrect channel mapping
Status in pulseaudio package in Ubuntu:
Confirmed
Bug description:
Similar to the Steelseries Arctis headphones, these sound "cards"
present as two output devices, one intended for voice chat and one for
everything else. As a result they also need a special profile.
But there's another complication. They also have hardware HRTF that
requires no special driver logic; instead, the "everything else"
output pretends to be 7.1, and simply applies the HRTF to the streams
sent by the host. However, the channel mappings picked up by ALSA are
wrong -- the rear speakers and center/LFE are swapped.
I know, technically this is two bugs, but they have the same fix which
is impractical to separate. I'm attaching a "sennheiser-gsx.conf"
based on the Arctis 7 profile that both corrects the channel mapping
and exposes both output subdevices. A simple udev rule seals the deal:
ATTRS{idVendor}=="1395", ATTRS{idProduct}=="005e",
ENV{PULSE_PROFILE_SET}="sennheiser-gsx.conf"
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: pulseaudio 1:11.1-1ubuntu7.2
ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20
Uname: Linux 4.18.0-16-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC3: roothorick 7548 F pulseaudio
/dev/snd/controlC2: roothorick 7548 F pulseaudio
/dev/snd/controlC0: roothorick 7548 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Sat Mar 23 23:09:21 2019
InstallationDate: Installed on 2018-09-12 (193 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64
(20180725)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: pulseaudio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/07/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2004
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: H87M-E
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr2004:bd08/07/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH87M-E:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.family: ASUS MB
dmi.product.name: All Series
dmi.product.sku: All
dmi.product.version: System Version
dmi.sys.vendor: ASUS
modified.conffile..etc.pulse.daemon.conf: [modified]
modified.conffile..etc.pulse.default.pa: [modified]
mtime.conffile..etc.pulse.daemon.conf: 2019-03-23T20:51:33.488207
mtime.conffile..etc.pulse.default.pa: 2019-03-23T23:03:49.029912
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1821494/+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 1824699] [NEW] gnome-calendar pango critical
Public bug reported: Hello, my calendar does not start anymore. I have Ubuntu 18.10. olli@T470:~/.local/share$ gnome-calendar (gnome-calendar:8982): Pango-CRITICAL **: 14:08:31.426: pango_font_description_set_size: assertion 'size >= 0' failed (gnome-calendar:8982): GcalWeatherSettings-WARNING **: 14:08:31.589: Unknown location 'dorsten' selected Speicherzugriffsfehler (Speicherabzug geschrieben) Does anybody have an idea how to solve this? Thanks! ** Affects: gnome-calendar (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1824699 Title: gnome-calendar pango critical Status in gnome-calendar package in Ubuntu: New Bug description: Hello, my calendar does not start anymore. I have Ubuntu 18.10. olli@T470:~/.local/share$ gnome-calendar (gnome-calendar:8982): Pango-CRITICAL **: 14:08:31.426: pango_font_description_set_size: assertion 'size >= 0' failed (gnome-calendar:8982): GcalWeatherSettings-WARNING **: 14:08:31.589: Unknown location 'dorsten' selected Speicherzugriffsfehler (Speicherabzug geschrieben) Does anybody have an idea how to solve this? Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1824699/+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 1823650] Re: v4l-utils ftbfs in cosmic
Hello,
attached you'll find the debdiff with critical patches for v4l-utils
1.14 in cosmic. All of them have been taken from v4l-utils stable-1.14
branch.
The source of this debdiff could be found in the debian v4l-utils repo
on salsa in the cosmic branch:
https://salsa.debian.org/debian/libv4l/tree/cosmic
How to proceed from here?
Thanks,
Gregor
** Attachment added: "v4l-utils-lp1823650.diff"
https://bugs.launchpad.net/bugs/1823650/+attachment/5255664/+files/v4l-utils-lp1823650.diff
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to v4l-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1823650
Title:
v4l-utils ftbfs in cosmic
Status in v4l-utils package in Ubuntu:
New
Bug description:
https://launchpadlibrarian.net/418304769/buildlog_ubuntu-cosmic-amd64
.v4l-utils_1.14.2-1_BUILDING.txt.gz
g++ -I. -I../.. -I../../utils/common -I../../lib/include -Wall
-Wpointer-arith -D_GNU_SOURCE -I../../include -Wdate-time -D_FORTIFY_SOURCE=2
-g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
-Werror=format-security -c -o v4l2_compliance-v4l2-compliance.o `test -f
'v4l2-compliance.cpp' || echo './'`v4l2-compliance.cpp
In file included from v4l2-compliance.h:42,
from v4l2-compliance.cpp:38:
../../utils/common/cv4l-helpers.h: In member function ‘void
cv4l_buffer::init(const cv4l_buffer&)’:
../../utils/common/cv4l-helpers.h:843:29: warning: ‘void* memcpy(void*, const
void*, size_t)’ writing to an object of type ‘class cv4l_buffer’ with no
trivial copy-assignment; use copy-assignment or copy-initialization instead
[-Wclass-memaccess]
memcpy(this, , sizeof(b));
^
../../utils/common/cv4l-helpers.h:817:7: note: ‘class cv4l_buffer’ declared
here
class cv4l_buffer : public v4l_buffer {
^~~
g++ -I. -I../.. -I../../utils/common -I../../lib/include -Wall
-Wpointer-arith -D_GNU_SOURCE -I../../include -Wdate-time -D_FORTIFY_SOURCE=2
-g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
-Werror=format-security -c -o v4l2_compliance-v4l2-test-debug.o `test -f
'v4l2-test-debug.cpp' || echo './'`v4l2-test-debug.cpp
In file included from v4l2-compliance.h:42,
from v4l2-test-debug.cpp:35:
../../utils/common/cv4l-helpers.h: In member function ‘void
cv4l_buffer::init(const cv4l_buffer&)’:
../../utils/common/cv4l-helpers.h:843:29: warning: ‘void* memcpy(void*, const
void*, size_t)’ writing to an object of type ‘class cv4l_buffer’ with no
trivial copy-assignment; use copy-assignment or copy-initialization instead
[-Wclass-memaccess]
memcpy(this, , sizeof(b));
^
../../utils/common/cv4l-helpers.h:817:7: note: ‘class cv4l_buffer’ declared
here
class cv4l_buffer : public v4l_buffer {
^~~
g++ -I. -I../.. -I../../utils/common -I../../lib/include -Wall
-Wpointer-arith -D_GNU_SOURCE -I../../include -Wdate-time -D_FORTIFY_SOURCE=2
-g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
-Werror=format-security -c -o v4l2_compliance-v4l2-test-input-output.o `test -f
'v4l2-test-input-output.cpp' || echo './'`v4l2-test-input-output.cpp
In file included from v4l2-compliance.h:42,
from v4l2-test-input-output.cpp:32:
../../utils/common/cv4l-helpers.h: In member function ‘void
cv4l_buffer::init(const cv4l_buffer&)’:
../../utils/common/cv4l-helpers.h:843:29: warning: ‘void* memcpy(void*, const
void*, size_t)’ writing to an object of type ‘class cv4l_buffer’ with no
trivial copy-assignment; use copy-assignment or copy-initialization instead
[-Wclass-memaccess]
memcpy(this, , sizeof(b));
^
../../utils/common/cv4l-helpers.h:817:7: note: ‘class cv4l_buffer’ declared
here
class cv4l_buffer : public v4l_buffer {
^~~
g++ -I. -I../.. -I../../utils/common -I../../lib/include -Wall
-Wpointer-arith -D_GNU_SOURCE -I../../include -Wdate-time -D_FORTIFY_SOURCE=2
-g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
-Werror=format-security -c -o v4l2_compliance-v4l2-test-controls.o `test -f
'v4l2-test-controls.cpp' || echo './'`v4l2-test-controls.cpp
In file included from v4l2-compliance.h:42,
from v4l2-test-controls.cpp:33:
../../utils/common/cv4l-helpers.h: In member function ‘void
cv4l_buffer::init(const cv4l_buffer&)’:
../../utils/common/cv4l-helpers.h:843:29: warning: ‘void* memcpy(void*, const
void*, size_t)’ writing to an object of type ‘class cv4l_buffer’ with no
trivial copy-assignment; use copy-assignment or copy-initialization instead
[-Wclass-memaccess]
memcpy(this, , sizeof(b));
^
../../utils/common/cv4l-helpers.h:817:7: note: ‘class cv4l_buffer’ declared
here
class cv4l_buffer : public v4l_buffer {
^~~
g++ -I. -I../.. -I../../utils/common
[Desktop-packages] [Bug 1812266] Re: Keyboard layout indicator does not indicate current layout (18.04 Bionic beaver)
I can also confirm that after following the instructions from #51 on Bionic, this bug is fixed. (I would however comment that it would have been easy to miss that safety measure and upgrade a whole bunch of proposed packages by mistake. I would caution everyone to be more careful when directing non- developers to alter developer configurations.) -- 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/1812266 Title: Keyboard layout indicator does not indicate current layout (18.04 Bionic beaver) Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Bionic: Fix Committed Status in gnome-shell source package in Cosmic: Fix Released Bug description: Upstream issue: https://gitlab.gnome.org/GNOME/gnome-shell/issues/913 [ Impact ] Keyboard Layout indicator don't display current layout (empty selected drop down box) [ Test case ] 1. Boot 2. Suspend or lock the screen 3. Log again with your user 4. The keyboard indicator should display current layout [ Regression Potential ] Really low, we properly pass a null value instead of an undefined one, without breaking JS. -- Steps to reproduce the bug: 1. After normal boot, suspend or lock. 2. Login again. Result: Keyboard Layout indicator don't display current layout (empty selected drop down box) [ Workarounds ] - Switch with keyboard (Super+space) or mouse. BUT if you then logout on the login screen *when you press the first character* of the password the shown selected keyboard layout resets. - Restart Gnome Shell (Alt+F2 r): https://wiki.gnome.org/Projects/GnomeShell/CheatSheet#Developer_tools - Also asked here https://askubuntu.com/q/1109555/349837 - Similar old bug https://bugs.launchpad.net/gnome-settings-daemon/+bug/531173 $ inxi -SG -! 31 -y80 && cat /etc/default/keyboard && localectl status System:Kernel: 4.15.0-43-generic x86_64 bits: 64 Desktop: Gnome 3.28.3 Distro: Ubuntu 18.04.1 LTS Graphics: Card-1: Intel HD Graphics 520 Card-2: NVIDIA GM108M [GeForce 940M] Display Server: x11 (X.Org 1.19.6 ) drivers: fbdev (unloaded: modesetting,vesa) Resolution: 1920x1080@60.00hz OpenGL: renderer: Mesa DRI Intel HD Graphics 520 (Skylake GT2) version: 4.5 Mesa 18.0.5 # KEYBOARD CONFIGURATION FILE # Consult the keyboard(5) manual page. XKBMODEL="pc105" XKBLAYOUT="es" XKBVARIANT="en" XKBOPTIONS="terminate:ctrl_alt_bksp" BACKSPACE="guess" System Locale: LANG=en_US.UTF-8 LC_NUMERIC=es_AR.UTF-8 LC_MONETARY=es_AR.UTF-8 LC_PAPER=es_AR.UTF-8 LC_NAME=es_AR.UTF-8 LC_ADDRESS=es_AR.UTF-8 LC_TELEPHONE=es_AR.UTF-8 LC_MEASUREMENT=es_AR.UTF-8 LC_IDENTIFICATION=es_AR.UTF-8 VC Keymap: n/a X11 Layout: es X11 Model: pc105 X11 Variant: en X11 Options: terminate:ctrl_alt_bksp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1812266/+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 1824692] [NEW] Question mark within the Wi-Fi icon
Public bug reported: I had two problems with Ubuntu 18.04 and earlier. 1. Question mark within the Wi-Fi icon after connecting to the internet. 2. Question mark within the battery icon after the battery is fully charged. I tested the 19.04 version right now and realized that my problem with the battery icon was fixed. But my problem with Wi-Fi icon is still there. It should be noted that there is no problem with connecting to the Internet, and I have full Internet access and there is only a question mark within the Wi-Fi icon. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-11.12-generic 5.0.6 Uname: Linux 5.0.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperVersion: 1.403 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Apr 14 10:48:29 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 5500 [1043:194d] Subsystem: ASUSTeK Computer Inc. GK208BM [GeForce 920M] [1043:232a] LiveMediaBuild: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190413.2) MachineType: ASUSTeK COMPUTER INC. TP300LJ ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed boot=casper quiet splash --- SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/05/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: TP300LJ.206 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: TP300LJ dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrTP300LJ.206:bd08/05/2015:svnASUSTeKCOMPUTERINC.:pnTP300LJ:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnTP300LJ:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: TP dmi.product.name: TP300LJ dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco ubuntu ** Attachment added: "Screenshot from 2019-04-14 11-31-52.png" https://bugs.launchpad.net/bugs/1824692/+attachment/5255644/+files/Screenshot%20from%202019-04-14%2011-31-52.png -- 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/1824692 Title: Question mark within the Wi-Fi icon Status in xorg package in Ubuntu: New Bug description: I had two problems with Ubuntu 18.04 and earlier. 1. Question mark within the Wi-Fi icon after connecting to the internet. 2. Question mark within the battery icon after the battery is fully charged. I tested the 19.04 version right now and realized that my problem with the battery icon was fixed. But my problem with Wi-Fi icon is still there. It should be noted that there is no problem with connecting to the Internet, and I have full Internet access and there is only a question mark within the Wi-Fi icon. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-11.12-generic 5.0.6 Uname: Linux 5.0.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperVersion: 1.403 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Apr 14 10:48:29 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 5500 [1043:194d] Subsystem: ASUSTeK Computer Inc. GK208BM [GeForce 920M] [1043:232a] LiveMediaBuild: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190413.2) MachineType: ASUSTeK COMPUTER INC. TP300LJ ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8
[Desktop-packages] [Bug 1812266] Re: Keyboard layout indicator does not indicate current layout (18.04 Bionic beaver)
I can also confirm that after following the instructions from #51 on Bionic, this bug is fixed. (I would however comment that it would have been easy to miss that safety measure and upgrade a whole bunch of proposed packages by mistake. I would caution everyone to be more careful when directing non- developers to alter developer configurations.) -- 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/1812266 Title: Keyboard layout indicator does not indicate current layout (18.04 Bionic beaver) Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Bionic: Fix Committed Status in gnome-shell source package in Cosmic: Fix Released Bug description: Upstream issue: https://gitlab.gnome.org/GNOME/gnome-shell/issues/913 [ Impact ] Keyboard Layout indicator don't display current layout (empty selected drop down box) [ Test case ] 1. Boot 2. Suspend or lock the screen 3. Log again with your user 4. The keyboard indicator should display current layout [ Regression Potential ] Really low, we properly pass a null value instead of an undefined one, without breaking JS. -- Steps to reproduce the bug: 1. After normal boot, suspend or lock. 2. Login again. Result: Keyboard Layout indicator don't display current layout (empty selected drop down box) [ Workarounds ] - Switch with keyboard (Super+space) or mouse. BUT if you then logout on the login screen *when you press the first character* of the password the shown selected keyboard layout resets. - Restart Gnome Shell (Alt+F2 r): https://wiki.gnome.org/Projects/GnomeShell/CheatSheet#Developer_tools - Also asked here https://askubuntu.com/q/1109555/349837 - Similar old bug https://bugs.launchpad.net/gnome-settings-daemon/+bug/531173 $ inxi -SG -! 31 -y80 && cat /etc/default/keyboard && localectl status System:Kernel: 4.15.0-43-generic x86_64 bits: 64 Desktop: Gnome 3.28.3 Distro: Ubuntu 18.04.1 LTS Graphics: Card-1: Intel HD Graphics 520 Card-2: NVIDIA GM108M [GeForce 940M] Display Server: x11 (X.Org 1.19.6 ) drivers: fbdev (unloaded: modesetting,vesa) Resolution: 1920x1080@60.00hz OpenGL: renderer: Mesa DRI Intel HD Graphics 520 (Skylake GT2) version: 4.5 Mesa 18.0.5 # KEYBOARD CONFIGURATION FILE # Consult the keyboard(5) manual page. XKBMODEL="pc105" XKBLAYOUT="es" XKBVARIANT="en" XKBOPTIONS="terminate:ctrl_alt_bksp" BACKSPACE="guess" System Locale: LANG=en_US.UTF-8 LC_NUMERIC=es_AR.UTF-8 LC_MONETARY=es_AR.UTF-8 LC_PAPER=es_AR.UTF-8 LC_NAME=es_AR.UTF-8 LC_ADDRESS=es_AR.UTF-8 LC_TELEPHONE=es_AR.UTF-8 LC_MEASUREMENT=es_AR.UTF-8 LC_IDENTIFICATION=es_AR.UTF-8 VC Keymap: n/a X11 Layout: es X11 Model: pc105 X11 Variant: en X11 Options: terminate:ctrl_alt_bksp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1812266/+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 1821820] Re: Cannot boot or install - have to use nomodeset
Robert suggest create a new bug report to cover your issue. Dont forget to tag this with disco and iso-testing tags. Since I created this issue report I am pleased to report that the kernel update in this release candidate iso has resolved this issue. -- 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/1821820 Title: Cannot boot or install - have to use nomodeset Status in linux package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Fix Committed Bug description: On this 19.04 beta I have to use nomodeset to boot & install Ubuntu Budgie. This is different behaviour from 18.04 and 18.10 where it booted and installed just fine without nomodeset. Without nomodeset, grub/efi disappears, and after a while a solid rather than blinking cursor on a black screen is seen. It does not boot into a live session, nor displays the ubiquity window ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xserver-xorg-video-intel 2:2.99.917+git20180925-2 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: Budgie:GNOME Date: Tue Mar 26 23:40:49 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b1] (rev 21) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [103c:80bf] InstallationDate: Installed on 2019-03-26 (0 days ago) InstallationMedia: Ubuntu-Budgie 19.04 "Disco Dingo" - Alpha amd64 (20190326.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0a5c:216d Broadcom Corp. BCM43142A0 Bluetooth 4.0 Bus 001 Device 003: ID 05c8:022a Cheng Uei Precision Industry Co., Ltd (Foxlink) Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Notebook ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic root=UUID=62ab7c7b-50c8-4719-98c6-55991179ff20 ro nomodeset quiet splash SourcePackage: xserver-xorg-video-intel UpgradeStatus: No upgrade log present (probably fresh install) XorgLogOld: dmi.bios.date: 02/15/2016 dmi.bios.vendor: Insyde dmi.bios.version: F.1F dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80BF dmi.board.vendor: HP dmi.board.version: 95.16 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.1F:bd02/15/2016:svnHP:pnHPNotebook:pvr:rvnHP:rn80BF:rvr95.16:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.sku: N9S73EA#ABU dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821820/+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 1767564] Re: Ubuntu 18.04 Workspaces only change on primary monitor
@torzsmokus > the Activities (and the hot corner) on the secondary display shows windows on > all workspaces I had noticed that too, but it appears this bug was fixed. I cannot reproduce it in a current Ubuntu Cosmic install. -- 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/1767564 Title: Ubuntu 18.04 Workspaces only change on primary monitor Status in gnome-shell package in Ubuntu: Invalid Bug description: After connecting an external monitor to the laptop: - the 4 workspaces that I could access using keyboard shortcuts seem to have been reduced to only 2 - the 'workspace' does not appear to be changeable on the external (secondary) monitor ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 28 12:42:28 2018 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'command-history' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2018-04-28 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1767564/+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 1824677] Re: Display only has 640x480
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xserver-xorg-video-nouveau (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1824677 Title: Display only has 640x480 Status in xserver-xorg-video-nouveau package in Ubuntu: Confirmed Bug description: Upgraded kernel available. Restarted to 640x480 display. No other resolutions apparently available. Rebooted to previous kernel - display resolution now correct. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xserver-xorg-video-nouveau 1:1.0.16-1 ProcVersionSignature: Ubuntu 5.0.0-11.12-generic 5.0.6 Uname: Linux 5.0.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: XFCE Date: Sun Apr 14 06:20:02 2019 DistUpgraded: 2018-10-14 15:47:40,052 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GT218 [GeForce 210] [10de:0a65] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. GT218 [GeForce 210] [19da:1160] InstallationDate: Installed on 2018-08-27 (229 days ago) InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180824) MachineType: NOVATECH LTD MBB-44608 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-11-generic root=UUID=5ea4b063-e7d4-43c8-8d9a-5c5f89fa3a3f ro quiet splash vt.handoff=1 SourcePackage: xserver-xorg-video-nouveau UpgradeStatus: Upgraded to disco on 2018-10-14 (181 days ago) dmi.bios.date: 06/19/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-DS2V dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: 7383241-001 dmi.chassis.type: 3 dmi.chassis.vendor: NOVATECH LTD dmi.chassis.version: V1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd06/19/2014:svnNOVATECHLTD:pnMBB-44608:pvrV1.0:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-DS2V:rvrTobefilledbyO.E.M.:cvnNOVATECHLTD:ct3:cvrV1.0: dmi.product.family: AMI PLATFORM dmi.product.name: MBB-44608 dmi.product.sku: MBB-44608 dmi.product.version: V1.0 dmi.sys.vendor: NOVATECH LTD modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2018-09-21T16:30:23.845026 version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1824677/+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
