[Desktop-packages] [Bug 1763263] Re: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from oth
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1763263 Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of package libsane1:i386 Status in sane-backends package in Ubuntu: New Bug description: bug at the beginning of setup ProblemType: Package DistroRelease: Ubuntu 17.10 Package: libsane1 1.0.27-1~experimental2ubuntu2.1 ProcVersionSignature: Ubuntu 4.13.0-38.43-generic 4.13.16 Uname: Linux 4.13.0-38-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 Date: Wed Apr 11 17:43:35 2018 DuplicateSignature: package:libsane1:1.0.27-1~experimental2ubuntu2.1 Unpacking libsane1:i386 (1.0.27-1~experimental2ubuntu2.1) ... dpkg: error processing archive /tmp/apt-dpkg-install-U4Z7ZQ/62-libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb (--unpack): trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of package libsane1:i386 ErrorMessage: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of package libsane1:i386 InstallationDate: Installed on 2018-03-06 (36 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5.1 SourcePackage: sane-backends Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of package libsane1:i386 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1763263/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1763263] [NEW] package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from o
Public bug reported: bug at the beginning of setup ProblemType: Package DistroRelease: Ubuntu 17.10 Package: libsane1 1.0.27-1~experimental2ubuntu2.1 ProcVersionSignature: Ubuntu 4.13.0-38.43-generic 4.13.16 Uname: Linux 4.13.0-38-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 Date: Wed Apr 11 17:43:35 2018 DuplicateSignature: package:libsane1:1.0.27-1~experimental2ubuntu2.1 Unpacking libsane1:i386 (1.0.27-1~experimental2ubuntu2.1) ... dpkg: error processing archive /tmp/apt-dpkg-install-U4Z7ZQ/62-libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb (--unpack): trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of package libsane1:i386 ErrorMessage: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of package libsane1:i386 InstallationDate: Installed on 2018-03-06 (36 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5.1 SourcePackage: sane-backends Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of package libsane1:i386 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: sane-backends (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package artful package-conflict -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1763263 Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of package libsane1:i386 Status in sane-backends package in Ubuntu: New Bug description: bug at the beginning of setup ProblemType: Package DistroRelease: Ubuntu 17.10 Package: libsane1 1.0.27-1~experimental2ubuntu2.1 ProcVersionSignature: Ubuntu 4.13.0-38.43-generic 4.13.16 Uname: Linux 4.13.0-38-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 Date: Wed Apr 11 17:43:35 2018 DuplicateSignature: package:libsane1:1.0.27-1~experimental2ubuntu2.1 Unpacking libsane1:i386 (1.0.27-1~experimental2ubuntu2.1) ... dpkg: error processing archive /tmp/apt-dpkg-install-U4Z7ZQ/62-libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb (--unpack): trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of package libsane1:i386 ErrorMessage: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of package libsane1:i386 InstallationDate: Installed on 2018-03-06 (36 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5.1 SourcePackage: sane-backends Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of package libsane1:i386 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1763263/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1763258] Re: gnome-control-center crashed with SIGSEGV in g_main_context_dispatch()
*** This bug is a duplicate of bug 1754924 *** https://bugs.launchpad.net/bugs/1754924 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1754924, so 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. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1763258/+attachment/5111654/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1763258/+attachment/5111656/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1763258/+attachment/5111659/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1763258/+attachment/5111660/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1763258/+attachment/5111661/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1763258/+attachment/5111662/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1763258/+attachment/5111663/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1754924 gnome-control-center crashed with SIGSEGV in actualize_printers_list() ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- 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/1763258 Title: gnome-control-center crashed with SIGSEGV in g_main_context_dispatch() Status in gnome-control-center package in Ubuntu: New Bug description: Was in the process of connecting my bluetooth headphones when the control center crashed. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1:3.28.0-0ubuntu6 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 11 21:22:27 2018 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2018-04-02 (10 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) ProcCmdline: gnome-control-center bluetooth ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x55e169c1a311:mov0x90(%rbp),%rsi PC (0x55e169c1a311) ok source "0x90(%rbp)" (0x0090) not located in a known VMA region (needed readable region)! destination "%rsi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: ?? () ?? () ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-control-center crashed with SIGSEGV in g_main_context_dispatch() UpgradeStatus: Upgraded to bionic on 2018-04-07 (4 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1763258/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1471501] Re: package libminiupnpc8 1.6-3ubuntu2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
[Expired for miniupnpc (Ubuntu) because there has been no activity for 60 days.] ** Changed in: miniupnpc (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to miniupnpc in Ubuntu. https://bugs.launchpad.net/bugs/1471501 Title: package libminiupnpc8 1.6-3ubuntu2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in miniupnpc package in Ubuntu: Expired Bug description: This bug also prevents a "shutdown" from the Action Buttons. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libminiupnpc8 1.6-3ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-24.47-lowlatency 3.13.9 Uname: Linux 3.13.0-24-lowlatency i686 ApportVersion: 2.14.1-0ubuntu3.11 AptOrdering: dkms: Purge libminiupnpc8: Configure Architecture: i386 Date: Sat Jul 4 21:37:36 2015 Dependencies: gcc-4.9-base 4.9.1-0ubuntu1 libc6 2.19-0ubuntu6.6 libgcc1 1:4.9.1-0ubuntu1 multiarch-support 2.19-0ubuntu6.6 DpkgTerminalLog: Removing dkms (2.2.0.3-1.1ubuntu5) ... Purging configuration files for dkms (2.2.0.3-1.1ubuntu5) ... dpkg: error processing package libminiupnpc8 (--configure): package is in a very bad inconsistent state; you should reinstall it before attempting configuration DuplicateSignature: package:libminiupnpc8:1.6-3ubuntu2:package is in a very bad inconsistent state; you should reinstall it before attempting configuration ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2015-07-05 (0 days ago) InstallationMedia: Ubuntu-Studio 14.04 LTS "Trusty Tahr" - Release i386 (20140416.3) SourcePackage: miniupnpc Title: package libminiupnpc8 1.6-3ubuntu2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/miniupnpc/+bug/1471501/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1747488] Re: [GeForce GTX 1080] 17.10.1 DisplayPort 15m cable no display after starting "EFI VGA"
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1747488 Title: [GeForce GTX 1080] 17.10.1 DisplayPort 15m cable no display after starting "EFI VGA" Status in linux package in Ubuntu: Expired Status in mesa package in Ubuntu: Expired Bug description: Ubuntu 17.10.1 boots into a black screen with no display, when switching into "EFI VGA" during boot up. Modifying the boot menu to run in "text" mode, shows the last line as below, before losing all monitor output: "Switching to EFI VGA" The 15m DisplayPort cable shouldn't be a problem, but using a DisplayPort-to-DVI adapter and a 1m DVI cable works PC Specs CPU : Intel Core i9-7900X 4.3GHz 10-Core MBO : ASRock X299 Taichi RAM : Corsair Vengeance 32GB GPU : EVGA GeForce GTX 1080 Ti 11GB FTW3 --- ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 17.10 EcryptfsInUse: Yes InstallationDate: Installed on 2018-02-05 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: gnome-shell 3.26.2-0ubuntu0.1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Tags: artful Uname: Linux 4.13.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: eric 2029 F pulseaudio /dev/snd/controlC1: eric 2029 F pulseaudio /dev/snd/pcmC0D0p: eric 2029 F...m pulseaudio /dev/snd/controlC0: eric 2029 F pulseaudio CurrentDesktop: GNOME DistUpgraded: Fresh install DistroCodename: artful DistroRelease: Ubuntu 17.10 DistroVariant: ubuntu EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=efed4438-d8f7-494f-bc1f-c5097c43bfff InstallationDate: Installed on 2018-02-05 (2 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: mesa (not installed) ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed root=UUID=e6bd0705-72b8-4f01-ba2f-15282ceafa55 ro text ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-32-generic N/A linux-backports-modules-4.13.0-32-generic N/A linux-firmware 1.169.3 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: yes Tags: artful ubuntu Uname: Linux 4.13.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/08/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.60 dmi.board.name: X299 Taichi dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.60:bd08/08/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX299Taichi:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~17.10.2 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~17.10.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1747488/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to
[Desktop-packages] [Bug 1695710] Re: package libminiupnpc10:amd64 1.9.20140610-2ubuntu2 failed to install/upgrade: package libminiupnpc10:amd64 is not ready for configuration cannot configure (current
[Expired for miniupnpc (Ubuntu) because there has been no activity for 60 days.] ** Changed in: miniupnpc (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to miniupnpc in Ubuntu. https://bugs.launchpad.net/bugs/1695710 Title: package libminiupnpc10:amd64 1.9.20140610-2ubuntu2 failed to install/upgrade: package libminiupnpc10:amd64 is not ready for configuration cannot configure (current status 'half-installed') Status in miniupnpc package in Ubuntu: Expired Bug description: . ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libminiupnpc10:amd64 1.9.20140610-2ubuntu2 ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11 Uname: Linux 4.8.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 Date: Sun Jun 4 10:48:50 2017 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu7 libgcc1 1:6.0.1-0ubuntu1 ErrorMessage: package libminiupnpc10:amd64 is not ready for configuration cannot configure (current status 'half-installed') InstallationDate: Installed on 2017-06-04 (0 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: miniupnpc Title: package libminiupnpc10:amd64 1.9.20140610-2ubuntu2 failed to install/upgrade: package libminiupnpc10:amd64 is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/miniupnpc/+bug/1695710/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1747488] Re: [GeForce GTX 1080] 17.10.1 DisplayPort 15m cable no display after starting "EFI VGA"
[Expired for mesa (Ubuntu) because there has been no activity for 60 days.] ** Changed in: mesa (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1747488 Title: [GeForce GTX 1080] 17.10.1 DisplayPort 15m cable no display after starting "EFI VGA" Status in linux package in Ubuntu: Expired Status in mesa package in Ubuntu: Expired Bug description: Ubuntu 17.10.1 boots into a black screen with no display, when switching into "EFI VGA" during boot up. Modifying the boot menu to run in "text" mode, shows the last line as below, before losing all monitor output: "Switching to EFI VGA" The 15m DisplayPort cable shouldn't be a problem, but using a DisplayPort-to-DVI adapter and a 1m DVI cable works PC Specs CPU : Intel Core i9-7900X 4.3GHz 10-Core MBO : ASRock X299 Taichi RAM : Corsair Vengeance 32GB GPU : EVGA GeForce GTX 1080 Ti 11GB FTW3 --- ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 17.10 EcryptfsInUse: Yes InstallationDate: Installed on 2018-02-05 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: gnome-shell 3.26.2-0ubuntu0.1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Tags: artful Uname: Linux 4.13.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: eric 2029 F pulseaudio /dev/snd/controlC1: eric 2029 F pulseaudio /dev/snd/pcmC0D0p: eric 2029 F...m pulseaudio /dev/snd/controlC0: eric 2029 F pulseaudio CurrentDesktop: GNOME DistUpgraded: Fresh install DistroCodename: artful DistroRelease: Ubuntu 17.10 DistroVariant: ubuntu EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=efed4438-d8f7-494f-bc1f-c5097c43bfff InstallationDate: Installed on 2018-02-05 (2 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: mesa (not installed) ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed root=UUID=e6bd0705-72b8-4f01-ba2f-15282ceafa55 ro text ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-32-generic N/A linux-backports-modules-4.13.0-32-generic N/A linux-firmware 1.169.3 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: yes Tags: artful ubuntu Uname: Linux 4.13.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/08/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.60 dmi.board.name: X299 Taichi dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.60:bd08/08/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX299Taichi:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~17.10.2 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~17.10.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1747488/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to
[Desktop-packages] [Bug 1763256] [NEW] The "update-interval" don't go beyond 100 secs and the app can crash
Public bug reported: Steps: 1 - Edit the range on the 'update-interval' key to a max over 100.00 seconds. 2 - Re-compile the schemas (glib-compile-schemas) 3 - Run gnome-system-monitor. 4 - Open the 'Preferences' window 5 - Click on the "+" button several times 6 - Verify that it won't be beyond "100.00". Also, if after following the above steps you use 'gsettings' or 'dconf- editor' to update the current value to a value above 100.00 secs you will see that the 'Preferences' window will keep the value '100.00' - please see the attached screenshot. Finally, during the tests the app crashed several times. At least in one of them I sent the automatic report. My environment: Distributor ID: Ubuntu Description:Ubuntu Bionic Beaver (development branch) Release:18.04 Codename: bionic Hardware: Memory: 7.7 GiB Processor: Intel Core i7-5600U CPY @ 2.60GHz x 4 Graphics: Intel HG Graphics 5500 (Broadwell GT2) OS type:64-bit Disk: 243.6 GB Please, let me know if you need more data or info. Thank you. ** Affects: gnome-system-monitor (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Screenshot-Several windows" https://bugs.launchpad.net/bugs/1763256/+attachment/5111653/+files/Screenshot%20from%202018-04-11%2021-09-11.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-system-monitor in Ubuntu. https://bugs.launchpad.net/bugs/1763256 Title: The "update-interval" don't go beyond 100 secs and the app can crash Status in gnome-system-monitor package in Ubuntu: New Bug description: Steps: 1 - Edit the range on the 'update-interval' key to a max over 100.00 seconds. 2 - Re-compile the schemas (glib-compile-schemas) 3 - Run gnome-system-monitor. 4 - Open the 'Preferences' window 5 - Click on the "+" button several times 6 - Verify that it won't be beyond "100.00". Also, if after following the above steps you use 'gsettings' or 'dconf-editor' to update the current value to a value above 100.00 secs you will see that the 'Preferences' window will keep the value '100.00' - please see the attached screenshot. Finally, during the tests the app crashed several times. At least in one of them I sent the automatic report. My environment: Distributor ID: Ubuntu Description: Ubuntu Bionic Beaver (development branch) Release: 18.04 Codename: bionic Hardware: Memory: 7.7 GiB Processor: Intel Core i7-5600U CPY @ 2.60GHz x 4 Graphics: Intel HG Graphics 5500 (Broadwell GT2) OS type:64-bit Disk: 243.6 GB Please, let me know if you need more data or info. Thank you. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1763256/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1763252] [NEW] cant launch
Public bug reported: IDK ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: evince 3.28.2-1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Apr 12 11:55:47 2018 InstallationDate: Installed on 2018-03-21 (21 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180319) SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: evince (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apparmor apport-bug bionic third-party-packages -- 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/1763252 Title: cant launch Status in evince package in Ubuntu: New Bug description: IDK ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: evince 3.28.2-1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Apr 12 11:55:47 2018 InstallationDate: Installed on 2018-03-21 (21 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180319) 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/1763252/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1763236] Re: file-roller crashed with SIGSEGV in g_cclosure_marshal_VOID__ENUMv()
*** This bug is a duplicate of bug 1760257 *** https://bugs.launchpad.net/bugs/1760257 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1760257, so 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. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1763236/+attachment/5111509/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1763236/+attachment/5111511/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1763236/+attachment/5111514/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1763236/+attachment/5111515/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1763236/+attachment/5111516/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1763236/+attachment/5111517/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1763236/+attachment/5111518/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1760257 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to file-roller in Ubuntu. https://bugs.launchpad.net/bugs/1763236 Title: file-roller crashed with SIGSEGV in g_cclosure_marshal_VOID__ENUMv() Status in file-roller package in Ubuntu: New Bug description: # ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: file-roller 3.16.5-0ubuntu1.2 ProcVersionSignature: Ubuntu 4.8.0-58.63~16.04.1-lowlatency 4.8.17 Uname: Linux 4.8.0-58-lowlatency x86_64 ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 CurrentDesktop: LXDE Date: Thu Apr 12 05:27:10 2018 ExecutablePath: /usr/bin/file-roller InstallationDate: Installed on 2012-05-25 (2147 days ago) InstallationMedia: Kubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120423) ProcCmdline: file-roller --extract /home/username/data/kerya4/kerya4/distrib/android-sdk_r20.0.3-linux.tgz ProcEnviron: LANGUAGE=ru_UA:ru PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_UA.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x449228: mov0x1e0(%rax),%rbp PC (0x00449228) ok source "0x1e0(%rax)" (0x01e0) not located in a known VMA region (needed readable region)! destination "%rbp" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: file-roller StacktraceTop: ?? () g_cclosure_marshal_VOID__ENUMv () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: file-roller crashed with SIGSEGV in g_cclosure_marshal_VOID__ENUMv() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom debian-tor dialout dip disk libvirtd lp lpadmin plugdev sambashare sudo vboxusers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1763236/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1763237] Re: gnome-shell crashed with signal 5 in g_log_default_handler()
*** This bug is a duplicate of bug 1748450 *** https://bugs.launchpad.net/bugs/1748450 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1748450, so 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. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1763237/+attachment/5111519/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1763237/+attachment/5111521/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1763237/+attachment/5111525/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1763237/+attachment/5111526/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1763237/+attachment/5111527/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1763237/+attachment/5111528/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1763237/+attachment/5111529/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1748450 gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_default_handler() from default_log_handler(message="Connection to xwayland lost") from g_logv() from g_log() from ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- 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/1763237 Title: gnome-shell crashed with signal 5 in g_log_default_handler() Status in gnome-shell package in Ubuntu: New Bug description: I just install ubuntu 18.04, probably the bug at principal log screen, or the icon of change bright freeze in the screen at changing bright ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.0-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME-Greeter:GNOME Date: Wed Apr 11 21:10:29 2018 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2018-04-11 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180403) ProcCmdline: /usr/bin/gnome-shell Signal: 5 SourcePackage: gnome-shell StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-shell crashed with signal 5 in g_log_default_handler() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1763237/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1536751] Re: Font/text rendering is irregular and not pixel-aligned on low DPI screens
** No longer affects: ubuntu-font-family-sources (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to harfbuzz in Ubuntu. https://bugs.launchpad.net/bugs/1536751 Title: Font/text rendering is irregular and not pixel-aligned on low DPI screens Status in Canonical System Image: Confirmed Status in fontconfig package in Ubuntu: Incomplete Status in freetype package in Ubuntu: Incomplete Status in harfbuzz package in Ubuntu: Confirmed Status in qtbase-opensource-src package in Ubuntu: Incomplete Status in qtdeclarative-opensource-src package in Ubuntu: New Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Confirmed Bug description: This is a Dell Vostro 3550 laptop with a fresh install of 16.04 and unity8 Mir session the version of qtdeclarative5-qtmir-plugin is 0.4.7+16.04.20160104-0ubuntu1 As you can see from the screenshots the text has low details and, in the case of indicators descriptions at the top, almost disappears. The text could be fixed by using Text.NativeRendering instead of Text.QtRendering for the QML labels on low dpi screens, although text doesn't seem to be the only issue here. The icons are definitely lacking detail as well (QML Image's smoothing is enabled maybe?). Also the dots of the infographic don't look like circles at all, they're missing pixels and many of them look like a C more than an O. It looks to me like something is setting the wrong resolution, because it looks quite bad. But the screenshots are 1366x768 so I think that's not the case. NOTE: Unity7 looks perfectly fine and detailed To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1536751/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1762427] Re: Snap install / remove failures aren't stopped in GNOME Software
** Branch linked: lp:~ubuntu-desktop/gnome-software/ubuntu-xenial -- 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/1762427 Title: Snap install / remove failures aren't stopped in GNOME Software Status in gnome-software package in Ubuntu: Fix Released Status in gnome-software source package in Xenial: Fix Committed Status in gnome-software source package in Artful: Fix Released Status in gnome-software source package in Bionic: Fix Released Bug description: [Impact] Install / remove operations that fail don't show correctly in GNOME Software. Solution was to fix incorrect logic in snapd API code in GNOME software. [Test Case] 1. Open GNOME Software 2. Start installing a snap 3. Cancel the operation from the command line (need to wait until install starts, but before it completes): $ snap abort --last=install Expected result: Install stops and GNOME software show correct state Observed result: Install button still shows, but no progress occurs. [Regression Potential] Could create new bugs in async results. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1762427/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1701757] Re: 17.04 (Zesty) does not source ~/.profile for umask
** Tags added: artful bionic trusty xenial ** Summary changed: - 17.04 (Zesty) does not source ~/.profile for umask + does not source ~/.profile for umask -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1701757 Title: does not source ~/.profile for umask Status in gedit: New Status in Nautilus: New Status in gnome-session package in Ubuntu: Confirmed Bug description: I have always set umask at ~/.profile and gnome-session would source this. But in Zesty, this isn't happening, and I can find no way to set a umask default of my choosing for the gnome-session. Creating a document using gedit always produces the default (unchangeable) permission represented by umask 022. If I adjust umask at ~/.bashrc, creating a document in nano or vi works to get a different umask. But Ubuntu users should be able to adjust umask for GTK3 apps (like gedit) as well. If there is a new way to set ~/.profile variables, the documentation needs to be updated to reflect this so people know how to set them. To manage notifications about this bug go to: https://bugs.launchpad.net/gedit/+bug/1701757/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1692394] Re: Speaker volume overlay sometimes jitters left/right slightly when pressing volume keys
I don't recall seeing this in a while. ** Changed in: gnome-shell (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1692394 Title: Speaker volume overlay sometimes jitters left/right slightly when pressing volume keys Status in gnome-shell package in Ubuntu: Incomplete Bug description: When I press the volume keys on my keyboard the shell displays an overlay showing the volume level. Normally this overlay is stationary, but sometimes when adjusting the volume, the overlay shifts slightly a pixel or two left or right. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.24.2-0ubuntu4 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 ApportVersion: 2.20.5-0ubuntu3 Architecture: amd64 Date: Mon May 22 11:02:57 2017 DisplayManager: lightdm GsettingsChanges: b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true' b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 'org.gnome.Terminal.desktop', 'rhythmbox.desktop', 'yelp.desktop', 'org.gnome.Nautilus.desktop', 'org.gnome.Software.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'scaling-factor' b'uint32 1' InstallationDate: Installed on 2017-05-03 (18 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1692394/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1762910] Re: The position of audio mute icon doesn't keep alignment to audio on icon
** Tags added: visual-quality -- 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/1762910 Title: The position of audio mute icon doesn't keep alignment to audio on icon Status in gnome-shell package in Ubuntu: Confirmed Bug description: When using audio hotkeys to adjust the audio volume, I found the position of audio mute icon doesn't keep alignment to audio on icon. Please compare the attached screenshots, i.e. AudioMute.png and AudioOn.png, to see the difference. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1762910/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1762427] Re: No feedback when snap installation fails
** Description changed: - What happened: + [Impact] + Install / remove operations that fail don't show correctly in GNOME Software. Solution was to fix incorrect logic in snapd API code in GNOME software. - I tried to install Ora from gnome-software 3.20.5-0ubuntu0.16.04.8. The - install button showed the initialised progress state, but never updated. - Dropping to the terminal I could see with snap changes that the task had - errored (because of a 503 talking to the store). + [Test Case] + 1. Open GNOME Software + 2. Start installing a snap + 3. Cancel the operation from the command line (need to wait until install starts, but before it completes): + $ snap abort --last=install - What should happen: + Expected result: + Install stops and GNOME software show correct state - The UI should provide some indication that the install was not - successful. + Observed result: + Install button still shows, but no progress occurs. + + [Regression Potential] + Could create new bugs in async results. ** Summary changed: - No feedback when snap installation fails + Snap install / remove failures aren't stopped in GNOME Software ** Changed in: gnome-software (Ubuntu) Status: New => Fix Committed ** Changed in: gnome-software (Ubuntu) Importance: Undecided => High ** Also affects: gnome-software (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: gnome-software (Ubuntu Bionic) Importance: High Status: Fix Committed ** Also affects: gnome-software (Ubuntu Artful) Importance: Undecided Status: New ** Changed in: gnome-software (Ubuntu Xenial) Status: New => Fix Committed ** Changed in: gnome-software (Ubuntu Artful) Status: New => Fix Released ** Changed in: gnome-software (Ubuntu Bionic) Status: Fix Committed => Fix Released ** Changed in: gnome-software (Ubuntu Bionic) Importance: High => Undecided ** Changed in: gnome-software (Ubuntu Xenial) Importance: Undecided => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1762427 Title: Snap install / remove failures aren't stopped in GNOME Software Status in gnome-software package in Ubuntu: Fix Released Status in gnome-software source package in Xenial: Fix Committed Status in gnome-software source package in Artful: Fix Released Status in gnome-software source package in Bionic: Fix Released Bug description: [Impact] Install / remove operations that fail don't show correctly in GNOME Software. Solution was to fix incorrect logic in snapd API code in GNOME software. [Test Case] 1. Open GNOME Software 2. Start installing a snap 3. Cancel the operation from the command line (need to wait until install starts, but before it completes): $ snap abort --last=install Expected result: Install stops and GNOME software show correct state Observed result: Install button still shows, but no progress occurs. [Regression Potential] Could create new bugs in async results. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1762427/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1762910] Re: The position of audio mute icon doesn't keep alignment to audio on icon
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed -- 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/1762910 Title: The position of audio mute icon doesn't keep alignment to audio on icon Status in gnome-shell package in Ubuntu: Confirmed Bug description: When using audio hotkeys to adjust the audio volume, I found the position of audio mute icon doesn't keep alignment to audio on icon. Please compare the attached screenshots, i.e. AudioMute.png and AudioOn.png, to see the difference. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1762910/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1761663] Re: Attached encrypted USB drive gets stuck in password prompt
Fixed then? ** Changed in: gnome-shell (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1761663 Title: Attached encrypted USB drive gets stuck in password prompt Status in gnome-shell package in Ubuntu: Fix Released Bug description: I used the standard tools in Ubuntu 16 to format and encrypt a large USB hard drive for storing secure backups to. I then used that drive with the standard "Backups" tool to capture periodic backups. My hard drive recently died, forcing me to re-install Ubuntu 16. The re-install went well, but when I tried to attach the drive to restore my personal files, a modal appeared, prompting me to enter my password. So I did. And then it prompted me again. I thought I'd mistyped my password, so I re-entered it, making sure my caplocks or numlock key weren't on, but again, it prompted me. After each prompt, the full- screen modal darkened the background until after a dozen attempts, my background was almost completely black. I suspect what's going on is something's trying to access the encrypted disk while I'm typing in the password, and each access is triggering another prompt, effectively locking me out of the system because it's impossible for me to enter a nearly infinite series of prompts. This bug is a huge problem for two reasons: 1. it locks you out of your computer 2. it prevents you from accessing secure storage and restoring your system I managed to partially workaround #1 by switching to a terminal and running `export DISPLAY=:0; gnome-shell --replace`. That caused Gnome to reload, which minimized the modal program, allowing me to kill it in the app thumbnail view. However, that's a huge hassle, and I'm still unable to access any data on encrypted USB drives, even when I enter the password correctly. Please advise. I don't know exactly what component to file this bug under, so I chose "gnome-shell". Please re-tag it if this is incorrect. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-shell 3.18.5-0ubuntu0.3 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Fri Apr 6 00:26:33 2018 DisplayManager: lightdm InstallationDate: Installed on 2018-03-23 (13 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1761663/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1762427] Re: No feedback when snap installation fails
On code inspection, I think the snap support in gnome-software 3.20 doesn't handle async operation failures correctly. -- 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/1762427 Title: No feedback when snap installation fails Status in gnome-software package in Ubuntu: New Bug description: What happened: I tried to install Ora from gnome-software 3.20.5-0ubuntu0.16.04.8. The install button showed the initialised progress state, but never updated. Dropping to the terminal I could see with snap changes that the task had errored (because of a 503 talking to the store). What should happen: The UI should provide some indication that the install was not successful. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1762427/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1672297] Re: gnome-shell uses lots of memory, and grows over time
Yes, when a fix lands we will push it into 18.04 as a priority.
--
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/1672297
Title:
gnome-shell uses lots of memory, and grows over time
Status in GNOME Shell:
Confirmed
Status in gjs package in Ubuntu:
Triaged
Status in gnome-shell package in Ubuntu:
Confirmed
Status in gjs source package in Bionic:
Triaged
Status in gnome-shell source package in Bionic:
Confirmed
Bug description:
Upstream:
https://gitlab.gnome.org/GNOME/gnome-shell/issues/64
---
gnome-shell's RSS is growing by 1 MiB every few minutes, and is now at
almost 2 GiB.
user 3039 1.8 16.1 4302340 1968476 tty2 Sl+ Mar09 120:17
/usr/bin/gnome-shell
strace output is voluminous; here is a representative sample:
poll([{fd=5, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=5, revents=POLLOUT}])
writev(5, [{"\231\n\10\0\n\0
\0\0\0\0\0\0\0\0\0\0\0\0\0\1\0\0\0\0\0\0\0\0\0\0\0", 32}], 1) = 32
poll([{fd=5, events=POLLIN}], 1, -1)= 1 ([{fd=5, revents=POLLIN}])
recvmsg(5, {msg_name(0)=NULL,
msg_iov(1)=[{"\1\0{\224\0\0\0\0H\0\0\0\0\23\266\32\0\0\0\0\201\242\204\0\0\0\0\0\261.\0\0",
4096}], msg_controllen=0, msg_flags=0}, 0) = 32
recvmsg(5, 0x7fff60efac90, 0) = -1 EAGAIN (Resource temporarily
unavailable)
recvmsg(5, 0x7fff60efac90, 0) = -1 EAGAIN (Resource temporarily
unavailable)
poll([{fd=5, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=5, revents=POLLOUT}])
writev(5, [{"\212\5\4\0a\2228\0y\3\5\0%\3\27\4\231\6\5\0\n\0
\0a\2228\0\0\0\0\0"..., 36}, {NULL, 0}, {"", 0}], 3) = 36
poll([{fd=5, events=POLLIN}], 1, -1)= 1 ([{fd=5, revents=POLLIN}])
recvmsg(5, {msg_name(0)=NULL,
msg_iov(1)=[{"\1\0}\224\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0",
4096}], msg_controllen=0, msg_flags=0}, 0) = 32
recvmsg(5, 0x7fff60efac90, 0) = -1 EAGAIN (Resource temporarily
unavailable)
poll([{fd=5, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=5, revents=POLLOUT}])
writev(5, [{"\212\n\2\0a\2228\0", 8}, {NULL, 0}, {"", 0}], 3) = 8
recvmsg(5, 0x7fff60efb020, 0) = -1 EAGAIN (Resource temporarily
unavailable)
recvmsg(12, 0x7fff60efb000, 0) = -1 EAGAIN (Resource temporarily
unavailable)
poll([{fd=4, events=POLLIN}, {fd=5, events=POLLIN}, {fd=11, events=POLLIN},
{fd=12, events=POLLIN}, {fd=14, events=POLLIN}, {fd=16, events=POLLIN}, {fd=26,
events=POLLIN}, {fd=29, events=POLLIN}, {fd=32, events=POLLIN}, {fd=34,
events=POLLIN}, {fd=37, events=POLLIN}, {fd=38, events=POLLIN}, {fd=40,
events=POLLIN}, {fd=42, events=POLLIN}, {fd=43, events=POLLIN}], 15, 0) = 0
(Timeout)
recvmsg(5, 0x7fff60efb040, 0) = -1 EAGAIN (Resource temporarily
unavailable)
recvmsg(5, 0x7fff60efb020, 0) = -1 EAGAIN (Resource temporarily
unavailable)
recvmsg(12, 0x7fff60efb000, 0) = -1 EAGAIN (Resource temporarily
unavailable)
poll([{fd=4, events=POLLIN}, {fd=5, events=POLLIN}, {fd=11, events=POLLIN},
{fd=12, events=POLLIN}, {fd=14, events=POLLIN}, {fd=16, events=POLLIN}, {fd=26,
events=POLLIN}, {fd=29, events=POLLIN}, {fd=32, events=POLLIN}, {fd=34,
events=POLLIN}, {fd=37, events=POLLIN}, {fd=38, events=POLLIN}, {fd=40,
events=POLLIN}, {fd=42, events=POLLIN}, {fd=43, events=POLLIN}], 15, 0) = 0
(Timeout)
recvmsg(5, 0x7fff60efb040, 0) = -1 EAGAIN (Resource temporarily
unavailable)
open("/proc/self/stat", O_RDONLY) = 36
fstat(36, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0
fcntl(36, F_GETFL) = 0x8000 (flags O_RDONLY|O_LARGEFILE)
fstat(36, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0
read(36, "3039 (gnome-shell) R 2930 2917 2"..., 4096) = 354
read(36, "", 3072) = 0
close(36) = 0
recvmsg(5, 0x7fff60efb020, 0) = -1 EAGAIN (Resource temporarily
unavailable)
recvmsg(12, 0x7fff60efb000, 0) = -1 EAGAIN (Resource temporarily
unavailable)
poll([{fd=4, events=POLLIN}, {fd=5, events=POLLIN}, {fd=11, events=POLLIN},
{fd=12, events=POLLIN}, {fd=14, events=POLLIN}, {fd=16, events=POLLIN}, {fd=26,
events=POLLIN}, {fd=29, events=POLLIN}, {fd=32, events=POLLIN}, {fd=34,
events=POLLIN}, {fd=37, events=POLLIN}, {fd=38, events=POLLIN}, {fd=40,
events=POLLIN}, {fd=42, events=POLLIN}, {fd=43, events=POLLIN}], 15, 117885) =
1 ([{fd=4, revents=POLLIN}])
read(4, "\1\0\0\0\0\0\0\0", 16) = 8
recvmsg(5, 0x7fff60efb040, 0) = -1 EAGAIN (Resource temporarily
unavailable)
recvmsg(5, 0x7fff60efb020, 0) = -1 EAGAIN (Resource temporarily
unavailable)
recvmsg(12, {msg_name(0)=NULL,
msg_iov(1)=[{"[\2\327&h\0@\0i\0@\0(nu\22\n\0I\0\336\2\232\1\265\0038\2\362\2\355\1",
4096}], msg_controllen=0, msg_flags=0}, 0) = 32
recvmsg(12, 0x7fff60efb000, 0) = -1 EAGAIN (Resource temporarily
unavailable)
poll([{fd=4, events=POLLIN}, {fd=5, eve
[Desktop-packages] [Bug 1746949] Re: Terminal lags (low FPS) the whole desktop when fast output
** Also affects: gtk via https://bugzilla.gnome.org/show_bug.cgi?id=778926 Importance: Unknown Status: Unknown -- 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/1746949 Title: Terminal lags (low FPS) the whole desktop when fast output Status in GTK+: Unknown Status in gnome-terminal package in Ubuntu: New Status in gtk+3.0 package in Ubuntu: Triaged Status in mutter package in Ubuntu: Triaged Bug description: Hi, When using Wayland and gnome-terminal, the performance/fps of the whole desktop is real low when gnome-terminal outputs alot of data. This happens when you cat some logfile for example, or do a tail -f on a quickly growing file. The whole desktop feels sluggish then. This is only the case on Wayland. on X-Server it goes perfectly! To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1746949/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1762427] Re: No feedback when snap installation fails
I'm guessing the trigger for this was the store / CDN failing? It downloads for me, so I'm not able to reproduce. Any download failure like this should report an error in GNOME Software, trying to think of another method to trigger this... -- 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/1762427 Title: No feedback when snap installation fails Status in gnome-software package in Ubuntu: New Bug description: What happened: I tried to install Ora from gnome-software 3.20.5-0ubuntu0.16.04.8. The install button showed the initialised progress state, but never updated. Dropping to the terminal I could see with snap changes that the task had errored (because of a 503 talking to the store). What should happen: The UI should provide some indication that the install was not successful. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1762427/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1763227] Re: gnome-terminal-server crashed with SIGSEGV in gdk_display_get_event()
*** This bug is a duplicate of bug 1664613 *** https://bugs.launchpad.net/bugs/1664613 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1664613, so 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. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1763227/+attachment/5111457/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1763227/+attachment/5111459/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1763227/+attachment/5111462/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1763227/+attachment/5111463/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1763227/+attachment/5111464/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1763227/+attachment/5111465/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1763227/+attachment/5111466/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1664613 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- 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/1763227 Title: gnome-terminal-server crashed with SIGSEGV in gdk_display_get_event() Status in gnome-terminal package in Ubuntu: New Bug description: switched display from extended with 200% scaling to a single display with 100% scaling. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-terminal 3.28.0-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 11 18:04:54 2018 ExecutablePath: /usr/lib/gnome-terminal/gnome-terminal-server InstallationDate: Installed on 2018-03-28 (14 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180325) ProcCmdline: /usr/lib/gnome-terminal/gnome-terminal-server ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SegvAnalysis: Segfault happened at: 0x7f59531ad978:mov0x90(%r14),%rsi PC (0x7f59531ad978) ok source "0x90(%r14)" (0x0090) not located in a known VMA region (needed readable region)! destination "%rsi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-terminal StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 gdk_display_get_event () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 Title: gnome-terminal-server crashed with SIGSEGV in gdk_display_get_event() 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/gnome-terminal/+bug/1763227/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1751460] Re: [regression] deja-dup-monitor crashed with SIGSEGV in Gigacage::::operator()
deja-dup 38.0 was released with the ulimit workaround removed for compatibility with the latest webkit release. ** Changed in: deja-dup Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to deja-dup in Ubuntu. https://bugs.launchpad.net/bugs/1751460 Title: [regression] deja-dup-monitor crashed with SIGSEGV in Gigacageoperator() Status in Déjà Dup: Fix Released Status in WebKit: Fix Released Status in deja-dup package in Ubuntu: Fix Released Status in webkit2gtk package in Ubuntu: Invalid Status in deja-dup source package in Xenial: Triaged Status in deja-dup source package in Artful: Triaged Status in deja-dup source package in Bionic: Fix Released Bug description: Impact -- webkit2gtk 2.20 adds a new security feature called the Gigacage that uses an extremely large virtual memory address space (much larger than available physical memory). Deja Dup's monitor background service had "ulimit -v 100" (that's 1 GB) set as a workaround for a memory leak issue that the developer was unable to reproduce. After upgrading to the new webkit2gtk version, Deja Dup's monitor service will crash because of that virtual memory limit. Test Case - Install the deja-dup update. Install the webkit2gtk update from a PPA (not prepared yet). Log out. Log in. After a few minutes, check /var/crash/ for any Deja Dup crash reports. Regression Potential This could reintroduce the memory leak bug, but otherwise this is a minimal fix. Even if that happens, it's better than the service refusing to run. Other Info -- https://errors.ubuntu.com/problem/27441b78823246dd5392ee29ac30546f6464289e ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: deja-dup 37.1-1fakesync1 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME Date: Sat Feb 24 14:30:47 2018 ExecutablePath: /usr/lib/deja-dup/deja-dup-monitor InstallationDate: Installed on 2017-12-27 (59 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcCmdline: /usr/lib/deja-dup/deja-dup-monitor ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7ff1c3dda588:movl $0x0,(%rax) PC (0x7ff1c3dda588) ok source "$0x0" ok destination "(%rax)" (0xbbadbeef) not located in a known VMA region (needed writable region)! SegvReason: writing unknown VMA Signal: 11 SourcePackage: deja-dup StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18 __pthread_once_slow (once_control=0x7ff1c404202c, init_routine=0x7ff1baec0490 <__once_proxy>) at pthread_once.c:116 Gigacage::ensureGigacage() () from /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18 bmalloc::Heap::Heap(bmalloc::HeapKind, std::lock_guard&) () from /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18 bmalloc::PerProcess >::getSlowCase() () from /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18 Title: deja-dup-monitor crashed with SIGSEGV in __pthread_once_slow() UpgradeStatus: Upgraded to bionic on 2018-02-24 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/deja-dup/+bug/1751460/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1763164] Re: Typos in translatable strings of GNOME Initial Setup
** Changed in: gnome-initial-setup (Ubuntu) Importance: Undecided => High ** Changed in: gnome-initial-setup (Ubuntu) Status: New => Confirmed ** Changed in: ubuntu-translations Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-initial-setup in Ubuntu. https://bugs.launchpad.net/bugs/1763164 Title: Typos in translatable strings of GNOME Initial Setup Status in Ubuntu Translations: Invalid Status in gnome-initial-setup package in Ubuntu: Confirmed Bug description: There are some typos in the translatable strings in GNOME Initial Setup: "Failed to get report informaiton: %s" informaiton -> information "If you like, you can read a quick guide to the new system." The link points to an empty url. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/1763164/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1751508] Re: Xwayland crashed with SIGABRT in OsAbort()
I am also seeing this on a similar system - Lenovo Thinkpad X260 - and for me this occurs when I boot with the laptop docked with two external monitors connected. If I boot without it docked then it boots fine - but when docked Xwayland seems to always crash on startup. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1751508 Title: Xwayland crashed with SIGABRT in OsAbort() Status in xorg-server package in Ubuntu: Confirmed Bug description: Xorg crashed with VS Code. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: xwayland 2:1.19.6-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CrashCounter: 1 CurrentDesktop: GNOME-Greeter:GNOME Date: Sat Feb 24 18:28:10 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExecutablePath: /usr/bin/Xwayland GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 5500 [17aa:3820] InstallationDate: Installed on 2018-02-24 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222) MachineType: LENOVO 80NE ProcCmdline: /usr/bin/Xwayland :1024 -rootless -terminate -core -listen 4 -listen 5 -displayfd 6 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed root=UUID=0beb58c8-0bf5-4e01-95dd-ae78f4ce0dea ro quiet splash vt.handoff=1 Signal: 6 SourcePackage: xorg-server StacktraceTop: OsAbort () ?? () FatalError () InitOutput () ?? () Title: Xwayland crashed with SIGABRT in OsAbort() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 09/09/2015 dmi.bios.vendor: Lenovo dmi.bios.version: BDCN61WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo Yoga 500-14IBD dmi.board.vendor: LENOVO dmi.board.version: SDK0J40688 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga 500-14IBD dmi.modalias: dmi:bvnLenovo:bvrBDCN61WW:bd09/09/2015:svnLENOVO:pn80NE:pvrLenovoYoga500-14IBD:rvnLENOVO:rnLenovoYoga500-14IBD:rvrSDK0J40688WIN:cvnLENOVO:ct10:cvrLenovoYoga500-14IBD: dmi.product.family: IDEAPAD dmi.product.name: 80NE dmi.product.version: Lenovo Yoga 500-14IBD dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.90-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.3.3-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.3.3-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1751508/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1481049] Re: list view defines .iso as unknown types
The attachment "details_full.patch" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** Tags added: patch -- 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/1481049 Title: list view defines .iso as unknown types Status in nautilus package in Ubuntu: Confirmed Bug description: the file manager does not have iin order "type" the .iso file, as shown in the picture you see that I enclose, the files with the extension .iso not respect the line and are scattered around the window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1481049/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1481049] Re: list view defines .iso as unknown types
If Ubuntu wanted to add this to 3.26 it's rather trivial ** Patch added: "details_full.patch" https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1481049/+attachment/5111429/+files/details_full.patch -- 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/1481049 Title: list view defines .iso as unknown types Status in nautilus package in Ubuntu: Confirmed Bug description: the file manager does not have iin order "type" the .iso file, as shown in the picture you see that I enclose, the files with the extension .iso not respect the line and are scattered around the window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1481049/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1724810] Re: 17.10/wayland causing flashes in virtualbox
** Changed in: gnome-shell Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1724810 Title: 17.10/wayland causing flashes in virtualbox Status in GNOME Shell: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Status in virtualbox package in Ubuntu: Fix Released Status in gnome-shell source package in Artful: Triaged Bug description: Hi, just as a quick response: I've installed the new 17.10 Desktop for testing in a virtual machine (VirtualBox 5.1.20 running on MacOS), and while it installed smoothly and booted instantly, there's a problem with the graphics (probably related to wayland): Especially when moving the mouse or starting new programs the screen flashes white every few seconds or sometimes shows just a blank grey screen for about a second. Not suited for regular work. But I have no clue which component precisely is causing that problem. regards To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1724810/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1763209] [NEW] Cannot click and drag on trackpad
Public bug reported: I was previously using Ubuntu 17.10, but just upgraded to 18.04 today. After upgrading, I found that I could no longer click and drag using my trackpad, so I've been unable to drag files anywhere or highlight text without using an external mouse. This is on Dell XPS 13 L321X. Whenever I try to click and drag, the mouse just stops moving wherever it was, and I cannot move the mouse until I click again. External USB mouse seems to work perfectly fine. ** Affects: unity-greeter (Ubuntu) Importance: Undecided Status: New -- 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/1763209 Title: Cannot click and drag on trackpad Status in unity-greeter package in Ubuntu: New Bug description: I was previously using Ubuntu 17.10, but just upgraded to 18.04 today. After upgrading, I found that I could no longer click and drag using my trackpad, so I've been unable to drag files anywhere or highlight text without using an external mouse. This is on Dell XPS 13 L321X. Whenever I try to click and drag, the mouse just stops moving wherever it was, and I cannot move the mouse until I click again. External USB mouse seems to work perfectly fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1763209/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1758306] Re: Cannot switch mouse primary button in GCC
Thanks a lot! Been driving me nuts and afraid that I'll get used to this and not able to go back. On Wed, Apr 11, 2018 at 4:15 PM Launchpad Bug Tracker < 1758...@bugs.launchpad.net> wrote: > Status changed to 'Confirmed' because the bug affects multiple users. > > ** Changed in: gnome-control-center (Ubuntu) >Status: New => Confirmed > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1758306 > > Title: > Cannot switch mouse primary button in GCC > > Status in gnome-control-center package in Ubuntu: > Confirmed > > Bug description: > Prior to yesterday's (March 22/18) Bionic update, I had my mouse > configured for left handed use. That is the mouse primary button being > switched to the right. GCC doesn't seem to work for this now. I don't know > if it's related to evdev or what. > Held back reporting this in case it was fixed by changes overnight. > Updated this morning and problem persists. > > ProblemType: Bug > DistroRelease: Ubuntu 18.04 > Package: gnome-control-center 1:3.28.0-0ubuntu3 > ProcVersionSignature: Ubuntu > 4.13.0-36201803011620.0+mediatree+hauppauge-generic 4.13.13 > Uname: Linux 4.13.0-36201803011620-generic x86_64 > ApportVersion: 2.20.8-0ubuntu10 > Architecture: amd64 > CurrentDesktop: GNOME > Date: Fri Mar 23 07:07:02 2018 > InstallationDate: Installed on 2018-01-19 (62 days ago) > InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 > (20170920) > 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/1758306/+subscriptions > -- This email is printed from 100% recycled electrons. -- 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/1758306 Title: Cannot switch mouse primary button in GCC Status in gnome-control-center package in Ubuntu: Confirmed Bug description: Prior to yesterday's (March 22/18) Bionic update, I had my mouse configured for left handed use. That is the mouse primary button being switched to the right. GCC doesn't seem to work for this now. I don't know if it's related to evdev or what. Held back reporting this in case it was fixed by changes overnight. Updated this morning and problem persists. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1:3.28.0-0ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-36201803011620.0+mediatree+hauppauge-generic 4.13.13 Uname: Linux 4.13.0-36201803011620-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Mar 23 07:07:02 2018 InstallationDate: Installed on 2018-01-19 (62 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170920) 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/1758306/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1763195] Re: usb_modeswitch_dispatcher crashed with SIGSEGV in __strrchr_avx2()
*** This bug is a duplicate of bug 1755017 *** https://bugs.launchpad.net/bugs/1755017 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1755017, so 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. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1763195/+attachment/5111370/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1763195/+attachment/5111372/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1763195/+attachment/5111375/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1763195/+attachment/5111376/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1763195/+attachment/5111377/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1763195/+attachment/5111378/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1763195/+attachment/5111379/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1755017 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to usb-modeswitch in Ubuntu. https://bugs.launchpad.net/bugs/1763195 Title: usb_modeswitch_dispatcher crashed with SIGSEGV in __strrchr_avx2() Status in usb-modeswitch package in Ubuntu: New Bug description: Fujitsu U727 Lifebook with Sierra Wireless LTE Modem EM7305. Problem is after every boot. cp@U727:~$ lsusb | grep rr Bus 001 Device 007: ID 1199:9041 Sierra Wireless, Inc. cp@U727:~$ usb-devices T: Bus=01 Lev=01 Prnt=01 Port=08 Cnt=04 Dev#= 7 Spd=480 MxCh= 0 D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 2 P: Vendor=1199 ProdID=9041 Rev=00.06 S: Manufacturer=Sierra Wireless, Incorporated S: Product=EM7305 C: #Ifs= 2 Cfg#= 2 Atr=e0 MxPwr=500mA /usr/bin/usb-devices: Zeile 79: printf: c: Ungültige Zahl. I: If#= 0 Alt= 0 #EPs= 1 Cls=02(commc) Sub=0e Prot=00 Driver=cdc_mbim /usr/bin/usb-devices: Zeile 79: printf: d: Ungültige Zahl. I: If#= 0 Alt= 1 #EPs= 2 Cls=0a(data ) Sub=00 Prot=02 Driver=cdc_mbim ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: usb-modeswitch 2.5.2+repack0-2ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CrashCounter: 1 Date: Thu Apr 12 00:20:23 2018 ExecutablePath: /usr/sbin/usb_modeswitch_dispatcher InstallationDate: Installed on 2018-04-10 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180410) ProcCmdline: /usr/sbin/usb_modeswitch_dispatcher --switch-mode 1-9 ProcEnviron: LANG=de_DE.UTF-8 PATH=(custom, no user) SegvAnalysis: Segfault happened at: 0x7f04832c63d7 <__strrchr_avx2+23>:vmovdqu (%rdi),%ymm1 PC (0x7f04832c63d7) ok source "(%rdi)" (0x) not located in a known VMA region (needed readable region)! destination "%ymm1" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: usb-modeswitch StacktraceTop: __strrchr_avx2 () at ../sysdeps/x86_64/multiarch/strrchr-avx2.S:54 ?? () __libc_start_main (main=0x55615b296b70, argc=3, argv=0x7ffc9481ba88, init=, fini=, rtld_fini=, stack_end=0x7ffc9481ba78) at ../csu/libc-start.c:310 ?? () Title: usb_modeswitch_dispatcher crashed with SIGSEGV in __strrchr_avx2() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1763195/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1760998] Re: Libreoffice doesn't starts on kubuntu 18.04 32bit
something really not understandable to me has happened. I tried to open Writer and clicking "annulla" nothing was happening and same message was coming back, after about 10 time clicking "annulla" the application appears and as well the same message as before, at this point clicking again "annulla it disappears", but when I close the app, the same message come back again and to close it I click "annulla" 2 times. Opening libreoffice with "libreoffice --safe-mode" the main app is showed with another window to reset any settings and after doing so it seems to work normally. After that any application of the libreoffice suite seems to works as aspected. Should I consider the problem solved !?! -- 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/1760998 Title: Libreoffice doesn't starts on kubuntu 18.04 32bit Status in libreoffice package in Ubuntu: Incomplete Bug description: Any time I try to run any libreoffice package I can see just the loader image, starts loading and than crash ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libreoffice 1:6.0.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic i686 ApportVersion: 2.20.9-0ubuntu2 Architecture: i386 CurrentDesktop: KDE Date: Tue Apr 3 23:43:48 2018 InstallationDate: Installed on 2018-03-28 (6 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha i386 (20180327) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.9-0ubuntu2 Architecture: i386 CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-03-28 (6 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha i386 (20180327) Package: libreoffice 1:6.0.2-0ubuntu1 PackageArchitecture: i386 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Tags: bionic Uname: Linux 4.15.0-13-generic i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1760998/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1685754] Re: gnome-terminal unduly forces umask=0022
You can of course use pam_umask(8) on Ubuntu as well if you wish.
Thanks
--
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/1685754
Title:
gnome-terminal unduly forces umask=0022
Status in gedit:
New
Status in gnome-session:
New
Status in GNOME Terminal:
Confirmed
Status in Nautilus:
New
Status in gnome-terminal package in Ubuntu:
Confirmed
Bug description:
In order to set the default umask of my users to 027 or 007, I
followed the instructions provided in 'man pam_umask' :
In the 'gecos' field of '/etc/passwd', I have inserted 'umask=027' or
'umask=007' (for myself).
Then, MOST graphical applications systematically run with the correct
umask.
In particular, when I press Alt-F2, run 'xterm sh' and type 'umask',
it systematically displays 0007.
But when I press Alt-F2, run 'gnome-terminal -e sh' and type 'umask',
it systematically displays 0022.
That is BAD, and is a security issue.
Workaround : Inside the newly created '/etc/profile.d/umask.sh', and in each
'~/.bashrc', add following content :
UMASK="$(grep -o "^$USER:.*,umask=0[0-7]*" /etc/passwd)"
if [ "$UMASK" ]; then
umask "${UMASK#$USER:*,umask=}"
fi
In fact, 'gnome-terminal' MUST NOT force umask=022, but keep umask unchanged.
Thank you in advance for a quick correction.
ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: gnome-terminal 3.20.2-1ubuntu8
ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
Uname: Linux 4.10.0-19-generic x86_64
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
CurrentDesktop: X-Cinnamon
Date: Mon Apr 24 08:36:58 2017
InstallationDate: Installed on 2017-03-28 (26 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321)
SourcePackage: gnome-terminal
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/gedit/+bug/1685754/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1761606] Re: Two Wi-Fi network applets appear after logging back into live-usb Lubuntu 18.04 session.
Confirmed on Lubuntu 18.04 32bit @ 12/4/18 on daily iso, after a succesfull install 2 wifi icons showing at right down corner -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1761606 Title: Two Wi-Fi network applets appear after logging back into live-usb Lubuntu 18.04 session. Status in network-manager-applet package in Ubuntu: Confirmed Bug description: Lubuntu 18.04 ISO version: 20180404 network-manager-applet version: 1.8.10-2ubuntu1 After logging into my Wi-Fi network then logging out then logging back into the Live-USB session Two Wi-Fi network applets appeared where One would be the expected outcome. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager-gnome 1.8.10-2ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CasperVersion: 1.392 CurrentDesktop: LXDE Date: Thu Apr 5 21:06:24 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IpRoute: default via 192.168.1.1 dev wlp3s0 proto dhcp metric 600 192.168.1.0/24 dev wlp3s0 proto kernel scope link src 192.168.1.166 metric 600 LiveMediaBuild: Lubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: network-manager-applet UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REALAUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE Zero-Daya2f10fa9-551c-4a4f-93ba-5fe6c22c4134 wifi 1522962221 Thu Apr 5 21:03:41 2018 yes 0 no /org/freedesktop/NetworkManager/Settings/2 yes wlp3s0 activated /org/freedesktop/NetworkManager/ActiveConnection/2 -- Wired connection 1 472b45a7-c95b-3638-b452-3f6720688df8 ethernet 1522961321 Thu Apr 5 20:48:41 2018 yes 4294966297no /org/freedesktop/NetworkManager/Settings/1 no -- -- -- -- nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlp3s0 wifi connected/org/freedesktop/NetworkManager/Devices/3 Zero-Daya2f10fa9-551c-4a4f-93ba-5fe6c22c4134 /org/freedesktop/NetworkManager/ActiveConnection/2 enp0s25 ethernet unavailable /org/freedesktop/NetworkManager/Devices/2 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1761606/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1557752] Re: doesn't use screenshots.u.c images
** Changed in: appstream-glib (Ubuntu) Status: Confirmed => Fix Committed ** Changed in: gnome-software (Ubuntu) Status: Incomplete => Fix Committed ** Changed in: appstream-glib (Ubuntu) Assignee: (unassigned) => Andronux (andronuxx27) ** Changed in: gnome-software (Ubuntu) Assignee: (unassigned) => Andronux (andronuxx27) -- 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/1557752 Title: doesn't use screenshots.u.c images Status in appstream-glib package in Ubuntu: Fix Committed Status in gnome-software package in Ubuntu: Fix Committed Bug description: Using current xenial, it seems to main GNOME softwares (cheese, file- roller, eog, ...) don't have a screenshot but should have one (the appstreamcli command lists some valid ones and e.g software-center display some for those) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream-glib/+bug/1557752/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1744941] Re: gnome-software crashes in as_app_parse_desktop_file
** Changed in: appstream-glib (Ubuntu Artful) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to appstream-glib in Ubuntu. https://bugs.launchpad.net/bugs/1744941 Title: gnome-software crashes in as_app_parse_desktop_file Status in appstream-glib package in Ubuntu: Fix Released Status in appstream-glib source package in Xenial: In Progress Status in appstream-glib source package in Artful: Confirmed Status in appstream-glib source package in Bionic: Fix Released Bug description: [ Impact ] Malformed .desktop files might causes crashes because the returned list is NULL. [ Test case ] - Download and copy in one of your XDG_DATA_DIRS (i.e. ~/.local/share/applications) this .desktop file: https://github.com/hughsie/appstream-glib/files/1656100/org.gnome.frogr.desktop.gz - Run gnome-software it must not crash. [ Regression potential ] Missing metadata from .desktop files, but really this is just a null- checks fix, so not really anything might go worse. See more at upstream bug: https://github.com/hughsie/appstream- glib/pull/221 This affects all the releases since xenial. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream-glib/+bug/1744941/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1685754] Re: gnome-terminal unduly forces umask=0022
fwiw → https://bugzilla.gnome.org/show_bug.cgi?id=780622#c44 → where
security issue is also mentioned.
And → https://bugzilla.gnome.org/show_bug.cgi?id=780622#c49 → in fedora
we're going to start adding pam_umask to the default pam configuration
so admins can edit /etc/login.defs
Does it mean Ubuntu 18.04 may benefit from it - as an LTS release, it
should.
--
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/1685754
Title:
gnome-terminal unduly forces umask=0022
Status in gedit:
New
Status in gnome-session:
New
Status in GNOME Terminal:
Confirmed
Status in Nautilus:
New
Status in gnome-terminal package in Ubuntu:
Confirmed
Bug description:
In order to set the default umask of my users to 027 or 007, I
followed the instructions provided in 'man pam_umask' :
In the 'gecos' field of '/etc/passwd', I have inserted 'umask=027' or
'umask=007' (for myself).
Then, MOST graphical applications systematically run with the correct
umask.
In particular, when I press Alt-F2, run 'xterm sh' and type 'umask',
it systematically displays 0007.
But when I press Alt-F2, run 'gnome-terminal -e sh' and type 'umask',
it systematically displays 0022.
That is BAD, and is a security issue.
Workaround : Inside the newly created '/etc/profile.d/umask.sh', and in each
'~/.bashrc', add following content :
UMASK="$(grep -o "^$USER:.*,umask=0[0-7]*" /etc/passwd)"
if [ "$UMASK" ]; then
umask "${UMASK#$USER:*,umask=}"
fi
In fact, 'gnome-terminal' MUST NOT force umask=022, but keep umask unchanged.
Thank you in advance for a quick correction.
ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: gnome-terminal 3.20.2-1ubuntu8
ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
Uname: Linux 4.10.0-19-generic x86_64
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
CurrentDesktop: X-Cinnamon
Date: Mon Apr 24 08:36:58 2017
InstallationDate: Installed on 2017-03-28 (26 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321)
SourcePackage: gnome-terminal
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/gedit/+bug/1685754/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1730242] Re: My system will not recover from suspend
Thank you for the advice. Apparently, there must have been a prior email that I did not see. I apologize for that and plan to try the steps outlined in the “Debugging Kernel Suspend” this weekend. If a still cannot solve the problem can I still come back for help. Sincerely, Bob McCarter > On Apr 9, 2018, at 12:17 AM, Launchpad Bug Tracker > <1730...@bugs.launchpad.net> wrote: > > [Expired for xorg (Ubuntu) because there has been no activity for 60 > days.] > > ** Changed in: xorg (Ubuntu) > Status: Incomplete => Expired > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1730242 > > Title: > My system will not recover from suspend > > Status in xorg package in Ubuntu: > Expired > > Bug description: > I have ubuntu installed on a dell vostro 200 desktop. I think this > problem began with version 12 upgrade. Prior to that it would recover > from auto suspends. > > Thanks in advance for any advice to correct the problem. > > Best, > > Bob > > ProblemType: Bug > DistroRelease: Ubuntu 16.04 > Package: xorg 1:7.7+13ubuntu3 > Uname: Linux 4.13.11-041311-generic i686 > .tmp.unity_support_test.1: > > ApportVersion: 2.20.1-0ubuntu2.10 > Architecture: i386 > CompizPlugins: No value set for > `/apps/compiz-1/general/screen0/options/active_plugins' > CompositorRunning: compiz > CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' > CompositorUnredirectFSW: true > Date: Sun Nov 5 16:57:10 2017 > DistUpgraded: Fresh install > DistroCodename: xenial > DistroVariant: ubuntu > DkmsStatus: > bbswitch, 0.8, 4.13.11-041311-generic, i686: installed > bbswitch, 0.8, 4.4.0-100-generic, i686: installed > nvidia-304, 304.135, 4.4.0-100-generic, i686: installed > ExtraDebuggingInterest: Yes, if not too technical > GraphicsCard: > NVIDIA Corporation GF119 [GeForce GT 620 OEM] [10de:1049] (rev a1) (prog-if > 00 [VGA controller]) > Subsystem: NVIDIA Corporation GF119 [GeForce GT 620 OEM] [10de:0977] > InstallationDate: Installed on 2012-08-05 (1917 days ago) > InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 > (20120423) > ProcEnviron: > LANGUAGE=en_US > PATH=(custom, no user) > LANG=en_US.UTF-8 > SHELL=/bin/bash > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.11-041311-generic > root=UUID=c8f2cac1-e3af-4e51-8a89-726ef2282d44 ro drm.debug=0xe plymouth:debug > Renderer: Software > SourcePackage: xorg > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.vendor: Dell Inc. > dmi.board.vendor: Dell Inc. > version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 > version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1 > version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2 > version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A > version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2 > version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7 > version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 > version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 > version.xserver-xorg-video-intel: xserver-xorg-video-intel > 2:2.99.917+git20160325-1ubuntu1.2 > version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau > 1:1.0.12-1build2 > xserver.bootTime: Sun Nov 5 16:53:35 2017 > xserver.configfile: default > xserver.devices: > inputPower Button KEYBOARD, id 6 > inputPower Button KEYBOARD, id 7 > inputDell Dell KM632 Wireless Keyboard and Mouse KEYBOARD, id 8 > inputDell Dell KM632 Wireless Keyboard and Mouse KEYBOARD, id 9 > inputDell Dell KM632 Wireless Keyboard and Mouse MOUSE, id 10 > xserver.logfile: /var/log/Xorg.0.log > xserver.version: 2:1.18.4-0ubuntu0.7 > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1730242/+subscriptions -- 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/1730242 Title: My system will not recover from suspend Status in xorg package in Ubuntu: Expired Bug description: I have ubuntu installed on a dell vostro 200 desktop. I think this problem began with version 12 upgrade. Prior to that it would recover from auto suspends. Thanks in advance for any advice to correct the problem. Best, Bob ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 Uname: Linux 4.13.11-041311-generic i686 .tmp.unity_support_test.1: ApportVersion: 2.20.1-0ubuntu2.10 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sun Nov 5 16:57:10 2017 DistUpgraded: Fresh instal
[Desktop-packages] [Bug 1701757] Re: 17.04 (Zesty) does not source ~/.profile for umask
fwiw → https://bugzilla.gnome.org/show_bug.cgi?id=780622#c44 → where security issue is mentioned And → https://bugzilla.gnome.org/show_bug.cgi?id=780622#c49 → in fedora we're going to start adding pam_umask to the default pam configuration so admins can edit /etc/login.defs Does it mean Ubuntu 18.04 may benefit from it - as an LTS release, it should. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1701757 Title: 17.04 (Zesty) does not source ~/.profile for umask Status in gedit: New Status in Nautilus: New Status in gnome-session package in Ubuntu: Confirmed Bug description: I have always set umask at ~/.profile and gnome-session would source this. But in Zesty, this isn't happening, and I can find no way to set a umask default of my choosing for the gnome-session. Creating a document using gedit always produces the default (unchangeable) permission represented by umask 022. If I adjust umask at ~/.bashrc, creating a document in nano or vi works to get a different umask. But Ubuntu users should be able to adjust umask for GTK3 apps (like gedit) as well. If there is a new way to set ~/.profile variables, the documentation needs to be updated to reflect this so people know how to set them. To manage notifications about this bug go to: https://bugs.launchpad.net/gedit/+bug/1701757/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1763180] [NEW] Some snaps are showing metadata from .desktop files
Public bug reported: When viewing the Firefox snap in GNOME Software the title is set to "Firefox Web Browser". This comes from the .desktop file from the installed .deb (the snap is not installed). The snap has the title set to "Firefox". ** Affects: gnome-software (Ubuntu) Importance: Medium Status: Triaged ** Changed in: gnome-software (Ubuntu) Status: New => Triaged ** Changed in: gnome-software (Ubuntu) Importance: Undecided => Medium -- 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/1763180 Title: Some snaps are showing metadata from .desktop files Status in gnome-software package in Ubuntu: Triaged Bug description: When viewing the Firefox snap in GNOME Software the title is set to "Firefox Web Browser". This comes from the .desktop file from the installed .deb (the snap is not installed). The snap has the title set to "Firefox". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1763180/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1749481] Re: Wrong session marked as selected in session dropdown on login screen
Seems to be fixed in Ubuntu 18.04.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/1749481
Title:
Wrong session marked as selected in session dropdown on login screen
Status in gdm:
Invalid
Status in gdm3 package in Ubuntu:
Incomplete
Status in gnome-session package in Ubuntu:
Incomplete
Bug description:
My usual session is "Ubuntu" (/usr/share/xsessions/ubuntu.desktop).
When I reboot my machine, on the login screen if I click the cog icon
to show the list of sessions available, a dot is displayed to the left
of the first session in the list ("GNOME"), instead of "Ubuntu".
If I don't click on a session to change it, when I log in the session
used is "Ubuntu" as expected, not "GNOME".
So the greeter fails to reflect which session is actually selected
when first displaying the dropdown, but internally it doesn't mess up
with session selection.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gdm3 3.26.2.1-2ubuntu2
ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Feb 14 16:00:38 2018
EcryptfsInUse: Yes
InstallationDate: Installed on 2016-07-02 (591 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64
(20160420.1)
SourcePackage: gdm3
UpgradeStatus: Upgraded to bionic on 2018-01-29 (16 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/gdm/+bug/1749481/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1763172] Re: gnome-software crashed with signal 5 in g_main_context_new()
*** This bug is a duplicate of bug 1762787 *** https://bugs.launchpad.net/bugs/1762787 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1762787, so 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. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1763172/+attachment/5111264/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1763172/+attachment/5111266/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1763172/+attachment/5111270/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1763172/+attachment/5111271/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1763172/+attachment/5111272/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1763172/+attachment/5111273/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1763172/+attachment/5111274/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1762787 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- 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/1763172 Title: gnome-software crashed with signal 5 in g_main_context_new() Status in gnome-software package in Ubuntu: New Bug description: occurred during software update ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-software 3.28.0-0ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 11 22:33:38 2018 ExecutablePath: /usr/bin/gnome-software InstallationDate: Installed on 2015-05-01 (1076 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-limba N/A gnome-software-plugin-snap3.28.0-0ubuntu7 ProcCmdline: /usr/bin/gnome-software --gapplication-service Signal: 5 SourcePackage: gnome-software StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_main_context_new () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_dbus_connection_send_message_with_reply_sync () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: gnome-software crashed with signal 5 in g_main_context_new() UpgradeStatus: Upgraded to bionic on 2018-04-04 (7 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1763172/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1761663] Re: Attached encrypted USB drive gets stuck in password prompt
I just ran updates, rebooted, and retried, and it worked without issue. -- 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/1761663 Title: Attached encrypted USB drive gets stuck in password prompt Status in gnome-shell package in Ubuntu: New Bug description: I used the standard tools in Ubuntu 16 to format and encrypt a large USB hard drive for storing secure backups to. I then used that drive with the standard "Backups" tool to capture periodic backups. My hard drive recently died, forcing me to re-install Ubuntu 16. The re-install went well, but when I tried to attach the drive to restore my personal files, a modal appeared, prompting me to enter my password. So I did. And then it prompted me again. I thought I'd mistyped my password, so I re-entered it, making sure my caplocks or numlock key weren't on, but again, it prompted me. After each prompt, the full- screen modal darkened the background until after a dozen attempts, my background was almost completely black. I suspect what's going on is something's trying to access the encrypted disk while I'm typing in the password, and each access is triggering another prompt, effectively locking me out of the system because it's impossible for me to enter a nearly infinite series of prompts. This bug is a huge problem for two reasons: 1. it locks you out of your computer 2. it prevents you from accessing secure storage and restoring your system I managed to partially workaround #1 by switching to a terminal and running `export DISPLAY=:0; gnome-shell --replace`. That caused Gnome to reload, which minimized the modal program, allowing me to kill it in the app thumbnail view. However, that's a huge hassle, and I'm still unable to access any data on encrypted USB drives, even when I enter the password correctly. Please advise. I don't know exactly what component to file this bug under, so I chose "gnome-shell". Please re-tag it if this is incorrect. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-shell 3.18.5-0ubuntu0.3 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Fri Apr 6 00:26:33 2018 DisplayManager: lightdm InstallationDate: Installed on 2018-03-23 (13 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1761663/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1763171] [NEW] graphic card driver packages cant be installed
Public bug reported: i used intel graphics update tool for linux, couldnt install packages, i also tried lots of command lines from various guides but still the problem cant be solved. What i could understand is that maybe intel doesnt support this old drivers for linux? because i had windows on this laptop (Lenovo Thinkpad T410)earlier and everything was fine. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-38.43~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-38-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Thu Apr 12 00:29:35 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo Core Processor Integrated Graphics Controller [17aa:215a] InstallationDate: Installed on 2018-03-19 (23 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) MachineType: LENOVO 25184HU ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-38-generic root=UUID=566b3489-a039-4407-a87c-e4ee4bbb0565 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/07/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 6IET65WW (1.25 ) dmi.board.name: 25184HU dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6IET65WW(1.25):bd06/07/2010:svnLENOVO:pn25184HU:pvrThinkPadT410:rvnLENOVO:rn25184HU:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T410 dmi.product.name: 25184HU dmi.product.version: ThinkPad T410 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91+git1804061830.cb850c~oibaf~x version.libgl1-mesa-dri: libgl1-mesa-dri 18.1~git1804111930.bd9539~oibaf~x version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.1~git1804111930.bd9539~oibaf~x version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Thu Apr 12 00:23:23 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.5-0ubuntu2~16.04.1 xserver.video_driver: modeset ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 third-party-packages ubuntu xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1763171 Title: graphic card driver packages cant be installed Status in xorg package in Ubuntu: New Bug description: i used intel graphics update tool for linux, couldnt install packages, i also tried lots of command lines from various guides but still the problem cant be solved. What i could understand is that maybe intel doesnt support this old drivers for linux? because i had windows on this laptop (Lenovo Thinkpad T410)earlier and everything was fine. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-38.43~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-38-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Thu Apr 12 00:29:35 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo Core Processor Integrated Graphics Controller [17aa:215a] InstallationDate: Installed on 2018-03-19 (23 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) MachineType: LENOVO 25184HU ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlin
[Desktop-packages] [Bug 1763166] Re: GNOME Initial Setup is untranslated
Language packs are only built once per week. Try again after the next language pack update. ** Changed in: gnome-initial-setup (Ubuntu) Status: New => Invalid ** Changed in: ubuntu-translations Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-initial-setup in Ubuntu. https://bugs.launchpad.net/bugs/1763166 Title: GNOME Initial Setup is untranslated Status in Ubuntu Translations: Invalid Status in gnome-initial-setup package in Ubuntu: Invalid Bug description: GNOME Initial Setup is untranslated on my non-English (Czech) Ubuntu 18.04 system. It looks like that the translation is not applied for some reason. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/1763166/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1763164] [NEW] Typos in translatable strings of GNOME Initial Setup
Public bug reported: There are some typos in the translatable strings in GNOME Initial Setup: "Failed to get report informaiton: %s" informaiton -> information "If you like, you can read a quick guide to the new system." The link points to an empty url. ** Affects: ubuntu-translations Importance: Undecided Status: New ** Affects: gnome-initial-setup (Ubuntu) Importance: Undecided Status: New ** Tags: bionic l10n ** Also affects: ubuntu-translations Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-initial-setup in Ubuntu. https://bugs.launchpad.net/bugs/1763164 Title: Typos in translatable strings of GNOME Initial Setup Status in Ubuntu Translations: New Status in gnome-initial-setup package in Ubuntu: New Bug description: There are some typos in the translatable strings in GNOME Initial Setup: "Failed to get report informaiton: %s" informaiton -> information "If you like, you can read a quick guide to the new system." The link points to an empty url. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/1763164/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1763166] [NEW] GNOME Initial Setup is untranslated
Public bug reported: GNOME Initial Setup is untranslated on my non-English (Czech) Ubuntu 18.04 system. It looks like that the translation is not applied for some reason. ** Affects: ubuntu-translations Importance: Undecided Status: New ** Affects: gnome-initial-setup (Ubuntu) Importance: Undecided Status: New ** Tags: bionic l10n ** Also affects: ubuntu-translations Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-initial-setup in Ubuntu. https://bugs.launchpad.net/bugs/1763166 Title: GNOME Initial Setup is untranslated Status in Ubuntu Translations: New Status in gnome-initial-setup package in Ubuntu: New Bug description: GNOME Initial Setup is untranslated on my non-English (Czech) Ubuntu 18.04 system. It looks like that the translation is not applied for some reason. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/1763166/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1758306] Re: Cannot switch mouse primary button in GCC
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-control-center (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1758306 Title: Cannot switch mouse primary button in GCC Status in gnome-control-center package in Ubuntu: Confirmed Bug description: Prior to yesterday's (March 22/18) Bionic update, I had my mouse configured for left handed use. That is the mouse primary button being switched to the right. GCC doesn't seem to work for this now. I don't know if it's related to evdev or what. Held back reporting this in case it was fixed by changes overnight. Updated this morning and problem persists. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1:3.28.0-0ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-36201803011620.0+mediatree+hauppauge-generic 4.13.13 Uname: Linux 4.13.0-36201803011620-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Mar 23 07:07:02 2018 InstallationDate: Installed on 2018-01-19 (62 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170920) 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/1758306/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1685754] Re: gnome-terminal unduly forces umask=0022
In Ubuntu 18.04 beta 2 (Bionic), the issue is the same.
** Tags added: artful bionic
--
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/1685754
Title:
gnome-terminal unduly forces umask=0022
Status in gedit:
New
Status in gnome-session:
New
Status in GNOME Terminal:
Confirmed
Status in Nautilus:
New
Status in gnome-terminal package in Ubuntu:
Confirmed
Bug description:
In order to set the default umask of my users to 027 or 007, I
followed the instructions provided in 'man pam_umask' :
In the 'gecos' field of '/etc/passwd', I have inserted 'umask=027' or
'umask=007' (for myself).
Then, MOST graphical applications systematically run with the correct
umask.
In particular, when I press Alt-F2, run 'xterm sh' and type 'umask',
it systematically displays 0007.
But when I press Alt-F2, run 'gnome-terminal -e sh' and type 'umask',
it systematically displays 0022.
That is BAD, and is a security issue.
Workaround : Inside the newly created '/etc/profile.d/umask.sh', and in each
'~/.bashrc', add following content :
UMASK="$(grep -o "^$USER:.*,umask=0[0-7]*" /etc/passwd)"
if [ "$UMASK" ]; then
umask "${UMASK#$USER:*,umask=}"
fi
In fact, 'gnome-terminal' MUST NOT force umask=022, but keep umask unchanged.
Thank you in advance for a quick correction.
ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: gnome-terminal 3.20.2-1ubuntu8
ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
Uname: Linux 4.10.0-19-generic x86_64
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
CurrentDesktop: X-Cinnamon
Date: Mon Apr 24 08:36:58 2017
InstallationDate: Installed on 2017-03-28 (26 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321)
SourcePackage: gnome-terminal
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/gedit/+bug/1685754/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1761261] Re: nouveau/nvidia drivers do not work with display in Bionic on Asus GL703VD Laptop
Maybe the back-light problem is related to the patch for the Elan1200 touchpad: https://bugzilla.redhat.com/show_bug.cgi?id=1543769#c69 ** Bug watch added: Red Hat Bugzilla #1543769 https://bugzilla.redhat.com/show_bug.cgi?id=1543769 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1761261 Title: nouveau/nvidia drivers do not work with display in Bionic on Asus GL703VD Laptop Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in xserver-xorg-video-nouveau package in Ubuntu: Confirmed Bug description: Tried to install Bionic Desktop on my Asus GL703VD ROG Laptop with NVIDIA GTX 1050M Video Card (with i915 Intel graphics card when not using 3D) and the installer does not display. I have tried nouveau.modeset=0 and nomodeset boot options to no avail. I was able to finally install Bionic by hooking up the laptop to a projector, but after a reboot, the laptop display still did not work and I had to set the account to autologin otherwise I could not login to the laptop. I then install openssh-server so that I could ssh into the laptop and I installed the nvidia-390 drivers from ppa:graphics-drivers/ppa which installed, but still no local display. In Artful, I could install with the nouveau.modeset=0 and then installing the proprietary NVIDIA drivers and everything (except touchpad, LP: 1738263) worked. lspci shows the graphics card and NVIDIA card, and lsmod does show that before NVIDIA drivers install, it is using nouveau, asus_wmi, and i915 for graphcis, and once NVIDIA drivers are install, lsmod only shows i915 and asus_wmi for graphics while nvidia is used for gpu and 3D, but still no display on the laptop. lsmod_prenvidia.txt shows the nouveau driver and the /proc/cmdline lsmod_nvidia.txt shows nvidia drivers installed and the /proc/cmdline lspci.txt shows the detected hardware lshw.txt shows the hardware in the laptop. Please let me know if you need any other information. Thanks, Luke To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1761261/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1763120] Re: gnome-shell crashed with signal 5 in g_log_default_handler()
*** This bug is a duplicate of bug 1748450 *** https://bugs.launchpad.net/bugs/1748450 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1748450, so 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. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1763120/+attachment/5111084/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1763120/+attachment/5111086/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1763120/+attachment/5111090/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1763120/+attachment/5111091/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1763120/+attachment/5111092/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1763120/+attachment/5111093/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1763120/+attachment/5111094/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1748450 gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_default_handler() from default_log_handler(message="Connection to xwayland lost") from g_logv() from g_log() from ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- 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/1763120 Title: gnome-shell crashed with signal 5 in g_log_default_handler() Status in gnome-shell package in Ubuntu: New Bug description: gnome-shell crashed with signal 5 in g_log_default_handler() ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.0-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME-Greeter:GNOME Date: Wed Apr 11 19:25:00 2018 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2017-10-01 (192 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) ProcCmdline: /usr/bin/gnome-shell Signal: 5 SourcePackage: gnome-shell StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-shell crashed with signal 5 in g_log_default_handler() UpgradeStatus: Upgraded to bionic on 2018-03-28 (14 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1763120/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1762292] Re: FFE: Sync appstream 0.12.0-3 (main) from Debian unstable (main)
Ok, FFe request approved - but please, before pushing it to the archives, I would like to request rebuilding the package in your PPA with all arches enabled and do some upgrade testing from the existing Ubuntu 0.11.8-3 package. If all looks good, please sync it from Debian. I think packages already in PPA need to be rebuilt if one enabled new architectures in the given PPA. Just a no-change bump should be enough. Thanks! ** Changed in: appstream (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to appstream in Ubuntu. https://bugs.launchpad.net/bugs/1762292 Title: FFE: Sync appstream 0.12.0-3 (main) from Debian unstable (main) Status in appstream package in Ubuntu: Triaged Bug description: Please sync appstream 0.12.0-3 (main) from Debian unstable (main) This introduces a new feature release pretty late in the cycle, so it is something to more carefully consider. Even if it's very late, I do think upgrading this package in Bionic is a good idea though. First of all, it makes upgrading the appstream-generator package to version 0.7.1-3 possible, allowing people to generate much better and smaller metadata for Debian and Ubuntu repositories (and this is what sparked the creation of this sync request). But there are also many other good reasons. This is the NEWS file for the new release, with explanations on why we want the respective changes (I shuffled some entries around to form logical groups) : Version 0.12.0 ~~ Released: 2018-04-04 Features: * Implement release types * qt: Support release types This adds a new feature to the AppStream specification and libappstream that allows release metadata to be tagged as "development" or "stable" releases. Nothing in Ubuntu uses this, so adding will not break anything, but having this in the LTS release means upstream projects can use this feature more easily, and Ubuntu will understand metadata containing it. * Update static data lists * spdx: Add some compatibility workarounds for SPDX 3.0 * validator: Validate SPDX license expressions for metadata_license This updates the SPDX[1] license lists to version 3.0 and adds some compatibility glue to libappstream to parse the new license strings introduced in SPDX 3.0. This is very useful to have, because many projects will start using the new identifier, and it makes sense for AppStream in Ubuntu to be ready for that. Furthermore, it prevents errors from people using the new IDs with older AppStream versions (unfortunately, SPDX 3.0 broke the format, AppStream speaks all flavors of SPDX now, though) [1]: https://spdx.org/licenses/ * apt: Add config snippets to enable icon downloads This results in an easy way for users as well as software centers to enable the download of application icon tarballs via APT just by installing a sepecific package (apt-icons-*). This is quite neat to make icon downloads configurable easily, and also have a central place for the APT configuration. The new packages are used in Debian already by GNOME Software and Plasma Dicover. All existing solutions to enable icons work though, this is an optional change. * Implement support for requires/recommends * Add recommends/requires data to the cache * Add a quick way to check if a version satisfies an AsRelation requirement * yaml: Make Requires/Recommends data more compact and easier to emit * Default to format version 0.12 * validator: Validate requires/recommends tags This adds a new feature to allow AppStream components to require other components or system resources (e.g. minimal memory sizes). Nothing uses this yet, due to that this feature also can't break anything. Having it in the LTS means that upstream projects can already add the metadata easily though and have it validated. * ascli: Properly document the --no-net flag * ascli: Allow to disable network access via an environment variable This is useful in a package build environment where AppStream metadata is validated and the distributor wants to make sure appstreamcli doesn't try to access the network without changing upstream's code and passing the --no-net flag explicitly somewhere. Nice feature to have, no risk potential to break existing code. * Make as_str_replace use as_gstring_replace internally * yaml: Ensure all string values have whitespaces stripped * Make as_component_get_launchables public API * apt: Support 48x48px icons This are miscellaneous improvements which should not cause any issue at all. The 48x48px icons are used in some software centers, having them can be useful (this was a feature requested by Elementary, so chances are they will use these icons at some point). Specification: * spec: Add a "type" property to tag * spec: Initial draft for requires/recommends * spec: Doc
[Desktop-packages] [Bug 1725257] Re: Does not search or index files from Dropbox [Ubuntu 17.10]
** Package changed: gnome-shell (Ubuntu) => nautilus (Ubuntu) -- 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/1725257 Title: Does not search or index files from Dropbox [Ubuntu 17.10] Status in nautilus package in Ubuntu: Confirmed Bug description: Gnome-Shell of ubuntu 17.10 do not search and not index files from Dropbox folders. Shell of ubuntu 17.10 only search files from all folders except files that are in dropbox folders, this files only can located in nautilus but not in shell. Please solve this bug to can search the files of diferentes clouds providers as dropbox in the shell, now do not search files in shell. Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1725257/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1763104] Re: nautilus crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a()
*** This bug is a duplicate of bug 1713581 *** https://bugs.launchpad.net/bugs/1713581 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1713581, so 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. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1763104/+attachment/5111004/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1763104/+attachment/5111006/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1763104/+attachment/5111010/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1763104/+attachment/5111011/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1763104/+attachment/5111012/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1763104/+attachment/5111013/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1763104/+attachment/5111014/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1713581 nautilus crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a() ** Tags removed: need-amd64-retrace -- 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/1763104 Title: nautilus crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a() Status in nautilus package in Ubuntu: New Bug description: Description: Ubuntu Bionic Beaver (development branch) Release: 18.04 nautilus: Installed: 1:3.26.3-0ubuntu1 Candidate: 1:3.26.3-0ubuntu1 Version table: *** 1:3.26.3-0ubuntu1 500 500 http://nl.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status crash report just appeared. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.3-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 11 19:25:43 2018 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.window-state' b'sidebar-width' b'196' b'org.gnome.nautilus.window-state' b'geometry' b"'890x550+346+34'" b'org.gnome.nautilus.window-state' b'maximized' b'true' b'org.gnome.nautilus.list-view' b'default-zoom-level' b"'small'" InstallationDate: Installed on 2018-04-07 (4 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) ProcCmdline: /usr/bin/nautilus --gapplication-service SegvAnalysis: Segfault happened at: 0x7f01f6ce5c0f : mov(%rdx),%rdx PC (0x7f01f6ce5c0f) ok source "(%rdx)" (0x297d76737b6128) not located in a known VMA region (needed readable region)! destination "%rdx" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: nautilus StacktraceTop: g_type_check_instance_is_fundamentally_a () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_object_ref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_list_copy_deep () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () ?? () Title: nautilus crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1763104/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1763111] [NEW] autokey starting maximized (not in system tray)
Public bug reported: It's so in Kubuntu 18.04 (beta final): autokey (auto)start as window, not, as expected (and as in Kubuntu 17.10) as system tray icon. ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: autotey start system-tray window -- 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/1763111 Title: autokey starting maximized (not in system tray) Status in xorg package in Ubuntu: New Bug description: It's so in Kubuntu 18.04 (beta final): autokey (auto)start as window, not, as expected (and as in Kubuntu 17.10) as system tray icon. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1763111/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1725257] Re: Does not search or index files from Dropbox [Ubuntu 17.10]
Also impacts Ubuntu 18.04 LTS (Bionic Beaver) Beta 2. I'd love to try my hand at a patch—any advice on where to star there? -- 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/1725257 Title: Does not search or index files from Dropbox [Ubuntu 17.10] Status in gnome-shell package in Ubuntu: Confirmed Bug description: Gnome-Shell of ubuntu 17.10 do not search and not index files from Dropbox folders. Shell of ubuntu 17.10 only search files from all folders except files that are in dropbox folders, this files only can located in nautilus but not in shell. Please solve this bug to can search the files of diferentes clouds providers as dropbox in the shell, now do not search files in shell. Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1725257/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1763097] Re: gnome-software crashed with signal 5 in g_main_context_new()
*** This bug is a duplicate of bug 1755064 *** https://bugs.launchpad.net/bugs/1755064 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1755064, so 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. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1763097/+attachment/5110983/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1763097/+attachment/5110985/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1763097/+attachment/5110989/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1763097/+attachment/5110990/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1763097/+attachment/5110991/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1763097/+attachment/5110992/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1763097/+attachment/5110993/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1755064 gnome-software crashed with signal 5 in g_wakeup_new → g_main_context_new → pk_client_resolve → gs_plugin_packagekit_resolve_packages_with_filter → gs_plugin_packagekit_resolve_packages ** Tags removed: need-amd64-retrace -- 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/1763097 Title: gnome-software crashed with signal 5 in g_main_context_new() Status in gnome-software package in Ubuntu: New Bug description: Crash report appears with this. Looks like nothing is broken and did a relaunch of the application. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-software 3.28.0-0ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 11 18:47:37 2018 ExecutablePath: /usr/bin/gnome-software InstallationDate: Installed on 2018-04-07 (4 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-limba N/A gnome-software-plugin-snap3.28.0-0ubuntu7 ProcCmdline: /usr/bin/gnome-software --gapplication-service Signal: 5 SourcePackage: gnome-software StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_main_context_new () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 pk_client_resolve () from /usr/lib/x86_64-linux-gnu/libpackagekit-glib2.so.18 ?? () from /usr/lib/x86_64-linux-gnu/gs-plugins-11/libgs_plugin_packagekit-refine.so gs_plugin_refine () from /usr/lib/x86_64-linux-gnu/gs-plugins-11/libgs_plugin_packagekit-refine.so Title: gnome-software crashed with signal 5 in g_main_context_new() 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/gnome-software/+bug/1763097/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1763104] [NEW] nautilus crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a()
*** This bug is a security vulnerability *** Public security bug reported: Description:Ubuntu Bionic Beaver (development branch) Release:18.04 nautilus: Installed: 1:3.26.3-0ubuntu1 Candidate: 1:3.26.3-0ubuntu1 Version table: *** 1:3.26.3-0ubuntu1 500 500 http://nl.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status crash report just appeared. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.3-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 11 19:25:43 2018 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.window-state' b'sidebar-width' b'196' b'org.gnome.nautilus.window-state' b'geometry' b"'890x550+346+34'" b'org.gnome.nautilus.window-state' b'maximized' b'true' b'org.gnome.nautilus.list-view' b'default-zoom-level' b"'small'" InstallationDate: Installed on 2018-04-07 (4 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) ProcCmdline: /usr/bin/nautilus --gapplication-service SegvAnalysis: Segfault happened at: 0x7f01f6ce5c0f :mov(%rdx),%rdx PC (0x7f01f6ce5c0f) ok source "(%rdx)" (0x297d76737b6128) not located in a known VMA region (needed readable region)! destination "%rdx" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: nautilus StacktraceTop: g_type_check_instance_is_fundamentally_a () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_object_ref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_list_copy_deep () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () ?? () Title: nautilus crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo usr_lib_nautilus: ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash bionic need-amd64-retrace ** Information type changed from Private to Public Security -- 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/1763104 Title: nautilus crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a() Status in nautilus package in Ubuntu: New Bug description: Description: Ubuntu Bionic Beaver (development branch) Release: 18.04 nautilus: Installed: 1:3.26.3-0ubuntu1 Candidate: 1:3.26.3-0ubuntu1 Version table: *** 1:3.26.3-0ubuntu1 500 500 http://nl.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status crash report just appeared. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.3-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 11 19:25:43 2018 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.window-state' b'sidebar-width' b'196' b'org.gnome.nautilus.window-state' b'geometry' b"'890x550+346+34'" b'org.gnome.nautilus.window-state' b'maximized' b'true' b'org.gnome.nautilus.list-view' b'default-zoom-level' b"'small'" InstallationDate: Installed on 2018-04-07 (4 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) ProcCmdline: /usr/bin/nautilus --gapplication-service SegvAnalysis: Segfault happened at: 0x7f01f6ce5c0f : mov(%rdx),%rdx PC (0x7f01f6ce5c0f) ok source "(%rdx)" (0x297d76737b6128) not located in a known VMA region (needed readable region)! destination "%rdx" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: nautilus StacktraceTop: g_type_check_instance_is_fundamentally_a () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_object_ref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_list_copy_deep () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () ?? () Title: nautilus crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1763104/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1763097] [NEW] gnome-software crashed with signal 5 in g_main_context_new()
*** This bug is a duplicate of bug 1755064 *** https://bugs.launchpad.net/bugs/1755064 *** This bug is a security vulnerability *** Public security bug reported: Crash report appears with this. Looks like nothing is broken and did a relaunch of the application. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-software 3.28.0-0ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 11 18:47:37 2018 ExecutablePath: /usr/bin/gnome-software InstallationDate: Installed on 2018-04-07 (4 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-limba N/A gnome-software-plugin-snap3.28.0-0ubuntu7 ProcCmdline: /usr/bin/gnome-software --gapplication-service Signal: 5 SourcePackage: gnome-software StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_main_context_new () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 pk_client_resolve () from /usr/lib/x86_64-linux-gnu/libpackagekit-glib2.so.18 ?? () from /usr/lib/x86_64-linux-gnu/gs-plugins-11/libgs_plugin_packagekit-refine.so gs_plugin_refine () from /usr/lib/x86_64-linux-gnu/gs-plugins-11/libgs_plugin_packagekit-refine.so Title: gnome-software crashed with signal 5 in g_main_context_new() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash bionic ** Information type changed from Private to Public Security -- 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/1763097 Title: gnome-software crashed with signal 5 in g_main_context_new() Status in gnome-software package in Ubuntu: New Bug description: Crash report appears with this. Looks like nothing is broken and did a relaunch of the application. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-software 3.28.0-0ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 11 18:47:37 2018 ExecutablePath: /usr/bin/gnome-software InstallationDate: Installed on 2018-04-07 (4 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-limba N/A gnome-software-plugin-snap3.28.0-0ubuntu7 ProcCmdline: /usr/bin/gnome-software --gapplication-service Signal: 5 SourcePackage: gnome-software StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_main_context_new () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 pk_client_resolve () from /usr/lib/x86_64-linux-gnu/libpackagekit-glib2.so.18 ?? () from /usr/lib/x86_64-linux-gnu/gs-plugins-11/libgs_plugin_packagekit-refine.so gs_plugin_refine () from /usr/lib/x86_64-linux-gnu/gs-plugins-11/libgs_plugin_packagekit-refine.so Title: gnome-software crashed with signal 5 in g_main_context_new() 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/gnome-software/+bug/1763097/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1762292] Re: FFE: Sync appstream 0.12.0-3 (main) from Debian unstable (main)
** Tags added: bionic upgrade-software-version -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to appstream in Ubuntu. https://bugs.launchpad.net/bugs/1762292 Title: FFE: Sync appstream 0.12.0-3 (main) from Debian unstable (main) Status in appstream package in Ubuntu: New Bug description: Please sync appstream 0.12.0-3 (main) from Debian unstable (main) This introduces a new feature release pretty late in the cycle, so it is something to more carefully consider. Even if it's very late, I do think upgrading this package in Bionic is a good idea though. First of all, it makes upgrading the appstream-generator package to version 0.7.1-3 possible, allowing people to generate much better and smaller metadata for Debian and Ubuntu repositories (and this is what sparked the creation of this sync request). But there are also many other good reasons. This is the NEWS file for the new release, with explanations on why we want the respective changes (I shuffled some entries around to form logical groups) : Version 0.12.0 ~~ Released: 2018-04-04 Features: * Implement release types * qt: Support release types This adds a new feature to the AppStream specification and libappstream that allows release metadata to be tagged as "development" or "stable" releases. Nothing in Ubuntu uses this, so adding will not break anything, but having this in the LTS release means upstream projects can use this feature more easily, and Ubuntu will understand metadata containing it. * Update static data lists * spdx: Add some compatibility workarounds for SPDX 3.0 * validator: Validate SPDX license expressions for metadata_license This updates the SPDX[1] license lists to version 3.0 and adds some compatibility glue to libappstream to parse the new license strings introduced in SPDX 3.0. This is very useful to have, because many projects will start using the new identifier, and it makes sense for AppStream in Ubuntu to be ready for that. Furthermore, it prevents errors from people using the new IDs with older AppStream versions (unfortunately, SPDX 3.0 broke the format, AppStream speaks all flavors of SPDX now, though) [1]: https://spdx.org/licenses/ * apt: Add config snippets to enable icon downloads This results in an easy way for users as well as software centers to enable the download of application icon tarballs via APT just by installing a sepecific package (apt-icons-*). This is quite neat to make icon downloads configurable easily, and also have a central place for the APT configuration. The new packages are used in Debian already by GNOME Software and Plasma Dicover. All existing solutions to enable icons work though, this is an optional change. * Implement support for requires/recommends * Add recommends/requires data to the cache * Add a quick way to check if a version satisfies an AsRelation requirement * yaml: Make Requires/Recommends data more compact and easier to emit * Default to format version 0.12 * validator: Validate requires/recommends tags This adds a new feature to allow AppStream components to require other components or system resources (e.g. minimal memory sizes). Nothing uses this yet, due to that this feature also can't break anything. Having it in the LTS means that upstream projects can already add the metadata easily though and have it validated. * ascli: Properly document the --no-net flag * ascli: Allow to disable network access via an environment variable This is useful in a package build environment where AppStream metadata is validated and the distributor wants to make sure appstreamcli doesn't try to access the network without changing upstream's code and passing the --no-net flag explicitly somewhere. Nice feature to have, no risk potential to break existing code. * Make as_str_replace use as_gstring_replace internally * yaml: Ensure all string values have whitespaces stripped * Make as_component_get_launchables public API * apt: Support 48x48px icons This are miscellaneous improvements which should not cause any issue at all. The 48x48px icons are used in some software centers, having them can be useful (this was a feature requested by Elementary, so chances are they will use these icons at some point). Specification: * spec: Add a "type" property to tag * spec: Initial draft for requires/recommends * spec: Document the YAML Rquires/Recommends fields * spec: Clarify that the memory requirement uses MiB as unit This improve the AppStream specification or extend it. It's just documentation changes. Bugfixes: * qt: Implement missing constructors This fixes some nasty crashes in Qt applications using AppStream, like Plasma Discover. * apt: escape the icon scale factor as it is using the arobase character This fixes a bug which
[Desktop-packages] [Bug 1763072] Re: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: tentata sovrascrittura di "/lib/udev/hwdb.d/20-sane.hwdb" (condiviso), diverso da altre
*** This bug is a duplicate of bug 1762827 *** https://bugs.launchpad.net/bugs/1762827 ** This bug has been marked a duplicate of bug 1762827 package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of package libsane1:i386 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1763072 Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: tentata sovrascrittura di "/lib/udev/hwdb.d/20-sane.hwdb" (condiviso), diverso da altre istanze del pacchetto libsane1:i386 Status in sane-backends package in Ubuntu: New Bug description: ubuntu 17.10 ProblemType: Package DistroRelease: Ubuntu 17.10 Package: libsane1 1.0.27-1~experimental2ubuntu2.1 ProcVersionSignature: Ubuntu 4.13.0-38.43-generic 4.13.16 Uname: Linux 4.13.0-38-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 Date: Wed Apr 11 15:44:32 2018 ErrorMessage: tentata sovrascrittura di "/lib/udev/hwdb.d/20-sane.hwdb" (condiviso), diverso da altre istanze del pacchetto libsane1:i386 InstallationDate: Installed on 2018-04-11 (0 days ago) InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Release amd64 (20180106) Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5.1 SourcePackage: sane-backends Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: tentata sovrascrittura di "/lib/udev/hwdb.d/20-sane.hwdb" (condiviso), diverso da altre istanze del pacchetto libsane1:i386 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1763072/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1762827] Re: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from oth
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: sane-backends (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1762827 Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of package libsane1:i386 Status in sane-backends package in Ubuntu: Confirmed Bug description: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 17.10 Package: libsane1 1.0.27-1~experimental2ubuntu2.1 ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 Date: Wed Apr 11 01:29:46 2018 DuplicateSignature: package:libsane1:1.0.27-1~experimental2ubuntu2.1 Unpacking libsane1:i386 (1.0.27-1~experimental2ubuntu2.1) ... dpkg: error processing archive /tmp/apt-dpkg-install-BVXsrr/2-libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb (--unpack): trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of package libsane1:i386 ErrorMessage: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of package libsane1:i386 InstallationDate: Installed on 2017-12-21 (109 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5.1 SourcePackage: sane-backends Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of package libsane1:i386 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1762827/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1756226] Re: nvidia-driver-390 fails to start GUI
Here is my Xorg.0.log with nvidia enabled by PrimaryGPU commented out: https://paste.ubuntu.com/p/XptX6tTdRr/ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1756226 Title: nvidia-driver-390 fails to start GUI Status in nvidia-graphics-drivers-390 package in Ubuntu: In Progress Status in ubuntu-drivers-common package in Ubuntu: In Progress Bug description: I was the original person who posted Ubuntu [Bug 1752053] nvidia-390 fails to boot graphical display. I was able to use the fix on my laptop successfully. However, my desktop computer has 2 GTX1080 Ti cards and the fix does not work. After I boot my desktop computer, I do not get a login screen. I get a blank screen with a flickering text cursor in the top left corner. I am running Bionic. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1756226/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1756226] Re: nvidia-driver-390 fails to start GUI
Here is my Xorg.0.log: https://paste.ubuntu.com/p/mfkBK8hQ3F/ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1756226 Title: nvidia-driver-390 fails to start GUI Status in nvidia-graphics-drivers-390 package in Ubuntu: In Progress Status in ubuntu-drivers-common package in Ubuntu: In Progress Bug description: I was the original person who posted Ubuntu [Bug 1752053] nvidia-390 fails to boot graphical display. I was able to use the fix on my laptop successfully. However, my desktop computer has 2 GTX1080 Ti cards and the fix does not work. After I boot my desktop computer, I do not get a login screen. I get a blank screen with a flickering text cursor in the top left corner. I am running Bionic. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1756226/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1758563] Re: Blocked at gdm login screen on 18.04 if user password has a circumflex accent
This affects me as well. I am using: - GNOME Shell 3.28.0 - GDM 3.28.1 - a 105-key ISO keyboard - 'German' keyboard layout (_not_ the 'no dead keys' variant) I am not using Ubuntu but I am adding this info here, since this issue seems to be much easier to find than the one on GNOME's GitLab. When using the 'no dead keys' variant I can successfully enter single accent characters like '`' or '^' but not accented vowels like 'ò' (it becomes '`o'). When using the 'German' keyboard layout with dead keys, I cannot enter certain accented vowels either. Pressing [^] and [o] simply outputs 'o'. These keys have to be pressed _after_ each other usually. Numerous other special characters, that require simultaneous keypresses work though: €@§~#µ etc., e.g. [AltGr] + [a] --> æ. Compose keys do not work either and thus I believe that this is indeed issue #115 linked by seb1228 above. Interestingly, the on-screen keyboard could not enter many of the simpler special characters, like 'ö' or 'ä' which are single keypresses on the keyboard, at all (see attached picture). In three instances I could enter 'š', 'å' and 'ß'. I deleted 'š' and could not reproduce any of those characters with the on-screen keyboard after that. This problem persists on the desktop though, so it appears to be unrelated? I'll wait for GNOME Shell 3.28.1 and report back if that fixes my issue. ** Attachment added: "showing different special characters that work. dead keys do not work." https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1758563/+attachment/5110930/+files/deadkeys.jpg -- 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/1758563 Title: Blocked at gdm login screen on 18.04 if user password has a circumflex accent Status in gnome-shell package in Ubuntu: Triaged Bug description: Hi, I have a bug since the recent updates on Ubuntu 18.04 (post 10th March): when the user password contains a circumflex accent, like "û", access is denied even if password entered is correct and I stay blocked in a loop at gdm login screen - error message (translated from French): "Sorry, it doesn't work, please try again". Even after modifying it on recovery mode with passwd without û, it stays blocked. Only way to solve it is to reinstall. Graphic card: [AMD/ATI] Cape Verde XT [Radeon HD 7770/8760 / R7 250X] Kernel driver in use: radeon Kernel modules: radeon, amdgpu Steps to reproduce : I did a fresh and new install with 18.04 daily iso from 21st March, formatting / and /home with following user password: Ubuntu42 At startup, I could log successfully both on Xorg and Wayland sessions. Then I modified and tested those passwords, with all of them I could again boot and connect, on Xorg and Wayland: ArchLinux43 LinuxMint@28 KDENeon=51 Fedora_1984 But the last one made me blocked at the gdm login screen: Debianû74 Here unable to modify it on recovery session, error message in French: "erreur de manipulation du jeton d'authentification". Also unable to launch terminal: CTRl Alt F1 refreshes the screen, but F2, F3... F12 freezes it! I only can update in chroot with lie USB. I had to again format and reinstall, with a password without any circumflex accent. How and when I discovered it : On 10th March, I ran since many weeks the alpha version of Ubuntu 18.04, with a password having a "û" inside, which had always worked fine. I did an update, cumulating the last 3 weeks before. On next startup, when I typed my password, both on Xorg and Wayland sessions, no error message but no desktop, nothing appeared but a few seconds later I was back on login screen. I could well log in on terminal (Ctrl Alt F2) or chroot with a live USB, and do the last updates in the next days, but nothing changed. On console, if I ran "startx" I got the message "timeout in locking authority file" and "fatal server error: cannot open log file ./local/share/xorg/Xorg.0.log Both / and /home were not full - more than 60% space available, verified with df -Th ; echo ; df -Ti I tried to reinstall Ubuntu with daily live of 15th March, formatting / but not /home as it was protected by ecryptfs and I didn't save some files, using same user name and password, still blocked. So I copied the /home and .Private folders to another disk to try later recover them, reinstall again, formatting both / and /home, always with my usual password having a "û" (I verified French language, keyboard with French activated, upper case, symbols... OK). This time, again both for Xorg or Wayland sessions, at gdm login I did not success to connect, I got an error message "Désolé ça n'a pas fonctionné, veuillez réessayer", I tried to modify the password in recovery mode, with no special characters nor accents, but still blocked at gdm. And no terminal availa
[Desktop-packages] [Bug 1763075] Re: gnome-software crashed with signal 5 in g_cancellable_make_pollfd()
*** This bug is a duplicate of bug 1742134 *** https://bugs.launchpad.net/bugs/1742134 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1742134, so 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. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1763075/+attachment/5110898/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1763075/+attachment/5110900/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1763075/+attachment/5110903/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1763075/+attachment/5110904/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1763075/+attachment/5110905/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1763075/+attachment/5110906/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1763075/+attachment/5110907/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1742134 gnome-software crashed with signal 5 in g_cancellable_make_pollfd → g_socket_condition_timed_wait → g_socket_connect → g_socket_connection_connect → g_socket_client_connect → soup_socket_connect_sync_internal → soup_connection_connect_sync ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- 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/1763075 Title: gnome-software crashed with signal 5 in g_cancellable_make_pollfd() Status in gnome-software package in Ubuntu: New Bug description: i was running updates...software was not open at all... ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-software 3.28.0-0ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 11 06:50:09 2018 ExecutablePath: /usr/bin/gnome-software InstallationDate: Installed on 2018-03-08 (34 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180307) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-limba N/A gnome-software-plugin-snap3.28.0-0ubuntu7 ProcCmdline: /usr/bin/gnome-software --gapplication-service ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 5 SourcePackage: gnome-software StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_cancellable_make_pollfd () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 g_socket_condition_timed_wait () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 g_socket_connect () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 g_socket_client_connect () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: gnome-software crashed with signal 5 in g_cancellable_make_pollfd() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kismet lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1763075/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1763069] Re: nautilus crashed with SIGABRT in g_assertion_message()
*** This bug is a duplicate of bug 1725745 *** https://bugs.launchpad.net/bugs/1725745 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1725745, so 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. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1763069/+attachment/5110879/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1763069/+attachment/5110881/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1763069/+attachment/5110884/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1763069/+attachment/5110885/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1763069/+attachment/5110886/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1763069/+attachment/5110887/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1763069/+attachment/5110888/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1725745 nautilus crashed with SIGABRT in g_assertion_message() ((source == info->idle_source)) ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- 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/1763069 Title: nautilus crashed with SIGABRT in g_assertion_message() Status in nautilus package in Ubuntu: New Bug description: The crash happened when I cancelled a huge copy operation (5Tb) started by mistake. Nautilus was still estimating the copy, not copying yet. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.3-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 11 14:58:54 2018 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'235' b'org.gnome.nautilus.window-state' b'geometry' b"'1079x735+2020+113'" InstallationDate: Installed on 2018-04-11 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180407) ProcCmdline: nautilus --new-window /home/username ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: nautilus StacktraceTop: g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: nautilus crashed with SIGABRT in g_assertion_message() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1763069/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1763072] [NEW] package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: tentata sovrascrittura di "/lib/udev/hwdb.d/20-sane.hwdb" (condiviso), diverso da alt
Public bug reported: ubuntu 17.10 ProblemType: Package DistroRelease: Ubuntu 17.10 Package: libsane1 1.0.27-1~experimental2ubuntu2.1 ProcVersionSignature: Ubuntu 4.13.0-38.43-generic 4.13.16 Uname: Linux 4.13.0-38-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 Date: Wed Apr 11 15:44:32 2018 ErrorMessage: tentata sovrascrittura di "/lib/udev/hwdb.d/20-sane.hwdb" (condiviso), diverso da altre istanze del pacchetto libsane1:i386 InstallationDate: Installed on 2018-04-11 (0 days ago) InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Release amd64 (20180106) Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5.1 SourcePackage: sane-backends Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: tentata sovrascrittura di "/lib/udev/hwdb.d/20-sane.hwdb" (condiviso), diverso da altre istanze del pacchetto libsane1:i386 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: sane-backends (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package artful -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1763072 Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: tentata sovrascrittura di "/lib/udev/hwdb.d/20-sane.hwdb" (condiviso), diverso da altre istanze del pacchetto libsane1:i386 Status in sane-backends package in Ubuntu: New Bug description: ubuntu 17.10 ProblemType: Package DistroRelease: Ubuntu 17.10 Package: libsane1 1.0.27-1~experimental2ubuntu2.1 ProcVersionSignature: Ubuntu 4.13.0-38.43-generic 4.13.16 Uname: Linux 4.13.0-38-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 Date: Wed Apr 11 15:44:32 2018 ErrorMessage: tentata sovrascrittura di "/lib/udev/hwdb.d/20-sane.hwdb" (condiviso), diverso da altre istanze del pacchetto libsane1:i386 InstallationDate: Installed on 2018-04-11 (0 days ago) InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Release amd64 (20180106) Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5.1 SourcePackage: sane-backends Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: tentata sovrascrittura di "/lib/udev/hwdb.d/20-sane.hwdb" (condiviso), diverso da altre istanze del pacchetto libsane1:i386 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1763072/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1437700] Re: Active file selection is not removed on a new search result
** Changed in: nautilus (Ubuntu) Status: New => Confirmed -- 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/1437700 Title: Active file selection is not removed on a new search result Status in nautilus package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1) Search for a file so that exactly one file is found 2) Select the file 3) Copy it (Ctrl+C) and paste it to another folder 4) Search for a new file so that exactly one file is found, but don't clear the file selection 5) Observe, that despite a new result, the file selection is still active Now, confusing things will follow: 6) Copy the file as it's already selected and paste it the to same folder as the previous file 7) Observe, that an overwrite confirmation dialog opens. The file selection was pointing to the previous file despite the fact that the new file was highlighted during copy. What should happen: - The file selection/highlight should be removed on a new search result so that user has to explicitly select the new file. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: nautilus 1:3.10.1-0ubuntu9.7 ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4 Uname: Linux 3.13.0-34-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.8 Architecture: amd64 CurrentDesktop: Unity Date: Sat Mar 28 21:22:54 2015 GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'owner', 'group', 'permissions', 'mime_type', 'where']" SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1437700/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1652404] Re: .desktop file fails with unhelpful error message "The was an error launching the application"
Filed here: https://gitlab.gnome.org/GNOME/nautilus/issues/357 ** Changed in: nautilus (Ubuntu) Status: New => Confirmed -- 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/1652404 Title: .desktop file fails with unhelpful error message "The was an error launching the application" Status in nautilus package in Ubuntu: Confirmed Bug description: Launching a .desktop file can result in the error message "The was an error launching the application". Such unhelpful message hiding the cause of the failure and leaving the user incapable of fixing the it should not be included in any application ever programmed/released including nautilus. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: nautilus 1:3.20.3-1ubuntu3.1 ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11 Uname: Linux 4.8.0-32-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CurrentDesktop: Unity Date: Sat Dec 24 00:34:23 2016 InstallationDate: Installed on 2015-12-12 (377 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: nautilus UpgradeStatus: Upgraded to yakkety on 2016-10-17 (67 days ago) usr_lib_nautilus: gnome-terminal 3.20.2-1ubuntu5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1652404/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1652404] Re: .desktop file fails with unhelpful error message "The was an error launching the application"
(Applies to Ubuntu 17.10 and the Files 3.28 Nightly Flatpak) -- 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/1652404 Title: .desktop file fails with unhelpful error message "The was an error launching the application" Status in nautilus package in Ubuntu: Confirmed Bug description: Launching a .desktop file can result in the error message "The was an error launching the application". Such unhelpful message hiding the cause of the failure and leaving the user incapable of fixing the it should not be included in any application ever programmed/released including nautilus. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: nautilus 1:3.20.3-1ubuntu3.1 ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11 Uname: Linux 4.8.0-32-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CurrentDesktop: Unity Date: Sat Dec 24 00:34:23 2016 InstallationDate: Installed on 2015-12-12 (377 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: nautilus UpgradeStatus: Upgraded to yakkety on 2016-10-17 (67 days ago) usr_lib_nautilus: gnome-terminal 3.20.2-1ubuntu5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1652404/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1763060] Re: gnome-shell crashed with signal 5 in g_log_default_handler()
*** This bug is a duplicate of bug 1748450 *** https://bugs.launchpad.net/bugs/1748450 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1748450, so 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. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1763060/+attachment/5110862/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1763060/+attachment/5110864/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1763060/+attachment/5110867/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1763060/+attachment/5110868/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1763060/+attachment/5110869/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1763060/+attachment/5110870/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1763060/+attachment/5110871/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1748450 gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_default_handler() from default_log_handler(message="Connection to xwayland lost") from g_logv() from g_log() from ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- 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/1763060 Title: gnome-shell crashed with signal 5 in g_log_default_handler() Status in gnome-shell package in Ubuntu: New Bug description: Happened immediately after restart ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.0-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME-Greeter:GNOME Date: Wed Apr 11 15:50:50 2018 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2018-04-08 (2 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/false Signal: 5 SourcePackage: gnome-shell StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-shell crashed with signal 5 in g_log_default_handler() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1763060/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1763057] Re: gnome-software crashed with signal 5
*** This bug is a duplicate of bug 1762787 *** https://bugs.launchpad.net/bugs/1762787 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1762787, so 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. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1763057/+attachment/5110850/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1763057/+attachment/5110852/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1763057/+attachment/5110856/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1763057/+attachment/5110857/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1763057/+attachment/5110858/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1763057/+attachment/5110859/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1763057/+attachment/5110860/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1762787 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- 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/1763057 Title: gnome-software crashed with signal 5 Status in gnome-software package in Ubuntu: New Bug description: A crash during a software update. I don't know if it matches the other tickets, someone might want to look at the stack trace. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-software 3.28.0-0ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 11 16:43:39 2018 ExecutablePath: /usr/bin/gnome-software InstallationDate: Installed on 2017-10-24 (169 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-limba N/A gnome-software-plugin-snap3.28.0-0ubuntu7 ProcCmdline: /usr/bin/gnome-software --gapplication-service Signal: 5 SourcePackage: gnome-software StacktraceTop: () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_main_context_new () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_dbus_connection_send_message_with_reply_sync () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: gnome-software crashed with signal 5 UpgradeStatus: Upgraded to bionic on 2018-02-06 (64 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1763057/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1482961] Re: Messed up icon sizes for .desktop files
Thank you for reporting this bug to Ubuntu. Ubuntu 15.04 (vivid) reached end-of-life on February 4, 2016. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: nautilus (Ubuntu) Status: New => Incomplete -- 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/1482961 Title: Messed up icon sizes for .desktop files Status in nautilus package in Ubuntu: Incomplete Bug description: .desktop entries showing the original size of the image files as icon. A screenshot is attached. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: nautilus 1:3.14.2-0ubuntu9.1 ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2 Uname: Linux 3.19.0-25-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CurrentDesktop: Unity Date: Sun Aug 9 13:30:38 2015 GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'group', 'where', 'mime_type', 'owner', 'permissions']" InstallationDate: Installed on 2012-06-22 (1142 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) SourcePackage: nautilus UpgradeStatus: Upgraded to vivid on 2015-08-04 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1482961/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1481049] Re: list view defines .iso as unknown types
If you think this is still an issue on Files 3.28 then comment on my issue and I may reopen it :) -- 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/1481049 Title: list view defines .iso as unknown types Status in nautilus package in Ubuntu: Confirmed Bug description: the file manager does not have iin order "type" the .iso file, as shown in the picture you see that I enclose, the files with the extension .iso not respect the line and are scattered around the window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1481049/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1481049] Re: list view defines .iso as unknown types
Confirmed on Ubuntu 17.10. The Files 3.28 Flatpak has this bug fixed by calling the Type of ISOs 'Other' and you can get more info on the Types with the 'Type (Detailed)' column. Ubuntu 18.04 is shipping with Files 3.26, however, so this bug still applies to Ubuntu. I filed a bug upstream here but immediately closed it when I realized that the new behavior is intended and makes sense: https://gitlab.gnome.org/GNOME/nautilus/issues/356 On Ubuntu 17.10 or 18.04: ``` sudo apt install flatpak flatpak remote-add --from gnome-apps-nightly https://sdk.gnome.org/gnome-apps-nightly.flatpakrepo flatpak install gnome-apps-nightly org.gnome.Nautilus/x86_64/master nautilus --quit flatpak run org.gnome.Nautilus ``` -- 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/1481049 Title: list view defines .iso as unknown types Status in nautilus package in Ubuntu: Confirmed Bug description: the file manager does not have iin order "type" the .iso file, as shown in the picture you see that I enclose, the files with the extension .iso not respect the line and are scattered around the window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1481049/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1481049] Re: list view defines .iso as unknown types
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nautilus (Ubuntu) Status: New => Confirmed -- 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/1481049 Title: list view defines .iso as unknown types Status in nautilus package in Ubuntu: Confirmed Bug description: the file manager does not have iin order "type" the .iso file, as shown in the picture you see that I enclose, the files with the extension .iso not respect the line and are scattered around the window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1481049/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1744619] Re: Transitioning GNOME away from libnm-glib
Debian's network-manager-applet 1.8.10-4 has dropped libnm-gtk-dev and libnm-gtk0. While that's not necessarily going to be done for Ubuntu 18.04 LTS, I believe you still need to update unity-control-center so that the VPN features will work there. ** Changed in: unity-control-center (Ubuntu) Importance: Undecided => High ** Changed in: unity-control-center (Ubuntu) Status: New => Confirmed -- 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/1744619 Title: Transitioning GNOME away from libnm-glib Status in network-manager-iodine package in Ubuntu: Fix Released Status in network-manager-l2tp package in Ubuntu: Fix Released Status in network-manager-openvpn package in Ubuntu: Fix Released Status in network-manager-pptp package in Ubuntu: Fix Released Status in network-manager-vpnc package in Ubuntu: Fix Released Status in unity-control-center package in Ubuntu: Confirmed Bug description: Debian has dropped libnm-glib support from most of its VPN plugins. We need to cherry-pick the gnome-shell 3.26.2-4 changes for gnome- shell to properly interact with VPNs. unity-control-center will need to be ported away from libnm-glib for it to display VPNs. The only other known affected desktop is Cinnamon which has fixes "pending" Here's the Debian transition bug: https://bugs.debian.org/cgi-bin/pkgreport.cgi?users=pkg-utopia-maintain...@lists.alioth.debian.org;tag=libnm At first look, KDE Plasma did not seem to be hurt by the libnm-glib support removal, but Kubuntu should probably check more closely. I am filing this bug to coordinate this transition and keep the VPN plugins in -proposed until we at least update gnome-shell. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-iodine/+bug/1744619/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1518740] Re: Filesystem type not shown (NTFS or FAT32)
Thank you for reporting this bug to Ubuntu. Ubuntu 15.04 (vivid) reached end-of-life on February 4, 2016. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. Also I don't have a USB stick to attempt to reproduce this bug with, if teo1978 or someone who is able to reproduce the bug on a supported version of Ubuntu wants to return this to New/Confirmed and report upstream then please do so. ** Changed in: nautilus (Ubuntu) Status: New => Incomplete -- 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/1518740 Title: Filesystem type not shown (NTFS or FAT32) Status in nautilus package in Ubuntu: Incomplete Bug description: I have an external USB hard disk connected; I think it's an NTFS or amybe FAT32 filesystem, certainly not an ext* one. I right-click on it on the left panel of Nautilus and select Properties (or I open it, right-click on the background of the right panel and select "properties", it's the same). Result: see the screenshot. It says: "Filesystem type:" and nothing follows. It should indicate the type of filesystem. Pathetic, as usual with Nautilus. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: nautilus 1:3.14.2-0ubuntu9.1 ProcVersionSignature: Ubuntu 3.19.0-33.38-generic 3.19.8-ckt7 Uname: Linux 3.19.0-33-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1.8 Architecture: amd64 CurrentDesktop: Unity Date: Sun Nov 22 19:05:34 2015 GsettingsChanges: b'org.gnome.nautilus.list-view' b'use-tree-view' b'true' b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where']" InstallationDate: Installed on 2013-10-11 (772 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: nautilus UpgradeStatus: Upgraded to vivid on 2015-08-15 (98 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1518740/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1635804] Re: short cut keys always showing
Upstream said in the upstream bug that it's a bug in GTK. 'there is a list of shortcut keys already available from the menu bar' this is not true because Files (in GNOME, at least) uses CSD? Perhaps this should be closed here and upstream as Won't Fix? ** Package changed: nautilus (Ubuntu) => gtk+3.0 (Ubuntu) ** Also affects: gtk via https://bugzilla.gnome.org/show_bug.cgi?id=773929 Importance: Unknown Status: Unknown -- 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/1635804 Title: short cut keys always showing Status in GTK+: Unknown Status in gtk+3.0 package in Ubuntu: Triaged Bug description: as of 16.10 the shortcut keys are always showing in the right click menu. This is ugly and un-needed as there is a list of shortcut keys already available from the menu bar. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: nautilus 1:3.20.3-1ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0 Uname: Linux 4.8.0-26-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Sat Oct 22 19:17:35 2016 InstallationDate: Installed on 2016-10-14 (8 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: gnome-terminal 3.20.2-1ubuntu5 To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1635804/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1763025] Re: ubuntu installations in Kenya are problematic because default language is little known Oromo, not English or Swahili
** Package changed: gnome-shell (Ubuntu) => ubuntu-translations -- 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/1763025 Title: ubuntu installations in Kenya are problematic because default language is little known Oromo, not English or Swahili Status in Ubuntu Translations: New Bug description: even on a fresh install and since many may years, despite even Debian Bug reports - e.g. #756277: There is an error with locale information for Kenya in ubuntu installation. Language is automatically set to 'Oromo' (understood only by a 3% minority of Ethiopian descent) yet the official languages in Kenya are (the not selectable) en-KE (somehow British English, Kenyan flavour, paper format A4, currency KES, currency format KES 123,456.00 or 123,456/= ) and (the also not selectable) sw-KE (somehow Swahili, Kenyan flavour, paper format A4, currency KES, currency format KES 123,456.00 or 123,456/= ) >>> please make work both locales, en-KE (default) and sw-KE. (Remove Oromo from Kenyan locales) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/1763025/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1763035] Re: gnome-shell crashed with signal 5 in g_log_default_handler()
*** This bug is a duplicate of bug 1748450 *** https://bugs.launchpad.net/bugs/1748450 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1748450, so 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. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1763035/+attachment/5110747/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1763035/+attachment/5110749/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1763035/+attachment/5110752/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1763035/+attachment/5110753/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1763035/+attachment/5110754/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1763035/+attachment/5110755/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1763035/+attachment/5110756/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1748450 gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_default_handler() from default_log_handler(message="Connection to xwayland lost") from g_logv() from g_log() from ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- 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/1763035 Title: gnome-shell crashed with signal 5 in g_log_default_handler() Status in gnome-shell package in Ubuntu: New Bug description: I don't now ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.0-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME-Greeter:GNOME Date: Wed Apr 11 08:06:55 2018 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2018-03-12 (29 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180311) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/false Signal: 5 SourcePackage: gnome-shell StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-shell crashed with signal 5 in g_log_default_handler() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1763035/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1763036] [NEW] Firefox menu not showing in Unity's top menubar
Public bug reported: Firefox menu not showing in Unity's top menubar, neither when I move the mouse to the top of the screen, nor when I press Alt. When I press Alt, the menu is shown below the Unity menubar. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: firefox 60.0~b11+build2-0ubuntu0.17.10.1 [origin: LP-PPA-mozillateam-firefox-next] Uname: Linux 4.15.0-15.1-liquorix-amd64 x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dserodio 1907 F pulseaudio BuildID: 20180410075342 Channel: beta CurrentDesktop: Unity:Unity7:ubuntu Date: Wed Apr 11 10:41:11 2018 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePlugins: Shockwave Flash - /usr/lib/adobe-flashplugin/libflashplayer.so (adobe-flashplugin) DefaultProfilePrefSources: /usr/lib/firefox/defaults/pref/vendor-gre.js /usr/lib/firefox/defaults/pref/channel-prefs.js prefs.js DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-10-11 (181 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MostRecentCrashID: bp-45cdae7e-18ce-4d0e-9de5-642950180405 Profile1Extensions: extensions.sqlite corrupt or missing Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile1Locales: extensions.sqlite corrupt or missing Profile1Plugins: Shockwave Flash - /usr/lib/adobe-flashplugin/libflashplayer.so (adobe-flashplugin) Profile1PrefSources: /usr/lib/firefox/defaults/pref/vendor-gre.js /usr/lib/firefox/defaults/pref/channel-prefs.js prefs.js Profile1Themes: extensions.sqlite corrupt or missing Profile2Extensions: extensions.sqlite corrupt or missing Profile2IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile2Locales: extensions.sqlite corrupt or missing Profile2Plugins: Shockwave Flash - /usr/lib/adobe-flashplugin/libflashplayer.so (adobe-flashplugin) Profile2PrefSources: /usr/lib/firefox/defaults/pref/vendor-gre.js /usr/lib/firefox/defaults/pref/channel-prefs.js prefs.js Profile2Themes: extensions.sqlite corrupt or missing Profiles: Profile0 (Default) - LastVersion=60.0/20180410075342 (In use) Profile1 - LastVersion=58.0.2/20180208173149 (Out of date) Profile2 - LastVersion=60.0/20180329210734 (Out of date) RelatedPackageVersions: adobe-flashplugin 1:20180313.1-0ubuntu0.17.10.1 RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: Upgraded to artful on 2017-10-19 (173 days ago) dmi.bios.date: 05/26/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.3 dmi.board.name: 0G22RW dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.3:bd05/26/2017:svnDellInc.:pnInspiron5567:pvr:rvnDellInc.:rn0G22RW:rvrA02:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5567 dmi.sys.vendor: Dell Inc. ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful beta-channel third-party-packages ** Attachment added: "Screenshot" https://bugs.launchpad.net/bugs/1763036/+attachment/5110757/+files/Workspace%201_003.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1763036 Title: Firefox menu not showing in Unity's top menubar Status in firefox package in Ubuntu: New Bug description: Firefox menu not showing in Unity's top menubar, neither when I move the mouse to the top of the screen, nor when I press Alt. When I press Alt, the menu is shown below the Unity menubar. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: firefox 60.0~b11+build2-0ubuntu0.17.10.1 [origin: LP-PPA-mozillateam-firefox-next] Uname: Linux 4.15.0-15.1-liquorix-amd64 x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dserodio 1907 F pulseaudio BuildID: 20180410075342 Channel: beta CurrentDesktop: Unity:Unity7:ubuntu Date: Wed Apr 11 10:41:11 2018 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePlugins: Shockwave Flash - /usr/lib/adobe-flashplugin/libflashplayer.so (adobe-flashplugin) DefaultProfilePrefSources
[Desktop-packages] [Bug 1672297] Re: gnome-shell uses lots of memory, and grows over time
Could the eventual fix be cherry-picked for Ubuntu's GNOME 3.28? Merge
requests 114 and 50 (gjs; upstream) are targeted for GNOME 3.30.0 (for
example) yet presumably Ubuntu would want the fix in Ubuntu 18.04 rather
than shipping with the leak?
--
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/1672297
Title:
gnome-shell uses lots of memory, and grows over time
Status in GNOME Shell:
Confirmed
Status in gjs package in Ubuntu:
Triaged
Status in gnome-shell package in Ubuntu:
Confirmed
Status in gjs source package in Bionic:
Triaged
Status in gnome-shell source package in Bionic:
Confirmed
Bug description:
Upstream:
https://gitlab.gnome.org/GNOME/gnome-shell/issues/64
---
gnome-shell's RSS is growing by 1 MiB every few minutes, and is now at
almost 2 GiB.
user 3039 1.8 16.1 4302340 1968476 tty2 Sl+ Mar09 120:17
/usr/bin/gnome-shell
strace output is voluminous; here is a representative sample:
poll([{fd=5, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=5, revents=POLLOUT}])
writev(5, [{"\231\n\10\0\n\0
\0\0\0\0\0\0\0\0\0\0\0\0\0\1\0\0\0\0\0\0\0\0\0\0\0", 32}], 1) = 32
poll([{fd=5, events=POLLIN}], 1, -1)= 1 ([{fd=5, revents=POLLIN}])
recvmsg(5, {msg_name(0)=NULL,
msg_iov(1)=[{"\1\0{\224\0\0\0\0H\0\0\0\0\23\266\32\0\0\0\0\201\242\204\0\0\0\0\0\261.\0\0",
4096}], msg_controllen=0, msg_flags=0}, 0) = 32
recvmsg(5, 0x7fff60efac90, 0) = -1 EAGAIN (Resource temporarily
unavailable)
recvmsg(5, 0x7fff60efac90, 0) = -1 EAGAIN (Resource temporarily
unavailable)
poll([{fd=5, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=5, revents=POLLOUT}])
writev(5, [{"\212\5\4\0a\2228\0y\3\5\0%\3\27\4\231\6\5\0\n\0
\0a\2228\0\0\0\0\0"..., 36}, {NULL, 0}, {"", 0}], 3) = 36
poll([{fd=5, events=POLLIN}], 1, -1)= 1 ([{fd=5, revents=POLLIN}])
recvmsg(5, {msg_name(0)=NULL,
msg_iov(1)=[{"\1\0}\224\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0",
4096}], msg_controllen=0, msg_flags=0}, 0) = 32
recvmsg(5, 0x7fff60efac90, 0) = -1 EAGAIN (Resource temporarily
unavailable)
poll([{fd=5, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=5, revents=POLLOUT}])
writev(5, [{"\212\n\2\0a\2228\0", 8}, {NULL, 0}, {"", 0}], 3) = 8
recvmsg(5, 0x7fff60efb020, 0) = -1 EAGAIN (Resource temporarily
unavailable)
recvmsg(12, 0x7fff60efb000, 0) = -1 EAGAIN (Resource temporarily
unavailable)
poll([{fd=4, events=POLLIN}, {fd=5, events=POLLIN}, {fd=11, events=POLLIN},
{fd=12, events=POLLIN}, {fd=14, events=POLLIN}, {fd=16, events=POLLIN}, {fd=26,
events=POLLIN}, {fd=29, events=POLLIN}, {fd=32, events=POLLIN}, {fd=34,
events=POLLIN}, {fd=37, events=POLLIN}, {fd=38, events=POLLIN}, {fd=40,
events=POLLIN}, {fd=42, events=POLLIN}, {fd=43, events=POLLIN}], 15, 0) = 0
(Timeout)
recvmsg(5, 0x7fff60efb040, 0) = -1 EAGAIN (Resource temporarily
unavailable)
recvmsg(5, 0x7fff60efb020, 0) = -1 EAGAIN (Resource temporarily
unavailable)
recvmsg(12, 0x7fff60efb000, 0) = -1 EAGAIN (Resource temporarily
unavailable)
poll([{fd=4, events=POLLIN}, {fd=5, events=POLLIN}, {fd=11, events=POLLIN},
{fd=12, events=POLLIN}, {fd=14, events=POLLIN}, {fd=16, events=POLLIN}, {fd=26,
events=POLLIN}, {fd=29, events=POLLIN}, {fd=32, events=POLLIN}, {fd=34,
events=POLLIN}, {fd=37, events=POLLIN}, {fd=38, events=POLLIN}, {fd=40,
events=POLLIN}, {fd=42, events=POLLIN}, {fd=43, events=POLLIN}], 15, 0) = 0
(Timeout)
recvmsg(5, 0x7fff60efb040, 0) = -1 EAGAIN (Resource temporarily
unavailable)
open("/proc/self/stat", O_RDONLY) = 36
fstat(36, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0
fcntl(36, F_GETFL) = 0x8000 (flags O_RDONLY|O_LARGEFILE)
fstat(36, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0
read(36, "3039 (gnome-shell) R 2930 2917 2"..., 4096) = 354
read(36, "", 3072) = 0
close(36) = 0
recvmsg(5, 0x7fff60efb020, 0) = -1 EAGAIN (Resource temporarily
unavailable)
recvmsg(12, 0x7fff60efb000, 0) = -1 EAGAIN (Resource temporarily
unavailable)
poll([{fd=4, events=POLLIN}, {fd=5, events=POLLIN}, {fd=11, events=POLLIN},
{fd=12, events=POLLIN}, {fd=14, events=POLLIN}, {fd=16, events=POLLIN}, {fd=26,
events=POLLIN}, {fd=29, events=POLLIN}, {fd=32, events=POLLIN}, {fd=34,
events=POLLIN}, {fd=37, events=POLLIN}, {fd=38, events=POLLIN}, {fd=40,
events=POLLIN}, {fd=42, events=POLLIN}, {fd=43, events=POLLIN}], 15, 117885) =
1 ([{fd=4, revents=POLLIN}])
read(4, "\1\0\0\0\0\0\0\0", 16) = 8
recvmsg(5, 0x7fff60efb040, 0) = -1 EAGAIN (Resource temporarily
unavailable)
recvmsg(5, 0x7fff60efb020, 0) = -1 EAGAIN (Resource temporarily
unavailable)
recvmsg(12, {msg_name(0)=NULL,
msg_iov(1)=[{"[\2\327&h\0@\0i\0@\0(nu\22\n\0I\0\336\2\232\1\265\0038\2\362\2\355\1",
[Desktop-packages] [Bug 254171] Re: Nautilus can't properly unmount FUSE file systems
** Tags added: bionic ** Tags removed: zesty -- 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/254171 Title: Nautilus can't properly unmount FUSE file systems Status in Nautilus: Confirmed Status in Files: Invalid Status in nautilus package in Ubuntu: Triaged Status in nautilus package in Debian: New Bug description: Normal users can create and mount fuser-filesystems, such as encfs. By doing "encfs ~/somedir ~/some-other-dir", these filesystems correctly show up on the desktop as mounted filesystems. However, if you right-click and select "unmount" you get a error- message saying you cannot unmount the filesystem, because it does not appear in fstab, and you are not root. This is factually incorrect -- you *can* unmount the filesystem, assuming you're the user who mounted it in the first place, by using the command "fusermount -u directoryname" Nautilus should recognize this kind of filesystem and call the apropriate command for unmounting, so that it would work, instead of falsely claiming that you cannot unount the filesystem. Tested with encfs, likely to affect other similar filesystems like sshfs. Affects both Hardy and Intrepid Update: Tested with the latest jaunty-alpha, still present. To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/254171/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1763033] [NEW] Caja can't properly unmount FUSE file systems
Public bug reported: Steps to reproduce: 1. Install Ubuntu 16.04 LTS MATE or 18.04 LTS MATE 2. Mount FUSE filesystem - for example with sshfs (`sudo apt-get install sshfs`) mkdir ~/sshfs sshfs user@host.local:/ ~/sshfs 3. Do some file operations with ~/sshfs 4. Try to unmount `sshfs` share from Caja Expected results: - Caja unmounts FUSE file-system successfully Actual results: - on onmount Caja shows error message: Unable to unmount sshfs umount: /home/user/sshfs: Permission denied and does not unmount filesystem ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: caja 1.12.7-1ubuntu0.1 ProcVersionSignature: Ubuntu 4.4.0-109.132-generic 4.4.98 Uname: Linux 4.4.0-109-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: MATE Date: Wed Apr 11 16:11:52 2018 InstallationDate: Installed on 2018-01-04 (96 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: caja UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: caja (Ubuntu) Importance: Undecided Status: New ** Affects: fuse (Ubuntu) Importance: Undecided Status: New ** Affects: gvfs (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug bionic xenial ** Also affects: gvfs (Ubuntu) Importance: Undecided Status: New ** Also affects: fuse (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1763033 Title: Caja can't properly unmount FUSE file systems Status in caja package in Ubuntu: New Status in fuse package in Ubuntu: New Status in gvfs package in Ubuntu: New Bug description: Steps to reproduce: 1. Install Ubuntu 16.04 LTS MATE or 18.04 LTS MATE 2. Mount FUSE filesystem - for example with sshfs (`sudo apt-get install sshfs`) mkdir ~/sshfs sshfs user@host.local:/ ~/sshfs 3. Do some file operations with ~/sshfs 4. Try to unmount `sshfs` share from Caja Expected results: - Caja unmounts FUSE file-system successfully Actual results: - on onmount Caja shows error message: Unable to unmount sshfs umount: /home/user/sshfs: Permission denied and does not unmount filesystem ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: caja 1.12.7-1ubuntu0.1 ProcVersionSignature: Ubuntu 4.4.0-109.132-generic 4.4.98 Uname: Linux 4.4.0-109-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: MATE Date: Wed Apr 11 16:11:52 2018 InstallationDate: Installed on 2018-01-04 (96 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: caja UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/caja/+bug/1763033/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 254171] Re: Nautilus can't properly unmount FUSE file systems
** No longer affects: caja (Ubuntu) -- 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/254171 Title: Nautilus can't properly unmount FUSE file systems Status in Nautilus: Confirmed Status in Files: Invalid Status in nautilus package in Ubuntu: Triaged Status in nautilus package in Debian: New Bug description: Normal users can create and mount fuser-filesystems, such as encfs. By doing "encfs ~/somedir ~/some-other-dir", these filesystems correctly show up on the desktop as mounted filesystems. However, if you right-click and select "unmount" you get a error- message saying you cannot unmount the filesystem, because it does not appear in fstab, and you are not root. This is factually incorrect -- you *can* unmount the filesystem, assuming you're the user who mounted it in the first place, by using the command "fusermount -u directoryname" Nautilus should recognize this kind of filesystem and call the apropriate command for unmounting, so that it would work, instead of falsely claiming that you cannot unount the filesystem. Tested with encfs, likely to affect other similar filesystems like sshfs. Affects both Hardy and Intrepid Update: Tested with the latest jaunty-alpha, still present. To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/254171/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1763025] [NEW] ubuntu installations in Kenya are problematic because default language is little known Oromo, not English or Swahili
Public bug reported: even on a fresh install and since many may years, despite even Debian Bug reports - e.g. #756277: There is an error with locale information for Kenya in ubuntu installation. Language is automatically set to 'Oromo' (understood only by a 3% minority of Ethiopian descent) yet the official languages in Kenya are (the not selectable) en-KE (somehow British English, Kenyan flavour, paper format A4, currency KES, currency format KES 123,456.00 or 123,456/= ) and (the also not selectable) sw-KE (somehow Swahili, Kenyan flavour, paper format A4, currency KES, currency format KES 123,456.00 or 123,456/= ) >>> please make work both locales, en-KE (default) and sw-KE. (Remove Oromo from Kenyan locales) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1763025 Title: ubuntu installations in Kenya are problematic because default language is little known Oromo, not English or Swahili Status in gnome-shell package in Ubuntu: New Bug description: even on a fresh install and since many may years, despite even Debian Bug reports - e.g. #756277: There is an error with locale information for Kenya in ubuntu installation. Language is automatically set to 'Oromo' (understood only by a 3% minority of Ethiopian descent) yet the official languages in Kenya are (the not selectable) en-KE (somehow British English, Kenyan flavour, paper format A4, currency KES, currency format KES 123,456.00 or 123,456/= ) and (the also not selectable) sw-KE (somehow Swahili, Kenyan flavour, paper format A4, currency KES, currency format KES 123,456.00 or 123,456/= ) >>> please make work both locales, en-KE (default) and sw-KE. (Remove Oromo from Kenyan locales) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1763025/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1763014] Re: gnome-shell crashed with signal 5 in g_log_default_handler()
*** This bug is a duplicate of bug 1748450 *** https://bugs.launchpad.net/bugs/1748450 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1748450, so 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. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1763014/+attachment/5110711/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1763014/+attachment/5110713/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1763014/+attachment/5110716/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1763014/+attachment/5110717/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1763014/+attachment/5110718/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1763014/+attachment/5110719/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1763014/+attachment/5110720/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1748450 gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_default_handler() from default_log_handler(message="Connection to xwayland lost") from g_logv() from g_log() from ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- 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/1763014 Title: gnome-shell crashed with signal 5 in g_log_default_handler() Status in gnome-shell package in Ubuntu: New Bug description: Crash happened shortly after restart. Had just successfully started a VPN connection and switched off blue-tooth. Then crash, which as such was not visible. Hope that helps. >>> If you could please include in blue-tooth settings an option to NOT switch blue-tooth on at start-up you could make many users happy. Thanks ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.0-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME-Greeter:GNOME Date: Wed Apr 11 15:22:45 2018 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2018-04-09 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANGUAGE=en_GB PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/false Signal: 5 SourcePackage: gnome-shell StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-shell crashed with signal 5 in g_log_default_handler() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1763014/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1762778] Re: ghostscript 9.22 breaks pstotext: Unrecoverable error: undefined in DELAYBIND
Till, would you please take a look and fix pstotext then please? Your upload of ghostscript to Ubuntu broke a package in Ubuntu. I think that there is a responsibility of the uploader to take care of things broken by their upload. -- 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/1762778 Title: ghostscript 9.22 breaks pstotext: Unrecoverable error: undefined in DELAYBIND Status in ghostscript package in Ubuntu: Won't Fix Status in pstotext package in Ubuntu: New Bug description: I noticed after my poppler upload that the "doc-rfc" tests are failing https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-bionic/bionic/amd64/d/doc- rfc/20180410_090135_46f84@/log.gz These tests basically zcat a ps.gz file to pstotext. It's this that is broken. See: laney@nightingale> echo "" | pstotext -debug GPL Ghostscript 9.22 (2017-10-04) Copyright (C) 2017 Artifex Software, Inc. All rights reserved. This software comes with NO WARRANTY: see the file PUBLIC for details. *** WARNING - the DELAYBIND command has been deprecated, and will be removed in the next version. For now you can restore the behaviour by using -dREALLYDEALYBIND but if you require continued use of this command you should contact the Ghostscript developers. Commercial customers of Artifex should email their support contact, free users are encouraged to talk to us on the #ghostscript IRC channel on irc.freenode.net. Unrecoverable error: undefined in DELAYBIND laney@nightingale> echo $? 3 but downgrading ghostscript libgs9 libgs9-common to the previous version 9.21~dfsg+1-0ubuntu3 fixes it: laney@nightingale> echo "" | pstotext -debug GPL Ghostscript 9.21 (2017-03-16) Copyright (C) 2017 Artifex Software, Inc. All rights reserved. This software comes with NO WARRANTY: see the file PUBLIC for details. QI 100 0 0 -100 0 84200 laney@nightingale> echo $? 0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1762778/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1762410] Re: hyphen-{hr, pl, ru}, Recommends: libreoffice-writer, all other hypen packages Suggests:
** Changed in: myspell-hr (Debian)
Status: New => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to openoffice.org-hyphenation-pl in
Ubuntu.
https://bugs.launchpad.net/bugs/1762410
Title:
hyphen-{hr,pl,ru}, Recommends: libreoffice-writer, all other hypen
packages Suggests:
Status in hyphen-ru package in Ubuntu:
Fix Released
Status in myspell-hr package in Ubuntu:
Fix Released
Status in openoffice.org-hyphenation-pl package in Ubuntu:
Fix Released
Status in hyphen-ru package in Debian:
New
Status in myspell-hr package in Debian:
Fix Released
Status in openoffice.org-hyphenation-pl package in Debian:
New
Bug description:
hyphen-{hr,pl,ru} are unlike any other i18n hyphen data package in
that they Recommends: libreoffice-writer but all others Suggests:
## Expected results
Choosing a minimal install on Ubuntu 18.04 will never have any
LibreOffice components installed.
## Actual results
Choosing a minimal install and either Croatian, Polish or Russian
locale on Ubuntu 18.04 will leave LibreOffice Writer and it's
dependencies installed.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/hyphen-ru/+bug/1762410/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1714745] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from shell_gtk_embed_window_created_cb() from g_closure_invoke() from signal_emit_unlocked_R()
I am still having this issue when using 3.26.2-0ubuntu0.1 -- 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/1714745 Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from shell_gtk_embed_window_created_cb() from g_closure_invoke() from signal_emit_unlocked_R() Status in GNOME Shell: Fix Released Status in gnome-shell package in Ubuntu: In Progress Bug description: https://errors.ubuntu.com/problem/7accb2ea7fd305736eb23cca5905e4b690a16cae --- gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.25.91-0ubuntu2 ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8 Uname: Linux 4.12.0-12-generic x86_64 NonfreeKernelModules: openafs ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME Date: Sun Sep 3 02:41:44 2017 DisplayManager: gdm3 EcryptfsInUse: Yes ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2016-02-19 (562 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160218) ProcCmdline: /usr/bin/gnome-shell SegvAnalysis: Segfault happened at: 0x7feb5dff7e26 : mov(%rdi),%rdi PC (0x7feb5dff7e26) ok source "(%rdi)" (0x3fe0) not located in a known VMA region (needed readable region)! destination "%rdi" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: g_type_check_instance_cast () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 () at /usr/lib/gnome-shell/libgnome-shell.so g_closure_invoke () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() UpgradeStatus: Upgraded to artful on 2017-05-02 (123 days ago) UserGroups: adm audio bumblebee cdrom dip docker libvirt libvirtd lpadmin mock plugdev sambashare sbuild sudo wireshark To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1714745/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 254171] Re: Nautilus can't properly unmount FUSE file systems
** Changed in: caja (Ubuntu) Status: Confirmed => 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/254171 Title: Nautilus can't properly unmount FUSE file systems Status in Nautilus: Confirmed Status in Files: Invalid Status in caja package in Ubuntu: Invalid Status in nautilus package in Ubuntu: Triaged Status in nautilus package in Debian: New Bug description: Normal users can create and mount fuser-filesystems, such as encfs. By doing "encfs ~/somedir ~/some-other-dir", these filesystems correctly show up on the desktop as mounted filesystems. However, if you right-click and select "unmount" you get a error- message saying you cannot unmount the filesystem, because it does not appear in fstab, and you are not root. This is factually incorrect -- you *can* unmount the filesystem, assuming you're the user who mounted it in the first place, by using the command "fusermount -u directoryname" Nautilus should recognize this kind of filesystem and call the apropriate command for unmounting, so that it would work, instead of falsely claiming that you cannot unount the filesystem. Tested with encfs, likely to affect other similar filesystems like sshfs. Affects both Hardy and Intrepid Update: Tested with the latest jaunty-alpha, still present. To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/254171/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1710373] Re: Desktop shortcut missing for Vino GUI in Ubuntu 17.10
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: vino (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vino in Ubuntu. https://bugs.launchpad.net/bugs/1710373 Title: Desktop shortcut missing for Vino GUI in Ubuntu 17.10 Status in gnome-control-center package in Ubuntu: Confirmed Status in vino package in Ubuntu: Confirmed Bug description: There is not any possibility for an end user to configure screen sharing via VNC in Ubuntu 17.10. The "Desktop sharing" shortcut cannot be found in the GNOME Shell Overview and is also missing in the Sharing section of the GNOME Control Center. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1710373/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1710373] Re: Desktop shortcut missing for Vino GUI in Ubuntu 17.10
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-control-center (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vino in Ubuntu. https://bugs.launchpad.net/bugs/1710373 Title: Desktop shortcut missing for Vino GUI in Ubuntu 17.10 Status in gnome-control-center package in Ubuntu: Confirmed Status in vino package in Ubuntu: Confirmed Bug description: There is not any possibility for an end user to configure screen sharing via VNC in Ubuntu 17.10. The "Desktop sharing" shortcut cannot be found in the GNOME Shell Overview and is also missing in the Sharing section of the GNOME Control Center. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1710373/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1762292] Re: FFE: Sync appstream 0.12.0-3 (main) from Debian unstable (main)
It is built now in https://launchpad.net/~ximion/+archive/ubuntu/appstream/+packages (it appears like enabling more architectures either needs approval or doesn't cause package already in the archive not to be built on these...) Let me know if there is anything more I can do to help! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to appstream in Ubuntu. https://bugs.launchpad.net/bugs/1762292 Title: FFE: Sync appstream 0.12.0-3 (main) from Debian unstable (main) Status in appstream package in Ubuntu: New Bug description: Please sync appstream 0.12.0-3 (main) from Debian unstable (main) This introduces a new feature release pretty late in the cycle, so it is something to more carefully consider. Even if it's very late, I do think upgrading this package in Bionic is a good idea though. First of all, it makes upgrading the appstream-generator package to version 0.7.1-3 possible, allowing people to generate much better and smaller metadata for Debian and Ubuntu repositories (and this is what sparked the creation of this sync request). But there are also many other good reasons. This is the NEWS file for the new release, with explanations on why we want the respective changes (I shuffled some entries around to form logical groups) : Version 0.12.0 ~~ Released: 2018-04-04 Features: * Implement release types * qt: Support release types This adds a new feature to the AppStream specification and libappstream that allows release metadata to be tagged as "development" or "stable" releases. Nothing in Ubuntu uses this, so adding will not break anything, but having this in the LTS release means upstream projects can use this feature more easily, and Ubuntu will understand metadata containing it. * Update static data lists * spdx: Add some compatibility workarounds for SPDX 3.0 * validator: Validate SPDX license expressions for metadata_license This updates the SPDX[1] license lists to version 3.0 and adds some compatibility glue to libappstream to parse the new license strings introduced in SPDX 3.0. This is very useful to have, because many projects will start using the new identifier, and it makes sense for AppStream in Ubuntu to be ready for that. Furthermore, it prevents errors from people using the new IDs with older AppStream versions (unfortunately, SPDX 3.0 broke the format, AppStream speaks all flavors of SPDX now, though) [1]: https://spdx.org/licenses/ * apt: Add config snippets to enable icon downloads This results in an easy way for users as well as software centers to enable the download of application icon tarballs via APT just by installing a sepecific package (apt-icons-*). This is quite neat to make icon downloads configurable easily, and also have a central place for the APT configuration. The new packages are used in Debian already by GNOME Software and Plasma Dicover. All existing solutions to enable icons work though, this is an optional change. * Implement support for requires/recommends * Add recommends/requires data to the cache * Add a quick way to check if a version satisfies an AsRelation requirement * yaml: Make Requires/Recommends data more compact and easier to emit * Default to format version 0.12 * validator: Validate requires/recommends tags This adds a new feature to allow AppStream components to require other components or system resources (e.g. minimal memory sizes). Nothing uses this yet, due to that this feature also can't break anything. Having it in the LTS means that upstream projects can already add the metadata easily though and have it validated. * ascli: Properly document the --no-net flag * ascli: Allow to disable network access via an environment variable This is useful in a package build environment where AppStream metadata is validated and the distributor wants to make sure appstreamcli doesn't try to access the network without changing upstream's code and passing the --no-net flag explicitly somewhere. Nice feature to have, no risk potential to break existing code. * Make as_str_replace use as_gstring_replace internally * yaml: Ensure all string values have whitespaces stripped * Make as_component_get_launchables public API * apt: Support 48x48px icons This are miscellaneous improvements which should not cause any issue at all. The 48x48px icons are used in some software centers, having them can be useful (this was a feature requested by Elementary, so chances are they will use these icons at some point). Specification: * spec: Add a "type" property to tag * spec: Initial draft for requires/recommends * spec: Document the YAML Rquires/Recommends fields * spec: Clarify that the memory requirement uses MiB as unit This improve the AppStream specification or extend it. It's just documentation changes. Bugfixe
[Desktop-packages] [Bug 1756226] Re: nvidia-driver-390 fails to start GUI
@Martin: can you attach your /var/log/Xorg.0.log with PrimaryGPU commented out, please? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1756226 Title: nvidia-driver-390 fails to start GUI Status in nvidia-graphics-drivers-390 package in Ubuntu: In Progress Status in ubuntu-drivers-common package in Ubuntu: In Progress Bug description: I was the original person who posted Ubuntu [Bug 1752053] nvidia-390 fails to boot graphical display. I was able to use the fix on my laptop successfully. However, my desktop computer has 2 GTX1080 Ti cards and the fix does not work. After I boot my desktop computer, I do not get a login screen. I get a blank screen with a flickering text cursor in the top left corner. I am running Bionic. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1756226/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1740106] Re: Gnome terminal not starting, timeout reached (bionic)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-terminal (Ubuntu) Status: New => Confirmed -- 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/1740106 Title: Gnome terminal not starting, timeout reached (bionic) Status in gnome-terminal package in Ubuntu: Confirmed Bug description: After a having my memory filled I had to reboot because the system got unresponsive. After that I can no longer open gnome terminal. I tried running it from xterm and the following message appears: Error constructing proxy for org.gnome.Terminal:/org/gnome/Terminal/Factory0: Error calling StartServiceByName for org.gnome.Terminal: Timeout was reached ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-terminal 3.24.2-0ubuntu4 ProcVersionSignature: Ubuntu 4.14.0-11.13-generic 4.14.3 Uname: Linux 4.14.0-11-generic x86_64 ApportVersion: 2.20.8-0ubuntu5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Dec 26 10:38:26 2017 InstallationDate: Installed on 2017-08-21 (126 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170820) 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/1740106/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
