[Desktop-packages] [Bug 1818089] Re: Cups can not print with "filter failed" error just after ghostcript update
That's your issue libfreetype.so.6 => /usr/local/lib/libfreetype.so.6 (0x7fdffae76000) You have an outdated local installation you did that is taking over the Ubuntu version, clean that one out and things should be back to working. Closing since that's not an Ubuntu bug ** Changed in: ghostscript (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ghostscript in Ubuntu. https://bugs.launchpad.net/bugs/1818089 Title: Cups can not print with "filter failed" error just after ghostcript update Status in ghostscript package in Ubuntu: Invalid Bug description: I was using my Epson 105 printer properly till i decided to do recommended upgrade to recent version of ghostscript after which my pinter stopped working. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ghostscript 9.26~dfsg+0-0ubuntu0.18.04.7 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Feb 28 20:31:23 2019 InstallationDate: Installed on 2018-06-01 (272 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: ghostscript UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1818089/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1818089] Re: Cups can not print with "filter failed" error just after ghostcript update
This is detailed error log of cups with debug mode on. ** Attachment added: "CUPS Error log with debug mode" https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1818089/+attachment/5242514/+files/cups_error_log.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ghostscript in Ubuntu. https://bugs.launchpad.net/bugs/1818089 Title: Cups can not print with "filter failed" error just after ghostcript update Status in ghostscript package in Ubuntu: Incomplete Bug description: I was using my Epson 105 printer properly till i decided to do recommended upgrade to recent version of ghostscript after which my pinter stopped working. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ghostscript 9.26~dfsg+0-0ubuntu0.18.04.7 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Feb 28 20:31:23 2019 InstallationDate: Installed on 2018-06-01 (272 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: ghostscript UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1818089/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1818089] Re: Cups can not print with "filter failed" error just after ghostcript update
Sorry that was output when I tried downgrade to gs9.22 This is with gs9.26 ldd -r /usr/lib/x86_64-linux-gnu/libgs.so.9 linux-vdso.so.1 (0x7ffe549ab000) libtiff.so.5 => /usr/lib/x86_64-linux-gnu/libtiff.so.5 (0x7fb4d87d1000) libcupsimage.so.2 => /usr/lib/x86_64-linux-gnu/libcupsimage.so.2 (0x7fb4d85c8000) libcups.so.2 => /usr/lib/x86_64-linux-gnu/libcups.so.2 (0x7fb4d833c000) libijs-0.35.so => /usr/lib/x86_64-linux-gnu/libijs-0.35.so (0x7fb4d8136000) libpng16.so.16 => /usr/lib/x86_64-linux-gnu/libpng16.so.16 (0x7fb4d7f04000) libjbig2dec.so.0 => /usr/lib/x86_64-linux-gnu/libjbig2dec.so.0 (0x7fb4d7cec000) libjpeg.so.8 => /usr/lib/x86_64-linux-gnu/libjpeg.so.8 (0x7fb4d7a84000) libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7fb4d7867000) liblcms2.so.2 => /usr/lib/x86_64-linux-gnu/liblcms2.so.2 (0x7fb4d760f000) libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7fb4d7271000) libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7fb4d706d000) libidn.so.11 => /lib/x86_64-linux-gnu/libidn.so.11 (0x7fb4d6e3a000) libpaper.so.1 => /usr/lib/x86_64-linux-gnu/libpaper.so.1 (0x7fb4d6c36000) libfontconfig.so.1 => /usr/lib/x86_64-linux-gnu/libfontconfig.so.1 (0x7fb4d69f1000) libfreetype.so.6 => /usr/local/lib/libfreetype.so.6 (0x7fb4d6765000) libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x7fb4d6546000) libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7fb4d6155000) liblzma.so.5 => /lib/x86_64-linux-gnu/liblzma.so.5 (0x7fb4d5f2f000) libjbig.so.0 => /usr/lib/x86_64-linux-gnu/libjbig.so.0 (0x7fb4d5d21000) libgssapi_krb5.so.2 => /usr/lib/x86_64-linux-gnu/libgssapi_krb5.so.2 (0x7fb4d5ad6000) libgnutls.so.30 => /usr/lib/x86_64-linux-gnu/libgnutls.so.30 (0x7fb4d5771000) libavahi-common.so.3 => /usr/lib/x86_64-linux-gnu/libavahi-common.so.3 (0x7fb4d5565000) libavahi-client.so.3 => /usr/lib/x86_64-linux-gnu/libavahi-client.so.3 (0x7fb4d5354000) /lib64/ld-linux-x86-64.so.2 (0x7fb4d9bf1000) libexpat.so.1 => /lib/x86_64-linux-gnu/libexpat.so.1 (0x7fb4d5122000) libkrb5.so.3 => /usr/lib/x86_64-linux-gnu/libkrb5.so.3 (0x7fb4d4e4c000) libk5crypto.so.3 => /usr/lib/x86_64-linux-gnu/libk5crypto.so.3 (0x7fb4d4c1a000) libcom_err.so.2 => /lib/x86_64-linux-gnu/libcom_err.so.2 (0x7fb4d4a16000) libkrb5support.so.0 => /usr/lib/x86_64-linux-gnu/libkrb5support.so.0 (0x7fb4d480b000) libp11-kit.so.0 => /usr/lib/x86_64-linux-gnu/libp11-kit.so.0 (0x7fb4d44dc000) libidn2.so.0 => /usr/lib/x86_64-linux-gnu/libidn2.so.0 (0x7fb4d42bf000) libunistring.so.2 => /usr/lib/x86_64-linux-gnu/libunistring.so.2 (0x7fb4d3f41000) libtasn1.so.6 => /usr/lib/x86_64-linux-gnu/libtasn1.so.6 (0x7fb4d3d2e000) libnettle.so.6 => /usr/lib/x86_64-linux-gnu/libnettle.so.6 (0x7fb4d3af8000) libhogweed.so.4 => /usr/lib/x86_64-linux-gnu/libhogweed.so.4 (0x7fb4d38c4000) libgmp.so.10 => /usr/lib/x86_64-linux-gnu/libgmp.so.10 (0x7fb4d3643000) libdbus-1.so.3 => /lib/x86_64-linux-gnu/libdbus-1.so.3 (0x7fb4d33f6000) libkeyutils.so.1 => /lib/x86_64-linux-gnu/libkeyutils.so.1 (0x7fb4d31f2000) libresolv.so.2 => /lib/x86_64-linux-gnu/libresolv.so.2 (0x7fb4d2fd7000) libffi.so.6 => /usr/lib/x86_64-linux-gnu/libffi.so.6 (0x7fb4d2dcf000) libsystemd.so.0 => /lib/x86_64-linux-gnu/libsystemd.so.0 (0x7fb4d2b4b000) librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x7fb4d2943000) liblz4.so.1 => /usr/lib/x86_64-linux-gnu/liblz4.so.1 (0x7fb4d2727000) libgcrypt.so.20 => /lib/x86_64-linux-gnu/libgcrypt.so.20 (0x7fb4d240c000) libgpg-error.so.0 => /lib/x86_64-linux-gnu/libgpg-error.so.0 (0x7fb4d21f7000) undefined symbol: FT_Property_Set (/usr/lib/x86_64-linux-gnu/libgs.so.9) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ghostscript in Ubuntu. https://bugs.launchpad.net/bugs/1818089 Title: Cups can not print with "filter failed" error just after ghostcript update Status in ghostscript package in Ubuntu: Incomplete Bug description: I was using my Epson 105 printer properly till i decided to do recommended upgrade to recent version of ghostscript after which my pinter stopped working. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ghostscript 9.26~dfsg+0-0ubuntu0.18.04.7 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Feb 28 20:31:23 2019
[Desktop-packages] [Bug 1818089] Re: Cups can not print with "filter failed" error just after ghostcript update
Following is the requested output artim@artim-ML10Gen9:~$ ldd -r /usr/lib/x86_64-linux-gnu/libgs.so.9 linux-vdso.so.1 (0x7fff542c9000) libtiff.so.5 => /usr/lib/x86_64-linux-gnu/libtiff.so.5 (0x7fdffcee2000) libcupsimage.so.2 => /usr/lib/x86_64-linux-gnu/libcupsimage.so.2 (0x7fdffccd9000) libcups.so.2 => /usr/lib/x86_64-linux-gnu/libcups.so.2 (0x7fdffca4d000) libijs-0.35.so => /usr/lib/x86_64-linux-gnu/libijs-0.35.so (0x7fdffc847000) libpng16.so.16 => /usr/lib/x86_64-linux-gnu/libpng16.so.16 (0x7fdffc615000) libjbig2dec.so.0 => /usr/lib/x86_64-linux-gnu/libjbig2dec.so.0 (0x7fdffc3fd000) libjpeg.so.8 => /usr/lib/x86_64-linux-gnu/libjpeg.so.8 (0x7fdffc195000) libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7fdffbf78000) liblcms2.so.2 => /usr/lib/x86_64-linux-gnu/liblcms2.so.2 (0x7fdffbd2) libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7fdffb982000) libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7fdffb77e000) libidn.so.11 => /lib/x86_64-linux-gnu/libidn.so.11 (0x7fdffb54b000) libpaper.so.1 => /usr/lib/x86_64-linux-gnu/libpaper.so.1 (0x7fdffb347000) libfontconfig.so.1 => /usr/lib/x86_64-linux-gnu/libfontconfig.so.1 (0x7fdffb102000) libfreetype.so.6 => /usr/local/lib/libfreetype.so.6 (0x7fdffae76000) libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x7fdffac57000) libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7fdffa866000) liblzma.so.5 => /lib/x86_64-linux-gnu/liblzma.so.5 (0x7fdffa64) libjbig.so.0 => /usr/lib/x86_64-linux-gnu/libjbig.so.0 (0x7fdffa432000) libgssapi_krb5.so.2 => /usr/lib/x86_64-linux-gnu/libgssapi_krb5.so.2 (0x7fdffa1e7000) libgnutls.so.30 => /usr/lib/x86_64-linux-gnu/libgnutls.so.30 (0x7fdff9e82000) libavahi-common.so.3 => /usr/lib/x86_64-linux-gnu/libavahi-common.so.3 (0x7fdff9c76000) libavahi-client.so.3 => /usr/lib/x86_64-linux-gnu/libavahi-client.so.3 (0x7fdff9a65000) /lib64/ld-linux-x86-64.so.2 (0x7fdffe2be000) libexpat.so.1 => /lib/x86_64-linux-gnu/libexpat.so.1 (0x7fdff9833000) libkrb5.so.3 => /usr/lib/x86_64-linux-gnu/libkrb5.so.3 (0x7fdff955d000) libk5crypto.so.3 => /usr/lib/x86_64-linux-gnu/libk5crypto.so.3 (0x7fdff932b000) libcom_err.so.2 => /lib/x86_64-linux-gnu/libcom_err.so.2 (0x7fdff9127000) libkrb5support.so.0 => /usr/lib/x86_64-linux-gnu/libkrb5support.so.0 (0x7fdff8f1c000) libp11-kit.so.0 => /usr/lib/x86_64-linux-gnu/libp11-kit.so.0 (0x7fdff8bed000) libidn2.so.0 => /usr/lib/x86_64-linux-gnu/libidn2.so.0 (0x7fdff89d) libunistring.so.2 => /usr/lib/x86_64-linux-gnu/libunistring.so.2 (0x7fdff8652000) libtasn1.so.6 => /usr/lib/x86_64-linux-gnu/libtasn1.so.6 (0x7fdff843f000) libnettle.so.6 => /usr/lib/x86_64-linux-gnu/libnettle.so.6 (0x7fdff8209000) libhogweed.so.4 => /usr/lib/x86_64-linux-gnu/libhogweed.so.4 (0x7fdff7fd5000) libgmp.so.10 => /usr/lib/x86_64-linux-gnu/libgmp.so.10 (0x7fdff7d54000) libdbus-1.so.3 => /lib/x86_64-linux-gnu/libdbus-1.so.3 (0x7fdff7b07000) libkeyutils.so.1 => /lib/x86_64-linux-gnu/libkeyutils.so.1 (0x7fdff7903000) libresolv.so.2 => /lib/x86_64-linux-gnu/libresolv.so.2 (0x7fdff76e8000) libffi.so.6 => /usr/lib/x86_64-linux-gnu/libffi.so.6 (0x7fdff74e) libsystemd.so.0 => /lib/x86_64-linux-gnu/libsystemd.so.0 (0x7fdff725c000) librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x7fdff7054000) liblz4.so.1 => /usr/lib/x86_64-linux-gnu/liblz4.so.1 (0x7fdff6e38000) libgcrypt.so.20 => /lib/x86_64-linux-gnu/libgcrypt.so.20 (0x7fdff6b1d000) libgpg-error.so.0 => /lib/x86_64-linux-gnu/libgpg-error.so.0 (0x7fdff6908000) undefined symbol: FT_Property_Set (/usr/lib/x86_64-linux-gnu/libgs.so.9) artim@artim-ML10Gen9:~$ "dpkg -l | grep freetype" dpkg -l | grep freetype: command not found artim@artim-ML10Gen9:~$ dpkg -l | grep freetype ii libfreetype6:amd642.8.1-2ubuntu2 amd64FreeType 2 font engine, shared library files ii libfreetype6:i386 2.8.1-2ubuntu2 i386 FreeType 2 font engine, shared library files -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ghostscript in Ubuntu. https://bugs.launchpad.net/bugs/1818089 Title: Cups can not print with "filter failed" error just after ghostcript update Status in ghostscript package in Ubuntu: Incomplete Bug description: I was using my Epson 105 printer properly till i decided to do recommended upgrade to recent
[Desktop-packages] [Bug 1795702] Re: snap-store reports incorrect OS to odrs
** Changed in: gnome-software (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1795702 Title: snap-store reports incorrect OS to odrs Status in gnome-software package in Ubuntu: Fix Released Bug description: Install snap-store - "snap install snap-store" Snap store - "snap run snap-store" Find an application (I opened Wire) Scroll down and click "Write a review" Write a review. Find your review on ODRS https://odrs.gnome.org Note the "Distro" says "Ubuntu Core". This is not correct, as I am on KDE Neon right now. Here is mine. https://odrs.gnome.org/admin/review/9621 In case the content changes I have attached a screenshot. This error is likely because snap-store is a confined snap application. /etc/os-release is allowed in the default template. Note this will be of the core/base snap, not the host. To read the host, you can use the system-observe interface which exposes /var/lib/snapd/hostfs/etc/os- release to the snap from the host. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1795702/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1818152] Re: Nvidia 340
** Also affects: nvidia-graphics-drivers-340 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1818152 Title: Nvidia 340 Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340 package in Ubuntu: New Bug description: After installing NVIDIA driver, the screen brightness is freezed by 100% ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-45-generic 4.15.0-45.48 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 NonfreeKernelModules: wl nvidia ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: senne 2237 F...m pulseaudio /dev/snd/controlC0: senne 2237 F pulseaudio CurrentDesktop: XFCE Date: Thu Feb 28 23:00:25 2019 InstallationDate: Installed on 2018-12-24 (66 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Apple Inc. MacBook5,1 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=UUID=8980397b-61c8-4011-a75c-9777552c623c ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-45-generic N/A linux-backports-modules-4.15.0-45-generic N/A linux-firmware 1.173.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/27/09 dmi.bios.vendor: Apple Inc. dmi.bios.version: MB51.88Z.007D.B03.0904271443 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-F42D89C8 dmi.board.vendor: Apple Inc. dmi.board.version: Proto dmi.chassis.asset.tag: Asset Tag# dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F42D89C8 dmi.modalias: dmi:bvnAppleInc.:bvrMB51.88Z.007D.B03.0904271443:bd04/27/09:svnAppleInc.:pnMacBook5,1:pvr1.0:rvnAppleInc.:rnMac-F42D89C8:rvrProto:cvnAppleInc.:ct10:cvrMac-F42D89C8: dmi.product.family: MacBook dmi.product.name: MacBook5,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818152/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1818101] Re: nvidia dkms modules fail to build with linux 4.4.0-143.169 [error: too many arguments to function ‘get_user_pages’]
*** This bug is a duplicate of bug 1573508 *** https://bugs.launchpad.net/bugs/1573508 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1573508, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** Summary changed: - nvidia dkms modules fail to build with linux 4.4.0-143.169 + nvidia dkms modules fail to build with linux 4.4.0-143.169 [error: too many arguments to function ‘get_user_pages’] ** This bug has been marked a duplicate of bug 1573508 nvidia-*: nvidia-* kernel module failed to build [error: too many arguments to function ‘get_user_pages’] -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1818101 Title: nvidia dkms modules fail to build with linux 4.4.0-143.169 [error: too many arguments to function ‘get_user_pages’] Status in Nvidia: New Status in nvidia-graphics-drivers-304 package in Ubuntu: New Status in nvidia-graphics-drivers-340 package in Ubuntu: New Status in nvidia-graphics-drivers-384 package in Ubuntu: New Status in nvidia-graphics-drivers-304 source package in Trusty: New Status in nvidia-graphics-drivers-340 source package in Trusty: New Status in nvidia-graphics-drivers-384 source package in Trusty: New Status in nvidia-graphics-drivers-304 source package in Xenial: New Status in nvidia-graphics-drivers-340 source package in Xenial: New Status in nvidia-graphics-drivers-384 source package in Xenial: New Bug description: [Impact] nvidia dkms modules (304, 340, 384) fail to build after Ubuntu kernel 4.4 backported the following fix from upstream stable, which is included on xenial kernel 4.4.0-143.169 that's currently in -proposed. mm: replace get_user_pages() write/force parameters with gup_flags https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/xenial/commit/?h=master-next=9c72ad08f1510332e9314046e6a2adba5064f39a Excerpt from ./nvidia-304/304.135/build/make.log: /var/lib/dkms/nvidia-304/304.135/build/nv-linux.h:1941:9: error: too many arguments to function ‘get_user_pages’ get_user_pages(current, current->mm, start, nr_pages, write, force, pages, vmas) ^ /var/lib/dkms/nvidia-304/304.135/build/nv-mlock.c:52:11: note: in expansion of macro ‘NV_GET_USER_PAGES’ ret = NV_GET_USER_PAGES((unsigned long)address, ^ In file included from /var/lib/dkms/nvidia-304/304.135/build/nv-linux.h:82:0, from /var/lib/dkms/nvidia-304/304.135/build/nv-mlock.c:15: include/linux/mm.h:1222:6: note: declared here long get_user_pages(struct task_struct *tsk, struct mm_struct *mm, ^ [Test case] Install nvidia dkms packages (nvidia-graphics-drivers-304, nvidia-graphics-drivers-340, nvidia-graphics-drivers-384) with Ubuntu linux 4.4 later or equal than 4.4.0-143. To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia/+bug/1818101/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1818167] [NEW] Canon Pixma TS6220 will not print with drvr Canon TS6000 series - CUPS+Gutenprint v5.2.13-2
Public bug reported: Ubuntu 18.04.2 LTS CUPS Installed: 2.2.7-1ubuntu2.3 The printer can print using drvr Canon TS6200 series Ver.5.70(en). But with the Gutenprint driver, printing files or test pages causes a response on the control panel of the printer, but no action mechanically. When the control panel returns to its normal idle state, the "job" is reported as completed. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cups 2.2.7-1ubuntu2.3 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Feb 28 20:47:42 2019 InstallationDate: Installed on 2018-08-04 (209 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lpstat: device for Canon_Gutenprint_Driver: usb://Canon/TS6200%20series?serial=30644B=1 device for Canon_Pixma_TS6220: usb://Canon/TS6200%20series?serial=30644B=1 MachineType: Acer Aspire XC-603 Papersize: letter PpdFiles: Canon_Pixma_TS6220: Canon TS6200 series Ver.5.70 Canon_Gutenprint_Driver: Canon TS6000 series - CUPS+Gutenprint v5.2.13 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=UUID=5ed3623f-f174-4ac2-b301-9dd35c726d45 ro quiet splash vt.handoff=1 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/15/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P11-B4 dmi.board.name: Aspire XC-603 dmi.board.vendor: Acer dmi.chassis.type: 3 dmi.chassis.vendor: Acer dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP11-B4:bd09/15/2015:svnAcer:pnAspireXC-603:pvr:rvnAcer:rnAspireXC-603:rvr:cvnAcer:ct3:cvr: dmi.product.family: Acer Desktop dmi.product.name: Aspire XC-603 dmi.sys.vendor: Acer ** Affects: cups (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 cups in Ubuntu. https://bugs.launchpad.net/bugs/1818167 Title: Canon Pixma TS6220 will not print with drvr Canon TS6000 series - CUPS+Gutenprint v5.2.13-2 Status in cups package in Ubuntu: New Bug description: Ubuntu 18.04.2 LTS CUPS Installed: 2.2.7-1ubuntu2.3 The printer can print using drvr Canon TS6200 series Ver.5.70(en). But with the Gutenprint driver, printing files or test pages causes a response on the control panel of the printer, but no action mechanically. When the control panel returns to its normal idle state, the "job" is reported as completed. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cups 2.2.7-1ubuntu2.3 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Feb 28 20:47:42 2019 InstallationDate: Installed on 2018-08-04 (209 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lpstat: device for Canon_Gutenprint_Driver: usb://Canon/TS6200%20series?serial=30644B=1 device for Canon_Pixma_TS6220: usb://Canon/TS6200%20series?serial=30644B=1 MachineType: Acer Aspire XC-603 Papersize: letter PpdFiles: Canon_Pixma_TS6220: Canon TS6200 series Ver.5.70 Canon_Gutenprint_Driver: Canon TS6000 series - CUPS+Gutenprint v5.2.13 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=UUID=5ed3623f-f174-4ac2-b301-9dd35c726d45 ro quiet splash vt.handoff=1 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/15/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P11-B4 dmi.board.name: Aspire XC-603 dmi.board.vendor: Acer dmi.chassis.type: 3 dmi.chassis.vendor: Acer dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP11-B4:bd09/15/2015:svnAcer:pnAspireXC-603:pvr:rvnAcer:rnAspireXC-603:rvr:cvnAcer:ct3:cvr: dmi.product.family: Acer Desktop dmi.product.name: Aspire XC-603 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1818167/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1818100] Re: sistema roto
Can you please provide a screenshot or photo of the problem? ** 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/1818100 Title: sistema roto Status in Ubuntu: Incomplete Bug description: cuando quiero actualizar, me dice que el sistema esta roto. cada vez que abro office, primero tiene que restaurar. esto es nuevo, hasta hace 2 dias no hacia nada de esto. gracias ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Thu Feb 28 12:53:00 2019 DistUpgraded: 2018-10-26 19:46:47,556 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Falló al ejecutar el proceso hijo «./xorg_fix_proprietary.py» (No existe el archivo o el directorio) (8)) DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DistroCodename: cosmic DistroVariant: ubuntu DkmsStatus: ath9k-msi, 1.1: added radeon-si, 1a, 4.4.0-38-generic, x86_64: built GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 620 [1028:0789] InstallationDate: Installed on 2017-07-14 (594 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. Inspiron 14-3467 ProcEnviron: PATH=(custom, no user) LANG=es_ES.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic root=UUID=4da0aff2-5e0c-4124-950f-922794c92879 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to cosmic on 2018-10-26 (124 days ago) dmi.bios.date: 04/07/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.07.00 dmi.board.name: 0PCXP1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.07.00:bd04/07/2017:svnDellInc.:pnInspiron14-3467:pvr:rvnDellInc.:rn0PCXP1:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 14-3467 dmi.product.sku: 0789 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+18.10.20180930-0ubuntu1 version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 xserver.bootTime: Sun Mar 25 21:08:16 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1319 vendor LGD xserver.version: 2:1.18.4-0ubuntu0.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1818100/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1773959] Re: High CPU usage by gnome-shell when only running gnome-terminal
Pedro, please answer comment #18. I would like to know if 18.10 or 19.04 has changed the situation for you. --- Nicolas, this bug is not about showing seconds in the clock. Please comment in bug 1814125 instead for that issue and not here. Or log a new bug. --- Mark, this bug is about the CPU usage of the gnome-shell process only, when displaying a terminal and nothing else. If you experience any other problem then please open a new bug. --- Roland, there is insufficient information in this bug at the moment and some irrelevant comments. So no, nobody is working on it because we're not sure any bug exists. Also be careful to remember that this bug is about the CPU usage of the gnome-shell process only when displaying a terminal and nothing else. If you experience any other problem then please open a new 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/1773959 Title: High CPU usage by gnome-shell when only running gnome-terminal Status in gnome-shell package in Ubuntu: Incomplete Bug description: Even when doing nothing but displaying a terminal screen with top running gnome-shell uses 10% of a CPU. That seems excessive. I disabled all extensions to try and make the test fair. Enabling the system monitor extension increases the load to 13-14%. It seems that the gnome-shell screen painting is highly CPU consuming even if screen updates are infrequent (1 a second for all these cases). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue May 29 11:38:05 2018 DisplayManager: gdm3 InstallationDate: Installed on 2016-10-27 (578 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: gnome-shell UpgradeStatus: Upgraded to bionic on 2018-05-19 (9 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1773959/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1795421] Re: [cosmic] sidebar requires scrolling
Fixed for scale 1.0 maybe. I don't think it is fixed for 2.0. -- 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/1795421 Title: [cosmic] sidebar requires scrolling Status in gnome-control-center package in Ubuntu: Fix Released Status in yaru-theme package in Ubuntu: New Bug description: In Ubuntu 18.10, the sidebar in GNOME Settings doesn't show the final item Details without scrolling. This issue affects the Yaru and Adwaita themes but Ambiance is not affected (because of slightly different element sizing there). Therefore, this issue is basically new to 18.10 for default Ubuntu users. This has been an upstream bug since the GNOME Settings redesign (introduction of sidebar) but we might want to handle this for Ubuntu 18.10 ourselves. https://gitlab.gnome.org/GNOME/gnome-control-center/issues/83 Because gnome-control-center 3.30 now hides panels like Wi-Fi if the computer does not have that hardware, this bug may not be reproducible on those computers. If we made the window taller, I don't think it would be much of a problem if there was extra space at the bottom of the sidebar for those users. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1795421/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1772898] Re: [SRU] New stable release 1.14.1
No. A bug won't help get the work done, we know about it. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1772898 Title: [SRU] New stable release 1.14.1 Status in gst-libav1.0 package in Ubuntu: Fix Released Status in gst-plugins-bad1.0 package in Ubuntu: Fix Released Status in gst-plugins-base1.0 package in Ubuntu: Fix Released Status in gst-plugins-good1.0 package in Ubuntu: Fix Released Status in gst-plugins-ugly1.0 package in Ubuntu: Fix Released Status in gst-python1.0 package in Ubuntu: Fix Released Status in gst-rtsp-server1.0 package in Ubuntu: Fix Released Status in gstreamer-editing-services1.0 package in Ubuntu: Fix Released Status in gstreamer-vaapi package in Ubuntu: Fix Released Status in gstreamer1.0 package in Ubuntu: Fix Released Status in gst-libav1.0 source package in Bionic: Fix Released Status in gst-plugins-bad1.0 source package in Bionic: Fix Released Status in gst-plugins-base1.0 source package in Bionic: Fix Released Status in gst-plugins-good1.0 source package in Bionic: Fix Released Status in gst-plugins-ugly1.0 source package in Bionic: Fix Released Status in gst-python1.0 source package in Bionic: Fix Released Status in gst-rtsp-server1.0 source package in Bionic: Fix Released Status in gstreamer-editing-services1.0 source package in Bionic: Fix Released Status in gstreamer-vaapi source package in Bionic: Fix Released Status in gstreamer1.0 source package in Bionic: Fix Released Bug description: [ Description ] We should keep up with GStreamer's bugfix releases in the 1.14 series that 18.04 shipped with. [ QA and testing ] Play a range of videos in Totem. Play a range of audio tracks in Rhythmbox. Try to stream audio and/or video. Try to install a missing codec. In all cases, make sure that everything which worked before still works. [ Regression potential ] One of the fixes could be bad. Watch out for it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-libav1.0/+bug/1772898/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1783298] Re: AuthInfoRequired negotiate in cups 2.2.7 in Bionic does not work
Upstream referenced to a commit that could fix the issue https://github.com/apple/cups/commit/ef2f369c -- 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/1783298 Title: AuthInfoRequired negotiate in cups 2.2.7 in Bionic does not work Status in CUPS: Fix Released Status in cups package in Ubuntu: Confirmed Bug description: Hi, We have our printers configured to print to a Windows print server. In Ubuntu 14.04 and 16.04 our setup works fine but in 18.04 our setup seems to be acting more like AuthInfoRequired username,password i.e. it prompts for a password when printing rather than using the available Kerberos credentials. We are using an unaltered cupsd.conf file and are adding printers with the following command: lpadmin -p "printer" -D "Printer" -L "room" -v "smb://printers.cis.strath.ac.uk/printers" -o Media=A4 -o PageSize=A4 -o printer-error-policy=abort-job -o auth-info-required=negotiate -m "CIS/hp-officejet_pro_476_576_series-ps.ppd" the smb backend has been linked to /usr/lib/x86_64-linux- gnu/samba/smbspool_krb5_wrapper (I've added this the apparmor profile as it's blocked by default) and the permissions on this file changed to 700 (owner root) as per manpage instructions. When using lp -d printer /tmp/test.txt I get the following response: Password for myuid on localhost? Typing my password gets the job accepted to the queue but it does spool to the Windows Print Server and in the error_log file I can see D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 - AUTH_INFO_REQUIRED=negotiate D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 - Started with uid=0 D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 - AUTH_UID is not set As I said earlier this all works perfectly on Xenial and Trusty. (A similar AuthInfoRequired negotiate setup also works in cups 2.2.5 on MacOS 10.13) Any ideas how to fix this? Thanks, Ian. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cups 2.2.7-1ubuntu2.1 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Tue Jul 24 10:03:57 2018 InstallationDate: Installed on 2018-06-22 (31 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 0461:4d81 Primax Electronics, Ltd Dell N889 Optical Mouse Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. OptiPlex 790 Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz root=/dev/mapper/pd--ig--vg-root ro quiet splash SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/28/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0HY9JP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA05:bd05/28/2011:svnDellInc.:pnOptiPlex790:pvr01:rvnDellInc.:rn0HY9JP:rvrA00:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 790 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/cups/+bug/1783298/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1752813] Re: Pointer speed is too slow even in the fastest setting
*** This bug is a duplicate of bug 924648 ***
https://bugs.launchpad.net/bugs/924648
I'm not sure if this is a duplicate of it's actually a bug in the
underlying driver and not GNOME.
--
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/1752813
Title:
Pointer speed is too slow even in the fastest setting
Status in gnome-control-center package in Ubuntu:
New
Bug description:
I use the trackpoint on my Lenovo T460s almost exclusively. Even in
the fastest setting on a 2560x1440 screen it is much too slow. I've
had to add the following udev rule to get it to be usable:
ACTION=="add",
SUBSYSTEM=="input",
ATTR{name}=="TPPS/2 IBM TrackPoint",
ATTR{device/sensitivity}="190",
ATTR{device/speed}="220",
ATTR{device/inertia}="6",
ATTR{device/press_to_select}="0"
And even with this and the speed in the control center set to maximum
it is still a bit slow. Trying to push the sensitivity/speed settings
higher will break the trackpoint and even with these settings it seems
that sometimes on resume from sleep the trackpoint fails. After
cycling suspend/resume again it comes back.
There should be a way to set much higher speed settings for the mouse.
Current settings make trackpoints very hard to use which even carries
risk of hand/arm injuries.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: gnome-control-center 1:3.18.2-1ubuntu6
ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
CurrentDesktop: GNOME
Date: Fri Mar 2 08:47:44 2018
InstallationDate: Installed on 2016-10-27 (490 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64
(20160719)
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1752813/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1783298] Re: AuthInfoRequired negotiate in cups 2.2.7 in Bionic does not work
** Changed in: cups Status: Unknown => Fix Released -- 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/1783298 Title: AuthInfoRequired negotiate in cups 2.2.7 in Bionic does not work Status in CUPS: Fix Released Status in cups package in Ubuntu: Confirmed Bug description: Hi, We have our printers configured to print to a Windows print server. In Ubuntu 14.04 and 16.04 our setup works fine but in 18.04 our setup seems to be acting more like AuthInfoRequired username,password i.e. it prompts for a password when printing rather than using the available Kerberos credentials. We are using an unaltered cupsd.conf file and are adding printers with the following command: lpadmin -p "printer" -D "Printer" -L "room" -v "smb://printers.cis.strath.ac.uk/printers" -o Media=A4 -o PageSize=A4 -o printer-error-policy=abort-job -o auth-info-required=negotiate -m "CIS/hp-officejet_pro_476_576_series-ps.ppd" the smb backend has been linked to /usr/lib/x86_64-linux- gnu/samba/smbspool_krb5_wrapper (I've added this the apparmor profile as it's blocked by default) and the permissions on this file changed to 700 (owner root) as per manpage instructions. When using lp -d printer /tmp/test.txt I get the following response: Password for myuid on localhost? Typing my password gets the job accepted to the queue but it does spool to the Windows Print Server and in the error_log file I can see D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 - AUTH_INFO_REQUIRED=negotiate D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 - Started with uid=0 D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 - AUTH_UID is not set As I said earlier this all works perfectly on Xenial and Trusty. (A similar AuthInfoRequired negotiate setup also works in cups 2.2.5 on MacOS 10.13) Any ideas how to fix this? Thanks, Ian. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cups 2.2.7-1ubuntu2.1 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Tue Jul 24 10:03:57 2018 InstallationDate: Installed on 2018-06-22 (31 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 0461:4d81 Primax Electronics, Ltd Dell N889 Optical Mouse Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. OptiPlex 790 Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz root=/dev/mapper/pd--ig--vg-root ro quiet splash SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/28/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0HY9JP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA05:bd05/28/2011:svnDellInc.:pnOptiPlex790:pvr01:rvnDellInc.:rn0HY9JP:rvrA00:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 790 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/cups/+bug/1783298/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1752813] Re: Pointer speed is too slow even in the fastest setting
*** This bug is a duplicate of bug 924648 ***
https://bugs.launchpad.net/bugs/924648
** Changed in: gnome-control-center (Ubuntu)
Importance: Undecided => Low
** This bug has been marked a duplicate of bug 924648
mouse preferences sensitivity: max is too low
--
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/1752813
Title:
Pointer speed is too slow even in the fastest setting
Status in gnome-control-center package in Ubuntu:
New
Bug description:
I use the trackpoint on my Lenovo T460s almost exclusively. Even in
the fastest setting on a 2560x1440 screen it is much too slow. I've
had to add the following udev rule to get it to be usable:
ACTION=="add",
SUBSYSTEM=="input",
ATTR{name}=="TPPS/2 IBM TrackPoint",
ATTR{device/sensitivity}="190",
ATTR{device/speed}="220",
ATTR{device/inertia}="6",
ATTR{device/press_to_select}="0"
And even with this and the speed in the control center set to maximum
it is still a bit slow. Trying to push the sensitivity/speed settings
higher will break the trackpoint and even with these settings it seems
that sometimes on resume from sleep the trackpoint fails. After
cycling suspend/resume again it comes back.
There should be a way to set much higher speed settings for the mouse.
Current settings make trackpoints very hard to use which even carries
risk of hand/arm injuries.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: gnome-control-center 1:3.18.2-1ubuntu6
ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
CurrentDesktop: GNOME
Date: Fri Mar 2 08:47:44 2018
InstallationDate: Installed on 2016-10-27 (490 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64
(20160719)
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1752813/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1506612] Re: pdfimages extracts black rectangles instead of the images
Unsure there is really a bug there, the example from example 1 doesn't seem to include images that fail to be extracted? The empty rectangle ones might just be due to the way the pdf is built. That's still behaving the same way under disco ** Changed in: poppler (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1506612 Title: pdfimages extracts black rectangles instead of the images Status in poppler package in Ubuntu: Confirmed Bug description: When I run pdfimages -f 1 -l 1 -png Z.pdf z-pdfimages, I get 5 images, two of which are black rectangles. If I run pdftocairo -png Z.pdf z-pdftocairo, I get one image that looks correct. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: poppler-utils 0.30.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-31.36-generic 3.19.8-ckt7 Uname: Linux 3.19.0-31-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1.5 Architecture: amd64 CurrentDesktop: Unity Date: Thu Oct 15 12:36:10 2015 InstallationDate: Installed on 2013-05-02 (896 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: poppler UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1506612/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1783298] Re: AuthInfoRequired negotiate in cups 2.2.7 in Bionic does not work
Reported upstream as https://github.com/apple/cups/issues/5536. ** Bug watch added: github.com/apple/cups/issues #5536 https://github.com/apple/cups/issues/5536 ** Also affects: cups via https://github.com/apple/cups/issues/5536 Importance: Unknown Status: Unknown -- 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/1783298 Title: AuthInfoRequired negotiate in cups 2.2.7 in Bionic does not work Status in CUPS: Unknown Status in cups package in Ubuntu: Confirmed Bug description: Hi, We have our printers configured to print to a Windows print server. In Ubuntu 14.04 and 16.04 our setup works fine but in 18.04 our setup seems to be acting more like AuthInfoRequired username,password i.e. it prompts for a password when printing rather than using the available Kerberos credentials. We are using an unaltered cupsd.conf file and are adding printers with the following command: lpadmin -p "printer" -D "Printer" -L "room" -v "smb://printers.cis.strath.ac.uk/printers" -o Media=A4 -o PageSize=A4 -o printer-error-policy=abort-job -o auth-info-required=negotiate -m "CIS/hp-officejet_pro_476_576_series-ps.ppd" the smb backend has been linked to /usr/lib/x86_64-linux- gnu/samba/smbspool_krb5_wrapper (I've added this the apparmor profile as it's blocked by default) and the permissions on this file changed to 700 (owner root) as per manpage instructions. When using lp -d printer /tmp/test.txt I get the following response: Password for myuid on localhost? Typing my password gets the job accepted to the queue but it does spool to the Windows Print Server and in the error_log file I can see D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 - AUTH_INFO_REQUIRED=negotiate D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 - Started with uid=0 D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 - AUTH_UID is not set As I said earlier this all works perfectly on Xenial and Trusty. (A similar AuthInfoRequired negotiate setup also works in cups 2.2.5 on MacOS 10.13) Any ideas how to fix this? Thanks, Ian. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cups 2.2.7-1ubuntu2.1 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Tue Jul 24 10:03:57 2018 InstallationDate: Installed on 2018-06-22 (31 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 0461:4d81 Primax Electronics, Ltd Dell N889 Optical Mouse Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. OptiPlex 790 Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz root=/dev/mapper/pd--ig--vg-root ro quiet splash SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/28/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0HY9JP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA05:bd05/28/2011:svnDellInc.:pnOptiPlex790:pvr01:rvnDellInc.:rn0HY9JP:rvrA00:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 790 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/cups/+bug/1783298/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1773959] Re: High CPU usage by gnome-shell when only running gnome-terminal
I really hope this is fixed by 19.04 -- 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/1773959 Title: High CPU usage by gnome-shell when only running gnome-terminal Status in gnome-shell package in Ubuntu: Incomplete Bug description: Even when doing nothing but displaying a terminal screen with top running gnome-shell uses 10% of a CPU. That seems excessive. I disabled all extensions to try and make the test fair. Enabling the system monitor extension increases the load to 13-14%. It seems that the gnome-shell screen painting is highly CPU consuming even if screen updates are infrequent (1 a second for all these cases). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue May 29 11:38:05 2018 DisplayManager: gdm3 InstallationDate: Installed on 2016-10-27 (578 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: gnome-shell UpgradeStatus: Upgraded to bionic on 2018-05-19 (9 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1773959/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1772898] Re: [SRU] New stable release 1.14.1
Hi, should I open a new bug to update to Gstreamer 1.14.4 in 18.04? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1772898 Title: [SRU] New stable release 1.14.1 Status in gst-libav1.0 package in Ubuntu: Fix Released Status in gst-plugins-bad1.0 package in Ubuntu: Fix Released Status in gst-plugins-base1.0 package in Ubuntu: Fix Released Status in gst-plugins-good1.0 package in Ubuntu: Fix Released Status in gst-plugins-ugly1.0 package in Ubuntu: Fix Released Status in gst-python1.0 package in Ubuntu: Fix Released Status in gst-rtsp-server1.0 package in Ubuntu: Fix Released Status in gstreamer-editing-services1.0 package in Ubuntu: Fix Released Status in gstreamer-vaapi package in Ubuntu: Fix Released Status in gstreamer1.0 package in Ubuntu: Fix Released Status in gst-libav1.0 source package in Bionic: Fix Released Status in gst-plugins-bad1.0 source package in Bionic: Fix Released Status in gst-plugins-base1.0 source package in Bionic: Fix Released Status in gst-plugins-good1.0 source package in Bionic: Fix Released Status in gst-plugins-ugly1.0 source package in Bionic: Fix Released Status in gst-python1.0 source package in Bionic: Fix Released Status in gst-rtsp-server1.0 source package in Bionic: Fix Released Status in gstreamer-editing-services1.0 source package in Bionic: Fix Released Status in gstreamer-vaapi source package in Bionic: Fix Released Status in gstreamer1.0 source package in Bionic: Fix Released Bug description: [ Description ] We should keep up with GStreamer's bugfix releases in the 1.14 series that 18.04 shipped with. [ QA and testing ] Play a range of videos in Totem. Play a range of audio tracks in Rhythmbox. Try to stream audio and/or video. Try to install a missing codec. In all cases, make sure that everything which worked before still works. [ Regression potential ] One of the fixes could be bad. Watch out for it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-libav1.0/+bug/1772898/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1585094] Re: Random stuck keys on Lenovo Yoga 13
I also have just experienced this bug on: Lenovo Ideapad Yoga 13 Ubuntu 18.04.02 Syslog looks the same: Feb 28 21:20:21 masha-Lenovo-IdeaPad-Yoga-13 kernel: [ 214.802472] atkbd serio0: Unknown key released (translated set 2, code 0xbe on isa0060/serio0). Feb 28 21:20:21 masha-Lenovo-IdeaPad-Yoga-13 kernel: [ 214.802479] atkbd serio0: Use 'setkeycodes e03e ' to make it known. Feb 28 21:20:22 masha-Lenovo-IdeaPad-Yoga-13 kernel: [ 215.961924] atkbd serio0: Unknown key pressed (translated set 2, code 0xbe on isa0060/serio0). Feb 28 21:20:22 masha-Lenovo-IdeaPad-Yoga-13 kernel: [ 215.961933] atkbd serio0: Use 'setkeycodes e03e ' to make it known. Feb 28 21:20:22 masha-Lenovo-IdeaPad-Yoga-13 kernel: [ 215.968062] atkbd serio0: Unknown key released (translated set 2, code 0xbe on isa0060/serio0). Feb 28 21:20:22 masha-Lenovo-IdeaPad-Yoga-13 kernel: [ 215.968068] atkbd serio0: Use 'setkeycodes e03e ' to make it known. Feb 28 21:20:23 masha-Lenovo-IdeaPad-Yoga-13 kernel: [ 217.052276] atkbd serio0: Unknown key pressed (translated set 2, code 0xbe on isa0060/serio0). Feb 28 21:20:23 masha-Lenovo-IdeaPad-Yoga-13 kernel: [ 217.052282] atkbd serio0: Use 'setkeycodes e03e ' to make it known. Feb 28 21:20:23 masha-Lenovo-IdeaPad-Yoga-13 kernel: [ 217.057285] atkbd serio0: Unknown key released (translated set 2, code 0xbe on isa0060/serio0). Feb 28 21:20:23 masha-Lenovo-IdeaPad-Yoga-13 kernel: [ 217.057291] atkbd serio0: Use 'setkeycodes e03e ' to make it known. -- 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/1585094 Title: Random stuck keys on Lenovo Yoga 13 Status in xorg package in Ubuntu: Confirmed Bug description: pressing arrow keys leads randomly to the effect of stuck number key and produces output in consoles or text editors like: "22" or "88". Pressing some other key stops the infinite flooding. This may (or not) be related to the following flooding in /var/log/system May 24 10:01:30 yogi kernel: [ 3816.438579] atkbd serio0: Unknown key pressed (translated set 2, code 0xbe on isa0060/serio0). May 24 10:01:30 yogi kernel: [ 3816.438603] atkbd serio0: Use 'setkeycodes e03e ' to make it known. May 24 10:01:30 yogi kernel: [ 3816.443504] atkbd serio0: Unknown key released (translated set 2, code 0xbe on isa0060/serio0). May 24 10:01:30 yogi kernel: [ 3816.443516] atkbd serio0: Use 'setkeycodes e03e ' to make it known. these messages are generated approximately each 200 msec. If the former is not related to stuck key problem, please, ignore. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue May 24 09:45:39 2016 DistUpgraded: 2016-04-24 00:21:19,103 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:3977] InstallationDate: Installed on 2013-11-17 (918 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: LENOVO 2191 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic.efi.signed root=UUID=f6200601-c430-459d-abab-c6d45f1e147a ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2016-04-23 (30 days ago) dmi.bios.date: 02/28/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 66CN55WW dmi.board.asset.tag: No Asset Tag dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: 3193WIN8 STD MLT dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad Yoga 13 dmi.modalias: dmi:bvnLENOVO:bvr66CN55WW:bd02/28/2013:svnLENOVO:pn2191:pvrLenovoIdeaPadYoga13:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadYoga13: dmi.product.name: 2191 dmi.product.version: Lenovo IdeaPad Yoga 13 dmi.sys.vendor: LENOVO 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
[Desktop-packages] [Bug 1818089] Re: Cups can not print with "filter failed" error just after ghostcript update
sorry, rather "dpkg -l | grep freetype" -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ghostscript in Ubuntu. https://bugs.launchpad.net/bugs/1818089 Title: Cups can not print with "filter failed" error just after ghostcript update Status in ghostscript package in Ubuntu: Incomplete Bug description: I was using my Epson 105 printer properly till i decided to do recommended upgrade to recent version of ghostscript after which my pinter stopped working. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ghostscript 9.26~dfsg+0-0ubuntu0.18.04.7 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Feb 28 20:31:23 2019 InstallationDate: Installed on 2018-06-01 (272 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: ghostscript UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1818089/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1730672] Re: Proxy settings not applied system-wide, are not used by Software Update or apt
Using the graphical tool would also prompt you for a password to be able to apply the change to the system so it wouldn't make a difference for you? -- 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/1730672 Title: Proxy settings not applied system-wide, are not used by Software Update or apt Status in gnome-control-center package in Ubuntu: Confirmed Status in update-manager package in Ubuntu: Confirmed Bug description: The Network Proxy settings available under Settings/Network are not applied system wide. Unlike 16.x, there is no "apply system wide" setting. Setting a proxy here: - does not modify /etc/environment - does not set root's http_proxy, https_proxy, ftp_proxy environment variables This means that apt and Software Updates do not receive the proxy settings, and package checks/updates/installs fail. workaround: sudo http_proxy='http://[username]:[password]@[webproxy]:[port]' apt update etc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1730672/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1818089] Re: Cups can not print with "filter failed" error just after ghostcript update
also "dpkg -l | grep fontconfig" -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ghostscript in Ubuntu. https://bugs.launchpad.net/bugs/1818089 Title: Cups can not print with "filter failed" error just after ghostcript update Status in ghostscript package in Ubuntu: Incomplete Bug description: I was using my Epson 105 printer properly till i decided to do recommended upgrade to recent version of ghostscript after which my pinter stopped working. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ghostscript 9.26~dfsg+0-0ubuntu0.18.04.7 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Feb 28 20:31:23 2019 InstallationDate: Installed on 2018-06-01 (272 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: ghostscript UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1818089/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1818089] Re: Cups can not print with "filter failed" error just after ghostcript update
Thank you for your bug report. The error in the local is D [28/Feb/2019:20:02:49 +0530] [Job 9259] gs: symbol lookup error: /usr/lib/x86_64-linux-gnu/libgs.so.9: undefined symbol: FT_Property_Set Could you give the output of $ ldd -r /usr/lib/x86_64-linux-gnu/libgs.so.9 ? ** Changed in: ghostscript (Ubuntu) Importance: Undecided => Low ** Changed in: ghostscript (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ghostscript in Ubuntu. https://bugs.launchpad.net/bugs/1818089 Title: Cups can not print with "filter failed" error just after ghostcript update Status in ghostscript package in Ubuntu: Incomplete Bug description: I was using my Epson 105 printer properly till i decided to do recommended upgrade to recent version of ghostscript after which my pinter stopped working. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ghostscript 9.26~dfsg+0-0ubuntu0.18.04.7 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Feb 28 20:31:23 2019 InstallationDate: Installed on 2018-06-01 (272 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: ghostscript UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1818089/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1818090] Re: Cups can not print with "filter failed" error just after ghostcript update
*** This bug is a duplicate of bug 1818089 *** https://bugs.launchpad.net/bugs/1818089 ** This bug has been marked a duplicate of bug 1818089 Cups can not print with "filter failed" error just after ghostcript update -- 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/1818090 Title: Cups can not print with "filter failed" error just after ghostcript update Status in cups package in Ubuntu: New Bug description: Cups can not print with filer failed message ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cups 2.2.7-1ubuntu2.2 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Feb 28 20:31:53 2019 InstallationDate: Installed on 2018-06-01 (272 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lpstat: device for EPSON_M105_Series: usb://EPSON/M105%20Series?serial=574C51593030393431 MachineType: HPE ML10Gen9 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/EPSON_M105_Series.ppd'] failed with exit code 2: grep: /etc/cups/ppd/EPSON_M105_Series.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic root=/dev/mapper/ubuntu--vg-root ro nosplash SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/27/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.003 dmi.board.asset.tag: (null) dmi.board.name: ML10Gen9 dmi.board.vendor: HPE dmi.board.version: (null) dmi.chassis.asset.tag: (null) dmi.chassis.type: 3 dmi.chassis.vendor: HPE dmi.chassis.version: (null) dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.003:bd07/27/2016:svnHPE:pnML10Gen9:pvr(null):rvnHPE:rnML10Gen9:rvr(null):cvnHPE:ct3:cvr(null): dmi.product.family: (null) dmi.product.name: ML10Gen9 dmi.product.version: (null) dmi.sys.vendor: HPE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1818090/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1767541] Re: Transparent background of calculator in ubuntu 18.04 using communitheme
After some googling around, in the end I ended up doing this: sudo apt install gnome-calculator sudo snap remove gnome-calculator And now both my keyboard calculator shortcut works as well as the calculator is no longer transparent. I have no idea what snap even is. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calculator in Ubuntu. https://bugs.launchpad.net/bugs/1767541 Title: Transparent background of calculator in ubuntu 18.04 using communitheme Status in gnome-calculator package in Ubuntu: Invalid Bug description: It also happen in system monitor ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-calculator (not installed) ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: communitheme:ubuntu:GNOME Date: Sat Apr 28 08:34:55 2018 InstallationDate: Installed on 2018-04-27 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_PH.UTF-8 SHELL=/bin/bash SourcePackage: gnome-calculator UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1767541/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1730672] Re: Proxy settings not applied system-wide, are not used by Software Update or apt
@seb128, here are some details. We don't rely on the GNOME tool. We only have one machine and I manually added it to out Windows AD domain. Applying the changes to the apt.conf and environment variable works but it necessitates to insert a username a password, correct me if I'm wrong, which I find a bit counter intuitive security wise. is there a way to modified it so prompts the users for their password. -- 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/1730672 Title: Proxy settings not applied system-wide, are not used by Software Update or apt Status in gnome-control-center package in Ubuntu: Confirmed Status in update-manager package in Ubuntu: Confirmed Bug description: The Network Proxy settings available under Settings/Network are not applied system wide. Unlike 16.x, there is no "apply system wide" setting. Setting a proxy here: - does not modify /etc/environment - does not set root's http_proxy, https_proxy, ftp_proxy environment variables This means that apt and Software Updates do not receive the proxy settings, and package checks/updates/installs fail. workaround: sudo http_proxy='http://[username]:[password]@[webproxy]:[port]' apt update etc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1730672/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1767541] Re: Transparent background of calculator in ubuntu 18.04 using communitheme
It's hitting me right now. Which kind of info should I be providing? I'm on Ubuntu 18.04 desktop, latest `apt dist upgrade`... ** Attachment added: "screenshot of transparent calc" https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1767541/+attachment/5242387/+files/calc_back.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calculator in Ubuntu. https://bugs.launchpad.net/bugs/1767541 Title: Transparent background of calculator in ubuntu 18.04 using communitheme Status in gnome-calculator package in Ubuntu: Invalid Bug description: It also happen in system monitor ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-calculator (not installed) ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: communitheme:ubuntu:GNOME Date: Sat Apr 28 08:34:55 2018 InstallationDate: Installed on 2018-04-27 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_PH.UTF-8 SHELL=/bin/bash SourcePackage: gnome-calculator UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1767541/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1813701] Re: [amdgpu] Flickering graphics corruption (but none observed in kernels 4.18.10-4.18.12)
I tried the v5.0-rc7 and rc8 kernels. the problem is not solved ** Tags added: kernel-bug-exists-upstream -- 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/1813701 Title: [amdgpu] Flickering graphics corruption (but none observed in kernels 4.18.10-4.18.12) Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-video-amdgpu package in Ubuntu: Confirmed Bug description: The screen always flickers at a frequency of 75 GHz on the AMD RX 580 gpu. At 60 and 50 GHz, if you switch to any other than 75, the flickering will disappear until the display turns off. After switching on, flicker returns. At the core of 4.18.0-10, just like on the AMD Radeon HD7970 gpu, the problem is not visible. More in the video https://www.youtube.com/watch?v=d_LXHqWKTbk ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 BootLog: Error: [Errno 13] Отказано в доступе: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jan 29 13:13:19 2019 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X] [1002:67df] (rev e7) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Ellesmere [Radeon RX 470/480/570/570X/580/580X] [1043:0519] InstallationDate: Installed on 2019-01-22 (6 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: MSI MS-7693 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic root=UUID=ad22bc6d-c4e8-4393-a30b-6c247159b9dd ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/08/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V10.6 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 970A-G43 (MS-7693) dmi.board.vendor: MSI dmi.board.version: 3.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 3.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV10.6:bd01/08/2016:svnMSI:pnMS-7693:pvr3.0:rvnMSI:rn970A-G43(MS-7693):rvr3.0:cvnMSI:ct3:cvr3.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7693 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 3.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97+git1901221830.b7a7a9~oibaf~c version.libgl1-mesa-dri: libgl1-mesa-dri 19.0~git1901280730.d1d2bb~oibaf~c version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813701/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1818101] Re: nvidia dkms modules fail to build with linux 4.4.0-143.169
** Also affects: nvidia-graphics-drivers-304 (Ubuntu) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-340 (Ubuntu) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-304 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-340 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-384 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-304 (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-340 (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-384 (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-304 (Ubuntu Trusty) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: nvidia-graphics-drivers-304 (Ubuntu Xenial) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: nvidia-graphics-drivers-340 (Ubuntu Trusty) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: nvidia-graphics-drivers-340 (Ubuntu Xenial) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: nvidia-graphics-drivers-384 (Ubuntu Trusty) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: nvidia-graphics-drivers-384 (Ubuntu Xenial) Assignee: (unassigned) => Alberto Milone (albertomilone) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1818101 Title: nvidia dkms modules fail to build with linux 4.4.0-143.169 Status in Nvidia: New Status in nvidia-graphics-drivers-304 package in Ubuntu: New Status in nvidia-graphics-drivers-340 package in Ubuntu: New Status in nvidia-graphics-drivers-384 package in Ubuntu: New Status in nvidia-graphics-drivers-304 source package in Trusty: New Status in nvidia-graphics-drivers-340 source package in Trusty: New Status in nvidia-graphics-drivers-384 source package in Trusty: New Status in nvidia-graphics-drivers-304 source package in Xenial: New Status in nvidia-graphics-drivers-340 source package in Xenial: New Status in nvidia-graphics-drivers-384 source package in Xenial: New Bug description: [Impact] nvidia dkms modules (304, 340, 384) fail to build after Ubuntu kernel 4.4 backported the following fix from upstream stable, which is included on xenial kernel 4.4.0-143.169 that's currently in -proposed. mm: replace get_user_pages() write/force parameters with gup_flags https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/xenial/commit/?h=master-next=9c72ad08f1510332e9314046e6a2adba5064f39a Excerpt from ./nvidia-304/304.135/build/make.log: /var/lib/dkms/nvidia-304/304.135/build/nv-linux.h:1941:9: error: too many arguments to function ‘get_user_pages’ get_user_pages(current, current->mm, start, nr_pages, write, force, pages, vmas) ^ /var/lib/dkms/nvidia-304/304.135/build/nv-mlock.c:52:11: note: in expansion of macro ‘NV_GET_USER_PAGES’ ret = NV_GET_USER_PAGES((unsigned long)address, ^ In file included from /var/lib/dkms/nvidia-304/304.135/build/nv-linux.h:82:0, from /var/lib/dkms/nvidia-304/304.135/build/nv-mlock.c:15: include/linux/mm.h:1222:6: note: declared here long get_user_pages(struct task_struct *tsk, struct mm_struct *mm, ^ [Test case] Install nvidia dkms packages (nvidia-graphics-drivers-304, nvidia-graphics-drivers-340, nvidia-graphics-drivers-384) with Ubuntu linux 4.4 later or equal than 4.4.0-143. To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia/+bug/1818101/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1769991] Re: [16.04] Unable to import OpenVPN configuration into Network Manager
I"m attaching an example OVPN file with more private details stripped out of it. This is a typical OpenVPN export. Network Manager is unable to parse it for the error specified previously. This is failing to import in both 16.04 and 18.04 and needs addressed. ** Attachment added: "test.opvn" https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1769991/+attachment/5242351/+files/test.opvn -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-openvpn in Ubuntu. https://bugs.launchpad.net/bugs/1769991 Title: [16.04] Unable to import OpenVPN configuration into Network Manager Status in network-manager-openvpn package in Ubuntu: Fix Released Status in network-manager-openvpn source package in Xenial: New Bug description: In 16.04, it is currently not possible to import OpenVPN configurations. Specifically, imports fail with the error of: The file 'filename.ovpn' could not be read or does not contain recognized VPN connection information. Error: Key file contains line 'client' which is not a key-value pair, group, or comment. -- An example configuration that fails to import is as follows (with some critical components excluded, like a proper remote address, or a proper x509 name); this is a config that otherwise works with a Sophos XG Firewall-based SSL VPN system client dev tun persist-tun persist-key proto tcp verify-x509-name "" route remote_host 255.255.255.255 net_gateway resolv-retry infinite remote 1.2.3.4 8443 tcp ca ca.crt cert client.crt key client.key auth-user-pass cipher AES-256-CBC auth SHA512 comp-lzo no route-delay 4 verb 3 reneg-sec 0 -- This same exact configuration works with a direct call of `openvpn ./filename.ovpn`. Why Network Manager is unable to parse or import the OpenVPN configuration is beyond my ability to comprehend. Note that the same configuration made by hand in the new VPN window works fine, but the import function fails. (Which is a pretty severe bug) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager-openvpn 1.1.93-1ubuntu1.1 ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-39-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 CurrentDesktop: Unity Date: Tue May 8 14:59:54 2018 InstallationDate: Installed on 2016-12-20 (503 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: network-manager-openvpn UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1769991/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1818100] [NEW] sistema roto
Public bug reported: cuando quiero actualizar, me dice que el sistema esta roto. cada vez que abro office, primero tiene que restaurar. esto es nuevo, hasta hace 2 dias no hacia nada de esto. gracias ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Thu Feb 28 12:53:00 2019 DistUpgraded: 2018-10-26 19:46:47,556 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Falló al ejecutar el proceso hijo «./xorg_fix_proprietary.py» (No existe el archivo o el directorio) (8)) DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DistroCodename: cosmic DistroVariant: ubuntu DkmsStatus: ath9k-msi, 1.1: added radeon-si, 1a, 4.4.0-38-generic, x86_64: built GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 620 [1028:0789] InstallationDate: Installed on 2017-07-14 (594 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. Inspiron 14-3467 ProcEnviron: PATH=(custom, no user) LANG=es_ES.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic root=UUID=4da0aff2-5e0c-4124-950f-922794c92879 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to cosmic on 2018-10-26 (124 days ago) dmi.bios.date: 04/07/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.07.00 dmi.board.name: 0PCXP1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.07.00:bd04/07/2017:svnDellInc.:pnInspiron14-3467:pvr:rvnDellInc.:rn0PCXP1:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 14-3467 dmi.product.sku: 0789 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+18.10.20180930-0ubuntu1 version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 xserver.bootTime: Sun Mar 25 21:08:16 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1319 vendor LGD xserver.version: 2:1.18.4-0ubuntu0.7 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic 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/1818100 Title: sistema roto Status in xorg package in Ubuntu: New Bug description: cuando quiero actualizar, me dice que el sistema esta roto. cada vez que abro office, primero tiene que restaurar. esto es nuevo, hasta hace 2 dias no hacia nada de esto. gracias ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Thu Feb 28 12:53:00 2019 DistUpgraded: 2018-10-26 19:46:47,556 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Falló al ejecutar el proceso hijo «./xorg_fix_proprietary.py» (No existe el archivo o el directorio) (8)) DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DistroCodename: cosmic DistroVariant: ubuntu DkmsStatus: ath9k-msi, 1.1: added radeon-si, 1a, 4.4.0-38-generic, x86_64: built GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 620 [1028:0789] InstallationDate: Installed on 2017-07-14 (594 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. Inspiron 14-3467
[Desktop-packages] [Bug 1818053] Re: /usr/bin/seahorse:11:g_atomic_ref_count_dec:g_variant_unref:___lambda22_:____lambda22__gasync_ready_callback:g_simple_async_result_complete
Upstreamed https://gitlab.gnome.org/GNOME/libsecret/issues/22 ** Changed in: seahorse (Ubuntu) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to seahorse in Ubuntu. https://bugs.launchpad.net/bugs/1818053 Title: /usr/bin/seahorse:11:g_atomic_ref_count_dec:g_variant_unref:___lambda22_:lambda22__gasync_ready_callback:g_simple_async_result_complete Status in seahorse package in Ubuntu: Triaged Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding seahorse. This problem was most recently seen with package version 3.31.91-1, the problem page at https://errors.ubuntu.com/problem/27dfb9fa56c174fbd9ea1d62a3efc5816a0b5fb9 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/1818053/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1818089] Re: Cups can not print with "filter failed" error just after ghostcript update
CUPS error log suggest fault with gs ** Attachment added: "CupsErrorLog.txt" https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1818089/+attachment/5242313/+files/CupsErrorLog.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ghostscript in Ubuntu. https://bugs.launchpad.net/bugs/1818089 Title: Cups can not print with "filter failed" error just after ghostcript update Status in ghostscript package in Ubuntu: New Bug description: I was using my Epson 105 printer properly till i decided to do recommended upgrade to recent version of ghostscript after which my pinter stopped working. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ghostscript 9.26~dfsg+0-0ubuntu0.18.04.7 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Feb 28 20:31:23 2019 InstallationDate: Installed on 2018-06-01 (272 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: ghostscript UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1818089/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1818089] [NEW] Cups can not print with "filter failed" error just after ghostcript update
Public bug reported: I was using my Epson 105 printer properly till i decided to do recommended upgrade to recent version of ghostscript after which my pinter stopped working. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ghostscript 9.26~dfsg+0-0ubuntu0.18.04.7 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Feb 28 20:31:23 2019 InstallationDate: Installed on 2018-06-01 (272 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: ghostscript UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ghostscript (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 ghostscript in Ubuntu. https://bugs.launchpad.net/bugs/1818089 Title: Cups can not print with "filter failed" error just after ghostcript update Status in ghostscript package in Ubuntu: New Bug description: I was using my Epson 105 printer properly till i decided to do recommended upgrade to recent version of ghostscript after which my pinter stopped working. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ghostscript 9.26~dfsg+0-0ubuntu0.18.04.7 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Feb 28 20:31:23 2019 InstallationDate: Installed on 2018-06-01 (272 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: ghostscript UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1818089/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1818090] [NEW] Cups can not print with "filter failed" error just after ghostcript update
Public bug reported: Cups can not print with filer failed message ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cups 2.2.7-1ubuntu2.2 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Feb 28 20:31:53 2019 InstallationDate: Installed on 2018-06-01 (272 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lpstat: device for EPSON_M105_Series: usb://EPSON/M105%20Series?serial=574C51593030393431 MachineType: HPE ML10Gen9 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/EPSON_M105_Series.ppd'] failed with exit code 2: grep: /etc/cups/ppd/EPSON_M105_Series.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic root=/dev/mapper/ubuntu--vg-root ro nosplash SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/27/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.003 dmi.board.asset.tag: (null) dmi.board.name: ML10Gen9 dmi.board.vendor: HPE dmi.board.version: (null) dmi.chassis.asset.tag: (null) dmi.chassis.type: 3 dmi.chassis.vendor: HPE dmi.chassis.version: (null) dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.003:bd07/27/2016:svnHPE:pnML10Gen9:pvr(null):rvnHPE:rnML10Gen9:rvr(null):cvnHPE:ct3:cvr(null): dmi.product.family: (null) dmi.product.name: ML10Gen9 dmi.product.version: (null) dmi.sys.vendor: HPE ** 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/1818090 Title: Cups can not print with "filter failed" error just after ghostcript update Status in cups package in Ubuntu: New Bug description: Cups can not print with filer failed message ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cups 2.2.7-1ubuntu2.2 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Feb 28 20:31:53 2019 InstallationDate: Installed on 2018-06-01 (272 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lpstat: device for EPSON_M105_Series: usb://EPSON/M105%20Series?serial=574C51593030393431 MachineType: HPE ML10Gen9 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/EPSON_M105_Series.ppd'] failed with exit code 2: grep: /etc/cups/ppd/EPSON_M105_Series.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic root=/dev/mapper/ubuntu--vg-root ro nosplash SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/27/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.003 dmi.board.asset.tag: (null) dmi.board.name: ML10Gen9 dmi.board.vendor: HPE dmi.board.version: (null) dmi.chassis.asset.tag: (null) dmi.chassis.type: 3 dmi.chassis.vendor: HPE dmi.chassis.version: (null) dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.003:bd07/27/2016:svnHPE:pnML10Gen9:pvr(null):rvnHPE:rnML10Gen9:rvr(null):cvnHPE:ct3:cvr(null): dmi.product.family: (null) dmi.product.name: ML10Gen9 dmi.product.version: (null) dmi.sys.vendor: HPE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1818090/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1815889] Re: qemu-system-x86_64 crashed with signal 31 in __pthread_setaffinity_new()
Launchpad has imported 9 comments from the remote bug at
https://bugs.freedesktop.org/show_bug.cgi?id=109695.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.
On 2019-02-20T20:12:32+00:00 Ahzo wrote:
Since upgrading Mesa from 18.2 to 18.3, launching a QEMU virtual machine
with Spice OpenGL enabled (for virgl), causes QEMU to crash with SIGSYS
inside the radeonsi driver. The reason for this is that the QEMU sandbox
option 'resourcecontrol=deny' disables the sched_setaffinity syscall
called in pthread_setaffinity_np, which is now used by the radeonsi
driver.
A simple way to reproduce this problem is:
$ gdb --batch --ex run --ex bt --args qemu-system-x86_64 -spice gl=on -sandbox
on,resourcecontrol=deny
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x745aa700 (LWP 23432)]
[New Thread 0x708e5700 (LWP 23433)]
[New Thread 0x7fffe3fff700 (LWP 23434)]
[New Thread 0x7fffe37fe700 (LWP 23435)]
Thread 4 "qemu-system-x86" received signal SIGSYS, Bad system call.
[Switching to Thread 0x7fffe3fff700 (LWP 23434)]
0x768cc9cf in __pthread_setaffinity_new (th=,
cpusetsize=cpusetsize@entry=128, cpuset=cpuset@entry=0x7fffe3ffe680) at
../sysdeps/unix/sysv/linux/pthread_setaffinity.c:34
34 ../sysdeps/unix/sysv/linux/pthread_setaffinity.c: No such file or
directory.
#0 0x768cc9cf in __pthread_setaffinity_new (th=,
cpusetsize=cpusetsize@entry=128, cpuset=cpuset@entry=0x7fffe3ffe680) at
../sysdeps/unix/sysv/linux/pthread_setaffinity.c:34
#1 0x712ba2b3 in util_queue_thread_func
(input=input@entry=0x5640b1f0) at ../src/util/u_queue.c:252
#2 0x712b9c17 in impl_thrd_routine (p=) at
../src/../include/c11/threads_posix.h:87
#3 0x768c1fa3 in start_thread (arg=) at
pthread_create.c:486
#4 0x767f280f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95
The problematic code at src/util/u_queue.c:252 was added in the following
commit:
commit d877451b48a59ab0f9a4210fc736f51da5851c9a
Author: Marek Olšák
Date: Mon Oct 1 15:51:06 2018 -0400
util/u_queue: add UTIL_QUEUE_INIT_SET_FULL_THREAD_AFFINITY
Initial version discussed with Rob Clark under a different patch name.
This approach leaves his driver unaffected.
Since setting the thread affinity seems non-essential here, the failing syscall
should be handled gracefully, for example by setting a signal handler to ignore
the SIGSYS signal.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1815889/comments/12
On 2019-02-20T21:30:42+00:00 Marek Olšák wrote:
Mesa needs a way to query that it can't set thread affinity.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1815889/comments/13
On 2019-02-21T17:15:56+00:00 Ahzo wrote:
To check for the availability of the syscall, one can try it in a child
process and see if the child is terminated by a signal, e.g. like this:
#include
#include
#include
#include
#include
static bool
can_set_affinity()
{
pid_t pid = fork();
int status = 0;
if (!pid) {
/* Disable coredumps, because a SIGSYS crash is expected. */
struct rlimit limit = { 0 };
limit.rlim_cur = 1;
limit.rlim_max = 1;
setrlimit(RLIMIT_CORE, );
/* Test the syscall in the child process. */
syscall(SYS_sched_setaffinity, 0, 0, 0);
_exit(0);
} else if (pid < 0) {
return false;
}
if (waitpid(pid, , 0) < 0) {
return false;
}
if (WIFSIGNALED(status)) {
/* The child process was terminated by a signal,
* thus the syscall cannot be used.
*/
return false;
}
return true;
}
Reply at:
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1815889/comments/14
On 2019-02-27T14:42:21+00:00 Dan-freedesktop wrote:
(In reply to Ahzo from comment #2)
> To check for the availability of the syscall, one can try it in a child
> process and see if the child is terminated by a signal, e.g. like this:
Afraid not, QEMU's seccomp filter blocks use of fork() too :-)
Reply at:
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1815889/comments/27
On 2019-02-27T14:45:24+00:00 Dan-freedesktop wrote:
(In reply to Ahzo from comment #0)
> The problematic code at src/util/u_queue.c:252 was added in the following
> commit:
> commit d877451b48a59ab0f9a4210fc736f51da5851c9a
> Author: Marek Olšák
> Date: Mon Oct 1 15:51:06 2018 -0400
>
>
Re: [Desktop-packages] [Bug 1817924] Re: apps launched from gnome shell do not get input focus
it's not generally slow enough for the latter to be an issue. :-) Even if I just go nice and slow. Click... window opens... it doesn't have focus... It continues to not have focus until I do something that would give it focus in the normal fashion, like clicking on it, clicking on its dock icon now it's running, alt-tabbing to it... Is this not happening for you in launching gnome-terminal? It's same for me whether from dock, from app grid, from app grid's search field. *Sometimes* it's been slow enough that I think I've seen the window have focus for a tiny moment (the close-window icon in the titlebar is orange for a moment) then it gets taken away. Usually it's too fast to see that happen. BTW I've also tried it with *all* extensions removed, including ubuntu-dock and appindicators and desktop-icons, by removing their packages. No difference. -- 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/1817924 Title: apps launched from gnome shell do not get input focus Status in gnome-shell package in Ubuntu: Incomplete Bug description: Observed on upgrading to disco-proposed today... When launching an app from the dock or from the applications grid (so i believe it's a gnome-shell thing rather than a dock thing), the app opens, but does not get the input focus. You have to either click in the window, or clicking again on the icon of the running app in the dock works, to give it focus. An extra step my muscle memory isn't prepared for! It seems like the sort of thing that might be an option rather than a bug, but if so, changing this behaviour back to its previous default is not at all obvious (I haven't found a way). So guessing it is a bug. NB: After launching an app this way, *no* window has focus. It is lost by the app that had it before, but not given to the newly started app. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.31.90-1ubuntu1 ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20 Uname: Linux 4.19.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Feb 27 15:53:07 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-09-11 (169 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) SourcePackage: gnome-shell UpgradeStatus: Upgraded to disco on 2019-01-13 (44 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1817924/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1783298] Re: AuthInfoRequired negotiate in cups 2.2.7 in Bionic does not work
Ideally that would be reported upstream, Till maybe you can help with that? ** Changed in: cups (Ubuntu) Assignee: (unassigned) => Till Kamppeter (till-kamppeter) -- 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/1783298 Title: AuthInfoRequired negotiate in cups 2.2.7 in Bionic does not work Status in cups package in Ubuntu: Confirmed Bug description: Hi, We have our printers configured to print to a Windows print server. In Ubuntu 14.04 and 16.04 our setup works fine but in 18.04 our setup seems to be acting more like AuthInfoRequired username,password i.e. it prompts for a password when printing rather than using the available Kerberos credentials. We are using an unaltered cupsd.conf file and are adding printers with the following command: lpadmin -p "printer" -D "Printer" -L "room" -v "smb://printers.cis.strath.ac.uk/printers" -o Media=A4 -o PageSize=A4 -o printer-error-policy=abort-job -o auth-info-required=negotiate -m "CIS/hp-officejet_pro_476_576_series-ps.ppd" the smb backend has been linked to /usr/lib/x86_64-linux- gnu/samba/smbspool_krb5_wrapper (I've added this the apparmor profile as it's blocked by default) and the permissions on this file changed to 700 (owner root) as per manpage instructions. When using lp -d printer /tmp/test.txt I get the following response: Password for myuid on localhost? Typing my password gets the job accepted to the queue but it does spool to the Windows Print Server and in the error_log file I can see D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 - AUTH_INFO_REQUIRED=negotiate D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 - Started with uid=0 D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 - AUTH_UID is not set As I said earlier this all works perfectly on Xenial and Trusty. (A similar AuthInfoRequired negotiate setup also works in cups 2.2.5 on MacOS 10.13) Any ideas how to fix this? Thanks, Ian. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cups 2.2.7-1ubuntu2.1 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Tue Jul 24 10:03:57 2018 InstallationDate: Installed on 2018-06-22 (31 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 0461:4d81 Primax Electronics, Ltd Dell N889 Optical Mouse Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. OptiPlex 790 Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz root=/dev/mapper/pd--ig--vg-root ro quiet splash SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/28/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0HY9JP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA05:bd05/28/2011:svnDellInc.:pnOptiPlex790:pvr01:rvnDellInc.:rn0HY9JP:rvrA00:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 790 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1783298/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1818063] Re: gedit crashed with SIGSEGV in update_actions_sensitivity()
Thank you for your bug report. It looks like you had gedit open with some documents though? Do you remember which ones/where they are located? (the backtrace has a call 'readonly_changed') Did you change any of the open files from outside gedit? (cp, package update, ...)? ** Changed in: gedit (Ubuntu) Status: New => Incomplete -- 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/1818063 Title: gedit crashed with SIGSEGV in update_actions_sensitivity() Status in gedit package in Ubuntu: Incomplete Bug description: I was NOT using gedit. corrado@corrado-p7-dd-0225:~$ inxi -Fx System:Host: corrado-p7-dd-0225 Kernel: 4.19.0-13-generic x86_64 bits: 64 compiler: gcc v: 8.2.1 Desktop: Gnome 3.30.2 Distro: Ubuntu 19.04 (Disco Dingo) Machine: Type: Desktop Mobo: ASRock model: H110M-G/M.2 serial: UEFI: American Megatrends v: P1.10 date: 05/11/2017 CPU: Topology: Dual Core model: Intel Core i3-7100 bits: 64 type: MT MCP arch: Kaby Lake rev: 9 L2 cache: 3072 KiB flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 31296 Speed: 800 MHz min/max: 800/3900 MHz Core speeds (MHz): 1: 800 2: 800 3: 801 4: 800 Graphics: Device-1: Intel HD Graphics 630 vendor: ASRock driver: i915 v: kernel bus ID: 00:02.0 Display: x11 server: X.Org 1.20.3 driver: i915 resolution: 1920x1080~60Hz OpenGL: renderer: Mesa DRI Intel HD Graphics 630 (Kaby Lake GT2) v: 4.5 Mesa 18.3.4 direct render: Yes Audio: Device-1: Intel 100 Series/C230 Series Family HD Audio vendor: ASRock driver: snd_hda_intel v: kernel bus ID: 00:1f.3 Device-2: Logitech QuickCam Pro 9000 type: USB driver: snd-usb-audio,uvcvideo bus ID: 1-10:4 Sound Server: ALSA v: k4.19.0-13-generic Network: Device-1: Intel Ethernet I219-V vendor: ASRock driver: e1000e v: 3.2.6-k port: f040 bus ID: 00:1f.6 IF: enp0s31f6 state: up speed: 100 Mbps duplex: full mac: 70:85:c2:44:7b:86 Drives:Local Storage: total: 931.51 GiB used: 8.05 GiB (0.9%) ID-1: /dev/sda vendor: Toshiba model: DT01ACA100 size: 931.51 GiB Partition: ID-1: / size: 31.25 GiB used: 8.04 GiB (25.7%) fs: ext4 dev: /dev/sda7 ID-2: swap-1 size: 8.00 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda2 Sensors: System Temperatures: cpu: 40.5 C mobo: N/A Fan Speeds (RPM): N/A Info: Processes: 205 Uptime: 1h 14m Memory: 7.50 GiB used: 1.31 GiB (17.5%) Init: systemd runlevel: 5 Compilers: gcc: 8.2.0 Shell: bash v: 5.0.2 inxi: 3.0.32 corrado@corrado-p7-dd-0225:~$ ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: gedit 3.31.90-1build1 ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20 Uname: Linux 4.19.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu21 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Thu Feb 28 13:43:55 2019 ExecutablePath: /usr/bin/gedit InstallationDate: Installed on 2019-02-25 (3 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190225) ProcCmdline: /usr/bin/gedit --gapplication-service SegvAnalysis: Segfault happened at: 0x7f181f12e302:mov0x18(%rax),%rdi PC (0x7f181f12e302) ok source "0x18(%rax)" (0x0498) not located in a known VMA region (needed readable region)! destination "%rdi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gedit StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/gedit/libgedit-3.14.so ?? () from /usr/lib/x86_64-linux-gnu/gedit/libgedit-3.14.so g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gedit crashed with SIGSEGV in g_closure_invoke() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo whoopsie separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1818063/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1817924] Re: apps launched from gnome shell do not get input focus
Weird, command line do get the focus here, the right thing to do would probably to report upstream in any case. Do you wait for the dialog to be displayed before starting to type or do you hit the keyboard while it's loading? -- 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/1817924 Title: apps launched from gnome shell do not get input focus Status in gnome-shell package in Ubuntu: Incomplete Bug description: Observed on upgrading to disco-proposed today... When launching an app from the dock or from the applications grid (so i believe it's a gnome-shell thing rather than a dock thing), the app opens, but does not get the input focus. You have to either click in the window, or clicking again on the icon of the running app in the dock works, to give it focus. An extra step my muscle memory isn't prepared for! It seems like the sort of thing that might be an option rather than a bug, but if so, changing this behaviour back to its previous default is not at all obvious (I haven't found a way). So guessing it is a bug. NB: After launching an app this way, *no* window has focus. It is lost by the app that had it before, but not given to the newly started app. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.31.90-1ubuntu1 ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20 Uname: Linux 4.19.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Feb 27 15:53:07 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-09-11 (169 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) SourcePackage: gnome-shell UpgradeStatus: Upgraded to disco on 2019-01-13 (44 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1817924/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1809685] Re: The evince application often freezes
Could you also add your journalctl log after getting the issue? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1809685 Title: The evince application often freezes Status in evince package in Ubuntu: Incomplete Bug description: Hi! The evince application (pdf document viewer) often freezes. Thanks. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: evince 3.28.4-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Dec 25 07:12:13 2018 InstallationDate: Installed on 2018-05-06 (232 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1809685/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1797779] Re: [snap] Spellchecking appears to be not working
The iso-codes issue got resolved with https://gitlab.gnome.org/GNOME/gedit/commit/0b3c018d The snap doesn't include dictionnaries though... ** Changed in: gedit (Ubuntu) Importance: Undecided => High ** Changed in: gedit (Ubuntu) Status: New => Triaged -- 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/1797779 Title: [snap] Spellchecking appears to be not working Status in gedit package in Ubuntu: Triaged Bug description: Possibly related console output: ``` (gedit:16993): GLib-GIO-WARNING **: 22:40:02.951: Error creating IO channel for /proc/self/mountinfo: Permission denied (g-file-error-quark, 2) (gedit:16993): gspell-WARNING **: 22:40:03.068: iso_639.xml: Failed to open file ?/usr/share/xml/iso-codes/iso_639.xml?: open() failed: No such file or directory (gedit:16993): gspell-WARNING **: 22:40:03.068: iso_3166.xml: Failed to open file ?/usr/share/xml/iso-codes/iso_3166.xml?: open() failed: No such file or directory ``` The check spelling window spills "Error: Spell checker error: no language set. It’s maybe because no dictionaries are installed." In the poedit snap that uses GtkSpell and Enchant to implement the spellchecking we patched the iso-codes prefix and packs all the spellchecking dictionaries to solve the issue: https://github.com/vslavik/poedit/blob/master/snap/snapcraft.yaml Also, I've packaged a Hunspell content snap that provides the dictionaries: https://forum.snapcraft.io/t/the-hunspell-dictionaries-content-snap/7160 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1797779/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1794895] Re: [snap] Include gedit-plugins as part of gedit build
That's the case in the current version ** Changed in: gedit (Ubuntu) Importance: Undecided => Low ** Changed in: gedit (Ubuntu) Status: New => 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/1794895 Title: [snap] Include gedit-plugins as part of gedit build Status in gedit package in Ubuntu: Fix Released Bug description: Could you have the gedit snap include gedit-plugins as part of its build? That was suggested for Flatpak as a solution to the root cause behind https://gitlab.gnome.org/GNOME/gedit/merge_requests/8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1794895/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1809685] Re: The evince application often freezes
** Changed in: evince (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1809685 Title: The evince application often freezes Status in evince package in Ubuntu: Incomplete Bug description: Hi! The evince application (pdf document viewer) often freezes. Thanks. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: evince 3.28.4-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Dec 25 07:12:13 2018 InstallationDate: Installed on 2018-05-06 (232 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1809685/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1538615] Re: Cat causes login screen to hang
Ok. This bug should be reopened. My lock screen was frozen few times in last months by a cleaning lady who put my headphones on keyboard when cleaning my desk, and left them until next morning. Lock screen is frozen and keyboard or mouse actions do nothing. I wrote about it on https://askubuntu.com/questions/1121906/how-to-prevent-cleaner-from- hanging-my-lock-screen-in-ubuntu-16-04 I have version with this "fix" but it does not work. $ apt policy unity-greeter unity-greeter: Installed: 16.04.2-0ubuntu1 Candidate: 16.04.2-0ubuntu1 Version table: *** 16.04.2-0ubuntu1 500 500 http://pl.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-greeter in Ubuntu. https://bugs.launchpad.net/bugs/1538615 Title: Cat causes login screen to hang Status in unity-greeter package in Ubuntu: Fix Released Status in unity-greeter source package in Trusty: Triaged Bug description: Steps to reproduce: 1. Leave laptop unattended in a cold room with a warm cat. 2. Cat will sit on laptop keyboard. 3. Wait 1 hour. 4. Lightdm will become unresponsive. Symptoms: Due to excessive password input by cat, lightdm acts oddly. I try to hit enter to try the invalid password and then type in the correct password, but enter has no affect. The cursor is not blinking, and hitting backspace has no effect. Using Ctrl+a or using shift+Ctrl+left arrow doesn't select the whole password to delete it. Hitting capslock causes the warning symbol to appear or disappear. The mouse moves, but clicking on the settings icon, date, sound icon, or language icon has no effect. One person suggested seeing if the cat had triggered scroll lock, but toggling between ctrl+q and ctrl+s had no effect. Logging in on a virtual terminal still works. Alternative steps to reproduce if cat is unavailable or uncooperative about being placed on keyboard (see attached pictures): 0. Glare at cat. 1. Restart lightdm. 2. Log in as a normal user. 3. Lock screen with ctrl+alt+l (I'm running Ubuntu 15.10). 4. Weigh self. Weigh self + cat. Find books approximately equal to 10 lbs, and various household items to simulate cat paws (I used two large nail clippers, a fat key, and a bottle opener). 5. Put items on keyboard, avoiding function keys, backspace, and enter. Place books on top of household items. 6. Wait 1 hour. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1538615/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1752813] Re: Pointer speed is too slow even in the fastest setting
Another strange thing that happens is that sometimes after
suspend/resume the pointer speed is changed. Right now, using that
250/250 udev rule I was before having just enough speed at maximum
setting. Today after a suspend/resume cycle I now had to set the
trackpoint speed to around 40% to get a reasonable level. So it seems
somewhere in kernerl/libinput/mutter there is also a bug that makes the
speed inconsistent over suspend/resume.
--
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/1752813
Title:
Pointer speed is too slow even in the fastest setting
Status in gnome-control-center package in Ubuntu:
New
Bug description:
I use the trackpoint on my Lenovo T460s almost exclusively. Even in
the fastest setting on a 2560x1440 screen it is much too slow. I've
had to add the following udev rule to get it to be usable:
ACTION=="add",
SUBSYSTEM=="input",
ATTR{name}=="TPPS/2 IBM TrackPoint",
ATTR{device/sensitivity}="190",
ATTR{device/speed}="220",
ATTR{device/inertia}="6",
ATTR{device/press_to_select}="0"
And even with this and the speed in the control center set to maximum
it is still a bit slow. Trying to push the sensitivity/speed settings
higher will break the trackpoint and even with these settings it seems
that sometimes on resume from sleep the trackpoint fails. After
cycling suspend/resume again it comes back.
There should be a way to set much higher speed settings for the mouse.
Current settings make trackpoints very hard to use which even carries
risk of hand/arm injuries.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: gnome-control-center 1:3.18.2-1ubuntu6
ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
CurrentDesktop: GNOME
Date: Fri Mar 2 08:47:44 2018
InstallationDate: Installed on 2016-10-27 (490 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64
(20160719)
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1752813/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1817620] Re: High cpu usage on alt-tab-ing
OK, removed. Just found it weird that both issues disappered by restarting `gnome-shell`, so assumed they were related by some root cause. Thank you. ** Description changed: Switching between apps was feeling extremely laggy and unsmooth after some days of keeping the laptop on and just alt-tab-ing between apps would keep the cpu consistently at 100% when hitting it more than 8-9 times per second and *not* letting go of Alt (meaning I stay at the same app). - - Also, just whizzing the mouse around on the screen (not moving anything) - would keep the cpu at 40-50%. Some investigation (1) led me to try out restarting the gnome-shell instance (killall followed by manually starting it in the terminal), upon which everything seemed zippy again. No lagginess. The restart was a supposed fix for a memory leak bug (2), but according to the comments a bug fix was supposed to have landed in 18.04 long ago. So either this has not been fixed or this bug is about something else - probably the latter, as the reported memory usage in htop was nowhere near the gigabytes of memory reported in the bug issue for 16722297. Another thing worth mentioning perhaps, based on comments in (3) found through (4), is that I have disabled all extensions. I used to use the Coverflow extension. Expected behaviour: There should be no percieved lag or stuttering in the interface when switching between applications. Actual behaviour: Switching between applications causes a noticable lag/stuttering when the computer has been running for an extended period of time (weeks, but where it has mostly been suspended, meaning actual usage is limited to 3-4 days). - 1. https://www.omgubuntu.co.uk/2018/03/gnome-shell-has-a-memory-leak-and-it-might-not-be-fixed-for-ubuntu-18-04-lts 2. https://bugs.launchpad.net/gnome-shell/+bug/1672297 3. https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1773959 4. https://askubuntu.com/a/1090987/165026 System info: Running Wayland. Description: Ubuntu 18.04.1 LTS Release: 18.04 gnome-shell: - Installert: 3.28.3-0ubuntu0.18.04.4 - Kandidat: 3.28.3-0ubuntu0.18.04.4 - Versjonstabell: - *** 3.28.3-0ubuntu0.18.04.4 500 - 500 http://no.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages - 100 /var/lib/dpkg/status - 3.28.1-0ubuntu2 500 - 500 http://no.archive.ubuntu.com/ubuntu bionic/main amd64 Packages + Installert: 3.28.3-0ubuntu0.18.04.4 + Kandidat: 3.28.3-0ubuntu0.18.04.4 + Versjonstabell: + *** 3.28.3-0ubuntu0.18.04.4 500 + 500 http://no.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages + 100 /var/lib/dpkg/status + 3.28.1-0ubuntu2 500 + 500 http://no.archive.ubuntu.com/ubuntu bionic/main amd64 Packages + + edit: removed info on high cpu usage when using mouse. supposedly + unrelated. -- 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/1817620 Title: High cpu usage on alt-tab-ing Status in gnome-shell package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: Switching between apps was feeling extremely laggy and unsmooth after some days of keeping the laptop on and just alt-tab-ing between apps would keep the cpu consistently at 100% when hitting it more than 8-9 times per second and *not* letting go of Alt (meaning I stay at the same app). Some investigation (1) led me to try out restarting the gnome-shell instance (killall followed by manually starting it in the terminal), upon which everything seemed zippy again. No lagginess. The restart was a supposed fix for a memory leak bug (2), but according to the comments a bug fix was supposed to have landed in 18.04 long ago. So either this has not been fixed or this bug is about something else - probably the latter, as the reported memory usage in htop was nowhere near the gigabytes of memory reported in the bug issue for 16722297. Another thing worth mentioning perhaps, based on comments in (3) found through (4), is that I have disabled all extensions. I used to use the Coverflow extension. Expected behaviour: There should be no percieved lag or stuttering in the interface when switching between applications. Actual behaviour: Switching between applications causes a noticable lag/stuttering when the computer has been running for an extended period of time (weeks, but where it has mostly been suspended, meaning actual usage is limited to 3-4 days). 1. https://www.omgubuntu.co.uk/2018/03/gnome-shell-has-a-memory-leak-and-it-might-not-be-fixed-for-ubuntu-18-04-lts 2. https://bugs.launchpad.net/gnome-shell/+bug/1672297 3. https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1773959 4. https://askubuntu.com/a/1090987/165026 System info:
[Desktop-packages] [Bug 1455097] Please test proposed package
Hello Alex, or anyone else affected,
Accepted unattended-upgrades into xenial-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/unattended-upgrades/1.1ubuntu1.18.04.7~16.04.2 in a few hours, and then
in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. In either case, without details of
your testing we will not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pm-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1455097
Title:
/etc/pm/sleep.d/ is no more processed
Status in aiccu package in Ubuntu:
Invalid
Status in ceph package in Ubuntu:
Fix Released
Status in grub2 package in Ubuntu:
New
Status in ifplugd package in Ubuntu:
New
Status in lizardfs package in Ubuntu:
New
Status in oss4 package in Ubuntu:
New
Status in pm-utils package in Ubuntu:
Won't Fix
Status in toshset package in Ubuntu:
New
Status in unattended-upgrades package in Ubuntu:
Fix Released
Status in unattended-upgrades source package in Xenial:
Fix Committed
Bug description:
[Impact (unattended-upgrades)]
* Unattended-upgrades does not gracefully stop installing updates
when the system goes to hibernation potentially letting the system to
hibernate in a state where the system can't resume from.
[Test Case (unattended-upgrades)]
* Configure the system to have several 20+ packages upgradable by
unattended-upgrades. One easy way of setting this up is starting with
a system where packages from -security are installed but packages from
-updates are not and enabling -updates in u-u:
# echo 'Unattended-Upgrade::Allowed-Origins::
"${distro_id}:${distro_codename}-updates";' > /etc/apt/apt.conf.d
/51unattended-upgrades-updates-too
* Pre-download upgrades
# unattended-upgraded --download-only
* Trigger unattended-upgrades run:
# service apt-daily-upgrade start
* Hibernate, then resume the system and watch unattended-upgrades
being gracefully stopped, checking /var/log/unattended-upgrades
/unattended-upgrades.log. There should be packages left to be
upgraded.
[Regression Potential (unattended-upgrades)]
* The added hook for unattended-upgrades may block the system from
hibernation for 25 minutes if unattended-upgrades (or most likely a
package upgrades) hangs. There is a better solution proposed based on
systemd's inhibitor interface at https://github.com/mvo5/unattended-
upgrades/issues/162 .
[Original Bug Text]
I added a new script in /etc/pm/sleep.d/ that worked fine before the
upgrade to vivid. I was wondering why it doesn't work and I find out
that /var/log/pm-suspend.log is empty, and pm-powersave.log too (last
logs from pm-suspend were on Apr 28, when I upgraded from utopic to
vivid.
The laptop suspends and wakes fine, it just seems that no pm scripts
are run after suspend/powersave.
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: pm-utils 1.4.1-15
ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3
Uname: Linux 3.19.0-16-generic x86_64
ApportVersion: 2.17.2-0ubuntu1
Architecture: amd64
CurrentDesktop: Unity
Date: Thu May 14 15:36:26 2015
DistributionChannelDescriptor:
# This is a distribution channel descriptor
# For more information see
http://wiki.ubuntu.com/DistributionChannelDescriptor
canonical-oem-somerville-precise-amd64-20120703-2
EcryptfsInUse: Yes
InstallationDate: Installed on 2013-03-12 (792 days ago)
InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary
20120703-15:08
PackageArchitecture: all
SourcePackage: pm-utils
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/aiccu/+bug/1455097/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1624644] Please test proposed package
Hello Jarno, or anyone else affected, Accepted unattended-upgrades into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /unattended-upgrades/1.1ubuntu1.18.04.7~16.04.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- 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/1624644 Title: By default settings unattended-upgrade does not automatically remove packages that become unused in conjunction with updating by other software Status in apt package in Ubuntu: Confirmed Status in gnome-software package in Ubuntu: Invalid Status in unattended-upgrades package in Ubuntu: Fix Released Status in update-manager package in Ubuntu: Fix Released Status in unattended-upgrades source package in Xenial: Fix Committed Status in update-manager source package in Xenial: Fix Released Status in apt source package in Artful: Confirmed Status in gnome-software source package in Artful: Invalid Status in unattended-upgrades source package in Artful: Won't Fix Status in update-manager source package in Artful: Fix Released Bug description: [Impact] * Update-manager and unattended-upgrades install many kernel packages during the lifetime of a release but does not remove them automatically leading to those packages filling disk space potentially completely filling /boot and making the system unable to install updates or even boot. * Stable release users are impacted by this bug for years and their systems already collected many autoremovable unused kernel packages, thus they would benefit from backporting the fix greatly. * The bug is fixed by removing autoremovable (not currently booted) kernel packages when running unattended-upgrades or update-manager. Update manager offers the kernel removals when there are other updates to be installed. [Test Case] 1. Install kernel packages to be removed, mark them auto-installed and run apt's kernel hook script to make apt consider them autoremovable: sudo apt install -y linux-image-extra-4.4.0-92-generic linux-image-extra-4.4.0-93-generic sudo apt-mark auto linux-image-extra-4.4.0-92-generic linux-image-extra-4.4.0-93-generic sudo /etc/kernel/postinst.d/apt-auto-removal 2. Also downgrade a package to be upgraded: sudo apt-get install -y --allow-downgrades ca- certificates=20160104ubuntu1 3. (update-manager). Run update-manager and observe that kernel packages are offered for removal in Details of updates. sudo update-manager 4. (update-manager) Click on Install Now and observe that the kernel packages are removed. 3. (unattended-upgrades, the fix comes in an update of u-u) Run unattended-upgrades manually and observe the removal of the autoremovable kernel packages: sudo unattended-upgrade -v [Regression Potential] The change may cause update-manager or unattanded-upgrades to remove used kernel packages or fail to install other package updates. [Other Info] The unattended-upgrades fix is uploaded with many other fixes and those may cause regressions in other areas in unattended-upgrades. [Original bug text] When using default settings for unattended-upgrade i.e. Unattended-Upgrade::Remove-Unused-Dependencies "false"; # default "false" Unattended-Upgrade::Remove-New-Unused-Dependencies "true"; # default "true" in configuration file /etc/apt/apt.conf.d/50unattended-upgrades, unattended-upgrade is unable to remove packages that become unused in conjunction with updating by other software such as update-manager or apt full-upgrade. This is because unattended-upgrade compares the list of unneeded packages before and after it upgrades packages to detect which packages are new unused ones. Consequently, if user installs new kernels using e.g. update-manager, the excessive kernels will not be removed by
[Desktop-packages] [Bug 1818063] gedit crashed with SIGSEGV in g_closure_invoke()
StacktraceTop: update_actions_sensitivity (window=0x558054c68e30) at ../gedit/gedit-window.c:605 readonly_changed (file=, pspec=, window=0x558054c68e30) at ../gedit/gedit-window.c:1923 ?? () ?? () -- 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/1818063 Title: gedit crashed with SIGSEGV in update_actions_sensitivity() Status in gedit package in Ubuntu: New Bug description: I was NOT using gedit. corrado@corrado-p7-dd-0225:~$ inxi -Fx System:Host: corrado-p7-dd-0225 Kernel: 4.19.0-13-generic x86_64 bits: 64 compiler: gcc v: 8.2.1 Desktop: Gnome 3.30.2 Distro: Ubuntu 19.04 (Disco Dingo) Machine: Type: Desktop Mobo: ASRock model: H110M-G/M.2 serial: UEFI: American Megatrends v: P1.10 date: 05/11/2017 CPU: Topology: Dual Core model: Intel Core i3-7100 bits: 64 type: MT MCP arch: Kaby Lake rev: 9 L2 cache: 3072 KiB flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 31296 Speed: 800 MHz min/max: 800/3900 MHz Core speeds (MHz): 1: 800 2: 800 3: 801 4: 800 Graphics: Device-1: Intel HD Graphics 630 vendor: ASRock driver: i915 v: kernel bus ID: 00:02.0 Display: x11 server: X.Org 1.20.3 driver: i915 resolution: 1920x1080~60Hz OpenGL: renderer: Mesa DRI Intel HD Graphics 630 (Kaby Lake GT2) v: 4.5 Mesa 18.3.4 direct render: Yes Audio: Device-1: Intel 100 Series/C230 Series Family HD Audio vendor: ASRock driver: snd_hda_intel v: kernel bus ID: 00:1f.3 Device-2: Logitech QuickCam Pro 9000 type: USB driver: snd-usb-audio,uvcvideo bus ID: 1-10:4 Sound Server: ALSA v: k4.19.0-13-generic Network: Device-1: Intel Ethernet I219-V vendor: ASRock driver: e1000e v: 3.2.6-k port: f040 bus ID: 00:1f.6 IF: enp0s31f6 state: up speed: 100 Mbps duplex: full mac: 70:85:c2:44:7b:86 Drives:Local Storage: total: 931.51 GiB used: 8.05 GiB (0.9%) ID-1: /dev/sda vendor: Toshiba model: DT01ACA100 size: 931.51 GiB Partition: ID-1: / size: 31.25 GiB used: 8.04 GiB (25.7%) fs: ext4 dev: /dev/sda7 ID-2: swap-1 size: 8.00 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda2 Sensors: System Temperatures: cpu: 40.5 C mobo: N/A Fan Speeds (RPM): N/A Info: Processes: 205 Uptime: 1h 14m Memory: 7.50 GiB used: 1.31 GiB (17.5%) Init: systemd runlevel: 5 Compilers: gcc: 8.2.0 Shell: bash v: 5.0.2 inxi: 3.0.32 corrado@corrado-p7-dd-0225:~$ ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: gedit 3.31.90-1build1 ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20 Uname: Linux 4.19.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu21 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Thu Feb 28 13:43:55 2019 ExecutablePath: /usr/bin/gedit InstallationDate: Installed on 2019-02-25 (3 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190225) ProcCmdline: /usr/bin/gedit --gapplication-service SegvAnalysis: Segfault happened at: 0x7f181f12e302:mov0x18(%rax),%rdi PC (0x7f181f12e302) ok source "0x18(%rax)" (0x0498) not located in a known VMA region (needed readable region)! destination "%rdi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gedit StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/gedit/libgedit-3.14.so ?? () from /usr/lib/x86_64-linux-gnu/gedit/libgedit-3.14.so g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gedit crashed with SIGSEGV in g_closure_invoke() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo whoopsie separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1818063/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1818063] Stacktrace.txt
** Attachment added: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1818063/+attachment/5242284/+files/Stacktrace.txt -- 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/1818063 Title: gedit crashed with SIGSEGV in update_actions_sensitivity() Status in gedit package in Ubuntu: New Bug description: I was NOT using gedit. corrado@corrado-p7-dd-0225:~$ inxi -Fx System:Host: corrado-p7-dd-0225 Kernel: 4.19.0-13-generic x86_64 bits: 64 compiler: gcc v: 8.2.1 Desktop: Gnome 3.30.2 Distro: Ubuntu 19.04 (Disco Dingo) Machine: Type: Desktop Mobo: ASRock model: H110M-G/M.2 serial: UEFI: American Megatrends v: P1.10 date: 05/11/2017 CPU: Topology: Dual Core model: Intel Core i3-7100 bits: 64 type: MT MCP arch: Kaby Lake rev: 9 L2 cache: 3072 KiB flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 31296 Speed: 800 MHz min/max: 800/3900 MHz Core speeds (MHz): 1: 800 2: 800 3: 801 4: 800 Graphics: Device-1: Intel HD Graphics 630 vendor: ASRock driver: i915 v: kernel bus ID: 00:02.0 Display: x11 server: X.Org 1.20.3 driver: i915 resolution: 1920x1080~60Hz OpenGL: renderer: Mesa DRI Intel HD Graphics 630 (Kaby Lake GT2) v: 4.5 Mesa 18.3.4 direct render: Yes Audio: Device-1: Intel 100 Series/C230 Series Family HD Audio vendor: ASRock driver: snd_hda_intel v: kernel bus ID: 00:1f.3 Device-2: Logitech QuickCam Pro 9000 type: USB driver: snd-usb-audio,uvcvideo bus ID: 1-10:4 Sound Server: ALSA v: k4.19.0-13-generic Network: Device-1: Intel Ethernet I219-V vendor: ASRock driver: e1000e v: 3.2.6-k port: f040 bus ID: 00:1f.6 IF: enp0s31f6 state: up speed: 100 Mbps duplex: full mac: 70:85:c2:44:7b:86 Drives:Local Storage: total: 931.51 GiB used: 8.05 GiB (0.9%) ID-1: /dev/sda vendor: Toshiba model: DT01ACA100 size: 931.51 GiB Partition: ID-1: / size: 31.25 GiB used: 8.04 GiB (25.7%) fs: ext4 dev: /dev/sda7 ID-2: swap-1 size: 8.00 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda2 Sensors: System Temperatures: cpu: 40.5 C mobo: N/A Fan Speeds (RPM): N/A Info: Processes: 205 Uptime: 1h 14m Memory: 7.50 GiB used: 1.31 GiB (17.5%) Init: systemd runlevel: 5 Compilers: gcc: 8.2.0 Shell: bash v: 5.0.2 inxi: 3.0.32 corrado@corrado-p7-dd-0225:~$ ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: gedit 3.31.90-1build1 ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20 Uname: Linux 4.19.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu21 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Thu Feb 28 13:43:55 2019 ExecutablePath: /usr/bin/gedit InstallationDate: Installed on 2019-02-25 (3 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190225) ProcCmdline: /usr/bin/gedit --gapplication-service SegvAnalysis: Segfault happened at: 0x7f181f12e302:mov0x18(%rax),%rdi PC (0x7f181f12e302) ok source "0x18(%rax)" (0x0498) not located in a known VMA region (needed readable region)! destination "%rdi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gedit StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/gedit/libgedit-3.14.so ?? () from /usr/lib/x86_64-linux-gnu/gedit/libgedit-3.14.so g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gedit crashed with SIGSEGV in g_closure_invoke() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo whoopsie separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1818063/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1783298] Re: AuthInfoRequired negotiate in cups 2.2.7 in Bionic does not work
To get kerberos authentication fixed again in CUPS would be extremely good! I guess downgrading to SMB1 is not even an option in many bigger and/or more open environments -- typically managed by someone else with security oriented attitude. -- 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/1783298 Title: AuthInfoRequired negotiate in cups 2.2.7 in Bionic does not work Status in cups package in Ubuntu: Confirmed Bug description: Hi, We have our printers configured to print to a Windows print server. In Ubuntu 14.04 and 16.04 our setup works fine but in 18.04 our setup seems to be acting more like AuthInfoRequired username,password i.e. it prompts for a password when printing rather than using the available Kerberos credentials. We are using an unaltered cupsd.conf file and are adding printers with the following command: lpadmin -p "printer" -D "Printer" -L "room" -v "smb://printers.cis.strath.ac.uk/printers" -o Media=A4 -o PageSize=A4 -o printer-error-policy=abort-job -o auth-info-required=negotiate -m "CIS/hp-officejet_pro_476_576_series-ps.ppd" the smb backend has been linked to /usr/lib/x86_64-linux- gnu/samba/smbspool_krb5_wrapper (I've added this the apparmor profile as it's blocked by default) and the permissions on this file changed to 700 (owner root) as per manpage instructions. When using lp -d printer /tmp/test.txt I get the following response: Password for myuid on localhost? Typing my password gets the job accepted to the queue but it does spool to the Windows Print Server and in the error_log file I can see D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 - AUTH_INFO_REQUIRED=negotiate D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 - Started with uid=0 D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 - AUTH_UID is not set As I said earlier this all works perfectly on Xenial and Trusty. (A similar AuthInfoRequired negotiate setup also works in cups 2.2.5 on MacOS 10.13) Any ideas how to fix this? Thanks, Ian. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cups 2.2.7-1ubuntu2.1 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Tue Jul 24 10:03:57 2018 InstallationDate: Installed on 2018-06-22 (31 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 0461:4d81 Primax Electronics, Ltd Dell N889 Optical Mouse Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. OptiPlex 790 Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz root=/dev/mapper/pd--ig--vg-root ro quiet splash SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/28/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0HY9JP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA05:bd05/28/2011:svnDellInc.:pnOptiPlex790:pvr01:rvnDellInc.:rn0HY9JP:rvrA00:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 790 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1783298/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1818063] StacktraceSource.txt
** Attachment added: "StacktraceSource.txt" https://bugs.launchpad.net/bugs/1818063/+attachment/5242285/+files/StacktraceSource.txt -- 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/1818063 Title: gedit crashed with SIGSEGV in update_actions_sensitivity() Status in gedit package in Ubuntu: New Bug description: I was NOT using gedit. corrado@corrado-p7-dd-0225:~$ inxi -Fx System:Host: corrado-p7-dd-0225 Kernel: 4.19.0-13-generic x86_64 bits: 64 compiler: gcc v: 8.2.1 Desktop: Gnome 3.30.2 Distro: Ubuntu 19.04 (Disco Dingo) Machine: Type: Desktop Mobo: ASRock model: H110M-G/M.2 serial: UEFI: American Megatrends v: P1.10 date: 05/11/2017 CPU: Topology: Dual Core model: Intel Core i3-7100 bits: 64 type: MT MCP arch: Kaby Lake rev: 9 L2 cache: 3072 KiB flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 31296 Speed: 800 MHz min/max: 800/3900 MHz Core speeds (MHz): 1: 800 2: 800 3: 801 4: 800 Graphics: Device-1: Intel HD Graphics 630 vendor: ASRock driver: i915 v: kernel bus ID: 00:02.0 Display: x11 server: X.Org 1.20.3 driver: i915 resolution: 1920x1080~60Hz OpenGL: renderer: Mesa DRI Intel HD Graphics 630 (Kaby Lake GT2) v: 4.5 Mesa 18.3.4 direct render: Yes Audio: Device-1: Intel 100 Series/C230 Series Family HD Audio vendor: ASRock driver: snd_hda_intel v: kernel bus ID: 00:1f.3 Device-2: Logitech QuickCam Pro 9000 type: USB driver: snd-usb-audio,uvcvideo bus ID: 1-10:4 Sound Server: ALSA v: k4.19.0-13-generic Network: Device-1: Intel Ethernet I219-V vendor: ASRock driver: e1000e v: 3.2.6-k port: f040 bus ID: 00:1f.6 IF: enp0s31f6 state: up speed: 100 Mbps duplex: full mac: 70:85:c2:44:7b:86 Drives:Local Storage: total: 931.51 GiB used: 8.05 GiB (0.9%) ID-1: /dev/sda vendor: Toshiba model: DT01ACA100 size: 931.51 GiB Partition: ID-1: / size: 31.25 GiB used: 8.04 GiB (25.7%) fs: ext4 dev: /dev/sda7 ID-2: swap-1 size: 8.00 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda2 Sensors: System Temperatures: cpu: 40.5 C mobo: N/A Fan Speeds (RPM): N/A Info: Processes: 205 Uptime: 1h 14m Memory: 7.50 GiB used: 1.31 GiB (17.5%) Init: systemd runlevel: 5 Compilers: gcc: 8.2.0 Shell: bash v: 5.0.2 inxi: 3.0.32 corrado@corrado-p7-dd-0225:~$ ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: gedit 3.31.90-1build1 ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20 Uname: Linux 4.19.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu21 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Thu Feb 28 13:43:55 2019 ExecutablePath: /usr/bin/gedit InstallationDate: Installed on 2019-02-25 (3 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190225) ProcCmdline: /usr/bin/gedit --gapplication-service SegvAnalysis: Segfault happened at: 0x7f181f12e302:mov0x18(%rax),%rdi PC (0x7f181f12e302) ok source "0x18(%rax)" (0x0498) not located in a known VMA region (needed readable region)! destination "%rdi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gedit StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/gedit/libgedit-3.14.so ?? () from /usr/lib/x86_64-linux-gnu/gedit/libgedit-3.14.so g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gedit crashed with SIGSEGV in g_closure_invoke() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo whoopsie separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1818063/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1759462] Re: Keyboard shortcuts not operational on 18.04
Kubuntu 18.04, KDE Plasma Version 5.12.7, Qt Version 5.9.5, Microsoft Natural keyboard: Same thing: Although configured in Global Shortcuts, Ctrl-Alt-t does not trigger Konsole -- 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/1759462 Title: Keyboard shortcuts not operational on 18.04 Status in gnome-settings-daemon package in Ubuntu: Confirmed Bug description: After installing 18.04, I noticed that certain keyboard shortcuts no longer function. It appears to be related to the shortcuts that gnome-settings-daemon control as my shortcuts that are provided by my desktop (Budgie) still function. Some examples are: * Media keys for volume up/down/mute * ctrl-alt-t for the terminal. I tried changing the shortcut to test. Same behaviour. I double checked, and it looks like the needed daemon is still running, ``` dustin3337 0.0 0.2 500736 22216 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-keyboard dustin3338 0.0 0.3 943372 25732 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-media-keys dustin3343 0.0 0.0 274908 5844 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-mouse dustin3345 0.0 0.3 519896 25144 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-power dustin3348 0.0 0.1 346004 10212 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-print-notifications dustin3351 0.0 0.0 374684 7952 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-smartcard dustin3355 0.0 0.1 329584 8064 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-sound dustin3361 0.0 0.1 449708 9856 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-sharing dustin3367 0.0 0.0 272416 4772 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-screensaver-proxy dustin3375 0.0 0.0 420028 5804 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-rfkill dustin3383 0.0 0.2 507120 23244 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-wacom dustin3385 0.0 0.3 498040 25040 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-xsettings dustin3387 0.0 0.0 274900 5936 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-a11y-settings dustin3392 0.0 0.2 496016 22044 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-clipboard dustin3395 0.0 0.3 810156 25976 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-color dustin3396 0.0 0.2 471656 21080 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-datetime dustin3400 0.0 0.0 361196 7116 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-housekeeping dustin3433 0.0 0.1 505404 12576 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-printer dustin9776 0.0 0.0 18188 1032 pts/1S+ 21:19 0:00 grep --color=auto gnome-settings-daemon ``` Reboot does not seem to help. However, occasionally the shortcuts do seem to work - but only very occasionally. Any other info needed? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-settings-daemon 3.28.0-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 ApportVersion: 2.20.9-0ubuntu1 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Tue Mar 27 21:12:18 2018 InstallationDate: Installed on 2018-03-05 (22 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180304) SourcePackage: gnome-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1759462/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1818063] ThreadStacktrace.txt
** Attachment added: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1818063/+attachment/5242286/+files/ThreadStacktrace.txt ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1818063/+attachment/5242273/+files/CoreDump.gz ** Changed in: gedit (Ubuntu) Importance: Undecided => Medium ** Summary changed: - gedit crashed with SIGSEGV in g_closure_invoke() + gedit crashed with SIGSEGV in update_actions_sensitivity() ** Tags removed: need-amd64-retrace -- 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/1818063 Title: gedit crashed with SIGSEGV in update_actions_sensitivity() Status in gedit package in Ubuntu: New Bug description: I was NOT using gedit. corrado@corrado-p7-dd-0225:~$ inxi -Fx System:Host: corrado-p7-dd-0225 Kernel: 4.19.0-13-generic x86_64 bits: 64 compiler: gcc v: 8.2.1 Desktop: Gnome 3.30.2 Distro: Ubuntu 19.04 (Disco Dingo) Machine: Type: Desktop Mobo: ASRock model: H110M-G/M.2 serial: UEFI: American Megatrends v: P1.10 date: 05/11/2017 CPU: Topology: Dual Core model: Intel Core i3-7100 bits: 64 type: MT MCP arch: Kaby Lake rev: 9 L2 cache: 3072 KiB flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 31296 Speed: 800 MHz min/max: 800/3900 MHz Core speeds (MHz): 1: 800 2: 800 3: 801 4: 800 Graphics: Device-1: Intel HD Graphics 630 vendor: ASRock driver: i915 v: kernel bus ID: 00:02.0 Display: x11 server: X.Org 1.20.3 driver: i915 resolution: 1920x1080~60Hz OpenGL: renderer: Mesa DRI Intel HD Graphics 630 (Kaby Lake GT2) v: 4.5 Mesa 18.3.4 direct render: Yes Audio: Device-1: Intel 100 Series/C230 Series Family HD Audio vendor: ASRock driver: snd_hda_intel v: kernel bus ID: 00:1f.3 Device-2: Logitech QuickCam Pro 9000 type: USB driver: snd-usb-audio,uvcvideo bus ID: 1-10:4 Sound Server: ALSA v: k4.19.0-13-generic Network: Device-1: Intel Ethernet I219-V vendor: ASRock driver: e1000e v: 3.2.6-k port: f040 bus ID: 00:1f.6 IF: enp0s31f6 state: up speed: 100 Mbps duplex: full mac: 70:85:c2:44:7b:86 Drives:Local Storage: total: 931.51 GiB used: 8.05 GiB (0.9%) ID-1: /dev/sda vendor: Toshiba model: DT01ACA100 size: 931.51 GiB Partition: ID-1: / size: 31.25 GiB used: 8.04 GiB (25.7%) fs: ext4 dev: /dev/sda7 ID-2: swap-1 size: 8.00 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda2 Sensors: System Temperatures: cpu: 40.5 C mobo: N/A Fan Speeds (RPM): N/A Info: Processes: 205 Uptime: 1h 14m Memory: 7.50 GiB used: 1.31 GiB (17.5%) Init: systemd runlevel: 5 Compilers: gcc: 8.2.0 Shell: bash v: 5.0.2 inxi: 3.0.32 corrado@corrado-p7-dd-0225:~$ ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: gedit 3.31.90-1build1 ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20 Uname: Linux 4.19.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu21 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Thu Feb 28 13:43:55 2019 ExecutablePath: /usr/bin/gedit InstallationDate: Installed on 2019-02-25 (3 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190225) ProcCmdline: /usr/bin/gedit --gapplication-service SegvAnalysis: Segfault happened at: 0x7f181f12e302:mov0x18(%rax),%rdi PC (0x7f181f12e302) ok source "0x18(%rax)" (0x0498) not located in a known VMA region (needed readable region)! destination "%rdi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gedit StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/gedit/libgedit-3.14.so ?? () from /usr/lib/x86_64-linux-gnu/gedit/libgedit-3.14.so g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gedit crashed with SIGSEGV in g_closure_invoke() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo whoopsie separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1818063/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1818063] [NEW] gedit crashed with SIGSEGV in update_actions_sensitivity()
Public bug reported: I was NOT using gedit. corrado@corrado-p7-dd-0225:~$ inxi -Fx System:Host: corrado-p7-dd-0225 Kernel: 4.19.0-13-generic x86_64 bits: 64 compiler: gcc v: 8.2.1 Desktop: Gnome 3.30.2 Distro: Ubuntu 19.04 (Disco Dingo) Machine: Type: Desktop Mobo: ASRock model: H110M-G/M.2 serial: UEFI: American Megatrends v: P1.10 date: 05/11/2017 CPU: Topology: Dual Core model: Intel Core i3-7100 bits: 64 type: MT MCP arch: Kaby Lake rev: 9 L2 cache: 3072 KiB flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 31296 Speed: 800 MHz min/max: 800/3900 MHz Core speeds (MHz): 1: 800 2: 800 3: 801 4: 800 Graphics: Device-1: Intel HD Graphics 630 vendor: ASRock driver: i915 v: kernel bus ID: 00:02.0 Display: x11 server: X.Org 1.20.3 driver: i915 resolution: 1920x1080~60Hz OpenGL: renderer: Mesa DRI Intel HD Graphics 630 (Kaby Lake GT2) v: 4.5 Mesa 18.3.4 direct render: Yes Audio: Device-1: Intel 100 Series/C230 Series Family HD Audio vendor: ASRock driver: snd_hda_intel v: kernel bus ID: 00:1f.3 Device-2: Logitech QuickCam Pro 9000 type: USB driver: snd-usb-audio,uvcvideo bus ID: 1-10:4 Sound Server: ALSA v: k4.19.0-13-generic Network: Device-1: Intel Ethernet I219-V vendor: ASRock driver: e1000e v: 3.2.6-k port: f040 bus ID: 00:1f.6 IF: enp0s31f6 state: up speed: 100 Mbps duplex: full mac: 70:85:c2:44:7b:86 Drives:Local Storage: total: 931.51 GiB used: 8.05 GiB (0.9%) ID-1: /dev/sda vendor: Toshiba model: DT01ACA100 size: 931.51 GiB Partition: ID-1: / size: 31.25 GiB used: 8.04 GiB (25.7%) fs: ext4 dev: /dev/sda7 ID-2: swap-1 size: 8.00 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda2 Sensors: System Temperatures: cpu: 40.5 C mobo: N/A Fan Speeds (RPM): N/A Info: Processes: 205 Uptime: 1h 14m Memory: 7.50 GiB used: 1.31 GiB (17.5%) Init: systemd runlevel: 5 Compilers: gcc: 8.2.0 Shell: bash v: 5.0.2 inxi: 3.0.32 corrado@corrado-p7-dd-0225:~$ ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: gedit 3.31.90-1build1 ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20 Uname: Linux 4.19.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu21 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Thu Feb 28 13:43:55 2019 ExecutablePath: /usr/bin/gedit InstallationDate: Installed on 2019-02-25 (3 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190225) ProcCmdline: /usr/bin/gedit --gapplication-service SegvAnalysis: Segfault happened at: 0x7f181f12e302: mov0x18(%rax),%rdi PC (0x7f181f12e302) ok source "0x18(%rax)" (0x0498) not located in a known VMA region (needed readable region)! destination "%rdi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gedit StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/gedit/libgedit-3.14.so ?? () from /usr/lib/x86_64-linux-gnu/gedit/libgedit-3.14.so g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gedit crashed with SIGSEGV in g_closure_invoke() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo whoopsie separator: ** Affects: gedit (Ubuntu) Importance: Medium Status: New ** Tags: amd64 apport-crash disco ** Information type changed from Private to Public -- 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/1818063 Title: gedit crashed with SIGSEGV in update_actions_sensitivity() Status in gedit package in Ubuntu: New Bug description: I was NOT using gedit. corrado@corrado-p7-dd-0225:~$ inxi -Fx System:Host: corrado-p7-dd-0225 Kernel: 4.19.0-13-generic x86_64 bits: 64 compiler: gcc v: 8.2.1 Desktop: Gnome 3.30.2 Distro: Ubuntu 19.04 (Disco Dingo) Machine: Type: Desktop Mobo: ASRock model: H110M-G/M.2 serial: UEFI: American Megatrends v: P1.10 date: 05/11/2017 CPU: Topology: Dual Core model: Intel Core i3-7100 bits: 64 type: MT MCP arch: Kaby Lake rev: 9 L2 cache: 3072 KiB flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 31296 Speed: 800 MHz min/max: 800/3900 MHz Core speeds (MHz): 1: 800 2: 800 3: 801 4: 800 Graphics: Device-1: Intel HD Graphics 630 vendor: ASRock driver: i915 v: kernel bus ID: 00:02.0 Display: x11 server: X.Org 1.20.3 driver: i915 resolution: 1920x1080~60Hz OpenGL: renderer: Mesa DRI Intel HD Graphics 630 (Kaby Lake GT2) v: 4.5 Mesa 18.3.4 direct render: Yes Audio: Device-1: Intel 100 Series/C230
[Desktop-packages] [Bug 998056] Re: Maximize window freezes computer for about 10 seconds
No reply to comment #9 so with 15 users affected the issue must have been fixed ** Changed in: gnome-terminal (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/998056 Title: Maximize window freezes computer for about 10 seconds Status in gnome-terminal package in Ubuntu: Fix Released Status in xchat-gnome package in Ubuntu: Fix Released Bug description: When using the terminal, if I try to maximize it's window using the menus, the maximize button or any shortcut, my display freezes for about 10 seconds (nothing responding, not even alt-tab, displaying the dash or anything... ). After that, everything goes back to normal. If I type something in the mean time, the terminal still grabs those keys. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gnome-terminal 3.4.1.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14 Uname: Linux 3.2.0-24-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu7 Architecture: amd64 Date: Fri May 11 09:43:57 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) ProcEnviron: LANGUAGE=en_CA:en TERM=xterm PATH=(custom, user) LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/998056/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 850649] Re: gnome-terminal extremely slow and display buggy
Report did not expire due to bug watch No reply to comment #56 62 users affected so issue must have been fixed ** Changed in: nvidia-drivers-ubuntu Status: Incomplete => Fix Released ** Changed in: gnome-terminal (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/850649 Title: gnome-terminal extremely slow and display buggy Status in NVIDIA Drivers Ubuntu: Fix Released Status in gnome-terminal package in Ubuntu: Fix Released Bug description: After the update to oneiric the gnome-terminal appears to be slow and display is sometimes buggy: * changing between windows and tabs is slow although other applications (like chromium) are not affected * sometimes the display is not updated and some parts (exactly on character box boundaries) of the terminal just show the background ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gnome-terminal 3.0.1-0ubuntu3 ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4 Uname: Linux 3.0.0-11-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.23-0ubuntu1 Architecture: amd64 Date: Thu Sep 15 08:28:30 2011 EcryptfsInUse: Yes ExecutablePath: /usr/bin/gnome-terminal InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) SourcePackage: gnome-terminal UpgradeStatus: Upgraded to oneiric on 2011-09-01 (13 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/850649/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 880734] Re: gnome-terminal window changes size to one-line in KDE
Bug did not expire due to bug watch No reply to comment #4 so closing ** Changed in: gnome-terminal (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/880734 Title: gnome-terminal window changes size to one-line in KDE Status in gnome-terminal package in Ubuntu: Invalid Bug description: I'm using kde, but I prefer the gnome-terminal, because I'm using some features which the konsole does not offer. Under kde, the gnome- terminal behaves a bit strange. When starting the gnome-terminal under kwin, the window sizes down to one single line hight. When activating or deactivating the menu (F12), the window sizes down to minimum width and height. When I resize the window, the cursor freezes and the window contents stop updating, e.g. text does not appear when I'm typing. After dragging the window by grabbing the title bar with the mouse, the cursor will blink again and the contents will be updated. I tried to force gnome-terminal windows to open in a certain size via kcmshell4, but this had no helpful effect. The gnome-terminal first opened in the desired size, but then rapidly changed size to a single line again. There are also some redraw problems, when parts of a gnome-terminal have been hidden and are brought into foreground again, but these problems appear randomly: the hidden parts are being redrawn when I move the windows. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gnome-terminal 3.0.1-0ubuntu3 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic-pae 3.0.4 Uname: Linux 3.0.0-12-generic-pae i686 ApportVersion: 1.23-0ubuntu3 Architecture: i386 Date: Mon Oct 24 10:34:07 2011 ExecutablePath: /usr/bin/gnome-terminal InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007) ProcEnviron: PATH=(custom, user) LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: gnome-terminal UpgradeStatus: Upgraded to oneiric on 2011-10-14 (9 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/880734/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1127777] Re: nautilus 3.6 SIGSEGV in g_str_has_suffix()
Bug did not expire due big watch No reply to comment #28 so closing ** Changed in: nautilus (Ubuntu) Status: Incomplete => Invalid -- 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/112 Title: nautilus 3.6 SIGSEGV in g_str_has_suffix() Status in nautilus package in Ubuntu: Invalid Status in nautilus package in Fedora: Won't Fix Bug description: Not really sure what I was doing, but nautilus crashed and wallpaper turned black. ProblemType: Crash DistroRelease: Ubuntu 13.04 Package: nautilus 1:3.6.3-0ubuntu5 ProcVersionSignature: Ubuntu 3.8.0-6.13-generic 3.8.0-rc7 Uname: Linux 3.8.0-6-generic x86_64 ApportVersion: 2.8-0ubuntu4 Architecture: amd64 Date: Sat Feb 16 20:24:53 2013 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b"'800x550+1120+24'" InstallationDate: Installed on 2013-02-14 (3 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130211) MarkForUpload: True ProcCmdline: nautilus -n ProcEnviron: LANGUAGE=en_US:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f8927214711:movdqu (%rdi),%xmm1 PC (0x7f8927214711) ok source "(%rdi)" (0x736e6f63692e) not located in a known VMA region (needed readable region)! destination "%xmm1" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: nautilus StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libc.so.6 g_str_has_suffix () from /lib/x86_64-linux-gnu/libglib-2.0.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 in g_str_has_suffix() 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/112/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1797255] Re: Epson WF-2760 Not working properly
** Tags added: cosmic -- 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/1797255 Title: Epson WF-2760 Not working properly Status in cups package in Ubuntu: New Bug description: My Epson WF-2670 Network printer is having issues printing correctly on Ubuntu. It prints differently depending on what protocol i use, and what configuration i use. The only configuration that gets it right, is the Driverless IPP printing on Ubuntu 18.04. However using the same Driverless Printing option in Ubuntu 18.10 dose not work properly. When printing the text runs off the side of the page. The printer supports PPD, LDP, IPP, and DNS printing. There is no specific driver for this printer in the repos. There is an official driver on the Epson Website for this printer however it's unmaintained and out of date. As a result it doesn't work. Instead When choosing a setup option in Ubuntu (or any other distro) it automatically selects the generic epson-escpr inkjet Driver. This driver will print. But again, it prints incorrectly with the text going off the side of the page. The driverless IPP printing in Ubuntu 18.04 gets it right. But in 18.10 the same exact configuration prints incorrectly. All other protocols i mentioned all print the same on both versions of Ubuntu, all of which are equally incorrect. Driverless IPP printing in 18.04 is the only one that dose it correctly. This problem locks me to 18.04. Which isn't an immediate problem, But probably will be in the long term. I've included a picture of some test prints. Both are from Ubuntu 18.10. The one on the left is using the epson-escpr Driver using the LDP/passthru option. And the one on the right is using the Default Driverless Printing. You can see the text going off the side of the page on both, and off the bottom of the page on the one on the right. Whatever configuration/package version is being used in Ubuntu 18.04 for Driverless Printing works properly. But in 18.10 it dose Not. Nor do any of the other configuration Options. I can manually change the page margins in the settings, But this only changes where the Black border is on those test prints, The text itself stills runs outside of the margins. Trying to print an Office document or PDF yields similar results. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1797255/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1818053] Re: /usr/bin/seahorse:11:g_atomic_ref_count_dec:g_variant_unref:___lambda22_:____lambda22__gasync_ready_callback:g_simple_async_result_complete
Confirmed, it segfaults when change the keyring password * right click on the 'login' in the sidebar * select change password * type the old password then new one/confirm/validate -> it segfaults, on this code line https://gitlab.gnome.org/GNOME/seahorse/blob/3.31.91/gkr/gkr-keyring.vala#L194 could it be a vala bug? (that's still an issue in git master) ** Changed in: seahorse (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to seahorse in Ubuntu. https://bugs.launchpad.net/bugs/1818053 Title: /usr/bin/seahorse:11:g_atomic_ref_count_dec:g_variant_unref:___lambda22_:lambda22__gasync_ready_callback:g_simple_async_result_complete Status in seahorse package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding seahorse. This problem was most recently seen with package version 3.31.91-1, the problem page at https://errors.ubuntu.com/problem/27dfb9fa56c174fbd9ea1d62a3efc5816a0b5fb9 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/1818053/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1818053] Re: /usr/bin/seahorse:11:g_atomic_ref_count_dec:g_variant_unref:___lambda22_:____lambda22__gasync_ready_callback:g_simple_async_result_complete
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: seahorse (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to seahorse in Ubuntu. https://bugs.launchpad.net/bugs/1818053 Title: /usr/bin/seahorse:11:g_atomic_ref_count_dec:g_variant_unref:___lambda22_:lambda22__gasync_ready_callback:g_simple_async_result_complete Status in seahorse package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding seahorse. This problem was most recently seen with package version 3.31.91-1, the problem page at https://errors.ubuntu.com/problem/27dfb9fa56c174fbd9ea1d62a3efc5816a0b5fb9 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/1818053/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1818053] [NEW] /usr/bin/seahorse:11:g_atomic_ref_count_dec:g_variant_unref:___lambda22_:____lambda22__gasync_ready_callback:g_simple_async_result_complete
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding seahorse. This problem was most recently seen with package version 3.31.91-1, the problem page at https://errors.ubuntu.com/problem/27dfb9fa56c174fbd9ea1d62a3efc5816a0b5fb9 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: seahorse (Ubuntu) Importance: High Status: Confirmed ** Tags: disco -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to seahorse in Ubuntu. https://bugs.launchpad.net/bugs/1818053 Title: /usr/bin/seahorse:11:g_atomic_ref_count_dec:g_variant_unref:___lambda22_:lambda22__gasync_ready_callback:g_simple_async_result_complete Status in seahorse package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding seahorse. This problem was most recently seen with package version 3.31.91-1, the problem page at https://errors.ubuntu.com/problem/27dfb9fa56c174fbd9ea1d62a3efc5816a0b5fb9 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/1818053/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1817924] Re: apps launched from gnome shell do not get input focus
confirmed, gedit seems to be immune for some reason. pretty much anything else i tried is not; calculator, terminal, libreoffice, nautilus... -- 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/1817924 Title: apps launched from gnome shell do not get input focus Status in gnome-shell package in Ubuntu: Incomplete Bug description: Observed on upgrading to disco-proposed today... When launching an app from the dock or from the applications grid (so i believe it's a gnome-shell thing rather than a dock thing), the app opens, but does not get the input focus. You have to either click in the window, or clicking again on the icon of the running app in the dock works, to give it focus. An extra step my muscle memory isn't prepared for! It seems like the sort of thing that might be an option rather than a bug, but if so, changing this behaviour back to its previous default is not at all obvious (I haven't found a way). So guessing it is a bug. NB: After launching an app this way, *no* window has focus. It is lost by the app that had it before, but not given to the newly started app. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.31.90-1ubuntu1 ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20 Uname: Linux 4.19.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Feb 27 15:53:07 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-09-11 (169 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) SourcePackage: gnome-shell UpgradeStatus: Upgraded to disco on 2019-01-13 (44 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1817924/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1817924] Re: apps launched from gnome shell do not get input focus
sublime text, slack also immune, firefox, thunderbird are not... so ok it's not universal but *lots* of apps are affected, and the pattern doesn't seem to be gnome/not-gnome. -- 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/1817924 Title: apps launched from gnome shell do not get input focus Status in gnome-shell package in Ubuntu: Incomplete Bug description: Observed on upgrading to disco-proposed today... When launching an app from the dock or from the applications grid (so i believe it's a gnome-shell thing rather than a dock thing), the app opens, but does not get the input focus. You have to either click in the window, or clicking again on the icon of the running app in the dock works, to give it focus. An extra step my muscle memory isn't prepared for! It seems like the sort of thing that might be an option rather than a bug, but if so, changing this behaviour back to its previous default is not at all obvious (I haven't found a way). So guessing it is a bug. NB: After launching an app this way, *no* window has focus. It is lost by the app that had it before, but not given to the newly started app. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.31.90-1ubuntu1 ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20 Uname: Linux 4.19.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Feb 27 15:53:07 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-09-11 (169 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) SourcePackage: gnome-shell UpgradeStatus: Upgraded to disco on 2019-01-13 (44 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1817924/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1721319] Re: On-screen keyboard pops up with touchscreen even when physical keyboard present
** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Triaged ** Changed in: gnome-shell (Ubuntu) Assignee: Andrea Azzarone (azzar1) => (unassigned) ** Description changed: - Upstream bug: https://bugzilla.gnome.org/show_bug.cgi?id=742246 + Upstream bug: https://gitlab.gnome.org/GNOME/gnome-shell/issues/872 -- 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/1721319 Title: On-screen keyboard pops up with touchscreen even when physical keyboard present Status in GNOME Shell: Invalid Status in gnome-shell package in Ubuntu: Triaged Bug description: Upstream bug: https://gitlab.gnome.org/GNOME/gnome-shell/issues/872 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1721319/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1809685] Re: The evince application often freezes
Thanks for reporting this bug. Can you please attach a PDF file that causes this issue? ** Changed in: evince (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1809685 Title: The evince application often freezes Status in evince package in Ubuntu: Incomplete Bug description: Hi! The evince application (pdf document viewer) often freezes. Thanks. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: evince 3.28.4-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Dec 25 07:12:13 2018 InstallationDate: Installed on 2018-05-06 (232 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1809685/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1808344] Re: Various bugs printing pdf files
Please file a separate bug report for each bug and provide much more information than you have provided here. If possible please attach a PDF file with which we can reproduce the bug. ** Changed in: cups (Ubuntu) Status: New => Incomplete -- 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/1808344 Title: Various bugs printing pdf files Status in cups package in Ubuntu: Incomplete Bug description: I want to report multiple issues encountered so far on Ubuntu 18.10 regarding printing PDF files. My configuration: - Computer: Dell XPS 15 9530 - OS: Ubuntu 18.10 - Printer: Samsung M2825ND Xpress Mono Laser Printer - PDF Readers Tested: Various (Evince, Foxit, Okular) - PDF Creator Tested: Word, LibreOffice, GhostScript, PDFTex, Acrobat PDFMaker, ... - PDF Sizes Tested: Various - PDF Versions Tested: Various Issues: - Printing 1 page per physical page encounter a lot problems while printing 2 pages per physical page produces issues less often - Sometimes playing around with print setting (such as scaling, centering) solves the issue sometimes it creates it and sometimes does nothing - Printing calc file directly from LibreOffice is not possible Error: - PCL-6 error (don't remember the exact code right now but can provide it if needed) Notes: - My guess is that this is an error related to the printer drivers but since I don't have another printer to test on can't verify. - Another guess is that the PDF produces PDF that use feature that are not properly handled on linux - Turning Markdown text to PDF using PDFlatex causes a printing error whereas turning the same Markdown to html and printing through Chrome causes no issue - If you need more logs please instruct me what I need to to help ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: cups 2.2.8-5ubuntu1.1 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Dec 13 13:35:13 2018 InstallationDate: Installed on 2018-09-21 (82 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180920) Lpstat: device for M262x-282x: usb://Samsung/M262x%20282x%20Series?serial=ZD2JBJCF6000LMA device for MG3500-series: usb://Canon/MG3500%20series?serial=68152B=1 MachineType: Dell Inc. XPS 15 9530 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/M262x-282x.ppd', '/etc/cups/ppd/MG3500-series.ppd'] failed with exit code 2: grep: /etc/cups/ppd/M262x-282x.ppd: Permission denied grep: /etc/cups/ppd/MG3500-series.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic root=UUID=41f390ce-33d0-4b6a-96a1-fef284448f69 ro quiet splash vt.handoff=1 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/29/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: XPS 15 9530 dmi.board.vendor: Dell Inc. dmi.board.version: A10 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA10:bd01/29/2018:svnDellInc.:pnXPS159530:pvrA10:rvnDellInc.:rnXPS159530:rvrA10:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: XPS 15 9530 dmi.product.sku: XPS 15 9530 dmi.product.version: A10 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1808344/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1506612] Re: pdfimages extracts black rectangles instead of the images
** Tags added: raring xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1506612 Title: pdfimages extracts black rectangles instead of the images Status in poppler package in Ubuntu: Confirmed Bug description: When I run pdfimages -f 1 -l 1 -png Z.pdf z-pdfimages, I get 5 images, two of which are black rectangles. If I run pdftocairo -png Z.pdf z-pdftocairo, I get one image that looks correct. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: poppler-utils 0.30.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-31.36-generic 3.19.8-ckt7 Uname: Linux 3.19.0-31-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1.5 Architecture: amd64 CurrentDesktop: Unity Date: Thu Oct 15 12:36:10 2015 InstallationDate: Installed on 2013-05-02 (896 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: poppler UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1506612/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1791417] Re: Sound bug ubuntu 18.04
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Thanks! ** Changed in: alsa-driver (Ubuntu) Importance: Undecided => Low ** Changed in: alsa-driver (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1791417 Title: Sound bug ubuntu 18.04 Status in alsa-driver package in Ubuntu: Incomplete Bug description: wget -O alsa-info.sh http://www.alsa-project.org/alsa-info.sh && chmod +x ./alsa-info.sh && ./alsa-info.sh --2018-09-07 12:24:00-- http://www.alsa-project.org/alsa-info.sh Resolving www.alsa-project.org (www.alsa-project.org)... 77.48.224.243 Connecting to www.alsa-project.org (www.alsa-project.org)|77.48.224.243|:80... connected. HTTP request sent, awaiting response... 302 Found Location: http://git.alsa-project.org/?p=alsa-utils.git;a=blob_plain;f=alsa-info/alsa-info.sh [following] --2018-09-07 12:24:00-- http://git.alsa-project.org/?p=alsa-utils.git;a=blob_plain;f=alsa-info/alsa-info.sh Resolving git.alsa-project.org (git.alsa-project.org)... 77.48.224.243 Connecting to git.alsa-project.org (git.alsa-project.org)|77.48.224.243|:80... connected. HTTP request sent, awaiting response... 200 OK Length: unspecified [application/x-sh] Saving to: ‘alsa-info.sh’ alsa-info.sh[ <=> ] 28.03K 170KB/sin 0.2s 2018-09-07 12:24:01 (170 KB/s) - ‘alsa-info.sh’ saved [28707] ALSA Information Script v 0.4.64 This script visits the following commands/files to collect diagnostic information about your ALSA installation and sound related hardware. dmesg lspci lsmod aplay amixer alsactl /proc/asound/ /sys/class/sound/ ~/.asoundrc (etc.) See './alsa-info.sh --help' for command line options. Automatically upload ALSA information to www.alsa-project.org? [y/N] : y Uploading information to www.alsa-project.org ... Done! Your ALSA information is located at http://www.alsa- project.org/db/?f=84ba91e70cc537608d8ffa04c5ec05a08bcf1ed6 Please inform the person helping you. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1791417/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1795421] Re: [cosmic] sidebar requires scrolling
Was fixed https://launchpad.net/ubuntu/+source/gnome-control- center/1:3.30.2-4ubuntu2 ** Changed in: gnome-control-center (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1795421 Title: [cosmic] sidebar requires scrolling Status in gnome-control-center package in Ubuntu: Fix Released Status in yaru-theme package in Ubuntu: New Bug description: In Ubuntu 18.10, the sidebar in GNOME Settings doesn't show the final item Details without scrolling. This issue affects the Yaru and Adwaita themes but Ambiance is not affected (because of slightly different element sizing there). Therefore, this issue is basically new to 18.10 for default Ubuntu users. This has been an upstream bug since the GNOME Settings redesign (introduction of sidebar) but we might want to handle this for Ubuntu 18.10 ourselves. https://gitlab.gnome.org/GNOME/gnome-control-center/issues/83 Because gnome-control-center 3.30 now hides panels like Wi-Fi if the computer does not have that hardware, this bug may not be reproducible on those computers. If we made the window taller, I don't think it would be much of a problem if there was extra space at the bottom of the sidebar for those users. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1795421/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1817924] Re: apps launched from gnome shell do not get input focus
Not confirming here, with gedit added to the launcher, click on gedit, wait for the editor to open and typing does correctly input in the text widget -- 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/1817924 Title: apps launched from gnome shell do not get input focus Status in gnome-shell package in Ubuntu: Incomplete Bug description: Observed on upgrading to disco-proposed today... When launching an app from the dock or from the applications grid (so i believe it's a gnome-shell thing rather than a dock thing), the app opens, but does not get the input focus. You have to either click in the window, or clicking again on the icon of the running app in the dock works, to give it focus. An extra step my muscle memory isn't prepared for! It seems like the sort of thing that might be an option rather than a bug, but if so, changing this behaviour back to its previous default is not at all obvious (I haven't found a way). So guessing it is a bug. NB: After launching an app this way, *no* window has focus. It is lost by the app that had it before, but not given to the newly started app. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.31.90-1ubuntu1 ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20 Uname: Linux 4.19.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Feb 27 15:53:07 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-09-11 (169 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) SourcePackage: gnome-shell UpgradeStatus: Upgraded to disco on 2019-01-13 (44 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1817924/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1815889] Re: qemu-system-x86_64 crashed with signal 31 in __pthread_setaffinity_new()
Adding Timo who maintainers mesa. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1815889 Title: qemu-system-x86_64 crashed with signal 31 in __pthread_setaffinity_new() Status in Mesa: Unknown Status in QEMU: New Status in mesa package in Ubuntu: New Status in qemu package in Ubuntu: Triaged Bug description: Unable to launch Default Fedora 29 images in gnome-boxes ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: qemu-system-x86 1:3.1+dfsg-2ubuntu1 ProcVersionSignature: Ubuntu 4.19.0-12.13-generic 4.19.18 Uname: Linux 4.19.0-12-generic x86_64 ApportVersion: 2.20.10-0ubuntu20 Architecture: amd64 Date: Thu Feb 14 11:00:45 2019 ExecutablePath: /usr/bin/qemu-system-x86_64 KvmCmdLine: COMMAND STAT EUID RUID PID PPID %CPU COMMAND MachineType: Dell Inc. Precision T3610 ProcEnviron: PATH=(custom, user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.19.0-12-generic root=UUID=939b509b-d627-4642-a655-979b44972d17 ro splash quiet vt.handoff=1 Signal: 31 SourcePackage: qemu StacktraceTop: __pthread_setaffinity_new (th=, cpusetsize=128, cpuset=0x7f5771fbf680) at ../sysdeps/unix/sysv/linux/pthread_setaffinity.c:34 () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so start_thread (arg=) at pthread_create.c:486 clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Title: qemu-system-x86_64 crashed with signal 31 in __pthread_setaffinity_new() UpgradeStatus: Upgraded to disco on 2018-11-14 (91 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo video dmi.bios.date: 11/14/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A18 dmi.board.name: 09M8Y8 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA18:bd11/14/2018:svnDellInc.:pnPrecisionT3610:pvr00:rvnDellInc.:rn09M8Y8:rvrA01:cvnDellInc.:ct7:cvr: dmi.product.name: Precision T3610 dmi.product.sku: 05D2 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1815889/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1116513] Re: /usr/lib/cups/filter/pdftops failed
Official support for the desktop editions of Ubuntu 12.04 and Ubuntu 13.10 has ended. If this bug is still occurring on Ubuntu 18.04 "Bionic Beaver" please run ubuntu-bug to gather a fresh set of system information and please upload a new crash report. ** Changed in: poppler (Ubuntu) Status: Triaged => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1116513 Title: /usr/lib/cups/filter/pdftops failed Status in poppler package in Ubuntu: Invalid Bug description: ubuntu-bug /var/crash/_usr_bin_pdftops.7.crash won't load the crash report. Here is the copy of the beginning of the crash file. It appears that it caused by SIGFPE Floating Point exception. and the root cause is an uninitialized variable leading to a division by zero in poppler-tools. ProblemType: Crash Architecture: i386 CrashCounter: 1 Date: Tue Feb 5 11:39:24 2013 DistroRelease: Ubuntu 12.04 ExecutablePath: /usr/bin/pdftops ExecutableTimestamp: 1343381837 ProcCmdline: pdftops -level2 -origpagesizes -r 300 /tmp/00f4c511a5f16 - ProcCwd: / ProcEnviron: PATH=(custom, no user) LANG=en_CA.UTF-8 ProcMaps: ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: cups 1.5.3-0ubuntu6 ProcVersionSignature: Ubuntu 3.2.0-37.58-generic 3.2.35 Uname: Linux 3.2.0-37-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu17.1 Architecture: i386 CurrentDmesg: [ 44.042521] agpgart-intel :00:00.0: putting AGP V3 device into 8x mode [ 44.042564] nvidia :01:00.0: putting AGP V3 device into 8x mode [ 45.599391] init: plymouth-stop pre-start process (1257) terminated with status 1 [ 52.912013] eth0: no IPv6 routers present Date: Tue Feb 5 13:07:10 2013 InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release i386 (20100816.1) Lpstat: device for hp_color_LaserJet_5550: hp:/net/hp_color_LaserJet_5550?zc=Electrical MachineType: Dell Computer Corporation Dimension 4600 MarkForUpload: True Papersize: letter PpdFiles: hp_color_LaserJet_5550: HP Color LaserJet 5550 v3010.107 Postscript (recommended) ProcEnviron: PATH=(custom, no user) LANG=en_CA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-37-generic root=UUID=adff9268-f105-4bd3-aeb2-11be7b02eb8e ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: Upgraded to precise on 2013-01-22 (13 days ago) dmi.bios.date: 07/21/2003 dmi.bios.vendor: Dell Computer Corporation dmi.bios.version: A03 dmi.board.name: 02Y832 dmi.board.vendor: Dell Computer Corp. dmi.chassis.type: 6 dmi.chassis.vendor: Dell Computer Corporation dmi.modalias: dmi:bvnDellComputerCorporation:bvrA03:bd07/21/2003:svnDellComputerCorporation:pnDimension4600:pvr:rvnDellComputerCorp.:rn02Y832:rvr:cvnDellComputerCorporation:ct6:cvr: dmi.product.name: Dimension 4600 dmi.sys.vendor: Dell Computer Corporation mtime.conffile..etc.cups.cupsd.conf: 2013-01-31T16:58:59.450493 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1116513/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1815579] Re: Broken dependencies with nvidia-driver-390 and xserver-xorg-hwe-18.04 in bionic
** Changed in: nvidia-graphics-drivers-340 (Ubuntu) Status: Triaged => Invalid ** Changed in: nvidia-graphics-drivers-390 (Ubuntu) Status: Triaged => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1815579 Title: Broken dependencies with nvidia-driver-390 and xserver-xorg-hwe-18.04 in bionic Status in nvidia-graphics-drivers-340 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-390 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-340 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-390 source package in Bionic: Fix Released Bug description: I am trying to test new HWE stack from 18.10 in my destkop Ubuntu 18.04.1 (expected release 18.04.2 this week) and I have broken dependencies when installing `xserver-xorg-hwe-18.04` package with NVidia drivers: me@me-H110M-DS2:~$ sudo apt install xserver-xorg-hwe-18.04 xserver-xorg-video-nvidia-390 Reading package lists... Done Building dependency tree Reading state information... Done xserver-xorg-video-nvidia-390 is already the newest version (390.77-0ubuntu0.18.04.1). xserver-xorg-video-nvidia-390 set to manually installed. Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: xserver-xorg-hwe-18.04 : Depends: xserver-xorg-core-hwe-18.04 (>= 2:1.17.2-2) but it is not going to be installed Conflicts: xserver-xorg-core (>= 0~) Recommends: xserver-xorg-video-all-hwe-18.04 but it is not going to be installed E: Unable to correct problems, you have held broken packages. Otherwise, if I try to install it without `xserver-xorg-video-nvidia-390` this happens: me@me-H110M-DS2:~$ sudo apt install xserver-xorg-hwe-18.04 Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: dkms libbsd0:i386 libdrm-amdgpu1:i386 libdrm-intel1:i386 libdrm-nouveau2:i386 libdrm-radeon1:i386 libdrm2:i386 libedit2:i386 libelf1:i386 libexpat1:i386 libffi6:i386 libgl1:i386 libgl1-mesa-dri:i386 libglapi-mesa:i386 libglvnd0:i386 libglx-mesa0:i386 libglx0:i386 libllvm7:i386 libnvidia-cfg1-390 libnvidia-common-390 libnvidia-compute-390 libnvidia-compute-390:i386 libnvidia-decode-390 libnvidia-decode-390:i386 libnvidia-encode-390 libnvidia-encode-390:i386 libnvidia-fbc1-390 libnvidia-fbc1-390:i386 libnvidia-gl-390 libnvidia-gl-390:i386 libnvidia-ifr1-390 libnvidia-ifr1-390:i386 libpciaccess0:i386 libsensors4:i386 libstdc++6:i386 libvdpau1 libwayland-client0:i386 libwayland-server0:i386 libx11-6:i386 libx11-xcb1:i386 libxau6:i386 libxcb-dri2-0:i386 libxcb-dri3-0:i386 libxcb-glx0:i386 libxcb-present0:i386 libxcb-sync1:i386 libxcb1:i386 libxdamage1:i386 libxdmcp6:i386 libxext6:i386 libxfixes3:i386 libxnvctrl0 libxshmfence1:i386 libxxf86vm1:i386 mesa-vdpau-drivers nvidia-compute-utils-390 nvidia-dkms-390 nvidia-kernel-common-390 nvidia-kernel-source-390 nvidia-prime nvidia-settings nvidia-utils-390 pkg-config screen-resolution-extra vdpau-driver-all Use 'sudo apt autoremove' to remove them. The following additional packages will be installed: xserver-xorg-core-hwe-18.04 xserver-xorg-input-all-hwe-18.04 xserver-xorg-input-libinput-hwe-18.04 xserver-xorg-video-all-hwe-18.04 xserver-xorg-video-amdgpu-hwe-18.04 xserver-xorg-video-ati-hwe-18.04 xserver-xorg-video-fbdev-hwe-18.04 xserver-xorg-video-intel-hwe-18.04 xserver-xorg-video-nouveau-hwe-18.04 xserver-xorg-video-qxl-hwe-18.04 xserver-xorg-video-radeon-hwe-18.04 xserver-xorg-video-vesa-hwe-18.04 xserver-xorg-video-vmware-hwe-18.04 Suggested packages: xfonts-100dpi | xfonts-75dpi firmware-amd-graphics xserver-xorg-video-r128 xserver-xorg-video-mach64 firmware-misc-nonfree Recommended packages: xserver-xorg-input-wacom-hwe-18.04 The following packages will be REMOVED: nvidia-driver-390 xserver-xorg xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-libinput xserver-xorg-video-nvidia-390 The following NEW packages will be installed: xserver-xorg-core-hwe-18.04 xserver-xorg-hwe-18.04 xserver-xorg-input-all-hwe-18.04 xserver-xorg-input-libinput-hwe-18.04 xserver-xorg-video-all-hwe-18.04 xserver-xorg-video-amdgpu-hwe-18.04 xserver-xorg-video-ati-hwe-18.04 xserver-xorg-video-fbdev-hwe-18.04 xserver-xorg-video-intel-hwe-18.04 xserver-xorg-video-nouveau-hwe-18.04 xserver-xorg-video-qxl-hwe-18.04 xserver-xorg-video-radeon-hwe-18.04
[Desktop-packages] [Bug 1815889] Re: qemu-system-x86_64 crashed with signal 31 in __pthread_setaffinity_new()
@Ubuntu-Desktop Team (now subscribed) - is there a chance we can revert [1] in mesa before it will be released with Disco for now. That would be needed until an accepted solution throughout the stack of libvirt/qemu/mesa is found? Otherwise using GL backed qemu graphics will fail as outlined in the bug. Once such a cross-package solution to the problem is found we can (if needed at all) SRU back the set of changes to all components required. [1]: https://github.com/mesa3d/mesa/commit/d877451b48a59ab0f9a4210fc736f51da5851c9a -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1815889 Title: qemu-system-x86_64 crashed with signal 31 in __pthread_setaffinity_new() Status in Mesa: Unknown Status in QEMU: New Status in mesa package in Ubuntu: New Status in qemu package in Ubuntu: Triaged Bug description: Unable to launch Default Fedora 29 images in gnome-boxes ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: qemu-system-x86 1:3.1+dfsg-2ubuntu1 ProcVersionSignature: Ubuntu 4.19.0-12.13-generic 4.19.18 Uname: Linux 4.19.0-12-generic x86_64 ApportVersion: 2.20.10-0ubuntu20 Architecture: amd64 Date: Thu Feb 14 11:00:45 2019 ExecutablePath: /usr/bin/qemu-system-x86_64 KvmCmdLine: COMMAND STAT EUID RUID PID PPID %CPU COMMAND MachineType: Dell Inc. Precision T3610 ProcEnviron: PATH=(custom, user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.19.0-12-generic root=UUID=939b509b-d627-4642-a655-979b44972d17 ro splash quiet vt.handoff=1 Signal: 31 SourcePackage: qemu StacktraceTop: __pthread_setaffinity_new (th=, cpusetsize=128, cpuset=0x7f5771fbf680) at ../sysdeps/unix/sysv/linux/pthread_setaffinity.c:34 () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so start_thread (arg=) at pthread_create.c:486 clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Title: qemu-system-x86_64 crashed with signal 31 in __pthread_setaffinity_new() UpgradeStatus: Upgraded to disco on 2018-11-14 (91 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo video dmi.bios.date: 11/14/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A18 dmi.board.name: 09M8Y8 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA18:bd11/14/2018:svnDellInc.:pnPrecisionT3610:pvr00:rvnDellInc.:rn09M8Y8:rvrA01:cvnDellInc.:ct7:cvr: dmi.product.name: Precision T3610 dmi.product.sku: 05D2 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1815889/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1815889] Re: qemu-system-x86_64 crashed with signal 31 in __pthread_setaffinity_new()
Thanks Daniel and MarcAndre for chiming in here. Atfer thinking more about it I agree to Daniel that actually mesa should honor and stick with its affinity assignment. For documentation purpose: the solution proposed on the ML is at https://lists.freedesktop.org/archives/mesa-dev/2019-February/215926.html I also added a bug tracker to the fredesktop bug as task. ** Also affects: mesa (Ubuntu) Importance: Undecided Status: New ** Also affects: mesa via https://bugs.freedesktop.org/show_bug.cgi?id=109695 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1815889 Title: qemu-system-x86_64 crashed with signal 31 in __pthread_setaffinity_new() Status in Mesa: Unknown Status in QEMU: New Status in mesa package in Ubuntu: New Status in qemu package in Ubuntu: Triaged Bug description: Unable to launch Default Fedora 29 images in gnome-boxes ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: qemu-system-x86 1:3.1+dfsg-2ubuntu1 ProcVersionSignature: Ubuntu 4.19.0-12.13-generic 4.19.18 Uname: Linux 4.19.0-12-generic x86_64 ApportVersion: 2.20.10-0ubuntu20 Architecture: amd64 Date: Thu Feb 14 11:00:45 2019 ExecutablePath: /usr/bin/qemu-system-x86_64 KvmCmdLine: COMMAND STAT EUID RUID PID PPID %CPU COMMAND MachineType: Dell Inc. Precision T3610 ProcEnviron: PATH=(custom, user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.19.0-12-generic root=UUID=939b509b-d627-4642-a655-979b44972d17 ro splash quiet vt.handoff=1 Signal: 31 SourcePackage: qemu StacktraceTop: __pthread_setaffinity_new (th=, cpusetsize=128, cpuset=0x7f5771fbf680) at ../sysdeps/unix/sysv/linux/pthread_setaffinity.c:34 () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so start_thread (arg=) at pthread_create.c:486 clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Title: qemu-system-x86_64 crashed with signal 31 in __pthread_setaffinity_new() UpgradeStatus: Upgraded to disco on 2018-11-14 (91 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo video dmi.bios.date: 11/14/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A18 dmi.board.name: 09M8Y8 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA18:bd11/14/2018:svnDellInc.:pnPrecisionT3610:pvr00:rvnDellInc.:rn09M8Y8:rvrA01:cvnDellInc.:ct7:cvr: dmi.product.name: Precision T3610 dmi.product.sku: 05D2 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1815889/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 823155]
(In reply to Buovjaga from comment #46) > (In reply to Mark Hung from comment #45) > > I didn't check how the original test file play. The file path is > > share/gallery/sounds/apert.wav in LibreOffice installation directory. It's > > about one second, may be cut off because of the effect duration. > > I tested from scratch with different sounds, all behave the same. Well ... I also found that. It seems that my solution didn't fixed the issue completely. Let us track with another new issue. -- 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/823155 Title: [Upstream] Impress Custom Animation Sound Effect not audible in Slide Show Status in LibreOffice: Fix Released Status in OpenOffice: Unknown Status in libreoffice package in Ubuntu: Triaged Status in openoffice.org package in Ubuntu: Won't Fix Bug description: 1) lsb_release -rd Description: Ubuntu 12.04 LTS Release: 12.04 2) apt-cache policy libreoffice-impress libreoffice-impress: Installed: 1:3.5.2-2ubuntu1 Candidate: 1:3.5.2-2ubuntu1 Version table: *** 1:3.5.2-2ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ precise/main i386 Packages 100 /var/lib/dpkg/status 3) What is expected to happen in a new Impress document via the Terminal: loimpress --nologo New Impress file -> click the rectangle containing "Click to add text" -> Under Tasks Custom Animation -> button Add... -> Entrance tab highlight Random Effects -> OK button -> right of Property ... button -> Effect tab -> change Sound dropdown apert -> OK button -> Slide Show and it plays the apert sound. 4) What happens instead is no sound is played during the slide show. Original Reporter Comments: I am using Ubuntu 11.04 Natty. I have tested this in Ubuntu 10.10 with OpenOffice.org presentation (Impress), same problem too. All in all I have tried this on 3 different computers. 2 on 11.04 and 1 on 10.10 ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: libreoffice 1:3.3.2-1ubuntu5 ProcVersionSignature: Ubuntu 2.6.38-10.46-generic 2.6.38.7 Uname: Linux 2.6.38-10-generic i686 Architecture: i386 Date: Tue Aug 9 16:59:45 2011 InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1) ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/823155/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1721319] Re: On-screen keyboard pops up with touchscreen even when physical keyboard present
** Changed in: gnome-shell Status: Confirmed => 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/1721319 Title: On-screen keyboard pops up with touchscreen even when physical keyboard present Status in GNOME Shell: Invalid Status in gnome-shell package in Ubuntu: Incomplete Bug description: Upstream bug: https://bugzilla.gnome.org/show_bug.cgi?id=742246 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1721319/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1784488] Re: libwacom touch strip mappings are reversed for cintiq 21ux
you should file this upstream https://github.com/linuxwacom/libwacom/issues -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libwacom in Ubuntu. https://bugs.launchpad.net/bugs/1784488 Title: libwacom touch strip mappings are reversed for cintiq 21ux Status in libwacom package in Ubuntu: New Bug description: In the location libwacom/ the file 'cintiq-21ux2.tablet' has the wrong button mapping for the touch strips. This error causes the LED lights/touch strip modes to correspond to the buttons on the opposite sides of the cintiq, rather than their correct groupings. The Cintiq has 4 LED lights that represent 4 different modes that a center button toggles between. There is one center button and 4 LEDs on each side of the Cintiq that correspond to a touch-strip. The expected action is that by pressing the center button, it would change the button mappings of the touch-strip located directly behind the center button. The Leds would reflect this change by lighting up a different led. Continued presses would toggle between the 4 LEDs/modes. What is happening is the button toggle is not changing the mappings of the touch-strip directly behind it, instead it's changing the button mappings for touch-strip on the other side of the Cintiq. At the end of the file, you will see : 'Touchstrip=A' and 'Touchstrip2=J' These should be corrected as 'Touchstrip=J' and 'Touchstrip2=A'. After correcting my file, the button mapping in Wacom Tablet works correctly. I believe this issue is a kernal one, but the problem can be solved by simply changing the file that libwacom has. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libwacom/+bug/1784488/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1767993] Re: Lubuntu: X11 freezing/low resolution on N3150 intel graphics
Still broken despite upgrading kernel to 4.15.0-46.49 grub to 2.02-2ubuntu8.12 mesa to 18.2.8-0ubuntu0~18.04.2 The recent mesa changelog gave hope:- "i965-revert-enabling-softpin.diff: Don't enable softpin, causes issues on 32bit installs. (LP: #1815172)" but no improvement noted and GPU still hanging at the login screen. Perhaps installing i386 was a mistake? -- 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/1767993 Title: Lubuntu: X11 freezing/low resolution on N3150 intel graphics Status in xorg-server package in Ubuntu: Confirmed Bug description: Hi, I just installed a fresh 18.04 on an ASRock beebox N3150 machine. The regular ubuntu desktop installer hanged after entering X11 mode, machine froze. I then used Lubuntu alternate installer with the console based installation, which worked without any problem. But after rebooting the system again hung after the graphical login prompt. I then changed the boot options in /etc/default/grub to give the kernel the options nosplash nomodeset and to leave the system in console mode (I had similar experiences with former ubuntu versions on that machine where X11 did not start when the mode had been set by console.) Now X11 works, but comes up in vesa mode (1024x768) only. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xserver-xorg-core 2:1.19.6-1ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: LXDE Date: Mon Apr 30 12:25:09 2018 InstallationDate: Installed on 2018-04-30 (0 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: xorg-server UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1767993/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1796549] Re: Xorg sessions have higher output lag than Wayland sessions
** Changed in: mutter (Ubuntu) Milestone: None => ubuntu-19.03 -- 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/1796549 Title: Xorg sessions have higher output lag than Wayland sessions Status in mutter package in Ubuntu: In Progress Bug description: https://gitlab.gnome.org/GNOME/mutter/issues/334 --- Xorg sessions have higher output lag than Wayland sessions. Test case: Grab a window with the mouse and drag it around smoothly. Expected: the same minimal gap between the cursor and the window's title bar in both Xorg and Wayland sessions. Observed: a bigger gap (higher latency) in Xorg sessions. I only realized this was a bug when I stumbled on a fix while experimenting with the presentation timing logic in mutter, so assigning to myself. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: mutter 3.30.0-4 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 Date: Sun Oct 7 17:22:48 2018 InstallationDate: Installed on 2018-05-26 (133 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180525) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1796549/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1817924] Re: apps launched from gnome shell do not get input focus
FYI problem remains with all those extensions removed. BTW one does tend to notice it most with apps you type into. I first noticed with terminal, where I'm used to click, then start typing, and it's suddenly become click, click-again, then start typing. With an app you'd tend first to click into anyway, you're more likely to not notice it as the first click in an unfocused window is passed in. (Along the way, minor invisible-to-user bug in that the setting org.gnome.shell.enabled-extensions retains entries for extensions that have been removed. Noticed first because I already didn't have dash-to- dock installed, but did until recently - when without -proposed enabled, the ubuntu dock extension stopped working (works again with -proposed enabled, i think the latest non-proposed version of ubuntu-dock secretly depends on the proposed gnome shell). Confirmed as all those listed extensions remained in that setting after removing all of them. I've just reset it to default value, empty array.) -- 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/1817924 Title: apps launched from gnome shell do not get input focus Status in gnome-shell package in Ubuntu: Incomplete Bug description: Observed on upgrading to disco-proposed today... When launching an app from the dock or from the applications grid (so i believe it's a gnome-shell thing rather than a dock thing), the app opens, but does not get the input focus. You have to either click in the window, or clicking again on the icon of the running app in the dock works, to give it focus. An extra step my muscle memory isn't prepared for! It seems like the sort of thing that might be an option rather than a bug, but if so, changing this behaviour back to its previous default is not at all obvious (I haven't found a way). So guessing it is a bug. NB: After launching an app this way, *no* window has focus. It is lost by the app that had it before, but not given to the newly started app. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.31.90-1ubuntu1 ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20 Uname: Linux 4.19.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Feb 27 15:53:07 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-09-11 (169 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) SourcePackage: gnome-shell UpgradeStatus: Upgraded to disco on 2019-01-13 (44 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1817924/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
