[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()
Bumped to High. This bug is the most common gnome-shell crash (not counting those caused by Xwayland) that is still affecting 18.04: https://errors.ubuntu.com/?package=gnome-shell&period=month ** Changed in: gnome-shell (Ubuntu) Importance: Medium => 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/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: Confirmed 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 1714989] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from st_label_set_text() from ffi_call_unix64()
It appears the fix for this bug is scheduled for release in gnome-shell, specifically 3.26.3: https://git.gnome.org/browse/gnome- shell/commit/?h=gnome-3-26&id=3b4be770a0590bcee9c739f3d9264320e23d555b -- 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: Incomplete 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 1741671] Re: nvidia-340 340.102-0ubuntu0.16.04.2: nvidia-340 kernel module failed to build [nv-linux.h:199:2: error: #error "This driver requires the ability to change memory t
I fixed a problem using this commands: # Show all posible drivers sudo ubuntu-drivers devices # Choose another one sudo apt install nvidia-384 rm .Xauthority .ICEauthority After that Ubuntu started. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1741671 Title: nvidia-340 340.102-0ubuntu0.16.04.2: nvidia-340 kernel module failed to build [nv-linux.h:199:2: error: #error "This driver requires the ability to change memory types!"] Status in linux-hwe package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Bug description: not compiling after installation of linux-image-4.13.0-21-generic ProblemType: Package DistroRelease: Ubuntu 16.04 Package: nvidia-340 340.102-0ubuntu0.16.04.2 ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87 Uname: Linux 4.4.0-97-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.102 Mon Jan 16 13:06:29 PST 2017 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.5) .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 DKMSKernelVersion: 4.13.0-21-generic Date: Sat Jan 6 18:36:58 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DuplicateSignature: dkms:nvidia-340:340.102-0ubuntu0.16.04.2:/var/lib/dkms/nvidia-340/340.102/build/nv-linux.h:199:2: error: #error "This driver requires the ability to change memory types!" GraphicsCard: NVIDIA Corporation GT216M [GeForce GT 230M] [10de:0a28] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company GT216M [GeForce GT 230M] [103c:363c] InstallationDate: Installed on 2016-04-26 (619 days ago) InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1) MachineType: Hewlett-Packard HP Pavilion dv7 Notebook PC PackageVersion: 340.102-0ubuntu0.16.04.2 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-97-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.24 SourcePackage: nvidia-graphics-drivers-340 Title: nvidia-340 340.102-0ubuntu0.16.04.2: nvidia-340 kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/05/2010 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.1D dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 363C dmi.board.vendor: Hewlett-Packard dmi.board.version: 32.25 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.1D:bd10/05/2010:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvr039E202413102:rvnHewlett-Packard:rn363C:rvr32.25:cvnHewlett-Packard:ct10:cvrN/A: dmi.product.name: HP Pavilion dv7 Notebook PC dmi.product.version: 039E202413102 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.2 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A 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: Sat Jan 6 18:17:29 2018 xserver.configfile: default xserver.errors: open /dev/fb0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.4-0ubuntu0.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1741671/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 993298] Re: Please make NetworkManager-controlled dnsmasq respect /etc/hosts
+1 Affects me. Tooks me some time to dig and find out the solution. It's really bad user experience. -- 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/993298 Title: Please make NetworkManager-controlled dnsmasq respect /etc/hosts Status in network-manager package in Ubuntu: Confirmed Bug description: Since 12.04 NetworkManager uses the dnsmasq plugin by default to resolve DNS requests. Unfortunately the dnsmasq plug-in has --no- hosts, etc. hard coded [1] which means (among other things) that after the upgrade to 12.04 /etc/hosts will no longer be used to resolve DNS requests. This changes the prior behavior of NetworkManager without any visible warning to the end user. AFAICS there's no other way to work around this problem as to manually revert the change and disable the dnsmasq plug-in in the NetworkManager config, see [2,3]: "To turn off dnsmasq in Network Manager, you need to edit /etc/NetworkManager/NetworkManager.conf and comment the 'dns=dnsmasq' line then do a 'sudo restart network-manager'." This is of course not a bug in the NetworkManager which just behaves as intended. The problem is in the change of the configuration of the Ubuntu packaging which will probably leave many wondering why their /etc/hosts suddenly no longer works. This cost me considerable time to debug and probably is a usability problem for others, too. Maybe you could provide a more visible documentation than that in [3]? E.g., *including a comment in /etc/hosts that explains the change* and how to work around it would have saved me a lot of time. It would have automatically alerted me on upgrade as manual changes to /etc/hosts would then have triggered a prompt while leaving those users with standard /etc/hosts in peace. Probably similar problems arise with other disabled config files and could be alerted to the users? Thinking of resolv.conf, etc. [1] http://cgit.freedesktop.org/NetworkManager/NetworkManager/tree/src/dnsmasq-manager/nm-dnsmasq-manager.c, line 285 [2] i.e. http://ubuntuforums.org/showthread.php?t=1968061 [3] http://www.stgraber.org/2012/02/24/dns-in-ubuntu-12-04/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/993298/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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 broken after upgrade from 17.04 to 17.10
Detail of my the affected machine : Motherboard produit: M3N78-VM fabriquant: ASUSTeK Computer INC. BIOS fabriquant: American Megatrends Inc. identifiant matériel: 0 version: 1406 date: 10/30/2009 Video NVidia C77 [GeForce 8200] (rev a2) (integrated in NVidia chipset) Chipset as identified by the nouveau driver NVidia NVAA -- 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 broken after upgrade from 17.04 to 17.10 Status in gnome-shell package in Ubuntu: Confirmed 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=wa
[Desktop-packages] [Bug 1730174] Re: [artful] Mouse broken after upgrade from 17.04 to 17.10
I could narrow this bug with a 100% certitude (and confirm it also on Manjaro Linux on the same machine) with using the NVidia 304 proprietary driver. My machine has a NVidia C77 [GeForce 8200] (rev a2) which is unsupported with latest NVidia 340 drivers (the system justs freezes). It used to work perrfectly using NVidia 304 "legacy" driver until upgrading to Ubuntu 17.10, but something must have recently changed in the way Gnome or Xorg handles the mouse and the legacy NVidia driver has probably not been updated, alas. THe bug does *NOT* exist when using the "nouveau" driver. Unfortunately, its doesn't perform as well as the proprietray NVidia did... But at least the mouse works again. -- 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 broken after upgrade from 17.04 to 17.10 Status in gnome-shell package in Ubuntu: Confirmed 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
[Desktop-packages] [Bug 1681513] Re: Ubuntu 17.04/17.10: New feature in NetworkManager stops several WiFi adapters from working (MAC Address Randomization issue)
I too ran up against this as I updated some custom bootable systems based on 17.04 and many of my test network dongles would not work. Took lots of time finding this solution, ie adding [device] wifi.scan-rand-mac-address=no to the /etc/NetworkManager/NetworkManager.conf file. -- 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/1681513 Title: Ubuntu 17.04/17.10: New feature in NetworkManager stops several WiFi adapters from working (MAC Address Randomization issue) Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Zesty: Triaged Bug description: According to https://blogs.gnome.org/thaller/2016/08/26/mac-address-spoofing-in-networkmanager-1-4-0/ there is a new privacy feature in the new version of NetworkManager. This privacy feature can cause some USB WiFi adapters to stop working while they used to work with older versions of NetworkManager (Ubuntu 16.10 or older). The purpose of this privacy feature is to get your computer to report a new random MAC address whenever you connect to a WiFi network. This privacy feature is especially useful when you connect to public WiFi networks, so that the operators cannot identify you when you connect multiple times. The downside of this privacy feature is that some USB WiFi adapters misbehave when NetworkManager tries to change their MAC address repeatedly. The result is that those USB WiFi adapters cannot connect anymore to the WiFi network. Original report follows: My Panda USB wi-fi adapter works just fine on 16.10, but when I try to connect to my wi-fi router in 17.04, GNOME network manager reports "Connection failed." I did some tinkering, and noticed that my MAC address for my wifi adapter, according to GNOME, is DIFFERENT every time I make it forget my wifi settings and try to reconnect. Weird, right? Any leads on a possible fix or work-around? I'm running the latest beta of Ubuntu GNOME 17.04, kernel 4.10.0-19-generic, GNOME 3.24.0. https://blogs.gnome.org/thaller/2016/08/26/mac-address-spoofing-in- networkmanager-1-4-0/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1681513/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1717240] Re: libreoffice base not working properly, crashing.
[Expired for libreoffice (Ubuntu) because there has been no activity for 60 days.] ** Changed in: libreoffice (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1717240 Title: libreoffice base not working properly, crashing. Status in libreoffice package in Ubuntu: Expired Bug description: 1. lsb_release -rd : Description: Zorin OS 12.2 Release: 12 1a. lsb_release -a : No LSB modules are available. Distributor ID: Zorin Description: Zorin OS 12.2 Release: 12 Codename: xenial 1b. uname -a : 4.10.0-33-generic #37~16.04.1-Ubuntu SMP Fri Aug 11 14:03:33 UTC 2017 i686 i686 i686 GNU/Linux 1c. cat /proc/version : Linux version 4.10.0-33-generic (buildd@lcy01-22) (gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4) ) #37~16.04.1-Ubuntu SMP Fri Aug 11 14:03:33 UTC 2017 2. apt-cache policy libreoffice-base libreoffice-base: Instalat: 1:5.4.1~rc2-0ubuntu0.16.04.1~lo0 Candidează: 1:5.4.1~rc2-0ubuntu0.16.04.1~lo0 Tabela de versiuni: *** 1:5.4.1~rc2-0ubuntu0.16.04.1~lo0 500 500 http://ppa.launchpad.net/libreoffice/libreoffice-5-4/ubuntu xenial/main i386 Packages 100 /var/lib/dpkg/status 1:5.1.6~rc2-0ubuntu1~xenial2 500 500 http://ro.archive.ubuntu.com/ubuntu xenial-updates/main i386 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/main i386 Packages 1:5.1.2-0ubuntu1 500 500 http://ro.archive.ubuntu.com/ubuntu xenial/main i386 Packages apt-show-versions -r libreoffice-base : libreoffice-base:i386/xenial 1:5.4.1~rc2-0ubuntu0.16.04.1~lo0 uptodate libreoffice-base-core:i386/xenial 1:5.4.1~rc2-0ubuntu0.16.04.1~lo0 uptodate libreoffice-base-drivers:i386/xenial 1:5.4.1~rc2-0ubuntu0.16.04.1~lo0 uptodate apt-show-versions -r libreoffice* : libreoffice:i386/xenial 1:5.4.1~rc2-0ubuntu0.16.04.1~lo0 uptodate libreoffice-avmedia-backend-gstreamer:i386/xenial 1:5.4.1~rc2-0ubuntu0.16.04.1~lo0 uptodate libreoffice-base:i386/xenial 1:5.4.1~rc2-0ubuntu0.16.04.1~lo0 uptodate libreoffice-base-core:i386/xenial 1:5.4.1~rc2-0ubuntu0.16.04.1~lo0 uptodate libreoffice-base-drivers:i386/xenial 1:5.4.1~rc2-0ubuntu0.16.04.1~lo0 uptodate libreoffice-calc:i386/xenial 1:5.4.1~rc2-0ubuntu0.16.04.1~lo0 uptodate libreoffice-common:all/xenial 1:5.4.1~rc2-0ubuntu0.16.04.1~lo0 uptodate libreoffice-core:i386/xenial 1:5.4.1~rc2-0ubuntu0.16.04.1~lo0 uptodate libreoffice-dmaths:all/xenial 3.5.4+dfsg1-1 uptodate libreoffice-draw:i386/xenial 1:5.4.1~rc2-0ubuntu0.16.04.1~lo0 uptodate libreoffice-gnome:i386/xenial 1:5.4.1~rc2-0ubuntu0.16.04.1~lo0 uptodate libreoffice-gtk:all/xenial 1:5.4.1~rc2-0ubuntu0.16.04.1~lo0 uptodate libreoffice-gtk:i386 not installed libreoffice-gtk2:i386/xenial 1:5.4.1~rc2-0ubuntu0.16.04.1~lo0 uptodate libreoffice-gtk3:i386/xenial 1:5.4.1~rc2-0ubuntu0.16.04.1~lo0 uptodate libreoffice-help-en-gb:all/xenial 1:5.4.1~rc2-0ubuntu0.16.04.1~lo0 uptodate libreoffice-help-en-us:all/xenial 1:5.4.1~rc2-0ubuntu0.16.04.1~lo0 uptodate libreoffice-impress:i386/xenial 1:5.4.1~rc2-0ubuntu0.16.04.1~lo0 uptodate libreoffice-java-common:all/xenial 1:5.4.1~rc2-0ubuntu0.16.04.1~lo0 uptodate libreoffice-l10n-en-gb:all/xenial 1:5.4.1~rc2-0ubuntu0.16.04.1~lo0 uptodate libreoffice-l10n-en-za:all/xenial 1:5.4.1~rc2-0ubuntu0.16.04.1~lo0 uptodate libreoffice-l10n-ro:all/xenial 1:5.4.1~rc2-0ubuntu0.16.04.1~lo0 uptodate libreoffice-librelogo:all/xenial 1:5.4.1~rc2-0ubuntu0.16.04.1~lo0 uptodate libreoffice-math:i386/xenial 1:5.4.1~rc2-0ubuntu0.16.04.1~lo0 uptodate libreoffice-mysql-connector:i386/xenial 1.0.2+LibO5.4.1~rc2-0ubuntu0.16.04.1~lo0 uptodate libreoffice-nlpsolver:all/xenial 0.9+LibO5.4.1~rc2-0ubuntu0.16.04.1~lo0 uptodate libreoffice-ogltrans:i386/xenial 1:5.4.1~rc2-0ubuntu0.16.04.1~lo0 uptodate libreoffice-pdfimport:all/xenial 1:5.4.1~rc2-0ubuntu0.16.04.1~lo0 uptodate libreoffice-pdfimport:i386 not installed libreoffice-report-builder:all/xenial 1:5.4.1~rc2-0ubuntu0.16.04.1~lo0 uptodate libreoffice-report-builder-bin:i386/xenial 1:5.4.1~rc2-0ubuntu0.16.04.1~lo0 uptodate libreoffice-script-provider-bsh:all/xenial 1:5.4.1~rc2-0ubuntu0.16.04.1~lo0 uptodate libreoffice-script-provider-js:all/xenial 1:5.4.1~rc2-0ubuntu0.16.04.1~lo0 uptodate libreoffice-script-provider-python:all/xenial 1:5.4.1~rc2-0ubuntu0.16.04.1~lo0 uptodate libreoffice-sdbc-hsqldb:i386/xenial 1:5.4.1~rc2-0ubuntu0.16.04.1~lo0 uptodate libreoffice-sdbc-postgresql:i386/xenial 1:5.4.1~rc2-0ubuntu0.16.04.1~lo0 uptodate libreoffice-style-breeze:all/xenial 1:5.4.1~rc2-0ubuntu0.16.04.1~lo0 uptodate libreoffice-style-elementary:all/xenial 1:5.4.1~rc2-0ubuntu0.16.04.1~lo0 uptodate libreoffice-style-galaxy:all/xenial 1:5.4.1~rc2-0ubuntu0.16.04.1~lo0 uptodate libreoffice-style-hicontr
[Desktop-packages] [Bug 1730174] Re: [artful] Mouse broken after upgrade from 17.04 to 17.10
See also similar bug 1181666, and the general class of bugs: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bugs?field.tag=noclick ** Tags added: noclick -- 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 broken after upgrade from 17.04 to 17.10 Status in gnome-shell package in Ubuntu: Confirmed 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 jou
[Desktop-packages] [Bug 1730174] Re: [artful] Mouse broken after upgrade from 17.04 to 17.10
I also experienced mouse issue, can't click on wayland, while on Xorg works as normal, -- 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 broken after upgrade from 17.04 to 17.10 Status in gnome-shell package in Ubuntu: Confirmed 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 insufficient permissions. PackageArchitectur
[Desktop-packages] [Bug 1743058] Re: In multiple apps, the input field "jumps"
** No longer affects: gdm3 (Ubuntu) ** No longer affects: gnome-keyring (Ubuntu) ** Tags added: visual-quality ** Summary changed: - In multiple apps, the input field "jumps" + Input field height changes slightly when entering in st password fields. ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Low -- 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/1743058 Title: Input field height changes slightly when entering in st password fields. Status in gnome-shell package in Ubuntu: Confirmed Bug description: It appears there is the font/height rendering issue in multiple places. With the textentry "jumping" in height slightly upon entering anything. I have observed this on the login screen password entry screen, lockscreen entry, and the gnome pin entry for my ssh/gpg smartcard. It almost feels as if the "dots" of the hidden password are either of larger font size and/or bold, whilst an empty text field and/or unfocused text field font is either smaller and or regular (non-bold). Resulting in a rendering / layout jiggles. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1743058/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1743058] Re: In multiple apps, the input field "jumps"
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-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1743058 Title: Input field height changes slightly when entering in st password fields. Status in gnome-shell package in Ubuntu: Confirmed Bug description: It appears there is the font/height rendering issue in multiple places. With the textentry "jumping" in height slightly upon entering anything. I have observed this on the login screen password entry screen, lockscreen entry, and the gnome pin entry for my ssh/gpg smartcard. It almost feels as if the "dots" of the hidden password are either of larger font size and/or bold, whilst an empty text field and/or unfocused text field font is either smaller and or regular (non-bold). Resulting in a rendering / layout jiggles. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1743058/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1743058] Re: In multiple apps, the input field "jumps"
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-keyring (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1743058 Title: Input field height changes slightly when entering in st password fields. Status in gnome-shell package in Ubuntu: Confirmed Bug description: It appears there is the font/height rendering issue in multiple places. With the textentry "jumping" in height slightly upon entering anything. I have observed this on the login screen password entry screen, lockscreen entry, and the gnome pin entry for my ssh/gpg smartcard. It almost feels as if the "dots" of the hidden password are either of larger font size and/or bold, whilst an empty text field and/or unfocused text field font is either smaller and or regular (non-bold). Resulting in a rendering / layout jiggles. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1743058/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1743058] Re: In multiple apps, the input field "jumps"
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gdm3 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1743058 Title: Input field height changes slightly when entering in st password fields. Status in gnome-shell package in Ubuntu: Confirmed Bug description: It appears there is the font/height rendering issue in multiple places. With the textentry "jumping" in height slightly upon entering anything. I have observed this on the login screen password entry screen, lockscreen entry, and the gnome pin entry for my ssh/gpg smartcard. It almost feels as if the "dots" of the hidden password are either of larger font size and/or bold, whilst an empty text field and/or unfocused text field font is either smaller and or regular (non-bold). Resulting in a rendering / layout jiggles. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1743058/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1743058] Re: In multiple apps, the input field "jumps"
As far as I can tell, this is either an 'st' (Shell Toolkit in gnome- shell, also used on the login screen) bug, or an issue with our theming which is patched into gnome-shell. The same st gnome-shell code is used in security prompts. So I think this bug lays entirely within gnome-shell and not the other components. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1743058 Title: Input field height changes slightly when entering in st password fields. Status in gnome-shell package in Ubuntu: Confirmed Bug description: It appears there is the font/height rendering issue in multiple places. With the textentry "jumping" in height slightly upon entering anything. I have observed this on the login screen password entry screen, lockscreen entry, and the gnome pin entry for my ssh/gpg smartcard. It almost feels as if the "dots" of the hidden password are either of larger font size and/or bold, whilst an empty text field and/or unfocused text field font is either smaller and or regular (non-bold). Resulting in a rendering / layout jiggles. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1743058/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1743054] Re: Notifications - disappear, regression since xenial
So that we know what version you're using, please run: apport-collect 1743054 ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1743054 Title: Notifications - disappear, regression since xenial Status in gnome-shell package in Ubuntu: Incomplete Status in hexchat package in Ubuntu: New Bug description: In xenial, messenging menu would display hexchat irc highlights e.g. "#channel1 #channel2 nick1 nick2". Upon clicking one of them, the rest were preserved. Now, in gnome-shell, all notifications are cleared. A number bubble remains, and highlighted channels remain, but it is a lot more difficult to jump to each highlight, as previously I could could go back to the messaging menu and click #channel2 to open that hightlight. I'm not sure if this is a bug in hexchat, gnome-shell, or both. Is there an IRC client with better / preserving capacity of the highlights and gnome-shell integration? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1743054/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1743055] Re: Show dock on all screens, should also show the top bar on all screens
I can't seem to find the option "Show dock on all screens settings". Can you please point out where it is? Please also: * Run: apport-collect 1743055 * Try: https://extensions.gnome.org/extension/323/multiple-monitor-panels/ ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1743055 Title: Show dock on all screens, should also show the top bar on all screens Status in gnome-shell package in Ubuntu: Incomplete Bug description: Show dock on all screens settings, should also show the top bar on all screens (ie the activities, calendar settings bar). As otherwise I cannot display aps / terminals side by side on two screens and have them match vertically for comparison etc. This is a regression from xenial, were in dual-monitor setup both screens had identical vertical height space. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1743055/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1721074] Re: [P95_HR, Realtek Generic, Speaker, Internal] 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/1721074 Title: [P95_HR, Realtek Generic, Speaker, Internal] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: New Bug description: no sound at all. used to work a few weeks ago. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.10.0-36.40~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-36-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC1: cc16 2656 F pulseaudio /dev/snd/pcmC0D0c: cc16 2656 F...m pulseaudio /dev/snd/controlC0: cc16 2656 F pulseaudio CurrentDesktop: Unity Date: Tue Oct 3 17:23:32 2017 InstallationDate: Installed on 2017-08-22 (42 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) 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: USER PID ACCESS COMMAND /dev/snd/controlC1: cc16 2656 F pulseaudio /dev/snd/controlC0: cc16 2656 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [P95_HR, Realtek Generic, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/29/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.02 dmi.board.asset.tag: Tag 12345 dmi.board.name: P95_HR dmi.board.vendor: CLEVO dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.02:bd06/29/2017:svnPCSpecialistLimited:pnP95_HR:pvrNotApplicable:rvnCLEVO:rnP95_HR:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.name: P95_HR dmi.product.version: Not Applicable dmi.sys.vendor: PC Specialist Limited To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1721074/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1743003] Re: no audio via internal laptop speakers; reporting via ubuntu-bug results in pulseaudio crash
*** This bug is a duplicate of bug 1721074 *** https://bugs.launchpad.net/bugs/1721074 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 1721074, 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 1721074 [P95_HR, Realtek Generic, Speaker, Internal] No sound at all -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1743003 Title: no audio via internal laptop speakers; reporting via ubuntu-bug results in pulseaudio crash Status in pulseaudio package in Ubuntu: New Bug description: No sound at all via internal laptop speakers. Tried to report via ubuntu-bug, but get an error "pulseaudio has crashed." ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu3.7 ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13 Uname: Linux 4.13.0-26-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/pcmC0D0p: cc16 2679 F...m pulseaudio /dev/snd/controlC0: cc16 2679 F pulseaudio /dev/snd/controlC1: cc16 2679 F pulseaudio Date: Fri Jan 12 17:21:02 2018 InstallationDate: Installed on 2017-08-22 (143 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/29/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.02 dmi.board.asset.tag: Tag 12345 dmi.board.name: P95_HR dmi.board.vendor: CLEVO dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.02:bd06/29/2017:svnPCSpecialistLimited:pnP95_HR:pvrNotApplicable:rvnCLEVO:rnP95_HR:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: P95_HR dmi.product.version: Not Applicable dmi.sys.vendor: PC Specialist Limited To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1743003/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1696305] Re: High CPU usage in gnome-shell just redrawing the screen (Firefox is running)
** Changed in: gnome-shell (Ubuntu) Assignee: (unassigned) => Daniel van Vugt (vanvugt) ** Changed in: mutter (Ubuntu) Assignee: (unassigned) => Daniel van Vugt (vanvugt) ** Changed in: gnome-shell (Ubuntu) Status: Confirmed => In Progress ** Changed in: mutter (Ubuntu) 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/1696305 Title: High CPU usage in gnome-shell just redrawing the screen (Firefox is running) Status in gnome-shell package in Ubuntu: In Progress Status in mutter package in Ubuntu: In Progress Bug description: Even when doing nothing at all, gnome-shell uses around 70% CPU. ``` inxi -t cm Processes: CPU: % used - top 5 active 1: cpu: 68.6% command: gnome-shell pid: 1399 2: cpu: 50.4% command: Xwayland pid: 1405 3: cpu: 19.7% command: firefox pid: 3684 4: cpu: 2.4% command: gnome-shell pid: 1859 5: cpu: 1.5% command: gnome-tweak-tool (started by: python) pid: 13603 Memory: MB / % used - Used/Total: 2350.1/11897.0MB - top 5 active 1: mem: 1033.63MB (8.6%) command: firefox pid: 3684 2: mem: 317.59MB (2.6%) command: gnome-shell pid: 1859 3: mem: 267.55MB (2.2%) command: gnome-software pid: 2058 4: mem: 111.25MB (0.9%) command: Xorg pid: 1506 5: mem: 90.90MB (0.7%) command: nautilus-desktop pid: 2055 ``` It's also strange that Xwayland is active as I did choose the "normal" gnome session upon signin. ``` echo $XDG_SESSION_TYPE x11 ``` While searching I found a recent problem with AMD GPUs, but I'm using an Intel GPU ``` glxinfo name of display: :0 display: :0 screen: 0 direct rendering: Yes server glx vendor string: SGI server glx version string: 1.4 server glx extensions: GLX_ARB_create_context, GLX_ARB_create_context_profile, GLX_ARB_create_context_robustness, GLX_ARB_fbconfig_float, GLX_ARB_framebuffer_sRGB, GLX_ARB_multisample, GLX_EXT_create_context_es2_profile, GLX_EXT_create_context_es_profile, GLX_EXT_fbconfig_packed_float, GLX_EXT_framebuffer_sRGB, GLX_EXT_import_context, GLX_EXT_libglvnd, GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_INTEL_swap_event, GLX_MESA_copy_sub_buffer, GLX_OML_swap_method, GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group, GLX_SGI_make_current_read, GLX_SGI_swap_control client glx vendor string: Mesa Project and SGI client glx version string: 1.4 client glx extensions: GLX_ARB_create_context, GLX_ARB_create_context_profile, GLX_ARB_create_context_robustness, GLX_ARB_fbconfig_float, GLX_ARB_framebuffer_sRGB, GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_buffer_age, GLX_EXT_create_context_es2_profile, GLX_EXT_create_context_es_profile, GLX_EXT_fbconfig_packed_float, GLX_EXT_framebuffer_sRGB, GLX_EXT_import_context, GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_INTEL_swap_event, GLX_MESA_copy_sub_buffer, GLX_MESA_multithread_makecurrent, GLX_MESA_query_renderer, GLX_MESA_swap_control, GLX_OML_swap_method, GLX_OML_sync_control, GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group, GLX_SGI_make_current_read, GLX_SGI_swap_control, GLX_SGI_video_sync GLX version: 1.4 GLX extensions: GLX_ARB_create_context, GLX_ARB_create_context_profile, GLX_ARB_create_context_robustness, GLX_ARB_fbconfig_float, GLX_ARB_framebuffer_sRGB, GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_buffer_age, GLX_EXT_create_context_es2_profile, GLX_EXT_create_context_es_profile, GLX_EXT_fbconfig_packed_float, GLX_EXT_framebuffer_sRGB, GLX_EXT_import_context, GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_INTEL_swap_event, GLX_MESA_copy_sub_buffer, GLX_MESA_multithread_makecurrent, GLX_MESA_query_renderer, GLX_MESA_swap_control, GLX_OML_swap_method, GLX_OML_sync_control, GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group, GLX_SGI_make_current_read, GLX_SGI_swap_control, GLX_SGI_video_sync Extended renderer info (GLX_MESA_query_renderer): Vendor: Intel Open Source Technology Center (0x8086) Device: Mesa DRI Intel(R) Haswell Mobile (0xa16) Version: 17.1.0 Accelerated: yes Video memory: 1536MB Unified memory: yes Preferred profile: core (0x1) Max core profile version: 4.5 Max compat profile version: 3.0 Max GLES1 profile version: 1.1 Max GLES[23] profile version: 3.1 OpenGL vendor string: Intel Ope
[Desktop-packages] [Bug 1721074] Re: [P95_HR, Realtek Generic, Speaker, Internal] No sound at all
** Also affects: pulseaudio (Ubuntu) Importance: Undecided Status: New -- 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/1721074 Title: [P95_HR, Realtek Generic, Speaker, Internal] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: New Bug description: no sound at all. used to work a few weeks ago. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.10.0-36.40~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-36-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC1: cc16 2656 F pulseaudio /dev/snd/pcmC0D0c: cc16 2656 F...m pulseaudio /dev/snd/controlC0: cc16 2656 F pulseaudio CurrentDesktop: Unity Date: Tue Oct 3 17:23:32 2017 InstallationDate: Installed on 2017-08-22 (42 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) 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: USER PID ACCESS COMMAND /dev/snd/controlC1: cc16 2656 F pulseaudio /dev/snd/controlC0: cc16 2656 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [P95_HR, Realtek Generic, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/29/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.02 dmi.board.asset.tag: Tag 12345 dmi.board.name: P95_HR dmi.board.vendor: CLEVO dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.02:bd06/29/2017:svnPCSpecialistLimited:pnP95_HR:pvrNotApplicable:rvnCLEVO:rnP95_HR:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.name: P95_HR dmi.product.version: Not Applicable dmi.sys.vendor: PC Specialist Limited To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1721074/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1731102] Re: Poor performance with Wayland
*** This bug is a duplicate of bug 1690719 *** https://bugs.launchpad.net/bugs/1690719 Thanks for the bug report. This sounds like multiple issues which have already been reported. Please see bug 1690719 and bug 1696305. ** Package changed: wayland (Ubuntu) => gnome-shell (Ubuntu) ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New ** This bug has been marked a duplicate of bug 1690719 Mouse randomly pauses/stutters in gnome shell. It's not perfectly smooth. -- 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/1731102 Title: Poor performance with Wayland Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: New Bug description: When running Gnome 3 in Wayland mode (confirmed with XDG_SESSION_TYPE env var) I see the following issues on this hardware: * Jerky animations (glxgears stutters noticably) * Mouse cursor sometimes updated at a reduced framerate, usualy when CPU is under load, appearing to worsen over time (> 8 hours uptime) * High CPU usage when mousing over icons in left-hand side Unity dock (20-30%), also causing mouse cursor to stutter * 15fps in Kodi and poor video playback framerate * 30-40% CPU usage in Kodi when program idle * Gnome shell frequently using 25% of CPU or more All issues disappear when using x11 mode (again confirmed with XDG_SESSION_TYPE env var). Performance in that case seems as good as 17.04 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 BootLog: * Setting up X socket directories... [240G [234G[ OK ] * Restoring resolver state... [240G [234G[ OK ] Starting jabber server: ejabberd CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Nov 9 13:03:08 2017 DistUpgraded: 2017-11-07 09:38:15,448 DEBUG icon theme changed, re-reading DistroCodename: artful DistroVariant: ubuntu DkmsStatus: virtualbox, 5.1.30, 4.10.0-37-generic, x86_64: installed virtualbox, 5.1.30, 4.13.0-16-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 6310] [1002:9802] (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. Wrestler [Radeon HD 6310] [19da:a191] InstallationDate: Installed on 2011-12-05 (2165 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=e1bf9820-e70e-4e84-9037-621437cc90f1 ro radeon.audio=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to artful on 2017-11-06 (2 days ago) dmi.bios.date: 10/28/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.4 dmi.board.name: AMD HUDSON-M1 dmi.board.vendor: ZOTAC dmi.chassis.type: 3 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.4:bd10/28/2011:svn:pn:pvr:rvnZOTAC:rnAMDHUDSON-M1:rvr:cvn:ct3:cvr: version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1 version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Wed Oct 18 20:39:16 2017 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputRiitek Micro Keyboard KEYBOARD, id 8 inputRiitek Micro Keyboard MOUSE, id 9 inputRiitek Micro Keyboard KEYBOARD, id 10 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.3-1ubuntu1.3 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1731102/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1690719] Re: Mouse randomly pauses/stutters in gnome shell. It's not perfectly smooth.
** Changed in: gnome-shell (Ubuntu) Status: Confirmed => In Progress ** Changed in: mutter (Ubuntu) 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/1690719 Title: Mouse randomly pauses/stutters in gnome shell. It's not perfectly smooth. Status in Mutter: Confirmed Status in gnome-shell package in Ubuntu: In Progress Status in mutter package in Ubuntu: In Progress Bug description: The mouse pointer randomly pauses/stutters in Gnome Shell. It's not reliably smooth like you would see in Xorg or Mir demo servers. Feels like there is a blocking call being made in a GUI thread that shouldn't have any blocking calls. Although it's not clear if this is just a problem with pointer input or the shell compositing in general. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.24.2-0ubuntu2 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 ApportVersion: 2.20.4-0ubuntu7 Architecture: amd64 Date: Mon May 15 13:23:22 2017 DisplayManager: lightdm GsettingsChanges: b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'scaling-factor' b'uint32 1' InstallationDate: Installed on 2017-05-03 (12 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1690719/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1726106] Re: [P95_HR, Realtek ALC1220, Speaker, Internal] No sound at all
*** This bug is a duplicate of bug 1721074 *** https://bugs.launchpad.net/bugs/1721074 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 1721074, 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 1721074 [P95_HR, Realtek Generic, Speaker, Internal] No sound at all -- 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/1726106 Title: [P95_HR, Realtek ALC1220, Speaker, Internal] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: No sound at all, internal laptop speakers or headphones plugged in. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 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 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dan2209 F pulseaudio CurrentDesktop: Budgie:GNOME Date: Sun Oct 22 14:16:56 2017 InstallationDate: Installed on 2017-10-21 (0 days ago) InstallationMedia: Ubuntu-Budgie 17.10 "Artful Aardvark" - Release amd64 (20171017.1) 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/controlC0: dan2209 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [P95_HR, Realtek ALC1220, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/14/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.03 dmi.board.asset.tag: Tag 12345 dmi.board.name: P95_HR dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.03:bd07/14/2017:svnNotebook:pnP95_HR:pvrNotApplicable:rvnNotebook:rnP95_HR:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: P95_HR 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/1726106/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1721428] Re: Artful (17.10) Session logout after screen turned off
Everyone please log your own separate bugs for this issue. Because it's not really one issue - it is multiple different gnome-shell crashes. Logging your own bug will help us to figure out exactly which crash you are experiencing and which fix you need. -- 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/1721428 Title: Artful (17.10) Session logout after screen turned off Status in GNOME Shell: Unknown Status in Nouveau Xorg driver: New Status in gnome-shell package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: Whenever I turn off my screen, the computer (a desktop PC) logs me out of my session. Here is a discussion thread with users of similar issue: https://ubuntuforums.org/showthread.php?t=2372388&p=13694312&posted=1#post13694312 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1721428/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1725863] Re: Logitech G930 drops connection and reconnects in 17.10 (But not in 17.04)
Thanks for the update. We don't really need to do anything with this bug now, because it is set to automatically close itself if no comments are added for 60 days. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1725863 Title: Logitech G930 drops connection and reconnects in 17.10 (But not in 17.04) Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: Every so many seconds / minutes the Wireless headset Logitech G930 simply drops connection. It always reconnects but when doing a recording, a meeting, listening to music or a movie it simply drops the connection for 1 to 3 second. This happens several times an hour. If it helps, it was not happening in 17.04 (Never happened in more than 200+ hours of using the headset). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: pulseaudio 1:10.0-2ubuntu3 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 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: cyrex 1288 F pulseaudio /dev/snd/controlC2: cyrex 1288 F pulseaudio /dev/snd/controlC0: cyrex 1288 F pulseaudio Date: Sat Oct 21 17:55:42 2017 InstallationDate: Installed on 2017-10-19 (2 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/30/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3504 dmi.board.asset.tag: Default string dmi.board.name: MAXIMUS VIII HERO ALPHA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3504:bd06/30/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIIIHEROALPHA:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1725863/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1710858] Re: totem crashed with SIGSEGV in in __GI_____strtoul_l_internal() from __GI___strtoul_l() from g_ascii_strtoull() from _cogl_gpu_info_parse_version_string() from chec
This crash is also being tracked in: https://errors.ubuntu.com/problem/8c8cfc48195ee610b89b3b2fa352c622b507d073 But see also related: https://errors.ubuntu.com/problem/e412508b4134f38c5ad9ea35c0efbe5fa62a4f09 ** Summary changed: - totem crashed with SIGSEGV in __GI_strtoul_l_internal() + totem crashed with SIGSEGV in in __GI_strtoul_l_internal() from __GI___strtoul_l() from g_ascii_strtoull() from _cogl_gpu_info_parse_version_string() from check_mesa_driver_package() ** Description changed: + https://errors.ubuntu.com/problem/8c8cfc48195ee610b89b3b2fa352c622b507d073 + + --- + crashed trying to open .avi video ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: totem 3.25.90.1-0ubuntu1 Uname: Linux 4.12.6-041206-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.6-0ubuntu5 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME Date: Tue Aug 15 12:20:00 2017 ExecutablePath: /usr/bin/totem InstallationDate: Installed on 2016-05-20 (451 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcCmdline: /usr/bin/totem --gapplication-service ProcEnviron: - XDG_RUNTIME_DIR= - SHELL=/bin/bash - PATH=(custom, no user) - LANG=it_IT.UTF-8 + XDG_RUNTIME_DIR= + SHELL=/bin/bash + PATH=(custom, no user) + LANG=it_IT.UTF-8 SegvAnalysis: - Segfault happened at: 0x7fe5160f1bf5 <__GI_strtoul_l_internal+53>: movsbq (%r14),%rax - PC (0x7fe5160f1bf5) ok - source "(%r14)" (0x) not located in a known VMA region (needed readable region)! - destination "%rax" ok + Segfault happened at: 0x7fe5160f1bf5 <__GI_strtoul_l_internal+53>: movsbq (%r14),%rax + PC (0x7fe5160f1bf5) ok + source "(%r14)" (0x) not located in a known VMA region (needed readable region)! + destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: totem StacktraceTop: - __GI_strtoul_l_internal (nptr=0x0, endptr=0x7fff97eb9aa8, base=10, group=, loc=0x7fe516474820 <_nl_C_locobj>) at ../stdlib/strtol_l.c:293 - () at /usr/lib/x86_64-linux-gnu/libcogl.so.20 - () at /usr/lib/x86_64-linux-gnu/libcogl.so.20 - () at /usr/lib/x86_64-linux-gnu/libcogl.so.20 - () at /usr/lib/x86_64-linux-gnu/libcogl.so.20 + __GI_strtoul_l_internal (nptr=0x0, endptr=0x7fff97eb9aa8, base=10, group=, loc=0x7fe516474820 <_nl_C_locobj>) at ../stdlib/strtol_l.c:293 + () at /usr/lib/x86_64-linux-gnu/libcogl.so.20 + () at /usr/lib/x86_64-linux-gnu/libcogl.so.20 + () at /usr/lib/x86_64-linux-gnu/libcogl.so.20 + () at /usr/lib/x86_64-linux-gnu/libcogl.so.20 Title: totem crashed with SIGSEGV in __GI_strtoul_l_internal() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm autopilot cdrom colord dialout dip libvirt libvirtd lpadmin netdev pico plugdev sambashare sudo -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1710858 Title: totem crashed with SIGSEGV in in __GI_strtoul_l_internal() from __GI___strtoul_l() from g_ascii_strtoull() from _cogl_gpu_info_parse_version_string() from check_mesa_driver_package() Status in totem package in Ubuntu: Confirmed Status in totem package in Debian: Confirmed Bug description: https://errors.ubuntu.com/problem/8c8cfc48195ee610b89b3b2fa352c622b507d073 --- crashed trying to open .avi video ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: totem 3.25.90.1-0ubuntu1 Uname: Linux 4.12.6-041206-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.6-0ubuntu5 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME Date: Tue Aug 15 12:20:00 2017 ExecutablePath: /usr/bin/totem InstallationDate: Installed on 2016-05-20 (451 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcCmdline: /usr/bin/totem --gapplication-service ProcEnviron: XDG_RUNTIME_DIR= SHELL=/bin/bash PATH=(custom, no user) LANG=it_IT.UTF-8 SegvAnalysis: Segfault happened at: 0x7fe5160f1bf5 <__GI_strtoul_l_internal+53>: movsbq (%r14),%rax PC (0x7fe5160f1bf5) ok source "(%r14)" (0x) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: totem StacktraceTop: __GI_strtoul_l_internal (nptr=0x0, endptr=0x7fff97eb9aa8, base=10, group=, loc=0x7fe516474820 <_nl_C_locobj>) at ../stdlib/strtol_l.c:293 () at /usr/lib/x86_64-linux-gnu/libcogl.so.20 () at /usr/lib/x86_64-linux-gnu/libcogl.so.20 () at /usr/lib/x86_64-linux-gnu/libcogl.so.20 () at /usr/lib/x86_64-linux-gnu/libcogl.so.20 Title: totem crashed with SIGSEGV in __GI_strtoul_l_internal() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: a
[Desktop-packages] [Bug 1743281] [NEW] /usr/bin/totem:11:__GI_____strtoul_l_internal:__GI___strtoul_l:g_ascii_strtoull:_cogl_gpu_info_parse_version_string:check_mesa_driver_package
*** This bug is a duplicate of bug 1710858 *** https://bugs.launchpad.net/bugs/1710858 Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding totem. This problem was most recently seen with package version 3.26.0-0ubuntu2, the problem page at https://errors.ubuntu.com/problem/8c8cfc48195ee610b89b3b2fa352c622b507d073 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: totem (Ubuntu) Importance: Undecided Status: New ** Tags: artful bionic kylin-17.10 xenial yakkety zesty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1743281 Title: /usr/bin/totem:11:__GI_strtoul_l_internal:__GI___strtoul_l:g_ascii_strtoull:_cogl_gpu_info_parse_version_string:check_mesa_driver_package Status in totem package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding totem. This problem was most recently seen with package version 3.26.0-0ubuntu2, the problem page at https://errors.ubuntu.com/problem/8c8cfc48195ee610b89b3b2fa352c622b507d073 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1743281/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1743281] Re: /usr/bin/totem:11:__GI_____strtoul_l_internal:__GI___strtoul_l:g_ascii_strtoull:_cogl_gpu_info_parse_version_string:check_mesa_driver_package
*** This bug is a duplicate of bug 1710858 *** https://bugs.launchpad.net/bugs/1710858 ** This bug has been marked a duplicate of bug 1710858 totem crashed with SIGSEGV in __GI_strtoul_l_internal() -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1743281 Title: /usr/bin/totem:11:__GI_strtoul_l_internal:__GI___strtoul_l:g_ascii_strtoull:_cogl_gpu_info_parse_version_string:check_mesa_driver_package Status in totem package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding totem. This problem was most recently seen with package version 3.26.0-0ubuntu2, the problem page at https://errors.ubuntu.com/problem/8c8cfc48195ee610b89b3b2fa352c622b507d073 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1743281/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1741447] Re: Unity / Compiz in a crash loop after login, after mesa updates of 2018-01-04
*** This bug is a duplicate of bug 1735594 *** https://bugs.launchpad.net/bugs/1735594 sudo apt-add-repository ppa:paulo-miguel-dias/pkppa sudo apt update && sudo apt upgrade -y sudo reboot works for me!!! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1741447 Title: Unity / Compiz in a crash loop after login, after mesa updates of 2018-01-04 Status in Mesa: New Status in mesa package in Ubuntu: Confirmed Status in mesa source package in Xenial: Confirmed Status in mesa source package in Artful: Confirmed Bug description: GUI is constantly crashing, can't start desktop Jan 5 11:21:29 1810 kernel: [ 806.368754] compiz[10824]: segfault at 0 ip 7f83c4f31c16 sp 7ffd48dfc2f0 error 4 in i965_dri.so[7f83c4954000+82d000] Jan 5 11:21:40 1810 kernel: [ 817.279740] compiz[1]: segfault at 0 ip 7fda21519c16 sp 7ffd7b40a150 error 4 in i965_dri.so[7fda20f3c000+82d000] Jan 5 11:22:30 1810 kernel: [ 867.445137] compiz[11271]: segfault at 0 ip 7f8462855c16 sp 7fff07c857f0 error 4 in i965_dri.so[7f8462278000+82d000] Jan 5 11:22:46 1810 kernel: [ 883.319195] compiz[11458]: segfault at 0 ip 7f72b7af0c16 sp 7ffc3b92d830 error 4 in i965_dri.so[7f72b7513000+82d000] Jan 5 11:23:01 1810 kernel: [ 898.587610] compiz[11516]: segfault at 0 ip 7fe25113dc16 sp 7ffcf79754c0 error 4 in i965_dri.so[7fe250b6+82d000] In /var/crash: _usr_bin_compiz.999.crash Did manage to start a GUI in Low graphics mode (lowgfx.conf) but this is not really usable. - dash not working - no window switching - sometimes all windows disappear for a few seconds So effectively my laptop is not usable after latest updates. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: unity 7.4.0+16.04.20160906-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-42-generic x86_64 .tmp.unity_support_test.0: .tmp.unity_support_test.1: ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Jan 5 11:16:53 2018 DistUpgraded: 2016-04-22 18:36:32,349 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated Graphics Controller [1025:029b] Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated Graphics Controller [1025:029b] InstallationDate: Installed on 2014-04-18 (1357 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Acer Aspire 1810TZ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-42-generic root=UUID=86d7d9a6-ffc3-47cb-adc4-68cfcbcadcef ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: Upgraded to xenial on 2016-04-22 (622 days ago) dmi.bios.date: 08/31/2010 dmi.bios.vendor: INSYDE dmi.bios.version: v1.3314 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: JM11-MS dmi.board.vendor: Acer dmi.board.version: Base Board Version dmi.chassis.type: 1 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDE:bvrv1.3314:bd08/31/2010:svnAcer:pnAspire1810TZ:pvrv1.3314:rvnAcer:rnJM11-MS:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion: dmi.product.name: Aspire 1810TZ dmi.product.version: v1.3314 dmi.sys.vendor: Acer 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.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~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: Fri Jan 5 11:14:24 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.5-0ubuntu2~16.04.1 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1741447/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.
[Desktop-packages] [Bug 1743276] [NEW] Failed to start network-manager.service: Unit network-manager.service not found.
Public bug reported: root@ubuntu:~# sudo service network-manager start Failed to start network-manager.service: Unit network-manager.service not found. root@ubuntu:~# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 16.04.3 LTS Release:16.04 Codename: xenial ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1743276 Title: Failed to start network-manager.service: Unit network-manager.service not found. Status in network-manager package in Ubuntu: New Bug description: root@ubuntu:~# sudo service network-manager start Failed to start network-manager.service: Unit network-manager.service not found. root@ubuntu:~# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 16.04.3 LTS Release: 16.04 Codename: xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1743276/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1742134] Re: gnome-software crashed with signal 5 in g_cancellable_make_pollfd()
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-software (Ubuntu) Status: New => Confirmed -- 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/1742134 Title: gnome-software crashed with signal 5 in g_cancellable_make_pollfd() Status in gnome-software package in Ubuntu: Confirmed Bug description: Search function in Ubuntu software center ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-software 3.26.3-2ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 Uname: Linux 4.13.0-17-generic x86_64 ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Jan 9 13:16:06 2018 ExecutablePath: /usr/bin/gnome-software InstallationDate: Installed on 2018-01-08 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-limba N/A gnome-software-plugin-snap3.26.3-2ubuntu1 ProcCmdline: /usr/bin/gnome-software --gapplication-service Signal: 5 SourcePackage: gnome-software StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_cancellable_make_pollfd () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 g_socket_condition_timed_wait () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 g_socket_connect () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 g_socket_client_connect () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: gnome-software crashed with signal 5 in g_cancellable_make_pollfd() UpgradeStatus: Upgraded to bionic on 2018-01-09 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1742134/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1743259] [NEW] 3D acceleration stops working after kernel upgrade
Public bug reported: I have a Thinkpad X200. I installed Ubunntu 16.04.3. It works fine immediately after installation (kernel 4.10.0-28). But when I install updates (kernel 4.13, post Meltdown/Spectre), it starts to behave weirdly: WHAT HAPPENS: All Unity eye-candies stop to work and cause a session refresh. I mean, when I press Alt (HUD), or Super (Dash), or even when I hover my mouse over an icon on the launcher the system goes through a mini-crash: all elements on the screen disappear for ~2 seconds, and they come back again. I never see HUD, Dash, or the laucher tooltip that I intended to see. POSSIBLE PROBLEM: Is it safe to say 3D accleration has stopped working after kernel update? SYSTEM SPECS: Intel Core 2 CPU P8600 @ 2.40GHz x 2, Mobile Intel GM45 Express Chipset, 64-bit (and by the way, it is running Libreboot as BIOS) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17 Uname: Linux 4.10.0-28-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sun Jan 14 22:16:30 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller [17aa:20e4] Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller [17aa:20e4] InstallationDate: Installed on 2018-01-13 (1 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: LENOVO 74595FG ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-28-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/07/2016 dmi.bios.vendor: coreboot dmi.bios.version: CBET4000 3774c98 dmi.board.name: 74595FG dmi.board.vendor: LENOVO dmi.board.version: ThinkPad X200 dmi.chassis.type: 9 dmi.chassis.vendor: LENOVO dmi.modalias: dmi:bvncoreboot:bvrCBET40003774c98:bd09/07/2016:svnLENOVO:pn74595FG:pvrThinkPadX200:rvnLENOVO:rn74595FG:rvrThinkPadX200:cvnLENOVO:ct9:cvr: dmi.product.name: 74595FG dmi.product.version: ThinkPad X200 dmi.sys.vendor: LENOVO 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.0.7-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~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: Sat Jan 13 16:11:04 2018 xserver.configfile: default xserver.errors: Serial Wacom Tablet WACf004 stylus: wcmWriteWait error : Input/output error Serial Wacom Tablet WACf004 stylus: wcmWriteWait error : Input/output error PreInit returned 8 for "Serial Wacom Tablet WACf004 stylus" xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.3-1ubuntu1~16.04.2 xserver.video_driver: modeset ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 crash 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/1743259 Title: 3D acceleration stops working after kernel upgrade Status in xorg package in Ubuntu: New Bug description: I have a Thinkpad X200. I installed Ubunntu 16.04.3. It works fine immediately after installation (kernel 4.10.0-28). But when I install updates (kernel 4.13, post Meltdown/Spectre), it starts to behave weirdly: WHAT HAPPENS: All Unity eye-candies stop to work and cause a session refresh. I mean, when I press Alt (HUD), or Super (Dash), or even when I hover my mouse over an icon on the launcher the system goes through a mini-crash: all elements on the screen disappear for ~2 seconds, and they come back again. I never see HUD, Dash, or the laucher tooltip that I intended to see. POSSIBLE PROBLEM: Is it safe to say 3D accleration has stopped working after kernel update? SYSTEM SPECS: Intel Core 2 CPU P8600 @ 2.40GHz x 2, Mobile Intel GM45 Express Chipset, 64-bit (and by the way, it is running Libreboot as BIOS) ProblemTyp
[Desktop-packages] [Bug 1743260] [NEW] lightDB crash report after login
Public bug reported: I just get a popup that lightdm has crashed signal 11, seconds after I have logged in ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: lightdm 1.22.0-0ubuntu2.1 ProcVersionSignature: Ubuntu 4.10.0-42.46-generic 4.10.17 Uname: Linux 4.10.0-42-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.10 Architecture: amd64 CurrentDesktop: Unity:Unity7 Date: Mon Jan 15 08:26:40 2018 InstallationDate: Installed on 2017-12-29 (16 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug zesty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1743260 Title: lightDB crash report after login Status in lightdm package in Ubuntu: New Bug description: I just get a popup that lightdm has crashed signal 11, seconds after I have logged in ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: lightdm 1.22.0-0ubuntu2.1 ProcVersionSignature: Ubuntu 4.10.0-42.46-generic 4.10.17 Uname: Linux 4.10.0-42-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.10 Architecture: amd64 CurrentDesktop: Unity:Unity7 Date: Mon Jan 15 08:26:40 2018 InstallationDate: Installed on 2017-12-29 (16 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1743260/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1721428] Re: Artful (17.10) Session logout after screen turned off
Actually logout can occur without any cable manipulation or turning on/off external monitor. Few times it already happened to me with just lock screen activated. No standby, no hibernate. After I came back, I expected a screen to enter password for unlock, but login screen appear... Means session was logged out and all work lost... No restart was made concerning uptime result... My config: Lenovo P50, noveau driver for nvidia, Ubuntu17.10, everything updated to most recent versions -- 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/1721428 Title: Artful (17.10) Session logout after screen turned off Status in GNOME Shell: Unknown Status in Nouveau Xorg driver: New Status in gnome-shell package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: Whenever I turn off my screen, the computer (a desktop PC) logs me out of my session. Here is a discussion thread with users of similar issue: https://ubuntuforums.org/showthread.php?t=2372388&p=13694312&posted=1#post13694312 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1721428/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1721428] Re: Artful (17.10) Session logout after screen turned off
I can confirm this as well when using Ubuntu 17.10. I'm on a desktop (Shuttle XPC DH110SE) with Skylake processor and Intel graphics with latest updates. Didn't have any problems on 17.04, don't have problems when using Gnome on logon. What I can add: I have no extension enabled - at least none of the ones displayed in Gnome Tweaks' "Extensions" tab. And it seemed to force log-off when a HDMI cable was plugged into my PC, but was not connected to a display. The actual connection to the display is done via DisplayPort. So the dead-end HDMI cable could cause trouble? -- 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/1721428 Title: Artful (17.10) Session logout after screen turned off Status in GNOME Shell: Unknown Status in Nouveau Xorg driver: New Status in gnome-shell package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: Whenever I turn off my screen, the computer (a desktop PC) logs me out of my session. Here is a discussion thread with users of similar issue: https://ubuntuforums.org/showthread.php?t=2372388&p=13694312&posted=1#post13694312 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1721428/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1652272] Re: Firefox suddenly loses internet connection
** Changed in: firefox Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1652272 Title: Firefox suddenly loses internet connection Status in Mozilla Firefox: Invalid Status in Ubuntu GNOME: Confirmed Status in firefox package in Ubuntu: Confirmed Bug description: Since earlier today I have found that after about 10 minutes or less of using Firefox that suddenly for no apparent reason pages will refuse to load any contents, and although Firefox does not take me to the page which says it can't reach the site, it doesn't manage to load anything as though its internet connection has suddenly been lost. It won't even let me check for updates for plugins and gives an error for that. I have tested with other applications such as ping and the internet connection is fine, it's just Firefox which loses it. I have noticed that when I run firefox from Terminal that this is the output to begin with: 1482487989643 addons.webextension.fire...@ghostery.comWARN Loading extension 'fire...@ghostery.com': Reading manifest: Error processing background.persistent: Event pages are not currently supported. This will run as a persistent background page. 1482487989666 addons.webextension.fire...@ghostery.comWARN Loading extension 'fire...@ghostery.com': Reading manifest: Error processing author: An unexpected property was found in the WebExtension manifest. 1482487989666 addons.webextension.fire...@ghostery.comWARN Loading extension 'fire...@ghostery.com': Reading manifest: Error processing version_name: An unexpected property was found in the WebExtension manifest. 1482487989666 addons.webextension.fire...@ghostery.comWARN Loading extension 'fire...@ghostery.com': Reading manifest: Error processing options_page: An unexpected property was found in the WebExtension manifest. 1482487989708 addons.webextension.fire...@ghostery.comWARN Please specify whether you want browser_style or not in your browser_action options. Promise resolved after context unloaded Then when the problem starts to occur, I find that the only way to resolve it, if even for a short period, is to restart the browser, so I tell Firefox to quit, however although the window does close, the process carries on and this is the output: tabs.onRemoved event fired after context unloaded. tabs.onRemoved event fired after context unloaded. tabs.onRemoved event fired after context unloaded. console.error: Message: Error: SessionFile is closed Stack: SessionFileInternal.write@resource://app/modules/sessionstore/SessionFile.jsm:315:29 this.SessionFile.write@resource://app/modules/sessionstore/SessionFile.jsm:76:12 SessionSaverInternal._writeState@resource://app/modules/sessionstore/SessionSaver.jsm:259:12 SessionSaverInternal._saveState@resource://app/modules/sessionstore/SessionSaver.jsm:230:12 SessionSaverInternal._saveStateAsync@resource://app/modules/sessionstore/SessionSaver.jsm:243:5 SessionSaverInternal.runDelayed/this._timeoutID<@resource://app/modules/sessionstore/SessionSaver.jsm:147:40 setTimeout_timer@resource://gre/modules/Timer.jsm:30:5 ExceptionHandler::GenerateDump cloned child 12324 ExceptionHandler::SendContinueSignalToChild sent continue signal to child ExceptionHandler::WaitForContinueSignal waiting for continue signal... I am then told that Firefox crashed and asked if I would like to submit a report, so far I have told it to submit a report three times as the crash has occurred that number of times. For that entire period of time this is the output from Firefox in syslog: Dec 23 10:00:42 firefox.desktop[11349]: 1482487242751#011addons.webextension.fire...@ghostery.com#011WARN#011Loading extension 'fire...@ghostery.com': Reading manifest: Error processing background.persistent: Event pages are not currently supported. This will run as a persistent background page. Dec 23 10:00:42 firefox.desktop[11349]: 1482487242778#011addons.webextension.fire...@ghostery.com#011WARN#011Loading extension 'fire...@ghostery.com': Reading manifest: Error processing author: An unexpected property was found in the WebExtension manifest. Dec 23 10:00:42 firefox.desktop[11349]: 1482487242779#011addons.webextension.fire...@ghostery.com#011WARN#011Loading extension 'fire...@ghostery.com': Reading manifest: Error processing version_name: An unexpected property was found in the WebExtension manifest. Dec 23 10:00:42 firefox.desktop[11349]: 1482487242779#011addons.webextension.fire...@ghostery.com#011WARN#011Loading extension 'fire...@ghostery.com': Reading manifest: Error processing options_page: An unexpected property was f
[Desktop-packages] [Bug 1742653] Re: chromium-browser 63+ packages 50+ MB of binaries only needed at build time
** Branch linked: lp:~chromium-team/chromium-browser/trusty-stable -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1742653 Title: chromium-browser 63+ packages 50+ MB of binaries only needed at build time Status in chromium-browser package in Ubuntu: In Progress Bug description: As mentioned in [1], it seems like the chromium-browser package might be, since Chromium 63, packaging a new and pretty big (44MB) binary that is not needed at run time, just at build time. This binary is `/usr/lib/chromium-browser/v8_context_snapshot_generator`, which is at the moment being packaged (see file list for bionic in [2]) in the chromium-browser package along with the 1MB related binary that is the only one that should be included in the package: ``` $ ls -ltrh /usr/lib/chromium-browser/v8_context_snapshot* -rwxr-xr-x 1 root root 44M Jan 9 18:21 /usr/lib/chromium-browser/v8_context_snapshot_generator -rw-r--r-- 1 root root 1.6M Jan 9 18:21 /usr/lib/chromium-browser/v8_context_snapshot.bin ``` This can become a big deal in space-constrained installations, of course, but considering that the installed size of the package is ~260MB, this binary alone accounts for ~16% of the package's size, so it would be good to clean that up from the package if possible. [1] https://askubuntu.com/questions/986031/why-is-chromium-browser-63-so-much-bigger-than-62/986132 [2] https://packages.ubuntu.com/bionic/amd64/chromium-browser/filelist [3] https://docs.google.com/document/d/1jpQQX0piaxcHJPWakp_Kr_03g5Gnma5h5-Kdlqu7jVQ/edit#heading=h.k6iklq6rvd30 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1742653/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1742653] Re: chromium-browser 63+ packages 50+ MB of binaries only needed at build time
** Branch linked: lp:~chromium-team/chromium-browser/xenial-stable -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1742653 Title: chromium-browser 63+ packages 50+ MB of binaries only needed at build time Status in chromium-browser package in Ubuntu: In Progress Bug description: As mentioned in [1], it seems like the chromium-browser package might be, since Chromium 63, packaging a new and pretty big (44MB) binary that is not needed at run time, just at build time. This binary is `/usr/lib/chromium-browser/v8_context_snapshot_generator`, which is at the moment being packaged (see file list for bionic in [2]) in the chromium-browser package along with the 1MB related binary that is the only one that should be included in the package: ``` $ ls -ltrh /usr/lib/chromium-browser/v8_context_snapshot* -rwxr-xr-x 1 root root 44M Jan 9 18:21 /usr/lib/chromium-browser/v8_context_snapshot_generator -rw-r--r-- 1 root root 1.6M Jan 9 18:21 /usr/lib/chromium-browser/v8_context_snapshot.bin ``` This can become a big deal in space-constrained installations, of course, but considering that the installed size of the package is ~260MB, this binary alone accounts for ~16% of the package's size, so it would be good to clean that up from the package if possible. [1] https://askubuntu.com/questions/986031/why-is-chromium-browser-63-so-much-bigger-than-62/986132 [2] https://packages.ubuntu.com/bionic/amd64/chromium-browser/filelist [3] https://docs.google.com/document/d/1jpQQX0piaxcHJPWakp_Kr_03g5Gnma5h5-Kdlqu7jVQ/edit#heading=h.k6iklq6rvd30 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1742653/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1742653] Re: chromium-browser 63+ packages 50+ MB of binaries only needed at build time
** Branch linked: lp:~chromium-team/chromium-browser/zesty-stable -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1742653 Title: chromium-browser 63+ packages 50+ MB of binaries only needed at build time Status in chromium-browser package in Ubuntu: In Progress Bug description: As mentioned in [1], it seems like the chromium-browser package might be, since Chromium 63, packaging a new and pretty big (44MB) binary that is not needed at run time, just at build time. This binary is `/usr/lib/chromium-browser/v8_context_snapshot_generator`, which is at the moment being packaged (see file list for bionic in [2]) in the chromium-browser package along with the 1MB related binary that is the only one that should be included in the package: ``` $ ls -ltrh /usr/lib/chromium-browser/v8_context_snapshot* -rwxr-xr-x 1 root root 44M Jan 9 18:21 /usr/lib/chromium-browser/v8_context_snapshot_generator -rw-r--r-- 1 root root 1.6M Jan 9 18:21 /usr/lib/chromium-browser/v8_context_snapshot.bin ``` This can become a big deal in space-constrained installations, of course, but considering that the installed size of the package is ~260MB, this binary alone accounts for ~16% of the package's size, so it would be good to clean that up from the package if possible. [1] https://askubuntu.com/questions/986031/why-is-chromium-browser-63-so-much-bigger-than-62/986132 [2] https://packages.ubuntu.com/bionic/amd64/chromium-browser/filelist [3] https://docs.google.com/document/d/1jpQQX0piaxcHJPWakp_Kr_03g5Gnma5h5-Kdlqu7jVQ/edit#heading=h.k6iklq6rvd30 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1742653/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1742653] Re: chromium-browser 63+ packages 50+ MB of binaries only needed at build time
** Branch linked: lp:~chromium-team/chromium-browser/bionic-stable -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1742653 Title: chromium-browser 63+ packages 50+ MB of binaries only needed at build time Status in chromium-browser package in Ubuntu: In Progress Bug description: As mentioned in [1], it seems like the chromium-browser package might be, since Chromium 63, packaging a new and pretty big (44MB) binary that is not needed at run time, just at build time. This binary is `/usr/lib/chromium-browser/v8_context_snapshot_generator`, which is at the moment being packaged (see file list for bionic in [2]) in the chromium-browser package along with the 1MB related binary that is the only one that should be included in the package: ``` $ ls -ltrh /usr/lib/chromium-browser/v8_context_snapshot* -rwxr-xr-x 1 root root 44M Jan 9 18:21 /usr/lib/chromium-browser/v8_context_snapshot_generator -rw-r--r-- 1 root root 1.6M Jan 9 18:21 /usr/lib/chromium-browser/v8_context_snapshot.bin ``` This can become a big deal in space-constrained installations, of course, but considering that the installed size of the package is ~260MB, this binary alone accounts for ~16% of the package's size, so it would be good to clean that up from the package if possible. [1] https://askubuntu.com/questions/986031/why-is-chromium-browser-63-so-much-bigger-than-62/986132 [2] https://packages.ubuntu.com/bionic/amd64/chromium-browser/filelist [3] https://docs.google.com/document/d/1jpQQX0piaxcHJPWakp_Kr_03g5Gnma5h5-Kdlqu7jVQ/edit#heading=h.k6iklq6rvd30 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1742653/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1742653] Re: chromium-browser 63+ packages 50+ MB of binaries only needed at build time
** Branch linked: lp:~chromium-team/chromium-browser/artful-stable -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1742653 Title: chromium-browser 63+ packages 50+ MB of binaries only needed at build time Status in chromium-browser package in Ubuntu: In Progress Bug description: As mentioned in [1], it seems like the chromium-browser package might be, since Chromium 63, packaging a new and pretty big (44MB) binary that is not needed at run time, just at build time. This binary is `/usr/lib/chromium-browser/v8_context_snapshot_generator`, which is at the moment being packaged (see file list for bionic in [2]) in the chromium-browser package along with the 1MB related binary that is the only one that should be included in the package: ``` $ ls -ltrh /usr/lib/chromium-browser/v8_context_snapshot* -rwxr-xr-x 1 root root 44M Jan 9 18:21 /usr/lib/chromium-browser/v8_context_snapshot_generator -rw-r--r-- 1 root root 1.6M Jan 9 18:21 /usr/lib/chromium-browser/v8_context_snapshot.bin ``` This can become a big deal in space-constrained installations, of course, but considering that the installed size of the package is ~260MB, this binary alone accounts for ~16% of the package's size, so it would be good to clean that up from the package if possible. [1] https://askubuntu.com/questions/986031/why-is-chromium-browser-63-so-much-bigger-than-62/986132 [2] https://packages.ubuntu.com/bionic/amd64/chromium-browser/filelist [3] https://docs.google.com/document/d/1jpQQX0piaxcHJPWakp_Kr_03g5Gnma5h5-Kdlqu7jVQ/edit#heading=h.k6iklq6rvd30 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1742653/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1731417] Re: Installed printer removed after suspend/resume
Please do the following: Edit /etc/cups/cups-browsed.conf so that it has a line DebugLogging file without "#" in the beginning. Do not modify the other lines. Attach your /etc/cups/cups-browsed.conf and your /etc/cups/cupsd.conf files to this bug report. Reboot your system. Run lpstat -v and post the output here. Set up your printer with hp-setup as you are used to. immediately afterwards run the command lpstat -v and poste the output here. Copy also the file /etc/cups/printers.conf (you will need "sudo") and post its contents here. Print a job and do "lpstat -v" and copy printers.conf again. Post the output of "lpstat -v" and the contents of the file here again. Now suspend your system, wait for the suspend to complete and resume again. Do "lpstat -v" and copy printers.conf again. Post the output of "lpstat -v" and the contents of the file here again. Did your print queue go away again? If not, reboot your system. Did it go away now? If so, do "lpstat -v" and copy printers.conf again. Post the output of "lpstat -v" and the contents of the file here again. Please attach the files /var/log/cups/error_log and /var/log/cups/cups- browsed_log to this bug report. Please do not compress any files and do not package the files together when attaching them to this bug report, to make it easier to read the files right out of the browser. ** Changed in: cups (Ubuntu) Status: New => Incomplete ** Changed in: hplip (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1731417 Title: Installed printer removed after suspend/resume Status in cups package in Ubuntu: Incomplete Status in hplip package in Ubuntu: Incomplete Bug description: After installing artful, I configured my HP LaserJet M1212nf via network as usual via hp-setup. Installation worked and I could print/scan via network, but next time I needed to print, the printer was gone from the system. Basically, every time I need to print, I have to install the printer again. I'm not sure when the printer disappears, but I can reproduce consistently. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: hplip-gui 3.17.7+repack0-3 ProcVersionSignature: Ubuntu 4.8.0-59.64-generic 4.8.17 Uname: Linux 4.8.0-59-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CupsErrorLog: CurrentDesktop: GNOME Date: Fri Nov 10 09:33:12 2017 InstallationDate: Installed on 2017-07-30 (102 days ago) InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Alpha amd64 (20170730) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. PackageArchitecture: all Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.8.0-59-generic.efi.signed root=UUID=c2e94423-ace9-437c-ab5b-6dd78d6a052a ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: hplip UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/23/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F15 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B75M-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF15:bd10/23/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnB75M-D3H:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1731417/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1743248] [NEW] package software-center (not installed) failed to install/upgrade: Unterprozess installiertes post-removal-Skript gab den Fehlerwert 1 zurück
Public bug reported: Nothing ProblemType: Package DistroRelease: elementary 0.4.1 Package: software-center (not installed) ProcVersionSignature: Ubuntu 4.13.0-29.32~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-29-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.15 AptOrdering: software-center: Purge NULL: ConfigurePending Architecture: amd64 Date: Sun Jan 14 20:24:17 2018 DpkgTerminalLog: Entfernen von software-center (16.01+16.04.20160420) ... Löschen der Konfigurationsdateien von software-center (16.01+16.04.20160420) ... rmdir: konnte '/var/cache/software-center/xapian/' nicht entfernen: Datei oder Verzeichnis nicht gefunden dpkg: Fehler beim Bearbeiten des Paketes software-center (--purge): Unterprozess installiertes post-removal-Skript gab den Fehlerwert 1 zurück ErrorMessage: Unterprozess installiertes post-removal-Skript gab den Fehlerwert 1 zurück InstallationDate: Installed on 2018-01-14 (0 days ago) InstallationMedia: elementary OS 0.4.1 "Loki" - Stable amd64 (20170814) RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.25 SourcePackage: software-center Title: package software-center (not installed) failed to install/upgrade: Unterprozess installiertes post-removal-Skript gab den Fehlerwert 1 zurück UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: software-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package loki -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-center in Ubuntu. https://bugs.launchpad.net/bugs/1743248 Title: package software-center (not installed) failed to install/upgrade: Unterprozess installiertes post-removal-Skript gab den Fehlerwert 1 zurück Status in software-center package in Ubuntu: New Bug description: Nothing ProblemType: Package DistroRelease: elementary 0.4.1 Package: software-center (not installed) ProcVersionSignature: Ubuntu 4.13.0-29.32~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-29-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.15 AptOrdering: software-center: Purge NULL: ConfigurePending Architecture: amd64 Date: Sun Jan 14 20:24:17 2018 DpkgTerminalLog: Entfernen von software-center (16.01+16.04.20160420) ... Löschen der Konfigurationsdateien von software-center (16.01+16.04.20160420) ... rmdir: konnte '/var/cache/software-center/xapian/' nicht entfernen: Datei oder Verzeichnis nicht gefunden dpkg: Fehler beim Bearbeiten des Paketes software-center (--purge): Unterprozess installiertes post-removal-Skript gab den Fehlerwert 1 zurück ErrorMessage: Unterprozess installiertes post-removal-Skript gab den Fehlerwert 1 zurück InstallationDate: Installed on 2018-01-14 (0 days ago) InstallationMedia: elementary OS 0.4.1 "Loki" - Stable amd64 (20170814) RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.25 SourcePackage: software-center Title: package software-center (not installed) failed to install/upgrade: Unterprozess installiertes post-removal-Skript gab den Fehlerwert 1 zurück UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/1743248/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1743247] [NEW] B2 Python APIs are missing
Public bug reported: When I try to use the B2 backend with 0.7.16-0ubuntu1ppa1347~ubuntu16.04.1, I get the following error: > BackendException: B2 backend requires B2 Python APIs (pip install b2) It seems odd to me that the library would be installed outside of apt. I had an old package from trusty (duplicity_0.7.14-0ubuntu0ppa1316~ubuntu14.04.1_amd64.deb) with 0.7.14 which works fine on 16.04, which makes me think this regression was in 0.7.15 or 0.7.16. ** Affects: duplicity (Ubuntu) Importance: Undecided Status: New ** Description changed: When I try to use the B2 backend with 0.7.16-0ubuntu1ppa1347~ubuntu16.04.1, I get the following error: > BackendException: B2 backend requires B2 Python APIs (pip install b2) It seems odd to me that the library would be installed outside of apt. I had an old package from trusty (duplicity_0.7.14-0ubuntu0ppa1316~ubuntu14.04.1_amd64.deb) with 0.7.14 - which works fine on 16.04, which makes me think this regression was - added in 0.7.15 or 0.7.16. + which works fine on 16.04, which makes me think this regression was in + 0.7.15 or 0.7.16. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1743247 Title: B2 Python APIs are missing Status in duplicity package in Ubuntu: New Bug description: When I try to use the B2 backend with 0.7.16-0ubuntu1ppa1347~ubuntu16.04.1, I get the following error: > BackendException: B2 backend requires B2 Python APIs (pip install b2) It seems odd to me that the library would be installed outside of apt. I had an old package from trusty (duplicity_0.7.14-0ubuntu0ppa1316~ubuntu14.04.1_amd64.deb) with 0.7.14 which works fine on 16.04, which makes me think this regression was in 0.7.15 or 0.7.16. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/1743247/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1743246] [NEW] problema audio
Public bug reported: Buonasera, è da qualche giorno che non funziona l'Audio nel mio sistema, nell'icona in alto a destra del desktop che indica il volume c'è una x come se fosse disabilitata la scheda audio, nella scheda audio sulle impostazioni di sistema nel riquadro che indica Riproduci suono tramite, non si vede la scheda audio. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-108.131-generic 4.4.98 Uname: Linux 4.4.0-108-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] È una directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.102 Mon Jan 16 13:06:29 PST 2017 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.5) .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: Sun Jan 14 20:28:52 2018 DistUpgraded: 2016-05-03 22:27:56,922 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation G92 [GeForce 9800 GT] [10de:0614] (rev a2) (prog-if 00 [VGA controller]) Subsystem: CardExpert Technology G92 [GeForce 9800 GT] [10b0:0401] InstallationDate: Installed on 2016-01-19 (726 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE=it PATH=(custom, no user) LANG=it_IT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-108-generic root=UUID=90cd0f82-be9c-4d2d-8632-288f1a48bc83 ro quiet splash SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2016-05-03 (620 days ago) dmi.bios.date: 03/11/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0303 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5Q TURBO dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0303:bd03/11/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5QTURBO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer 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.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.2 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Sun Jan 14 20:18:05 2018 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputMicrosoft Basic Optical Mouse MOUSE, id 8 inputAT Translated Set 2 keyboard KEYBOARD, id 9 xserver.errors: open /dev/fb0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.outputs: 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/1743246 Title: problema audio Status in xorg package in Ubuntu: New Bug description: Buonasera, è da qualche giorno che non funziona l'Audio nel mio sistema, nell'icona in alto a destra del desktop che indica il volume c'è una x come se fosse disabilitata la scheda audio, nella scheda audio sulle impostazioni di sistema nel riquadro che indica Riproduci suono tramite, non si vede la scheda audio. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-108.131-generic 4.4.98 Uname: Linux 4.4.0-108-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] È una directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary
[Desktop-packages] [Bug 1735594] Re: [regression] compiz crashes after Mesa upgrade
Proposed fixed this bug on my Dell Vostro 1015 description: Portable Computer product: Vostro 1015 vendor: Dell Inc. serial: 9KKDQQ1 width: 64 bits capabilities: smbios-2.4 dmi-2.4 vsyscall32 configuration: boot=normal chassis=portable uuid=44454C4C-4B00-104B-8044-B9C04F515131 *-cpu description: CPU product: Intel(R) Core(TM)2 Duo CPU T6670 @ 2.20GHz vendor: Intel Corp. physical id: 400 bus info: cpu@0 slot: Microprocessor size: 918MHz capacity: 2201MHz width: 64 bits *-display:0 description: VGA compatible controller product: Mobile 4 Series Chipset Integrated Graphics Controller vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 version: 07 width: 64 bits clock: 33MHz capabilities: msi pm vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 resources: irq:16 memory:f6c0-f6ff memory:e000-efff ioport:efe8(size=8) memory:c-d *-display:1 UNCLAIMED description: Display controller product: Mobile 4 Series Chipset Integrated Graphics Controller vendor: Intel Corporation physical id: 2.1 bus info: pci@:00:02.1 version: 07 width: 64 bits clock: 33MHz capabilities: pm bus_master cap_list configuration: latency=0 resources: memory:f6b0-f6bf libgl1-mesa-dri: Installed: 17.2.4-0ubuntu1~16.04.4 Candidate: 17.2.4-0ubuntu1~16.04.4 Version table: *** 17.2.4-0ubuntu1~16.04.4 100 100 /var/lib/dpkg/status 17.2.4-0ubuntu1~16.04.2 500 500 http://do.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 11.2.0-1ubuntu2 500 500 http://do.archive.ubuntu.com/ubuntu xenial/main amd64 Packages clock: 200MHz capabilities: x86-64 fpu fpu_exception wp vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx constant_tsc arch_perfmon pebs bts rep_good nopl cpuid aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 xsave lahf_lm pti tpr_shadow vnmi flexpriority dtherm ida cpufreq configuration: cores=2 enabledcores=2 threads=2 *-pci description: Host bridge product: Mobile 4 Series Chipset Memory Controller Hub vendor: Intel Corporation physical id: 100 bus info: pci@:00:00.0 version: 07 width: 32 bits clock: 33MHz -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1735594 Title: [regression] compiz crashes after Mesa upgrade Status in mesa package in Ubuntu: Fix Committed Status in mesa source package in Xenial: Fix Committed Status in mesa source package in Artful: Fix Committed Bug description: [Impact] When I use the Unity session I automatically get logged out under these conditions: When I hover with my mouse over any icon of the sidebar. When I press the alt key. When I press the super key. running dmesg after this unwanted logout happens I get following information: compiz[10616]: segfault at 0 ip 7fbca309feeb sp 7fff5f59a4d0 error 4 in i965_dri.so[7fbca2af6000+7e4000] This is caused by a mesa upgrade, which added a patch for bug #1727401. The crasher is reproduced on: - gen4 / gen5 Intel - if using modesetting X driver, like when xserver-xorg-video-intel is not installed, or the HWE stack is installed (xserver-xorg-core-hwe-16.04 defaults to modesetting) [Test case] Log in to Unity, open the dash or try to log out etc. Compiz shouldn't crash. [Regression potential] The backported patches need to be tested, here for regressions and on 1727401 that they fix the original bug (again). Best to test on a wide array of Intel HW: gen4 (965GM/GM45/G45) gen5 (Ironlake) gen6 (Sandy Bridge) gen7 (Bay Trail, Ivy Bridge, Haswell) gen8 (Braswell, Broadwell) gen9 (Apollo Lake, Skylake, Gemini Lake, Kaby Lake, Coffee Lake) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1735594/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1251182] Re: Thunderbird: Deleted emails get lost instead of going to the Trash folder
** Changed in: thunderbird Status: Confirmed => Fix Released -- 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/1251182 Title: Thunderbird: Deleted emails get lost instead of going to the Trash folder Status in Mozilla Thunderbird: Fix Released Status in thunderbird package in Ubuntu: Confirmed Bug description: I'm using Ubuntu 13.04 x64 and Thunderbird 1:24.1.0+build1-0ubuntu0.13.04.1 Hungarian locale. When I delete an email in Thunderbird (IMAP) it gets permanently deleted instead of it going to the Trash folder. According to the settings the deleted emails should go to the Trash folder. See attached screenshot. I can't reproduce this issue on Windows with Thunderbird 24.1.0. According to bugzilla this has something to do with localized versions of Thunderbird not working correclty: https://bugzilla.mozilla.org/show_bug.cgi?id=480393 https://bugzilla.mozilla.org/show_bug.cgi?id=836631 https://bugzilla.mozilla.org/show_bug.cgi?id=160644 ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: thunderbird 1:24.1.0+build1-0ubuntu0.13.04.1 ProcVersionSignature: Ubuntu 3.8.0-33.48-generic 3.8.13.11 Uname: Linux 3.8.0-33-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.9.2-0ubuntu8.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: anied 1723 F pulseaudio BuildID: 20131028130532 CRDA: country GB: (2402 - 2482 @ 40), (N/A, 20) (5170 - 5250 @ 40), (N/A, 20) (5250 - 5330 @ 40), (N/A, 20), DFS (5490 - 5710 @ 40), (N/A, 27), DFS Channel: Unavailable Date: Thu Nov 14 11:06:10 2013 ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-07-22 (114 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) IpRoute: default via 192.168.1.1 dev eth0 proto static 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.112 metric 1 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.119 metric 9 MarkForUpload: True PrefSources: prefs.js [Profile]/extensions/{e2fda1a4-762b-4020-b5ad-a41df1933103}/defaults/preferences/lightning.js Prefs: extensions.lastAppVersion: "24.1.0" (prefs.js) network.cookie.prefsMigrated: true (prefs.js) places.database.lastMaintenance: 1384248354 (prefs.js) places.history.expiration.transient_current_max_pages: 104858 (prefs.js) plugin.importedState: true (prefs.js) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=hu_HU.UTF-8 SHELL=/bin/bash Profiles: Profile0 (Default) - LastVersion=24.1.0/20131028130532 (In use) RelatedPackageVersions: icedtea-7-plugin 1.3.2-1ubuntu1.1 totem-mozilla 3.6.3-0ubuntu6 rhythmbox-mozilla 2.98-0ubuntu5 RunningIncompatibleAddons: False SourcePackage: thunderbird UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/22/2013 dmi.bios.vendor: Acer dmi.bios.version: V2.17 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Mimic dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.17 dmi.modalias: dmi:bvnAcer:bvrV2.17:bd03/22/2013:svnAcer:pnV5-171:pvrV2.17:rvnAcer:rnMimic:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.17: dmi.product.name: V5-171 dmi.product.version: V2.17 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1251182/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1743244] [NEW] Keyboard autorepeat does not work after latest update
Public bug reported: After latest update, keyboard autorepeat has stopped working. I can confirm that the problem is related to the peaq-wmi module having been recently whitelisted as using modprobe to remove peaq-wmi fixes the problem. Workaround: Blacklist the peaq-wmi module I really think the peaq-wmi module should be re-blacklised by default until the bugs can be worked out. Running Xubuntu, version 16.04.3 LTS ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: evince 3.18.2-1ubuntu4.3 ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13 Uname: Linux 4.13.0-26-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: XFCE Date: Sun Jan 14 12:56:53 2018 InstallationDate: Installed on 2017-12-18 (27 days ago) InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: evince (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1743244 Title: Keyboard autorepeat does not work after latest update Status in evince package in Ubuntu: New Bug description: After latest update, keyboard autorepeat has stopped working. I can confirm that the problem is related to the peaq-wmi module having been recently whitelisted as using modprobe to remove peaq-wmi fixes the problem. Workaround: Blacklist the peaq-wmi module I really think the peaq-wmi module should be re-blacklised by default until the bugs can be worked out. Running Xubuntu, version 16.04.3 LTS ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: evince 3.18.2-1ubuntu4.3 ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13 Uname: Linux 4.13.0-26-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: XFCE Date: Sun Jan 14 12:56:53 2018 InstallationDate: Installed on 2017-12-18 (27 days ago) InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1743244/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 683388] Re: pwd is changed when opening a new tab from withing a symbolic link
*** This bug is a duplicate of bug 263637 *** https://bugs.launchpad.net/bugs/263637 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-terminal (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/683388 Title: pwd is changed when opening a new tab from withing a symbolic link Status in gnome-terminal package in Ubuntu: Confirmed Bug description: Binary package hint: gnome-terminal Normally when you open up a new tab your pwd i the new tab remains the same as your pwd in the old tab. However, If you have navigated into a directory structure that contains symbolic links and open up a new tab, your pwd is changed to the absolute path, bypassing any symbolic links. For example: cd ~ mkdir temp cd temp ln -s /media drives cd drives # at this point 'pwd' should show ~/temp/drives # however if a new tab is opened, 'pwd' would show /media This is in Gnome 2.32.0 on Ubuntu 10.10 ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: gnome-terminal 2.32.0-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.35-23.41-generic 2.6.35.7 Uname: Linux 2.6.35-23-generic x86_64 Architecture: amd64 Date: Tue Nov 30 16:25:23 2010 EcryptfsInUse: Yes ExecutablePath: /usr/bin/gnome-terminal InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) ProcEnviron: LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: gnome-terminal XsessionErrors: (polkit-gnome-authentication-agent-1:1623): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed (nautilus:1624): GConf-CRITICAL **: gconf_value_free: assertion `value != NULL' failed (nautilus:1624): GConf-CRITICAL **: gconf_value_free: assertion `value != NULL' failed (nautilus:1624): GConf-CRITICAL **: gconf_value_free: assertion `value != NULL' failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/683388/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1743240] [NEW] I can't access the side bar menu
Public bug reported: When I move the mouse over the side bar menu the screen (monitor) starts to blink, the sidebar and the menu bar (top) disappear. It takes some seconds to come back the normality. Ubuntu 16.04.3 LTS Release: 16.04 Expected to happen: click over the icons in the side bar and open the applications. What happened: if the mouse cursor goes over the side bar the screen starts to blink, the side bar and the top menu disappear for some seconds. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13 Uname: Linux 4.13.0-26-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sun Jan 14 08:55:21 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated Graphics Controller [1025:029b] Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated Graphics Controller [1025:029b] InstallationDate: Installed on 2018-01-02 (11 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: Acer Aspire 1410 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-26-generic root=UUID=dac73f30-7fd8-45c0-a3a1-5f92fdee9322 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/14/2009 dmi.bios.vendor: INSYDE dmi.bios.version: v0.3115 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Base Board Product Name dmi.board.vendor: Acer dmi.board.version: Base Board Version dmi.chassis.type: 1 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDE:bvrv0.3115:bd08/14/2009:svnAcer:pnAspire1410:pvrv0.3115:rvnAcer:rnBaseBoardProductName:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion: dmi.product.family: Intel_Mobile dmi.product.name: Aspire 1410 dmi.product.version: v0.3115 dmi.sys.vendor: Acer 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.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~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: Sun Jan 14 07:53:19 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.5-0ubuntu2~16.04.1 xserver.video_driver: modeset ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 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/1743240 Title: I can't access the side bar menu Status in xorg package in Ubuntu: New Bug description: When I move the mouse over the side bar menu the screen (monitor) starts to blink, the sidebar and the menu bar (top) disappear. It takes some seconds to come back the normality. Ubuntu 16.04.3 LTS Release: 16.04 Expected to happen: click over the icons in the side bar and open the applications. What happened: if the mouse cursor goes over the side bar the screen starts to blink, the side bar and the top menu disappear for some seconds. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13 Uname: Linux 4.13.0-26-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sun Jan 14 08:55:21 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated Graphics Controll
[Desktop-packages] [Bug 1743234] Re: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: tentative de remplacement de « /lib/udev/hwdb.d/20-sane.hwdb », qui est différent d'aut
*** 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/1743234 Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: tentative de remplacement de « /lib/udev/hwdb.d/20-sane.hwdb », qui est différent d'autres instances du paquet libsane1:i386 Status in sane-backends package in Ubuntu: New Bug description: error comes in at every boot (xubuntu 17.10) ProblemType: Package DistroRelease: Ubuntu 17.10 Package: libsane1 1.0.27-1~experimental2ubuntu2.1 ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 Uname: Linux 4.13.0-25-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 Date: Sun Jan 14 15:48:06 2018 ErrorMessage: tentative de remplacement de « /lib/udev/hwdb.d/20-sane.hwdb », qui est différent d'autres instances du paquet libsane1:i386 InstallationDate: Installed on 2018-01-04 (10 days ago) InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1) Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5.1 SourcePackage: sane-backends Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: tentative de remplacement de « /lib/udev/hwdb.d/20-sane.hwdb », qui est différent d'autres instances du paquet 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/1743234/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1743237] Re: gnome-shell crashed with SIGSEGV in meta_window_get_monitor()
*** This bug is a duplicate of bug 1724439 *** https://bugs.launchpad.net/bugs/1724439 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 #1724439, 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/1743237/+attachment/5036894/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1743237/+attachment/5036896/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1743237/+attachment/5036900/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1743237/+attachment/5036901/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1743237/+attachment/5036902/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1743237/+attachment/5036903/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1743237/+attachment/5036904/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1724439 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() ** 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/1743237 Title: gnome-shell crashed with SIGSEGV in meta_window_get_monitor() Status in gnome-shell package in Ubuntu: New Bug description: . ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.26.2-0ubuntu2 Uname: Linux 4.15.0-041500rc7-generic x86_64 ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Sun Jan 14 11:40:41 2018 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2017-11-08 (67 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7fcd150872d4 :mov 0x18(%rax),%eax PC (0x7fcd150872d4) 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 () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 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 () at /usr/lib/libgjs.so.0 Title: gnome-shell crashed with SIGSEGV in meta_window_get_monitor() UpgradeStatus: Upgraded to bionic on 2017-11-20 (55 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1743237/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1656065] Re: Firefox and plugin-container (Chrome_ChildThr): segfault at 0 ip, sp error 6 in plugin-container/libxul.so
I seem to have the same problem on Ubuntu 17.10, firefox-57.0.4+build1-0ubuntu0.17.10.1. I get random crashes about twice a day. The crash is usually accompaigned by a gnome-shell crash & restart. I observe no suspicios activity such as eating up too much RAM or a high CPU usage before the crash. dmesg contains something like: [230270.664890] rfkill: input handler enabled [230276.136725] traps: gnome-shell[2403] general protection ip:7fa4c6c0cde2 sp:7ffe28542d40 error:0 in libgobject-2.0.so.0.5400.1[7fa4c6bd7000+52000] [230295.837969] rfkill: input handler disabled [230308.490256] rfkill: input handler enabled [230332.394705] Chrome_~dThread[59613]: segfault at 0 ip 7f3389d10e7d sp 7f3387ffdb10 error 6 in libxul.so[7f3388ec3000+5805000] [230332.475649] Chrome_~dThread[59369]: segfault at 0 ip 7f7482b10e7d sp 7f7480dfdb10 error 6 [230332.475652] Chrome_~dThread[67396]: segfault at 0 ip 7f860b910e7d sp 7f8609bfdb10 error 6 [230332.475656] in libxul.so[7f7481cc3000+5805000] [230332.475657] in libxul.so[7f860aac3000+5805000] [230341.929151] rfkill: input handler disabled -- 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/1656065 Title: Firefox and plugin-container (Chrome_ChildThr): segfault at 0 ip, sp error 6 in plugin-container/libxul.so Status in firefox package in Ubuntu: Expired Bug description: Hello. Some days ago, Firefox unexpectedly has been closed after a couple of hours (mostly viewed: YouTube and some other websites). Next, a dialog box related to the Mozilla Crash Reporter appeared - with message, that reporter is disabled (which I did earlier via 'about:config' and *datareporting.healthreport.service.enabled* key set to _false_) and no crash report is available even via 'about:crashes' etc. After this situation two entries appeared in the log files: first related to the AppArmor and second: plugin-container segfault. By the way: in the same time there was an update for flash-plugin available (see: 1). Anyway, 'LastCrash' file (which can be found in ~/.mozilla/firefox/Crash Reports/ directory) contains only: 1484142985. Just like all the others files in this directory. There are also two folders called: 'events' and 'pending'. But they are completely empty. However, system log files, such as '/var/log/kern.log' or '/var/log/syslog', contains an interesting entries: ● Jan 11 14:56:25 t4 kernel: [ 4161.295639] type=1400 audit(1484142985.517:46): apparmor="DENIED" operation="open" parent=2818 profile="/usr/lib/firefox/firefox{,*[^s][^h]}" name="/proc/2818/task/" pid=3253 comm="firefox" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000 ● Jan 11 14:56:25 t4 kernel: [ 4161.540727] Chrome_ChildThr[2890]: segfault at 0 ip b76df673 sp b1efe9f0 error 6 in plugin- container[b76d8000+42000] As we know, thanks to the plugin-container, plugins are separated from the browser process, making it more stable, right? So now if a plugin crashes, Firefox should remains unharmed. It looks like this is a known problem (see: 2, 3). By the way; on Moday, 16 January, Firefox has been closed again - no action from my side. Log files contain the same entries as above: ● Jan 16 16:39:35 t4 kernel: [14373.711834] type=1400 audit(1484581175.931:48): apparmor="DENIED" operation="open" parent=2532 profile="/usr/lib/firefox/firefox{,*[^s][^h]}" name="/proc/2532/task/" pid=3389 comm="firefox" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000 ● Jan 16 16:39:36 t4 kernel: [14373.934394] Chrome_ChildThr[3041]: segfault at 0 ip b76f8673 sp b1efe9f0 error 6 in plugin- container[b76f1000+42000] Anyway, after adding these two rules to the Firefox profile, everything seems to be OK and there is not DENIED message for "/proc/*/task/" entry anymore (so the first issue is solved): owner @{PROC}/[0-9]*/task/ r, owner @{PROC}/[0-9]*/task/* r, NOTE: This problem occurs when adobe-flash plugin is not activated and is permanently disabled and also when is used/enabled. Here are some informations about versions etc.: ● Firefox: 50.1.0 ● Flash: 24.0.0.194ubuntu0.12.04.1 ● Linux: 3.2.0-120-generic-pae (3.2.79) i686 ● AppArmor: 2.7.102-0ubuntu3.10 ● Release: 12.04.5 LTS (via `lsb_release -a` command) Best regards. _ [1] https://lists.ubuntu.com/archives/precise-changes/2017-January/026047.html [2] https://bugzilla.mozilla.org/show_bug.cgi?id=1205199 [3] https://bugzilla.redhat.com/show_bug.cgi?id=1253086 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1656065/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1743234] [NEW] package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: tentative de remplacement de « /lib/udev/hwdb.d/20-sane.hwdb », qui est différent d'a
Public bug reported: error comes in at every boot (xubuntu 17.10) ProblemType: Package DistroRelease: Ubuntu 17.10 Package: libsane1 1.0.27-1~experimental2ubuntu2.1 ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 Uname: Linux 4.13.0-25-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 Date: Sun Jan 14 15:48:06 2018 ErrorMessage: tentative de remplacement de « /lib/udev/hwdb.d/20-sane.hwdb », qui est différent d'autres instances du paquet libsane1:i386 InstallationDate: Installed on 2018-01-04 (10 days ago) InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1) Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5.1 SourcePackage: sane-backends Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: tentative de remplacement de « /lib/udev/hwdb.d/20-sane.hwdb », qui est différent d'autres instances du paquet 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/1743234 Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: tentative de remplacement de « /lib/udev/hwdb.d/20-sane.hwdb », qui est différent d'autres instances du paquet libsane1:i386 Status in sane-backends package in Ubuntu: New Bug description: error comes in at every boot (xubuntu 17.10) ProblemType: Package DistroRelease: Ubuntu 17.10 Package: libsane1 1.0.27-1~experimental2ubuntu2.1 ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 Uname: Linux 4.13.0-25-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 Date: Sun Jan 14 15:48:06 2018 ErrorMessage: tentative de remplacement de « /lib/udev/hwdb.d/20-sane.hwdb », qui est différent d'autres instances du paquet libsane1:i386 InstallationDate: Installed on 2018-01-04 (10 days ago) InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1) Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5.1 SourcePackage: sane-backends Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: tentative de remplacement de « /lib/udev/hwdb.d/20-sane.hwdb », qui est différent d'autres instances du paquet 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/1743234/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1725865] Re: Network shows Cable Unplugged
** Also affects: network-manager via https://bugzilla.gnome.org/show_bug.cgi?id=792506 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1725865 Title: Network shows Cable Unplugged Status in NetworkManager: Unknown Status in network-manager package in Ubuntu: New Bug description: This was working perfectly on 17.04, but after installing 17.10 from scratch, the wired network is not detected. It simply shows as Cable Unplugged when in fact there is the same cable still connected directly to the router. This same computer has Windows 10 and it detects the network correctly. I also tested Fedora and it detected the network correctly (The wired one). I am currently using only the Wireless connection because of this. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: network-manager 1.8.4-1ubuntu3 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 Date: Sat Oct 21 17:59:31 2017 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-10-19 (2 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) IpRoute: default via 192.168.1.1 dev wlp9s0 proto static metric 600 169.254.0.0/16 dev wlp9s0 scope link metric 1000 192.168.1.0/24 dev wlp9s0 proto kernel scope link src 192.168.1.2 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlp9s0 wifi connected/org/freedesktop/NetworkManager/Devices/3 Linux ecb8e125-48ff-4994-94c8-bdf3731334ce /org/freedesktop/NetworkManager/ActiveConnection/13 enp0s31f6 ethernet unavailable /org/freedesktop/NetworkManager/Devices/2 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.8.4connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1725865/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1743207] 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/1743207 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: the context is merge when i tried to install itunes 12 using playlinux. it won't t wowrk to install. so idecided tto install first wwine bbeside of playlinux then i thought to use playlinux to finish itunes 12 installation. ProblemType: Package DistroRelease: Ubuntu 17.10 Package: libsane1 1.0.27-1~experimental2ubuntu2.1 ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 Uname: Linux 4.13.0-25-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 Date: Sun Jan 14 12:28:50 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-fCxkux/114-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-09 (35 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) 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: Upgraded to artful on 2018-01-07 (6 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1743207/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1743013] Re: deja-dup fails when launched automatically
Hello Vej, to hear that an issue is not an issue is quite irritating. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to deja-dup in Ubuntu. https://bugs.launchpad.net/bugs/1743013 Title: deja-dup fails when launched automatically Status in deja-dup package in Ubuntu: Invalid Bug description: In #1727653 an error was reported that stated that backup using duplicity failed. However, the error only manifests in duplicity but is triggered by the calling Deja-Dup. Launching Deja-Dup automatically will ALWAYS lead to the error. Launching Deja-Dup from the console/bash will NEVER lead to the error. Any attempts to set number of open file limits do not remedy the issue. Please refer to #1727653 and associated errors as all analysis have gone into duplicity so far. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: deja-dup 36.3-0ubuntu0.1 ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 Uname: Linux 4.13.0-25-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jan 12 18:55:12 2018 InstallationDate: Installed on 2017-10-20 (84 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: deja-dup UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1743013/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1725865] Re: Network shows Cable Unplugged
Hi Sebastien, I have added the corresponding bug here https://bugzilla.gnome.org/show_bug.cgi?id=792506 Is this what it was needed buddy? ** Bug watch added: GNOME Bug Tracker #792506 https://bugzilla.gnome.org/show_bug.cgi?id=792506 -- 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/1725865 Title: Network shows Cable Unplugged Status in network-manager package in Ubuntu: New Bug description: This was working perfectly on 17.04, but after installing 17.10 from scratch, the wired network is not detected. It simply shows as Cable Unplugged when in fact there is the same cable still connected directly to the router. This same computer has Windows 10 and it detects the network correctly. I also tested Fedora and it detected the network correctly (The wired one). I am currently using only the Wireless connection because of this. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: network-manager 1.8.4-1ubuntu3 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 Date: Sat Oct 21 17:59:31 2017 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-10-19 (2 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) IpRoute: default via 192.168.1.1 dev wlp9s0 proto static metric 600 169.254.0.0/16 dev wlp9s0 scope link metric 1000 192.168.1.0/24 dev wlp9s0 proto kernel scope link src 192.168.1.2 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlp9s0 wifi connected/org/freedesktop/NetworkManager/Devices/3 Linux ecb8e125-48ff-4994-94c8-bdf3731334ce /org/freedesktop/NetworkManager/ActiveConnection/13 enp0s31f6 ethernet unavailable /org/freedesktop/NetworkManager/Devices/2 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.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/1725865/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1730540] Re: gnome-shell freezes after resume then unlock
This is still an issue in Ubuntu 18.04. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1730540 Title: gnome-shell freezes after resume then unlock Status in gnome-shell package in Ubuntu: Incomplete Bug description: Often after resuming and then entering my password to unlock gnome- shell, when I press the enter key gnome-shell immediately freezes. The lock screen is still displayed, the mouse no longer responds, and the keys no longer respond (I can't even get a tty console with CTRL-ALT- Fn key). I have to perform a hard reset at this point because gnome- shell remains frozen even after leaving the PC alone for 15 minutes. I haven't been able to find any crash files or error logs. It seems that this freeze is much more likely to occur if I have changed location between suspending and resuming and am therefore connecting to a different wifi router. Once, however, it happened at home on the same router and I was able to log in via ssh from another machine (so only gnome-shell was frozen, not the kernel). However, I couldn't see any messages or reason that gnome-shell had crashed, so all I could do was reboot (any hints as to what I should try at this stage are welcome). Bug #1709994 looks similar but in that case a) the user is using Xorg, not Wayland, b) he also gets past the lock screen, and c) gnome-shell eventually restarts. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu5 Uname: Linux 4.14.0-rc8-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Nov 7 08:46:43 2017 DisplayManager: gdm3 InstallationDate: Installed on 2017-08-16 (82 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) 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 insufficient permissions. SourcePackage: gnome-shell UpgradeStatus: Upgraded to artful on 2017-08-17 (81 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1730540/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1741671] Re: nvidia-340 340.102-0ubuntu0.16.04.2: nvidia-340 kernel module failed to build [nv-linux.h:199:2: error: #error "This driver requires the ability to change memory t
I solved the 340.120 issue with kernel 4.13.0-26-generic Ubuntu 16.04.3 LTS Boot with an older kernel, download this patch: https://devtalk.nvidia.com/default/topic/1019362/fully-working-patch- for-nvidia-driver-340-102-compiler-installer-file-and-linux-kernel-4-12/ Rename and copy the patch in /usr/src/nvidia-340-340.102/patches/buildfix_kernel-4.12.patch Modified the dkms.conf by disable patch 4.9 & 4.10 and enable only patch 4.12. Part of the dkms.conf: #PATCH[0]="buildfix_kernel_4.9.patch" #PATCH[1]="buildfix_kernel_4.10.patch" PATCH[0]="buildfix_kernel_4.12.patch" #PATCH_MATCH[0]="^3.[8-9]" Build and Install the kernel module: sudo dkms build -m nvidia-340 -v 340.102 -k 4.13.0-26-generic sudo dkms install -m nvidia-340 -v 340.102 -k 4.13.0-26-generic Reboot -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1741671 Title: nvidia-340 340.102-0ubuntu0.16.04.2: nvidia-340 kernel module failed to build [nv-linux.h:199:2: error: #error "This driver requires the ability to change memory types!"] Status in linux-hwe package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Bug description: not compiling after installation of linux-image-4.13.0-21-generic ProblemType: Package DistroRelease: Ubuntu 16.04 Package: nvidia-340 340.102-0ubuntu0.16.04.2 ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87 Uname: Linux 4.4.0-97-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.102 Mon Jan 16 13:06:29 PST 2017 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.5) .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 DKMSKernelVersion: 4.13.0-21-generic Date: Sat Jan 6 18:36:58 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DuplicateSignature: dkms:nvidia-340:340.102-0ubuntu0.16.04.2:/var/lib/dkms/nvidia-340/340.102/build/nv-linux.h:199:2: error: #error "This driver requires the ability to change memory types!" GraphicsCard: NVIDIA Corporation GT216M [GeForce GT 230M] [10de:0a28] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company GT216M [GeForce GT 230M] [103c:363c] InstallationDate: Installed on 2016-04-26 (619 days ago) InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1) MachineType: Hewlett-Packard HP Pavilion dv7 Notebook PC PackageVersion: 340.102-0ubuntu0.16.04.2 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-97-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.24 SourcePackage: nvidia-graphics-drivers-340 Title: nvidia-340 340.102-0ubuntu0.16.04.2: nvidia-340 kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/05/2010 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.1D dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 363C dmi.board.vendor: Hewlett-Packard dmi.board.version: 32.25 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.1D:bd10/05/2010:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvr039E202413102:rvnHewlett-Packard:rn363C:rvr32.25:cvnHewlett-Packard:ct10:cvrN/A: dmi.product.name: HP Pavilion dv7 Notebook PC dmi.product.version: 039E202413102 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.2 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A 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: Sat Jan 6 18:17:29 2018 xserver.configfile: default xserver.errors: open /dev/fb0: No such fi
[Desktop-packages] [Bug 1743211] [NEW] ubuntu crashed on VM started
Public bug reported: ubuntu crashed on VM (virtualbox) started ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13 Uname: Linux 4.13.0-26-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.gpus..03.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:03:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 384.111 Tue Dec 19 23:51:45 PST 2017 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.5) .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: Sun Jan 14 14:01:04 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.10.0-42-generic, x86_64: installed bbswitch, 0.8, 4.13.0-26-generic, x86_64: installed nvidia-384, 384.111, 4.10.0-42-generic, x86_64: installed nvidia-384, 384.111, 4.13.0-26-generic, x86_64: installed virtualbox, 5.0.40, 4.13.0-26-generic, x86_64: installed GraphicsCard: Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Skylake Integrated Graphics [17aa:3824] Subsystem: Lenovo Device [17aa:3824] InstallationDate: Installed on 2017-11-12 (63 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: LENOVO 80SM ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-26-generic root=UUID=fd53ae53-c812-4c0c-8109-89e7c0c7310d ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/03/2016 dmi.bios.vendor: LENOVO dmi.bios.version: 0XCN37WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Toronto 5A2 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 310-15ISK dmi.modalias: dmi:bvnLENOVO:bvr0XCN37WW:bd10/03/2016:svnLENOVO:pn80SM:pvrLenovoideapad310-15ISK:rvnLENOVO:rnToronto5A2:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad310-15ISK: dmi.product.family: IDEAPAD dmi.product.name: 80SM dmi.product.version: Lenovo ideapad 310-15ISK dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Sun Jan 14 13:47:58 2018 xserver.configfile: /etc/X11/xorg.conf xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.3-1ubuntu1~16.04.4 ** 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/1743211 Title: ubuntu crashed on VM started Status in xorg package in Ubuntu: New Bug description: ubuntu crashed on VM (virtualbox) started ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13 Uname: Linux 4.13.0-26-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.gpus..03.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:03:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 384.111 Tue Dec 19 23:51:45 PST 2017 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.5) .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: Sun Jan 14 14:01:04 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.10.0-42-generic, x86_64: installed bbswitch, 0.8, 4
[Desktop-packages] [Bug 1743207] 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/1743207 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: the context is merge when i tried to install itunes 12 using playlinux. it won't t wowrk to install. so idecided tto install first wwine bbeside of playlinux then i thought to use playlinux to finish itunes 12 installation. ProblemType: Package DistroRelease: Ubuntu 17.10 Package: libsane1 1.0.27-1~experimental2ubuntu2.1 ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 Uname: Linux 4.13.0-25-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 Date: Sun Jan 14 12:28:50 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-fCxkux/114-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-09 (35 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) 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: Upgraded to artful on 2018-01-07 (6 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1743207/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1743207] [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: the context is merge when i tried to install itunes 12 using playlinux. it won't t wowrk to install. so idecided tto install first wwine bbeside of playlinux then i thought to use playlinux to finish itunes 12 installation. ProblemType: Package DistroRelease: Ubuntu 17.10 Package: libsane1 1.0.27-1~experimental2ubuntu2.1 ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 Uname: Linux 4.13.0-25-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 Date: Sun Jan 14 12:28:50 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-fCxkux/114-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-09 (35 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) 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: Upgraded to artful on 2018-01-07 (6 days ago) ** 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/1743207 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: the context is merge when i tried to install itunes 12 using playlinux. it won't t wowrk to install. so idecided tto install first wwine bbeside of playlinux then i thought to use playlinux to finish itunes 12 installation. ProblemType: Package DistroRelease: Ubuntu 17.10 Package: libsane1 1.0.27-1~experimental2ubuntu2.1 ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 Uname: Linux 4.13.0-25-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 Date: Sun Jan 14 12:28:50 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-fCxkux/114-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-09 (35 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) 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: Upgraded to artful on 2018-01-07 (6 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1743207/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1743154] Re: sane-dll (5) man page missing
** Changed in: sane-backends (Debian) Status: Unknown => Fix Released -- 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/1743154 Title: sane-dll (5) man page missing Status in sane-backends package in Ubuntu: Confirmed Status in sane-backends package in Debian: Fix Released Bug description: In Ubuntu 17.10, with packages "sane" and "libsane1" installed, man sane-dll man 5 sane-dll say "No manual entry for sane-dll". This man page is the SEE ALSO list in the sane(7) man page and mentioned on the Internet. Note: When trying to install libsane, apt-get substitutes "libsane1" for some reason: # apt-get install libsane Note, selecting 'libsane1' instead of 'libsane' libsane1 is already the newest version (1.0.27-1~experimental2ubuntu2.1). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: sane 1.0.14-12build1 ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 Uname: Linux 4.13.0-25-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Jan 13 12:35:48 2018 InstallationDate: Installed on 2017-12-13 (31 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: sane-frontends 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/1743154/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1735594] Re: [regression] compiz crashes after Mesa upgrade
Proposed fix fixed it for me (Lenovo 3000 N200). Many thanks. Original error was: compiz[1519]: segfault at 0 ip 7f54d91a2986 sp 7ffd58273a20 error 4 in i965_dri.so[7f54d8bca000+82d000] Machine details: $ sudo lshws description: Notebook product: 0769EUG (Lenovo) vendor: LENOVO version: 3000 N200 width: 64 bits capabilities: smbios-2.4 dmi-2.4 vsyscall32 configuration: boot=oem-specific chassis=notebook family=Lenovo sku=Lenovo *-cpu description: CPU product: Intel(R) Core(TM)2 Duo CPU T5750 @ 2.00GHz vendor: Intel Corp. physical id: 4 bus info: cpu@0 version: CPU Version slot: U2E1 size: 1634MHz capacity: 4096MHz width: 64 bits capabilities: fpu fpu_exception wp vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx x86-64 constant_tsc arch_perfmon pebs bts rep_good nopl cpuid aperfmperf pni dtes64 monitor ds_cpl est tm2 ssse3 cx16 xtpr pdcm lahf_lm pti dtherm cpufreq *-pci description: Host bridge product: Mobile PM965/GM965/GL960 Memory Controller Hub vendor: Intel Corporation physical id: 100 bus info: pci@:00:00.0 version: 0c width: 32 bits clock: 33MHz *-display:0 description: VGA compatible controller product: Mobile GM965/GL960 Integrated Graphics Controller (primary) vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 version: 0c width: 64 bits clock: 33MHz capabilities: msi pm vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 resources: irq:16 memory:fc00-fc0f memory:d000-dfff ioport:1800(size=8) memory:c-d $ apt policy install libgl1-mesa-dri libgl1-mesa-dri: Installed: 17.2.4-0ubuntu1~16.04.4 Candidate: 17.2.4-0ubuntu1~16.04.4 Version table: *** 17.2.4-0ubuntu1~16.04.4 400 400 http://gb.archive.ubuntu.com/ubuntu xenial-proposed/main amd64 Packages 100 /var/lib/dpkg/status 17.2.4-0ubuntu1~16.04.2 500 500 http://gb.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 11.2.0-1ubuntu2 500 500 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64 Packages -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1735594 Title: [regression] compiz crashes after Mesa upgrade Status in mesa package in Ubuntu: Fix Committed Status in mesa source package in Xenial: Fix Committed Status in mesa source package in Artful: Fix Committed Bug description: [Impact] When I use the Unity session I automatically get logged out under these conditions: When I hover with my mouse over any icon of the sidebar. When I press the alt key. When I press the super key. running dmesg after this unwanted logout happens I get following information: compiz[10616]: segfault at 0 ip 7fbca309feeb sp 7fff5f59a4d0 error 4 in i965_dri.so[7fbca2af6000+7e4000] This is caused by a mesa upgrade, which added a patch for bug #1727401. The crasher is reproduced on: - gen4 / gen5 Intel - if using modesetting X driver, like when xserver-xorg-video-intel is not installed, or the HWE stack is installed (xserver-xorg-core-hwe-16.04 defaults to modesetting) [Test case] Log in to Unity, open the dash or try to log out etc. Compiz shouldn't crash. [Regression potential] The backported patches need to be tested, here for regressions and on 1727401 that they fix the original bug (again). Best to test on a wide array of Intel HW: gen4 (965GM/GM45/G45) gen5 (Ironlake) gen6 (Sandy Bridge) gen7 (Bay Trail, Ivy Bridge, Haswell) gen8 (Braswell, Broadwell) gen9 (Apollo Lake, Skylake, Gemini Lake, Kaby Lake, Coffee Lake) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1735594/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1743154] Re: sane-dll (5) man page missing
Thanks for taking your time to report this issue and help making Ubuntu better. I found a corresponding bug report in Debian, so I have attached a bug watch. Looks like this might be fixed in the upcoming 18.04, but I haven't verified this yet. ** Package changed: sane-frontends (Ubuntu) => sane-backends (Ubuntu) ** Bug watch added: Debian Bug tracker #872366 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872366 ** Also affects: sane-backends (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872366 Importance: Unknown Status: Unknown ** Changed in: sane-backends (Ubuntu) Status: New => Confirmed ** Tags added: manpage -- 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/1743154 Title: sane-dll (5) man page missing Status in sane-backends package in Ubuntu: Confirmed Status in sane-backends package in Debian: Unknown Bug description: In Ubuntu 17.10, with packages "sane" and "libsane1" installed, man sane-dll man 5 sane-dll say "No manual entry for sane-dll". This man page is the SEE ALSO list in the sane(7) man page and mentioned on the Internet. Note: When trying to install libsane, apt-get substitutes "libsane1" for some reason: # apt-get install libsane Note, selecting 'libsane1' instead of 'libsane' libsane1 is already the newest version (1.0.27-1~experimental2ubuntu2.1). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: sane 1.0.14-12build1 ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 Uname: Linux 4.13.0-25-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Jan 13 12:35:48 2018 InstallationDate: Installed on 2017-12-13 (31 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: sane-frontends 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/1743154/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1743185] Re: package gnome-menus 3.13.3-11ubuntu1 failed to install/upgrade: 트리거가 반복하고 있으므로 지웁니다
Message is: *** dpkg: cycle found while processing triggers: chain of packages whose triggers are or may be responsible: gnome-menus -> gconf2 *** Be sure to have nothing else but Bionic into /etc/apt/sources.list; then update Be sure to purge old things, using 'deborphan' & 'bleachbit' (as root, but select carefully options) ** Changed in: gnome-menus (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-menus in Ubuntu. https://bugs.launchpad.net/bugs/1743185 Title: package gnome-menus 3.13.3-11ubuntu1 failed to install/upgrade: 트리거가 반복하고 있으므로 지웁니다 Status in gnome-menus package in Ubuntu: Incomplete Bug description: occurred while apt upgrade with proposed update checked. $ lsb_release -rd Description: Ubuntu Bionic Beaver (development branch) Release: 18.04 ProblemType: Package DistroRelease: Ubuntu 18.04 Package: gnome-menus 3.13.3-11ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 Uname: Linux 4.13.0-25-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 Date: Sun Jan 14 14:44:30 2018 Dependencies: ErrorMessage: 트리거가 반복하고 있으므로 지웁니다 InstallationDate: Installed on 2018-01-13 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180112) Python3Details: /usr/bin/python3.6, Python 3.6.4, python3-minimal, 3.6.4-1 PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4 RelatedPackageVersions: dpkg 1.19.0.4ubuntu1 apt 1.6~alpha6 SourcePackage: gnome-menus Title: package gnome-menus 3.13.3-11ubuntu1 failed to install/upgrade: 트리거가 반복하고 있으므로 지웁니다 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-menus/+bug/1743185/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1735594] Re: [regression] compiz crashes after Mesa upgrade
The proposed fix works on my machine. Thanks. Ubuntu 16.04; Processor: Intel® Core™ i5 CPU M 540 @ 2.53GHz × 4; Graphics: Intel® Ironlake Mobile description: Laptop product: Latitude E4310 vendor: Dell Inc. version: 0001 serial: G4N8XN1 width: 64 bits capabilities: smbios-2.6 dmi-2.6 vsyscall32 configuration: boot=normal chassis=laptop uuid=44454C4C-3400-104E-8038-C7C04F584E31 *-core description: Motherboard product: 012JJ4 vendor: Dell Inc. physical id: 0 version: A01 *-firmware description: BIOS vendor: Dell Inc. physical id: 0 version: A15 date: 05/12/2017 size: 64KiB capacity: 960KiB *-display description: VGA compatible controller product: Core Processor Integrated Graphics Controller vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 version: 02 width: 64 bits clock: 33MHz capabilities: msi pm vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1735594 Title: [regression] compiz crashes after Mesa upgrade Status in mesa package in Ubuntu: Fix Committed Status in mesa source package in Xenial: Fix Committed Status in mesa source package in Artful: Fix Committed Bug description: [Impact] When I use the Unity session I automatically get logged out under these conditions: When I hover with my mouse over any icon of the sidebar. When I press the alt key. When I press the super key. running dmesg after this unwanted logout happens I get following information: compiz[10616]: segfault at 0 ip 7fbca309feeb sp 7fff5f59a4d0 error 4 in i965_dri.so[7fbca2af6000+7e4000] This is caused by a mesa upgrade, which added a patch for bug #1727401. The crasher is reproduced on: - gen4 / gen5 Intel - if using modesetting X driver, like when xserver-xorg-video-intel is not installed, or the HWE stack is installed (xserver-xorg-core-hwe-16.04 defaults to modesetting) [Test case] Log in to Unity, open the dash or try to log out etc. Compiz shouldn't crash. [Regression potential] The backported patches need to be tested, here for regressions and on 1727401 that they fix the original bug (again). Best to test on a wide array of Intel HW: gen4 (965GM/GM45/G45) gen5 (Ironlake) gen6 (Sandy Bridge) gen7 (Bay Trail, Ivy Bridge, Haswell) gen8 (Braswell, Broadwell) gen9 (Apollo Lake, Skylake, Gemini Lake, Kaby Lake, Coffee Lake) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1735594/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1743154] [NEW] sane-dll (5) man page missing
You have been subscribed to a public bug: In Ubuntu 17.10, with packages "sane" and "libsane1" installed, man sane-dll man 5 sane-dll say "No manual entry for sane-dll". This man page is the SEE ALSO list in the sane(7) man page and mentioned on the Internet. Note: When trying to install libsane, apt-get substitutes "libsane1" for some reason: # apt-get install libsane Note, selecting 'libsane1' instead of 'libsane' libsane1 is already the newest version (1.0.27-1~experimental2ubuntu2.1). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: sane 1.0.14-12build1 ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 Uname: Linux 4.13.0-25-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Jan 13 12:35:48 2018 InstallationDate: Installed on 2017-12-13 (31 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: sane-frontends UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: sane-backends (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful -- sane-dll (5) man page missing https://bugs.launchpad.net/bugs/1743154 You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends 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 1743018] Re: Unable to install mesa-opencl-icd because of unmet dependencies on Xenial
** Tags added: unmetdeps -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1743018 Title: Unable to install mesa-opencl-icd because of unmet dependencies on Xenial Status in mesa package in Ubuntu: Invalid Status in mesa source package in Xenial: Fix Committed Bug description: Steps to reproduce: 1. Install Ubuntu 16.04 LTS 2. Try to install `mesa-opencl-icd` with $ sudo apt-get install mesa-opencl-icd [sudo] password for user: Reading package lists... Done Building dependency tree Reading state information... Done Expected results: * mesa-opencl-icd is installed successfully Actual results: * got errors as follow Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: mesa-opencl-icd : Depends: libclc-r600 (>= 0.2.0+git20170330-3) but it is not going to be installed Depends: libclc-amdgcn (>= 0.2.0+git20170330-3) but it is not going to be installed E: Unable to correct problems, you have held broken packages. Note: inspired by this AskUbuntu question - https://askubuntu.com/q/995274/66509 . ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: mesa-opencl-icd (not installed) 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 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,mousepoll,move,gnomecompat,wall,regex,place,resize,snap,session,imgpng,vpswitch,grid,unitymtgrabhandles,animation,expo,workarounds,ezoom,staticswitcher,fade,scale,unityshell] CompositorRunning: None CurrentDesktop: MATE Date: Fri Jan 12 21:22:22 2018 DistUpgraded: 2017-04-16 02:19:02,541 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 3rd Gen Core processor Graphics Controller [1043:2135] InstallationDate: Installed on 2014-02-07 (1434 days ago) InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release amd64 (20140204) MachineType: ASUSTeK COMPUTER INC. UX32A ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-109-generic root=UUID=1e3c78e2-1a6e-4afe-8249-40fe7fa81a86 ro quiet splash vt.handoff=7 SourcePackage: mesa UpgradeStatus: Upgraded to xenial on 2017-04-15 (271 days ago) dmi.bios.date: 02/12/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX32A.216 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX32A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX32A.216:bd02/12/2014:svnASUSTeKCOMPUTERINC.:pnUX32A:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32A:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: UX32A dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER 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.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Fri Jan 12 20:32:41 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.7 xserver.video_driver: intel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1743018/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1718839] Re: nvidia-340 340.104-0ubuntu1: nvidia-340 kernel module failed to build (error: initialization from incompatible pointer type [-Werror=incompatible-pointer-types] .f
To Pedro: Yes, downgrading to nvidia drivers 304.137 does work. However, I have some other issues (tearing in videos) with drivers 304.137. The alternative is to keep nvidia drivers 340, and to downgrade the kernel to 4.4.0-109: nvidia drivers 340 work fine with kernel 4.4.0-109. And kernel 4.4.0-109 has patches for Spectre and Meltdown flaws. This worked for me. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1718839 Title: nvidia-340 340.104-0ubuntu1: nvidia-340 kernel module failed to build (error: initialization from incompatible pointer type [-Werror =incompatible-pointer-types] .fault = _fault,) Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Bug description: After installing new drivers when I restart, it shows crash report. ProblemType: Package DistroRelease: Ubuntu 17.10 Package: nvidia-340 340.104-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1 Uname: Linux 4.13.0-11-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 DKMSKernelVersion: 4.13.0-11-generic Date: Thu Sep 21 15:08:42 2017 DuplicateSignature: dkms:nvidia-340:340.104-0ubuntu1:/var/lib/dkms/nvidia-340/340.104/build/uvm/nvidia_uvm_lite.c:857:14: error: initialization from incompatible pointer type [-Werror=incompatible-pointer-types] InstallationDate: Installed on 2017-04-03 (171 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) PackageVersion: 340.104-0ubuntu1 Python3Details: /usr/bin/python3.6, Python 3.6.3rc1, python3-minimal, 3.6.2-1ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-1 RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5~rc4 SourcePackage: nvidia-graphics-drivers-340 Title: nvidia-340 340.104-0ubuntu1: nvidia-340 kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1718839/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp