[Desktop-packages] [Bug 1724439] Re: gnome-shell crashed with SIGSEGV in meta_window_get_monitor() from ffi_call_unix64() from ffi_call() from gjs_invoke_c_function() from function_call()
** Changed in: mutter Status: Confirmed => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1724439 Title: gnome-shell crashed with SIGSEGV in meta_window_get_monitor() from ffi_call_unix64() from ffi_call() from gjs_invoke_c_function() from function_call() Status in Mutter: In Progress Status in gnome-shell package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/3e662975e4b7e6829b9d68d1c2b06f429e44c854 --- left virtual box to update win10 came back and got error message ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 17 23:37:32 2017 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2017-04-18 (182 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7feb2ed42d94 :mov 0x18(%rax),%eax PC (0x7feb2ed42d94) ok source "0x18(%rax)" (0x0018) not located in a known VMA region (needed readable region)! destination "%eax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: meta_window_get_monitor () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6 ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6 ?? () from /usr/lib/libgjs.so.0 ?? () from /usr/lib/libgjs.so.0 Title: gnome-shell crashed with SIGSEGV in meta_window_get_monitor() 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/mutter/+bug/1724439/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1747509] 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
*** This bug is a duplicate of bug 1725928 *** https://bugs.launchpad.net/bugs/1725928 ** This bug has been marked a duplicate of bug 1725928 package libsane1 1.0.27-1~experimental2ubuntu1: multiarch packages with differing files -- 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/1747509 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: This greeted me as I logged in. ProblemType: Package DistroRelease: Ubuntu 17.10 Package: libsane1 1.0.27-1~experimental2ubuntu2.1 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 Date: Sun Feb 4 20:04:52 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-eTHUbf/46-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-06 (61 days ago) InstallationMedia: Ubuntu-MATE 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/1747509/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1747412] Re: package network-manager-config-connectivity-ubuntu 1.8.4-1ubuntu3 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saí
*** This bug is a duplicate of bug 1742403 *** https://bugs.launchpad.net/bugs/1742403 ** This bug has been marked a duplicate of bug 1742403 package network-manager-config-connectivity-ubuntu 1.8.4-1ubuntu3 failed to install/upgrade: installed network-manager-config-connectivity-ubuntu package post-installation script subprocess returned error exit status 1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1747412 Title: package network-manager-config-connectivity-ubuntu 1.8.4-1ubuntu3 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 1 Status in network-manager package in Ubuntu: New Bug description: This issue happened when i tried to update. ProblemType: Package DistroRelease: Ubuntu 17.10 Package: network-manager-config-connectivity-ubuntu 1.8.4-1ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 Date: Mon Feb 5 09:54:10 2018 ErrorMessage: sub-processo script post-installation instalado retornou estado de saída de erro 1 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-05-28 (252 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) IpRoute: default via 192.168.0.1 dev enp2s0 proto static metric 100 169.254.0.0/16 dev enp2s0 scope link metric 1000 192.168.0.0/24 dev enp2s0 proto kernel scope link src 192.168.0.100 metric 100 IwConfig: enp2s0no wireless extensions. lono wireless extensions. NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true PackageArchitecture: all 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 RfKill: SourcePackage: network-manager Title: package network-manager-config-connectivity-ubuntu 1.8.4-1ubuntu3 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 1 UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMP TIMESTAMP-REALAUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE Conexão cabeada 1 e9be19de-58c5-300b-8d8c-7c5a5c25ded5 802-3-ethernet 1517832180 seg 05 fev 2018 10:03:00 -02 yes 4294966297no /org/freedesktop/NetworkManager/Settings/1 yes enp2s0 activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH enp2s0 ethernet connected /org/freedesktop/NetworkManager/Devices/2 Conexão cabeada 1 e9be19de-58c5-300b-8d8c-7c5a5c25ded5 /org/freedesktop/NetworkManager/ActiveConnection/1 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.8.4connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1747412/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1723378] Re: gnome-shell crashed with SIGTRAP in g_malloc0() from blur_pixels() from _st_create_shadow_pipeline() from _st_create_shadow_pipeline_from_actor() from st_icon_upda
** 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/1723378 Title: gnome-shell crashed with SIGTRAP in g_malloc0() from blur_pixels() from _st_create_shadow_pipeline() from _st_create_shadow_pipeline_from_actor() from st_icon_update_shadow_pipeline() Status in GNOME Shell: Fix Released Status in gnome-shell package in Ubuntu: In Progress Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.26.1-0ubuntu2, the problem page at https://errors.ubuntu.com/problem/39ad471656564025f5de8136fcb05bccd9c3e8c7 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1723378/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1747578] Re: gvfsd-mtp crashed with SIGSEGV
*** This bug is a duplicate of bug 1706097 *** https://bugs.launchpad.net/bugs/1706097 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 #1706097, 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/1747578/+attachment/5049514/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1747578/+attachment/5049516/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1747578/+attachment/5049520/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1747578/+attachment/5049521/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1747578/+attachment/5049522/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1747578/+attachment/5049523/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1747578/+attachment/5049524/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1706097 gvfsd-mtp crashed with SIGSEGV ** 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 gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1747578 Title: gvfsd-mtp crashed with SIGSEGV Status in gvfs package in Ubuntu: New Bug description: idon know ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gvfs-backends 1.34.1-1ubuntu4 ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 Uname: Linux 4.13.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Tue Feb 6 13:22:54 2018 ExecutablePath: /usr/lib/gvfs/gvfsd-mtp InstallationDate: Installed on 2018-01-27 (9 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180125) ProcCmdline: /usr/lib/gvfs/gvfsd-mtp --spawner :1.7 /org/gtk/gvfs/exec_spaw/8 SegvAnalysis: Segfault happened at: 0x7f729811f5a9:mov0x18(%rax),%rax PC (0x7f729811f5a9) ok source "0x18(%rax)" (0x0018) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gvfs StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/gvfs/libgvfsdaemon.so ?? () 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 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: gvfsd-mtp crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1747578/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1737046] Re: Razer Naga Chroma wheel tilt being remapped to vertical scroll
https://bugs.freedesktop.org/show_bug.cgi?id=104960 ** Bug watch added: freedesktop.org Bugzilla #104960 https://bugs.freedesktop.org/show_bug.cgi?id=104960 -- 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/1737046 Title: Razer Naga Chroma wheel tilt being remapped to vertical scroll Status in xorg package in Ubuntu: Triaged Bug description: My Razer Naga Chroma's wheel tilt right and left (buttons 6, and 7) are being remapped to scroll up and down (buttons 4, and 5) as per xev. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-17.20~16.04.1-generic 4.13.8 Uname: Linux 4.13.0-17-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.13 Architecture: amd64 BootLog: Scanning for Btrfs filesystems Ubuntu: clean, 394556/11829248 files, 20977988/47286784 blocks CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Thu Dec 7 14:25:33 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Device [1558:1303] Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 5986: Acer, Inc Bus 001 Device 004: ID 1532:0053 Razer USA, Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System76 Galago Pro ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=4bf03301-9454-4893-8590-722b1fa2efa7 ro quiet splash crashkernel=384M-2G:128M,2G-:256M vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/26/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.04nRSA dmi.board.asset.tag: Tag 12345 dmi.board.name: Galago Pro dmi.board.vendor: System76 dmi.board.version: galp2 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76 dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.04nRSA:bd04/26/2017:svnSystem76:pnGalagoPro:pvrgalp2:rvnSystem76:rnGalagoPro:rvrgalp2:cvnSystem76:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: Galago Pro dmi.product.version: galp2 dmi.sys.vendor: System76 version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.80-1~xenial 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 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 Dec 7 14:21:19 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.3-1ubuntu1~16.04.4 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1737046/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1747568] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1747568/+attachment/5049502/+files/JournalErrors.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1747568 Title: Mouse clicks ignored in Wayland Status in gnome-shell package in Ubuntu: Incomplete Bug description: If I disable Wayland, mouse clicks start working again. Randomly started occurring sometime after initial install. Ubuntu 17.10 --- ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-10-27 (102 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Package: gnome-shell 3.26.2-0ubuntu0.1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Tags: artful third-party-packages Uname: Linux 4.15.0-041500rc9-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip emby libvirt lpadmin plex plugdev sambashare sudo users video _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1747568/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1747568] GsettingsChanges.txt
apport information ** Attachment added: "GsettingsChanges.txt" https://bugs.launchpad.net/bugs/1747568/+attachment/5049501/+files/GsettingsChanges.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1747568 Title: Mouse clicks ignored in Wayland Status in gnome-shell package in Ubuntu: Incomplete Bug description: If I disable Wayland, mouse clicks start working again. Randomly started occurring sometime after initial install. Ubuntu 17.10 --- ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-10-27 (102 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Package: gnome-shell 3.26.2-0ubuntu0.1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Tags: artful third-party-packages Uname: Linux 4.15.0-041500rc9-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip emby libvirt lpadmin plex plugdev sambashare sudo users video _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1747568/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1747568] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1747568/+attachment/5049503/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1747568 Title: Mouse clicks ignored in Wayland Status in gnome-shell package in Ubuntu: Incomplete Bug description: If I disable Wayland, mouse clicks start working again. Randomly started occurring sometime after initial install. Ubuntu 17.10 --- ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-10-27 (102 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Package: gnome-shell 3.26.2-0ubuntu0.1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Tags: artful third-party-packages Uname: Linux 4.15.0-041500rc9-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip emby libvirt lpadmin plex plugdev sambashare sudo users video _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1747568/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1747568] Re: Mouse clicks ignored in Wayland
apport information ** Tags added: apport-collected artful third-party-packages ** Description changed: If I disable Wayland, mouse clicks start working again. Randomly started occurring sometime after initial install. Ubuntu 17.10 + --- + ApportVersion: 2.20.7-0ubuntu3.7 + Architecture: amd64 + CurrentDesktop: ubuntu:GNOME + DisplayManager: gdm3 + DistroRelease: Ubuntu 17.10 + InstallationDate: Installed on 2017-10-27 (102 days ago) + InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) + Package: gnome-shell 3.26.2-0ubuntu0.1 + PackageArchitecture: amd64 + ProcEnviron: + TERM=xterm + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + Tags: artful third-party-packages + Uname: Linux 4.15.0-041500rc9-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip emby libvirt lpadmin plex plugdev sambashare sudo users video + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1747568/+attachment/5049500/+files/Dependencies.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1747568 Title: Mouse clicks ignored in Wayland Status in gnome-shell package in Ubuntu: Incomplete Bug description: If I disable Wayland, mouse clicks start working again. Randomly started occurring sometime after initial install. Ubuntu 17.10 --- ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-10-27 (102 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Package: gnome-shell 3.26.2-0ubuntu0.1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Tags: artful third-party-packages Uname: Linux 4.15.0-041500rc9-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip emby libvirt lpadmin plex plugdev sambashare sudo users video _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1747568/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1747566] Re: org.gnome.Shell.desktop stacktraces; tweener.js:73
** Summary changed: - org.gnome.Shell.desktop stacktraces; tweener.js + org.gnome.Shell.desktop stacktraces; tweener.js:73 -- 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/1747566 Title: org.gnome.Shell.desktop stacktraces; tweener.js:73 Status in gnome-shell package in Ubuntu: Confirmed Bug description: I'm running Ubuntu Bionic. After latest dist-upgrade today I'm not getting a lot of stacktraces in my syslog: Feb 5 16:14:04 fog gnome-shell[5676]: Object Clutter.Actor (0x55c40613dde0), has been already finalized. Impossible to get any property from it. Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: == Stack trace for context 0x55c40593a000 == Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: #0 0x7fff5f700870 b resource:///org/gnome/shell/ui/tweener.js:73 (0x7f38c40ddef0 @ 9) Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: #1 0x7fff5f700910 b resource:///org/gnome/shell/ui/tweener.js:105 (0x7f38c40df230 @ 36) Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: #2 0x7fff5f7009b0 b resource:///org/gnome/shell/ui/tweener.js:92 (0x7f38c40df098 @ 52) Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: #3 0x7fff5f700a20 I resource:///org/gnome/gjs/modules/tweener/tweener.js:203 (0x7f38c40e9cd0 @ 54) Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: #4 0x7fff5f700b70 b resource:///org/gnome/gjs/modules/tweener/tweener.js:332 (0x7f38c40e9d58 @ 1626) Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: #5 0x7fff5f700c20 b resource:///org/gnome/gjs/modules/tweener/tweener.js:345 (0x7f38c40e9de0 @ 100) Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: #6 0x7fff5f700cb0 b resource:///org/gnome/gjs/modules/tweener/tweener.js:360 (0x7f38c40e9e68 @ 10) Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: #7 0x7fff5f700da0 b resource:///org/gnome/gjs/modules/signals.js:126 (0x7f38c40e2b38 @ 386) Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: #8 0x7fff5f700e50 b resource:///org/gnome/shell/ui/tweener.js:208 (0x7f38c40df808 @ 159) Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: #9 0x7fff5f700eb0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f38c40c2bc0 @ 71) Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: #10 0x7fff5f700eb0 I resource:///org/gnome/shell/ui/tweener.js:183 (0x7f38c40df780 @ 20) Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: #11 0x7fff5f700f50 I self-hosted:917 (0x7f38c40ee5e8 @ 394) Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: == Stack trace for context 0x55c40593a000 == Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: #0 0x7fff5f700870 b resource:///org/gnome/shell/ui/tweener.js:80 (0x7f38c40ddef0 @ 82) Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: #1 0x7fff5f700910 b resource:///org/gnome/shell/ui/tweener.js:105 (0x7f38c40df230 @ 36) Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: #2 0x7fff5f7009b0 b resource:///org/gnome/shell/ui/tweener.js:92 (0x7f38c40df098 @ 52) Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: #3 0x7fff5f700a20 I resource:///org/gnome/gjs/modules/tweener/tweener.js:203 (0x7f38c40e9cd0 @ 54) Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: #4 0x7fff5f700b70 b resource:///org/gnome/gjs/modules/tweener/tweener.js:332 (0x7f38c40e9d58 @ 1626) Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: #5 0x7fff5f700c20 b resource:///org/gnome/gjs/modules/tweener/tweener.js:345 (0x7f38c40e9de0 @ 100) Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: #6 0x7fff5f700cb0 b resource:///org/gnome/gjs/modules/tweener/tweener.js:360 (0x7f38c40e9e68 @ 10) Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: #7 0x7fff5f700da0 b resource:///org/gnome/gjs/modules/signals.js:126 (0x7f38c40e2b38 @ 386) Feb 5 16:14:04 fog gnome-shell[5676]: Object Clutter.Actor (0x55c40613dde0), has been already finalized. Impossible to set any property to it. Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: #8 0x7fff5f700e50 b resource:///org/gnome/shell/ui/tweener.js:208 (0x7f38c40df808 @ 159) Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: #9 0x7fff5f700eb0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f38c40c2bc0 @ 71) Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: #10 0x7fff5f700eb0 I resource:///org/gnome/shell/ui/tweener.js:183 (0x7f38c40df780 @ 20) Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: #11 0x7fff5f700f50 I self-hosted:917 (0x7f38c40ee5e8 @ 394) Feb 5 16:14:04 fog gnome-shell[5676]: Object St.BoxLayout (0x55c407f24860), has been already finalized. Impossible to get any property from it. Feb 5 16:14:04 fog gnome-shell[5676]: Object St.BoxLayout (0x55c407f24860), has been already finalized. Impossible to set any property to it. Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: == Stack trace for context 0x55c40593a000 == Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: #0 0x7f
[Desktop-packages] [Bug 1747568] Re: Mouse clicks ignored in Wayland
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 1747568 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete ** Tags added: noclick wayland wayland-session ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => High -- 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/1747568 Title: Mouse clicks ignored in Wayland Status in gnome-shell package in Ubuntu: Incomplete Bug description: If I disable Wayland, mouse clicks start working again. Randomly started occurring sometime after initial install. Ubuntu 17.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1747568/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1730174] Re: [artful] mouse clicks are completely ignored both in Gnome's gdm and once logged in to the desktop
If you can instruct me on how to gather the pertinent information, I can make a report. Honestly though, it seems like the chances of some unique rare issue that few have is going to get much attention. If it comes to it that I need Wayland on this system, I'd sooner just reinstall which typically resets weird elusive configuration issues of which there could be many. It's too bad there isn't a financially backed bounty system somewhere for fixing bugs? I might pay into some reward to fix these odd issues that aren't likely to get much attention. -- 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/1730174 Title: [artful] mouse clicks are completely ignored both in Gnome's gdm and once logged in to the desktop Status in gnome-shell package in Ubuntu: Incomplete Bug description: After upgrading from 17.04 to 17.10, I encounter strange mouse issues, namely : - The mouse cursor moves allright - But mouse clicks are completely ignored both in Gnome's gdm and once logged in to the desktop, they are also ignored in all the Gnome panel and lef side dock. However, once started using keyboard, mouse DOES work INSIDE applications allright (all the times), and SOME windows can be moved by dragging their title bar when focus is given to them (i.e. I currently have a gedit window that I can move around with the mouse, while I cannot move a gnome-terminal or the firefox in which I type this text). Also, a directory/file selection dialog for the "save" action in gedit works perfectly well with the mouse. This is definitely not a hardware mouse issue. But I cannot change focus with the mouse, I have to [Alt]-[Tab] to change window. Also if I shift focus to the desktop, I can interact with icons on the desktop and the right-click on the background *may* work. I've purged all the .something config dirs in my homedir to no avail (and I don't believe it relates to it because gdm shows this behaviour even before I actually login). I've seen the exact same problem (after upgrade from 17.04 to 17.10) being reported on miscellaneous forums by at least 3 other people. So I'm not alone, but I have no clue. Trying to investigate this I checked a big part of my system's configuration and fell upon im-config. I have noticed that, when completely uninstalled (all the files that it refers to being removed), then reinstalled, this package actually FAILS installing any of its configuration files (but without any error message), resulting in the following situation : root@totor:~# dpkg -r --force depends im-config dpkg: im-config : problème de dépendance, mais suppression comme demandé : language-selector-gnome dépend de im-config (>= 0.29-1ubuntu10~). (Lecture de la base de données... 387605 fichiers et répertoires déjà installés.) Suppression de im-config (0.32-1ubuntu3) ... Traitement des actions différées (« triggers ») pour man-db (2.7.6.1-2) ... Traitement des actions différées (« triggers ») pour desktop-file-utils (0.23-1ubuntu3) ... Traitement des actions différées (« triggers ») pour gnome-menus (3.13.3-6ubuntu5) ... Traitement des actions différées (« triggers ») pour mime-support (3.60ubuntu1) ... root@totor:~# apt-get install im-config Lecture des listes de paquets... Fait Construction de l'arbre des dépendances Lecture des informations d'état... Fait Les NOUVEAUX paquets suivants seront installés : im-config 0 mis à jour, 1 nouvellement installés, 0 à enlever et 0 non mis à jour. Il est nécessaire de prendre 0 o/24,5 ko dans les archives. Après cette opération, 365 ko d'espace disque supplémentaires seront utilisés. Sélection du paquet im-config précédemment désélectionné. (Lecture de la base de données... 387551 fichiers et répertoires déjà installés.) Préparation du dépaquetage de .../im-config_0.32-1ubuntu3_all.deb ... Dépaquetage de im-config (0.32-1ubuntu3) ... Paramétrage de im-config (0.32-1ubuntu3) ... Traitement des actions différées (« triggers ») pour mime-support (3.60ubuntu1) ... Traitement des actions différées (« triggers ») pour desktop-file-utils (0.23-1ubuntu3) ... Traitement des actions différées (« triggers ») pour man-db (2.7.6.1-2) ... Traitement des actions différées (« triggers ») pour gnome-menus (3.13.3-6ubuntu5) ... root@totor:~# dpkg -V im-config ??5?? c /etc/X11/Xsession.d/70im-config_launch ??5?? c /etc/X11/xinit/xinputrc ??5?? c /etc/default/im-config ??5?? c /etc/profile.d/input-method-config.sh Any help greatly appreciated, my desktop being currently quite unusable. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: im-config 0.32-1ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20
[Desktop-packages] [Bug 1730174] Re: [artful] mouse clicks are completely ignored both in Gnome's gdm and once logged in to the desktop
Here it is: https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1747568 -- 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/1730174 Title: [artful] mouse clicks are completely ignored both in Gnome's gdm and once logged in to the desktop Status in gnome-shell package in Ubuntu: Incomplete Bug description: After upgrading from 17.04 to 17.10, I encounter strange mouse issues, namely : - The mouse cursor moves allright - But mouse clicks are completely ignored both in Gnome's gdm and once logged in to the desktop, they are also ignored in all the Gnome panel and lef side dock. However, once started using keyboard, mouse DOES work INSIDE applications allright (all the times), and SOME windows can be moved by dragging their title bar when focus is given to them (i.e. I currently have a gedit window that I can move around with the mouse, while I cannot move a gnome-terminal or the firefox in which I type this text). Also, a directory/file selection dialog for the "save" action in gedit works perfectly well with the mouse. This is definitely not a hardware mouse issue. But I cannot change focus with the mouse, I have to [Alt]-[Tab] to change window. Also if I shift focus to the desktop, I can interact with icons on the desktop and the right-click on the background *may* work. I've purged all the .something config dirs in my homedir to no avail (and I don't believe it relates to it because gdm shows this behaviour even before I actually login). I've seen the exact same problem (after upgrade from 17.04 to 17.10) being reported on miscellaneous forums by at least 3 other people. So I'm not alone, but I have no clue. Trying to investigate this I checked a big part of my system's configuration and fell upon im-config. I have noticed that, when completely uninstalled (all the files that it refers to being removed), then reinstalled, this package actually FAILS installing any of its configuration files (but without any error message), resulting in the following situation : root@totor:~# dpkg -r --force depends im-config dpkg: im-config : problème de dépendance, mais suppression comme demandé : language-selector-gnome dépend de im-config (>= 0.29-1ubuntu10~). (Lecture de la base de données... 387605 fichiers et répertoires déjà installés.) Suppression de im-config (0.32-1ubuntu3) ... Traitement des actions différées (« triggers ») pour man-db (2.7.6.1-2) ... Traitement des actions différées (« triggers ») pour desktop-file-utils (0.23-1ubuntu3) ... Traitement des actions différées (« triggers ») pour gnome-menus (3.13.3-6ubuntu5) ... Traitement des actions différées (« triggers ») pour mime-support (3.60ubuntu1) ... root@totor:~# apt-get install im-config Lecture des listes de paquets... Fait Construction de l'arbre des dépendances Lecture des informations d'état... Fait Les NOUVEAUX paquets suivants seront installés : im-config 0 mis à jour, 1 nouvellement installés, 0 à enlever et 0 non mis à jour. Il est nécessaire de prendre 0 o/24,5 ko dans les archives. Après cette opération, 365 ko d'espace disque supplémentaires seront utilisés. Sélection du paquet im-config précédemment désélectionné. (Lecture de la base de données... 387551 fichiers et répertoires déjà installés.) Préparation du dépaquetage de .../im-config_0.32-1ubuntu3_all.deb ... Dépaquetage de im-config (0.32-1ubuntu3) ... Paramétrage de im-config (0.32-1ubuntu3) ... Traitement des actions différées (« triggers ») pour mime-support (3.60ubuntu1) ... Traitement des actions différées (« triggers ») pour desktop-file-utils (0.23-1ubuntu3) ... Traitement des actions différées (« triggers ») pour man-db (2.7.6.1-2) ... Traitement des actions différées (« triggers ») pour gnome-menus (3.13.3-6ubuntu5) ... root@totor:~# dpkg -V im-config ??5?? c /etc/X11/Xsession.d/70im-config_launch ??5?? c /etc/X11/xinit/xinputrc ??5?? c /etc/default/im-config ??5?? c /etc/profile.d/input-method-config.sh Any help greatly appreciated, my desktop being currently quite unusable. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: im-config 0.32-1ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Nov 5 09:42:24 2017 EcryptfsInUse: Yes JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insuffi
[Desktop-packages] [Bug 1747568] [NEW] Mouse clicks ignored in Wayland
Public bug reported: If I disable Wayland, mouse clicks start working again. Randomly started occurring sometime after initial install. Ubuntu 17.10 ** 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/1747568 Title: Mouse clicks ignored in Wayland Status in gnome-shell package in Ubuntu: New Bug description: If I disable Wayland, mouse clicks start working again. Randomly started occurring sometime after initial install. Ubuntu 17.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1747568/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1736858] Re: package python-libxml2 2.9.4+dfsg1-2.2ubuntu0.1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 127
[Expired for libxml2 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: libxml2 (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libxml2 in Ubuntu. https://bugs.launchpad.net/bugs/1736858 Title: package python-libxml2 2.9.4+dfsg1-2.2ubuntu0.1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 127 Status in libxml2 package in Ubuntu: Expired Bug description: can't install it ProblemType: Package DistroRelease: Ubuntu 17.04 Package: python-libxml2 2.9.4+dfsg1-2.2ubuntu0.1 ProcVersionSignature: Ubuntu 4.10.0-40.44-generic 4.10.17 Uname: Linux 4.10.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu4.8 Architecture: amd64 Date: Thu Dec 7 12:47:53 2017 ErrorMessage: subprocess new pre-removal script returned error exit status 127 InstallationDate: Installed on 2017-12-03 (3 days ago) InstallationMedia: Ubuntu-Kylin 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4.6~17.04.1 SourcePackage: libxml2 Title: package python-libxml2 2.9.4+dfsg1-2.2ubuntu0.1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 127 UpgradeStatus: Upgraded to zesty on 2017-12-04 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxml2/+bug/1736858/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1714886] Re: gnome-shell crashed with SIGSEGV in meta_window_is_on_primary_monitor()
** Changed in: mutter Status: Confirmed => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1714886 Title: gnome-shell crashed with SIGSEGV in meta_window_is_on_primary_monitor() Status in GNOME Shell: Fix Released Status in Mutter: In Progress Status in gnome-shell package in Ubuntu: Fix Released Status in mutter package in Ubuntu: Fix Released Bug description: https://errors.ubuntu.com/problem/2248f9a7d43e5e9a3bba2ac8364590ed8b7361a7 --- This crash appears after login in, when gnome-shell restarts it seems to be stable. 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 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Sep 4 09:18:43 2017 DisplayManager: gdm3 EcryptfsInUse: Yes ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2017-04-03 (153 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) ProcCmdline: /usr/bin/gnome-shell SegvAnalysis: Segfault happened at: 0x7ff4e23f8b24 : mov0x2c(%rax),%eax PC (0x7ff4e23f8b24) ok source "0x2c(%rax)" (0x002c) not located in a known VMA region (needed readable region)! destination "%eax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: meta_window_is_on_primary_monitor () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 meta_window_on_all_workspaces_changed () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 meta_window_update_monitor () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 g_slist_foreach () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-shell crashed with SIGSEGV in meta_window_is_on_primary_monitor() UpgradeStatus: Upgraded to artful on 2017-08-31 (3 days ago) UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1714886/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1744696] Re: web interface fails on load
** Changed in: transmission (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to transmission in Ubuntu. https://bugs.launchpad.net/bugs/1744696 Title: web interface fails on load Status in transmission package in Ubuntu: Invalid Bug description: Upstream issue report (fixed in upstream version 2.92) https://github.com/transmission/transmission/issues/476 I am unable to connect to the remote web UI, or use any other remote control application. Transmission itself works, but I can't control it except by ssh-ing into the machine its running on with transmission- remote. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: transmission 2.84-3ubuntu3.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 Date: Mon Jan 22 21:57:36 2018 Dependencies: transmission-common 2.84-3ubuntu3.1 InstallationDate: Installed on 2013-06-24 (1673 days ago) InstallationMedia: Ubuntu-Server 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130214) PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: transmission UpgradeStatus: Upgraded to xenial on 2017-02-05 (351 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1744696/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1744696] Re: web interface fails on load
Hi Leonid, thanks for quick response, and sorry for my tardy reply (I had to fix a more pressing issue first). I went looking for the settings.json file you mention (for reference, I'm using https://anonscm.debian.org/cgit/collab- maint/transmission.git/tree/debian/settings.json?id=refs/heads/master ). Using the content there, I was able to trace the issue - my ancient config file didn't require the (now compulsory, I think) authentication. Regardless, it's now working. Please close this bug; thanks for your help. Richarrd -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to transmission in Ubuntu. https://bugs.launchpad.net/bugs/1744696 Title: web interface fails on load Status in transmission package in Ubuntu: New Bug description: Upstream issue report (fixed in upstream version 2.92) https://github.com/transmission/transmission/issues/476 I am unable to connect to the remote web UI, or use any other remote control application. Transmission itself works, but I can't control it except by ssh-ing into the machine its running on with transmission- remote. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: transmission 2.84-3ubuntu3.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 Date: Mon Jan 22 21:57:36 2018 Dependencies: transmission-common 2.84-3ubuntu3.1 InstallationDate: Installed on 2013-06-24 (1673 days ago) InstallationMedia: Ubuntu-Server 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130214) PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: transmission UpgradeStatus: Upgraded to xenial on 2017-02-05 (351 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1744696/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1747566] Re: org.gnome.Shell.desktop stacktraces; tweener.js
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/1747566 Title: org.gnome.Shell.desktop stacktraces; tweener.js Status in gnome-shell package in Ubuntu: Confirmed Bug description: I'm running Ubuntu Bionic. After latest dist-upgrade today I'm not getting a lot of stacktraces in my syslog: Feb 5 16:14:04 fog gnome-shell[5676]: Object Clutter.Actor (0x55c40613dde0), has been already finalized. Impossible to get any property from it. Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: == Stack trace for context 0x55c40593a000 == Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: #0 0x7fff5f700870 b resource:///org/gnome/shell/ui/tweener.js:73 (0x7f38c40ddef0 @ 9) Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: #1 0x7fff5f700910 b resource:///org/gnome/shell/ui/tweener.js:105 (0x7f38c40df230 @ 36) Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: #2 0x7fff5f7009b0 b resource:///org/gnome/shell/ui/tweener.js:92 (0x7f38c40df098 @ 52) Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: #3 0x7fff5f700a20 I resource:///org/gnome/gjs/modules/tweener/tweener.js:203 (0x7f38c40e9cd0 @ 54) Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: #4 0x7fff5f700b70 b resource:///org/gnome/gjs/modules/tweener/tweener.js:332 (0x7f38c40e9d58 @ 1626) Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: #5 0x7fff5f700c20 b resource:///org/gnome/gjs/modules/tweener/tweener.js:345 (0x7f38c40e9de0 @ 100) Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: #6 0x7fff5f700cb0 b resource:///org/gnome/gjs/modules/tweener/tweener.js:360 (0x7f38c40e9e68 @ 10) Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: #7 0x7fff5f700da0 b resource:///org/gnome/gjs/modules/signals.js:126 (0x7f38c40e2b38 @ 386) Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: #8 0x7fff5f700e50 b resource:///org/gnome/shell/ui/tweener.js:208 (0x7f38c40df808 @ 159) Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: #9 0x7fff5f700eb0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f38c40c2bc0 @ 71) Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: #10 0x7fff5f700eb0 I resource:///org/gnome/shell/ui/tweener.js:183 (0x7f38c40df780 @ 20) Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: #11 0x7fff5f700f50 I self-hosted:917 (0x7f38c40ee5e8 @ 394) Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: == Stack trace for context 0x55c40593a000 == Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: #0 0x7fff5f700870 b resource:///org/gnome/shell/ui/tweener.js:80 (0x7f38c40ddef0 @ 82) Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: #1 0x7fff5f700910 b resource:///org/gnome/shell/ui/tweener.js:105 (0x7f38c40df230 @ 36) Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: #2 0x7fff5f7009b0 b resource:///org/gnome/shell/ui/tweener.js:92 (0x7f38c40df098 @ 52) Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: #3 0x7fff5f700a20 I resource:///org/gnome/gjs/modules/tweener/tweener.js:203 (0x7f38c40e9cd0 @ 54) Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: #4 0x7fff5f700b70 b resource:///org/gnome/gjs/modules/tweener/tweener.js:332 (0x7f38c40e9d58 @ 1626) Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: #5 0x7fff5f700c20 b resource:///org/gnome/gjs/modules/tweener/tweener.js:345 (0x7f38c40e9de0 @ 100) Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: #6 0x7fff5f700cb0 b resource:///org/gnome/gjs/modules/tweener/tweener.js:360 (0x7f38c40e9e68 @ 10) Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: #7 0x7fff5f700da0 b resource:///org/gnome/gjs/modules/signals.js:126 (0x7f38c40e2b38 @ 386) Feb 5 16:14:04 fog gnome-shell[5676]: Object Clutter.Actor (0x55c40613dde0), has been already finalized. Impossible to set any property to it. Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: #8 0x7fff5f700e50 b resource:///org/gnome/shell/ui/tweener.js:208 (0x7f38c40df808 @ 159) Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: #9 0x7fff5f700eb0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f38c40c2bc0 @ 71) Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: #10 0x7fff5f700eb0 I resource:///org/gnome/shell/ui/tweener.js:183 (0x7f38c40df780 @ 20) Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: #11 0x7fff5f700f50 I self-hosted:917 (0x7f38c40ee5e8 @ 394) Feb 5 16:14:04 fog gnome-shell[5676]: Object St.BoxLayout (0x55c407f24860), has been already finalized. Impossible to get any property from it. Feb 5 16:14:04 fog gnome-shell[5676]: Object St.BoxLayout (0x55c407f24860), has been already finalized. Impossible to set any property to it. Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: == Stack trace for context 0x55c40593a000 == Feb 5 16:14:04 fog org.gnome.Shell.desktop[56
[Desktop-packages] [Bug 1747566] [NEW] org.gnome.Shell.desktop stacktraces; tweener.js
Public bug reported: I'm running Ubuntu Bionic. After latest dist-upgrade today I'm not getting a lot of stacktraces in my syslog: Feb 5 16:14:04 fog gnome-shell[5676]: Object Clutter.Actor (0x55c40613dde0), has been already finalized. Impossible to get any property from it. Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: == Stack trace for context 0x55c40593a000 == Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: #0 0x7fff5f700870 b resource:///org/gnome/shell/ui/tweener.js:73 (0x7f38c40ddef0 @ 9) Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: #1 0x7fff5f700910 b resource:///org/gnome/shell/ui/tweener.js:105 (0x7f38c40df230 @ 36) Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: #2 0x7fff5f7009b0 b resource:///org/gnome/shell/ui/tweener.js:92 (0x7f38c40df098 @ 52) Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: #3 0x7fff5f700a20 I resource:///org/gnome/gjs/modules/tweener/tweener.js:203 (0x7f38c40e9cd0 @ 54) Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: #4 0x7fff5f700b70 b resource:///org/gnome/gjs/modules/tweener/tweener.js:332 (0x7f38c40e9d58 @ 1626) Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: #5 0x7fff5f700c20 b resource:///org/gnome/gjs/modules/tweener/tweener.js:345 (0x7f38c40e9de0 @ 100) Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: #6 0x7fff5f700cb0 b resource:///org/gnome/gjs/modules/tweener/tweener.js:360 (0x7f38c40e9e68 @ 10) Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: #7 0x7fff5f700da0 b resource:///org/gnome/gjs/modules/signals.js:126 (0x7f38c40e2b38 @ 386) Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: #8 0x7fff5f700e50 b resource:///org/gnome/shell/ui/tweener.js:208 (0x7f38c40df808 @ 159) Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: #9 0x7fff5f700eb0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f38c40c2bc0 @ 71) Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: #10 0x7fff5f700eb0 I resource:///org/gnome/shell/ui/tweener.js:183 (0x7f38c40df780 @ 20) Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: #11 0x7fff5f700f50 I self-hosted:917 (0x7f38c40ee5e8 @ 394) Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: == Stack trace for context 0x55c40593a000 == Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: #0 0x7fff5f700870 b resource:///org/gnome/shell/ui/tweener.js:80 (0x7f38c40ddef0 @ 82) Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: #1 0x7fff5f700910 b resource:///org/gnome/shell/ui/tweener.js:105 (0x7f38c40df230 @ 36) Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: #2 0x7fff5f7009b0 b resource:///org/gnome/shell/ui/tweener.js:92 (0x7f38c40df098 @ 52) Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: #3 0x7fff5f700a20 I resource:///org/gnome/gjs/modules/tweener/tweener.js:203 (0x7f38c40e9cd0 @ 54) Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: #4 0x7fff5f700b70 b resource:///org/gnome/gjs/modules/tweener/tweener.js:332 (0x7f38c40e9d58 @ 1626) Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: #5 0x7fff5f700c20 b resource:///org/gnome/gjs/modules/tweener/tweener.js:345 (0x7f38c40e9de0 @ 100) Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: #6 0x7fff5f700cb0 b resource:///org/gnome/gjs/modules/tweener/tweener.js:360 (0x7f38c40e9e68 @ 10) Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: #7 0x7fff5f700da0 b resource:///org/gnome/gjs/modules/signals.js:126 (0x7f38c40e2b38 @ 386) Feb 5 16:14:04 fog gnome-shell[5676]: Object Clutter.Actor (0x55c40613dde0), has been already finalized. Impossible to set any property to it. Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: #8 0x7fff5f700e50 b resource:///org/gnome/shell/ui/tweener.js:208 (0x7f38c40df808 @ 159) Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: #9 0x7fff5f700eb0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f38c40c2bc0 @ 71) Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: #10 0x7fff5f700eb0 I resource:///org/gnome/shell/ui/tweener.js:183 (0x7f38c40df780 @ 20) Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: #11 0x7fff5f700f50 I self-hosted:917 (0x7f38c40ee5e8 @ 394) Feb 5 16:14:04 fog gnome-shell[5676]: Object St.BoxLayout (0x55c407f24860), has been already finalized. Impossible to get any property from it. Feb 5 16:14:04 fog gnome-shell[5676]: Object St.BoxLayout (0x55c407f24860), has been already finalized. Impossible to set any property to it. Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: == Stack trace for context 0x55c40593a000 == Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: #0 0x7fff5f6ff970 b resource:///org/gnome/shell/ui/tweener.js:73 (0x7f38c40ddef0 @ 9) Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: #1 0x7fff5f6ffa10 b resource:///org/gnome/shell/ui/tweener.js:105 (0x7f38c40df230 @ 36) Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: #2 0x7fff5f6ffab0 b resource:///org/gnome/shell/ui/tweener.js:92 (0x7f38c40df098 @ 52) Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: #3 0x7fff5f700a20 b resource:///org/gnome/gjs/modules/twee
[Desktop-packages] [Bug 1747488] Re: [GeForce GTX 1080] 17.10.1 DisplayPort 15m cable no display after starting "EFI VGA"
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 1747488 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. ** Summary changed: - 17.10.1 DisplayPort 15m cable no display after starting "EFI VGA" + [GeForce GTX 1080] 17.10.1 DisplayPort 15m cable no display after starting "EFI VGA" ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1747488 Title: [GeForce GTX 1080] 17.10.1 DisplayPort 15m cable no display after starting "EFI VGA" Status in gnome-shell package in Ubuntu: Incomplete 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1747488/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1747492] Re: [GeForce GTX 1080] 17.10.1 DisplayPort 15m cable monitor flickering
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 1747492 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. ** Summary changed: - 17.10.1 DisplayPort 15m cable monitor flickering + [GeForce GTX 1080] 17.10.1 DisplayPort 15m cable monitor flickering ** Package changed: gnome-shell (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1747492 Title: [GeForce GTX 1080] 17.10.1 DisplayPort 15m cable monitor flickering Status in linux package in Ubuntu: Incomplete Bug description: After installing 17.10.1, plugging in the 15m DisplayPort cable, it works, however, there is an unusable amount of screen tearing and flickering, and pixelated lines across the screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1747492/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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] [NEW] [GeForce GTX 1080] 17.10.1 DisplayPort 15m cable no display after starting "EFI VGA"
You have been subscribed to a public bug: 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 ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: Incomplete -- [GeForce GTX 1080] 17.10.1 DisplayPort 15m cable no display after starting "EFI VGA" https://bugs.launchpad.net/bugs/1747488 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1714459] Re: Shell font is blurry under Wayland (panels, menus and login screen too)
** Tags added: fixed-in-3.26.3 -- 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/1714459 Title: Shell font is blurry under Wayland (panels, menus and login screen too) Status in Mutter: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Status in mutter package in Ubuntu: In Progress Status in mutter package in Fedora: Confirmed Bug description: gnome-shell doesn't respect hinting and subpixel order under Wayland. Note that the Xorg session has the fix for this. Check the referenced bug for screenshots and comparing with the gtk renderer of decoration in the wired bugzilla bug. More context on the IRC discussion at https://irclogs.ubuntu.com/2017/09/01/%23ubuntu-desktop.html#t09:01 To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1714459/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1747410] Re: gnome-shell crashed with signal 5
*** This bug is a duplicate of bug 1505409 *** https://bugs.launchpad.net/bugs/1505409 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1505409, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1505409 gnome-shell crashed with SIGTRAP in x_io_error() from _XIOError() from _XEventsQueued() from XPending() from gdk_check_xpending() ["Connection to xwayland lost"] -- 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/1747410 Title: gnome-shell crashed with signal 5 Status in gnome-shell package in Ubuntu: Confirmed Bug description: Hello, I do not know why this happens... Regards, -- Cristian ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.26.2-0ubuntu2 Uname: Linux 4.15.1-041501-generic x86_64 ApportVersion: 2.20.8-0ubuntu8 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME-Greeter:GNOME Date: Mon Feb 5 09:00:13 2018 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2017-10-13 (114 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANGUAGE=es_CL:es PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_CL.UTF-8 SHELL=/bin/false Signal: 5 SourcePackage: gnome-shell StacktraceTop: () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 _XIOError () at /usr/lib/x86_64-linux-gnu/libX11.so.6 _XEventsQueued () at /usr/lib/x86_64-linux-gnu/libX11.so.6 XPending () at /usr/lib/x86_64-linux-gnu/libX11.so.6 () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 Title: gnome-shell crashed with signal 5 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/1747410/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1747448] Re: gnome-shell crashed with signal 5 in g_log_default_handler()
*** This bug is a duplicate of bug 1505409 *** https://bugs.launchpad.net/bugs/1505409 ** This bug is no longer a duplicate of bug 1747410 gnome-shell crashed with signal 5 ** This bug has been marked a duplicate of bug 1505409 gnome-shell crashed with SIGTRAP in x_io_error() from _XIOError() from _XEventsQueued() from XPending() from gdk_check_xpending() ["Connection to xwayland lost"] -- 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/1747448 Title: gnome-shell crashed with signal 5 in g_log_default_handler() Status in gnome-shell package in Ubuntu: New Bug description: Not sure if related but accompanied with problems with keyboard. Some keys did not work until restart. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.26.2-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.8-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME-Greeter:GNOME Date: Mon Feb 5 16:15:09 2018 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2018-02-01 (3 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180201) 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/1747448/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1744970] Re: Lowering some windows causes other, unrelated windows to also be lowered.
** Tags added: fixed-in-3.26.3 -- 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/1744970 Title: Lowering some windows causes other, unrelated windows to also be lowered. Status in gnome-shell package in Ubuntu: Triaged Status in mutter package in Ubuntu: Triaged Bug description: Steps to reproduce: 1. Open four windows, each using half of the screen: ┌──C──╥──D──┐ ┌──A──╥──B──┐ │┌──A─╨╥──B─┴┐ │ ║ │ ││ ║ │ │ ║ │ └┤ ║ │ └─╨─┘ └─╨─┘ 2D view3D view 2. Lower window A. Expected behavior: Window A is lowered: ┌──A──╥──D──┐ ┌──C──╥──B──┐ │┌──C─╨╥──B─┴┐ │ ║ │ ││ ║ │ │ ║ │ └┤ ║ │ └─╨─┘ └─╨─┘ 2D view3D view Actual behavior: Window A and window B are lowered: ┌──A──╥──B──┐ ┌──C──╥──D──┐ │┌──C─╨╥──D─┴┐ │ ║ │ ││ ║ │ │ ║ │ └┤ ║ │ └─╨─┘ └─╨─┘ 2D view3D view ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.2-0ubuntu0.1 ProcVersionSignature: Ubuntu 4.13.0-30.33-generic 4.13.13 Uname: Linux 4.13.0-30-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Jan 23 07:50:21 2018 DisplayManager: gdm3 InstallationDate: Installed on 2016-09-15 (495 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: gnome-shell UpgradeStatus: Upgraded to artful on 2018-01-21 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1744970/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1746874] Re: gnome-shell and Xwayland sometimes leave $HOME/core files (should be /var/crash files)
In case it's not clear to all readers yet; Xwayland and gnome-shell are co-dependent processes. If one crashes then the other will also crash. So we need apport to be capable of handling both crashes simultaneously. ** No longer affects: gnome-shell (Ubuntu) ** No longer affects: linux (Ubuntu) ** No longer affects: mutter (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1746874 Title: gnome-shell and Xwayland sometimes leave $HOME/core files (should be /var/crash files) Status in apport package in Ubuntu: Triaged Bug description: gnome-shell and Xwayland sometimes leave $HOME/core files (should be /var/crash files). This is despite: $ grep . /proc/sys/kernel/core_* /proc/sys/kernel/core_pattern:|/usr/share/apport/apport %p %s %c %d %P /proc/sys/kernel/core_pipe_limit:0 /proc/sys/kernel/core_uses_pid:0 So really there are two problems: 1. ~/core files are created but no /var/crash/ files 2. Because they all have the same name (core_uses_pid == 0), when gnome-shell crashes as a result of an Xwayland crash, you can only get the core from one of them at most. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.26.2-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 Uname: Linux 4.13.0-25-generic x86_64 ApportVersion: 2.20.8-0ubuntu7 Architecture: amd64 Date: Fri Feb 2 15:13:52 2018 DisplayManager: InstallationDate: Installed on 2017-12-12 (52 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.8-0ubuntu7 Architecture: amd64 CrashReports: 640:1000:118:3122469:2018-01-29 16:25:03.658845409 +0800:2018-02-02 15:39:18.799970611 +0800:/var/crash/_usr_bin_Xwayland.1000.crash 640:1000:118:24558024:2018-01-29 16:22:23.127058238 +0800:2018-02-02 15:39:18.887970685 +0800:/var/crash/_usr_bin_gdb.1000.crash 640:120:118:23982380:2018-01-29 15:52:09.799486456 +0800:2018-01-29 15:51:51.467493515 +0800:/var/crash/_usr_bin_gnome-shell.120.crash 640:1000:118:6315115:2018-01-29 16:18:12.723424671 +0800:2018-01-29 16:18:10.555428082 +0800:/var/crash/_usr_bin_gnome-shell.1000.crash 640:120:118:3103046:2018-01-29 15:52:12.923485257 +0800:2018-01-29 15:52:09.859486433 +0800:/var/crash/_usr_bin_Xwayland.120.crash DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2017-12-12 (52 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211) Package: mutter PackageArchitecture: all ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 Tags: bionic Uname: Linux 4.13.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1746874/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1316970] Re: g_dbus memory leak in lrmd
@ddstreet Could you please review V3 again? Thanks in advance! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1316970 Title: g_dbus memory leak in lrmd Status in glib2.0 package in Ubuntu: New Status in pacemaker package in Ubuntu: Fix Released Status in glib2.0 source package in Trusty: New Status in pacemaker source package in Trusty: In Progress Bug description: [Impact] lrmd daemon with upstart resource has memory leak in Trusty affected to pacemaker 1.1.10. affected to glib2.0 2.40.2-0ubuntu1 Please note that patch for pacemaker is created myself. [Test Case] 1. deploy 3 trusty instance. 2. install corosync, pacemaker, mysql. 3. setting with below info 3.1 corosync.conf, proper setting for 3 node 3.2 crm configure < setup.crm ( which has upstart:mysql setting ) 3.3 monitor lrmd daemon's memory usage [Regression] Restarting daemon after upgrading this pkg will be needed. this patch added NULL check for several parts. prior commit[1] changed file structure. and This change makes user changes usage of upstart:mysql to lsb:mysql. So I added free function myself. This might affect to system. For glib2.0, commit [1] is critical, but [2],[3],[4] is needed for building it. [Others] Related commits. [1] commit a7b61e276120184c7586a3217ed3571a982f5017 Author: Andrew Beekhof Date: Fri Aug 23 16:25:35 2013 +1000 Refactor: attrd: Move to its own directory and create a stub for attrd-ng -- $ git describe --contains a1a6922e43dfe80b23887a88401cbb93fe3645c0 Pacemaker-1.1.11-rc3 $ git describe --contains a7b61e276120184c7586a3217ed3571a982f5017 Pacemaker-1.1.11-rc1~168 $ rmadison pacemaker pacemaker | 1.1.10+git20130802-1ubuntu2 | trusty pacemaker | 1.1.10+git20130802-1ubuntu2.4 | trusty-security pacemaker | 1.1.10+git20130802-1ubuntu2.4 | trusty-updates pacemaker | 1.1.14-2ubuntu1 | xenial pacemaker | 1.1.14-2ubuntu1.3 | xenial-security pacemaker | 1.1.14-2ubuntu1.3 | xenial-update pacemaker | 1.1.16-1ubuntu1 | zesty pacemaker | 1.1.16-1ubuntu1 | artful pacemaker | 1.1.18~rc3-1ubuntu1 | bionic -- For glib [1] https://github.com/GNOME/glib/commit/db641e32920ee8b553ab6f2d318aafa156e4390c [2] https://github.com/GNOME/glib/commit/8792609e15394967cab526838b83f90acb401663 [3] https://github.com/GNOME/glib/commit/ec02a1875f29ecb8e46c0d8c1403cd00a0b3a9e4 [4] https://github.com/GNOME/glib/commit/f10b6550ff2ce55d06b92d6dc3e443fc007b2f7a [Original Description] I'm running Pacemaker 1.1.10+git20130802-1ubuntu1 on Ubuntu Saucy (13.10) and have encountered a memory leak in lrmd. The details of the bug are covered here in this thread (http://oss.clusterlabs.org/pipermail/pacemaker/2014-May/021689.html) but to summarise, the Pacemaker developers believe the leak is caused by the g_dbus API, the use of which was removed in Pacemaker 1.11. I've also attached the Valgrind output from the run that exposed the issue. Given that this issue affects production stability (a periodic restart of Pacemaker is required), will a version of 1.11 be released for Trusty? (I'm happy to upgrade the OS to Trusty to get it). If not, can you advise which version of the OS will be the first to take 1.11 please? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1316970/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1316970] Re: g_dbus memory leak in lrmd
For V3. It seems that g_variant_unref(value); part is needed. Added it again and no memory leaks. in g_variant_lookup_value, it calls g_variant_get_child_value so as you said. it need to be unref value as well i think. Thanks. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1316970 Title: g_dbus memory leak in lrmd Status in glib2.0 package in Ubuntu: New Status in pacemaker package in Ubuntu: Fix Released Status in glib2.0 source package in Trusty: New Status in pacemaker source package in Trusty: In Progress Bug description: [Impact] lrmd daemon with upstart resource has memory leak in Trusty affected to pacemaker 1.1.10. affected to glib2.0 2.40.2-0ubuntu1 Please note that patch for pacemaker is created myself. [Test Case] 1. deploy 3 trusty instance. 2. install corosync, pacemaker, mysql. 3. setting with below info 3.1 corosync.conf, proper setting for 3 node 3.2 crm configure < setup.crm ( which has upstart:mysql setting ) 3.3 monitor lrmd daemon's memory usage [Regression] Restarting daemon after upgrading this pkg will be needed. this patch added NULL check for several parts. prior commit[1] changed file structure. and This change makes user changes usage of upstart:mysql to lsb:mysql. So I added free function myself. This might affect to system. For glib2.0, commit [1] is critical, but [2],[3],[4] is needed for building it. [Others] Related commits. [1] commit a7b61e276120184c7586a3217ed3571a982f5017 Author: Andrew Beekhof Date: Fri Aug 23 16:25:35 2013 +1000 Refactor: attrd: Move to its own directory and create a stub for attrd-ng -- $ git describe --contains a1a6922e43dfe80b23887a88401cbb93fe3645c0 Pacemaker-1.1.11-rc3 $ git describe --contains a7b61e276120184c7586a3217ed3571a982f5017 Pacemaker-1.1.11-rc1~168 $ rmadison pacemaker pacemaker | 1.1.10+git20130802-1ubuntu2 | trusty pacemaker | 1.1.10+git20130802-1ubuntu2.4 | trusty-security pacemaker | 1.1.10+git20130802-1ubuntu2.4 | trusty-updates pacemaker | 1.1.14-2ubuntu1 | xenial pacemaker | 1.1.14-2ubuntu1.3 | xenial-security pacemaker | 1.1.14-2ubuntu1.3 | xenial-update pacemaker | 1.1.16-1ubuntu1 | zesty pacemaker | 1.1.16-1ubuntu1 | artful pacemaker | 1.1.18~rc3-1ubuntu1 | bionic -- For glib [1] https://github.com/GNOME/glib/commit/db641e32920ee8b553ab6f2d318aafa156e4390c [2] https://github.com/GNOME/glib/commit/8792609e15394967cab526838b83f90acb401663 [3] https://github.com/GNOME/glib/commit/ec02a1875f29ecb8e46c0d8c1403cd00a0b3a9e4 [4] https://github.com/GNOME/glib/commit/f10b6550ff2ce55d06b92d6dc3e443fc007b2f7a [Original Description] I'm running Pacemaker 1.1.10+git20130802-1ubuntu1 on Ubuntu Saucy (13.10) and have encountered a memory leak in lrmd. The details of the bug are covered here in this thread (http://oss.clusterlabs.org/pipermail/pacemaker/2014-May/021689.html) but to summarise, the Pacemaker developers believe the leak is caused by the g_dbus API, the use of which was removed in Pacemaker 1.11. I've also attached the Valgrind output from the run that exposed the issue. Given that this issue affects production stability (a periodic restart of Pacemaker is required), will a version of 1.11 be released for Trusty? (I'm happy to upgrade the OS to Trusty to get it). If not, can you advise which version of the OS will be the first to take 1.11 please? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1316970/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1730174] Re: [artful] mouse clicks are completely ignored both in Gnome's gdm and once logged in to the desktop
@enimga0, Wayland may not be the default in 18.04 but if it's going to be in better shape by 18.10 then we really have to stay focussed on fixing it. Judging by the bug reports I'm seeing, I don't share your confidence that your particular issue will fix itself before October. Because nobody else is reporting the same issue, so nobody else is working on fixing it yet. -- 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/1730174 Title: [artful] mouse clicks are completely ignored both in Gnome's gdm and once logged in to the desktop Status in gnome-shell package in Ubuntu: Incomplete Bug description: After upgrading from 17.04 to 17.10, I encounter strange mouse issues, namely : - The mouse cursor moves allright - But mouse clicks are completely ignored both in Gnome's gdm and once logged in to the desktop, they are also ignored in all the Gnome panel and lef side dock. However, once started using keyboard, mouse DOES work INSIDE applications allright (all the times), and SOME windows can be moved by dragging their title bar when focus is given to them (i.e. I currently have a gedit window that I can move around with the mouse, while I cannot move a gnome-terminal or the firefox in which I type this text). Also, a directory/file selection dialog for the "save" action in gedit works perfectly well with the mouse. This is definitely not a hardware mouse issue. But I cannot change focus with the mouse, I have to [Alt]-[Tab] to change window. Also if I shift focus to the desktop, I can interact with icons on the desktop and the right-click on the background *may* work. I've purged all the .something config dirs in my homedir to no avail (and I don't believe it relates to it because gdm shows this behaviour even before I actually login). I've seen the exact same problem (after upgrade from 17.04 to 17.10) being reported on miscellaneous forums by at least 3 other people. So I'm not alone, but I have no clue. Trying to investigate this I checked a big part of my system's configuration and fell upon im-config. I have noticed that, when completely uninstalled (all the files that it refers to being removed), then reinstalled, this package actually FAILS installing any of its configuration files (but without any error message), resulting in the following situation : root@totor:~# dpkg -r --force depends im-config dpkg: im-config : problème de dépendance, mais suppression comme demandé : language-selector-gnome dépend de im-config (>= 0.29-1ubuntu10~). (Lecture de la base de données... 387605 fichiers et répertoires déjà installés.) Suppression de im-config (0.32-1ubuntu3) ... Traitement des actions différées (« triggers ») pour man-db (2.7.6.1-2) ... Traitement des actions différées (« triggers ») pour desktop-file-utils (0.23-1ubuntu3) ... Traitement des actions différées (« triggers ») pour gnome-menus (3.13.3-6ubuntu5) ... Traitement des actions différées (« triggers ») pour mime-support (3.60ubuntu1) ... root@totor:~# apt-get install im-config Lecture des listes de paquets... Fait Construction de l'arbre des dépendances Lecture des informations d'état... Fait Les NOUVEAUX paquets suivants seront installés : im-config 0 mis à jour, 1 nouvellement installés, 0 à enlever et 0 non mis à jour. Il est nécessaire de prendre 0 o/24,5 ko dans les archives. Après cette opération, 365 ko d'espace disque supplémentaires seront utilisés. Sélection du paquet im-config précédemment désélectionné. (Lecture de la base de données... 387551 fichiers et répertoires déjà installés.) Préparation du dépaquetage de .../im-config_0.32-1ubuntu3_all.deb ... Dépaquetage de im-config (0.32-1ubuntu3) ... Paramétrage de im-config (0.32-1ubuntu3) ... Traitement des actions différées (« triggers ») pour mime-support (3.60ubuntu1) ... Traitement des actions différées (« triggers ») pour desktop-file-utils (0.23-1ubuntu3) ... Traitement des actions différées (« triggers ») pour man-db (2.7.6.1-2) ... Traitement des actions différées (« triggers ») pour gnome-menus (3.13.3-6ubuntu5) ... root@totor:~# dpkg -V im-config ??5?? c /etc/X11/Xsession.d/70im-config_launch ??5?? c /etc/X11/xinit/xinputrc ??5?? c /etc/default/im-config ??5?? c /etc/profile.d/input-method-config.sh Any help greatly appreciated, my desktop being currently quite unusable. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: im-config 0.32-1ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Nov 5 09:42:24 2017 EcryptfsInUse: Yes JournalErrors: Error: command ['journalctl', '-b', '--pr
[Desktop-packages] [Bug 1548006] Re: gnome-shell crashed with SIGSEGV in _gdk_window_has_impl() from gdk_x11_window_get_xid() from gtk_im_context_xim_filter_keypress()
^^^ That shows this bug stopped happening after 16.04 so if anyone would like to get a fix you will need to install Ubuntu 17.10 (or 18.04). ** Changed in: gnome-shell (Ubuntu) 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/1548006 Title: gnome-shell crashed with SIGSEGV in _gdk_window_has_impl() from gdk_x11_window_get_xid() from gtk_im_context_xim_filter_keypress() Status in gnome-shell package in Ubuntu: Fix Released Bug description: https://errors.ubuntu.com/problem/15cea21766411dfb0695dd32e40d9bfc23d82496 --- gnome-shell crashed with SIGSEGV in gdk_x11_window_get_xid() ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: gnome-shell 3.18.3-3ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1 Uname: Linux 4.4.0-6-generic x86_64 NonfreeKernelModules: openafs ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Feb 20 23:14:14 2016 DisplayManager: EcryptfsInUse: Yes ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2016-02-19 (1 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160218) ProcCmdline: /usr/bin/gnome-shell SegvAnalysis: Segfault happened at: 0x7ffaec3c76b2:cmp%rdi,0xe8(%rdi) PC (0x7ffaec3c76b2) ok source "%rdi" ok destination "0xe8(%rdi)" (0x00e8) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 gdk_x11_window_get_xid () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/gtk-3.0/3.0.0/immodules/im-xim.so ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/gnome-shell/libgnome-shell.so Title: gnome-shell crashed with SIGSEGV in gdk_x11_window_get_xid() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1548006/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1548006] Re: gnome-shell crashed with SIGSEGV in _gdk_window_has_impl() from gdk_x11_window_get_xid() from gtk_im_context_xim_filter_keypress()
Also tracking in: https://errors.ubuntu.com/problem/15cea21766411dfb0695dd32e40d9bfc23d82496 ** Description changed: + https://errors.ubuntu.com/problem/15cea21766411dfb0695dd32e40d9bfc23d82496 + + --- + gnome-shell crashed with SIGSEGV in gdk_x11_window_get_xid() ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: gnome-shell 3.18.3-3ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1 Uname: Linux 4.4.0-6-generic x86_64 NonfreeKernelModules: openafs ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Feb 20 23:14:14 2016 DisplayManager: - + EcryptfsInUse: Yes ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2016-02-19 (1 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160218) ProcCmdline: /usr/bin/gnome-shell SegvAnalysis: - Segfault happened at: 0x7ffaec3c76b2:cmp%rdi,0xe8(%rdi) - PC (0x7ffaec3c76b2) ok - source "%rdi" ok - destination "0xe8(%rdi)" (0x00e8) not located in a known VMA region (needed writable region)! + Segfault happened at: 0x7ffaec3c76b2:cmp%rdi,0xe8(%rdi) + PC (0x7ffaec3c76b2) ok + source "%rdi" ok + destination "0xe8(%rdi)" (0x00e8) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: - ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 - gdk_x11_window_get_xid () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 - ?? () from /usr/lib/x86_64-linux-gnu/gtk-3.0/3.0.0/immodules/im-xim.so - ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 - ?? () from /usr/lib/gnome-shell/libgnome-shell.so + ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 + gdk_x11_window_get_xid () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 + ?? () from /usr/lib/x86_64-linux-gnu/gtk-3.0/3.0.0/immodules/im-xim.so + ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 + ?? () from /usr/lib/gnome-shell/libgnome-shell.so Title: gnome-shell crashed with SIGSEGV in gdk_x11_window_get_xid() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo -- 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/1548006 Title: gnome-shell crashed with SIGSEGV in _gdk_window_has_impl() from gdk_x11_window_get_xid() from gtk_im_context_xim_filter_keypress() Status in gnome-shell package in Ubuntu: Fix Released Bug description: https://errors.ubuntu.com/problem/15cea21766411dfb0695dd32e40d9bfc23d82496 --- gnome-shell crashed with SIGSEGV in gdk_x11_window_get_xid() ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: gnome-shell 3.18.3-3ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1 Uname: Linux 4.4.0-6-generic x86_64 NonfreeKernelModules: openafs ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Feb 20 23:14:14 2016 DisplayManager: EcryptfsInUse: Yes ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2016-02-19 (1 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160218) ProcCmdline: /usr/bin/gnome-shell SegvAnalysis: Segfault happened at: 0x7ffaec3c76b2:cmp%rdi,0xe8(%rdi) PC (0x7ffaec3c76b2) ok source "%rdi" ok destination "0xe8(%rdi)" (0x00e8) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 gdk_x11_window_get_xid () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/gtk-3.0/3.0.0/immodules/im-xim.so ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/gnome-shell/libgnome-shell.so Title: gnome-shell crashed with SIGSEGV in gdk_x11_window_get_xid() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1548006/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1548006] Re: gnome-shell crashed with SIGSEGV in _gdk_window_has_impl() from gdk_x11_window_get_xid() from gtk_im_context_xim_filter_keypress()
This looks similar, but different, to bug 1743442. -- 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/1548006 Title: gnome-shell crashed with SIGSEGV in _gdk_window_has_impl() from gdk_x11_window_get_xid() from gtk_im_context_xim_filter_keypress() Status in gnome-shell package in Ubuntu: Fix Released Bug description: https://errors.ubuntu.com/problem/15cea21766411dfb0695dd32e40d9bfc23d82496 --- gnome-shell crashed with SIGSEGV in gdk_x11_window_get_xid() ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: gnome-shell 3.18.3-3ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1 Uname: Linux 4.4.0-6-generic x86_64 NonfreeKernelModules: openafs ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Feb 20 23:14:14 2016 DisplayManager: EcryptfsInUse: Yes ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2016-02-19 (1 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160218) ProcCmdline: /usr/bin/gnome-shell SegvAnalysis: Segfault happened at: 0x7ffaec3c76b2:cmp%rdi,0xe8(%rdi) PC (0x7ffaec3c76b2) ok source "%rdi" ok destination "0xe8(%rdi)" (0x00e8) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 gdk_x11_window_get_xid () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/gtk-3.0/3.0.0/immodules/im-xim.so ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/gnome-shell/libgnome-shell.so Title: gnome-shell crashed with SIGSEGV in gdk_x11_window_get_xid() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1548006/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1714989] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from st_label_set_text() from ffi_call_unix64()
** Tags added: fixed-in-3.26.3 -- 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/1714989 Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from st_label_set_text() from ffi_call_unix64() Status in GNOME Shell: Fix Released Status in gjs package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Bug description: Saw some reports with the same title but they're all for previous versions. error report: https://errors.ubuntu.com/problem/1c95cc2653ab00054b5d1764e41d974328a5f49d 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: nvidia_uvm nvidia ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Sep 4 16:52:13 2017 DisplayManager: gdm3 EcryptfsInUse: Yes ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2017-04-21 (135 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7fd97c8e7e5d : movzbl 0x16(%rax),%edx PC (0x7fd97c8e7e5d) ok source "0x16(%rax)" (0xeb1e) not located in a known VMA region (needed readable region)! destination "%edx" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: g_type_check_instance_cast () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 st_label_set_text () from /usr/lib/gnome-shell/libst-1.0.so ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6 ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6 ?? () from /usr/lib/libgjs.so.0 Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() 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/gnome-shell/+bug/1714989/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1724557] Re: gnome-shell crashed with SIGSEGV in meta_logical_monitor_get_scale()
** Tags added: fixed-in-3.26.3 -- 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/1724557 Title: gnome-shell crashed with SIGSEGV in meta_logical_monitor_get_scale() Status in Mutter: Fix Released Status in gnome-shell package in Ubuntu: Fix Committed Bug description: Hi all, Originally I was reporting bug 1717170, about session crash after monitor disconnect/switch-off/input change on desktop PC and the bug was fixed according to bug tracker. But now, after gnome-shell and mutter update, the crash goes worse. Now it is not just session kick-out but complete crash. Same events can be used to reproduce the crash. This time also crash files was created. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Oct 18 13:52:07 2017 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2017-09-11 (37 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170906) ProcCmdline: /usr/bin/gnome-shell SegvAnalysis: Segfault happened at: 0x7f475acbac30 : movss 0x38(%rdi),%xmm0 PC (0x7f475acbac30) ok source "0x38(%rdi)" (0x0038) not located in a known VMA region (needed readable region)! destination "%xmm0" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: meta_logical_monitor_get_scale () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 meta_window_wayland_get_geometry_scale () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 meta_surface_actor_wayland_get_scale () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 meta_surface_actor_wayland_sync_state () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 Title: gnome-shell crashed with SIGSEGV in meta_logical_monitor_get_scale() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1724557/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1181666] Re: gnome-shell randomly blocks mouse clicks from working in app windows
No, I think that's probably luck or an indirect side-effect. The issues with clicks being ignored are in the 'mutter' code. ** Package changed: gnome-shell (Ubuntu) => mutter (Ubuntu) ** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => High -- 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/1181666 Title: gnome-shell randomly blocks mouse clicks from working in app windows Status in GNOME Shell: Confirmed Status in Ubuntu GNOME: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: Under GNOME 3, the use of the mouse-click stops occasionally, though I can still move the mouse around and can still click on items in the Activities screen and the top-bar. I can use alt-tab to cycle windows and can still type into already- active textboxes in windows, but I cannot click within the windows, and the mouse is not picked up at all by the windows. I can open the alt-f2 "run command" dialogue, but cannot type into it. The workaround I'm using is to open terminal (ctrl-alt-T) and run "gnome-shell -r", and restarting that command every time I have the problem again. Please ask if there's anything I forgot to mention. ADDITIONAL: The error tends to happen randomly, but it seems to happen upon opening a new window, changing windows, closing windows, or opening the activities pane (whether a change of window is thus instigated or not) ADDITIONAL 2: (sorry, it's early) The other workaround is to log out and to log in again, but that is also less than ideal ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: gnome-shell 3.6.3.1-0ubuntu6 ProcVersionSignature: Ubuntu 3.8.0-22.33-generic 3.8.11 Uname: Linux 3.8.0-22-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Sun May 19 07:02:18 2013 DisplayManager: gdm GsettingsChanges: b'org.gnome.desktop.interface' b'clock-show-date' b'true' b'org.gnome.desktop.interface' b'clock-show-seconds' b'true' b'org.gnome.desktop.interface' b'document-font-name' b"'Sans 10'" b'org.gnome.desktop.interface' b'font-name' b"'Cantarell 10'" b'org.gnome.desktop.interface' b'monospace-font-name' b"'Ubuntu Mono 12'" InstallationDate: Installed on 2013-05-04 (14 days ago) InstallationMedia: Ubuntu-GNOME 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1181666/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1700092] Re: Text is tiny on HiDPI screens
** Changed in: gedit Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1700092 Title: Text is tiny on HiDPI screens Status in gedit: Fix Released Status in gedit package in Ubuntu: Confirmed Bug description: I am on Artful and have switched to GNOME as GNOME is the default desktop now and Unity shows some instabilities. I am using a Lenovo Thinkpad X1 Carbon (2nd gen.) notebook with 14-inch QHD (2560x1440) display, so I am well over the good old 72-dpi CRT resolution. With some effort I have at least got a somewhat useful scaling of the GUI elements (esp. text size), mainly by getting into Unity7, getting into the Display Settings there, removing my ~1.5 scaling factor, returning to GNOME, installing the advanced settings manager (gnome- tweak-tool or so) and setting a scaling factor of ~2). Large text in accessibilty does not work for me as it makes the text huge. Unfortunately gedit does not bother on these efforts, it seems to be hard-coded to 72 dpi and so the text is tiny, unusable not only for people with vision problems. As this is the default text editor, which is often also called by web browsers to display text files, this needs to get fixed. Please take this into account ASAP, ideally on 17.10 at the latest. Please consider backporting upstream fixes for achieving this goal. To manage notifications about this bug go to: https://bugs.launchpad.net/gedit/+bug/1700092/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1649566] Re: [GeForce 7025 / nForce 630a] System freeze
** Attachment removed: ""nouveau" related entries in "kern.log"" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1649566/+attachment/5049298/+files/nouveau.log -- 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/1649566 Title: [GeForce 7025 / nForce 630a] System freeze Status in xorg package in Ubuntu: Incomplete Bug description: Yesterday, I upgraded from Ubuntu 12.04 via 14.04 to 16.04. From 14.04 on, I was unable to graphically log in. A few seconds after the login (varying between 1 and 10 s), the screen changed to a pattern with dense white stripes on the violet/red background, and X froze (no reaction to mouse or keyboard). The latest messages in "/var/log/syslog" each time showed varying "nouveau E" problems, e.g. "unrecognized interupt", "PFIFO", or "PBUS" problems such as e.g.: "nouveau E[PBUS][:00:0d.0] MMIO write of 0x01f70001 FAULT at 0x00b010" (values and addresses varying). Usually, the freeze happens when e.g. "firefox" is started (which happens in my context automatically after a graphical login). In my case, the NVidia driver could not be started (I did not investigate why). Using boot parameter "nouveau.config=NvMSI=0" made the graphical login successful again. Today, I wanted to report the bug with "ubuntu-bug". However, during the collection of the system information, the error happened again (despite the "nouveau.config" boot parameter). Syslog gives: ... Dec 13 11:12:01 localhost CRON[5230]: (root) CMD ( test -x /etc/cron.daily/popularity-contest && /etc/cron.daily/popularity-contest --crond) Dec 13 11:14:16 localhost kernel: [ 6889.138599] nouveau E[ PBUS][:00:0d.0] MMIO write of 0x07920001 FAULT at 0x00b020 Dec 13 11:14:16 localhost kernel: [ 6889.140532] nouveau E[ PBUS][:00:0d.0] MMIO write of 0x07920001 FAULT at 0x00b020 Dec 13 11:14:59 localhost dbus[795]: [system] Activating service name='com.ubuntu.SoftwareProperties' (using servicehelper) Dec 13 11:14:59 localhost dbus[795]: [system] Successfully activated service 'com.ubuntu.SoftwareProperties' Dec 13 11:15:01 localhost CRON[5285]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1) Dec 13 11:17:01 localhost CRON[5303]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Dec 13 11:20:01 localhost CRON[5327]: (smmsp) CMD (test -x /etc/init.d/sendmail && test -x /usr/share/sendmail/sendmail && test -x /usr/lib/sm.bin/sendmail && /usr/share/sendmail/sendmail cron-msp) Dec 13 11:22:20 localhost kernel: [ 7372.621357] nouveau E[ PBUS][:00:0d.0] MMIO write of 0x FAULT at 0x00b020 Dec 13 11:25:01 localhost CRON[5580]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1) Dec 13 11:35:01 localhost CRON[5651]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1) Dec 13 11:38:02 localhost gnome-session[2248]: Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged. Dec 13 11:39:01 localhost CRON[5723]: (root) CMD ( [ -x /usr/lib/php5/maxlifetime ] && [ -x /usr/lib/php5/sessionclean ] && [ -d /var/lib/php5 ] && /usr/lib/php5/sessionclean /var/lib/php5 $(/usr/lib/php5/maxlifetime)) Dec 13 11:39:01 localhost CRON[5722]: (root) CMD ( [ -x /usr/lib/php/sessionclean ] && /usr/lib/php/sessionclean) Dec 13 11:39:46 localhost gnome-session[2248]: Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged. At this point, I had to reset the computer. --- ApportVersion: 2.20.1-0ubuntu2.15 Architecture: i386 CompizPlugins: [core,bailer,detection,composite,opengl,compiztoolbox,decor,move,resize,snap,place,grid,vpswitch,gnomecompat,mousepoll,imgpng,session,regex,animation,unitymtgrabhandles,workarounds,wall,fade,expo,ezoom,scale,unityshell] DistUpgraded: 2016-12-12 17:25:47,166 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation C61 [GeForce 7025 / nForce 630a] [10de:03d6] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ASRock Incorporation C61 [GeForce 7025 / nForce 630a] [1849:03d6] InstallationDate: Installed on 2013-01-21 (1838 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 (20120817.3) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: xorg 1:7.7+13ubuntu3 PackageArchitecture: i386 ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic root=UUID=9c03cebc-9cba-47bc-9974-5c236a34906e ro nouveau.config=NvMS
[Desktop-packages] [Bug 1747527] [NEW] High CPU Usage under Plasma
Public bug reported: Since Firefox was updated to version 58.0.1+build1-0ubuntu0.16.04.1 (xenial-updates), I noticed a consistent high CPU usage while Firefox was running under plasma (both by firefox and plasmashell processes). After a little inquiry, I tend to believe this is due to a global menu protocol compatibility issue (I use Plasma 5.12/Neon with global menu bar enabled). Facts that led me to that conclusion: 1 - Since Firefox 58 (xenial-updates, obviously patched for Unity global menu), Plasma's menu bar now displays a (surprisingly working) menu for Firefox. Previous implementations did not work at all (menus would show but not open when clicked). 2 - With current Firefox (xenial-updates), either disabling the global menu in Plasma, or disabling it in Firefox (setting ui.use_unity_menubar=false in about:config), makes CPU usage go down to normal levels. 3 - Before, I had been using Firefox 58beta (from webupd8 repository), which did not have this CPU issue... but no global menu either. Also, FYI: - A few months ago (until it was fixed), similar behaviour was exhibited by other pieces of software such as visual-studio-code and atom editor (both based on electron framework). They would hog a full CPU core, as long as they attempted to work with Plasma's global menu, but behave normally when global menu was disabled (either in plasma or in the incriminated editor). This latter fact proves it is possible for a piece of software to be compatible with both global menu implementations. Current status of Firefox in Ubuntu is actually very encouraging, as the global menu is now fully working even in Plasma. There only remains this CPU issue. Although Canonical does not officially endorse any KDE flavor of Ubuntu anymore, it would be much appreciated by Kubuntu and Neon users if this remaining little issue could be fixed! ** Affects: firefox (Ubuntu) Importance: Undecided Status: New -- 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/1747527 Title: High CPU Usage under Plasma Status in firefox package in Ubuntu: New Bug description: Since Firefox was updated to version 58.0.1+build1-0ubuntu0.16.04.1 (xenial-updates), I noticed a consistent high CPU usage while Firefox was running under plasma (both by firefox and plasmashell processes). After a little inquiry, I tend to believe this is due to a global menu protocol compatibility issue (I use Plasma 5.12/Neon with global menu bar enabled). Facts that led me to that conclusion: 1 - Since Firefox 58 (xenial-updates, obviously patched for Unity global menu), Plasma's menu bar now displays a (surprisingly working) menu for Firefox. Previous implementations did not work at all (menus would show but not open when clicked). 2 - With current Firefox (xenial-updates), either disabling the global menu in Plasma, or disabling it in Firefox (setting ui.use_unity_menubar=false in about:config), makes CPU usage go down to normal levels. 3 - Before, I had been using Firefox 58beta (from webupd8 repository), which did not have this CPU issue... but no global menu either. Also, FYI: - A few months ago (until it was fixed), similar behaviour was exhibited by other pieces of software such as visual-studio-code and atom editor (both based on electron framework). They would hog a full CPU core, as long as they attempted to work with Plasma's global menu, but behave normally when global menu was disabled (either in plasma or in the incriminated editor). This latter fact proves it is possible for a piece of software to be compatible with both global menu implementations. Current status of Firefox in Ubuntu is actually very encouraging, as the global menu is now fully working even in Plasma. There only remains this CPU issue. Although Canonical does not officially endorse any KDE flavor of Ubuntu anymore, it would be much appreciated by Kubuntu and Neon users if this remaining little issue could be fixed! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1747527/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1747276] Re: Firefox/Thunderbird busy wait at startup
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: firefox (Ubuntu) Status: New => Confirmed -- 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/1747276 Title: Firefox/Thunderbird busy wait at startup Status in firefox package in Ubuntu: Confirmed Status in thunderbird package in Ubuntu: Confirmed Bug description: Package firefox: i 57.0.1+build2-0ubuntu1bionic 500 << offending (main) p 58.0.1+build1-0ubuntu1bionic-proposed 500 << maybe offending p 59.0~b6+build1-0ubuntu0.18.04.1 bionic 500 << offending (PPA) Package firefox:i386: p 57.0.1+build2-0ubuntu1bionic 500 p 58.0.1+build1-0ubuntu1bionic-proposed 500 p 59.0~b6+build1-0ubuntu0.18.04.1 bionic 500 Firefox waits forever without a GUI at startup. I can not even start the profile manager. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1747276/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1747276] Re: Firefox/Thunderbird busy wait at startup
** Tags added: bionic -- 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/1747276 Title: Firefox/Thunderbird busy wait at startup Status in firefox package in Ubuntu: Confirmed Status in thunderbird package in Ubuntu: Confirmed Bug description: Package firefox: i 57.0.1+build2-0ubuntu1bionic 500 << offending (main) p 58.0.1+build1-0ubuntu1bionic-proposed 500 << maybe offending p 59.0~b6+build1-0ubuntu0.18.04.1 bionic 500 << offending (PPA) Package firefox:i386: p 57.0.1+build2-0ubuntu1bionic 500 p 58.0.1+build1-0ubuntu1bionic-proposed 500 p 59.0~b6+build1-0ubuntu0.18.04.1 bionic 500 Firefox waits forever without a GUI at startup. I can not even start the profile manager. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1747276/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1747276] Re: Firefox/Thunderbird busy wait at startup
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: thunderbird (Ubuntu) Status: New => Confirmed -- 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/1747276 Title: Firefox/Thunderbird busy wait at startup Status in firefox package in Ubuntu: Confirmed Status in thunderbird package in Ubuntu: Confirmed Bug description: Package firefox: i 57.0.1+build2-0ubuntu1bionic 500 << offending (main) p 58.0.1+build1-0ubuntu1bionic-proposed 500 << maybe offending p 59.0~b6+build1-0ubuntu0.18.04.1 bionic 500 << offending (PPA) Package firefox:i386: p 57.0.1+build2-0ubuntu1bionic 500 p 58.0.1+build1-0ubuntu1bionic-proposed 500 p 59.0~b6+build1-0ubuntu0.18.04.1 bionic 500 Firefox waits forever without a GUI at startup. I can not even start the profile manager. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1747276/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1747521] Re: gvfsd-mtp crashed with SIGSEGV
*** This bug is a duplicate of bug 1706097 *** https://bugs.launchpad.net/bugs/1706097 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 #1706097, 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/1747521/+attachment/5049427/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1747521/+attachment/5049429/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1747521/+attachment/5049432/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1747521/+attachment/5049433/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1747521/+attachment/5049434/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1747521/+attachment/5049435/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1747521/+attachment/5049436/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1706097 gvfsd-mtp crashed with SIGSEGV ** 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 gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1747521 Title: gvfsd-mtp crashed with SIGSEGV Status in gvfs package in Ubuntu: New Bug description: happened when unplugged the phone that has been charged. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gvfs-backends 1.34.1-1ubuntu4 Uname: Linux 4.15.1-041501-generic x86_64 ApportVersion: 2.20.8-0ubuntu8 Architecture: amd64 Date: Mon Feb 5 21:06:18 2018 ExecutablePath: /usr/lib/gvfs/gvfsd-mtp ProcCmdline: /usr/lib/gvfs/gvfsd-mtp --spawner :1.7 /org/gtk/gvfs/exec_spaw/3 ProcEnviron: LANG=en_GB.UTF-8 LANGUAGE=en_GB:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SegvAnalysis: Segfault happened at: 0x7f9b6a9a85a9:mov0x18(%rax),%rax PC (0x7f9b6a9a85a9) ok source "0x18(%rax)" (0x0018) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gvfs StacktraceTop: () at /usr/lib/x86_64-linux-gnu/gvfs/libgvfsdaemon.so () 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 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: gvfsd-mtp crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd netdev plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1747521/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1731940] Re: [P7xxDM2(-G), Realtek ALC898, Headphone Jack, External] No sound at all
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: alsa-driver (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1731940 Title: [P7xxDM2(-G), Realtek ALC898, Headphone Jack, External] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Bug description: Hello there, I have Ubuntu 16.04LTS installed on the Clevo P751DM2-G, also marketed as the Schenker XMG U507, the System76's Serval WS (2017 model), the Eurocom Sky X4E2, among others. The sound card is the Realtek ALC898 with the following output configuration: 1. One SPDIF/headphone combo jack (to the right) 2. One Line Out. 3. One Line-In. 4. One Mic-In. Background information: On Windows, one can use the Realtek HD Audio control panel pop-up menu on jack detection to set the output type when an audio device is plugged in to an appropriate jack, combined with Sound Blaster X-Fi MB5 software to enable post-processing effects such as Bass, noise cancellation, etc. What I have tried so far: 1. Setting the model definition at /etc/modprobe.d/sound.conf with the following entries: options snd-hda-intel model=no-primary-hp enable=1 index=0 Using such a line worked before on an MSI GS43VR 6RE Phantom Pro that also has the same (or a similar) ESS Sabre Audio DAC component. Expected behavior: When plugged into the microphone jack, the ESS Sabre DAC should be activated and sound should be routed to the headset. Observed anomaly: Sound comes out through the speakers instead. However, the line-out output works. In that case, when plugged into the line out, Audio works as expected. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 4.14.0 x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: lin2199 F pulseaudio /dev/snd/controlC0: lin2199 F pulseaudio CurrentDesktop: GNOME Date: Mon Nov 13 17:34:53 2017 InstallationDate: Installed on 2017-07-25 (111 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gdm1812 F pulseaudio lin2199 F pulseaudio /dev/snd/controlC0: gdm1812 F pulseaudio lin2199 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [P7xxDM2(-G), Realtek ALC898, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/21/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.06.04 dmi.board.asset.tag: Tag 12345 dmi.board.name: P7xxDM2(-G) dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.06.04:bd12/21/2016:svnNotebook:pnP7xxDM2(-G):pvrNotApplicable:rvnNotebook:rnP7xxDM2(-G):rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: P7xxDM2(-G) dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1731940/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1616332] Re: gnome-software using hundreds of MB of memory when not in use
> explain yourselves Ubuntu Never seen Ubuntu explaining anything, helping people with debugging or something like this in the last five years. Eventually the problem will go away some way or another, but even this event most likely won't get reported. So, don't expect too much. That said, clicking on "This bug affects xxx people, but not you" just under the bug title and adding one selfs to the list of affected people raises bug "heat", which I believe does make a distinction. -- 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/1616332 Title: gnome-software using hundreds of MB of memory when not in use Status in gnome-software package in Ubuntu: Triaged Bug description: It seems gnome-software is running in the background all the time. Not a big deal if it was lightweight, but it seems to use hundreds of MB (from smem output): PID User Command Swap USS PSS RSS 2291 jan /usr/bin/gnome-software --g 285436 112576 117982 134036 A total of over 400MB in RAM and swap combined. After killing and restarting, it takes "only" a bit over 100MB. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-software 3.20.1+git20160617.1.0440874.ubuntu-xenial-0ubuntu1~16.04.1 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 Uname: Linux 4.4.0-24-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Wed Aug 24 09:45:53 2016 InstallationDate: Installed on 2012-11-10 (1382 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) SourcePackage: gnome-software UpgradeStatus: Upgraded to xenial on 2016-06-19 (65 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1616332/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1744711] Re: Update gnome-terminal to 3.28 (vte 0.52)
** Patch added: "gnome-terminal-3.27.90 60_add_lp_handler.patch" https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1744711/+attachment/5049414/+files/60_add_lp_handler.patch -- 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/1744711 Title: Update gnome-terminal to 3.28 (vte 0.52) Status in gnome-terminal package in Ubuntu: Triaged Status in vte2.91 package in Ubuntu: Triaged Bug description: Followup of lp:1721412 18.04 LTS should ship gnome-terminal 3.28, libvte2.91 0.52 (assuming that it ships GNOME 3.28). This requires updating the PCRE2 patch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1744711/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1744711] Re: Update gnome-terminal to 3.28 (vte 0.52)
As per bug 1745825, I've dropped the code that decides whether to show/hide the "Use transparency from system theme" checkbox, it is now always shown. It shouldn't be that hard to bring it back. It'd need to be done manually; methods that received an extra parameter by this part of the patch now take different parameters in upstream, so the patch doesn't apply automatically. As this part of the code might cause a crash, I'm personally not motivated at all to bring back that crash, I vote for this patch which eliminates it. And as per that bug, bringing back this feature and fixing the bug in the same time is really nontrivial. ** Patch added: "gnome-terminal-3.27.90 0001-Restore-transparency.patch" https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1744711/+attachment/5049413/+files/0001-Restore-transparency.patch -- 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/1744711 Title: Update gnome-terminal to 3.28 (vte 0.52) Status in gnome-terminal package in Ubuntu: Triaged Status in vte2.91 package in Ubuntu: Triaged Bug description: Followup of lp:1721412 18.04 LTS should ship gnome-terminal 3.28, libvte2.91 0.52 (assuming that it ships GNOME 3.28). This requires updating the PCRE2 patch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1744711/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1744711] Re: Update gnome-terminal to 3.28 (vte 0.52)
** Patch added: "gnome-terminal-3.27.90 revert-pcre2.patch" https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1744711/+attachment/5049415/+files/revert-pcre2.patch -- 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/1744711 Title: Update gnome-terminal to 3.28 (vte 0.52) Status in gnome-terminal package in Ubuntu: Triaged Status in vte2.91 package in Ubuntu: Triaged Bug description: Followup of lp:1721412 18.04 LTS should ship gnome-terminal 3.28, libvte2.91 0.52 (assuming that it ships GNOME 3.28). This requires updating the PCRE2 patch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1744711/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1747509] 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/1747509 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: This greeted me as I logged in. ProblemType: Package DistroRelease: Ubuntu 17.10 Package: libsane1 1.0.27-1~experimental2ubuntu2.1 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 Date: Sun Feb 4 20:04:52 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-eTHUbf/46-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-06 (61 days ago) InstallationMedia: Ubuntu-MATE 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/1747509/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1737364] Re: 16.04: Fix CVE-2016-1968 and CVE-2016-1624 for brotli
This bug was fixed in the package brotli - 0.3.0+dfsg-2ubuntu1 --- brotli (0.3.0+dfsg-2ubuntu1) xenial-security; urgency=medium * SECURITY UPDATE: integer underflow in dec/decode.c (LP: #1737364) - debian/patches/fix-integer-underflow.patch: upstream patch via Debian - CVE-2016-1624 - CVE-2016-1968 -- Jeremy Bicha Sat, 09 Dec 2017 17:45:50 -0500 ** Changed in: brotli (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to brotli in Ubuntu. https://bugs.launchpad.net/bugs/1737364 Title: 16.04: Fix CVE-2016-1968 and CVE-2016-1624 for brotli Status in brotli package in Ubuntu: Fix Released Status in brotli source package in Xenial: Fix Released Bug description: Impact -- Integer underflow could be targeted as a buffer overflow https://security-tracker.debian.org/tracker/source-package/brotli Debdiff attached. Because brotli is embedded in web browsers for WOFF2 support (to be somewhat fixed by the proposed brotli MIR), this issue was already mentioned in https://usn.ubuntu.com/usn/USN-2917-1/ (Firefox) Luke Li discovered a buffer overflow during Brotli decompression in some circumstances. If a user were tricked in to opening a specially crafted website, an attacker could potentially exploit this to cause a denial of service via application crash, or execute arbitrary code with the privileges of the user invoking Firefox. (CVE-2016-1968) https://usn.ubuntu.com/usn/USN-2895-1/ (Oxide) An integer underflow was discovered in Brotli. If a user were tricked in to opening a specially crafted website, an attacker could potentially exploit this to cause a denial of service via application crash, or execute arbitrary code with the privileges of the user invoking the program. (CVE-2016-1624) Regression Potential This update was published in Debian unstable/testing as 0.3.0+dfsg-3 from late March to mid June 2016 when it was superseded by a newer version. The Ubuntu security sync tool wasn't able to retrieve this version now. brotli has no reverse dependencies in Ubuntu and is in universe. Testing Done Only a simple build test. There is a build test to ensure basic functionality of brotli with both python2 and python3. Other Info -- The main purpose of this security update is to clear up the security history section of MIR LP: #1737053. It is mentioned in the MIR bug that it is intended for brotli 1.0.2 to be backported to Ubuntu 16.04 and 17.10 as a security update (and promoted to main there), after 17.04 reaches End of Life. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brotli/+bug/1737364/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1747509] [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: This greeted me as I logged in. ProblemType: Package DistroRelease: Ubuntu 17.10 Package: libsane1 1.0.27-1~experimental2ubuntu2.1 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 Date: Sun Feb 4 20:04:52 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-eTHUbf/46-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-06 (61 days ago) InstallationMedia: Ubuntu-MATE 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) ** 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/1747509 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: This greeted me as I logged in. ProblemType: Package DistroRelease: Ubuntu 17.10 Package: libsane1 1.0.27-1~experimental2ubuntu2.1 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 Date: Sun Feb 4 20:04:52 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-eTHUbf/46-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-06 (61 days ago) InstallationMedia: Ubuntu-MATE 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/1747509/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1649566] Re: [GeForce 7025 / nForce 630a] System freeze
> 3) As per your snipped log, it looks like you are grabbing logs from your > install. What is > needed are the logs/video from booting > http://cdimage.ubuntu.com/daily-live/current/. You are right. All attachments come from the installation, not the "current" Ubuntu. I see no chance to get the DVD debugged: the failure is very early - likely immediately after the BIOS has passed control to the DVD. "https://wiki.ubuntu.com/DebuggingKernelBoot"; remains unapplicable, as no boot loader is involved (which would allow me to set boot parameters) or as the problem already occurs before the loader on the DVD gets activated. Likely, something went wrong with burning the DVD. I will try (probably tomorrow) to burn with a different device (I already tried with 2 different DVDs to exclude media failures). -- 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/1649566 Title: [GeForce 7025 / nForce 630a] System freeze Status in xorg package in Ubuntu: Incomplete Bug description: Yesterday, I upgraded from Ubuntu 12.04 via 14.04 to 16.04. From 14.04 on, I was unable to graphically log in. A few seconds after the login (varying between 1 and 10 s), the screen changed to a pattern with dense white stripes on the violet/red background, and X froze (no reaction to mouse or keyboard). The latest messages in "/var/log/syslog" each time showed varying "nouveau E" problems, e.g. "unrecognized interupt", "PFIFO", or "PBUS" problems such as e.g.: "nouveau E[PBUS][:00:0d.0] MMIO write of 0x01f70001 FAULT at 0x00b010" (values and addresses varying). Usually, the freeze happens when e.g. "firefox" is started (which happens in my context automatically after a graphical login). In my case, the NVidia driver could not be started (I did not investigate why). Using boot parameter "nouveau.config=NvMSI=0" made the graphical login successful again. Today, I wanted to report the bug with "ubuntu-bug". However, during the collection of the system information, the error happened again (despite the "nouveau.config" boot parameter). Syslog gives: ... Dec 13 11:12:01 localhost CRON[5230]: (root) CMD ( test -x /etc/cron.daily/popularity-contest && /etc/cron.daily/popularity-contest --crond) Dec 13 11:14:16 localhost kernel: [ 6889.138599] nouveau E[ PBUS][:00:0d.0] MMIO write of 0x07920001 FAULT at 0x00b020 Dec 13 11:14:16 localhost kernel: [ 6889.140532] nouveau E[ PBUS][:00:0d.0] MMIO write of 0x07920001 FAULT at 0x00b020 Dec 13 11:14:59 localhost dbus[795]: [system] Activating service name='com.ubuntu.SoftwareProperties' (using servicehelper) Dec 13 11:14:59 localhost dbus[795]: [system] Successfully activated service 'com.ubuntu.SoftwareProperties' Dec 13 11:15:01 localhost CRON[5285]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1) Dec 13 11:17:01 localhost CRON[5303]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Dec 13 11:20:01 localhost CRON[5327]: (smmsp) CMD (test -x /etc/init.d/sendmail && test -x /usr/share/sendmail/sendmail && test -x /usr/lib/sm.bin/sendmail && /usr/share/sendmail/sendmail cron-msp) Dec 13 11:22:20 localhost kernel: [ 7372.621357] nouveau E[ PBUS][:00:0d.0] MMIO write of 0x FAULT at 0x00b020 Dec 13 11:25:01 localhost CRON[5580]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1) Dec 13 11:35:01 localhost CRON[5651]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1) Dec 13 11:38:02 localhost gnome-session[2248]: Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged. Dec 13 11:39:01 localhost CRON[5723]: (root) CMD ( [ -x /usr/lib/php5/maxlifetime ] && [ -x /usr/lib/php5/sessionclean ] && [ -d /var/lib/php5 ] && /usr/lib/php5/sessionclean /var/lib/php5 $(/usr/lib/php5/maxlifetime)) Dec 13 11:39:01 localhost CRON[5722]: (root) CMD ( [ -x /usr/lib/php/sessionclean ] && /usr/lib/php/sessionclean) Dec 13 11:39:46 localhost gnome-session[2248]: Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged. At this point, I had to reset the computer. --- ApportVersion: 2.20.1-0ubuntu2.15 Architecture: i386 CompizPlugins: [core,bailer,detection,composite,opengl,compiztoolbox,decor,move,resize,snap,place,grid,vpswitch,gnomecompat,mousepoll,imgpng,session,regex,animation,unitymtgrabhandles,workarounds,wall,fade,expo,ezoom,scale,unityshell] DistUpgraded: 2016-12-12 17:25:47,166 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation C61 [GeForce 7025 / nForce 630a] [10de:03d6] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ASRock Incorporation C61 [GeForce 7025 / nForce 630a] [1849:03d6] Installati
[Desktop-packages] [Bug 1616332] Re: gnome-software using hundreds of MB of memory when not in use
explain yourselves Ubuntu -- 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/1616332 Title: gnome-software using hundreds of MB of memory when not in use Status in gnome-software package in Ubuntu: Triaged Bug description: It seems gnome-software is running in the background all the time. Not a big deal if it was lightweight, but it seems to use hundreds of MB (from smem output): PID User Command Swap USS PSS RSS 2291 jan /usr/bin/gnome-software --g 285436 112576 117982 134036 A total of over 400MB in RAM and swap combined. After killing and restarting, it takes "only" a bit over 100MB. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-software 3.20.1+git20160617.1.0440874.ubuntu-xenial-0ubuntu1~16.04.1 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 Uname: Linux 4.4.0-24-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Wed Aug 24 09:45:53 2016 InstallationDate: Installed on 2012-11-10 (1382 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) SourcePackage: gnome-software UpgradeStatus: Upgraded to xenial on 2016-06-19 (65 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1616332/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1649566] Re: [GeForce 7025 / nForce 630a] System freeze
** Attachment added: "Full dmesg" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1649566/+attachment/5049379/+files/dmesg -- 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/1649566 Title: [GeForce 7025 / nForce 630a] System freeze Status in xorg package in Ubuntu: Incomplete Bug description: Yesterday, I upgraded from Ubuntu 12.04 via 14.04 to 16.04. From 14.04 on, I was unable to graphically log in. A few seconds after the login (varying between 1 and 10 s), the screen changed to a pattern with dense white stripes on the violet/red background, and X froze (no reaction to mouse or keyboard). The latest messages in "/var/log/syslog" each time showed varying "nouveau E" problems, e.g. "unrecognized interupt", "PFIFO", or "PBUS" problems such as e.g.: "nouveau E[PBUS][:00:0d.0] MMIO write of 0x01f70001 FAULT at 0x00b010" (values and addresses varying). Usually, the freeze happens when e.g. "firefox" is started (which happens in my context automatically after a graphical login). In my case, the NVidia driver could not be started (I did not investigate why). Using boot parameter "nouveau.config=NvMSI=0" made the graphical login successful again. Today, I wanted to report the bug with "ubuntu-bug". However, during the collection of the system information, the error happened again (despite the "nouveau.config" boot parameter). Syslog gives: ... Dec 13 11:12:01 localhost CRON[5230]: (root) CMD ( test -x /etc/cron.daily/popularity-contest && /etc/cron.daily/popularity-contest --crond) Dec 13 11:14:16 localhost kernel: [ 6889.138599] nouveau E[ PBUS][:00:0d.0] MMIO write of 0x07920001 FAULT at 0x00b020 Dec 13 11:14:16 localhost kernel: [ 6889.140532] nouveau E[ PBUS][:00:0d.0] MMIO write of 0x07920001 FAULT at 0x00b020 Dec 13 11:14:59 localhost dbus[795]: [system] Activating service name='com.ubuntu.SoftwareProperties' (using servicehelper) Dec 13 11:14:59 localhost dbus[795]: [system] Successfully activated service 'com.ubuntu.SoftwareProperties' Dec 13 11:15:01 localhost CRON[5285]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1) Dec 13 11:17:01 localhost CRON[5303]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Dec 13 11:20:01 localhost CRON[5327]: (smmsp) CMD (test -x /etc/init.d/sendmail && test -x /usr/share/sendmail/sendmail && test -x /usr/lib/sm.bin/sendmail && /usr/share/sendmail/sendmail cron-msp) Dec 13 11:22:20 localhost kernel: [ 7372.621357] nouveau E[ PBUS][:00:0d.0] MMIO write of 0x FAULT at 0x00b020 Dec 13 11:25:01 localhost CRON[5580]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1) Dec 13 11:35:01 localhost CRON[5651]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1) Dec 13 11:38:02 localhost gnome-session[2248]: Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged. Dec 13 11:39:01 localhost CRON[5723]: (root) CMD ( [ -x /usr/lib/php5/maxlifetime ] && [ -x /usr/lib/php5/sessionclean ] && [ -d /var/lib/php5 ] && /usr/lib/php5/sessionclean /var/lib/php5 $(/usr/lib/php5/maxlifetime)) Dec 13 11:39:01 localhost CRON[5722]: (root) CMD ( [ -x /usr/lib/php/sessionclean ] && /usr/lib/php/sessionclean) Dec 13 11:39:46 localhost gnome-session[2248]: Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged. At this point, I had to reset the computer. --- ApportVersion: 2.20.1-0ubuntu2.15 Architecture: i386 CompizPlugins: [core,bailer,detection,composite,opengl,compiztoolbox,decor,move,resize,snap,place,grid,vpswitch,gnomecompat,mousepoll,imgpng,session,regex,animation,unitymtgrabhandles,workarounds,wall,fade,expo,ezoom,scale,unityshell] DistUpgraded: 2016-12-12 17:25:47,166 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation C61 [GeForce 7025 / nForce 630a] [10de:03d6] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ASRock Incorporation C61 [GeForce 7025 / nForce 630a] [1849:03d6] InstallationDate: Installed on 2013-01-21 (1838 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 (20120817.3) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: xorg 1:7.7+13ubuntu3 PackageArchitecture: i386 ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic root=UUID=9c03cebc-9cba-47bc-9974-5c236a34906e ro nouveau.config=NvMSI=0 ProcVersionSignature: Ubuntu 4.
[Desktop-packages] [Bug 1649566] Re: [GeForce 7025 / nForce 630a] System freeze
** Attachment added: "Full "kern.log"" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1649566/+attachment/5049380/+files/kern.log -- 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/1649566 Title: [GeForce 7025 / nForce 630a] System freeze Status in xorg package in Ubuntu: Incomplete Bug description: Yesterday, I upgraded from Ubuntu 12.04 via 14.04 to 16.04. From 14.04 on, I was unable to graphically log in. A few seconds after the login (varying between 1 and 10 s), the screen changed to a pattern with dense white stripes on the violet/red background, and X froze (no reaction to mouse or keyboard). The latest messages in "/var/log/syslog" each time showed varying "nouveau E" problems, e.g. "unrecognized interupt", "PFIFO", or "PBUS" problems such as e.g.: "nouveau E[PBUS][:00:0d.0] MMIO write of 0x01f70001 FAULT at 0x00b010" (values and addresses varying). Usually, the freeze happens when e.g. "firefox" is started (which happens in my context automatically after a graphical login). In my case, the NVidia driver could not be started (I did not investigate why). Using boot parameter "nouveau.config=NvMSI=0" made the graphical login successful again. Today, I wanted to report the bug with "ubuntu-bug". However, during the collection of the system information, the error happened again (despite the "nouveau.config" boot parameter). Syslog gives: ... Dec 13 11:12:01 localhost CRON[5230]: (root) CMD ( test -x /etc/cron.daily/popularity-contest && /etc/cron.daily/popularity-contest --crond) Dec 13 11:14:16 localhost kernel: [ 6889.138599] nouveau E[ PBUS][:00:0d.0] MMIO write of 0x07920001 FAULT at 0x00b020 Dec 13 11:14:16 localhost kernel: [ 6889.140532] nouveau E[ PBUS][:00:0d.0] MMIO write of 0x07920001 FAULT at 0x00b020 Dec 13 11:14:59 localhost dbus[795]: [system] Activating service name='com.ubuntu.SoftwareProperties' (using servicehelper) Dec 13 11:14:59 localhost dbus[795]: [system] Successfully activated service 'com.ubuntu.SoftwareProperties' Dec 13 11:15:01 localhost CRON[5285]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1) Dec 13 11:17:01 localhost CRON[5303]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Dec 13 11:20:01 localhost CRON[5327]: (smmsp) CMD (test -x /etc/init.d/sendmail && test -x /usr/share/sendmail/sendmail && test -x /usr/lib/sm.bin/sendmail && /usr/share/sendmail/sendmail cron-msp) Dec 13 11:22:20 localhost kernel: [ 7372.621357] nouveau E[ PBUS][:00:0d.0] MMIO write of 0x FAULT at 0x00b020 Dec 13 11:25:01 localhost CRON[5580]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1) Dec 13 11:35:01 localhost CRON[5651]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1) Dec 13 11:38:02 localhost gnome-session[2248]: Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged. Dec 13 11:39:01 localhost CRON[5723]: (root) CMD ( [ -x /usr/lib/php5/maxlifetime ] && [ -x /usr/lib/php5/sessionclean ] && [ -d /var/lib/php5 ] && /usr/lib/php5/sessionclean /var/lib/php5 $(/usr/lib/php5/maxlifetime)) Dec 13 11:39:01 localhost CRON[5722]: (root) CMD ( [ -x /usr/lib/php/sessionclean ] && /usr/lib/php/sessionclean) Dec 13 11:39:46 localhost gnome-session[2248]: Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged. At this point, I had to reset the computer. --- ApportVersion: 2.20.1-0ubuntu2.15 Architecture: i386 CompizPlugins: [core,bailer,detection,composite,opengl,compiztoolbox,decor,move,resize,snap,place,grid,vpswitch,gnomecompat,mousepoll,imgpng,session,regex,animation,unitymtgrabhandles,workarounds,wall,fade,expo,ezoom,scale,unityshell] DistUpgraded: 2016-12-12 17:25:47,166 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation C61 [GeForce 7025 / nForce 630a] [10de:03d6] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ASRock Incorporation C61 [GeForce 7025 / nForce 630a] [1849:03d6] InstallationDate: Installed on 2013-01-21 (1838 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 (20120817.3) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: xorg 1:7.7+13ubuntu3 PackageArchitecture: i386 ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic root=UUID=9c03cebc-9cba-47bc-9974-5c236a34906e ro nouveau.config=NvMSI=0 ProcVersionSignature: U
[Desktop-packages] [Bug 1737364] Re: 16.04: Fix CVE-2016-1968 and CVE-2016-1624 for brotli
ACK on the debdiff in comment #1. Package is building now and will be released as a security update. Thanks! ** Also affects: brotli (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: brotli (Ubuntu) Status: New => Fix Released ** Changed in: brotli (Ubuntu Xenial) Status: New => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to brotli in Ubuntu. https://bugs.launchpad.net/bugs/1737364 Title: 16.04: Fix CVE-2016-1968 and CVE-2016-1624 for brotli Status in brotli package in Ubuntu: Fix Released Status in brotli source package in Xenial: Fix Committed Bug description: Impact -- Integer underflow could be targeted as a buffer overflow https://security-tracker.debian.org/tracker/source-package/brotli Debdiff attached. Because brotli is embedded in web browsers for WOFF2 support (to be somewhat fixed by the proposed brotli MIR), this issue was already mentioned in https://usn.ubuntu.com/usn/USN-2917-1/ (Firefox) Luke Li discovered a buffer overflow during Brotli decompression in some circumstances. If a user were tricked in to opening a specially crafted website, an attacker could potentially exploit this to cause a denial of service via application crash, or execute arbitrary code with the privileges of the user invoking Firefox. (CVE-2016-1968) https://usn.ubuntu.com/usn/USN-2895-1/ (Oxide) An integer underflow was discovered in Brotli. If a user were tricked in to opening a specially crafted website, an attacker could potentially exploit this to cause a denial of service via application crash, or execute arbitrary code with the privileges of the user invoking the program. (CVE-2016-1624) Regression Potential This update was published in Debian unstable/testing as 0.3.0+dfsg-3 from late March to mid June 2016 when it was superseded by a newer version. The Ubuntu security sync tool wasn't able to retrieve this version now. brotli has no reverse dependencies in Ubuntu and is in universe. Testing Done Only a simple build test. There is a build test to ensure basic functionality of brotli with both python2 and python3. Other Info -- The main purpose of this security update is to clear up the security history section of MIR LP: #1737053. It is mentioned in the MIR bug that it is intended for brotli 1.0.2 to be backported to Ubuntu 16.04 and 17.10 as a security update (and promoted to main there), after 17.04 reaches End of Life. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brotli/+bug/1737364/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1181666] Re: gnome-shell randomly blocks mouse clicks from working in app windows
Upgrading from 4.13.0 to 4.14.15 did not solve the issue for me. -- 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/1181666 Title: gnome-shell randomly blocks mouse clicks from working in app windows Status in GNOME Shell: Confirmed Status in Ubuntu GNOME: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Bug description: Under GNOME 3, the use of the mouse-click stops occasionally, though I can still move the mouse around and can still click on items in the Activities screen and the top-bar. I can use alt-tab to cycle windows and can still type into already- active textboxes in windows, but I cannot click within the windows, and the mouse is not picked up at all by the windows. I can open the alt-f2 "run command" dialogue, but cannot type into it. The workaround I'm using is to open terminal (ctrl-alt-T) and run "gnome-shell -r", and restarting that command every time I have the problem again. Please ask if there's anything I forgot to mention. ADDITIONAL: The error tends to happen randomly, but it seems to happen upon opening a new window, changing windows, closing windows, or opening the activities pane (whether a change of window is thus instigated or not) ADDITIONAL 2: (sorry, it's early) The other workaround is to log out and to log in again, but that is also less than ideal ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: gnome-shell 3.6.3.1-0ubuntu6 ProcVersionSignature: Ubuntu 3.8.0-22.33-generic 3.8.11 Uname: Linux 3.8.0-22-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Sun May 19 07:02:18 2013 DisplayManager: gdm GsettingsChanges: b'org.gnome.desktop.interface' b'clock-show-date' b'true' b'org.gnome.desktop.interface' b'clock-show-seconds' b'true' b'org.gnome.desktop.interface' b'document-font-name' b"'Sans 10'" b'org.gnome.desktop.interface' b'font-name' b"'Cantarell 10'" b'org.gnome.desktop.interface' b'monospace-font-name' b"'Ubuntu Mono 12'" InstallationDate: Installed on 2013-05-04 (14 days ago) InstallationMedia: Ubuntu-GNOME 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1181666/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1649566] Re: [GeForce 7025 / nForce 630a] System freeze
Dieter Maurer: 1) Regarding logs, please don't cut, snip, extract, etc. Attach them in full. 2) To advise, please post dmesg in full. 3) As per your snipped log, it looks like you are grabbing logs from your install. What is needed are the logs/video from booting http://cdimage.ubuntu.com/daily-live/current/ . -- 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/1649566 Title: [GeForce 7025 / nForce 630a] System freeze Status in xorg package in Ubuntu: Incomplete Bug description: Yesterday, I upgraded from Ubuntu 12.04 via 14.04 to 16.04. From 14.04 on, I was unable to graphically log in. A few seconds after the login (varying between 1 and 10 s), the screen changed to a pattern with dense white stripes on the violet/red background, and X froze (no reaction to mouse or keyboard). The latest messages in "/var/log/syslog" each time showed varying "nouveau E" problems, e.g. "unrecognized interupt", "PFIFO", or "PBUS" problems such as e.g.: "nouveau E[PBUS][:00:0d.0] MMIO write of 0x01f70001 FAULT at 0x00b010" (values and addresses varying). Usually, the freeze happens when e.g. "firefox" is started (which happens in my context automatically after a graphical login). In my case, the NVidia driver could not be started (I did not investigate why). Using boot parameter "nouveau.config=NvMSI=0" made the graphical login successful again. Today, I wanted to report the bug with "ubuntu-bug". However, during the collection of the system information, the error happened again (despite the "nouveau.config" boot parameter). Syslog gives: ... Dec 13 11:12:01 localhost CRON[5230]: (root) CMD ( test -x /etc/cron.daily/popularity-contest && /etc/cron.daily/popularity-contest --crond) Dec 13 11:14:16 localhost kernel: [ 6889.138599] nouveau E[ PBUS][:00:0d.0] MMIO write of 0x07920001 FAULT at 0x00b020 Dec 13 11:14:16 localhost kernel: [ 6889.140532] nouveau E[ PBUS][:00:0d.0] MMIO write of 0x07920001 FAULT at 0x00b020 Dec 13 11:14:59 localhost dbus[795]: [system] Activating service name='com.ubuntu.SoftwareProperties' (using servicehelper) Dec 13 11:14:59 localhost dbus[795]: [system] Successfully activated service 'com.ubuntu.SoftwareProperties' Dec 13 11:15:01 localhost CRON[5285]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1) Dec 13 11:17:01 localhost CRON[5303]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Dec 13 11:20:01 localhost CRON[5327]: (smmsp) CMD (test -x /etc/init.d/sendmail && test -x /usr/share/sendmail/sendmail && test -x /usr/lib/sm.bin/sendmail && /usr/share/sendmail/sendmail cron-msp) Dec 13 11:22:20 localhost kernel: [ 7372.621357] nouveau E[ PBUS][:00:0d.0] MMIO write of 0x FAULT at 0x00b020 Dec 13 11:25:01 localhost CRON[5580]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1) Dec 13 11:35:01 localhost CRON[5651]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1) Dec 13 11:38:02 localhost gnome-session[2248]: Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged. Dec 13 11:39:01 localhost CRON[5723]: (root) CMD ( [ -x /usr/lib/php5/maxlifetime ] && [ -x /usr/lib/php5/sessionclean ] && [ -d /var/lib/php5 ] && /usr/lib/php5/sessionclean /var/lib/php5 $(/usr/lib/php5/maxlifetime)) Dec 13 11:39:01 localhost CRON[5722]: (root) CMD ( [ -x /usr/lib/php/sessionclean ] && /usr/lib/php/sessionclean) Dec 13 11:39:46 localhost gnome-session[2248]: Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged. At this point, I had to reset the computer. --- ApportVersion: 2.20.1-0ubuntu2.15 Architecture: i386 CompizPlugins: [core,bailer,detection,composite,opengl,compiztoolbox,decor,move,resize,snap,place,grid,vpswitch,gnomecompat,mousepoll,imgpng,session,regex,animation,unitymtgrabhandles,workarounds,wall,fade,expo,ezoom,scale,unityshell] DistUpgraded: 2016-12-12 17:25:47,166 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation C61 [GeForce 7025 / nForce 630a] [10de:03d6] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ASRock Incorporation C61 [GeForce 7025 / nForce 630a] [1849:03d6] InstallationDate: Installed on 2013-01-21 (1838 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 (20120817.3) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: xorg 1:7.7+13ubuntu3 PackageArchitecture: i386 ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHEL
[Desktop-packages] [Bug 1747488] Re: 17.10.1 DisplayPort 15m cable no display after starting "EFI VGA"
Related: https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1747492 -- 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/1747488 Title: 17.10.1 DisplayPort 15m cable no display after starting "EFI VGA" Status in gnome-shell package in Ubuntu: New 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1747488/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1747492] Re: 17.10.1 DisplayPort 15m cable monitor flickering
Related: https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1747488 -- 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/1747492 Title: 17.10.1 DisplayPort 15m cable monitor flickering Status in gnome-shell package in Ubuntu: New Bug description: After installing 17.10.1, plugging in the 15m DisplayPort cable, it works, however, there is an unusable amount of screen tearing and flickering, and pixelated lines across the screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1747492/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1747492] [NEW] 17.10.1 DisplayPort 15m cable monitor flickering
Public bug reported: After installing 17.10.1, plugging in the 15m DisplayPort cable, it works, however, there is an unusable amount of screen tearing and flickering, and pixelated lines across the screen ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: gnome-17.10 ** Tags added: gnome-17.10 -- 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/1747492 Title: 17.10.1 DisplayPort 15m cable monitor flickering Status in gnome-shell package in Ubuntu: New Bug description: After installing 17.10.1, plugging in the 15m DisplayPort cable, it works, however, there is an unusable amount of screen tearing and flickering, and pixelated lines across the screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1747492/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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] [NEW] 17.10.1 DisplayPort 15m cable no display after starting "EFI VGA"
Public bug reported: 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 ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Description changed: Ubuntu 17.10 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 ** Summary changed: - DisplayPort 15m cable no display after starting "EFI VGA" + 17.10.1 DisplayPort 15m cable no display after starting "EFI VGA" ** Description changed: - Ubuntu 17.10 boots into a black screen with no display, when switching + 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 ** Description changed: 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 + SSD : RAID0 2x Force MP500 120GB M.2-2280 + CSE : E4M20 iStarUSA 20-bay Chassis + PSU : Corsair CMPSU-850HX + MSE : Logitech G900 Chaos Spectrum + KYB : Happy Hacking Keyboard Pro v2 ** Description changed: 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 - SSD : RAID0 2x Force MP500 120GB M.2-2280 - CSE : E4M20 iStarUSA 20-bay Chassis - PSU : Corsair CMPSU-850HX - MSE : Logitech G900 Chaos Spectrum - KYB : Happy Hacking Keyboard Pro v2 -- 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/1747488 Title: 17.10.1 DisplayPort 15m cable no display after starting "EFI VGA" Status in gnome-shell package in Ubuntu: New 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1747488/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1649566] Re: [GeForce 7025 / nForce 630a] System freeze
> Then please post the results requested in
> https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1649566/comments/21
> so it may be reviewed.
Comment 21:
>> If still reproducible, please post results following:
>> https://wiki.ubuntu.com/DebuggingKernelBoot
This is not applicable as booting is successful
>> https://wiki.ubuntu.com/DebuggingSystemCrash
I reproduced the crash and tried "Alt+SysRq+1" followed by "Alt+SysRq+t".
As the display was frozen with the blue-white pattern I did not see a
traceback. After reboot,
I found in "kern.log":
Feb 5 19:05:10 localhost kernel: [ 4756.501608] nouveau :00:0d.0: bus:
MMIO write of 01b20001 FAULT at 00b020
Feb 5 19:05:11 localhost kernel: [ 4758.190584] nouveau :00:0d.0: bus:
MMIO write of FAULT at 00b020
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@Feb
5 19:07:22 localhost kernel: [0.00] Initializing cgroup subsys cpuset
I see many further "MMIO write of FAULT at 00b0[12]0" in "kern.log"
(I will attach the extract of "nouveau" messages from "kern.log").
Obiously, the kernel is in a very bad state. Do you see a good chance
that a crash kernel would get activated in the situation above?
> Did you checksum the ISO you downloaded?
Yes
> If so and it passed, you can make an ISO of what you burned and checksum this
> to confirm it burned correctly via a terminal:
> sudo dd if=/dev/sdX of=file.iso
Surprisingly "sudo dd if=/dev/sr0 of=file.iso" ("sr0" corresponds to my DVD
drive)
resulted in a much larger "file.iso" than the original Ubuntu ISO file (I
aborted the copy after "file.iso" grew up to about 2.7 GB (the Ubuntu ISO is
about 1.5 GB)).
When I mount the burned ISO file, the "properties" menu and "du -s" tell me the
correct size (thus, the "dd" copy may do something wrong).
--
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/1649566
Title:
[GeForce 7025 / nForce 630a] System freeze
Status in xorg package in Ubuntu:
Incomplete
Bug description:
Yesterday, I upgraded from Ubuntu 12.04 via 14.04 to 16.04. From 14.04
on, I was unable to graphically log in. A few seconds after the login
(varying between 1 and 10 s), the screen changed to a pattern with
dense white stripes on the violet/red background, and X froze (no
reaction to mouse or keyboard). The latest messages in
"/var/log/syslog" each time showed varying "nouveau E" problems, e.g.
"unrecognized interupt", "PFIFO", or "PBUS" problems such as e.g.:
"nouveau E[PBUS][:00:0d.0] MMIO write of 0x01f70001 FAULT at
0x00b010" (values and addresses varying).
Usually, the freeze happens when e.g. "firefox" is started (which
happens in my context automatically after a graphical login). In my
case, the NVidia driver could not be started (I did not investigate
why). Using boot parameter "nouveau.config=NvMSI=0" made the graphical
login successful again.
Today, I wanted to report the bug with "ubuntu-bug". However, during
the collection of the system information, the error happened again
(despite the "nouveau.config" boot parameter).
Syslog gives:
...
Dec 13 11:12:01 localhost CRON[5230]: (root) CMD ( test -x
/etc/cron.daily/popularity-contest && /etc/cron.daily/popularity-contest
--crond)
Dec 13 11:14:16 localhost kernel: [ 6889.138599] nouveau E[
PBUS][:00:0d.0] MMIO write of 0x07920001 FAULT at 0x00b020
Dec 13 11:14:16 localhost kernel: [ 6889.140532] nouveau E[
PBUS][:00:0d.0] MMIO write of 0x07920001 FAULT at 0x00b020
Dec 13 11:14:59 localhost dbus[795]: [system] Activating service
name='com.ubuntu.SoftwareProperties' (using servicehelper)
Dec 13 11:14:59 localhost dbus[795]: [system] Successfully activated service
'com.ubuntu.SoftwareProperties'
Dec 13 11:15:01 localhost CRON[5285]: (root) CMD (command -v debian-sa1 >
/dev/null && debian-sa1 1 1)
Dec 13 11:17:01 localhost CRON[5303]: (root) CMD ( cd / && run-parts
--report /etc/cron.hourly)
Dec 13 11:20:01 localhost CRON[5327]: (smmsp) CMD (test -x
/etc/init.d/sendmail && test -x /usr/share/sendmail/sendmail && tes
[Desktop-packages] [Bug 1649566] Re: [GeForce 7025 / nForce 630a] System freeze
** Attachment added: ""nouveau" related entries in "kern.log"" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1649566/+attachment/5049298/+files/nouveau.log -- 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/1649566 Title: [GeForce 7025 / nForce 630a] System freeze Status in xorg package in Ubuntu: Incomplete Bug description: Yesterday, I upgraded from Ubuntu 12.04 via 14.04 to 16.04. From 14.04 on, I was unable to graphically log in. A few seconds after the login (varying between 1 and 10 s), the screen changed to a pattern with dense white stripes on the violet/red background, and X froze (no reaction to mouse or keyboard). The latest messages in "/var/log/syslog" each time showed varying "nouveau E" problems, e.g. "unrecognized interupt", "PFIFO", or "PBUS" problems such as e.g.: "nouveau E[PBUS][:00:0d.0] MMIO write of 0x01f70001 FAULT at 0x00b010" (values and addresses varying). Usually, the freeze happens when e.g. "firefox" is started (which happens in my context automatically after a graphical login). In my case, the NVidia driver could not be started (I did not investigate why). Using boot parameter "nouveau.config=NvMSI=0" made the graphical login successful again. Today, I wanted to report the bug with "ubuntu-bug". However, during the collection of the system information, the error happened again (despite the "nouveau.config" boot parameter). Syslog gives: ... Dec 13 11:12:01 localhost CRON[5230]: (root) CMD ( test -x /etc/cron.daily/popularity-contest && /etc/cron.daily/popularity-contest --crond) Dec 13 11:14:16 localhost kernel: [ 6889.138599] nouveau E[ PBUS][:00:0d.0] MMIO write of 0x07920001 FAULT at 0x00b020 Dec 13 11:14:16 localhost kernel: [ 6889.140532] nouveau E[ PBUS][:00:0d.0] MMIO write of 0x07920001 FAULT at 0x00b020 Dec 13 11:14:59 localhost dbus[795]: [system] Activating service name='com.ubuntu.SoftwareProperties' (using servicehelper) Dec 13 11:14:59 localhost dbus[795]: [system] Successfully activated service 'com.ubuntu.SoftwareProperties' Dec 13 11:15:01 localhost CRON[5285]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1) Dec 13 11:17:01 localhost CRON[5303]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Dec 13 11:20:01 localhost CRON[5327]: (smmsp) CMD (test -x /etc/init.d/sendmail && test -x /usr/share/sendmail/sendmail && test -x /usr/lib/sm.bin/sendmail && /usr/share/sendmail/sendmail cron-msp) Dec 13 11:22:20 localhost kernel: [ 7372.621357] nouveau E[ PBUS][:00:0d.0] MMIO write of 0x FAULT at 0x00b020 Dec 13 11:25:01 localhost CRON[5580]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1) Dec 13 11:35:01 localhost CRON[5651]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1) Dec 13 11:38:02 localhost gnome-session[2248]: Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged. Dec 13 11:39:01 localhost CRON[5723]: (root) CMD ( [ -x /usr/lib/php5/maxlifetime ] && [ -x /usr/lib/php5/sessionclean ] && [ -d /var/lib/php5 ] && /usr/lib/php5/sessionclean /var/lib/php5 $(/usr/lib/php5/maxlifetime)) Dec 13 11:39:01 localhost CRON[5722]: (root) CMD ( [ -x /usr/lib/php/sessionclean ] && /usr/lib/php/sessionclean) Dec 13 11:39:46 localhost gnome-session[2248]: Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged. At this point, I had to reset the computer. --- ApportVersion: 2.20.1-0ubuntu2.15 Architecture: i386 CompizPlugins: [core,bailer,detection,composite,opengl,compiztoolbox,decor,move,resize,snap,place,grid,vpswitch,gnomecompat,mousepoll,imgpng,session,regex,animation,unitymtgrabhandles,workarounds,wall,fade,expo,ezoom,scale,unityshell] DistUpgraded: 2016-12-12 17:25:47,166 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation C61 [GeForce 7025 / nForce 630a] [10de:03d6] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ASRock Incorporation C61 [GeForce 7025 / nForce 630a] [1849:03d6] InstallationDate: Installed on 2013-01-21 (1838 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 (20120817.3) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: xorg 1:7.7+13ubuntu3 PackageArchitecture: i386 ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic root=UUID=9c03cebc-9cba-47bc-9974-5c236a34906e ro nouveau.config=NvMSI=
[Desktop-packages] [Bug 1747487] [NEW] Sonido
Public bug reported: No me reproduce sonido ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98 Uname: Linux 4.4.0-112-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Mon Feb 5 12:24:37 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation Device [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0767] InstallationDate: Installed on 2018-01-14 (21 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Dell Inc. Inspiron 5567 ProcEnviron: LANGUAGE=es_CR:es PATH=(custom, no user) LANG=es_CR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic.efi.signed root=UUID=6c7bacd6-3cb7-45a1-aae6-01b254d6be95 ro splash quiet SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/30/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.9 dmi.board.name: 01W6F7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.9:bd11/30/2016:svnDellInc.:pnInspiron5567:pvr:rvnDellInc.:rn01W6F7:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.name: Inspiron 5567 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.4 version.xserver-xorg-core: xserver-xorg-core 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: Mon Feb 5 12:20:03 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1317 vendor LGD xserver.version: 2:1.18.4-0ubuntu0.7 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 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/1747487 Title: Sonido Status in xorg package in Ubuntu: New Bug description: No me reproduce sonido ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98 Uname: Linux 4.4.0-112-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Mon Feb 5 12:24:37 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation Device [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0767] InstallationDate: Installed on 2018-01-14 (21 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Dell Inc. Inspiron 5567 ProcEnviron: LANGUAGE=es_CR:es PATH=(custom, no user) LANG=es_CR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic.efi.signed root=UUID=6c7bacd6-3cb7-45a1-aae6-01b254d6be95 ro splash quiet SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/30/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.9 dmi.board.name: 01W6F7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.9:bd11/30/2016:svnDellInc.:pnInspiron5567:pvr:rvnDellInc.:rn01W6F7:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.name: Inspiron 5567 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0u
[Desktop-packages] [Bug 1746874] Re: gnome-shell and Xwayland sometimes leave $HOME/core files (should be /var/crash files)
** Changed in: apport (Ubuntu) Status: Confirmed => Triaged ** Changed in: apport (Ubuntu) Importance: Undecided => High ** Tags added: rls-bb-incoming -- 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/1746874 Title: gnome-shell and Xwayland sometimes leave $HOME/core files (should be /var/crash files) Status in apport package in Ubuntu: Triaged Status in gnome-shell package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: gnome-shell and Xwayland sometimes leave $HOME/core files (should be /var/crash files). This is despite: $ grep . /proc/sys/kernel/core_* /proc/sys/kernel/core_pattern:|/usr/share/apport/apport %p %s %c %d %P /proc/sys/kernel/core_pipe_limit:0 /proc/sys/kernel/core_uses_pid:0 So really there are two problems: 1. ~/core files are created but no /var/crash/ files 2. Because they all have the same name (core_uses_pid == 0), when gnome-shell crashes as a result of an Xwayland crash, you can only get the core from one of them at most. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.26.2-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 Uname: Linux 4.13.0-25-generic x86_64 ApportVersion: 2.20.8-0ubuntu7 Architecture: amd64 Date: Fri Feb 2 15:13:52 2018 DisplayManager: InstallationDate: Installed on 2017-12-12 (52 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.8-0ubuntu7 Architecture: amd64 CrashReports: 640:1000:118:3122469:2018-01-29 16:25:03.658845409 +0800:2018-02-02 15:39:18.799970611 +0800:/var/crash/_usr_bin_Xwayland.1000.crash 640:1000:118:24558024:2018-01-29 16:22:23.127058238 +0800:2018-02-02 15:39:18.887970685 +0800:/var/crash/_usr_bin_gdb.1000.crash 640:120:118:23982380:2018-01-29 15:52:09.799486456 +0800:2018-01-29 15:51:51.467493515 +0800:/var/crash/_usr_bin_gnome-shell.120.crash 640:1000:118:6315115:2018-01-29 16:18:12.723424671 +0800:2018-01-29 16:18:10.555428082 +0800:/var/crash/_usr_bin_gnome-shell.1000.crash 640:120:118:3103046:2018-01-29 15:52:12.923485257 +0800:2018-01-29 15:52:09.859486433 +0800:/var/crash/_usr_bin_Xwayland.120.crash DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2017-12-12 (52 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211) Package: mutter PackageArchitecture: all ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 Tags: bionic Uname: Linux 4.13.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1746874/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1747474] [NEW] package libpoppler-glib8:amd64 0.57.0-2ubuntu4.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempti
Public bug reported: Impossible to remove and re-install. Message : libpoppler-glib8:amd64 (--configure) ProblemType: Package DistroRelease: Ubuntu 17.10 Package: libpoppler-glib8:amd64 0.57.0-2ubuntu4.2 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 AptOrdering: linux-firmware:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Mon Feb 5 18:15:06 2018 DpkgTerminalLog: Preparing to unpack .../linux-firmware_1.169.3_all.deb ... Unpacking linux-firmware (1.169.3) over (1.169.2) ... dpkg: error processing package libpoppler-glib8:amd64 (--configure): package is in a very bad inconsistent state; you should reinstall it before attempting configuration DuplicateSignature: package:libpoppler-glib8:amd64:0.57.0-2ubuntu4.2 Unpacking linux-firmware (1.169.3) over (1.169.2) ... dpkg: error processing package libpoppler-glib8:amd64 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2017-08-06 (182 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) 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: poppler Title: package libpoppler-glib8:amd64 0.57.0-2ubuntu4.2 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) ** Affects: poppler (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 poppler in Ubuntu. https://bugs.launchpad.net/bugs/1747474 Title: package libpoppler-glib8:amd64 0.57.0-2ubuntu4.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in poppler package in Ubuntu: New Bug description: Impossible to remove and re-install. Message : libpoppler-glib8:amd64 (--configure) ProblemType: Package DistroRelease: Ubuntu 17.10 Package: libpoppler-glib8:amd64 0.57.0-2ubuntu4.2 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 AptOrdering: linux-firmware:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Mon Feb 5 18:15:06 2018 DpkgTerminalLog: Preparing to unpack .../linux-firmware_1.169.3_all.deb ... Unpacking linux-firmware (1.169.3) over (1.169.2) ... dpkg: error processing package libpoppler-glib8:amd64 (--configure): package is in a very bad inconsistent state; you should reinstall it before attempting configuration DuplicateSignature: package:libpoppler-glib8:amd64:0.57.0-2ubuntu4.2 Unpacking linux-firmware (1.169.3) over (1.169.2) ... dpkg: error processing package libpoppler-glib8:amd64 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2017-08-06 (182 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) 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: poppler Title: package libpoppler-glib8:amd64 0.57.0-2ubuntu4.2 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/poppler/+bug/1747474/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1747474] Re: package libpoppler-glib8:amd64 0.57.0-2ubuntu4.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1747474 Title: package libpoppler-glib8:amd64 0.57.0-2ubuntu4.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in poppler package in Ubuntu: New Bug description: Impossible to remove and re-install. Message : libpoppler-glib8:amd64 (--configure) ProblemType: Package DistroRelease: Ubuntu 17.10 Package: libpoppler-glib8:amd64 0.57.0-2ubuntu4.2 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 AptOrdering: linux-firmware:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Mon Feb 5 18:15:06 2018 DpkgTerminalLog: Preparing to unpack .../linux-firmware_1.169.3_all.deb ... Unpacking linux-firmware (1.169.3) over (1.169.2) ... dpkg: error processing package libpoppler-glib8:amd64 (--configure): package is in a very bad inconsistent state; you should reinstall it before attempting configuration DuplicateSignature: package:libpoppler-glib8:amd64:0.57.0-2ubuntu4.2 Unpacking linux-firmware (1.169.3) over (1.169.2) ... dpkg: error processing package libpoppler-glib8:amd64 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2017-08-06 (182 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) 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: poppler Title: package libpoppler-glib8:amd64 0.57.0-2ubuntu4.2 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/poppler/+bug/1747474/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1714518] Re: GTK+3 doesn't show FUSE/GVFS, smb (SMB/CIFS), sftp (SFTP/SSH) network shares in file chooser
Never mind, found it: https://bugs.launchpad.net/launchpad/+bug/1747469
Sorry for the SPAM!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to transmission in Ubuntu.
https://bugs.launchpad.net/bugs/1714518
Title:
GTK+3 doesn't show FUSE/GVFS, smb (SMB/CIFS), sftp (SFTP/SSH) network
shares in file chooser
Status in GTK+:
Fix Released
Status in chromium-browser package in Ubuntu:
New
Status in deja-dup package in Ubuntu:
New
Status in firefox package in Ubuntu:
New
Status in gdebi package in Ubuntu:
New
Status in gtk+3.0 package in Ubuntu:
In Progress
Status in meld package in Ubuntu:
New
Status in remmina package in Ubuntu:
New
Status in thunderbird package in Ubuntu:
New
Status in transmission package in Ubuntu:
New
Status in usb-creator package in Ubuntu:
New
Status in vinagre package in Ubuntu:
New
Bug description:
Steps to reproduce:
1. Install any Gtk3 application such as Firefox or Chromium which use modern
file-chooser dialog.
2. Mount network location through fstab or file-manager ("smb://" = SMB/CIFS,
"sftp://"; = SFTP/SSH and so on)
3. Try to save/open file to/from the remote location from Gtk3 application.
Expected results:
* user is able to find network folder and save/open file to/from it with
GtkFileChooser dialog
Actual results:
* user is unable to find network folder and save/open file to/from it with
GtkFileChooser dialog and many user applications are affected
-
Original bug description is below:
GTK+3 doesn't show FUSE network shares in file chooser - it used to do
so in GTK+2, and the GTK+3 documentation still mentions it should do
it.
In the mean time, every user of every application switching to GTK+3
-- including Chromium, at some point between 58 and 60 -- (a change
which happened in 16.04 LTS!!), loses the functionality to open or
save directly to a network share.
I had chosen 16.04 LTS for deploying our workstations at work, and my 50
users have been suddenly unable to do a simple operation they have to do dozens
of times a day.
They now have to "buffer" these files to their local filesystem when saving
them and before uploading them, and then copy them to the company's network
shares.
They were already a little bit grumpy when it stopped working with Firefox,
and are now really side-eyeing me when they apply updates and find Chromium
broken.
I have reported the bug upstream and provided a patch to fix this. I
hope you'll be able and willing to include it to Ubuntu's GTK+3
package.
Thanks in advance.
Colin
To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/1714518/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1649566] Re: [GeForce 7025 / nForce 630a] System freeze
Dieter Maurer: >"I tried, but the resulting DVD does not boot:" Then please post the results requested in https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1649566/comments/21 so it may be reviewed. >"-- maybe, because it is for for the x64 platform while I typically use the i386 platform (however, my AMD Sempron should support x64)" Your CPU supports x64 as per AMD -> https://www.amd.com/en- us/products/processors/desktop/sempron-cpu# >"-- maybe due to a burning problem (the burning has been surprisingly fast; just some 10 s)." Did you checksum the ISO you downloaded? If so and it passed, you can make an ISO of what you burned and checksum this to confirm it burned correctly via a terminal: sudo dd if=/dev/sdX of=file.iso Where X is the letter for your cd drive. -- 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/1649566 Title: [GeForce 7025 / nForce 630a] System freeze Status in xorg package in Ubuntu: Incomplete Bug description: Yesterday, I upgraded from Ubuntu 12.04 via 14.04 to 16.04. From 14.04 on, I was unable to graphically log in. A few seconds after the login (varying between 1 and 10 s), the screen changed to a pattern with dense white stripes on the violet/red background, and X froze (no reaction to mouse or keyboard). The latest messages in "/var/log/syslog" each time showed varying "nouveau E" problems, e.g. "unrecognized interupt", "PFIFO", or "PBUS" problems such as e.g.: "nouveau E[PBUS][:00:0d.0] MMIO write of 0x01f70001 FAULT at 0x00b010" (values and addresses varying). Usually, the freeze happens when e.g. "firefox" is started (which happens in my context automatically after a graphical login). In my case, the NVidia driver could not be started (I did not investigate why). Using boot parameter "nouveau.config=NvMSI=0" made the graphical login successful again. Today, I wanted to report the bug with "ubuntu-bug". However, during the collection of the system information, the error happened again (despite the "nouveau.config" boot parameter). Syslog gives: ... Dec 13 11:12:01 localhost CRON[5230]: (root) CMD ( test -x /etc/cron.daily/popularity-contest && /etc/cron.daily/popularity-contest --crond) Dec 13 11:14:16 localhost kernel: [ 6889.138599] nouveau E[ PBUS][:00:0d.0] MMIO write of 0x07920001 FAULT at 0x00b020 Dec 13 11:14:16 localhost kernel: [ 6889.140532] nouveau E[ PBUS][:00:0d.0] MMIO write of 0x07920001 FAULT at 0x00b020 Dec 13 11:14:59 localhost dbus[795]: [system] Activating service name='com.ubuntu.SoftwareProperties' (using servicehelper) Dec 13 11:14:59 localhost dbus[795]: [system] Successfully activated service 'com.ubuntu.SoftwareProperties' Dec 13 11:15:01 localhost CRON[5285]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1) Dec 13 11:17:01 localhost CRON[5303]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Dec 13 11:20:01 localhost CRON[5327]: (smmsp) CMD (test -x /etc/init.d/sendmail && test -x /usr/share/sendmail/sendmail && test -x /usr/lib/sm.bin/sendmail && /usr/share/sendmail/sendmail cron-msp) Dec 13 11:22:20 localhost kernel: [ 7372.621357] nouveau E[ PBUS][:00:0d.0] MMIO write of 0x FAULT at 0x00b020 Dec 13 11:25:01 localhost CRON[5580]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1) Dec 13 11:35:01 localhost CRON[5651]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1) Dec 13 11:38:02 localhost gnome-session[2248]: Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged. Dec 13 11:39:01 localhost CRON[5723]: (root) CMD ( [ -x /usr/lib/php5/maxlifetime ] && [ -x /usr/lib/php5/sessionclean ] && [ -d /var/lib/php5 ] && /usr/lib/php5/sessionclean /var/lib/php5 $(/usr/lib/php5/maxlifetime)) Dec 13 11:39:01 localhost CRON[5722]: (root) CMD ( [ -x /usr/lib/php/sessionclean ] && /usr/lib/php/sessionclean) Dec 13 11:39:46 localhost gnome-session[2248]: Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged. At this point, I had to reset the computer. --- ApportVersion: 2.20.1-0ubuntu2.15 Architecture: i386 CompizPlugins: [core,bailer,detection,composite,opengl,compiztoolbox,decor,move,resize,snap,place,grid,vpswitch,gnomecompat,mousepoll,imgpng,session,regex,animation,unitymtgrabhandles,workarounds,wall,fade,expo,ezoom,scale,unityshell] DistUpgraded: 2016-12-12 17:25:47,166 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation C61 [GeForce 7025 / nForce 630a] [10de:03d6] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ASRock Incorporation C61 [GeForce 7025 / nForce 630a] [1849:03d6] InstallationDate: Installed on 2013-01-2
[Desktop-packages] [Bug 1747444] 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 1725928 *** https://bugs.launchpad.net/bugs/1725928 ** This bug has been marked a duplicate of bug 1725928 package libsane1 1.0.27-1~experimental2ubuntu1: multiarch packages with differing files -- 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/1747444 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: . ProblemType: Package DistroRelease: Ubuntu 17.10 Package: libsane1 1.0.27-1~experimental2ubuntu2.1 Uname: Linux 4.15.0-041500-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 Date: Mon Feb 5 15:23:52 2018 ErrorMessage: tentata sovrascrittura di "/lib/udev/hwdb.d/20-sane.hwdb" (condiviso), diverso da altre istanze del pacchetto libsane1:i386 InstallationDate: Installed on 2017-04-22 (289 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) 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/1747444/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1714518] Re: GTK+3 doesn't show FUSE/GVFS, smb (SMB/CIFS), sftp (SFTP/SSH) network shares in file chooser
OK so I'm _really_ glad to see the work on this bug progressing
and, as such, I've been attempting to "add myself" to this bug's
"affected user" list. However, I have _not_ been able to do so for the
past 2-weeks with the error message: "timeout, please try again later".
Does anybody know how to create a bug-report for Launchpad, itself?
Screenshot of bug, attached.
** Attachment added: "Timeout error after clicking the "me too" button"
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1714518/+attachment/5049260/+files/Screenshot_2018-02-05_10-19-35.png
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to transmission in Ubuntu.
https://bugs.launchpad.net/bugs/1714518
Title:
GTK+3 doesn't show FUSE/GVFS, smb (SMB/CIFS), sftp (SFTP/SSH) network
shares in file chooser
Status in GTK+:
Fix Released
Status in chromium-browser package in Ubuntu:
New
Status in deja-dup package in Ubuntu:
New
Status in firefox package in Ubuntu:
New
Status in gdebi package in Ubuntu:
New
Status in gtk+3.0 package in Ubuntu:
In Progress
Status in meld package in Ubuntu:
New
Status in remmina package in Ubuntu:
New
Status in thunderbird package in Ubuntu:
New
Status in transmission package in Ubuntu:
New
Status in usb-creator package in Ubuntu:
New
Status in vinagre package in Ubuntu:
New
Bug description:
Steps to reproduce:
1. Install any Gtk3 application such as Firefox or Chromium which use modern
file-chooser dialog.
2. Mount network location through fstab or file-manager ("smb://" = SMB/CIFS,
"sftp://"; = SFTP/SSH and so on)
3. Try to save/open file to/from the remote location from Gtk3 application.
Expected results:
* user is able to find network folder and save/open file to/from it with
GtkFileChooser dialog
Actual results:
* user is unable to find network folder and save/open file to/from it with
GtkFileChooser dialog and many user applications are affected
-
Original bug description is below:
GTK+3 doesn't show FUSE network shares in file chooser - it used to do
so in GTK+2, and the GTK+3 documentation still mentions it should do
it.
In the mean time, every user of every application switching to GTK+3
-- including Chromium, at some point between 58 and 60 -- (a change
which happened in 16.04 LTS!!), loses the functionality to open or
save directly to a network share.
I had chosen 16.04 LTS for deploying our workstations at work, and my 50
users have been suddenly unable to do a simple operation they have to do dozens
of times a day.
They now have to "buffer" these files to their local filesystem when saving
them and before uploading them, and then copy them to the company's network
shares.
They were already a little bit grumpy when it stopped working with Firefox,
and are now really side-eyeing me when they apply updates and find Chromium
broken.
I have reported the bug upstream and provided a patch to fix this. I
hope you'll be able and willing to include it to Ubuntu's GTK+3
package.
Thanks in advance.
Colin
To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/1714518/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1616332] Re: gnome-software using hundreds of MB of memory when not in use
I have 2 computers with Ubuntu 17.10 and both have the same issue: somehow it happens, that gnome-software occupies all spare memory, I've just killed the gnome-software process, because it occupied 9,1Gb out of 16Gb of my ram. -- 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/1616332 Title: gnome-software using hundreds of MB of memory when not in use Status in gnome-software package in Ubuntu: Triaged Bug description: It seems gnome-software is running in the background all the time. Not a big deal if it was lightweight, but it seems to use hundreds of MB (from smem output): PID User Command Swap USS PSS RSS 2291 jan /usr/bin/gnome-software --g 285436 112576 117982 134036 A total of over 400MB in RAM and swap combined. After killing and restarting, it takes "only" a bit over 100MB. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-software 3.20.1+git20160617.1.0440874.ubuntu-xenial-0ubuntu1~16.04.1 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 Uname: Linux 4.4.0-24-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Wed Aug 24 09:45:53 2016 InstallationDate: Installed on 2012-11-10 (1382 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) SourcePackage: gnome-software UpgradeStatus: Upgraded to xenial on 2016-06-19 (65 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1616332/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1724557] Re: gnome-shell crashed with SIGSEGV in meta_logical_monitor_get_scale()
@3v1n0: I suspect that this changeset -- which should be in 3.26.3 -- does the same: https://gitlab.gnome.org/GNOME/mutter/commit/71b4ef5940d16f7d3cb7dca5c224784315803492 -- 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/1724557 Title: gnome-shell crashed with SIGSEGV in meta_logical_monitor_get_scale() Status in Mutter: Fix Released Status in gnome-shell package in Ubuntu: Fix Committed Bug description: Hi all, Originally I was reporting bug 1717170, about session crash after monitor disconnect/switch-off/input change on desktop PC and the bug was fixed according to bug tracker. But now, after gnome-shell and mutter update, the crash goes worse. Now it is not just session kick-out but complete crash. Same events can be used to reproduce the crash. This time also crash files was created. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Oct 18 13:52:07 2017 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2017-09-11 (37 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170906) ProcCmdline: /usr/bin/gnome-shell SegvAnalysis: Segfault happened at: 0x7f475acbac30 : movss 0x38(%rdi),%xmm0 PC (0x7f475acbac30) ok source "0x38(%rdi)" (0x0038) not located in a known VMA region (needed readable region)! destination "%xmm0" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: meta_logical_monitor_get_scale () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 meta_window_wayland_get_geometry_scale () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 meta_surface_actor_wayland_get_scale () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 meta_surface_actor_wayland_sync_state () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 Title: gnome-shell crashed with SIGSEGV in meta_logical_monitor_get_scale() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1724557/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1747451] Re: package tex-common 6.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tex-common in Ubuntu. https://bugs.launchpad.net/bugs/1747451 Title: package tex-common 6.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in tex-common package in Ubuntu: New Bug description: notification states tex-common 6.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 synaptic or apport unable to fix problem ProblemType: Package DistroRelease: Ubuntu 16.04 Package: tex-common 6.04 ProcVersionSignature: Ubuntu 4.4.0-112.135-lowlatency 4.4.98 Uname: Linux 4.4.0-112-lowlatency x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Sun Feb 4 09:07:56 2018 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2012-09-22 (1962 days ago) InstallationMedia: Ubuntu-Studio 12.04.1 "Precise Pangolin" - Release amd64 (20120818) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.24 SourcePackage: tex-common Title: package tex-common 6.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2016-09-26 (497 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tex-common/+bug/1747451/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1747451] [NEW] package tex-common 6.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: notification states tex-common 6.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 synaptic or apport unable to fix problem ProblemType: Package DistroRelease: Ubuntu 16.04 Package: tex-common 6.04 ProcVersionSignature: Ubuntu 4.4.0-112.135-lowlatency 4.4.98 Uname: Linux 4.4.0-112-lowlatency x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Sun Feb 4 09:07:56 2018 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2012-09-22 (1962 days ago) InstallationMedia: Ubuntu-Studio 12.04.1 "Precise Pangolin" - Release amd64 (20120818) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.24 SourcePackage: tex-common Title: package tex-common 6.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2016-09-26 (497 days ago) ** Affects: tex-common (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tex-common in Ubuntu. https://bugs.launchpad.net/bugs/1747451 Title: package tex-common 6.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in tex-common package in Ubuntu: New Bug description: notification states tex-common 6.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 synaptic or apport unable to fix problem ProblemType: Package DistroRelease: Ubuntu 16.04 Package: tex-common 6.04 ProcVersionSignature: Ubuntu 4.4.0-112.135-lowlatency 4.4.98 Uname: Linux 4.4.0-112-lowlatency x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Sun Feb 4 09:07:56 2018 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2012-09-22 (1962 days ago) InstallationMedia: Ubuntu-Studio 12.04.1 "Precise Pangolin" - Release amd64 (20120818) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.24 SourcePackage: tex-common Title: package tex-common 6.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2016-09-26 (497 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tex-common/+bug/1747451/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1747456] [NEW] gnome-software process using 5.6 GiB of memory in the background
Public bug reported: gnome-software isn't open but is using 5.6 GiB of memory... See screenshot attached from System Monitor, I've ended the process (was getting a bit scary - using all my 2 GiB of swap and all my 8 GiB of RAM was all being used too) but if I can get appropriate logs from somewhere do tell me! :) ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-software 3.26.1-0ubuntu2.17.10.1 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Feb 5 15:57:42 2018 InstallationDate: Installed on 2017-08-03 (185 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-limba N/A gnome-software-plugin-snap3.26.1-0ubuntu2.17.10.1 SourcePackage: gnome-software UpgradeStatus: Upgraded to artful on 2017-10-21 (106 days ago) ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful ** Attachment added: "Screenshot from 2018-02-05 16-01-14.png" https://bugs.launchpad.net/bugs/1747456/+attachment/5049253/+files/Screenshot%20from%202018-02-05%2016-01-14.png -- 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/1747456 Title: gnome-software process using 5.6 GiB of memory in the background Status in gnome-software package in Ubuntu: New Bug description: gnome-software isn't open but is using 5.6 GiB of memory... See screenshot attached from System Monitor, I've ended the process (was getting a bit scary - using all my 2 GiB of swap and all my 8 GiB of RAM was all being used too) but if I can get appropriate logs from somewhere do tell me! :) ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-software 3.26.1-0ubuntu2.17.10.1 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Feb 5 15:57:42 2018 InstallationDate: Installed on 2017-08-03 (185 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-limba N/A gnome-software-plugin-snap3.26.1-0ubuntu2.17.10.1 SourcePackage: gnome-software UpgradeStatus: Upgraded to artful on 2017-10-21 (106 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1747456/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1637984] Re: Disks shows all mounted snaps
** Changed in: gnome-disk-utility Status: Unknown => Fix Released ** Changed in: gnome-disk-utility Importance: Unknown => Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1637984 Title: Disks shows all mounted snaps Status in GNOME Disks: Fix Released Status in gnome-disk-utility package in Ubuntu: In Progress Bug description: In 16.04 and later any installed snaps show as loop devices in Disks. While it is indeed a loop device I think it would be tidier if we could not show the snaps. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-disk-utility/+bug/1637984/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1724557] Re: gnome-shell crashed with SIGSEGV in meta_logical_monitor_get_scale()
@wdoekes Can you also attach [6] to that bug, or better, propose a merge proposal on mutter gitlab for that? -- 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/1724557 Title: gnome-shell crashed with SIGSEGV in meta_logical_monitor_get_scale() Status in Mutter: Fix Released Status in gnome-shell package in Ubuntu: Fix Committed Bug description: Hi all, Originally I was reporting bug 1717170, about session crash after monitor disconnect/switch-off/input change on desktop PC and the bug was fixed according to bug tracker. But now, after gnome-shell and mutter update, the crash goes worse. Now it is not just session kick-out but complete crash. Same events can be used to reproduce the crash. This time also crash files was created. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Oct 18 13:52:07 2017 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2017-09-11 (37 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170906) ProcCmdline: /usr/bin/gnome-shell SegvAnalysis: Segfault happened at: 0x7f475acbac30 : movss 0x38(%rdi),%xmm0 PC (0x7f475acbac30) ok source "0x38(%rdi)" (0x0038) not located in a known VMA region (needed readable region)! destination "%xmm0" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: meta_logical_monitor_get_scale () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 meta_window_wayland_get_geometry_scale () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 meta_surface_actor_wayland_get_scale () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 meta_surface_actor_wayland_sync_state () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 Title: gnome-shell crashed with SIGSEGV in meta_logical_monitor_get_scale() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1724557/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1747410] Re: gnome-shell crashed with signal 5
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/1747410 Title: gnome-shell crashed with signal 5 Status in gnome-shell package in Ubuntu: Confirmed Bug description: Hello, I do not know why this happens... Regards, -- Cristian ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.26.2-0ubuntu2 Uname: Linux 4.15.1-041501-generic x86_64 ApportVersion: 2.20.8-0ubuntu8 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME-Greeter:GNOME Date: Mon Feb 5 09:00:13 2018 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2017-10-13 (114 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANGUAGE=es_CL:es PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_CL.UTF-8 SHELL=/bin/false Signal: 5 SourcePackage: gnome-shell StacktraceTop: () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 _XIOError () at /usr/lib/x86_64-linux-gnu/libX11.so.6 _XEventsQueued () at /usr/lib/x86_64-linux-gnu/libX11.so.6 XPending () at /usr/lib/x86_64-linux-gnu/libX11.so.6 () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 Title: gnome-shell crashed with signal 5 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/1747410/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1730174] Re: [artful] mouse clicks are completely ignored both in Gnome's gdm and once logged in to the desktop
Ehh... Not really worth the trouble at this point as I've resolved it myself by just disabling Wayland. Since Wayland won't be default in 18.04 anyway, there's a good chance the issue will be fixed by 18.10. I've posted the same solution on an Ask Ubuntu question so it may help others. -- 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/1730174 Title: [artful] mouse clicks are completely ignored both in Gnome's gdm and once logged in to the desktop Status in gnome-shell package in Ubuntu: Incomplete Bug description: After upgrading from 17.04 to 17.10, I encounter strange mouse issues, namely : - The mouse cursor moves allright - But mouse clicks are completely ignored both in Gnome's gdm and once logged in to the desktop, they are also ignored in all the Gnome panel and lef side dock. However, once started using keyboard, mouse DOES work INSIDE applications allright (all the times), and SOME windows can be moved by dragging their title bar when focus is given to them (i.e. I currently have a gedit window that I can move around with the mouse, while I cannot move a gnome-terminal or the firefox in which I type this text). Also, a directory/file selection dialog for the "save" action in gedit works perfectly well with the mouse. This is definitely not a hardware mouse issue. But I cannot change focus with the mouse, I have to [Alt]-[Tab] to change window. Also if I shift focus to the desktop, I can interact with icons on the desktop and the right-click on the background *may* work. I've purged all the .something config dirs in my homedir to no avail (and I don't believe it relates to it because gdm shows this behaviour even before I actually login). I've seen the exact same problem (after upgrade from 17.04 to 17.10) being reported on miscellaneous forums by at least 3 other people. So I'm not alone, but I have no clue. Trying to investigate this I checked a big part of my system's configuration and fell upon im-config. I have noticed that, when completely uninstalled (all the files that it refers to being removed), then reinstalled, this package actually FAILS installing any of its configuration files (but without any error message), resulting in the following situation : root@totor:~# dpkg -r --force depends im-config dpkg: im-config : problème de dépendance, mais suppression comme demandé : language-selector-gnome dépend de im-config (>= 0.29-1ubuntu10~). (Lecture de la base de données... 387605 fichiers et répertoires déjà installés.) Suppression de im-config (0.32-1ubuntu3) ... Traitement des actions différées (« triggers ») pour man-db (2.7.6.1-2) ... Traitement des actions différées (« triggers ») pour desktop-file-utils (0.23-1ubuntu3) ... Traitement des actions différées (« triggers ») pour gnome-menus (3.13.3-6ubuntu5) ... Traitement des actions différées (« triggers ») pour mime-support (3.60ubuntu1) ... root@totor:~# apt-get install im-config Lecture des listes de paquets... Fait Construction de l'arbre des dépendances Lecture des informations d'état... Fait Les NOUVEAUX paquets suivants seront installés : im-config 0 mis à jour, 1 nouvellement installés, 0 à enlever et 0 non mis à jour. Il est nécessaire de prendre 0 o/24,5 ko dans les archives. Après cette opération, 365 ko d'espace disque supplémentaires seront utilisés. Sélection du paquet im-config précédemment désélectionné. (Lecture de la base de données... 387551 fichiers et répertoires déjà installés.) Préparation du dépaquetage de .../im-config_0.32-1ubuntu3_all.deb ... Dépaquetage de im-config (0.32-1ubuntu3) ... Paramétrage de im-config (0.32-1ubuntu3) ... Traitement des actions différées (« triggers ») pour mime-support (3.60ubuntu1) ... Traitement des actions différées (« triggers ») pour desktop-file-utils (0.23-1ubuntu3) ... Traitement des actions différées (« triggers ») pour man-db (2.7.6.1-2) ... Traitement des actions différées (« triggers ») pour gnome-menus (3.13.3-6ubuntu5) ... root@totor:~# dpkg -V im-config ??5?? c /etc/X11/Xsession.d/70im-config_launch ??5?? c /etc/X11/xinit/xinputrc ??5?? c /etc/default/im-config ??5?? c /etc/profile.d/input-method-config.sh Any help greatly appreciated, my desktop being currently quite unusable. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: im-config 0.32-1ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Nov 5 09:42:24 2017 EcryptfsInUse: Yes JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently n
[Desktop-packages] [Bug 1747448] Re: gnome-shell crashed with signal 5 in g_log_default_handler()
*** This bug is a duplicate of bug 1747410 *** https://bugs.launchpad.net/bugs/1747410 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 #1747410, 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/1747448/+attachment/5049228/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1747448/+attachment/5049230/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1747448/+attachment/5049234/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1747448/+attachment/5049235/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1747448/+attachment/5049236/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1747448/+attachment/5049237/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1747448/+attachment/5049238/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1747410 gnome-shell crashed with signal 5 ** 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/1747448 Title: gnome-shell crashed with signal 5 in g_log_default_handler() Status in gnome-shell package in Ubuntu: New Bug description: Not sure if related but accompanied with problems with keyboard. Some keys did not work until restart. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.26.2-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.8-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME-Greeter:GNOME Date: Mon Feb 5 16:15:09 2018 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2018-02-01 (3 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180201) 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/1747448/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1747276] Re: Firefox/Thunderbird busy wait at startup
Happens even in a live cd or a fresh install produced from it. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1747276 Title: Firefox/Thunderbird busy wait at startup Status in firefox package in Ubuntu: New Status in thunderbird package in Ubuntu: New Bug description: Package firefox: i 57.0.1+build2-0ubuntu1bionic 500 << offending (main) p 58.0.1+build1-0ubuntu1bionic-proposed 500 << maybe offending p 59.0~b6+build1-0ubuntu0.18.04.1 bionic 500 << offending (PPA) Package firefox:i386: p 57.0.1+build2-0ubuntu1bionic 500 p 58.0.1+build1-0ubuntu1bionic-proposed 500 p 59.0~b6+build1-0ubuntu0.18.04.1 bionic 500 Firefox waits forever without a GUI at startup. I can not even start the profile manager. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1747276/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1637984] Re: Disks shows all mounted snaps
** Changed in: gnome-disk-utility (Ubuntu) Status: Confirmed => In Progress ** Changed in: gnome-disk-utility (Ubuntu) Assignee: (unassigned) => Andrea Azzarone (azzar1) ** Bug watch added: GNOME Bug Tracker #790279 https://bugzilla.gnome.org/show_bug.cgi?id=790279 ** Also affects: gnome-disk-utility via https://bugzilla.gnome.org/show_bug.cgi?id=790279 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1637984 Title: Disks shows all mounted snaps Status in GNOME Disks: Unknown Status in gnome-disk-utility package in Ubuntu: In Progress Bug description: In 16.04 and later any installed snaps show as loop devices in Disks. While it is indeed a loop device I think it would be tidier if we could not show the snaps. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-disk-utility/+bug/1637984/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1726439] Re: Link copied with "Copy Link Address" cannot be pasted with Shift-Insert
This continues to be a real pain in day-to-day. Can we please fix this gnome-terminal regression? -- 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/1726439 Title: Link copied with "Copy Link Address" cannot be pasted with Shift- Insert Status in gnome-terminal package in Ubuntu: New Bug description: Steps to Reproduce -- 1) Open a new terminal 2) Run a command that will output a URL (e.g. `echo http://www.example.com`) 3) Right-click on the URL and select "Copy Link Address" 4) Press Shift-Insert. Expected Behaviour -- The copied link should be pasted where my cursor is. Actual Behaviour Nothing is pasted (or, sometimes, something I copied a while ago is; I haven't worked out a pattern to the source of the pasting). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-terminal 3.24.2-0ubuntu4 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Oct 23 10:52:24 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2014-09-04 (1145 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) SourcePackage: gnome-terminal UpgradeStatus: Upgraded to artful on 2016-12-05 (321 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1726439/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1747444] [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: . ProblemType: Package DistroRelease: Ubuntu 17.10 Package: libsane1 1.0.27-1~experimental2ubuntu2.1 Uname: Linux 4.15.0-041500-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 Date: Mon Feb 5 15:23:52 2018 ErrorMessage: tentata sovrascrittura di "/lib/udev/hwdb.d/20-sane.hwdb" (condiviso), diverso da altre istanze del pacchetto libsane1:i386 InstallationDate: Installed on 2017-04-22 (289 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) 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/1747444 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: . ProblemType: Package DistroRelease: Ubuntu 17.10 Package: libsane1 1.0.27-1~experimental2ubuntu2.1 Uname: Linux 4.15.0-041500-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 Date: Mon Feb 5 15:23:52 2018 ErrorMessage: tentata sovrascrittura di "/lib/udev/hwdb.d/20-sane.hwdb" (condiviso), diverso da altre istanze del pacchetto libsane1:i386 InstallationDate: Installed on 2017-04-22 (289 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) 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/1747444/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1714989] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from st_label_set_text() from ffi_call_unix64()
** Tags added: bionic -- 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/1714989 Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from st_label_set_text() from ffi_call_unix64() Status in GNOME Shell: Fix Released Status in gjs package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Bug description: Saw some reports with the same title but they're all for previous versions. error report: https://errors.ubuntu.com/problem/1c95cc2653ab00054b5d1764e41d974328a5f49d 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: nvidia_uvm nvidia ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Sep 4 16:52:13 2017 DisplayManager: gdm3 EcryptfsInUse: Yes ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2017-04-21 (135 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7fd97c8e7e5d : movzbl 0x16(%rax),%edx PC (0x7fd97c8e7e5d) ok source "0x16(%rax)" (0xeb1e) not located in a known VMA region (needed readable region)! destination "%edx" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: g_type_check_instance_cast () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 st_label_set_text () from /usr/lib/gnome-shell/libst-1.0.so ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6 ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6 ?? () from /usr/lib/libgjs.so.0 Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() 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/gnome-shell/+bug/1714989/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1747433] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast()
*** This bug is a duplicate of bug 1714989 *** https://bugs.launchpad.net/bugs/1714989 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 #1714989, 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/1747433/+attachment/5049179/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1747433/+attachment/5049181/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1747433/+attachment/5049186/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1747433/+attachment/5049187/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1747433/+attachment/5049188/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1747433/+attachment/5049189/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1747433/+attachment/5049190/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1714989 gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from st_label_set_text() from ffi_call_unix64() ** 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/1747433 Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() Status in gnome-shell package in Ubuntu: New Bug description: Occurred after return from lock screen. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.26.2-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.8-0ubuntu8 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Mon Feb 5 11:25:37 2018 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2018-01-11 (25 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180101) ProcCmdline: /usr/bin/gnome-shell SegvAnalysis: Segfault happened at: 0x7f57e2b6be0d : movzbl 0x16(%rax),%edx PC (0x7f57e2b6be0d) ok source "0x16(%rax)" (0xf6000816) not located in a known VMA region (needed readable region)! destination "%edx" 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 st_label_set_text () at /usr/lib/gnome-shell/libst-1.0.so ffi_call_unix64 () at /usr/lib/x86_64-linux-gnu/libffi.so.6 ffi_call () at /usr/lib/x86_64-linux-gnu/libffi.so.6 () at /usr/lib/libgjs.so.0 Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1747433/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1718227] Re: replacement of ifupdown with netplan needs integration for /etc/network/if{up, down}.d scripts
** Changed in: ubuntu-fan (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to wpa in Ubuntu.
https://bugs.launchpad.net/bugs/1718227
Title:
replacement of ifupdown with netplan needs integration for
/etc/network/if{up,down}.d scripts
Status in aiccu package in Ubuntu:
Invalid
Status in aoetools package in Ubuntu:
New
Status in avahi package in Ubuntu:
New
Status in bind9 package in Ubuntu:
New
Status in chrony package in Ubuntu:
New
Status in clamav package in Ubuntu:
New
Status in controlaula package in Ubuntu:
New
Status in epoptes package in Ubuntu:
New
Status in ethtool package in Ubuntu:
New
Status in guidedog package in Ubuntu:
New
Status in htpdate package in Ubuntu:
New
Status in ifenslave package in Ubuntu:
New
Status in ifmetric package in Ubuntu:
New
Status in ifupdown-multi package in Ubuntu:
New
Status in ifupdown-scripts-zg2 package in Ubuntu:
New
Status in isatapd package in Ubuntu:
New
Status in lprng package in Ubuntu:
New
Status in miredo package in Ubuntu:
New
Status in mythtv package in Ubuntu:
New
Status in nplan package in Ubuntu:
New
Status in nss-pam-ldapd package in Ubuntu:
New
Status in ntp package in Ubuntu:
New
Status in openntpd package in Ubuntu:
New
Status in openresolv package in Ubuntu:
New
Status in openssh package in Ubuntu:
New
Status in openvpn package in Ubuntu:
New
Status in postfix package in Ubuntu:
New
Status in quicktun package in Ubuntu:
New
Status in resolvconf package in Ubuntu:
New
Status in sendmail package in Ubuntu:
New
Status in shorewall-init package in Ubuntu:
New
Status in sidedoor package in Ubuntu:
New
Status in slrn package in Ubuntu:
New
Status in tinc package in Ubuntu:
New
Status in ubuntu-fan package in Ubuntu:
Fix Committed
Status in ucarp package in Ubuntu:
New
Status in uml-utilities package in Ubuntu:
New
Status in uruk package in Ubuntu:
New
Status in vlan package in Ubuntu:
New
Status in vzctl package in Ubuntu:
New
Status in wide-dhcpv6 package in Ubuntu:
New
Status in wpa package in Ubuntu:
New
Bug description:
when network is configured with ifupdown, scripts in
/etc/network/ifup.d/ were called on network being brought up and
/etc/network/ifdown.d were called on network being brought down.
Any packages that shipped these hooks need to be verified to have the
same functionality under a netplan configured system.
# binpkgs=$(apt-file search /etc/network/if-up | sed 's,: .*,,' | sort -u)
# for i in $binpkgs; do
src=$(apt-cache show $i | awk '$1 == "Source:" { print $2; exit(0); }');
[ -z "$src" ] && src="$i"; echo $src; done | sort -u
aiccu
aoetools
avahi
bind9
chrony
clamav
controlaula
epoptes
ethtool
guidedog
htpdate
ifenslave
ifmetric
ifupdown-extra
ifupdown-multi
ifupdown-scripts-zg2
isatapd
lprng
miredo
mythtv-backend
nss-pam-ldapd
ntp
openntpd
openresolv
openssh
openvpn
postfix
quicktun
resolvconf
sendmail
shorewall-init
sidedoor
slrn
tinc
ubuntu-fan
ucarp
uml-utilities
uruk
vlan
vzctl
wide-dhcpv6
wpa
Related bugs:
* bug 1718227: replacement of ifupdown with netplan needs integration for
/etc/network/if{up,down}.d scripts
* bug 1713803: replacement of resolvconf with systemd needs integration
* bug 1717983: replacement of isc-dhcp-client with with systemd-networkd for
dhclient needs integration
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: netplan (not installed)
ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
Uname: Linux 4.12.0-11-generic x86_64
NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CurrentDesktop: GNOME
Date: Tue Sep 19 10:53:08 2017
EcryptfsInUse: Yes
InstallationDate: Installed on 2015-07-23 (789 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: plan
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/aiccu/+bug/1718227/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1505024] Re: GUI terminal top menu
*** This bug is a duplicate of bug 1404726 *** https://bugs.launchpad.net/bugs/1404726 ** This bug is no longer a duplicate of bug 1570752 Two "terminal" menus with duplicates ** This bug has been marked a duplicate of bug 1404726 menu contains two Terminal entries -- 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/1505024 Title: GUI terminal top menu Status in gnome-terminal package in Ubuntu: New Bug description: Confusing two "Terminal" menus in top of terminal menu list. 1. Open terminal 2. In top menu you can see two "Terminal" menus. This is confusing, for example how to write a test case, or give a support on phone or forum in the internet? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1505024/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1404726] Re: menu contains two Terminal entries
Upstream gnome-terminal 3.28 (actually 3.27.90) is going to change this by no longer showing the appmenu (the first "Terminal" menu) on Unity. Just in time now that Unity is no longer Ubuntu's default... :P -- 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/1404726 Title: menu contains two Terminal entries Status in One Hundred Papercuts: New Status in gnome-terminal package in Ubuntu: Confirmed Bug description: GTK 3.14 version of gnome-terminal contains two visible "Terminal" menu options - see picture showing this Suggest the initial "Terminal" that appears before "File" should actually be combined with "File". ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: gnome-terminal 3.14.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1 Uname: Linux 3.16.0-28-generic x86_64 ApportVersion: 2.15.1-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sun Dec 21 20:54:43 2014 InstallationDate: Installed on 2014-11-27 (23 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20141123) SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1404726/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1570752] Re: Two "terminal" menus with duplicates
*** This bug is a duplicate of bug 1404726 *** https://bugs.launchpad.net/bugs/1404726 ** This bug has been marked a duplicate of bug 1404726 menu contains two Terminal entries -- 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/1570752 Title: Two "terminal" menus with duplicates Status in One Hundred Papercuts: Confirmed Status in gnome-terminal package in Ubuntu: Confirmed Bug description: 1)In Ubuntu 16.04 Unity 64 bits, 2)with Gnome Terminal 3.18.3, 3) there should be only one "terminal" dropdown menu (the one on the right) 4) there are two terminal dropdown menus, and the one on the left is totally useless since it contains duplicates entries from other menus, like I listed below: - New terminal : like in File -> Open a terminal - Preferences : like in Edit -> Preferences - Help : like in Help -> Summary - About : like in Help -> About - Exit : like in File -> Close all terminal The solution would be to suppress this menu since all the entries inside are already somewhere else. Note : Since my Ubuntu is in french, some menus name may not be exactly matching the one you have, but it should not be a real problem for your understanding of the situation. To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1570752/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1747410] Re: gnome-shell crashed with signal 5
Hello, https://gitlab.gnome.org/GNOME/gnome-shell/issues/24 Regards, -- Cristian ** Information type changed from Private to Public -- 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/1747410 Title: gnome-shell crashed with signal 5 Status in gnome-shell package in Ubuntu: New Bug description: Hello, I do not know why this happens... Regards, -- Cristian ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.26.2-0ubuntu2 Uname: Linux 4.15.1-041501-generic x86_64 ApportVersion: 2.20.8-0ubuntu8 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME-Greeter:GNOME Date: Mon Feb 5 09:00:13 2018 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2017-10-13 (114 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANGUAGE=es_CL:es PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_CL.UTF-8 SHELL=/bin/false Signal: 5 SourcePackage: gnome-shell StacktraceTop: () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 _XIOError () at /usr/lib/x86_64-linux-gnu/libX11.so.6 _XEventsQueued () at /usr/lib/x86_64-linux-gnu/libX11.so.6 XPending () at /usr/lib/x86_64-linux-gnu/libX11.so.6 () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 Title: gnome-shell crashed with signal 5 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/1747410/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1378117] Re: ibus-ui-gtk3 crashed with signal 5 in _XEventsQueued()
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ibus (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1378117 Title: ibus-ui-gtk3 crashed with signal 5 in _XEventsQueued() Status in ibus package in Ubuntu: Confirmed Bug description: Unclear what went wrong. ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: ibus 1.5.8-2ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-18.25-generic 3.16.3 Uname: Linux 3.16.0-18-generic x86_64 ApportVersion: 2.14.7-0ubuntu3 Architecture: amd64 CurrentDesktop: i3 Date: Mon Oct 6 15:05:41 2014 ExecutablePath: /usr/lib/ibus/ibus-ui-gtk3 InstallationDate: Installed on 2011-05-04 (1251 days ago) InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110426) ProcCmdline: /usr/lib/ibus/ibus-ui-gtk3 ProcEnviron: LANGUAGE=en_US PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 5 SourcePackage: ibus StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 _XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6 XPending () from /usr/lib/x86_64-linux-gnu/libX11.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 Title: ibus-ui-gtk3 crashed with signal 5 in _XEventsQueued() UpgradeStatus: Upgraded to utopic on 2014-09-15 (21 days ago) UserGroups: adm admin autopilot cdrom dialout libvirtd lpadmin pkcs11 plugdev sambashare sbuild sudo vboxusers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1378117/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1359110] Re: ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message()
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ibus (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1359110 Title: ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message() Status in ibus package in Ubuntu: Confirmed Bug description: on 14.10 ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: ibus 1.5.8-2ubuntu1 ProcVersionSignature: Ubuntu 3.15.0-6.11-generic 3.15.0 Uname: Linux 3.15.0-6-generic x86_64 ApportVersion: 2.14.6-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Wed Aug 20 09:35:05 2014 ExecutablePath: /usr/lib/ibus/ibus-ui-gtk3 InstallationDate: Installed on 2014-05-29 (82 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520) ProcCmdline: /usr/lib/ibus/ibus-ui-gtk3 ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: ibus 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 ?? () ?? () ?? () Title: ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message() 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/ibus/+bug/1359110/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1379822] Re: ibus-ui-gtk3 crashed with SIGABRT
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ibus (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1379822 Title: ibus-ui-gtk3 crashed with SIGABRT Status in ibus package in Ubuntu: Confirmed Bug description: happens on every start! ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: ibus 1.5.8-2ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-21.28-generic 3.16.4 Uname: Linux 3.16.0-21-generic x86_64 ApportVersion: 2.14.7-0ubuntu5 Architecture: amd64 CrashCounter: 1 CurrentDesktop: Unity Date: Fri Oct 10 17:09:08 2014 Disassembly: => 0x7f461004dd27: Cannot access memory at address 0x7f461004dd27 ExecutablePath: /usr/lib/ibus/ibus-ui-gtk3 InstallationDate: Installed on 2013-01-14 (633 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) ProcCmdline: /usr/lib/ibus/ibus-ui-gtk3 Signal: 6 SourcePackage: ibus StacktraceTop: ?? () ?? () ?? () ?? () ?? () Title: ibus-ui-gtk3 crashed with SIGABRT UpgradeStatus: Upgraded to utopic on 2014-09-14 (26 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1379822/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1747416] StacktraceSource.txt
** Attachment added: "StacktraceSource.txt" https://bugs.launchpad.net/bugs/1747416/+attachment/5049146/+files/StacktraceSource.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1747416 Title: ibus-ui-gtk3 crashed with signal 5 Status in ibus package in Ubuntu: New Bug description: ibus-ui-gtk3 crashed with signal 5 After login, after boot. When loading desktop(Lxde) ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: ibus 1.5.17-3ubuntu1 ProcVersionSignature: Ubuntu 4.14.0-3.4-generic 4.14.0-rc6 Uname: Linux 4.14.0-3-generic x86_64 ApportVersion: 2.20.8-0ubuntu8 Architecture: amd64 CrashCounter: 1 Date: Mon Feb 5 10:19:38 2018 ExecutablePath: /usr/lib/ibus/ibus-ui-gtk3 InstallationDate: Installed on 2016-08-02 (551 days ago) InstallationMedia: Lubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160727) ProcCmdline: /usr/lib/ibus/ibus-ui-gtk3 Signal: 5 SourcePackage: ibus StacktraceTop: () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_object_new_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_object_new () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 () Title: ibus-ui-gtk3 crashed with signal 5 UpgradeStatus: Upgraded to bionic on 2017-11-24 (72 days ago) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo vboxsf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1747416/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1747416] ibus-ui-gtk3 crashed with signal 5
StacktraceTop: g_settings_set_property (object=0x560dfb6a1750, prop_id=, value=, pspec=) at ../../../../gio/gsettings.c:590 object_set_property (nqueue=0x560dfb71cd60, value=, pspec=0x560dfb6dcee0, object=0x560dfb6a1750) at ../../../../gobject/gobject.c:1439 g_object_new_internal (class=class@entry=0x560dfb727b10, params=params@entry=0x7ffd35404e20, n_params=n_params@entry=1) at ../../../../gobject/gobject.c:1831 g_object_new_valist (object_type=94618053194976, first_property_name=first_property_name@entry=0x7f93a102bbc0 "schema-id", var_args=var_args@entry=0x7ffd35404f70) at ../../../../gobject/gobject.c:2120 g_object_new (object_type=, first_property_name=first_property_name@entry=0x7f93a102bbc0 "schema-id") at ../../../../gobject/gobject.c:1640 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1747416 Title: ibus-ui-gtk3 crashed with signal 5 Status in ibus package in Ubuntu: New Bug description: ibus-ui-gtk3 crashed with signal 5 After login, after boot. When loading desktop(Lxde) ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: ibus 1.5.17-3ubuntu1 ProcVersionSignature: Ubuntu 4.14.0-3.4-generic 4.14.0-rc6 Uname: Linux 4.14.0-3-generic x86_64 ApportVersion: 2.20.8-0ubuntu8 Architecture: amd64 CrashCounter: 1 Date: Mon Feb 5 10:19:38 2018 ExecutablePath: /usr/lib/ibus/ibus-ui-gtk3 InstallationDate: Installed on 2016-08-02 (551 days ago) InstallationMedia: Lubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160727) ProcCmdline: /usr/lib/ibus/ibus-ui-gtk3 Signal: 5 SourcePackage: ibus StacktraceTop: () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_object_new_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_object_new () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 () Title: ibus-ui-gtk3 crashed with signal 5 UpgradeStatus: Upgraded to bionic on 2017-11-24 (72 days ago) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo vboxsf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1747416/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
