[Desktop-packages] [Bug 1820323] Re: amdgpu-pro xorg crash
the only solution is to install a newer amdgpu-pro which supports 16.04.3, there's nothing we can do on ubuntu side ** Changed in: xorg-server (Ubuntu) Status: New => 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/1820323 Title: amdgpu-pro xorg crash Status in xorg-server package in Ubuntu: Invalid Bug description: This is on Precision 3620, Precision 5820, Precision 7820 - systems with AMD bundled for OEM fail to properly boot after update/upgrade. I believe this is related to this issue: https://www.amd.com/en/support/kb/faq/amdgpupro-ubuntu-advisory Since our image contains the amdgpu-pro package we are impacted. Canonical image is not impacted. Various systems (Precision 3420, 3620, 5820, and 7820) are having login issues with AMD GPUs after running system updates on the OEM Ubuntu image. After running sudo apt-get update && apt-get upgrade, the system will exhibit one of a few different behaviors: • Boots to a black screen • Loops at login • Boots to a screen indicating the system has been forced to low graphics mode and hard locks. I have a systems in the lab that exhibits this issue and I don’t know how to get around it. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-143.169-generic 4.4.170 Uname: Linux 4.4.0-143-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 BootLog: Scanning for Btrfs filesystems UBUNTU: clean, 267691/28237824 files, 3796147/112924672 blocks CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Fri Mar 15 13:22:36 2019 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Subsystem: Dell Device [1028:06c7] Advanced Micro Devices, Inc. [AMD/ATI] Lexa XT [Radeon PRO WX 2100] [1002:6995] (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0b0c] InstallationDate: Installed on 2019-03-14 (0 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. Precision Tower 3420 ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-143-generic root=UUID=ced18cfc-68aa-461d-a69d-d482f5880d16 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/07/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.11.2 dmi.board.name: 02K9CR dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.11.2:bd11/07/2018:svnDellInc.:pnPrecisionTower3420:pvr:rvnDellInc.:rn02K9CR:rvrA02:cvnDellInc.:ct3:cvr: dmi.product.name: Precision Tower 3420 dmi.sys.vendor: Dell Inc. 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 2:1.18.4-0ubuntu0.8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Fri Mar 15 13:21:28 2019 xserver.configfile: default xserver.devices: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.4-0ubuntu0.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1820323/+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 1832656] Re: chromium-browser deb->snap transition breaks ubuntukylin image builds
** Changed in: chromium-browser (Ubuntu Eoan) Assignee: (unassigned) => Olivier Tilloy (osomon) -- 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/1832656 Title: chromium-browser deb->snap transition breaks ubuntukylin image builds Status in chromium-browser package in Ubuntu: New Status in ubuntukylin-meta package in Ubuntu: New Status in chromium-browser source package in Eoan: New Status in ubuntukylin-meta source package in Eoan: New Bug description: From https://launchpad.net/~ubuntu- cdimage/+livefs/ubuntu/eoan/ubuntukylin/+build/169881: Preparing to unpack .../000-chromium-browser_75.0.3770.80-0ubuntu1~snap2_amd64.deb ... => Installing the chromium snap ==> Checking connectivity with the snap store ===> Unable to contact the store, trying every minute for the next 30 minutes ===> Still unable to contact the store, trying for another 20 minutes ===> Still unable to contact the store, trying for another 10 minutes ===> Still unable to contact the store, aborting dpkg: error processing archive /tmp/apt-dpkg-install-43SUPL/000-chromium-browser_75.0.3770.80-0ubuntu1~snap2_amd64.deb (--unpack): new chromium-browser package pre-installation script subprocess returned error exit status 1 It is possible that the flavors should switch to seeding the snap instead of the deb. However, it's unclear to me why the deb is failing to talk to the Snap Store, because seeding of snaps DOES work from within image builds. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1832656/+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 1832610] Re: [Dell Inspiron 5480] No sound at all from internal speakers
Thanks. In that case it sounds like maybe Wine was accessing the sound devices directly. If an app does that then PulseAudio is unable to access the sound hardware at the same time. The solution is to get all apps to change to using PulseAudio instead of ALSA, so they can all share the sound hardware. ** Changed in: pulseaudio (Ubuntu) Status: New => Invalid -- 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/1832610 Title: [Dell Inspiron 5480] No sound at all from internal speakers Status in pulseaudio package in Ubuntu: Invalid Bug description: No sounds at internal speakers but headphones works ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.2 ProcVersionSignature: Ubuntu 4.15.0-1039.44-oem 4.15.18 Uname: Linux 4.15.0-1039-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: marcelo 10930 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Jun 12 13:00:36 2019 InstallationDate: Installed on 2019-06-03 (8 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Áudio interno - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1813 F pulseaudio marcelo 10930 F pulseaudio Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: No sound at all Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/24/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.2.0 dmi.board.name: 07G539 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.2.0:bd03/24/2019:svnDellInc.:pnInspiron5480:pvr:rvnDellInc.:rn07G539:rvrA01:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5480 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1832610/+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 1832610] Re: [Dell Inspiron 5480] No sound at all from internal speakers
I remove package wine-stable and your dependencies. After reboot the internal speakers works again dpkg.log: 2019-06-12 16:35:10 startup packages remove 2019-06-12 16:35:11 remove wine-stable:all 3.0-1ubuntu1 2019-06-12 16:35:29 startup packages remove 2019-06-12 16:35:29 remove fonts-wine:all 3.0-1ubuntu1 2019-06-12 16:35:29 remove gstreamer1.0-plugins-base:i386 1.14.1-1ubuntu1~ubuntu18.04.2 2019-06-12 16:35:29 remove wine32:i386 3.0-1ubuntu1 2019-06-12 16:35:30 remove libwine:i386 3.0-1ubuntu1 2019-06-12 16:35:30 remove libldap-2.4-2:i386 2.4.45+dfsg-1ubuntu1.2 2019-06-12 16:35:30 remove libgssapi3-heimdal:i386 7.5.0+dfsg-1 2019-06-12 16:35:30 remove libheimntlm0-heimdal:i386 7.5.0+dfsg-1 2019-06-12 16:35:30 remove libkrb5-26-heimdal:i386 7.5.0+dfsg-1 2019-06-12 16:35:30 remove libhx509-5-heimdal:i386 7.5.0+dfsg-1 2019-06-12 16:35:30 remove libopenal1:i386 1:1.18.2-2 2019-06-12 16:35:31 remove libsndio6.1:i386 1.1.0-3 2019-06-12 16:35:31 remove libasound2-plugins:i386 1.1.1-1ubuntu1 2019-06-12 16:35:31 remove libasound2:i386 1.1.3-5ubuntu0.2 2019-06-12 16:35:31 remove libpulse0:i386 1:11.1-1ubuntu7.2 2019-06-12 16:35:31 remove libasyncns0:i386 0.8-6 2019-06-12 16:35:31 remove libcups2:i386 2.2.7-1ubuntu2.6 2019-06-12 16:35:31 remove libsane1:i386 1.0.27-1~experimental3ubuntu2 2019-06-12 16:35:32 remove libavahi-client3:i386 0.7-3.1ubuntu1.2 2019-06-12 16:35:32 remove libavahi-common3:i386 0.7-3.1ubuntu1.2 2019-06-12 16:35:32 remove libavahi-common-data:i386 0.7-3.1ubuntu1.2 2019-06-12 16:35:32 remove libtheora0:i386 1.1.1+dfsg.1-14 2019-06-12 16:35:32 remove libcairo2:i386 1.15.10-2ubuntu0.1 2019-06-12 16:35:32 remove libgstreamer-plugins-base1.0-0:i386 1.14.1-1ubuntu1~ubuntu18.04.2 2019-06-12 16:35:32 remove libgstreamer1.0-0:i386 1.14.1-1~ubuntu18.04.2 2019-06-12 16:35:33 remove libcap2:i386 1:2.25-1.2 2019-06-12 16:35:33 remove libcapi20-3:amd64 1:3.27-3 2019-06-12 16:35:33 remove libcapi20-3:i386 1:3.27-3 2019-06-12 16:35:33 remove libcdparanoia0:i386 3.10.2+debian-13 2019-06-12 16:35:33 remove libwind0-heimdal:i386 7.5.0+dfsg-1 2019-06-12 16:35:33 remove libgssapi-krb5-2:i386 1.16-2ubuntu0.1 2019-06-12 16:35:33 remove libkrb5-3:i386 1.16-2ubuntu0.1 2019-06-12 16:35:34 remove libcomerr2:i386 1.44.1-1ubuntu1.1 2019-06-12 16:35:34 remove libdbus-1-3:i386 1.12.2-1ubuntu1.1 2019-06-12 16:35:34 remove libgphoto2-6:i386 2.5.16-2 2019-06-12 16:35:34 remove libexif12:i386 0.6.21-4 2019-06-12 16:35:34 remove libsndfile1:i386 1.0.28-4ubuntu0.18.04.1 2019-06-12 16:35:34 remove libflac8:i386 1.3.2-1 2019-06-12 16:35:34 remove libgd3:i386 2.2.5-4ubuntu0.3 2019-06-12 16:35:35 remove libfontconfig1:i386 2.12.6-0ubuntu2 2019-06-12 16:35:35 remove libfreetype6:i386 2.8.1-2ubuntu2 2019-06-12 16:35:35 remove libglib2.0-0:i386 2.56.4-0ubuntu0.18.04.3 2019-06-12 16:35:35 remove libglu1-mesa:i386 9.0.0-2.1build1 2019-06-12 16:35:35 remove libgnutls30:i386 3.5.18-1ubuntu1.1 2019-06-12 16:35:35 remove libhogweed4:i386 3.4-1 2019-06-12 16:35:35 remove libgmp10:i386 2:6.1.2+dfsg-2 2019-06-12 16:35:36 remove libgphoto2-port12:i386 2.5.16-2 2019-06-12 16:35:36 remove libgsm1:i386 1.0.13-4build1 2019-06-12 16:35:36 remove libhcrypto4-heimdal:i386 7.5.0+dfsg-1 2019-06-12 16:35:36 remove libheimbase1-heimdal:i386 7.5.0+dfsg-1 2019-06-12 16:35:36 remove libxslt1.1:i386 1.1.29-5ubuntu0.1 2019-06-12 16:35:36 remove libxml2:i386 2.9.4+dfsg1-6.1ubuntu1.2 2019-06-12 16:35:36 remove libicu60:i386 60.2-3ubuntu3 2019-06-12 16:35:36 remove libidn2-0:i386 2.0.4-1.1build2 2019-06-12 16:35:37 remove libieee1284-3:i386 0.2.11-13 2019-06-12 16:35:37 remove libjack-jackd2-0:i386 1.9.12~dfsg-2 2019-06-12 16:35:37 remove libtiff5:i386 4.0.9-5ubuntu0.2 2019-06-12 16:35:37 remove libjbig0:i386 2.1-3.1build1 2019-06-12 16:35:37 remove libv4l-0:i386 1.14.2-1 2019-06-12 16:35:37 remove libv4lconvert0:i386 1.14.2-1 2019-06-12 16:35:37 remove libjpeg8:i386 8c-2ubuntu8 2019-06-12 16:35:38 remove libjpeg-turbo8:i386 1.5.2-0ubuntu5.18.04.1 2019-06-12 16:35:38 remove libk5crypto3:i386 1.16-2ubuntu0.1 2019-06-12 16:35:38 remove libkeyutils1:i386 1.5.9-9.2ubuntu2 2019-06-12 16:35:38 remove libkrb5support0:i386 1.16-2ubuntu0.1 2019-06-12 16:35:38 remove liblcms2-2:i386 2.9-1ubuntu0.1 2019-06-12 16:35:38 remove libodbc1:i386 2.3.4-1.1ubuntu3 2019-06-12 16:35:38 remove libltdl7:i386 2.4.6-2 2019-06-12 16:35:39 remove libmpg123-0:i386 1.25.10-1 2019-06-12 16:35:39 remove libnettle6:i386 3.4-1 2019-06-12 16:35:39 remove libvorbisenc2:i386 1.3.5-4.2 2019-06-12 16:35:39 remove libvorbis0a:i386 1.3.5-4.2 2019-06-12 16:35:39 remove libogg0:i386 1.3.2-1 2019-06-12 16:35:39 remove libopus0:i386 1.1.2-1ubuntu1 2019-06-12 16:35:39 remove liborc-0.4-0:i386 1:0.4.28-1 2019-06-12 16:35:40 remove libosmesa6:amd64 18.2.8-0ubuntu0~18.04.2 2019-06-12 16:35:40 remove libosmesa6:i386 18.2.8-0ubuntu0~18.04.2 2019-06-12 16:35:40 remove libp11-kit0:i386 0.23.9-2 2019-06-12 16:35:40 remove libpcap0.8:i386
[Desktop-packages] [Bug 1806697] Re: Status of interface connections not properly updated in the UI
** Also affects: gnome-software (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: gnome-software (Ubuntu Eoan) Importance: Medium Assignee: Robert Ancell (robert-ancell) Status: Confirmed ** Also affects: gnome-software (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: gnome-software (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: gnome-software (Ubuntu Disco) Importance: Undecided Status: New ** Changed in: gnome-software (Ubuntu Disco) Status: New => Triaged ** Changed in: gnome-software (Ubuntu Cosmic) Status: New => Triaged ** Changed in: gnome-software (Ubuntu Bionic) Status: New => Triaged ** Changed in: gnome-software (Ubuntu Xenial) Status: New => Triaged ** Changed in: gnome-software (Ubuntu Xenial) Assignee: (unassigned) => Robert Ancell (robert-ancell) ** Changed in: gnome-software (Ubuntu Bionic) Assignee: (unassigned) => Robert Ancell (robert-ancell) ** Changed in: gnome-software (Ubuntu Cosmic) Assignee: (unassigned) => Robert Ancell (robert-ancell) ** Changed in: gnome-software (Ubuntu Disco) Assignee: (unassigned) => Robert Ancell (robert-ancell) ** Changed in: gnome-software (Ubuntu Eoan) Status: Confirmed => Triaged ** Changed in: gnome-software (Ubuntu Disco) Importance: Undecided => High ** Changed in: gnome-software (Ubuntu Cosmic) Importance: Undecided => High ** Changed in: gnome-software (Ubuntu Bionic) Importance: Undecided => High ** Changed in: gnome-software (Ubuntu Xenial) Importance: Undecided => High ** Changed in: gnome-software (Ubuntu Eoan) Importance: Medium => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1806697 Title: Status of interface connections not properly updated in the UI Status in gnome-software package in Ubuntu: Triaged Status in gnome-software source package in Xenial: Triaged Status in gnome-software source package in Bionic: Triaged Status in gnome-software source package in Cosmic: Triaged Status in gnome-software source package in Disco: Triaged Status in gnome-software source package in Eoan: Triaged Bug description: Steps to reproduce the problem: 1. Go to the Chromium snap store page by e.g. right clicking on its icon and selecting Show details and then the specific app. 2. Press the Permissions button. 3. Press/slide the Read/write files on removable storage devices slider. 4. Close the permissions and the store window. 5. Reopen the windows. 6. The permission should be enabled, but it isn't. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1806697/+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 1832610] Re: [Dell Inspiron 5480] No sound at all
** Summary changed: - [HDA-Intel - HDA Intel PCH, playback] No sound at all + [Dell Inspiron 5480] No sound at all ** Summary changed: - [Dell Inspiron 5480] No sound at all + [Dell Inspiron 5480] No sound at all from internal speakers -- 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/1832610 Title: [Dell Inspiron 5480] No sound at all from internal speakers Status in pulseaudio package in Ubuntu: New Bug description: No sounds at internal speakers but headphones works ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.2 ProcVersionSignature: Ubuntu 4.15.0-1039.44-oem 4.15.18 Uname: Linux 4.15.0-1039-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: marcelo 10930 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Jun 12 13:00:36 2019 InstallationDate: Installed on 2019-06-03 (8 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Áudio interno - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1813 F pulseaudio marcelo 10930 F pulseaudio Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: No sound at all Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/24/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.2.0 dmi.board.name: 07G539 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.2.0:bd03/24/2019:svnDellInc.:pnInspiron5480:pvr:rvnDellInc.:rn07G539:rvrA01:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5480 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1832610/+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 1832449] Re: Right click menu does not appear near the mouse on multi-monitor setup
Sounds good. Thanks. ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Invalid -- 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/1832449 Title: Right click menu does not appear near the mouse on multi-monitor setup Status in gnome-shell package in Ubuntu: Invalid Bug description: I have an external monitor connected to a laptop via HDMI. If I set up the laptop display's position like this: https://imgur.com/oFbqnBm And open a new nautilus windows on my external monitor (which I've set to be primary), the right click context menu appears at some weird y-offset from where the mouse is: https://imgur.com/BfxUZVU However, when I set the position of the second monitor like so: https://imgur.com/yN6VzSI The right click menu appears where it is supposed to be. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-06-12 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Package: gnome-shell 3.32.1-1ubuntu1~19.04.1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 Tags: disco Uname: Linux 5.0.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1832449/+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 1832609] Re: i don't know speak EL
Can you please tell us (in any language) what problem with Ubuntu you are encountering? ** 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/1832609 Title: i don't know speak EL Status in Ubuntu: Incomplete Bug description: i don't know speak EL ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 Uname: Linux 5.0.0-16-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jun 12 22:45:21 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 5500 [1043:192d] Advanced Micro Devices, Inc. [AMD/ATI] Mars LE [Radeon HD 8530M / R5 M240] [1002:6607] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Mars LE [Radeon HD 8530M / R5 M240] [1043:192d] InstallationDate: Installed on 2019-06-12 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: ASUSTeK COMPUTER INC. X555LPB ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-16-generic root=UUID=57d9c032-5367-4516-862d-811dfda6989e ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/08/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X555LPB.301 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X555LPB 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.:bvrX555LPB.301:bd06/08/2015:svnASUSTeKCOMPUTERINC.:pnX555LPB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555LPB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X555LPB 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/+bug/1832609/+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 1825710] Re: Remove "Application is ready" notification
** Changed in: gnome-shell Status: Unknown => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1825710 Title: Remove "Application is ready" notification Status in GNOME Shell: New Status in gnome-shell package in Ubuntu: Confirmed Bug description: The "Application is ready" notification is pointless, really. Say, I click on the open downloads folder button in Firefox and GNOME Shell gives me a notification saying "Application is ready" but doesn't open the notification. I'm totally expecting an app to open because I actively initiated it. As a workaround, I'm using a GNOME extensions "Focus my Window" which removes the "Application is ready" message and focuses the app window automatically. However, this cannot be treated as a solution. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1825710/+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 1832426] Re: "Program" is not responding when debugging in gdb
I think gnome-shell could do better at ignoring programs being debugged. It appears you can detect this by looking at the process state like in /proc/PID/status. It will show: State: t (tracing stop) Or easier to parse: Look at /proc/PID/stat and the third field will be a lowercase 't'. This means the process is being debugged and gnome-shell should not be raising warnings about it. -- 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/1832426 Title: "Program" is not responding when debugging in gdb Status in gnome-shell package in Ubuntu: New Bug description: I believe this is a regression for bug 1740869: is not responding window is constantly showing when debugging a program I'm debugging my c++ sdl2 program in gdb and when I hit a breakpoint this window shows up and I can't get it to stop asking me to close the program. 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Description: Ubuntu 19.04 Release: 19.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center gnome-shell: Installed: 3.32.1-1ubuntu1~19.04.1 Candidate: 3.32.1-1ubuntu1~19.04.1 Version table: *** 3.32.1-1ubuntu1~19.04.1 500 500 http://us.archive.ubuntu.com/ubuntu disco-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.32.0+git20190410-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages 3) What you expected to happen When I hit a breakpoint in gdb, the program should stop. 4) What happened instead The program stops and ubuntu asks me if i want to kill the program. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.32.1-1ubuntu1~19.04.1 ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 Uname: Linux 5.0.0-16-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Jun 11 22:03:44 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-06-08 (4 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1832426/+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 1832004] Re: [amdgpu] display hanging after laptop opens lid
Thanks. Yes it sounds like a problem with the amdgpu graphics driver. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1832004 Title: [amdgpu] display hanging after laptop opens lid Status in xserver-xorg-video-amdgpu package in Ubuntu: Incomplete Bug description: ubuntu 19.04 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 Uname: Linux 5.0.0-16-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Toegang geweigerd: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jun 7 14:56:09 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu DkmsStatus: anbox, 1, 5.0.0-15-generic, x86_64: installed anbox, 1, 5.0.0-16-generic, x86_64: installed virtualbox, 6.0.6, 5.0.0-15-generic, x86_64: installed virtualbox, 6.0.6, 5.0.0-16-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Stoney [Radeon R2/R3/R4/R5 Graphics] [1002:98e4] (rev da) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Stoney [Radeon R2/R3/R4/R5 Graphics] [1043:1680] InstallationDate: Installed on 2018-08-03 (308 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: ASUSTeK COMPUTER INC. E402BA ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nl_NL.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-16-generic root=UUID=c593d94b-7cc0-45ca-a012-f79a49d00093 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/06/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E402BA.311 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: E402BA 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.:bvrE402BA.311:bd09/06/2018:svnASUSTeKCOMPUTERINC.:pnE402BA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE402BA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: E402BA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER 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 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-amdgpu/+bug/1832004/+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 1830792] Re: [i915] Rotated display is overscaled and overdrawn while i915 crashes repeatedly
Thanks for those logs. They show the problem happening immediately, as
soon as 2.5 seconds after the kernel starts.
This bug is now assigned to the kernel ('linux' component). I believe
this is a kernel bug, if not a hardware fault.
--
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/1830792
Title:
[i915] Rotated display is overscaled and overdrawn while i915 crashes
repeatedly
Status in gnome-shell package in Ubuntu:
Invalid
Status in linux package in Ubuntu:
Confirmed
Status in mutter package in Ubuntu:
Invalid
Status in xorg-server package in Ubuntu:
Invalid
Bug description:
On my system I have two display: one in landscape, and one in
portrait. The landscape display is fine, but the portrait display is
corrupted. If I unplug the display from the computer for some time and
then plug it back in it will occasionally fix the problem.
Once the problem is fixed, the display works perfectly fine,
indefinitely. However, as soon as I reboot the computer the display
will come up corrupted again and never recovers without many rounds of
plug/unplug turn off/turn on. It's extremely frustrating.
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: gnome-shell 3.32.0+git20190410-1ubuntu1
ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6
Uname: Linux 5.0.0-15-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue May 28 15:57:02 2019
DisplayManager: gdm3
GsettingsChanges:
b'org.gnome.shell' b'command-history' redacted by apport
b'org.gnome.shell' b'favorite-apps' redacted by apport
b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/usr/bin/fish
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to disco on 2019-04-22 (36 days ago)
modified.conffile..etc.logrotate.d.apport: [modified]
mtime.conffile..etc.logrotate.d.apport: 2019-01-12T15:50:59.090583
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1830792/+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 1825710] Re: Remove "Application is ready" notification
Tracking upstream in: https://gitlab.gnome.org/GNOME/gnome- shell/issues/358 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #358 https://gitlab.gnome.org/GNOME/gnome-shell/issues/358 ** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/gnome-shell/issues/358 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1825710 Title: Remove "Application is ready" notification Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Confirmed Bug description: The "Application is ready" notification is pointless, really. Say, I click on the open downloads folder button in Firefox and GNOME Shell gives me a notification saying "Application is ready" but doesn't open the notification. I'm totally expecting an app to open because I actively initiated it. As a workaround, I'm using a GNOME extensions "Focus my Window" which removes the "Application is ready" message and focuses the app window automatically. However, this cannot be treated as a solution. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1825710/+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 1832651] Re: jackdbus fails to start: cannot allocate memory
Is there a workaround? This is currently breaking my entire audio setup (using Ubuntu Studio, where jackd is crucial) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to jackd2 in Ubuntu. https://bugs.launchpad.net/bugs/1832651 Title: jackdbus fails to start: cannot allocate memory Status in systemd: Fix Released Status in jackd2 package in Ubuntu: Invalid Status in systemd package in Ubuntu: Confirmed Bug description: The `.log/jack/jackdbus.log` shows the following after trying to start/restart jack using "Ubuntu Studio Controls" (also tried using `jack_control start`): ERROR: Cannot lock down 82280346 byte memory area (Cannot allocate memory) This is a fresh install of Ubuntu Studio 19.04, installed via USB. The first thing I did after installing was check to see if jack was running, but unfortunately it's not working. The error would seem to indicate that I'm not in the `audio` group, however checking `groups` shows that I am in the audio group. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: jackd2 1.9.12~dfsg-2build1 ProcVersionSignature: Ubuntu 5.0.0-13.14-lowlatency 5.0.6 Uname: Linux 5.0.0-13-lowlatency x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Jun 12 18:13:25 2019 InstallationDate: Installed on 2019-06-12 (0 days ago) InstallationMedia: Ubuntu-Studio 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: jackd2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1832651/+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 1832651] Re: jackdbus fails to start: cannot allocate memory
@bendavis78 It's currently not possible. However, if you watch the natural progression of things, it's likely to land in Ubuntu 19.10 if the pattern of the past few releases holds. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to jackd2 in Ubuntu. https://bugs.launchpad.net/bugs/1832651 Title: jackdbus fails to start: cannot allocate memory Status in systemd: Fix Released Status in jackd2 package in Ubuntu: Invalid Status in systemd package in Ubuntu: Confirmed Bug description: The `.log/jack/jackdbus.log` shows the following after trying to start/restart jack using "Ubuntu Studio Controls" (also tried using `jack_control start`): ERROR: Cannot lock down 82280346 byte memory area (Cannot allocate memory) This is a fresh install of Ubuntu Studio 19.04, installed via USB. The first thing I did after installing was check to see if jack was running, but unfortunately it's not working. The error would seem to indicate that I'm not in the `audio` group, however checking `groups` shows that I am in the audio group. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: jackd2 1.9.12~dfsg-2build1 ProcVersionSignature: Ubuntu 5.0.0-13.14-lowlatency 5.0.6 Uname: Linux 5.0.0-13-lowlatency x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Jun 12 18:13:25 2019 InstallationDate: Installed on 2019-06-12 (0 days ago) InstallationMedia: Ubuntu-Studio 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: jackd2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1832651/+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 1832651] Re: jackdbus fails to start: cannot allocate memory
** Changed in: systemd Status: Unknown => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to jackd2 in Ubuntu. https://bugs.launchpad.net/bugs/1832651 Title: jackdbus fails to start: cannot allocate memory Status in systemd: Fix Released Status in jackd2 package in Ubuntu: Invalid Status in systemd package in Ubuntu: Confirmed Bug description: The `.log/jack/jackdbus.log` shows the following after trying to start/restart jack using "Ubuntu Studio Controls" (also tried using `jack_control start`): ERROR: Cannot lock down 82280346 byte memory area (Cannot allocate memory) This is a fresh install of Ubuntu Studio 19.04, installed via USB. The first thing I did after installing was check to see if jack was running, but unfortunately it's not working. The error would seem to indicate that I'm not in the `audio` group, however checking `groups` shows that I am in the audio group. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: jackd2 1.9.12~dfsg-2build1 ProcVersionSignature: Ubuntu 5.0.0-13.14-lowlatency 5.0.6 Uname: Linux 5.0.0-13-lowlatency x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Jun 12 18:13:25 2019 InstallationDate: Installed on 2019-06-12 (0 days ago) InstallationMedia: Ubuntu-Studio 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: jackd2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1832651/+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 1832651] Re: jackdbus fails to start: cannot allocate memory
How does one upgrade to systemd-241 in ubuntu? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to jackd2 in Ubuntu. https://bugs.launchpad.net/bugs/1832651 Title: jackdbus fails to start: cannot allocate memory Status in systemd: Unknown Status in jackd2 package in Ubuntu: Invalid Status in systemd package in Ubuntu: Confirmed Bug description: The `.log/jack/jackdbus.log` shows the following after trying to start/restart jack using "Ubuntu Studio Controls" (also tried using `jack_control start`): ERROR: Cannot lock down 82280346 byte memory area (Cannot allocate memory) This is a fresh install of Ubuntu Studio 19.04, installed via USB. The first thing I did after installing was check to see if jack was running, but unfortunately it's not working. The error would seem to indicate that I'm not in the `audio` group, however checking `groups` shows that I am in the audio group. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: jackd2 1.9.12~dfsg-2build1 ProcVersionSignature: Ubuntu 5.0.0-13.14-lowlatency 5.0.6 Uname: Linux 5.0.0-13-lowlatency x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Jun 12 18:13:25 2019 InstallationDate: Installed on 2019-06-12 (0 days ago) InstallationMedia: Ubuntu-Studio 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: jackd2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1832651/+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 1832449] Re: Right click menu does not appear near the mouse on multi-monitor setup
Oh my goodness. I just found out the culprit was the Gnome extension "Multi Monitors Add-On". I had originally installed this extension so that I can have the top bar on both monitors. But after disabling it, right click menus works fine ! I'm going to file a bug report with the author of that extension. -- 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/1832449 Title: Right click menu does not appear near the mouse on multi-monitor setup Status in gnome-shell package in Ubuntu: Incomplete Bug description: I have an external monitor connected to a laptop via HDMI. If I set up the laptop display's position like this: https://imgur.com/oFbqnBm And open a new nautilus windows on my external monitor (which I've set to be primary), the right click context menu appears at some weird y-offset from where the mouse is: https://imgur.com/BfxUZVU However, when I set the position of the second monitor like so: https://imgur.com/yN6VzSI The right click menu appears where it is supposed to be. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-06-12 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Package: gnome-shell 3.32.1-1ubuntu1~19.04.1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 Tags: disco Uname: Linux 5.0.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1832449/+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 1832449] Re: Right click menu does not appear near the mouse on multi-monitor setup
I'm not sure if this is relevant, but I'm adding that my laptop's display resolution has been set to 1368 x 768 even though it supports 1920 x 1080. -- 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/1832449 Title: Right click menu does not appear near the mouse on multi-monitor setup Status in gnome-shell package in Ubuntu: Incomplete Bug description: I have an external monitor connected to a laptop via HDMI. If I set up the laptop display's position like this: https://imgur.com/oFbqnBm And open a new nautilus windows on my external monitor (which I've set to be primary), the right click context menu appears at some weird y-offset from where the mouse is: https://imgur.com/BfxUZVU However, when I set the position of the second monitor like so: https://imgur.com/yN6VzSI The right click menu appears where it is supposed to be. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-06-12 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Package: gnome-shell 3.32.1-1ubuntu1~19.04.1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 Tags: disco Uname: Linux 5.0.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1832449/+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 1832449] Re: Right click menu on nautilus does not appear near the mouse
Thanks for helping to resolve this problem. I've notice that it's not just nautilus, right click menus are all other apps appear at an offset as well. And it happens to be the offset that is the distance between the cursor's y position and the top of the smaller monitor. Here it is described in a picture: https://imgur.com/uaM1KOM I'm on X11 and gdm3 display manager. ** Summary changed: - Right click menu on nautilus does not appear near the mouse + Right click menu does not appear near the mouse on multi-monitor setup -- 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/1832449 Title: Right click menu does not appear near the mouse on multi-monitor setup Status in gnome-shell package in Ubuntu: Incomplete Bug description: I have an external monitor connected to a laptop via HDMI. If I set up the laptop display's position like this: https://imgur.com/oFbqnBm And open a new nautilus windows on my external monitor (which I've set to be primary), the right click context menu appears at some weird y-offset from where the mouse is: https://imgur.com/BfxUZVU However, when I set the position of the second monitor like so: https://imgur.com/yN6VzSI The right click menu appears where it is supposed to be. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-06-12 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Package: gnome-shell 3.32.1-1ubuntu1~19.04.1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 Tags: disco Uname: Linux 5.0.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1832449/+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 1832651] Re: jackdbus fails to start: cannot allocate memory
Looks as though this was reported [1], and turns out is actually a bug in systemd <=240 [2]. Shows as fixed in systemd 241 [3]. [1] https://github.com/jackaudio/jack2/issues/429 [1] https://github.com/systemd/systemd/issues/11386 [2] https://github.com/systemd/systemd/pull/11448 ** Bug watch added: github.com/jackaudio/jack2/issues #429 https://github.com/jackaudio/jack2/issues/429 ** Also affects: jack via https://github.com/jackaudio/jack2/issues/429 Importance: Unknown Status: Unknown ** Also affects: systemd (Ubuntu) Importance: Undecided Status: New ** Bug watch added: github.com/systemd/systemd/issues #11386 https://github.com/systemd/systemd/issues/11386 ** No longer affects: jack ** Changed in: jackd2 (Ubuntu) Status: New => Invalid ** Changed in: systemd (Ubuntu) Status: New => Confirmed ** Also affects: systemd via https://github.com/systemd/systemd/issues/11386 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to jackd2 in Ubuntu. https://bugs.launchpad.net/bugs/1832651 Title: jackdbus fails to start: cannot allocate memory Status in systemd: Unknown Status in jackd2 package in Ubuntu: Invalid Status in systemd package in Ubuntu: Confirmed Bug description: The `.log/jack/jackdbus.log` shows the following after trying to start/restart jack using "Ubuntu Studio Controls" (also tried using `jack_control start`): ERROR: Cannot lock down 82280346 byte memory area (Cannot allocate memory) This is a fresh install of Ubuntu Studio 19.04, installed via USB. The first thing I did after installing was check to see if jack was running, but unfortunately it's not working. The error would seem to indicate that I'm not in the `audio` group, however checking `groups` shows that I am in the audio group. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: jackd2 1.9.12~dfsg-2build1 ProcVersionSignature: Ubuntu 5.0.0-13.14-lowlatency 5.0.6 Uname: Linux 5.0.0-13-lowlatency x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Jun 12 18:13:25 2019 InstallationDate: Installed on 2019-06-12 (0 days ago) InstallationMedia: Ubuntu-Studio 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: jackd2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1832651/+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 1832449] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1832449/+attachment/5270474/+files/ProcCpuinfoMinimal.txt -- 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/1832449 Title: Right click menu on nautilus does not appear near the mouse Status in gnome-shell package in Ubuntu: Incomplete Bug description: I have an external monitor connected to a laptop via HDMI. If I set up the laptop display's position like this: https://imgur.com/oFbqnBm And open a new nautilus windows on my external monitor (which I've set to be primary), the right click context menu appears at some weird y-offset from where the mouse is: https://imgur.com/BfxUZVU However, when I set the position of the second monitor like so: https://imgur.com/yN6VzSI The right click menu appears where it is supposed to be. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-06-12 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Package: gnome-shell 3.32.1-1ubuntu1~19.04.1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 Tags: disco Uname: Linux 5.0.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1832449/+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 1832449] Re: Right click menu on nautilus does not appear near the mouse
apport information ** Tags added: apport-collected disco ** Description changed: I have an external monitor connected to a laptop via HDMI. If I set up the laptop display's position like this: https://imgur.com/oFbqnBm And open a new nautilus windows on my external monitor (which I've set to be primary), the right click context menu appears at some weird y-offset from where the mouse is: https://imgur.com/BfxUZVU However, when I set the position of the second monitor like so: https://imgur.com/yN6VzSI The right click menu appears where it is supposed to be. + --- + ProblemType: Bug + ApportVersion: 2.20.10-0ubuntu27 + Architecture: amd64 + CurrentDesktop: ubuntu:GNOME + DisplayManager: gdm3 + DistroRelease: Ubuntu 19.04 + InstallationDate: Installed on 2019-06-12 (0 days ago) + InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) + Package: gnome-shell 3.32.1-1ubuntu1~19.04.1 + PackageArchitecture: amd64 + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 + Tags: disco + Uname: Linux 5.0.0-16-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1832449/+attachment/5270472/+files/Dependencies.txt -- 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/1832449 Title: Right click menu on nautilus does not appear near the mouse Status in gnome-shell package in Ubuntu: Incomplete Bug description: I have an external monitor connected to a laptop via HDMI. If I set up the laptop display's position like this: https://imgur.com/oFbqnBm And open a new nautilus windows on my external monitor (which I've set to be primary), the right click context menu appears at some weird y-offset from where the mouse is: https://imgur.com/BfxUZVU However, when I set the position of the second monitor like so: https://imgur.com/yN6VzSI The right click menu appears where it is supposed to be. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-06-12 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Package: gnome-shell 3.32.1-1ubuntu1~19.04.1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 Tags: disco Uname: Linux 5.0.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1832449/+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 1832449] GsettingsChanges.txt
apport information ** Attachment added: "GsettingsChanges.txt" https://bugs.launchpad.net/bugs/1832449/+attachment/5270473/+files/GsettingsChanges.txt -- 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/1832449 Title: Right click menu on nautilus does not appear near the mouse Status in gnome-shell package in Ubuntu: Incomplete Bug description: I have an external monitor connected to a laptop via HDMI. If I set up the laptop display's position like this: https://imgur.com/oFbqnBm And open a new nautilus windows on my external monitor (which I've set to be primary), the right click context menu appears at some weird y-offset from where the mouse is: https://imgur.com/BfxUZVU However, when I set the position of the second monitor like so: https://imgur.com/yN6VzSI The right click menu appears where it is supposed to be. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-06-12 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Package: gnome-shell 3.32.1-1ubuntu1~19.04.1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 Tags: disco Uname: Linux 5.0.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1832449/+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 1832656] [NEW] chromium-browser deb->snap transition breaks ubuntukylin image builds
Public bug reported: >From https://launchpad.net/~ubuntu- cdimage/+livefs/ubuntu/eoan/ubuntukylin/+build/169881: Preparing to unpack .../000-chromium-browser_75.0.3770.80-0ubuntu1~snap2_amd64.deb ... => Installing the chromium snap ==> Checking connectivity with the snap store ===> Unable to contact the store, trying every minute for the next 30 minutes ===> Still unable to contact the store, trying for another 20 minutes ===> Still unable to contact the store, trying for another 10 minutes ===> Still unable to contact the store, aborting dpkg: error processing archive /tmp/apt-dpkg-install-43SUPL/000-chromium-browser_75.0.3770.80-0ubuntu1~snap2_amd64.deb (--unpack): new chromium-browser package pre-installation script subprocess returned error exit status 1 It is possible that the flavors should switch to seeding the snap instead of the deb. However, it's unclear to me why the deb is failing to talk to the Snap Store, because seeding of snaps DOES work from within image builds. ** Affects: chromium-browser (Ubuntu) Importance: High Status: New ** Affects: ubuntukylin-meta (Ubuntu) Importance: High Status: New ** Affects: chromium-browser (Ubuntu Eoan) Importance: High Status: New ** Affects: ubuntukylin-meta (Ubuntu Eoan) Importance: High Status: New ** Also affects: chromium-browser (Ubuntu Eoan) Importance: Undecided Status: New ** Changed in: chromium-browser (Ubuntu Eoan) Importance: Undecided => High ** Also affects: ubuntukylin-meta (Ubuntu) Importance: Undecided Status: New ** Changed in: ubuntukylin-meta (Ubuntu Eoan) Importance: Undecided => High -- 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/1832656 Title: chromium-browser deb->snap transition breaks ubuntukylin image builds Status in chromium-browser package in Ubuntu: New Status in ubuntukylin-meta package in Ubuntu: New Status in chromium-browser source package in Eoan: New Status in ubuntukylin-meta source package in Eoan: New Bug description: From https://launchpad.net/~ubuntu- cdimage/+livefs/ubuntu/eoan/ubuntukylin/+build/169881: Preparing to unpack .../000-chromium-browser_75.0.3770.80-0ubuntu1~snap2_amd64.deb ... => Installing the chromium snap ==> Checking connectivity with the snap store ===> Unable to contact the store, trying every minute for the next 30 minutes ===> Still unable to contact the store, trying for another 20 minutes ===> Still unable to contact the store, trying for another 10 minutes ===> Still unable to contact the store, aborting dpkg: error processing archive /tmp/apt-dpkg-install-43SUPL/000-chromium-browser_75.0.3770.80-0ubuntu1~snap2_amd64.deb (--unpack): new chromium-browser package pre-installation script subprocess returned error exit status 1 It is possible that the flavors should switch to seeding the snap instead of the deb. However, it's unclear to me why the deb is failing to talk to the Snap Store, because seeding of snaps DOES work from within image builds. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1832656/+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 1829566] Re: network-manager 1.10.14-0ubuntu2 ignores systemd-resolved configured dns
** Tags removed: regression-update ** Tags added: regression-proposed ** Changed in: network-manager (Ubuntu) Status: Incomplete => Triaged ** Changed in: network-manager (Ubuntu Bionic) Status: Incomplete => Triaged -- 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/1829566 Title: network-manager 1.10.14-0ubuntu2 ignores systemd-resolved configured dns Status in network-manager package in Ubuntu: Triaged Status in network-manager source package in Bionic: Triaged Bug description: On 18.04.2 the `upgrade network-manager:amd64 1.10.6-2ubuntu1.1 1.10.14-0ubuntu2` lead to scoped DNS servers defined in `/etc/systemd/resolved.conf.d/*.conf` being ignored. Downgrading with `sudo apt-get install network- manager=1.10.6-2ubuntu1.1` has resolved the issue for now. Example systemd-resolved conf: [Resolve] Cache=no DNS=127.0.0.54 Domains=~.local.org.com Where 127.0.0.54:53 is bound to a dnsmasq server capable of resolving queries in that subdomain. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1829566/+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 1832651] [NEW] jackdbus fails to start: cannot allocate memory
Public bug reported: The `.log/jack/jackdbus.log` shows the following after trying to start/restart jack using "Ubuntu Studio Controls" (also tried using `jack_control start`): ERROR: Cannot lock down 82280346 byte memory area (Cannot allocate memory) This is a fresh install of Ubuntu Studio 19.04, installed via USB. The first thing I did after installing was check to see if jack was running, but unfortunately it's not working. The error would seem to indicate that I'm not in the `audio` group, however checking `groups` shows that I am in the audio group. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: jackd2 1.9.12~dfsg-2build1 ProcVersionSignature: Ubuntu 5.0.0-13.14-lowlatency 5.0.6 Uname: Linux 5.0.0-13-lowlatency x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Jun 12 18:13:25 2019 InstallationDate: Installed on 2019-06-12 (0 days ago) InstallationMedia: Ubuntu-Studio 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: jackd2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: jackd2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to jackd2 in Ubuntu. https://bugs.launchpad.net/bugs/1832651 Title: jackdbus fails to start: cannot allocate memory Status in jackd2 package in Ubuntu: New Bug description: The `.log/jack/jackdbus.log` shows the following after trying to start/restart jack using "Ubuntu Studio Controls" (also tried using `jack_control start`): ERROR: Cannot lock down 82280346 byte memory area (Cannot allocate memory) This is a fresh install of Ubuntu Studio 19.04, installed via USB. The first thing I did after installing was check to see if jack was running, but unfortunately it's not working. The error would seem to indicate that I'm not in the `audio` group, however checking `groups` shows that I am in the audio group. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: jackd2 1.9.12~dfsg-2build1 ProcVersionSignature: Ubuntu 5.0.0-13.14-lowlatency 5.0.6 Uname: Linux 5.0.0-13-lowlatency x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Jun 12 18:13:25 2019 InstallationDate: Installed on 2019-06-12 (0 days ago) InstallationMedia: Ubuntu-Studio 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: jackd2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/1832651/+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 1831091] Re: hp-plugin tries to put files into readonly /usr/lib(64) on Fedora Silverblue
Oh what timing, just discovered this problem today and both my personal and work computers are running Silverblue. It would be helpful if redistribution were permitted (no modification needed) for the binaries so rpmfusion packages can be created: https://bugs.launchpad.net/hplip/+bug/1214318 ** Also affects: hplip (Ubuntu) Importance: Undecided Status: New ** No longer affects: hplip (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1831091 Title: hp-plugin tries to put files into readonly /usr/lib(64) on Fedora Silverblue Status in HPLIP: In Progress Bug description: Hi! we have an issue on Fedora Silverblue https://bugzilla.redhat.com/show_bug.cgi?id=1695713 - Silverblue is new type of OS, which is based on flatpack and rpm-ostree, and its feature is to have /usr directory as readonly (only /usr/local is writeable, because it is symlink to /var/local). AFAIK it can be solved by two means: 1) patch internal plugin script to put binary blobs into /usr/local by default/only on Silverblue and change the code to look there for those libraries (this way it would be needed to patch sane-backends too, so it is not very good solution) 2) openly share binary blobs which acts as plugins - this way we can pack it into package and Silverblue can have it installed (PREFFERED) Would you mind looking into it? It is kind of critical issue on Silverblue, because all devices which needs plugin to work are unusable. Thank you in advance, Zdenek HPLIP maintainer in Fedora/RHEL To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/1831091/+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 1740894] Re: KEY_RFKILL is not passed to userspace
Switched back to verification-failed-bionic since comment #42 has not been addressed. ** Tags removed: verification-done-bionic ** Tags added: verification-failed-bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorgproto in Ubuntu. https://bugs.launchpad.net/bugs/1740894 Title: KEY_RFKILL is not passed to userspace Status in libxkbcommon package in Ubuntu: Fix Released Status in xkeyboard-config package in Ubuntu: Fix Released Status in xorgproto package in Ubuntu: Fix Released Status in libxkbcommon source package in Bionic: Fix Released Status in xkeyboard-config source package in Bionic: Fix Committed Status in xorgproto source package in Bionic: Fix Released Status in libxkbcommon source package in Cosmic: Fix Released Status in xkeyboard-config source package in Cosmic: Fix Released Status in xorgproto source package in Cosmic: Fix Released Bug description: * Impact the airplane mode key doesn't work in GNOME * Test case Use a laptop with a key to activate airplane mode, it should toggle the corresponding mode on/off when used * Regression potential The change adds a new key definition but doesn't touch any existing one, nothing specific to test out of the new key working - There are a couple things going on, that could be fixed by a Debian or Ubuntu maintainer: - libxkbdcommon needs to be updated from 0.7.1 to 0.7.2. This introduces the RFKill key: https://lists.freedesktop.org/archives /wayland-devel/2017-August/034721.html - x11-proto needs a new release. This commit added RFKill, but it is not in a release: https://cgit.freedesktop.org/xorg/proto/xproto/commit/?id=98a32d328e7195e12c38baa877917335bceffbaf - Likely other X11 packages need to be rebuilt. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxkbcommon/+bug/1740894/+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 1646762] Re: /usr/bin/gedit:11:g_type_check_instance_cast:GEDIT_OPEN_DOCUMENT_SELECTOR:real_populate_liststore:gdk_threads_dispatch:g_main_dispatch
This bug was fixed in the package gedit - 3.28.1-1ubuntu1.2 --- gedit (3.28.1-1ubuntu1.2) bionic; urgency=medium * debian/oatches/gitlab_idle_handling.patch: - use gitlab pr#34's patch to fix an incorrect handling of idle callbacks, thanks Andrea Azzarone (lp: #1646762) -- Sebastien Bacher Thu, 11 Apr 2019 16:25:40 +0200 ** Changed in: gedit (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1646762 Title: /usr/bin/gedit:11:g_type_check_instance_cast:GEDIT_OPEN_DOCUMENT_SELECTOR:real_populate_liststore:gdk_threads_dispatch:g_main_dispatch Status in gedit package in Ubuntu: Fix Released Status in gedit source package in Bionic: Fix Released Status in gedit source package in Cosmic: Fix Released Bug description: * Impact Gedit segfaults in some cases * Test case We don't have specific steps to trigger the issue but the fix is right on principle. Check that error reports stop and that there is no regression https://errors.ubuntu.com/problem/d7c6f86d74e0c09c473b25deddf3001a01dbf4db * Regression potential The change is in the 'open document selector' source so test that the popover UI to open recent files is still working as it should --- The Ubuntu Error Tracker has been receiving reports about a problem regarding gedit. This problem was most recently seen with package version 3.22.0-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/d7c6f86d74e0c09c473b25deddf3001a01dbf4db contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1646762/+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 1832646] [NEW] Printing to Brother_HL_L8260CDW_series outputs garbage
Public bug reported: Today I ran the software updater and rebooted. I now find that I am unable to print to Brother_HL_L8260CDW_series printer; all I get is garbage and a lot of wasted paper. I am printing plain text. I have tried printing it from Evolution, Mousepad, and by piping it into lpr. Power cycling the printer does not help. I can print successfully from another PC with a native 18.04 installation (not upgraded from 16.xx). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cups 2.2.7-1ubuntu2.6 ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18 Uname: Linux 4.15.0-51-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CupsErrorLog: E [12/Jun/2019:21:31:10 +0100] [Job 96] Print job canceled at printer. E [12/Jun/2019:21:35:13 +0100] [Job 98] Print job canceled at printer. CurrentDesktop: XFCE Date: Wed Jun 12 21:39:03 2019 InstallationDate: Installed on 2018-02-09 (488 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Lpstat: device for Brother_HL_L8260CDW_series: ipp://BRN3C2AF4345B8C.local:631/ipp/print device for HPLJ4: socket://192.168.1.3:9100 MachineType: LENOVO 20CJS0UU00 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HPLJ4.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HPLJ4.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-51-generic root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: cups UpgradeStatus: Upgraded to bionic on 2018-09-12 (272 days ago) dmi.bios.date: 09/13/2017 dmi.bios.vendor: LENOVO dmi.bios.version: N11ET42W (1.18 ) dmi.board.asset.tag: Not Available dmi.board.name: 20CJS0UU00 dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: R90G3N7R dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN11ET42W(1.18):bd09/13/2017:svnLENOVO:pn20CJS0UU00:pvrThinkPadT550:rvnLENOVO:rn20CJS0UU00:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T550 dmi.product.name: 20CJS0UU00 dmi.product.version: ThinkPad T550 dmi.sys.vendor: LENOVO ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apparmor apport-bug bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1832646 Title: Printing to Brother_HL_L8260CDW_series outputs garbage Status in cups package in Ubuntu: New Bug description: Today I ran the software updater and rebooted. I now find that I am unable to print to Brother_HL_L8260CDW_series printer; all I get is garbage and a lot of wasted paper. I am printing plain text. I have tried printing it from Evolution, Mousepad, and by piping it into lpr. Power cycling the printer does not help. I can print successfully from another PC with a native 18.04 installation (not upgraded from 16.xx). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cups 2.2.7-1ubuntu2.6 ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18 Uname: Linux 4.15.0-51-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CupsErrorLog: E [12/Jun/2019:21:31:10 +0100] [Job 96] Print job canceled at printer. E [12/Jun/2019:21:35:13 +0100] [Job 98] Print job canceled at printer. CurrentDesktop: XFCE Date: Wed Jun 12 21:39:03 2019 InstallationDate: Installed on 2018-02-09 (488 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Lpstat: device for Brother_HL_L8260CDW_series: ipp://BRN3C2AF4345B8C.local:631/ipp/print device for HPLJ4: socket://192.168.1.3:9100 MachineType: LENOVO 20CJS0UU00 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HPLJ4.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HPLJ4.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-51-generic root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: cups UpgradeStatus: Upgraded to bionic on 2018-09-12 (272 days ago) dmi.bios.date: 09/13/2017 dmi.bios.vendor: LENOVO dmi.bios.version: N11ET42W (1.18 ) dmi.board.asset.tag: Not Available dmi.board.name: 20CJS0UU00 dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: R90G3N7R dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN11ET42W(1.18):bd09/13/2017:svnLENOVO:pn20CJS0UU00:pvrThinkPadT550:rvnLENOVO:rn20CJS0UU00:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T550 dmi.product.name: 20CJS0UU00 dmi.product.version: ThinkPad T550 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1832646/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to :
[Desktop-packages] [Bug 1830792] Re: [i915] Rotated display is overscaled and overdrawn while i915 crashes repeatedly
** Attachment added: "journalctl -b0 from successful screen activation" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1830792/+attachment/5270412/+files/journal.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1830792 Title: [i915] Rotated display is overscaled and overdrawn while i915 crashes repeatedly Status in gnome-shell package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Invalid Bug description: On my system I have two display: one in landscape, and one in portrait. The landscape display is fine, but the portrait display is corrupted. If I unplug the display from the computer for some time and then plug it back in it will occasionally fix the problem. Once the problem is fixed, the display works perfectly fine, indefinitely. However, as soon as I reboot the computer the display will come up corrupted again and never recovers without many rounds of plug/unplug turn off/turn on. It's extremely frustrating. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.32.0+git20190410-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 Uname: Linux 5.0.0-15-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue May 28 15:57:02 2019 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'command-history' redacted by apport b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/fish SourcePackage: gnome-shell UpgradeStatus: Upgraded to disco on 2019-04-22 (36 days ago) modified.conffile..etc.logrotate.d.apport: [modified] mtime.conffile..etc.logrotate.d.apport: 2019-01-12T15:50:59.090583 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1830792/+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 1830792] Re: [i915] Rotated display is overscaled and overdrawn while i915 crashes repeatedly
This time I turned off the displayed, unplugged it, then left it unplugged while I rebooted. After rebooting and logging in, I turned on the display and plugged it in. Attached is the dmesg from this boot. ** Attachment added: "dmesg from functional boot" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1830792/+attachment/5270411/+files/dmesg.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1830792 Title: [i915] Rotated display is overscaled and overdrawn while i915 crashes repeatedly Status in gnome-shell package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Invalid Bug description: On my system I have two display: one in landscape, and one in portrait. The landscape display is fine, but the portrait display is corrupted. If I unplug the display from the computer for some time and then plug it back in it will occasionally fix the problem. Once the problem is fixed, the display works perfectly fine, indefinitely. However, as soon as I reboot the computer the display will come up corrupted again and never recovers without many rounds of plug/unplug turn off/turn on. It's extremely frustrating. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.32.0+git20190410-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 Uname: Linux 5.0.0-15-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue May 28 15:57:02 2019 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'command-history' redacted by apport b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/fish SourcePackage: gnome-shell UpgradeStatus: Upgraded to disco on 2019-04-22 (36 days ago) modified.conffile..etc.logrotate.d.apport: [modified] mtime.conffile..etc.logrotate.d.apport: 2019-01-12T15:50:59.090583 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1830792/+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 1832426] Re: "Program" is not responding when debugging in gdb
Hi Marco, No, the warning/dialog shows repeatedly. I think if I'm debugging a program, ubuntu and gnome-shell should never tell me the window is not responding. I might focus the window to use it, or to set it above all others so I can watch it. Thanks -- 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/1832426 Title: "Program" is not responding when debugging in gdb Status in gnome-shell package in Ubuntu: New Bug description: I believe this is a regression for bug 1740869: is not responding window is constantly showing when debugging a program I'm debugging my c++ sdl2 program in gdb and when I hit a breakpoint this window shows up and I can't get it to stop asking me to close the program. 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Description: Ubuntu 19.04 Release: 19.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center gnome-shell: Installed: 3.32.1-1ubuntu1~19.04.1 Candidate: 3.32.1-1ubuntu1~19.04.1 Version table: *** 3.32.1-1ubuntu1~19.04.1 500 500 http://us.archive.ubuntu.com/ubuntu disco-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.32.0+git20190410-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages 3) What you expected to happen When I hit a breakpoint in gdb, the program should stop. 4) What happened instead The program stops and ubuntu asks me if i want to kill the program. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.32.1-1ubuntu1~19.04.1 ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 Uname: Linux 5.0.0-16-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Jun 11 22:03:44 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-06-08 (4 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1832426/+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 1832632] [NEW] building from source on Ubuntu 18.04 fails
Public bug reported: Trying to build gtk+3.0-3.22.30 from source fails. I got the source using package gtk-3-examples. $ apt policy gtk-3-examples gtk-3-examples: Installed: 3.22.30-1ubuntu3 Candidate: 3.22.30-1ubuntu3 Version table: *** 3.22.30-1ubuntu3 500 500 http://il.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.22.30-1ubuntu1 500 500 http://il.archive.ubuntu.com/ubuntu bionic/main amd64 Packages Ubuntu version: Description:Ubuntu 18.04.2 LTS Release:18.04 Steps to reproduce: apt source gtk-3-examples sudo apt build-dep gtk-3-examples sudo apt install devscripts cd gtk+3.0-3.22.30 debuild -i -us -uc -d -b 2>&1 | tee build.log The build failed. First error (to the best of my knowledge): ERROR:../../../../../testsuite/gtk/scrolledwindow.c:100:test_size: assertion failed (min_size == MIN_SIZE): (153 == 150) FAIL Attached is the build log (build.log) ** Affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New ** Attachment added: "log of the build" https://bugs.launchpad.net/bugs/1832632/+attachment/5270405/+files/build.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1832632 Title: building from source on Ubuntu 18.04 fails Status in gtk+3.0 package in Ubuntu: New Bug description: Trying to build gtk+3.0-3.22.30 from source fails. I got the source using package gtk-3-examples. $ apt policy gtk-3-examples gtk-3-examples: Installed: 3.22.30-1ubuntu3 Candidate: 3.22.30-1ubuntu3 Version table: *** 3.22.30-1ubuntu3 500 500 http://il.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.22.30-1ubuntu1 500 500 http://il.archive.ubuntu.com/ubuntu bionic/main amd64 Packages Ubuntu version: Description: Ubuntu 18.04.2 LTS Release: 18.04 Steps to reproduce: apt source gtk-3-examples sudo apt build-dep gtk-3-examples sudo apt install devscripts cd gtk+3.0-3.22.30 debuild -i -us -uc -d -b 2>&1 | tee build.log The build failed. First error (to the best of my knowledge): ERROR:../../../../../testsuite/gtk/scrolledwindow.c:100:test_size: assertion failed (min_size == MIN_SIZE): (153 == 150) FAIL Attached is the build log (build.log) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1832632/+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 1832374] Re: Media keys stop working due to missing service file
** Changed in: gnome-settings-daemon Status: Unknown => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1832374 Title: Media keys stop working due to missing service file Status in GNOME Settings Daemon: New Status in gnome-settings-daemon package in Ubuntu: New Bug description: Over the last two releases I've noticed that if you have an audio player such as Clementine running, pause the audio playback and watch a video via VLC or SMPlayer and then close the video player and try to use the media keys again, the following is logged to journald: gsd-media-keys[2607]: Error calling method GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.mpris.MediaPlayer2.smplayer was not provided by any .service files. From what I can see is that a service file is created for the media keys for SMPlayer, when SMPlayer is closed that service file is removed and then media keys are still bound to that service. I get the above output for previous track, stop, play, pause and next track media keys. I do get the following output if neither is SMPlayer or Clementine is running or if Clementine is running and playing audio and SMPlayer is open, but no video is loaded: org.gnome.Shell.desktop[2480]: Window manager warning: Overwriting existing binding of keysym ffb5 with keysym ffb5 (keycode 54). org.gnome.Shell.desktop[2480]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a-e,12,f,10,11) <-- I collapsed the range into a comma separated list If you re-open SMPlayer and load a video, the media keys work and the GDBus error doesn't occur but the above "Overwriting ..." messages still get logged. Closing SMPlayer again does not restore media keys so that Clementine can handle them. I had SMPlayer running ~17 hours ago. Doing a shell reload doesn't seem to fix this either. I can't really tell if this is an SMPlay/VLC/Video Player issue or actually an issue in GSD, so filing here until someone can reassign to the relevant project. I hit this a while ago, while trying to get some debugging information for a Clementine bug: https://github.com/clementine- player/Clementine/issues/6320 If you need any other information let me know. Thanks ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-settings-daemon 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 Uname: Linux 5.0.0-16-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Jun 11 17:36:07 2019 InstallationDate: Installed on 2019-02-01 (129 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20181202) SourcePackage: gnome-settings-daemon UpgradeStatus: Upgraded to disco on 2019-04-09 (63 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1832374/+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 1726129] Re: nautilus crashed with SIGSEGV in widget_needs_widget_path
** Tags added: eoan -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1726129 Title: nautilus crashed with SIGSEGV in widget_needs_widget_path Status in nautilus package in Ubuntu: Expired Bug description: https://errors.ubuntu.com/problem/7c06cf06fd970ce31033f0d775b3adf97559e4ea --- . ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: nautilus 1:3.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CrashCounter: 1 CurrentDesktop: Budgie:GNOME Date: Sun Oct 22 15:30:05 2017 ExecutablePath: /usr/bin/nautilus InstallationDate: Installed on 2017-10-19 (3 days ago) InstallationMedia: Ubuntu-Budgie 17.10 "Artful Aardvark" - Release amd64 (20171017.1) ProcCmdline: nautilus --new-window ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7fe0115bd2a4:mov0x380(%rax),%rax PC (0x7fe0115bd2a4) ok source "0x380(%rax)" (0x0380) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: nautilus StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 Title: nautilus crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1726129/+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 1751508] Re: Xwayland crashed with SIGABRT in OsAbort() from AbortServer() from FatalError("Couldn't add screen\n") from InitOutput()
** Tags added: eoan
--
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/1751508
Title:
Xwayland crashed with SIGABRT in OsAbort() from AbortServer() from
FatalError("Couldn't add screen\n") from InitOutput()
Status in xorg-server package in Ubuntu:
Confirmed
Bug description:
Xorg crashed with VS Code.
ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: xwayland 2:1.19.6-1ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
Uname: Linux 4.15.0-10-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CompizPlugins: No value set for
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CrashCounter: 1
CurrentDesktop: GNOME-Greeter:GNOME
Date: Sat Feb 24 18:28:10 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExecutablePath: /usr/bin/Xwayland
GraphicsCard:
Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA
controller])
Subsystem: Lenovo HD Graphics 5500 [17aa:3820]
InstallationDate: Installed on 2018-02-24 (0 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222)
MachineType: LENOVO 80NE
ProcCmdline: /usr/bin/Xwayland :1024 -rootless -terminate -core -listen 4
-listen 5 -displayfd 6
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed
root=UUID=0beb58c8-0bf5-4e01-95dd-ae78f4ce0dea ro quiet splash vt.handoff=1
Signal: 6
SourcePackage: xorg-server
StacktraceTop:
OsAbort ()
?? ()
FatalError ()
InitOutput ()
?? ()
Title: Xwayland crashed with SIGABRT in OsAbort()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
dmi.bios.date: 09/09/2015
dmi.bios.vendor: Lenovo
dmi.bios.version: BDCN61WW
dmi.board.asset.tag: No Asset Tag
dmi.board.name: Lenovo Yoga 500-14IBD
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40688 WIN
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo Yoga 500-14IBD
dmi.modalias:
dmi:bvnLenovo:bvrBDCN61WW:bd09/09/2015:svnLENOVO:pn80NE:pvrLenovoYoga500-14IBD:rvnLENOVO:rnLenovoYoga500-14IBD:rvrSDK0J40688WIN:cvnLENOVO:ct10:cvrLenovoYoga500-14IBD:
dmi.product.family: IDEAPAD
dmi.product.name: 80NE
dmi.product.version: Lenovo Yoga 500-14IBD
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.90-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.3.3-0ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 17.3.3-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1751508/+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 1424201] Re: Web browsers lacking hardware-accelerated video decoding
** Changed in: firefox Importance: Medium => Unknown ** Changed in: firefox Status: Invalid => Unknown ** Changed in: firefox Remote watch: Mozilla Bugzilla #563206 => Mozilla Bugzilla #1210727 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1424201 Title: Web browsers lacking hardware-accelerated video decoding Status in Chromium Browser: Unknown Status in Mozilla Firefox: Unknown Status in chromium-browser package in Ubuntu: Confirmed Status in firefox package in Ubuntu: Confirmed Status in chromium-browser package in CentOS: Unknown Bug description: The chromium team has done a great job to totally disable hardware decoding on Linux. Even ignoring the GPU blacklist does not enable GPU decoding. How ever the patch is quite simple and it's already working using this PPA ( using libVA ) : https://launchpad.net/~saiarcot895/+archive/ubuntu/chromium-dev the corresponding patch is here : http://bazaar.launchpad.net/~saiarcot895/chromium-browser/chromium- browser.trusty.beta/view/head:/debian/patches/enable_vaapi_on_linux.diff that would be great if we could have this patch indefault Ubuntu chromium build, this situation is really sad right now, google use linux to make chromeOS so chromebook are really good at playing videos but GNU/Linux chromium is slow at doing it. To manage notifications about this bug go to: https://bugs.launchpad.net/chromium-browser/+bug/1424201/+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 1424201]
*** This bug has been marked as a duplicate of bug 1210726 *** -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1424201 Title: Web browsers lacking hardware-accelerated video decoding Status in Chromium Browser: Unknown Status in Mozilla Firefox: Invalid Status in chromium-browser package in Ubuntu: Confirmed Status in firefox package in Ubuntu: Confirmed Status in chromium-browser package in CentOS: Unknown Bug description: The chromium team has done a great job to totally disable hardware decoding on Linux. Even ignoring the GPU blacklist does not enable GPU decoding. How ever the patch is quite simple and it's already working using this PPA ( using libVA ) : https://launchpad.net/~saiarcot895/+archive/ubuntu/chromium-dev the corresponding patch is here : http://bazaar.launchpad.net/~saiarcot895/chromium-browser/chromium- browser.trusty.beta/view/head:/debian/patches/enable_vaapi_on_linux.diff that would be great if we could have this patch indefault Ubuntu chromium build, this situation is really sad right now, google use linux to make chromeOS so chromebook are really good at playing videos but GNU/Linux chromium is slow at doing it. To manage notifications about this bug go to: https://bugs.launchpad.net/chromium-browser/+bug/1424201/+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 1424201] Re: Web browsers lacking hardware-accelerated video decoding
** Changed in: firefox Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1424201 Title: Web browsers lacking hardware-accelerated video decoding Status in Chromium Browser: Unknown Status in Mozilla Firefox: Invalid Status in chromium-browser package in Ubuntu: Confirmed Status in firefox package in Ubuntu: Confirmed Status in chromium-browser package in CentOS: Unknown Bug description: The chromium team has done a great job to totally disable hardware decoding on Linux. Even ignoring the GPU blacklist does not enable GPU decoding. How ever the patch is quite simple and it's already working using this PPA ( using libVA ) : https://launchpad.net/~saiarcot895/+archive/ubuntu/chromium-dev the corresponding patch is here : http://bazaar.launchpad.net/~saiarcot895/chromium-browser/chromium- browser.trusty.beta/view/head:/debian/patches/enable_vaapi_on_linux.diff that would be great if we could have this patch indefault Ubuntu chromium build, this situation is really sad right now, google use linux to make chromeOS so chromebook are really good at playing videos but GNU/Linux chromium is slow at doing it. To manage notifications about this bug go to: https://bugs.launchpad.net/chromium-browser/+bug/1424201/+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 1825710] Re: Remove "Application is ready" notification
This window that keeps appearing is very annoying. Can't a setting be created in the OS with a CheckBox gadget to enable/disable the warning? "blah blah is ready" is very annoying. :-( ** Attachment added: "Screenshot" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1825710/+attachment/5270401/+files/VirtualBox_Ubuntu%2018.04.2%20LTS%20x64%20%28PureBasic%29%20-%202019-06-12.png -- 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/1825710 Title: Remove "Application is ready" notification Status in gnome-shell package in Ubuntu: Confirmed Bug description: The "Application is ready" notification is pointless, really. Say, I click on the open downloads folder button in Firefox and GNOME Shell gives me a notification saying "Application is ready" but doesn't open the notification. I'm totally expecting an app to open because I actively initiated it. As a workaround, I'm using a GNOME extensions "Focus my Window" which removes the "Application is ready" message and focuses the app window automatically. However, this cannot be treated as a solution. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1825710/+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 1825710] Re: Remove "Application is ready" notification
Note that the gnome-shell-extension-no-annoyance extension exists (presumably as a workaround rather than a solution to this bug). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1825710 Title: Remove "Application is ready" notification Status in gnome-shell package in Ubuntu: Confirmed Bug description: The "Application is ready" notification is pointless, really. Say, I click on the open downloads folder button in Firefox and GNOME Shell gives me a notification saying "Application is ready" but doesn't open the notification. I'm totally expecting an app to open because I actively initiated it. As a workaround, I'm using a GNOME extensions "Focus my Window" which removes the "Application is ready" message and focuses the app window automatically. However, this cannot be treated as a solution. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1825710/+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 1832610] [NEW] [HDA-Intel - HDA Intel PCH, playback] No sound at all
Public bug reported: No sounds at internal speakers but headphones works ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.2 ProcVersionSignature: Ubuntu 4.15.0-1039.44-oem 4.15.18 Uname: Linux 4.15.0-1039-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: marcelo 10930 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Jun 12 13:00:36 2019 InstallationDate: Installed on 2019-06-03 (8 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Áudio interno - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1813 F pulseaudio marcelo 10930 F pulseaudio Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: No sound at all Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/24/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.2.0 dmi.board.name: 07G539 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.2.0:bd03/24/2019:svnDellInc.:pnInspiron5480:pvr:rvnDellInc.:rn07G539:rvrA01:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5480 dmi.sys.vendor: Dell Inc. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1832610 Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all Status in pulseaudio package in Ubuntu: New Bug description: No sounds at internal speakers but headphones works ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.2 ProcVersionSignature: Ubuntu 4.15.0-1039.44-oem 4.15.18 Uname: Linux 4.15.0-1039-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: marcelo 10930 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Jun 12 13:00:36 2019 InstallationDate: Installed on 2019-06-03 (8 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Áudio interno - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1813 F pulseaudio marcelo 10930 F pulseaudio Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: No sound at all Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/24/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.2.0 dmi.board.name: 07G539 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.2.0:bd03/24/2019:svnDellInc.:pnInspiron5480:pvr:rvnDellInc.:rn07G539:rvrA01:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5480 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1832610/+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 1832374] Re: Media keys stop working due to missing service file
Hi Sebastian, This issue was partially fixed in GSD 3.30.2. See https://gitlab.gnome.org/GNOME/gnome-settings-daemon/issues/45 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-settings-daemon/issues #415 https://gitlab.gnome.org/GNOME/gnome-settings-daemon/issues/415 ** Also affects: gnome-settings-daemon via https://gitlab.gnome.org/GNOME/gnome-settings-daemon/issues/415 Importance: Unknown Status: Unknown ** Bug watch added: gitlab.gnome.org/GNOME/gnome-settings-daemon/issues #45 https://gitlab.gnome.org/GNOME/gnome-settings-daemon/issues/45 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1832374 Title: Media keys stop working due to missing service file Status in GNOME Settings Daemon: Unknown Status in gnome-settings-daemon package in Ubuntu: New Bug description: Over the last two releases I've noticed that if you have an audio player such as Clementine running, pause the audio playback and watch a video via VLC or SMPlayer and then close the video player and try to use the media keys again, the following is logged to journald: gsd-media-keys[2607]: Error calling method GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.mpris.MediaPlayer2.smplayer was not provided by any .service files. From what I can see is that a service file is created for the media keys for SMPlayer, when SMPlayer is closed that service file is removed and then media keys are still bound to that service. I get the above output for previous track, stop, play, pause and next track media keys. I do get the following output if neither is SMPlayer or Clementine is running or if Clementine is running and playing audio and SMPlayer is open, but no video is loaded: org.gnome.Shell.desktop[2480]: Window manager warning: Overwriting existing binding of keysym ffb5 with keysym ffb5 (keycode 54). org.gnome.Shell.desktop[2480]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a-e,12,f,10,11) <-- I collapsed the range into a comma separated list If you re-open SMPlayer and load a video, the media keys work and the GDBus error doesn't occur but the above "Overwriting ..." messages still get logged. Closing SMPlayer again does not restore media keys so that Clementine can handle them. I had SMPlayer running ~17 hours ago. Doing a shell reload doesn't seem to fix this either. I can't really tell if this is an SMPlay/VLC/Video Player issue or actually an issue in GSD, so filing here until someone can reassign to the relevant project. I hit this a while ago, while trying to get some debugging information for a Clementine bug: https://github.com/clementine- player/Clementine/issues/6320 If you need any other information let me know. Thanks ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-settings-daemon 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 Uname: Linux 5.0.0-16-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Jun 11 17:36:07 2019 InstallationDate: Installed on 2019-02-01 (129 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20181202) SourcePackage: gnome-settings-daemon UpgradeStatus: Upgraded to disco on 2019-04-09 (63 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1832374/+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 1832609] [NEW] i don't know speak EL
Public bug reported: i don't know speak EL ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 Uname: Linux 5.0.0-16-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jun 12 22:45:21 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 5500 [1043:192d] Advanced Micro Devices, Inc. [AMD/ATI] Mars LE [Radeon HD 8530M / R5 M240] [1002:6607] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Mars LE [Radeon HD 8530M / R5 M240] [1043:192d] InstallationDate: Installed on 2019-06-12 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: ASUSTeK COMPUTER INC. X555LPB ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-16-generic root=UUID=57d9c032-5367-4516-862d-811dfda6989e ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/08/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X555LPB.301 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X555LPB 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.:bvrX555LPB.301:bd06/08/2015:svnASUSTeKCOMPUTERINC.:pnX555LPB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555LPB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X555LPB 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 -- 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/1832609 Title: i don't know speak EL Status in xorg package in Ubuntu: New Bug description: i don't know speak EL ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 Uname: Linux 5.0.0-16-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jun 12 22:45:21 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 5500 [1043:192d] Advanced Micro Devices, Inc. [AMD/ATI] Mars LE [Radeon HD 8530M / R5 M240] [1002:6607] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Mars LE [Radeon HD 8530M / R5 M240] [1043:192d] InstallationDate: Installed on 2019-06-12 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: ASUSTeK COMPUTER INC. X555LPB ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-16-generic root=UUID=57d9c032-5367-4516-862d-811dfda6989e ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/08/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X555LPB.301 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X555LPB 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.:bvrX555LPB.301:bd06/08/2015:svnASUSTeKCOMPUTERINC.:pnX555LPB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555LPB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X555LPB 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:
[Desktop-packages] [Bug 1832426] Re: "Program" is not responding when debugging in gdb
Mh, if the warning is just showing once and when you unfocus such dialog you don't get any problem, I don't think this is an issue. Maybe the fix would be to delay the presentation of such dialog until the hanging window is focused? -- 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/1832426 Title: "Program" is not responding when debugging in gdb Status in gnome-shell package in Ubuntu: New Bug description: I believe this is a regression for bug 1740869: is not responding window is constantly showing when debugging a program I'm debugging my c++ sdl2 program in gdb and when I hit a breakpoint this window shows up and I can't get it to stop asking me to close the program. 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Description: Ubuntu 19.04 Release: 19.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center gnome-shell: Installed: 3.32.1-1ubuntu1~19.04.1 Candidate: 3.32.1-1ubuntu1~19.04.1 Version table: *** 3.32.1-1ubuntu1~19.04.1 500 500 http://us.archive.ubuntu.com/ubuntu disco-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.32.0+git20190410-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages 3) What you expected to happen When I hit a breakpoint in gdb, the program should stop. 4) What happened instead The program stops and ubuntu asks me if i want to kill the program. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.32.1-1ubuntu1~19.04.1 ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 Uname: Linux 5.0.0-16-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Jun 11 22:03:44 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-06-08 (4 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1832426/+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 1832606] [NEW] GNOME Disks Missing 'Close' Window Button When Set To Left-Hand Side
Public bug reported: When setting window control layout to the left hand side rather than the right, GNOME Disks (gnome-disk-utility) does not show the 'Close' button, however the 'Minimize' and 'Maximize' buttons are still present. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-disk-utility 3.32.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 Uname: Linux 5.0.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jun 12 08:44:30 2019 InstallationDate: Installed on 2019-06-12 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-disk-utility UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-disk-utility (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1832606 Title: GNOME Disks Missing 'Close' Window Button When Set To Left-Hand Side Status in gnome-disk-utility package in Ubuntu: New Bug description: When setting window control layout to the left hand side rather than the right, GNOME Disks (gnome-disk-utility) does not show the 'Close' button, however the 'Minimize' and 'Maximize' buttons are still present. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-disk-utility 3.32.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 Uname: Linux 5.0.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jun 12 08:44:30 2019 InstallationDate: Installed on 2019-06-12 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-disk-utility UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1832606/+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 1548970] Re: gvfsd-dnssd crashed with SIGSEGV in avahi_service_resolver_event()
Hello! My first comment here on this forum. This bug consistently occurs everytime my system is rebooted. Since I have absolutely no idea what goes on behind the scenes, I'd like to mention that I use NVIDIA drivers. Hoping to find a solution. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1548970 Title: gvfsd-dnssd crashed with SIGSEGV in avahi_service_resolver_event() Status in gvfs package in Ubuntu: Confirmed Bug description: Running: Description: Ubuntu Xenial Xerus (development branch) Release: 16.04 gvfs: Installed: 1.27.90-1ubuntu1 Candidate: 1.27.90-1ubuntu1 Version table: *** 1.27.90-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status Didn't expect anything happened shortly after booting & logging in. I got this pop-up. ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: gvfs-backends 1.27.90-1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1 Uname: Linux 4.4.0-6-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Feb 23 14:48:35 2016 ExecutablePath: /usr/lib/gvfs/gvfsd-dnssd InstallationDate: Installed on 2014-10-30 (481 days ago) InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) ProcCmdline: /usr/lib/gvfs/gvfsd-dnssd --spawner :1.14 /org/gtk/gvfs/exec_spaw/10 ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, user) LANG=en_US.UTF-8 SegvAnalysis: Segfault happened at: 0x7f8712280d9a <__strcmp_sse2_unaligned+26>: movdqu (%rdi),%xmm1 PC (0x7f8712280d9a) ok source "(%rdi)" (0x) not located in a known VMA region (needed readable region)! destination "%xmm1" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gvfs StacktraceTop: ?? () ?? () avahi_service_resolver_event () from /usr/lib/x86_64-linux-gnu/libavahi-client.so.3 ?? () from /usr/lib/x86_64-linux-gnu/libavahi-client.so.3 dbus_connection_dispatch () from /lib/x86_64-linux-gnu/libdbus-1.so.3 Title: gvfsd-dnssd crashed with SIGSEGV in avahi_service_resolver_event() UpgradeStatus: Upgraded to xenial on 2016-02-15 (8 days ago) UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1548970/+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 1819744] Re: 19.04 Disco default wallpapers
** Changed in: ubuntu-wallpapers (Ubuntu) Assignee: (unassigned) => Bekir Yekta Aktaş (yektabekr) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-wallpapers in Ubuntu. https://bugs.launchpad.net/bugs/1819744 Title: 19.04 Disco default wallpapers Status in ubuntu-wallpapers package in Ubuntu: Fix Released Bug description: Attached will be the Disco default wallpapers. One in colour, one in black and white. Both 4096 x 2304. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-wallpapers/+bug/1819744/+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 1832579] [NEW] Wrapper script might create duplicate launcher entries for chromium_chromium.desktop
Public bug reported:
When installing the updated deb package that transitions to the snap, if
the snap was already installed and its desktop file already pinned to
the GNOME Shell / Unity launcher, and if chromium-browser.desktop (from
the deb) was also pinned, the /usr/bin/chromium-browser wrapper script
will rewrite chromium-browser.desktop to chromium_chromium.desktop, but
it doesn't check whether there is already an entry for it in the
favorites, so it might result in duplicated entries.
This is not visible to the user because both GNOME Shell and Unity
launchers appear to have some logic to filter out duplicate entries.
Still, it would be nice to not add duplicate entries.
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: chromium-browser 75.0.3770.80-0ubuntu1~snap1 [modified:
usr/share/apport/package-hooks/chromium-browser.py]
ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8
Uname: Linux 5.0.0-16-generic x86_64
ApportVersion: 2.20.11-0ubuntu3
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
DRM.card0-VGA-1:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wBYWAAAaASUAgEAAQOAAAB47u6Ro1RMmSYPUFQBAQEBAQEBAQEBAQEBAQEBsxFoBkCUBiACAgIC/QAAyADIZAAKICAgICAg/ABWQk9YIG1vbml0b3IKEAAKICAgICAgICAgICAgAC8=
modes: 1128x660 2560x1600 2560x1600 1920x1440 1856x1392 1792x1344 2048x1152
1920x1200 1920x1200 1920x1080 1600x1200 1680x1050 1680x1050 1400x1050 1400x1050
1600x900 1280x1024 1440x900 1440x900 1280x960 1366x768 1366x768 1360x768
1280x800 1280x800 1280x768 1280x768 1280x720 1024x768 800x600 800x600 848x480
640x480
Date: Wed Jun 12 15:58:05 2019
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/sda1 ext430G 7,7G 21G 28% /
tmpfs tmpfs 2,0G 0 2,0G 0% /dev/shm
/dev/sda1 ext430G 7,7G 21G 28% /
InstallationDate: Installed on 2018-08-21 (294 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180821)
Lsusb:
Bus 001 Device 004: ID 80ee:0021 VirtualBox USB Tablet
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: innotek GmbH VirtualBox
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-16-generic
root=UUID=b6433793-b0b1-4fae-8bb3-585f57860605 ro quiet splash
Snap.ChromeDriverVersion: ChromeDriver 75.0.3770.80
(9a9aa15057b6b2cc0909bdcf638c0b65ecd516f2-refs/branch-heads/3770@{#948})
Snap.ChromiumVersion: Chromium 75.0.3770.80 snap
SourcePackage: chromium-browser
UpgradeStatus: Upgraded to eoan on 2019-06-05 (6 days ago)
dmi.bios.date: 12/01/2006
dmi.bios.vendor: innotek GmbH
dmi.bios.version: VirtualBox
dmi.board.name: VirtualBox
dmi.board.vendor: Oracle Corporation
dmi.board.version: 1.2
dmi.chassis.type: 1
dmi.chassis.vendor: Oracle Corporation
dmi.modalias:
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
dmi.product.family: Virtual Machine
dmi.product.name: VirtualBox
dmi.product.version: 1.2
dmi.sys.vendor: innotek GmbH
** Affects: chromium-browser (Ubuntu)
Importance: Low
Assignee: Olivier Tilloy (osomon)
Status: Triaged
** Tags: amd64 apport-bug eoan snap
--
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/1832579
Title:
Wrapper script might create duplicate launcher entries for
chromium_chromium.desktop
Status in chromium-browser package in Ubuntu:
Triaged
Bug description:
When installing the updated deb package that transitions to the snap,
if the snap was already installed and its desktop file already pinned
to the GNOME Shell / Unity launcher, and if chromium-browser.desktop
(from the deb) was also pinned, the /usr/bin/chromium-browser wrapper
script will rewrite chromium-browser.desktop to
chromium_chromium.desktop, but it doesn't check whether there is
already an entry for it in the favorites, so it might result in
duplicated entries.
This is not visible to the user because both GNOME Shell and Unity
launchers appear to have some logic to filter out duplicate entries.
Still, it would be nice to not add duplicate entries.
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: chromium-browser 75.0.3770.80-0ubuntu1~snap1 [modified:
usr/share/apport/package-hooks/chromium-browser.py]
ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8
Uname: Linux 5.0.0-16-generic x86_64
ApportVersion: 2.20.11-0ubuntu3
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
DRM.card0-VGA-1:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wBYWAAAaASUAgEAAQOAAAB47u6Ro1RMmSYPUFQBAQEBAQEBAQEBAQEBAQEBsxFoBkCUBiACAgIC/QAAyADIZAAKICAgICAg/ABWQk9YIG1vbml0b3IKEAAKICAgICAgICAgICAgAC8=
modes: 1128x660 2560x1600 2560x1600 1920x1440 1856x1392 1792x1344 2048x1152
1920x1200 1920x1200 1920x1080 1600x1200 1680x1050
Re: [Desktop-packages] [Bug 1832004] Re: [amdgpu] display hanging after laptop opens lid
None of those. Maybe I explaind the bug wrong. When the laptop comes out of sleep mode the screen won't get back on. Also the external screen won't get back on. On jun. 12 2019, at 4:01 am, Daniel van Vugt wrote: > Also, do you have any nonstandard gnome-shell extensions installed? > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1832004 > > Title: > [amdgpu] display hanging after laptop opens lid > > Status in xserver-xorg-video-amdgpu package in Ubuntu: > Incomplete > > Bug description: > ubuntu 19.04 > > ProblemType: Bug > DistroRelease: Ubuntu 19.04 > Package: xorg 1:7.7+19ubuntu12 > ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 > Uname: Linux 5.0.0-16-generic x86_64 > .tmp.unity_support_test.0: > > ApportVersion: 2.20.10-0ubuntu27 > Architecture: amd64 > BootLog: Error: [Errno 13] Toegang geweigerd: '/var/log/boot.log' > CompositorRunning: None > CurrentDesktop: ubuntu:GNOME > Date: Fri Jun 7 14:56:09 2019 > DistUpgraded: Fresh install > DistroCodename: disco > DistroVariant: ubuntu > DkmsStatus: > anbox, 1, 5.0.0-15-generic, x86_64: installed > anbox, 1, 5.0.0-16-generic, x86_64: installed > virtualbox, 6.0.6, 5.0.0-15-generic, x86_64: installed > virtualbox, 6.0.6, 5.0.0-16-generic, x86_64: installed > ExtraDebuggingInterest: No > GraphicsCard: > Advanced Micro Devices, Inc. [AMD/ATI] Stoney [Radeon R2/R3/R4/R5 Graphics] > [1002:98e4] (rev da) (prog-if 00 [VGA controller]) > Subsystem: ASUSTeK Computer Inc. Stoney [Radeon R2/R3/R4/R5 Graphics] > [1043:1680] > InstallationDate: Installed on 2018-08-03 (308 days ago) > InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) > MachineType: ASUSTeK COMPUTER INC. E402BA > ProcEnviron: > PATH=(custom, no user) > XDG_RUNTIME_DIR= > LANG=nl_NL.UTF-8 > SHELL=/bin/bash > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-16-generic > root=UUID=c593d94b-7cc0-45ca-a012-f79a49d00093 ro quiet splash vt.handoff=1 > SourcePackage: xorg > Symptom: display > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 09/06/2018 > dmi.bios.vendor: American Megatrends Inc. > dmi.bios.version: E402BA.311 > dmi.board.asset.tag: ATN12345678901234567 > dmi.board.name: E402BA > 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.:bvrE402BA.311:bd09/06/2018:svnASUSTeKCOMPUTERINC.:pnE402BA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE402BA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: > dmi.product.family: VivoBook > dmi.product.name: E402BA > dmi.product.version: 1.0 > dmi.sys.vendor: ASUSTeK COMPUTER 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 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-amdgpu/+bug/1832004/+subscriptions > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1832004 Title: [amdgpu] display hanging after laptop opens lid Status in xserver-xorg-video-amdgpu package in Ubuntu: Incomplete Bug description: ubuntu 19.04 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 Uname: Linux 5.0.0-16-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Toegang geweigerd: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jun 7 14:56:09 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu DkmsStatus: anbox, 1, 5.0.0-15-generic, x86_64: installed anbox, 1, 5.0.0-16-generic, x86_64: installed virtualbox, 6.0.6, 5.0.0-15-generic, x86_64: installed virtualbox, 6.0.6, 5.0.0-16-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Stoney [Radeon R2/R3/R4/R5 Graphics] [1002:98e4] (rev da) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Stoney [Radeon R2/R3/R4/R5 Graphics] [1043:1680] InstallationDate: Installed on 2018-08-03 (308 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" -
[Desktop-packages] [Bug 520546] Re: [Don't release SRU yet]Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right
** Tags removed: verification-failed-cosmic verification-failed-disco ** Tags added: verification-done-cosmic verification-done-disco -- 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/520546 Title: [Don't release SRU yet]Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right Status in console-setup package in Ubuntu: Fix Released Status in kbd package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Invalid Status in console-setup source package in Xenial: Confirmed Status in kbd source package in Xenial: Fix Committed Status in xorg-server source package in Xenial: Confirmed Status in console-setup source package in Bionic: Fix Released Status in kbd source package in Bionic: Fix Committed Status in linux source package in Bionic: Confirmed Status in xorg-server source package in Bionic: Invalid Status in console-setup source package in Cosmic: Fix Released Status in kbd source package in Cosmic: Fix Committed Status in linux source package in Cosmic: Confirmed Status in xorg-server source package in Cosmic: Invalid Status in console-setup source package in Disco: Fix Released Status in kbd source package in Disco: Fix Committed Status in linux source package in Disco: Confirmed Status in xorg-server source package in Disco: Invalid Status in console-setup source package in Eoan: Fix Released Status in kbd source package in Eoan: Fix Released Status in linux source package in Eoan: Confirmed Status in xorg-server source package in Eoan: Invalid Bug description: (kbd) [Impact] * kbd_mode -u is documented to break keyboards in modes other than xlate and unicode, while it is still called by some scripts. Those scripts are called transitively by maintainer scripts such as the one already fixed in console-setup. * To avoid accidentally breaking keyboards a -f option is added to force such breaking mode changes. Without -f only the safe mode changes are performed and an error is printed when the requested mode change is not safe. Next upstream version will also exit with error, but the cherry-picked fix makes kbd_mode return success even when the mode switch is not performed to avoid regressions of scripts. [Test case] * Verify that safe mode switches work and dangerous ones are skipped without -f. Please note that the test will temporarily break the system's keyboard and it is recommended to run the test in a VM. rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4; echo $? The keyboard is in Unicode (UTF-8) mode 0 rbalint@MacBookAir-test:~$ sudo kbd_mode -a -C /dev/tty4; echo $? 0 rbalint@MacBookAir-test:~$ sudo kbd_mode -a -C /dev/tty4; echo $? 0 rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4 The keyboard is in xlate (8-bit) mode rbalint@MacBookAir-test:~$ sudo kbd_mode -u -C /dev/tty4; echo $? 0 rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4 The keyboard is in Unicode (UTF-8) mode rbalint@MacBookAir-test:~$ sudo kbd_mode -u -C /dev/tty0; echo $? The keyboard is in some unknown mode Changing to the requested mode may make your keyboard unusable, please use -f to force the change. 0 rbalint@MacBookAir-test:~$ sudo kbd_mode -f -u -C /dev/tty0; echo $? 0 rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty0 The keyboard is in Unicode (UTF-8) mode rbalint@MacBookAir-test:~$ sudo kbd_mode -s -C /dev/tty0 rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty0 The keyboard is in raw (scancode) mode rbalint@MacBookAir-test:~$ sudo kbd_mode -u -C /dev/tty0; echo $? The keyboard is in raw (scancode) mode Changing to the requested mode may make your keyboard unusable, please use -f to force the change. 0 [Regression Potential] * kbd_mode stops performing breaking mode switches and this may make scripts ineffective when trying to perform a breaking change. This is the intention of the change and the emitter error helps in finding the offending script. The following packages found to call kbd_mode directly: console-setup xinit console-cyrillic initramfs-tools dracut console-tools xview ubiquity's embedded console-setup copy console-data vnc4 The console related packages are expected to execute only safe mode changes because they should operate on consoles only and the rest seem to be safe, too. (console-setup) [Impact] * keyboard-configuration's postinst changes keyboard mode breaking X keys. [Test Case] * Ssh to a system or open a terminal and unset DISPLAY $ echo $DISPLAY $ * Check kbd mode, should be raw (set by kbd_mode -s) or unknown: $ sudo kbd_mode The keyboard is in some unknown mode $ sudo kbd_mode The keyboard is in raw (scancode) mode $ On Xenial X runs on VT7 thus the graphical
[Desktop-packages] [Bug 1827451] Re: Japanese new era "Reiwa(令和)" support
** Tags added: id-5ccb134f178dcb256e668c1d -- 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/1827451 Title: Japanese new era "Reiwa(令和)" support Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice-l10n package in Ubuntu: Fix Released Status in libreoffice source package in Xenial: Fix Released Status in libreoffice source package in Bionic: Fix Released Status in libreoffice source package in Cosmic: Fix Released Status in libreoffice-l10n source package in Cosmic: Fix Released Bug description: Japanese new era "Reiwa(令和)" has began at 2019-05-01. These patches add Reiwa support for Libreoffice Bionic/Xenial. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libreoffice (not installed) ProcVersionSignature: Ubuntu 4.18.0-18.19~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-18-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri May 3 10:44:42 2019 InstallationDate: Installed on 2018-07-21 (285 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64(20180506.1) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) [Impact] * This effects all users who use the Japanese era date format in LibreOffice. * The fix is currently in LibreOffice 6.2.3 on eoan. [Test Case] 1. Start Calc 2. Put "01/05/2019" into a cell 3. Right-click on the cell and select "Format Cells" 4. Set “Language" to "Japanese" 5. Set “Format" to "H11.12.31" 6. Cell should show "R1.05.01" (not "N1.05.01”) 7. Set “Format" to "平成11年12月31日" 8. Cell should show "令和1年5月1日" (not "平成31年5月1日") [Regression Potential] * The fix is minor so potential for regression is low. * A combination of autopkgtests and manual testing as described above should provide reasonable confidence that no regressions sneaked in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1827451/+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 1790979] Re: Unable to change disk decryption passphrase
This bug occurred for me with a fresh installation of Ubuntu 19.04. I created a new installation of Ubuntu 19.04 on a empty disk and checked the box to encrypt the installation. After the installation I tried to change the password and got locked out. This is the output of sudo cryptsetup luksDump /dev/sda3 after the failed attempt to change my password: LUKS header information Version:2 Epoch: 4 Metadata area: 16384 [bytes] Keyslots area: 1678 [bytes] UUID: 233e3965-3d97-4619-969e-ab9ef9b379d8 Label: (no label) Subsystem: (no subsystem) Flags: (no flags) Data segments: 0: crypt offset: 16777216 [bytes] length: (whole device) cipher: aes-xts-plain64 sector: 512 [bytes] Keyslots: Tokens: Digests: 0: pbkdf2 Hash: sha256 Iterations: 37406 Salt: ec 30 aa 1b 97 ef d1 a5 fb b4 1f ba 58 a9 f6 6d e9 d8 c4 73 b4 1b b9 c0 52 ff bf 2f e9 93 d8 47 Digest: f3 dd bb 32 f3 69 45 26 76 86 9a c4 4c d4 41 d4 67 bc f1 10 b3 65 87 d6 3b 51 1d 52 f1 d6 1d 9f -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1790979 Title: Unable to change disk decryption passphrase Status in gnome-disk-utility package in Ubuntu: Confirmed Status in gnome-disk-utility package in Arch Linux: New Bug description: Versions: Ubuntu 18.04 LTS gnome-disk-utility 3.28.3-0ubuntu1~18.04.1 -- What I'm trying to do: Change the disk decryption passphrase of key in any slot other than slot 0 while there is an existing key in slot 0 (e.g. changing the disk decryption passphrase of slot 1) using gnome-disk-utility. Ran "Disks" > Selected my encrypted device partition > Clicked the gear icon > Selected "Change passphrase" > Entered the passphrase I wanted to change > Entered the passphrase I wanted to change to and confirmed it > clicked "Change". -- What I expected to happen: After clicking "Change" I expected to get no errors and have the passphrase I wanted to change to be valid to decrypt the disk. In the event of an error I expected the passphrase I was trying to change to still be valid to decrypt the disk. -- What is happening: I get an error message pop-up: Error changing passphrase Error changing passphrase on device /dev/sda2/:Failed to add the new passphrase: Invalid argument (udisks-error-quark, 0) And the key that I was trying to change gets deleted with no new key being added. -- (Before trying to change passphrase in key slot 2 using gnome-disk- utility) sudo cryptsetup luksDump /dev/sda2 LUKS header information for /dev/sda2 Version: 1 Cipher name: aes Cipher mode: cbc-essiv:sha256 Hash spec:sha1 Payload offset: 4096 MK bits: 256 MK digest:0f 5d 66 ec 16 0b 0c f2 4b 0a 9f 99 28 41 59 64 e9 9d 75 64 MK salt: 89 e5 16 e5 e0 5d f5 63 f6 ba 2b f1 df e8 e6 1d 11 52 27 39 ff 87 4c 70 ab b7 49 a2 97 e0 46 41 MK iterations:101875 UUID: c5754fe4-0835-431f-996b-e2202c380d05 Key Slot 0: ENABLED Iterations: 42 Salt: cb 25 fd 7d 14 ca af f1 6a 57 b9 b7 b8 7a 45 76 9e 9b 3f ef 6a 3a e7 f6 18 24 7a 6e bb 0d 36 78 Key material offset:8 AF stripes: 4000 Key Slot 1: ENABLED Iterations: 2074334 Salt: c2 cc 91 12 25 f4 80 21 d2 fa 91 44 ef 02 04 3e 6d d8 85 ef b2 39 fb c2 94 f1 62 ee db 79 3c ed Key material offset:264 AF stripes: 4000 Key Slot 2: ENABLED Iterations: 2090878 Salt: 47 fa 77 b7 f8 31 dc 48 ab 58 f7 25 a4 d5 c7 be 35 a3 83 6a 4d 1d bb 24 1c 38 12 2d f1 15 40 7f Key material offset:520 AF stripes: 4000 Key Slot 3: DISABLED Key Slot 4: DISABLED Key Slot 5: DISABLED Key Slot 6: DISABLED Key Slot 7: DISABLED -- (After trying to change passphrase in key slot 2 using gnome-disk- utility) sudo cryptsetup luksDump /dev/sda2 LUKS header information for /dev/sda2 Version: 1 Cipher name: aes Cipher mode: cbc-essiv:sha256 Hash spec:sha1 Payload offset: 4096 MK bits: 256 MK digest:0f 5d 66 ec 16 0b 0c f2 4b 0a 9f 99 28 41 59 64 e9 9d 75 64 MK salt:
[Desktop-packages] [Bug 1832510] Re: package install-info 6.5.0.dfsg.1-4build1 failed to install/upgrade: triggers looping, abandoned
*** This bug is a duplicate of bug 1821349 *** https://bugs.launchpad.net/bugs/1821349 ** This bug has been marked a duplicate of bug 1821349 package install-info 6.5.0.dfsg.1-4build1 failed to install/upgrade: triggers looping, abandoned -- 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/1832510 Title: package install-info 6.5.0.dfsg.1-4build1 failed to install/upgrade: triggers looping, abandoned Status in texinfo package in Ubuntu: New Bug description: hi, I try to update to 19.0 new linux version. My laptop turn off through the download . I open it again and I try to instail the update but I get this problem . ProblemType: Package DistroRelease: Ubuntu 19.04 Package: install-info 6.5.0.dfsg.1-4build1 ProcVersionSignature: Ubuntu 4.18.0-21.22-generic 4.18.20 Uname: Linux 4.18.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 Date: Wed Jun 12 14:45:14 2019 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2019-06-11 (1 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Python3Details: /usr/bin/python3.6, Python 3.6.8, python3-minimal, 3.6.7-1~18.10 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.6ubuntu1 apt 1.8.1 SourcePackage: texinfo Title: package install-info 6.5.0.dfsg.1-4build1 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to disco on 2019-06-12 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/texinfo/+bug/1832510/+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 1831356] Re: Settings crashes when I click "Devices"(Enheter in norwegian) tap
On 2019-06-12 13:34, Sebastien Bacher wrote: > Can you type "bt" in gdb after hitting the segfault? New attachment. ** Attachment added: "bt-output.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1831356/+attachment/5270343/+files/bt-output.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1831356 Title: Settings crashes when I click "Devices"(Enheter in norwegian) tap Status in gnome-control-center package in Ubuntu: Incomplete Bug description: Not much to say. It crashes every time, I cleick devices - and then continues to crash on every start up. Trying the command: gsettings reset org.gnome.ControlCenter last-panel as a known workaround for a similar problem, will let me access gnome- control-center and use it, until I click Devices again. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-control-center 1:3.32.1-1ubuntu4.1 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 Uname: Linux 5.0.0-15-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Sun Jun 2 03:21:58 2019 InstallationDate: Installed on 2018-12-11 (172 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to disco on 2019-06-02 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1831356/+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 1832510] Re: package install-info 6.5.0.dfsg.1-4build1 failed to install/upgrade: triggers looping, abandoned
** 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/1832510 Title: package install-info 6.5.0.dfsg.1-4build1 failed to install/upgrade: triggers looping, abandoned Status in texinfo package in Ubuntu: New Bug description: hi, I try to update to 19.0 new linux version. My laptop turn off through the download . I open it again and I try to instail the update but I get this problem . ProblemType: Package DistroRelease: Ubuntu 19.04 Package: install-info 6.5.0.dfsg.1-4build1 ProcVersionSignature: Ubuntu 4.18.0-21.22-generic 4.18.20 Uname: Linux 4.18.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 Date: Wed Jun 12 14:45:14 2019 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2019-06-11 (1 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Python3Details: /usr/bin/python3.6, Python 3.6.8, python3-minimal, 3.6.7-1~18.10 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.6ubuntu1 apt 1.8.1 SourcePackage: texinfo Title: package install-info 6.5.0.dfsg.1-4build1 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to disco on 2019-06-12 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/texinfo/+bug/1832510/+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 1832510] [NEW] package install-info 6.5.0.dfsg.1-4build1 failed to install/upgrade: triggers looping, abandoned
Public bug reported: hi, I try to update to 19.0 new linux version. My laptop turn off through the download . I open it again and I try to instail the update but I get this problem . ProblemType: Package DistroRelease: Ubuntu 19.04 Package: install-info 6.5.0.dfsg.1-4build1 ProcVersionSignature: Ubuntu 4.18.0-21.22-generic 4.18.20 Uname: Linux 4.18.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 Date: Wed Jun 12 14:45:14 2019 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2019-06-11 (1 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Python3Details: /usr/bin/python3.6, Python 3.6.8, python3-minimal, 3.6.7-1~18.10 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.6ubuntu1 apt 1.8.1 SourcePackage: texinfo Title: package install-info 6.5.0.dfsg.1-4build1 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to disco on 2019-06-12 (0 days ago) ** Affects: texinfo (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package disco -- 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/1832510 Title: package install-info 6.5.0.dfsg.1-4build1 failed to install/upgrade: triggers looping, abandoned Status in texinfo package in Ubuntu: New Bug description: hi, I try to update to 19.0 new linux version. My laptop turn off through the download . I open it again and I try to instail the update but I get this problem . ProblemType: Package DistroRelease: Ubuntu 19.04 Package: install-info 6.5.0.dfsg.1-4build1 ProcVersionSignature: Ubuntu 4.18.0-21.22-generic 4.18.20 Uname: Linux 4.18.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 Date: Wed Jun 12 14:45:14 2019 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2019-06-11 (1 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Python3Details: /usr/bin/python3.6, Python 3.6.8, python3-minimal, 3.6.7-1~18.10 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.6ubuntu1 apt 1.8.1 SourcePackage: texinfo Title: package install-info 6.5.0.dfsg.1-4build1 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to disco on 2019-06-12 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/texinfo/+bug/1832510/+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 1826918] Re: gnome-shell crashed with SIGSEGV in meta_x11_display_get_xdisplay() from detach_pixmap() from meta_surface_actor_x11_dispose() from g_object_unref() from g_object_
** Changed in: gnome-shell Status: Unknown => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1826918 Title: gnome-shell crashed with SIGSEGV in meta_x11_display_get_xdisplay() from detach_pixmap() from meta_surface_actor_x11_dispose() from g_object_unref() from g_object_unref() Status in GNOME Shell: New Status in gnome-shell package in Ubuntu: New Status in mutter package in Ubuntu: In Progress Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.32.0+git20190410-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/1a5d1f99fd9215f7a79b718d2e915c675ebcd69f contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1826918/+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 1831356] Re: Settings crashes when I click "Devices"(Enheter in norwegian) tap
Can you type "bt" in gdb after hitting the segfault? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1831356 Title: Settings crashes when I click "Devices"(Enheter in norwegian) tap Status in gnome-control-center package in Ubuntu: Incomplete Bug description: Not much to say. It crashes every time, I cleick devices - and then continues to crash on every start up. Trying the command: gsettings reset org.gnome.ControlCenter last-panel as a known workaround for a similar problem, will let me access gnome- control-center and use it, until I click Devices again. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-control-center 1:3.32.1-1ubuntu4.1 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 Uname: Linux 5.0.0-15-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Sun Jun 2 03:21:58 2019 InstallationDate: Installed on 2018-12-11 (172 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to disco on 2019-06-02 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1831356/+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 874535] Re: Volume Slider Jumps, due to rapidly changing hardware jack sense state
UPDATE: even after disconnection of the front audio panel, the issue still happens once in a blue moon: Left pulseaudio in debug mode for several days after fix: $ tail -f /tmp/pulseaudio.log | grep is.now (3284.252| 96.036) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now plugged in (3285.280| 1.006) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now unplugged (4430.108| 136.098) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now plugged in (4431.133| 1.003) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now unplugged (65064.220| 35.638) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now plugged in (65065.244| 1.023) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now unplugged (163655.996| 23.995) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now plugged in (163657.020| 1.023) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now unplugged (166826.748| 0.027) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now plugged in (166827.772| 0.712) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now unplugged (170071.580| 2.337) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now plugged in (170072.605| 0.483) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now unplugged (170196.156| 63.020) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now plugged in (170197.180| 1.022) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now unplugged (173292.956| 110.638) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now plugged in (173293.980| 1.023) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now unplugged (405426.784| 13.234) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now plugged in (405427.804| 0.998) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now unplugged (501250.208| 28.079) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now plugged in (501251.228| 1.018) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now unplugged (508205.532| 1.475) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now plugged in (508206.556| 1.022) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now unplugged (576198.464| 60.134) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now plugged in (576199.484| 1.018) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now unplugged (577215.964| 3.252) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now plugged in (577216.992| 0.726) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now unplugged (577250.780| 26.097) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now plugged in (577251.804| 1.022) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now unplugged (577291.740| 0.147) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now plugged in (577292.764| 0.515) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now unplugged (577495.964| 54.201) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now plugged in (577496.988| 1.023) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now unplugged (578591.196| 137.355) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now plugged in (578592.220| 1.022) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now unplugged (589797.436| 1.779) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now plugged in (589798.460| 1.022) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now unplugged (589802.556| 4.095) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now plugged in (589803.580| 1.022) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now unplugged (593142.972| 274.353) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now plugged in (593143.996| 1.002) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now unplugged (593435.804| 267.849) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now plugged in (593436.832| 1.005) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now unplugged (594411.680| 25.302) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now plugged in (594412.700| 1.001) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now unplugged (594960.540| 37.896) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now plugged in (594961.564| 1.002) D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now
[Desktop-packages] [Bug 1831356] Re: Settings crashes when I click "Devices"(Enheter in norwegian) tap
On 2019-06-12 08:47, Sebastien Bacher wrote: > Can you use gdb to get details on the segfault? Please see attachment. ** Attachment added: "g-c-c_segfault_gdb-output.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1831356/+attachment/5270332/+files/g-c-c_segfault_gdb-output.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1831356 Title: Settings crashes when I click "Devices"(Enheter in norwegian) tap Status in gnome-control-center package in Ubuntu: Incomplete Bug description: Not much to say. It crashes every time, I cleick devices - and then continues to crash on every start up. Trying the command: gsettings reset org.gnome.ControlCenter last-panel as a known workaround for a similar problem, will let me access gnome- control-center and use it, until I click Devices again. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-control-center 1:3.32.1-1ubuntu4.1 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 Uname: Linux 5.0.0-15-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Sun Jun 2 03:21:58 2019 InstallationDate: Installed on 2018-12-11 (172 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to disco on 2019-06-02 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1831356/+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 1832457] Re: [SRU] 2.60.4
disco in queue, will sync eoan once lp picks it up -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1832457 Title: [SRU] 2.60.4 Status in glib2.0 package in Ubuntu: In Progress Status in glib2.0 source package in Disco: In Progress Bug description: [ Description ] New stable release in the 2.60 series. [ QA ] Upstream release, so QA already performed by maintainers https://wiki.ubuntu.com/StableReleaseUpdates/GNOME This upload will trigger many autopkgtests that we expect to not be regressed by this upload. Pretty much all parts of GNOME use GLib, so test anything in the desktop that you can. [ Regression potential ] Various fixes in multiple places so multiple apps could be affected. [ Upstream NEWS ] Overview of changes in GLib 2.60.4 == * Fixes to improved network status detection with NetworkManager (#1788) * Leak fixes to some `glib-genmarshal` generated code (#1793) * Further fixes to the Happy Eyeballs (RFC 8305) implementation (!865) * File system permissions fix to clamp down permissions in a small time window when copying files (CVE-2019-12450, !876) * Bugs fixed: - #1755 Please revert #535 gmacros: Try to use the standard __func__ first in G_STRFUNC - #1788 GNetworkMonitor claims I am offline - #1792 glib-genmarshal generated valist marshal does not respect static scope for some types - #1793 glib-genmarshal generates wrong code for va marshaler for VARIANT type - #1795 Fix mingw32 CI on older branches - !865 gnetworkaddress: fix "happy eyeballs" logic - !878 Backport !876 “gfile: Limit access to files when copying” to glib-2-60 Overview of changes in GLib 2.60.3 == * Various fixes to small key/value support in `GHashTable` (#1749, #1780) * Bugs fixed: - #1747 Critical in g_socket_client_async_connect_complete - #1749 New GHashTable implementation confuses valgrind - #1759 test_month_names: assertion failed - #1771 GNetworkAddressAddressEnumerator unsafely modifies cache in GNetworkAddress - #1774 Leaks in gsocketclient.c connection code - #1776 glib/date test fails - #1780 GDB pretty-printer for GHashTable no longer works - !815 Merge branch 'wip/tingping/socketclient-cancel-2' into 'master' - !816 Backport !814 “gschema.dtd: Add target attribute to alias” to glib-2-60 - !826 Backport !824 “gsocketclient: Fix a leak in the connection code” to glib-2-60 - !829 Backport !828 “build: Fix a typo in the test whether _NL_ABALTMON_n is supported” to glib-2-60 - !834 Backport !823 "gnetworkaddress: Fix parallel enumerations interfering with eachother" to glib-2-60 - !838 Backport !835 “Fix typo in German translation” to glib-2-60 - !841 Backport !839 “tests: Update month name check for Greek locale” to glib-2-60 - !844 Backport !840 “ghash: Disable small-arrays under valgrind” to glib-2-60 - !846 Backport !845 “Fixing g_format_size_full() on Windows-x64” to glib-2-60 - !855 Backport !848 (more GHashTable fixes) to glib-2-60 - !858 Backport !852 “Update gdb pretty-printer for GHashTable” to glib-2-60 * Translation updates: - German Overview of changes in GLib 2.60.2 == * Fix crash when displaying notifications on macOS (!786) * Improve network status detection with NetworkManager (!781) * Bugs fixed: - !790 glib/gconstructor.h: Include stdlib.h for MSVC builds - !793 Backport !786: “cocoanotificationbackend: do not release readonly property” to glib-2-60 - !803 Backport !781 “gnetworkmonitornm: Fix network available detection” to glib-2-60 * Translation updates: - Catalan Overview of changes in GLib 2.60.1 == * Fix documentation for `gdbus-tool wait` to use correct units * Bugs fixed: - #1709 GResource generation test incompatible with stable LLVM on Linux - #1725 gosxappinfo.h is not installed on macOS - #1737 gdbus-tool wait command timeout argument incorrect unit reference - !711 socket: Fix annotation for flags in g_socket_receive_message - !722 Backport codegen: Fix use of uninitialised variable from !721 to glib-2-60 - !727 Backport !719 “Handle an UNKNOWN NetworkManager connectivity as NONE” to glib-2-60 - !729 Backport !728 “gsocket: Remove (type) annotation from flags arguments” to glib-2-60 - !758 gdbusaddress, win32: backport using cwd for running rundll32 - !775 meson: Hotfix for iconv detection on macOS * Translation updates: - Basque - Dutch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1832457/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe :
[Desktop-packages] [Bug 1832458] Re: [SRU] 2.60.3
disco in queue, will sync eoan once lp picks it up -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib-networking in Ubuntu. https://bugs.launchpad.net/bugs/1832458 Title: [SRU] 2.60.3 Status in glib-networking package in Ubuntu: In Progress Status in glib-networking source package in Disco: In Progress Bug description: [ Description ] Upstream have release 2.60.3 in the 2.60 series [ QA ] Upstream release, so QA already performed by maintainers https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Make sure no autopkgtests are regressed by this upload. Suggestion for something explicit to test would be epiphany on secure websites. [ Regression potential ] A broken glib-networking could affect various applications' ability to use networking properly, particularly TLS. [ Upstream NEWS ] 2.60.3 - June 9, 2019 = - Fix clobbering of the thread-default main context after certificate verification failure during async handshakes since 2.60.1 (#85) - Fix GTlsDatabase initialization failures in OpenSSL backend due to uninitialized memory use - Fix minor leak of ALPN protocols 2.60.2 - May 2, 2019 - OpenSSL backend now defaults to system trust store (#62) - Fix client auth failure error with GnuTLS 3.6.7 (#70) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib-networking/+bug/1832458/+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 1802208]
Would this bug also affect use of Oracle OpenJDK 12 when trying to call an external hsqldb.jar, e.g. when a user has what is known as a split database (no embedded hsqldb) ? If so, then it would be a regression for those users. -- 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/1802208 Title: Reports won't open Status in LibreOffice: Confirmed Status in libreoffice package in Ubuntu: Invalid Status in libreoffice source package in Xenial: Fix Released Status in libreoffice source package in Bionic: Fix Released Bug description: Reports that were working as of June this year (I haven't opened them since then) now are failing with the following error: Can not activate the factory for org.libreoffice.report.pentaho.SOReportJobFactory$_SOReportJobFactory I tried creating a fresh report to see if its some kind of out of date file format but I get the same error: 1. select "Create Report in Design View..." 2. select "Save" 3. Double click report 4. Same error as above Of course I'm expecting the report to open without an error. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libreoffice-report-builder 1:6.0.6-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Nov 8 12:16:08 2018 InstallationDate: Installed on 2018-02-17 (263 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) PackageArchitecture: all SourcePackage: libreoffice UpgradeStatus: Upgraded to bionic on 2018-05-01 (190 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1802208/+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 1802208]
(In reply to Alex Thurgood from comment #8) > Would this bug also affect use of Oracle OpenJDK 12 when trying to call an > external hsqldb.jar, e.g. when a user has what is known as a split database > (no embedded hsqldb) ? If so, then it would be a regression for those users. Hard to tell without further information about such failures. If there is a bug about that, please give a link to it here, so we can discuss that issue there instead of speculating here. -- 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/1802208 Title: Reports won't open Status in LibreOffice: Confirmed Status in libreoffice package in Ubuntu: Invalid Status in libreoffice source package in Xenial: Fix Released Status in libreoffice source package in Bionic: Fix Released Bug description: Reports that were working as of June this year (I haven't opened them since then) now are failing with the following error: Can not activate the factory for org.libreoffice.report.pentaho.SOReportJobFactory$_SOReportJobFactory I tried creating a fresh report to see if its some kind of out of date file format but I get the same error: 1. select "Create Report in Design View..." 2. select "Save" 3. Double click report 4. Same error as above Of course I'm expecting the report to open without an error. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libreoffice-report-builder 1:6.0.6-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Nov 8 12:16:08 2018 InstallationDate: Installed on 2018-02-17 (263 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) PackageArchitecture: all SourcePackage: libreoffice UpgradeStatus: Upgraded to bionic on 2018-05-01 (190 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1802208/+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 1256222] Re: radeonsi with glamor has very poor performance with line primitives drawing
Thank you for reporting this bug to Ubuntu. Ubuntu 13.10 (saucy) reached end-of-life on July 17, 2014. 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: xorg (Ubuntu) Status: Incomplete => Won't Fix -- 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/1256222 Title: radeonsi with glamor has very poor performance with line primitives drawing Status in xorg package in Ubuntu: Won't Fix Bug description: https://bugs.freedesktop.org/show_bug.cgi?id=68524 exists in Ubuntu 13.10 . It takes 5 seconds on my very fast computer with my very fast graphics card to maximize an openoffice calc windows, which is ridiculous. Other stuff is slow too. t@h ~> apt-cache policy xorg xserver-xorg-glamoregl xorg: Installed: 1:7.7+1ubuntu6 Candidate: 1:7.7+1ubuntu6 Version table: *** 1:7.7+1ubuntu6 0 500 http://dk.archive.ubuntu.com/ubuntu/ saucy/main amd64 Packages 100 /var/lib/dpkg/status xserver-xorg-glamoregl: Installed: 0.5.1-0ubuntu4.2 Candidate: 0.5.1-0ubuntu4.2 Version table: *** 0.5.1-0ubuntu4.2 0 500 http://dk.archive.ubuntu.com/ubuntu/ saucy-updates/main amd64 Packages 100 /var/lib/dpkg/status 0.5.1-0ubuntu4 0 500 http://dk.archive.ubuntu.com/ubuntu/ saucy/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1256222/+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 1467595] Re: cursor sometimes disappears on XPS 13 9343 and external monitor
Thank you for reporting this bug to Ubuntu. Ubuntu 15.04 (vivid) reached end-of-life on February 4, 2016. 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: unity (Ubuntu) Status: Confirmed => Incomplete ** Changed in: xorg (Ubuntu) Status: Confirmed => 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/1467595 Title: cursor sometimes disappears on XPS 13 9343 and external monitor Status in Dell Sputnik: New Status in Unity: Confirmed Status in unity package in Ubuntu: Incomplete Status in xorg package in Ubuntu: Incomplete Bug description: I have a new Dell XPS 13 9343 with the HiDPI touch screen and am using an external display port monitor. Occasionally, the mouse cursor disappears (sometimes after screen lock, other times just normal usage). I saw something on stack exchange that said this might help: gsettings set org.gnome.settings-daemon.plugins.cursor active false I've done this and it sometimes helps and sometimes doesn't. I've also just seen the cursor come back on its own after a few minutes without doing anything. Trying to interact with the touch screen, then the mouse has no effect. Unplugging and replugging the mouse has no effect. Using the touchpad has no effect. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity 7.3.2+15.04.20150420-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-21.21-generic 3.19.8 Uname: Linux 3.19.0-21-generic x86_64 NonfreeKernelModules: wl .tmp.unity.support.test.0: ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Jun 22 11:19:40 2015 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.248+bdcom, 3.19.0-18-generic, x86_64: installed bcmwl, 6.30.223.248+bdcom, 3.19.0-20-generic, x86_64: installed bcmwl, 6.30.223.248+bdcom, 3.19.0-21-generic, x86_64: installed GraphicsCard: Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0665] InstallationDate: Installed on 2015-06-13 (8 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: Dell Inc. XPS 13 9343 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-21-generic root=UUID=7bc4dcd2-0bd8-4e42-b8b7-9f1ed6b8a3e9 ro libata.force=noncq quiet splash vt.handoff=7 SourcePackage: unity UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/25/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.name: 0310JH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA03:bd03/25/2015:svnDellInc.:pnXPS139343:pvr01:rvnDellInc.:rn0310JH:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9343 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Mon Jun 22 10:53:54 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5153 vendor SHP xserver.version: 2:1.17.1-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1467595/+subscriptions --
[Desktop-packages] [Bug 1578618] Re: L_Ctrl and L_Super buttons has been switched between itself
** Tags added: xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1578618 Title: L_Ctrl and L_Super buttons has been switched between itself Status in xorg package in Ubuntu: New Bug description: After upgrade from 15.10 to 16.04 on my "Lenovo T420" the buttons L_Ctrl and L_Super switched places. When I try to create new shortcuts and press on Super button, the system treats it like Ctrl button. At the /usr/share/X11/xkb/symbols/pc - there is no changes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1578618/+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 303140]
It cannot be that difficult to finally solve this problem. What I've been doing as a workaround for years is the following: * use any tool/editor capable of manipulating the email (header), e.g., the HeaderToolsLite extension. * Change in the "Content-Type" entry the "multipart/signed" to "multipart/mixed" and remove (or even better, rename) the "protocol" parameter, e.g.: replace Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=SHA1; boundary="=_NextPart_000__01D1D126.351C61F0" by Content-Type: multipart/mixed; protocol="application/x-pkcs7-disabled-signature"; micalg=SHA1; boundary="=_NextPart_000__01D1D126.351C61F0" * As a result, the email is not considered signed anymore, while the signature is now treated as a regular attachment. * Detach/detect any attachments as you want. Note that this way there is still an indication that the email was signed originally, yet without a disturbing "broken signature" symbol being shown. In case you later restore the signature MIME header after manipulating the attachments (or the remaining body), the signature will of course show broken. If you did not change anything in the body including the attachments (or restore it), you can easily restore the valid signature by reverting the small header changes mentioned above. BTW, TB apparently blocks deleting/detaching attachments as long as it finds "application/x-pkcs7-signature" as a substring(!) of the Content- Type entry, which is bad hack. It should rather check that there is a parameter with (full) name "protocol" and (full) value "application/x-pkcs7-disabled-signature" Hope this helps as a hint how to design and implement a solution smoothly. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/303140 Title: No more "Save all" / "detach all" / "delete all" for attachments Status in Mozilla Thunderbird: Confirmed Status in thunderbird package in Ubuntu: Confirmed Bug description: Binary package hint: thunderbird After receiving an email with more than one attachment, I have to open/detach/save them one by one, cause "Save all" / "detach all" / "delete all" in the GUI are not available This happens since version 2.0.0.18 1) Description:Ubuntu 8.04.1 Release:8.04 User-Agent: Thunderbird 2.0.0.18 (X11/20081125) MIME-Version: 1.0 2) Package: Linux-Mint 5 3) "Save all" / "detach all" / "delete all" available when right- klicking on an attachment 4 )"Save all" / "detach all" / "delete all" greyed out, so not available ProblemType: Bug Architecture: i386 Date: Fri Nov 28 11:34:16 2008 DistroRelease: Ubuntu 8.04 NonfreeKernelModules: wl fglrx Package: mozilla-thunderbird 2.0.0.18+nobinonly-0ubuntu0.8.04.1 PackageArchitecture: all ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: thunderbird Uname: Linux 2.6.24-21-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/303140/+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 303140]
Removing myslef on all the bugs I'm cced on. Please NI me if you need something on MailNews Core bugs from me. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/303140 Title: No more "Save all" / "detach all" / "delete all" for attachments Status in Mozilla Thunderbird: Confirmed Status in thunderbird package in Ubuntu: Confirmed Bug description: Binary package hint: thunderbird After receiving an email with more than one attachment, I have to open/detach/save them one by one, cause "Save all" / "detach all" / "delete all" in the GUI are not available This happens since version 2.0.0.18 1) Description:Ubuntu 8.04.1 Release:8.04 User-Agent: Thunderbird 2.0.0.18 (X11/20081125) MIME-Version: 1.0 2) Package: Linux-Mint 5 3) "Save all" / "detach all" / "delete all" available when right- klicking on an attachment 4 )"Save all" / "detach all" / "delete all" greyed out, so not available ProblemType: Bug Architecture: i386 Date: Fri Nov 28 11:34:16 2008 DistroRelease: Ubuntu 8.04 NonfreeKernelModules: wl fglrx Package: mozilla-thunderbird 2.0.0.18+nobinonly-0ubuntu0.8.04.1 PackageArchitecture: all ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: thunderbird Uname: Linux 2.6.24-21-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/303140/+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 303140]
Hi everybody, more or less daily I send out emails with attachments, and I like the idea of having my emails signed. But the attachments are blowing up my email folder size on hard disk, so I have to stop signing them. And I want to read them in 25 years still without any special tools installed. Please make it possible to remove attachments from sent and signed emails. All I need is, that the recipient receives my emails signed - I don't need them signed on my own system (a flag showing "Sent signed" would be sufficient). The same applies to encryption. I'm using Seamonkey myself, but hope to get this fix one day from Thunderbird into Seamonkey (or I will switch to Thunderbird for the case there will not come any update to Seamonkey anymore). Friendly greetings, Torsten -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/303140 Title: No more "Save all" / "detach all" / "delete all" for attachments Status in Mozilla Thunderbird: Confirmed Status in thunderbird package in Ubuntu: Confirmed Bug description: Binary package hint: thunderbird After receiving an email with more than one attachment, I have to open/detach/save them one by one, cause "Save all" / "detach all" / "delete all" in the GUI are not available This happens since version 2.0.0.18 1) Description:Ubuntu 8.04.1 Release:8.04 User-Agent: Thunderbird 2.0.0.18 (X11/20081125) MIME-Version: 1.0 2) Package: Linux-Mint 5 3) "Save all" / "detach all" / "delete all" available when right- klicking on an attachment 4 )"Save all" / "detach all" / "delete all" greyed out, so not available ProblemType: Bug Architecture: i386 Date: Fri Nov 28 11:34:16 2008 DistroRelease: Ubuntu 8.04 NonfreeKernelModules: wl fglrx Package: mozilla-thunderbird 2.0.0.18+nobinonly-0ubuntu0.8.04.1 PackageArchitecture: all ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: thunderbird Uname: Linux 2.6.24-21-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/303140/+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 303140]
@wroot, if you more carefully read my post of 2016-06-28 01:49:32 PDT you will see that my workaround does not only prevent an error message, but also does enable removing attachments. I also indicated a sloppiness in TB's way of detecting that a message is signed (when determining whether it allows to remove attachments). The whole issue could have been solved pretty easily already some ten years ago, but like with most other reported bugs/problems, nobody actually takes it up. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/303140 Title: No more "Save all" / "detach all" / "delete all" for attachments Status in Mozilla Thunderbird: Confirmed Status in thunderbird package in Ubuntu: Confirmed Bug description: Binary package hint: thunderbird After receiving an email with more than one attachment, I have to open/detach/save them one by one, cause "Save all" / "detach all" / "delete all" in the GUI are not available This happens since version 2.0.0.18 1) Description:Ubuntu 8.04.1 Release:8.04 User-Agent: Thunderbird 2.0.0.18 (X11/20081125) MIME-Version: 1.0 2) Package: Linux-Mint 5 3) "Save all" / "detach all" / "delete all" available when right- klicking on an attachment 4 )"Save all" / "detach all" / "delete all" greyed out, so not available ProblemType: Bug Architecture: i386 Date: Fri Nov 28 11:34:16 2008 DistroRelease: Ubuntu 8.04 NonfreeKernelModules: wl fglrx Package: mozilla-thunderbird 2.0.0.18+nobinonly-0ubuntu0.8.04.1 PackageArchitecture: all ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: thunderbird Uname: Linux 2.6.24-21-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/303140/+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 303140]
Unfortunately, it's _not_ a "rather basic fix," because the MIME handling code in Thunderbird is a mess which makes even seemingly small changes difficult. I believe someone is in the process of rewriting all the MIME handling stuff in JavaScript which will eventually replace the old, messy, C++ MIME code. Once that happens this fix will probably be easier to implement. _Probably_. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/303140 Title: No more "Save all" / "detach all" / "delete all" for attachments Status in Mozilla Thunderbird: Confirmed Status in thunderbird package in Ubuntu: Confirmed Bug description: Binary package hint: thunderbird After receiving an email with more than one attachment, I have to open/detach/save them one by one, cause "Save all" / "detach all" / "delete all" in the GUI are not available This happens since version 2.0.0.18 1) Description:Ubuntu 8.04.1 Release:8.04 User-Agent: Thunderbird 2.0.0.18 (X11/20081125) MIME-Version: 1.0 2) Package: Linux-Mint 5 3) "Save all" / "detach all" / "delete all" available when right- klicking on an attachment 4 )"Save all" / "detach all" / "delete all" greyed out, so not available ProblemType: Bug Architecture: i386 Date: Fri Nov 28 11:34:16 2008 DistroRelease: Ubuntu 8.04 NonfreeKernelModules: wl fglrx Package: mozilla-thunderbird 2.0.0.18+nobinonly-0ubuntu0.8.04.1 PackageArchitecture: all ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: thunderbird Uname: Linux 2.6.24-21-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/303140/+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 303140]
Totally agree with comment 25: I often send signed mails with big attachments, and I need to keep trace of the mails sent, the attachments attached, and the text of the mails, but I do NOT need the attachments themselves. While deleting/detaching attachments is impossible since 10 years, marking the attachment and hitting the delete button still works and leaves an empty message. The proposed resolution is clear since 10 years: remove the signature/encryption when deleting an attachment, and warn the user about it, preferably with option not to warn again. David Bienvenu, who proposed this RFE 2005, retired from this bug after 7 years without any proposed patch. Anybody there who is willing to implement this rather basic fix? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/303140 Title: No more "Save all" / "detach all" / "delete all" for attachments Status in Mozilla Thunderbird: Confirmed Status in thunderbird package in Ubuntu: Confirmed Bug description: Binary package hint: thunderbird After receiving an email with more than one attachment, I have to open/detach/save them one by one, cause "Save all" / "detach all" / "delete all" in the GUI are not available This happens since version 2.0.0.18 1) Description:Ubuntu 8.04.1 Release:8.04 User-Agent: Thunderbird 2.0.0.18 (X11/20081125) MIME-Version: 1.0 2) Package: Linux-Mint 5 3) "Save all" / "detach all" / "delete all" available when right- klicking on an attachment 4 )"Save all" / "detach all" / "delete all" greyed out, so not available ProblemType: Bug Architecture: i386 Date: Fri Nov 28 11:34:16 2008 DistroRelease: Ubuntu 8.04 NonfreeKernelModules: wl fglrx Package: mozilla-thunderbird 2.0.0.18+nobinonly-0ubuntu0.8.04.1 PackageArchitecture: all ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: thunderbird Uname: Linux 2.6.24-21-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/303140/+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 303140]
Oops, correcting a copy error in my but-last paragraph above: BTW, TB apparently blocks deleting/detaching attachments as long as it finds "application/x-pkcs7-signature" as a substring(!) of the Content- Type entry, which is bad hack. It should rather check that there is a parameter with (full) name "protocol" and (full) value "application/x-pkcs7-signature" -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/303140 Title: No more "Save all" / "detach all" / "delete all" for attachments Status in Mozilla Thunderbird: Confirmed Status in thunderbird package in Ubuntu: Confirmed Bug description: Binary package hint: thunderbird After receiving an email with more than one attachment, I have to open/detach/save them one by one, cause "Save all" / "detach all" / "delete all" in the GUI are not available This happens since version 2.0.0.18 1) Description:Ubuntu 8.04.1 Release:8.04 User-Agent: Thunderbird 2.0.0.18 (X11/20081125) MIME-Version: 1.0 2) Package: Linux-Mint 5 3) "Save all" / "detach all" / "delete all" available when right- klicking on an attachment 4 )"Save all" / "detach all" / "delete all" greyed out, so not available ProblemType: Bug Architecture: i386 Date: Fri Nov 28 11:34:16 2008 DistroRelease: Ubuntu 8.04 NonfreeKernelModules: wl fglrx Package: mozilla-thunderbird 2.0.0.18+nobinonly-0ubuntu0.8.04.1 PackageArchitecture: all ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: thunderbird Uname: Linux 2.6.24-21-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/303140/+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 303140]
Created attachment 8622054 UI: delete/detach for attachment of signed message not available TB 31.7 still does not allow to delete attachments from signed messages. Attached is a screenshot that shows the delete/detach functions "greyed out" (disabled). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/303140 Title: No more "Save all" / "detach all" / "delete all" for attachments Status in Mozilla Thunderbird: Confirmed Status in thunderbird package in Ubuntu: Confirmed Bug description: Binary package hint: thunderbird After receiving an email with more than one attachment, I have to open/detach/save them one by one, cause "Save all" / "detach all" / "delete all" in the GUI are not available This happens since version 2.0.0.18 1) Description:Ubuntu 8.04.1 Release:8.04 User-Agent: Thunderbird 2.0.0.18 (X11/20081125) MIME-Version: 1.0 2) Package: Linux-Mint 5 3) "Save all" / "detach all" / "delete all" available when right- klicking on an attachment 4 )"Save all" / "detach all" / "delete all" greyed out, so not available ProblemType: Bug Architecture: i386 Date: Fri Nov 28 11:34:16 2008 DistroRelease: Ubuntu 8.04 NonfreeKernelModules: wl fglrx Package: mozilla-thunderbird 2.0.0.18+nobinonly-0ubuntu0.8.04.1 PackageArchitecture: all ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: thunderbird Uname: Linux 2.6.24-21-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/303140/+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 303140]
David, yes i understood that correctly and was able to remove attachments;) My second statement wasn't directed at you, but at the situation in general. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/303140 Title: No more "Save all" / "detach all" / "delete all" for attachments Status in Mozilla Thunderbird: Confirmed Status in thunderbird package in Ubuntu: Confirmed Bug description: Binary package hint: thunderbird After receiving an email with more than one attachment, I have to open/detach/save them one by one, cause "Save all" / "detach all" / "delete all" in the GUI are not available This happens since version 2.0.0.18 1) Description:Ubuntu 8.04.1 Release:8.04 User-Agent: Thunderbird 2.0.0.18 (X11/20081125) MIME-Version: 1.0 2) Package: Linux-Mint 5 3) "Save all" / "detach all" / "delete all" available when right- klicking on an attachment 4 )"Save all" / "detach all" / "delete all" greyed out, so not available ProblemType: Bug Architecture: i386 Date: Fri Nov 28 11:34:16 2008 DistroRelease: Ubuntu 8.04 NonfreeKernelModules: wl fglrx Package: mozilla-thunderbird 2.0.0.18+nobinonly-0ubuntu0.8.04.1 PackageArchitecture: all ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: thunderbird Uname: Linux 2.6.24-21-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/303140/+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 303140]
David, thanks for the workaround. It seems that this and other tickets a more about dealing with errors about broken signature and not about the thing that a user should be able to deal with attachments no matter if it will show an error or not. +1 annoyed Thunderbird user -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/303140 Title: No more "Save all" / "detach all" / "delete all" for attachments Status in Mozilla Thunderbird: Confirmed Status in thunderbird package in Ubuntu: Confirmed Bug description: Binary package hint: thunderbird After receiving an email with more than one attachment, I have to open/detach/save them one by one, cause "Save all" / "detach all" / "delete all" in the GUI are not available This happens since version 2.0.0.18 1) Description:Ubuntu 8.04.1 Release:8.04 User-Agent: Thunderbird 2.0.0.18 (X11/20081125) MIME-Version: 1.0 2) Package: Linux-Mint 5 3) "Save all" / "detach all" / "delete all" available when right- klicking on an attachment 4 )"Save all" / "detach all" / "delete all" greyed out, so not available ProblemType: Bug Architecture: i386 Date: Fri Nov 28 11:34:16 2008 DistroRelease: Ubuntu 8.04 NonfreeKernelModules: wl fglrx Package: mozilla-thunderbird 2.0.0.18+nobinonly-0ubuntu0.8.04.1 PackageArchitecture: all ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: thunderbird Uname: Linux 2.6.24-21-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/303140/+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 303140]
Given the increasing number of security issues and fraud with emails, it becomes very important to sign emails. My organisation recently moved to signed emails but we really need a feature to delete/detach attachments from emails. Is there a way to get this feature implemented soon? e.g. as an add-on? I'm happy to test that and give feedback. Apparently, several people in the community would love to have this feature. See also: https://support.mozilla.org/en-US/questions/1128673 Thank you in advance for your help. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/303140 Title: No more "Save all" / "detach all" / "delete all" for attachments Status in Mozilla Thunderbird: Confirmed Status in thunderbird package in Ubuntu: Confirmed Bug description: Binary package hint: thunderbird After receiving an email with more than one attachment, I have to open/detach/save them one by one, cause "Save all" / "detach all" / "delete all" in the GUI are not available This happens since version 2.0.0.18 1) Description:Ubuntu 8.04.1 Release:8.04 User-Agent: Thunderbird 2.0.0.18 (X11/20081125) MIME-Version: 1.0 2) Package: Linux-Mint 5 3) "Save all" / "detach all" / "delete all" available when right- klicking on an attachment 4 )"Save all" / "detach all" / "delete all" greyed out, so not available ProblemType: Bug Architecture: i386 Date: Fri Nov 28 11:34:16 2008 DistroRelease: Ubuntu 8.04 NonfreeKernelModules: wl fglrx Package: mozilla-thunderbird 2.0.0.18+nobinonly-0ubuntu0.8.04.1 PackageArchitecture: all ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: thunderbird Uname: Linux 2.6.24-21-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/303140/+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 1271166] Re: Gómez Peer under Wine appears on the lock screen
Thank you for reporting this bug to Ubuntu. Ubuntu 12.04 (precise) reached end-of-life on April 28, 2017. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: xorg (Ubuntu) Status: Triaged => Won't Fix -- 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/1271166 Title: Gómez Peer under Wine appears on the lock screen Status in xorg package in Ubuntu: Won't Fix Bug description: When running the Gómez Peer under Wine (including upstream), the application is still visible on top of the lock screen. Nothing running should be visible on top of the lock screen and this is a security concern. To work around this I run Wine with WINEDLLOVERRIDES=wined3d= Wine can be blamed for this, but X (or whatever provides the lock screen - Gnome?) shouldn't allow applications to "break through" the lock screen. Attached photo shows part of the application where it has updated its GUI. On a full update the full GUI is visible. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xorg 1:7.6+12ubuntu2 Uname: Linux 3.11.10-031110-generic x86_64 NonfreeKernelModules: wl .tmp.unity.support.test.0: ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,decor,mousepoll,vpswitch,regex,animation,snap,expo,move,compiztoolbox,place,grid,imgpng,gnomecompat,wall,ezoom,workarounds,staticswitcher,resize,fade,unitymtgrabhandles,scale,session,unityshell] CompositorRunning: None Date: Tue Jan 21 12:39:34 2014 DistUpgraded: Fresh install DistroCodename: precise DistroVariant: ubuntu ExtraDebuggingInterest: Yes, even including gdb or git bisection work if needed GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RS880M [Mobility Radeon HD 4225/4250] [1002:9712] (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:036e] InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130820.1) MachineType: Acer Aspire 5551 MarkForUpload: True ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.10-031110-generic root=UUID=a8da15b6-5377-4984-90ce-9ff3c6d3f047 ro zcache radeon.dpm=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/27/2011 dmi.bios.vendor: Acer dmi.bios.version: V2.14 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: JE50_DN dmi.board.vendor: Acer dmi.board.version: Base Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.14 dmi.modalias: dmi:bvnAcer:bvrV2.14:bd07/27/2011:svnAcer:pnAspire5551:pvrV2.14:rvnAcer:rnJE50_DN:rvrBaseBoardVersion:cvnAcer:ct10:cvrV2.14: dmi.product.name: Aspire 5551 dmi.product.version: V2.14 dmi.sys.vendor: Acer drirc: version.compiz: compiz 1:0.9.7.12-0ubuntu3 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1ubuntu0.0.0.1 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1271166/+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 1116791] Re: xterm and gnome-terminal should not be dependencies
Thank you for reporting this bug to Ubuntu. Ubuntu 13.04 (raring) reached end-of-life on January 27, 2014. 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: xinit (Ubuntu) Status: Triaged => Won't Fix ** Changed in: xorg (Ubuntu) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xinit in Ubuntu. https://bugs.launchpad.net/bugs/1116791 Title: xterm and gnome-terminal should not be dependencies Status in ubuntu-meta package in Ubuntu: Fix Released Status in xinit package in Ubuntu: Won't Fix Status in xorg package in Ubuntu: Won't Fix Bug description: Hi, ubuntu-desktop depends on xterm and gnome-terminal. xorg is a dependency as well, and in turn depends on xterm | x-terminal- emulator. Something is wrong here. I'd say either removing the depends on the terminal emulators from ubuntu-desktop or, in case of xorg getting replaced at some point, depend on xterm | x-terminal-emulator here too... Best wishes, Nafallo ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: ubuntu-desktop 1.293 ProcVersionSignature: Ubuntu 3.8.0-4.8-generic 3.8.0-rc6 Uname: Linux 3.8.0-4-generic i686 NonfreeKernelModules: wl ApportVersion: 2.8-0ubuntu4 Architecture: i386 Date: Tue Feb 5 23:58:17 2013 EcryptfsInUse: Yes InstallationDate: Installed on 2011-10-09 (485 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta i386 (20111007.1) MarkForUpload: True SourcePackage: ubuntu-meta UpgradeStatus: Upgraded to raring on 2012-12-07 (60 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1116791/+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 971018] Re: Auto-hide Unity Launcher will not reveal when mouse pushed to left side in VirtualBox or VMware
** Tags removed: precise -- 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/971018 Title: Auto-hide Unity Launcher will not reveal when mouse pushed to left side in VirtualBox or VMware Status in Unity: Opinion Status in libxfixes package in Ubuntu: Incomplete Status in unity package in Ubuntu: Opinion Status in xorg package in Ubuntu: Incomplete Bug description: Ubuntu Precise 12.04 Beta 2 AMD64 DVD: I am running Ubuntu Precise 12.04 Beta 2 in a VirtualBox 4.1.8 session. VirtualBox Guest Additions have been installed via "jockey-gtk" from the Ubuntu Precise repository, and Unity is running in 3D mode with Compiz. When the Unity Launcher is set to "autohide," the Launcher will never reveal when the mouse pointer is moved to the left edge of the screen. It does not matter how much "pressure" is applied; the Launcher never appears. I have tried the following VirtualBox window "form-factors," all with the same result (the Launcher never appears): -- VirtualBox session running in a non-maximized window -- VirtualBox session running in a maximized window -- VirtualBox session running full-screen I have attached a screen capture (OGV) with Ubuntu Precise running in a maximized VirtualBox window. Note: This Bug may be related to the following other Bugs reported on LaunchPad: -- Bug 965643: Unity 5.8: auto-hide using mouse reveals launcher inconsistently -- -- https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/965643 -- Bug 923749: New "push mouse offscreen" feature really difficult to get -- -- https://bugs.launchpad.net/unity/+bug/923749 -- Bug 937792: Left launcher does not revel when in autohide mode on multi-monitor setups -- -- https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/937792 ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: unity 5.8.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-21.34-generic 3.2.13 Uname: Linux 3.2.0-21-generic x86_64 ApportVersion: 2.0-0ubuntu2 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] Date: Sun Apr 1 14:46:23 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120328) ProcEnviron: TERM=xterm LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/971018/+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 1099115] Re: Can't change brightness while screen is locked
Thank you for reporting this bug to Ubuntu. Ubuntu 12.10 (quantal) reached end-of-life on May 16, 2014. 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: xorg (Ubuntu) Status: Triaged => Won't Fix -- 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/1099115 Title: Can't change brightness while screen is locked Status in xorg package in Ubuntu: Won't Fix Bug description: My laptop is configured to lock the screen after X minutes. I lowered the brightness until the point there the backlight is completely off, and after X minutes I wanted to turn the screen again by using the function keys to increase the brightness, but they weren't responding. After a while I realized the screen was blocked, so I blindly type the password, pressed enter and then used the function keys to increase the brightness and it worked. I think it will be much better if one can change the brightness of the screen even if the screen is locked. I can't see any security problems in allowing that. Optionally, it would be nice if the user can set his lock screen to allow changing the sound volume and other slightly harmless activities one can do with the function or multimedia keys while the screen is locked (is a common thing in the mobile world, I think). ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-22.33-generic 3.5.7.2 Uname: Linux 3.5.0-22-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.6.1-0ubuntu9 Architecture: amd64 CheckboxSubmission: f8b82cd9bc23fe075e5068a9824afda5 CheckboxSystem: b1865df84255b8716d3bcc269ff410d1 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,workarounds,scale,expo,ezoom] CompositorRunning: None Date: Sun Jan 13 14:43:16 2013 DistUpgraded: 2012-10-28 16:30:42,684 DEBUG enabling apt cron job DistroCodename: quantal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems Device [1179:0009] InstallationDate: Installed on 2012-04-26 (261 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MachineType: TOSHIBA SATELLITE Z830 MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-22-generic root=UUID=36929bf3-a158-44d9-a80d-3adac2840fa8 ro quiet splash acpi_backlight=vendor i915.i915_enable_rc6=1 i915.lvds_downclock=1 vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to quantal on 2012-10-28 (76 days ago) dmi.bios.date: 07/31/2012 dmi.bios.vendor: TOSHIBA dmi.bios.version: Version 1.70 dmi.board.asset.tag: 00 dmi.board.name: Portable PC dmi.board.vendor: TOSHIBA dmi.board.version: Version A0 dmi.chassis.asset.tag: 00 dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: Version 1.0 dmi.modalias: dmi:bvnTOSHIBA:bvrVersion1.70:bd07/31/2012:svnTOSHIBA:pnSATELLITEZ830:pvrPT22LE-00300GGR:rvnTOSHIBA:rnPortablePC:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0: dmi.product.name: SATELLITE Z830 dmi.product.version: PT22LE-00300GGR dmi.sys.vendor: TOSHIBA version.compiz: compiz 1:0.9.8.6-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.39-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu6.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.99.99~git20120913.8637f772-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.9-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.2-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1099115/+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 1267449] Re: Dual monitor: monitor position included in its width
Thank you for reporting this bug to Ubuntu. Ubuntu 12.04 (precise) reached end-of-life on April 28, 2017. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: xorg (Ubuntu) Status: New => Won't Fix -- 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/1267449 Title: Dual monitor: monitor position included in its width Status in xorg package in Ubuntu: Won't Fix Bug description: I have two monitors, 1600x900 and 1920x1200, and I cannot place them next to each other. But it's possible to place the larger one below the second one. I suppose that monitor position is included in its size so the size limit is reached. Error messages: požadovaná poloha/velikost CRTC 148 je mimo povolený limit: poloha=(1440, 0), velikost=(1920, 1200), maximum=(2880, 2880) GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._gnome_2drr_2derror_2dquark.Code3: požadovaná poloha/velikost CRTC 148 je mimo povolený limit: poloha=(1440, 0), velikost=(1920, 1200), maximum=(2880, 2880) In English: requested position/size CRTC 148 out of allowed limit: position=(1440,0),size=(1920, 1200), maximum=(2880,2880) GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._gnome_2drr_2derror_2dquark.Code3: requested position /size CRTC 148 is out of range: position=(1440,0), size(1920,1200),maximum=(2880,2880) Ubuntu 12.04.3 LTS Release: 12.04 ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xorg 1:7.6+12ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-57.87-generic 3.2.52 Uname: Linux 3.2.0-57-generic x86_64 NonfreeKernelModules: fglrx .tmp.unity.support.test.0: ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 CompizPlugins: [core,composite,opengl,decor,mousepoll,compiztoolbox,resize,imgpng,move,vpswitch,gnomecompat,place,wall,snap,unitymtgrabhandles,grid,regex,animation,fade,expo,session,ezoom,workarounds,scale,unityshell] CompositorRunning: compiz Date: Thu Jan 9 13:09:42 2014 DistUpgraded: 2013-10-09 11:13:55,749 DEBUG enabling apt cron job DistroCodename: precise DistroVariant: ubuntu DkmsStatus: fglrx-experimental-12, 12.100, 3.2.0-54-generic, x86_64: installed fglrx-experimental-12, 12.100, 3.2.0-55-generic, x86_64: installed fglrx-experimental-12, 12.100, 3.2.0-56-generic, x86_64: installed fglrx-experimental-12, 12.100, 3.2.0-57-generic, x86_64: installed fglrx-experimental-12, 12.100, 3.2.0-58-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Thames [Radeon HD 7550M/7570M/7650M] [1002:6841] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:17aa] InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) JockeyStatus: xorg:fglrx - Uzavřený grafický ovladač FGLRX od ATI/AMD (Uzavřená, Zakázáno, Nepoužívá se) xorg:fglrx_experimental_12 - ATI/AMD proprietary FGLRX graphics driver (**experimental** beta) (Uzavřená, Povoleno, Nepoužívá se) xorg:fglrx_experimental_13 - ATI/AMD proprietary FGLRX graphics driver (**experimental** beta) (Uzavřená, Zakázáno, Nepoužívá se) xorg:fglrx_experimental_9 - ATI/AMD proprietary FGLRX graphics driver (**experimental** beta) (Uzavřená, Zakázáno, Nepoužívá se) xorg:fglrx_updates - Uzavřený grafický ovladač FGLRX od ATI/AMD (aktualizace po vydání) (Uzavřená, Zakázáno, Nepoužívá se) MachineType: Hewlett-Packard HP ProBook 6570b MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-57-generic root=UUID=c0a530ab-937d-4917-9026-fbedfa7bf14b ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to precise on 2013-10-09 (92 days ago) dmi.bios.date: 07/16/2013 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68ICE Ver. F.43 dmi.board.name: 17AB dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 42.36 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68ICEVer.F.43:bd07/16/2013:svnHewlett-Packard:pnHPProBook6570b:pvrA1029D1103:rvnHewlett-Packard:rn17AB:rvrKBCVersion42.36:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP ProBook 6570b dmi.product.version: A1029D1103 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.7.12-0ubuntu3 version.fglrx-installer: fglrx-installer N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1ubuntu0.0.0.1 version.libgl1-mesa-dri:
[Desktop-packages] [Bug 1229734] Re: libgl1-mesa-glx conflicts with nvidia-current (nvidia-304)
Thank you for reporting this bug to Ubuntu. Ubuntu 13.04 (raring) reached end-of-life on January 27, 2014. 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: xorg (Ubuntu) Status: Confirmed => Won't Fix -- 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/1229734 Title: libgl1-mesa-glx conflicts with nvidia-current (nvidia-304) Status in xorg package in Ubuntu: Won't Fix Bug description: NOTES: I am NOT using the xorg-edgers PPA. I am NOT using the non-package binary driver from nvidia.com I am NOT using nouveau. When the libgl1-mesa-glx package is installed and the nvidia-current (i.e. nvidia-304) package is also installed, something is running update-alternatives --set x86_64-linux-gnu_gl_conf /usr/lib/x86_64 -linux-gnu/mesa/ld.so.conf on what seems to be every boot. This is problematic, because in fact the alternative should be set like: update-alternatives --set x86_64-linux-gnu_gl_conf /usr/lib/nvidia-304/ld.so.conf Having the alternative set to mesa prevents the nvidia kernel and xorg modules from being loaded, which causes X to fall back to the built-in intel GPU and driver, which doesn't work. The result on boot is either: 1. A black screen with a couple of notices e.g.: [ 14.475147] i915 :00:02.0: Invalid ROM contents 2. A purple screen with no other content, but the "lightdm has started the greeter and is waiting for your password" noise is heard. Neither of these is a good result; in case 1 I can switch to different VT but I do not get a login prompt on any of them, and in case 2 I _cannot switch VT_. If the alternative is set to the nvidia conf and then the gui is started, for example by: 1. boot 2. enter recovery mode 3. fsck 4. drop to root prompt 5. update-alternatives --set x86_64-linux-gnu_gl_conf /usr/lib/nvidia-304/ld.so.conf 6. exit 7. resume normal boot. Everything works perfectly. AFAICT this is _NOT_ a bug in the NVidia binary driver, the wrong alternative is simply being used. I am reporting this issue against the libgl1-mesa-glx package, as that package provides the mesa ld.so.conf file in question. Extra details: Hardware: MacBookPro9,1 Ubuntu version: Raring x86_64 ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-30.44-generic 3.8.13.6 Uname: Linux 3.8.0-30-generic x86_64 NonfreeKernelModules: nvidia wl .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 304.88 Wed Mar 27 14:26:46 PDT 2013 GCC version: gcc version 4.7.3 (Ubuntu/Linaro 4.7.3-1ubuntu1) .tmp.unity.support.test.0: ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Tue Sep 24 23:19:52 2013 DistUpgraded: Fresh install DistroCodename: raring DistroVariant: ubuntu DkmsStatus: bcmwl, 6.20.155.1+bdcom, 3.8.0-19-generic, x86_64: installed bcmwl, 6.20.155.1+bdcom, 3.8.0-30-generic, x86_64: installed nvidia-304, 304.88, 3.8.0-30-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GpuHangFrequency: Once a week GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: I don't know GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. Device [106b:00fb] NVIDIA Corporation GK107M [GeForce GT 650M Mac Edition] [10de:0fd5] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. Device [106b:00fc] InstallationDate: Installed on 2013-09-17 (7 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Apple Inc. MacBookPro9,1 MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-30-generic root=UUID=9d41d1bf-0a1a-4969-8be4-bb0f4bdeb0a4 ro recovery nomodeset SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2012 dmi.bios.vendor: Apple Inc. dmi.bios.version:
[Desktop-packages] [Bug 1574667] Re: Mouse pointer occasionally jumps to the bottom-left corner
** Tags removed: precise -- 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/1574667 Title: Mouse pointer occasionally jumps to the bottom-left corner Status in xorg package in Ubuntu: Confirmed Bug description: Sometimes the mouse pointer jumps directly to the bottom-left corner of the screen, which results in opening the trash window when clicking. This seems to be related: https://ubuntu-mate.community/t/mouse- pointer-jumps-on-clicking-touchpad/2932. Thanks, MZ ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 BootLog: /dev/sda6: clean, 276587/40779776 files, 15261626/163117056 blocks CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Apr 25 15:55:54 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Skylake Integrated Graphics [1028:06b2] InstallationDate: Installed on 2016-04-23 (2 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:07dc Intel Corp. Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 064e:920b Suyin Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 5559 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed root=UUID=c5bc0a1d-3fe9-4ae5-81e9-de7d141b419c ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/21/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.5 dmi.board.name: 06CMH7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.5:bd12/21/2015:svnDellInc.:pnInspiron5559:pvr:rvnDellInc.:rn06CMH7:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 5559 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Mon Apr 25 13:43:44 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1156 vendor LGD xserver.version: 2:1.18.3-1ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1574667/+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 1674704] Re: blank screen after software update
Thank you for reporting this bug to Ubuntu. Ubuntu 12.04 (precise) reached end-of-life on April 28, 2017. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: xorg (Ubuntu) Status: New => Won't Fix -- 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/1674704 Title: blank screen after software update Status in xorg package in Ubuntu: Won't Fix Bug description: I ran "sudo apt-get upgrade" and after rebooting I started to have problems with the display. Now it's black even from the boot options screen (I mean before GRUB menu). I left the system go up end after connecting via ssh I could see the following in dmesg: [ 796.633789] [drm:radeon_cs_ioctl] *ERROR* Failed to schedule IB ! [ 797.133525] [drm:radeon_ib_schedule] *ERROR* radeon: couldn't schedule IB(8). [ 797.133531] [drm:radeon_cs_ioctl] *ERROR* Failed to schedule IB ! [ 797.633326] [drm:radeon_ib_schedule] *ERROR* radeon: couldn't schedule IB(9). [ 797.61] [drm:radeon_cs_ioctl] *ERROR* Failed to schedule IB ! [ 798.133117] [drm:radeon_ib_schedule] *ERROR* radeon: couldn't schedule IB(10). [ 798.133122] [drm:radeon_cs_ioctl] *ERROR* Failed to schedule IB ! [ 798.632897] [drm:radeon_ib_schedule] *ERROR* radeon: couldn't schedule IB(11). [ 798.632903] [drm:radeon_cs_ioctl] *ERROR* Failed to schedule IB ! [ 799.132682] [drm:radeon_ib_schedule] *ERROR* radeon: couldn't schedule IB(12). [ 799.132687] [drm:radeon_cs_ioctl] *ERROR* Failed to schedule IB ! [ 799.632462] [drm:radeon_ib_schedule] *ERROR* radeon: couldn't schedule IB(13). [ 799.632467] [drm:radeon_cs_ioctl] *ERROR* Failed to schedule IB ! [ 800.132257] [drm:radeon_ib_schedule] *ERROR* radeon: couldn't schedule IB(14). [ 800.132263] [drm:radeon_cs_ioctl] *ERROR* Failed to schedule IB ! [ 800.632060] [drm:radeon_ib_schedule] *ERROR* radeon: couldn't schedule IB(15). [ 800.632065] [drm:radeon_cs_ioctl] *ERROR* Failed to schedule IB ! [ 801.131826] [drm:radeon_ib_schedule] *ERROR* radeon: couldn't schedule IB(0). [ 801.131832] [drm:radeon_cs_ioctl] *ERROR* Failed to schedule IB ! [ 801.631619] [drm:radeon_ib_schedule] *ERROR* radeon: couldn't schedule IB(1). [ 801.631624] [drm:radeon_cs_ioctl] *ERROR* Failed to schedule IB ! [ 802.131420] [drm:radeon_ib_schedule] *ERROR* radeon: couldn't schedule IB(2). [ 802.131426] [drm:radeon_cs_ioctl] *ERROR* Failed to schedule IB ! [ 802.631209] [drm:radeon_ib_schedule] *ERROR* radeon: couldn't schedule IB(3). $ uname -a Linux ajax 3.2.0-124-generic #167-Ubuntu SMP Fri Mar 3 15:25:36 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux Any suggestion? Thanks in advance, Giuseppe ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xorg 1:7.6+12ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-124.167-generic 3.2.79 Uname: Linux 3.2.0-124-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.15 Architecture: amd64 Date: Tue Mar 21 15:25:55 2017 InstallationMedia: Kubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120423) MarkForUpload: True SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1674704/+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 1744421] Re: I tried to upgrade from 16.4 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: xorg (Ubuntu) Status: New => Won't Fix -- 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/1744421 Title: I tried to upgrade from 16.4 to 17.10 Status in xorg package in Ubuntu: Won't Fix Bug description: Trying to upgrade from version 16.04 to 17.10, I used the following command line: sudo apt update && sudo apt dist -upgrade ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13 Uname: Linux 4.13.0-26-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sat Jan 20 00:03:32 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: virtualbox, 5.0.40, 4.10.0-42-generic, x86_64: installed virtualbox, 5.0.40, 4.13.0-26-generic, x86_64: installed GraphicsCard: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display [8086:0f31] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Atom Processor Z36xxx/Z37xxx Series Graphics & Display [103c:2209] InstallationDate: Installed on 2017-10-27 (84 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 1a40:0101 Terminus Technology Inc. Hub Bus 001 Device 002: ID 04f2:b40e Chicony Electronics Co., Ltd HP Truevision HD camera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Hewlett-Packard HP Pavilion 11 x360 PC ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) LANG=pt_BR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-26-generic root=UUID=9b0f7d79-6ae1-4287-8ac7-7ca5bec70fb0 ro splash quiet SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/13/2016 dmi.bios.vendor: Insyde dmi.bios.version: F.2B dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 2209 dmi.board.vendor: Hewlett-Packard dmi.board.version: 57.54 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.2B:bd06/13/2016:svnHewlett-Packard:pnHPPavilion11x360PC:pvr097810405F00010320180:rvnHewlett-Packard:rn2209:rvr57.54:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=MIN dmi.product.name: HP Pavilion 11 x360 PC dmi.product.version: 097810405F00010320180 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.4 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 Jan 19 23:59:58 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.5-0ubuntu2~16.04.1 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1744421/+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 1740635] Re: Correct screen resolution not available on Ubuntu 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: xorg (Ubuntu) Status: New => Won't Fix -- 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/1740635 Title: Correct screen resolution not available on Ubuntu 17.10 Status in xorg package in Ubuntu: Won't Fix Bug description: I did a fresh installation of Ubuntu 17.10 on my Dell Precision M2800. I use two external displays (both Dell U2715Hc) with a screen resolution of 2560x1440 (one connected over HDMI-1, the other over DP-1). On the one connected over HDMI the maximum available resolution is 2048x1152. I tried to add the missing resolution with xrandr to HDMI-1 - but this was not successful (Error: could not apply...). ... 00:02.0 VGA compatible controller [0300]: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) Subsystem: Dell 4th Gen Core Processor Integrated Graphics Controller [1028:0684] 01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Mars XTX [Radeon HD 8790M] [1002:6606] Kernel driver in use: radeon Kernel modules: radeon, amdgpu Linux swinkler-Precision-M2800 4.13.0-19-generic #22-Ubuntu SMP Mon Dec 4 11:58:07 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux /usr/lib/xorg/Xorg.wrap: Only console users are allowed to run the X server Hit:1 http://ch.archive.ubuntu.com/ubuntu artful InRelease Hit:2 http://ch.archive.ubuntu.com/ubuntu artful-updates InRelease Get:3 http://security.ubuntu.com/ubuntu artful-security InRelease [78.6 kB] Hit:4 http://ch.archive.ubuntu.com/ubuntu artful-backports InRelease Hit:5 http://ppa.launchpad.net/ubuntu-x-swat/updates/ubuntu artful InRelease Fetched 78.6 kB in 0s (194 kB/s) Reading package lists... Done Reading package lists... Done Building dependency tree Reading state information... Done fbset is already the newest version (2.1-29ubuntu1). hardinfo is already the newest version (0.5.1+git20170815-1). inxi is already the newest version (2.3.37-1). mesa-utils is already the newest version (8.3.0-5). nux-tools is already the newest version (4.0.8+17.10.20170922-0ubuntu1). 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. System:Host: swinkler-Precision-M2800 Kernel: 4.13.0-19-generic x86_64 bits: 64 Desktop: Gnome 3.26.2 Distro: Ubuntu 17.10 Machine: Device: laptop System: Dell product: Precision M2800 v: 01 serial: N/A Mobo: Dell model: 01P6V3 v: A00 serial: N/A BIOS: Dell v: A06 date: 05/18/2015 BatteryBAT0: charge: 42.0 Wh 93.5% condition: 44.9/65.5 Wh (69%) CPU: Quad core Intel Core i7-4810MQ (-HT-MCP-) cache: 6144 KB clock speeds: max: 3800 MHz 1: 2793 MHz 2: 2793 MHz 3: 2793 MHz 4: 2793 MHz 5: 2793 MHz 6: 2793 MHz 7: 2793 MHz 8: 2793 MHz Graphics: Card-1: Intel 4th Gen Core Processor Integrated Graphics Controller Card-2: Advanced Micro Devices [AMD/ATI] Mars XTX [Radeon HD 8790M] Display Server: x11 (X.Org 1.19.5 ) drivers: i915,radeon Resolution: 2048x1152@60.00hz, 2560x1440@59.95hz OpenGL: renderer: Mesa DRI Intel Haswell Mobile version: 4.5 Mesa 17.2.4 Audio: Card-1 Intel 8 Series/C220 Series High Definition Audio Controller driver: snd_hda_intel Card-2 Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller driver: snd_hda_intel Sound: Advanced Linux Sound Architecture v: k4.13.0-19-generic Network: Card-1: Intel Ethernet Connection I217-LM driver: e1000e IF: eno1 state: up speed: 1000 Mbps duplex: full mac: 34:e6:d7:87:64:35 Card-2: Intel Wireless 7260 driver: iwlwifi IF: wlp3s0 state: down mac: ac:fd:ce:4c:4a:8c Drives:HDD Total Size: 1272.3GB (28.8% used) ID-1: USB /dev/sda model: Rugged_Mini_USB3 size: 1000.2GB ID-2: USB /dev/sdb model: USB_Flash_Disk size: 16.0GB ID-3: /dev/sdc model: LITEONIT_LCS size: 256.1GB Partition: ID-1: / size: 218G used: 17G (9%) fs: ext4 dev: /dev/dm-1 ID-2: /boot size: 704M used: 137M (21%) fs: ext4 dev: /dev/sdc1 ID-3:
[Desktop-packages] [Bug 1670091] Re: pointeur
Thank you for reporting this bug to Ubuntu. Ubuntu 16.10 (yakkety) reached end-of-life on July 20, 2017. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: xorg (Ubuntu) Status: New => Won't Fix -- 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/1670091 Title: pointeur Status in xorg package in Ubuntu: Won't Fix Bug description: Bonjour dernièremment sous ubuntu 16.10 mo pointeur est invisible dans la moitié inférieure de mon écran si je démare avec option avancé ubuntu ancienne version linux cela ne le fait pas cordialement YC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1670091/+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 1678635] Re: Some keys on Portuguese Apple aluminium are incorrect
Thank you for reporting this bug to Ubuntu. Ubuntu 16.10 (yakkety) reached end-of-life on July 20, 2017. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: xorg (Ubuntu) Status: New => Won't Fix -- 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/1678635 Title: Some keys on Portuguese Apple aluminium are incorrect Status in xorg package in Ubuntu: Won't Fix Bug description: I use a Portuguese layout Apple aluminium keyboard on Ubuntu 16.10. While the mappings are correct for nearly all the keys, several keys are mapped incorrectly according to the legends on the keycaps: 1. the key left of z is marked as greater-than / less-than, yet when pressed yields the noncombining backtick and tilde characters. 2. The Euro symbol is shown as the alt-gr symbol on the three, yet this produces a £ sign (alt-gr E produces a Euro instead) 3. the section sign / plus-minus sign characters are shown on the key to the left of the "1", but this key produces the greater-than and less-than signs instead. I've enclosed the standard information in a zip file, plus a photo I took of the left hand side of the keyboard in case my explanations are a touch inadequate. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1678635/+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 1808979] Re: package python-gtk2-dev 2.24.0-5.1ubuntu2 failed to install/upgrade: installed python-gtk2-dev package post-installation script subprocess returned error exit stat
The issue is in python-defaults, maybe on systemd where the default python was changed Setting up python-gtk2-dev (2.24.0-5.1ubuntu2) ... File "/usr/bin/pyversions", line 20 except IOError, msg: ** Package changed: pygtk (Ubuntu) => python-defaults (Ubuntu) ** Changed in: python-defaults (Ubuntu) Status: Confirmed => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pygtk in Ubuntu. https://bugs.launchpad.net/bugs/1808979 Title: package python-gtk2-dev 2.24.0-5.1ubuntu2 failed to install/upgrade: installed python-gtk2-dev package post-installation script subprocess returned error exit status 1 Status in python-defaults package in Ubuntu: New Bug description: error by update ProblemType: Package DistroRelease: Ubuntu 18.04 Package: python-gtk2-dev 2.24.0-5.1ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 AptOrdering: gnome-desktop3-data:amd64: Install libgnome-desktop-3-17:amd64: Install gir1.2-gnomedesktop-3.0:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Tue Dec 18 14:33:12 2018 ErrorMessage: installed python-gtk2-dev package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2015-08-09 (1226 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) 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, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.6 SourcePackage: pygtk Title: package python-gtk2-dev 2.24.0-5.1ubuntu2 failed to install/upgrade: installed python-gtk2-dev package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to bionic on 2018-08-19 (121 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-defaults/+bug/1808979/+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 1832041] Re: The mouse stops working
It appears your mouse is USB and not related to wireless. Please choose one problem you would like to be this bug about, and optionally open a new bug for the other problem. ** 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/1832041 Title: The mouse stops working Status in linux package in Ubuntu: Incomplete Bug description: Sometime the wifi is not getting detected and the mouse is not working and and i am using touch instead of mouse, the external mouse is also not working ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.18.0-21.22~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-21-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Jun 8 00:40:19 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 390.116, 4.15.0-47-generic, x86_64: installed nvidia, 390.116, 4.15.0-51-generic, x86_64: installed nvidia, 390.116, 4.18.0-17-generic, x86_64: installed nvidia, 390.116, 4.18.0-21-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company UHD Graphics 620 [103c:83ba] Subsystem: Hewlett-Packard Company GP108M [GeForce MX150] [103c:83ba] InstallationDate: Installed on 2019-04-04 (64 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0025 Intel Corp. Bus 001 Device 003: ID 05c8:0815 Cheng Uei Precision Industry Co., Ltd (Foxlink) Bus 001 Device 009: ID 03f0:0941 Hewlett-Packard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Spectre x360 Convertible 15-ch0xx ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-21-generic root=UUID=a759c10c-be50-4caf-bd43-1516b97d1c6a ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/15/2018 dmi.bios.vendor: AMI dmi.bios.version: F.23 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 83BA dmi.board.vendor: HP dmi.board.version: 57.31 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.23:bd10/15/2018:svnHP:pnHPSpectrex360Convertible15-ch0xx:pvr:rvnHP:rn83BA:rvr57.31:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre x360 Convertible 15-ch0xx dmi.product.sku: 2FW61AV dmi.sys.vendor: HP version.compiz: compiz N/A 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 N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832041/+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 1615438] Re: package python-gtk2-dev 2.24.0-3ubuntu3 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1
** Changed in: pygtk (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pygtk in Ubuntu. https://bugs.launchpad.net/bugs/1615438 Title: package python-gtk2-dev 2.24.0-3ubuntu3 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 Status in pygtk package in Ubuntu: Invalid Bug description: I just upgraded from 14.04 to 16.04 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: python-gtk2-dev 2.24.0-3ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 Uname: Linux 4.4.0-34-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Thu Aug 18 17:16:42 2016 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2013-12-15 (980 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: pygtk Title: package python-gtk2-dev 2.24.0-3ubuntu3 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2016-08-18 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pygtk/+bug/1615438/+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 1317884] Re: Problem during upgrade from 10.4 to 12.1
the issue was a local I/O problem rather than a package bug ** Changed in: pygtk (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pygtk in Ubuntu. https://bugs.launchpad.net/bugs/1317884 Title: Problem during upgrade from 10.4 to 12.1 Status in pygtk package in Ubuntu: Invalid Bug description: cannot copy extracted data for './usr/lib/python2.7/dist- packages/gtk-2.0/gtk/_gtk.so' to '/usr/lib/python2.7/dist- packages/gtk-2.0/gtk/_gtk.so.dpkg-new': unexpected end of file or stream To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pygtk/+bug/1317884/+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 1826918] Re: gnome-shell crashed with SIGSEGV in meta_x11_display_get_xdisplay() from detach_pixmap() from meta_surface_actor_x11_dispose() from g_object_unref() from g_object_
** Changed in: mutter (Ubuntu) Assignee: (unassigned) => Daniel van Vugt (vanvugt) ** Changed in: mutter (Ubuntu) Status: New => In Progress -- 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/1826918 Title: gnome-shell crashed with SIGSEGV in meta_x11_display_get_xdisplay() from detach_pixmap() from meta_surface_actor_x11_dispose() from g_object_unref() from g_object_unref() Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: New Status in mutter package in Ubuntu: In Progress Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.32.0+git20190410-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/1a5d1f99fd9215f7a79b718d2e915c675ebcd69f contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1826918/+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 1832475] [NEW] tty do no work after putting laptop on docking station
Public bug reported:
On ubuntu 18.04 using gdm3 and gnome-shell, getting into virtual
consoles works well when the laptop is not on the docking station. After
putting it on the docking station (getting then 2 monitors), using
CTRL+ALT+F{3,4,5,6} freezes the GUI. I can come back to GUI using
CTRL+ALT+F7.
However, after going in text mode ("systemctl isolate multi-
user.target") and restarting gdm3, it works again, even if already on
the docking station.
It looks like putting the laptop on the docking station make this bug
happen. It does not happen when the laptop is booted on the docking
station.
Description:Ubuntu 18.04.2 LTS
Release:18.04
gdm3:
Installé : 3.28.3-0ubuntu18.04.4
Candidat : 3.28.3-0ubuntu18.04.4
Table de version :
*** 3.28.3-0ubuntu18.04.4 700
700 http://fr.archive.ubuntu.com/ubuntu bionic-updates/main amd64
Packages
700 http://security.ubuntu.com/ubuntu bionic-security/main amd64
Packages
100 /var/lib/dpkg/status
3.28.0-0ubuntu1 700
700 http://fr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
gnome-shell:
Installé : 3.28.4-0ubuntu18.04.1
Candidat : 3.28.4-0ubuntu18.04.1
Table de version :
*** 3.28.4-0ubuntu18.04.1 700
700 http://fr.archive.ubuntu.com/ubuntu bionic-updates/main amd64
Packages
100 /var/lib/dpkg/status
3.28.3+git20190124-0ubuntu18.04.2 700
700 http://security.ubuntu.com/ubuntu bionic-security/main amd64
Packages
3.28.1-0ubuntu2 700
700 http://fr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
** Affects: gdm3 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1832475
Title:
tty do no work after putting laptop on docking station
Status in gdm3 package in Ubuntu:
New
Bug description:
On ubuntu 18.04 using gdm3 and gnome-shell, getting into virtual
consoles works well when the laptop is not on the docking station.
After putting it on the docking station (getting then 2 monitors),
using CTRL+ALT+F{3,4,5,6} freezes the GUI. I can come back to GUI
using CTRL+ALT+F7.
However, after going in text mode ("systemctl isolate multi-
user.target") and restarting gdm3, it works again, even if already on
the docking station.
It looks like putting the laptop on the docking station make this bug
happen. It does not happen when the laptop is booted on the docking
station.
Description: Ubuntu 18.04.2 LTS
Release: 18.04
gdm3:
Installé : 3.28.3-0ubuntu18.04.4
Candidat : 3.28.3-0ubuntu18.04.4
Table de version :
*** 3.28.3-0ubuntu18.04.4 700
700 http://fr.archive.ubuntu.com/ubuntu bionic-updates/main amd64
Packages
700 http://security.ubuntu.com/ubuntu bionic-security/main amd64
Packages
100 /var/lib/dpkg/status
3.28.0-0ubuntu1 700
700 http://fr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
gnome-shell:
Installé : 3.28.4-0ubuntu18.04.1
Candidat : 3.28.4-0ubuntu18.04.1
Table de version :
*** 3.28.4-0ubuntu18.04.1 700
700 http://fr.archive.ubuntu.com/ubuntu bionic-updates/main amd64
Packages
100 /var/lib/dpkg/status
3.28.3+git20190124-0ubuntu18.04.2 700
700 http://security.ubuntu.com/ubuntu bionic-security/main amd64
Packages
3.28.1-0ubuntu2 700
700 http://fr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1832475/+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 1808979] Re: package python-gtk2-dev 2.24.0-5.1ubuntu2 failed to install/upgrade: installed python-gtk2-dev package post-installation script subprocess returned error exit stat
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: pygtk (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pygtk in Ubuntu. https://bugs.launchpad.net/bugs/1808979 Title: package python-gtk2-dev 2.24.0-5.1ubuntu2 failed to install/upgrade: installed python-gtk2-dev package post-installation script subprocess returned error exit status 1 Status in pygtk package in Ubuntu: Confirmed Bug description: error by update ProblemType: Package DistroRelease: Ubuntu 18.04 Package: python-gtk2-dev 2.24.0-5.1ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 AptOrdering: gnome-desktop3-data:amd64: Install libgnome-desktop-3-17:amd64: Install gir1.2-gnomedesktop-3.0:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Tue Dec 18 14:33:12 2018 ErrorMessage: installed python-gtk2-dev package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2015-08-09 (1226 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) 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, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.6 SourcePackage: pygtk Title: package python-gtk2-dev 2.24.0-5.1ubuntu2 failed to install/upgrade: installed python-gtk2-dev package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to bionic on 2018-08-19 (121 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pygtk/+bug/1808979/+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
