[Desktop-packages] [Bug 1751410] Re: xorg issue
[Expired for xorg (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1751410 Title: xorg issue Status in xorg package in Ubuntu: Expired Bug description: Firefox or Chrome will crash very often. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Fri Feb 23 22:35:25 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Richland [Radeon HD 8470D] [1002:9996] (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Richland [Radeon HD 8470D] [1458:d000] InstallationDate: Installed on 2016-10-29 (482 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-116-generic.efi.signed root=/dev/mapper/hostname--vg-root ro SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/24/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: F2A88X-D3HP dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x 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.:bvrF2:bd12/24/2015:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A88X-D3HP:rvrx.x: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. version.compiz: compiz N/A 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.8-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1 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 Feb 23 22:30:00 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.7 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1751410/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1750832] Re: xorg crash after coming from suspend
[Expired for xorg (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1750832 Title: xorg crash after coming from suspend Status in xorg package in Ubuntu: Expired Bug description: The problem i'm facing is, whenever my system revives back from suspended state, xorg crashes and i have restart all the applications that were running in the previous xorg session. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 Uname: Linux 4.15.3-041503-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset 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 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.6) .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: None CurrentDesktop: GNOME Date: Wed Feb 21 19:42:44 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:15e0] Subsystem: ASUSTeK Computer Inc. Device [1043:15e0] InstallationDate: Installed on 2017-08-15 (189 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: ASUSTeK COMPUTER INC. GL553VD ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.3-041503-generic root=UUID=ae3afa91-6139-4a8a-a15b-39b661535c3a ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/06/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GL553VD.302 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GL553VD 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.:bvrGL553VD.302:bd03/06/2017:svnASUSTeKCOMPUTERINC.:pnGL553VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL553VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: GL dmi.product.name: GL553VD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.12.3+16.04.20171116-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.8-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1 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: Wed Feb 21 19:23:46 2018 xserver.configfile: /etc/X11/xorg.conf xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.5-0ubuntu2~16.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1750832/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1751120] Re: Xorg freeze when moving a window between external/internal monitors
[Expired for xorg (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1751120 Title: Xorg freeze when moving a window between external/internal monitors Status in xorg package in Ubuntu: Expired Bug description: My mouse cursor would still move, but I couldn't do anything. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu4 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Feb 22 13:44:42 2018 DistUpgraded: 2018-01-23 11:42:22,182 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.6, 4.13.0-32-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GpuHangFrequency: Once a week GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Since a couple weeks or more GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Lenovo ThinkPad T440p [17aa:220e] InstallationDate: Installed on 2017-10-23 (121 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: LENOVO 20ANCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to bionic on 2018-01-23 (30 days ago) dmi.bios.date: 05/21/2014 dmi.bios.vendor: LENOVO dmi.bios.version: GLET70WW (2.24 ) dmi.board.asset.tag: Not Available dmi.board.name: 20ANCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0E50512 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGLET70WW(2.24):bd05/21/2014:svnLENOVO:pn20ANCTO1WW:pvrThinkPadT440p:rvnLENOVO:rn20ANCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T440p dmi.product.name: 20ANCTO1WW dmi.product.version: ThinkPad T440p dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.90-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.3.3-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.3.3-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1751120/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1756906] Re: package libreoffice-calc 1:4.4.6~rc3-0ubuntu1 failed to install/upgrade: el subproceso script pre-installation nuevo devolvió el código de salida de error 1
[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/1756906 Title: package libreoffice-calc 1:4.4.6~rc3-0ubuntu1 failed to install/upgrade: el subproceso script pre-installation nuevo devolvió el código de salida de error 1 Status in libreoffice package in Ubuntu: Expired Bug description: actualizar a version 16 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libreoffice-calc 1:4.4.6~rc3-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-84.92-generic 3.19.8-ckt22 Uname: Linux 3.19.0-84-generic i686 NonfreeKernelModules: wl ApportVersion: 2.17.2-0ubuntu1.8 Architecture: i386 Date: Mon Mar 19 11:38:50 2018 DuplicateSignature: package:libreoffice-calc:1:4.4.6~rc3-0ubuntu1:el subproceso script pre-installation nuevo devolvió el código de salida de error 1 ErrorMessage: el subproceso script pre-installation nuevo devolvió el código de salida de error 1 InstallationDate: Installed on 2017-11-07 (131 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422) RelatedPackageVersions: dpkg 1.17.25ubuntu1.1 apt 1.0.9.7ubuntu4.2 SourcePackage: libreoffice Title: package libreoffice-calc 1:4.4.6~rc3-0ubuntu1 failed to install/upgrade: el subproceso script pre-installation nuevo devolvió el código de salida de error 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1756906/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1770720] Re: network-manager-openvpn is not working on ubuntu 18.04
I think that I've got the same problem, with a little more information at https://bugs.launchpad.net/ubuntu/+source/network-manager- openvpn/+bug/1772066 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-openvpn in Ubuntu. https://bugs.launchpad.net/bugs/1770720 Title: network-manager-openvpn is not working on ubuntu 18.04 Status in network-manager-openvpn package in Ubuntu: New Bug description: I'm using Ubuntu 18.04. I installed network-manager-openvpn and as a dependency openvpn and network-manager-openvpn-gnome. I restarted NetworkManager with systemctl restart NetworkManager I'm able to add new openvpn connexion trough .ovpn files but when I click to ON to my openvpn server network-manager is doing nothing, its not trying to connect to the openvpn server. I think there is a bug there. I'm open to any further questions or informations devs will need Regards To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1770720/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1771650] Re: openvpn startup script isn't working in ubuntu 18.04
I have a problem that may be related, but I haven't been able to get OpenVPN working. https://bugs.launchpad.net/ubuntu/+source/network- manager-openvpn/+bug/1772066 How do you start OpenVPN manually? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-openvpn in Ubuntu. https://bugs.launchpad.net/bugs/1771650 Title: openvpn startup script isn't working in ubuntu 18.04 Status in network-manager-openvpn package in Ubuntu: New Bug description: Its very simple. 1- Install ubuntu 18.04. 2- Install Openvpn using apt. 3- Put your configuration at path /etc/openvpn, for example : /etc/openvpn/myconfig.conf. 4- start openvpn service! It won't start automatically. Note : my config have a security weakness, but it still valid and works perfect if I start it manually. For example : openvpn /etc/openvpn/myconfig.conf - it works ! Thank you To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1771650/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1763648] Re: [needs-packaging] nvidia-304 (304.137) missing in Ubuntu 18.04
I am getting the same error as Ricardo trying to install from ppa in Ubuntu 18.04 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-304 in Ubuntu. https://bugs.launchpad.net/bugs/1763648 Title: [needs-packaging] nvidia-304 (304.137) missing in Ubuntu 18.04 Status in nvidia-graphics-drivers-304 package in Ubuntu: Confirmed Bug description: nvidia-304 is not available in the Ubuntu 18.04. Newer versions are available but I have an old nVidia 7600 GT, so I need 304.137. I searched online and found that at https://answers.launchpad.net/ubuntu/bionic/amd64/nvidia-304/304.137-0ubuntu2 it has Status: Deleted :( Could you please pack this for the new release of Ubuntu? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1763648/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1724572] Re: vino-server crashed with SIGSEGV in _XSend()
** Changed in: vino Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vino in Ubuntu. https://bugs.launchpad.net/bugs/1724572 Title: vino-server crashed with SIGSEGV in _XSend() Status in vino: Fix Released Status in vino package in Ubuntu: Incomplete Status in vino package in Debian: Confirmed Bug description: Following upgrade from 17.04 (Gnome) to 17.10. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: vino 3.8.1-0ubuntu12 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME Date: Wed Oct 18 12:59:52 2017 ExecutablePath: /usr/lib/vino/vino-server InstallationDate: Installed on 2017-04-17 (183 days ago) InstallationMedia: Ubuntu-GNOME 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. ProcCmdline: /usr/lib/vino/vino-server ProcEnviron: LANG=en_GB.UTF-8 LANGUAGE=en_GB:en PATH=(custom, user) SHELL=/bin/bash XDG_RUNTIME_DIR= SegvAnalysis: Segfault happened at: 0x7f2a587b63ce <_XSend+126>: mov(%rax),%rdx PC (0x7f2a587b63ce) ok source "(%rax)" (0x) not located in a known VMA region (needed readable region)! destination "%rdx" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: vino StacktraceTop: _XSend () from /usr/lib/x86_64-linux-gnu/libX11.so.6 XQueryExtension () from /usr/lib/x86_64-linux-gnu/libX11.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libXtst.so.6 XTestQueryExtension () from /usr/lib/x86_64-linux-gnu/libXtst.so.6 ?? () Title: vino-server crashed with SIGSEGV in _XSend() UpgradeStatus: Upgraded to artful on 2017-10-18 (0 days ago) UserGroups: sudo To manage notifications about this bug go to: https://bugs.launchpad.net/vino/+bug/1724572/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1691675] Re: Gnome Shell desktop zoom judders and performs badly
** Changed in: gnome-shell Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1691675 Title: Gnome Shell desktop zoom judders and performs badly Status in GNOME Shell: Fix Released Status in gnome-shell package in Ubuntu: In Progress Bug description: Gnome Shell desktop zoom judders and performs badly ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.24.2-0ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 ApportVersion: 2.20.5-0ubuntu3 Architecture: amd64 Date: Thu May 18 15:22:50 2017 DisplayManager: lightdm GsettingsChanges: b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 'org.gnome.Terminal.desktop', 'rhythmbox.desktop', 'org.gnome.Nautilus.desktop', 'org.gnome.Software.desktop', 'yelp.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'scaling-factor' b'uint32 1' InstallationDate: Installed on 2017-05-03 (15 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/gnome-shell/+bug/1691675/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1772130] [NEW] [OMEN by HP Laptop, Realtek ALC295, Speaker, Internal] No sound at all
Public bug reported: Headphones worked for a while. After restart no sound at all ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-41.46~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-41-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jmachuca 7895 F pulseaudio CurrentDesktop: Unity Date: Fri May 18 21:20:36 2018 InstallationDate: Installed on 2018-03-22 (57 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) 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: jmachuca 7895 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [OMEN by HP Laptop, Realtek ALC295, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/13/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.44 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8259 dmi.board.vendor: HP dmi.board.version: 83.71 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.44:bd12/13/2017:svnHP:pnOMENbyHPLaptop:pvrType1ProductConfigId:rvnHP:rn8259:rvr83.71:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Omen dmi.product.name: OMEN by HP Laptop dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP ** Affects: alsa-driver (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 alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1772130 Title: [OMEN by HP Laptop, Realtek ALC295, Speaker, Internal] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: Headphones worked for a while. After restart no sound at all ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-41.46~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-41-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jmachuca 7895 F pulseaudio CurrentDesktop: Unity Date: Fri May 18 21:20:36 2018 InstallationDate: Installed on 2018-03-22 (57 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) 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: jmachuca 7895 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [OMEN by HP Laptop, Realtek ALC295, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/13/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.44 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8259 dmi.board.vendor: HP dmi.board.version: 83.71 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.44:bd12/13/2017:svnHP:pnOMENbyHPLaptop:pvrType1ProductConfigId:rvnHP:rn8259:rvr83.71:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Omen dmi.product.name: OMEN by HP Laptop dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1772130/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1509776] Re: xubuntu 15.10 synaptics ps2 touchpad mouse cursor jumps
For me, the problem is fixed when applying the patches in http://xps13-9333.appspot.com/#touchpad or https://askubuntu.com/questions/462135/touchpad-issue-jumping-cursor- while-typing-ubuntu-14-04-syndaemon-dont-help -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/1509776 Title: xubuntu 15.10 synaptics ps2 touchpad mouse cursor jumps Status in xserver-xorg-input-synaptics package in Ubuntu: Triaged Bug description: running live xubuntu 15.10 from usb stick. Synaptics ps2 touchpad configured to act as simple mouse. Mouse cursor suddenly and frequently jumps to screen edge with no reason. Problem not present in 15.04 with same touchpad configuration but has occurred in some earlier versions. Not prepared to upgrade as touchpad practically unusable. --- ApportVersion: 2.19.1-0ubuntu3 Architecture: amd64 CasperVersion: 1.365 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE DistUpgraded: Fresh install DistroCodename: wily DistroRelease: Ubuntu 15.10 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Pegatron Device [1b0a:2109] Subsystem: Pegatron Device [1b0a:2109] LiveMediaBuild: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: Novatech Ltd. Novatech 15.6 NSPIRE Laptop Package: xorg 1:7.7+7ubuntu4 PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi initrd=/casper/initrd.lz file=/cdrom/preseed/username.seed boot=casper quiet splash --- persistent ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Tags: wily ubuntu UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 4.2.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/05/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: C15B.610 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: C15B dmi.board.vendor: Novatech Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Novatech Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrC15B.610:bd12/05/2013:svnNovatechLtd.:pnNovatech15.6NSPIRELaptop:pvr1.0:rvnNovatechLtd.:rnC15B:rvr1.0:cvnNovatechLtd.:ct10:cvr1.0: dmi.product.name: Novatech 15.6 NSPIRE Laptop dmi.product.version: 1.0 dmi.sys.vendor: Novatech Ltd. version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4 version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0+git20150819-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3 xserver.bootTime: Mon Nov 2 10:44:16 2015 xserver.configfile: default xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) NOUVEAU(G0): Failed to initialise context object: 2D_NVC0 (0) NOUVEAU(G0): Error initialising acceleration. Falling back to NoAccel xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 18412 vendor AUO xserver.version: 2:1.17.2-1ubuntu9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1509776/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1772104] Re: clock-timezone help should note that Automatic Time Zone requires Location Services
Thanks for your report! I filed this merge request for upstream GNOME Help: https://gitlab.gnome.org/GNOME/gnome-user- docs/merge_requests/7/diffs?commit_id=d81692fb ** Package changed: ubuntu-docs (Ubuntu) => gnome-user-docs (Ubuntu) ** Changed in: gnome-user-docs (Ubuntu) Importance: Undecided => Medium ** Changed in: gnome-user-docs (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-user-docs in Ubuntu. https://bugs.launchpad.net/bugs/1772104 Title: clock-timezone help should note that Automatic Time Zone requires Location Services Status in gnome-user-docs package in Ubuntu: In Progress Bug description: The Automatic time zone feature doesn't work when Location Services is disabled in the Privacy settings of Gnome. See bug reports at https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1741928 and https://bugzilla.gnome.org/show_bug.cgi?id=788714 This should be noted in the help documentation at https://help.ubuntu.com/stable/ubuntu-help/clock-timezone.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-user-docs/+bug/1772104/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1772104] [NEW] clock-timezone help should note that Automatic Time Zone requires Location Services
You have been subscribed to a public bug: The Automatic time zone feature doesn't work when Location Services is disabled in the Privacy settings of Gnome. See bug reports at https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1741928 and https://bugzilla.gnome.org/show_bug.cgi?id=788714 This should be noted in the help documentation at https://help.ubuntu.com/stable/ubuntu-help/clock-timezone.html ** Affects: gnome-user-docs (Ubuntu) Importance: Medium Status: In Progress -- clock-timezone help should note that Automatic Time Zone requires Location Services https://bugs.launchpad.net/bugs/1772104 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-user-docs 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 1752053] Re: nvidia-390 fails to boot graphical display
So, if this bug is marked as "fixed released" and 500 comments further it's clear it doesn't fix anything, should we open a new bug report? -- 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/1752053 Title: nvidia-390 fails to boot graphical display Status in mesa package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in xserver-xorg-video-nouveau package in Ubuntu: Invalid Bug description: I'm using Bionic with the new 4.15 kernel. I've been using the nvidia-384 driver with no problem for a while. Today I issued "sudo apt-get upgrade" and I was prompted to upgrade the nvidia driver to the nvidia-390. After installing the driver and rebooting, I was only able to boot in to the tty terminal. The graphical display failed to boot. I have had similar problems with nvidia driver version 390 with Arch Linux and with Open Suse Tumbleweed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1725121] Re: package desktop-file-utils 0.23-1ubuntu3 failed to install/upgrade: dependency problems - leaving triggers unprocessed
** Tags added: triggers-unprocessed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to desktop-file-utils in Ubuntu. https://bugs.launchpad.net/bugs/1725121 Title: package desktop-file-utils 0.23-1ubuntu3 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in desktop-file-utils package in Ubuntu: Confirmed Bug description: Hello! During update from 17.04 to 17.10 I got error in subject Thank you! ProblemType: Package DistroRelease: Ubuntu 17.10 Package: desktop-file-utils 0.23-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: Fri Oct 20 08:58:43 2017 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2010-03-23 (2767 days ago) InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100317.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 SourcePackage: desktop-file-utils Title: package desktop-file-utils 0.23-1ubuntu3 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to artful on 2017-10-20 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/desktop-file-utils/+bug/1725121/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1772117] [NEW] xorg server
Public bug reported: x11 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-124.148-generic 4.4.117 Uname: Linux 4.4.0-124-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.17 Architecture: i386 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Fri May 18 22:55:35 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu 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 2016-10-19 (576 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1) MachineType: LENOVO 6475AG9 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: LANGUAGE=fr_FR PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-124-generic root=UUID=f2c844dc-cf64-4e07-87c5-50617f11c61e ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/24/2008 dmi.bios.vendor: LENOVO dmi.bios.version: 7UET46WW (1.16 ) dmi.board.name: 6475AG9 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: L002843 dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr7UET46WW(1.16):bd09/24/2008:svnLENOVO:pn6475AG9:pvrThinkPadT400:rvnLENOVO:rn6475AG9:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 6475AG9 dmi.product.version: ThinkPad T400 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1 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 May 18 22:36:56 2018 xserver.configfile: default xserver.devices: 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: apport-bug compiz-0.9 i386 third-party-packages ubuntu xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1772117 Title: xorg server Status in xorg package in Ubuntu: New Bug description: x11 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-124.148-generic 4.4.117 Uname: Linux 4.4.0-124-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.17 Architecture: i386 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Fri May 18 22:55:35 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu 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 2016-10-19 (576 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1) MachineType: LENOVO 6475AG9 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: LANGUAGE=fr_FR PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-124-generic root=UUID=f2c844dc-cf64-4e07-87c5-50617f11c61e ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/24/2008 dmi.bios.vendor: LENOVO dmi.bios.version: 7UET46WW (1.16 ) dmi.board.name:
[Desktop-packages] [Bug 1772115] [NEW] Update to 60.0.1
Public bug reported: See https://www.mozilla.org/en-US/firefox/60.0.1/releasenotes/ ** Affects: firefox (Ubuntu) Importance: Undecided Status: Fix Released ** Changed in: firefox (Ubuntu) Status: New => Fix Released -- 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/1772115 Title: Update to 60.0.1 Status in firefox package in Ubuntu: Fix Released Bug description: See https://www.mozilla.org/en-US/firefox/60.0.1/releasenotes/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1772115/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1532508] Re: Screen contents revealed briefly on resume, before even unlocking
Still experiencing this bug in Ubuntu Budgie 18.04. Shows the last (pre- hibernate) screen for a brief instant on wake, before displaying the login screen. -- 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/1532508 Title: Screen contents revealed briefly on resume, before even unlocking Status in GNOME Shell: In Progress Status in Ubuntu GNOME: Confirmed Status in gdm3 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in unity package in Ubuntu: Fix Released Status in unity source package in Xenial: Fix Released Status in gnome-shell package in Debian: Confirmed Status in gnome-shell package in Fedora: In Progress Bug description: [Impact] When lock is enabled, the screen doesn't get blank/covered by lockscreen before suspending, thus on early resume the content might be shown. Video showing the bug: https://youtu.be/dDOgtK1MldI Reproduced on Ubuntu 2015.10, Ubuntu 2014.04 [Test case] 1. Work on highly secret files 2. Close the lid of your laptop and go have a break 3. Anyone who opens the lid of the laptop can see the secret files for a half second before the lock screen appears [Possible Regression] Content on screen isn't painted anymore and screen stays black. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1532508/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1772109] Re: Xorg consuming 50% CPU for no good reason, at-spi2-registr another 20%, non-stop since boot
Interestingly, killing the "at-spi2-registr" process has made Xorg's CPU consumption go down to normal. -- 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/1772109 Title: Xorg consuming 50% CPU for no good reason, at-spi2-registr another 20%, non-stop since boot Status in xorg package in Ubuntu: New Bug description: I have booted the computer about half an hour ago. Since the very beginning, I noticed the fan spinning at high spin so I launched "top", and noticed that Xorg was consuming about 50% CPU and another process called "at-spi2-registr" is consuming another 20%. Since then, They have continued consuming that amount of CPU constantly, all the time, whether or not I was doing anything. The only applications I opened are a terminal where I'm running top and the browser where I've been browsing Facebook. Before I launched the browser and after I closed it, CPU usage by these processed has never gone below 50% and 20% respectively. This is fucking ridiculous. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-122.146-generic 4.4.117 Uname: Linux 4.4.0-122-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.104 Thu Sep 14 17:13:13 PDT 2017 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.9) .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.16 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 May 18 22:17:40 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] 3rd Gen Core processor Graphics Controller [1025:0647] NVIDIA Corporation GF117M [GeForce 610M/710M/810M/820M / GT 620M/625M/630M/720M] [10de:1140] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] GeForce 710M [1025:0691] InstallationDate: Installed on 2013-10-11 (1680 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Acer Aspire V3-571G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-122-generic.efi.signed root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/15/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.07 dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07: dmi.product.name: Aspire V3-571G dmi.product.version: V2.07 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.12.3+16.04.20180221-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.8-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1 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: Fri May 18 21:44:15 2018 xserver.configfile: /etc/X11/xorg.conf xserver.errors: NVIDIA(0): Failed to initiate mode change. NVIDIA(0): Failed to complete mode change xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1772109/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1772109] [NEW] Xorg consuming 50% CPU for no good reason, at-spi2-registr another 20%, non-stop since boot
Public bug reported: I have booted the computer about half an hour ago. Since the very beginning, I noticed the fan spinning at high spin so I launched "top", and noticed that Xorg was consuming about 50% CPU and another process called "at-spi2-registr" is consuming another 20%. Since then, They have continued consuming that amount of CPU constantly, all the time, whether or not I was doing anything. The only applications I opened are a terminal where I'm running top and the browser where I've been browsing Facebook. Before I launched the browser and after I closed it, CPU usage by these processed has never gone below 50% and 20% respectively. This is fucking ridiculous. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-122.146-generic 4.4.117 Uname: Linux 4.4.0-122-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.104 Thu Sep 14 17:13:13 PDT 2017 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.9) .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.16 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 May 18 22:17:40 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] 3rd Gen Core processor Graphics Controller [1025:0647] NVIDIA Corporation GF117M [GeForce 610M/710M/810M/820M / GT 620M/625M/630M/720M] [10de:1140] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] GeForce 710M [1025:0691] InstallationDate: Installed on 2013-10-11 (1680 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Acer Aspire V3-571G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-122-generic.efi.signed root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/15/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.07 dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07: dmi.product.name: Aspire V3-571G dmi.product.version: V2.07 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.12.3+16.04.20180221-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.8-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1 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: Fri May 18 21:44:15 2018 xserver.configfile: /etc/X11/xorg.conf xserver.errors: NVIDIA(0): Failed to initiate mode change. NVIDIA(0): Failed to complete mode change xserver.logfile: /var/log/Xorg.0.log 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/1772109 Title: Xorg consuming 50% CPU for no good reason, at-spi2-registr another 20%, non-stop since boot Status in xorg package in Ubuntu: New Bug description: I have booted the computer about half an hour ago. Since the very beginning, I noticed the fan spinning at high spin so I launched "top", and noticed that Xorg was consuming about 50% CPU and another process called "at-spi2-registr" is consuming another 20%. Since then, They have continued consuming that amount of CPU constantly, all the time, whether or not I was doing anything. The only applications I opened are a terminal where I'm running
Re: [Desktop-packages] [Bug 549256] Re: [GeForce 7025 / nForce 630a] video flicker on any I/O activity with nouveau; OK with nv driver
Will do - fortunately, I still have that PC. Give me a few days though. Cheers, Michael Am 18.05.2018 um 16:58 schrieb Christopher M. Penalver: > Michael Schmitz, to confirm this is still a problem in Ubuntu, could you > please test http://cdimage.ubuntu.com/daily-live/current/ and advise to > the results? > > ** Project changed: nouveau => xserver-xorg-video-nouveau (Ubuntu) > > ** Changed in: xserver-xorg-video-nouveau (Ubuntu) >Status: New => Incomplete > > ** Changed in: xserver-xorg-video-nouveau (Ubuntu) >Importance: Undecided => Low > > ** Tags removed: needs-apport-collect > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/549256 Title: [GeForce 7025 / nForce 630a] video flicker on any I/O activity with nouveau; OK with nv driver Status in xserver-xorg-video-nouveau package in Ubuntu: Incomplete Bug description: Binary package hint: xserver-xorg-video-nouveau Expectation: Default Xorg driver should work with no video artifacts. Observation: Bad screen flicker with default Xorg driver. Details: I installed the 10.04 beta from CD on Wednesday (incidentially, compliments for the smooth install). Already upon installation, the display did flicker badly whenever the CD was read or even the mouse moved. Flicker did already start at the initial splash screen. The system was fully responsive otherwise. On reboot post-installation, gdm came up OK but with the same flicker problems. The 'Monitors' control panel only offered the 2048x1536 resolution at 80 Hz with no other options. Tried to install and use one of the non- free nvidia drivers, this failed because the nouveau kernel module was loaded always and could not be unloaded (drm loads nouveau before framebuffer console init. as near as I can make out). With nvidia- current unable to load, the X server could not use the 'nvidia' driver. Switching xorg.conf to use the 'nv' driver results in a much better screen display (only occasional flicker) although the driver only supports 2048x1536 at 60 Hz. 1600x1200@85 Hz is useable. Kernel message buffer excerpt: [4.777915] [drm] Initialized drm 1.1.0 20060810 [4.807773] ACPI: PCI Interrupt Link [LMC9] enabled at IRQ 22 [4.807779] nouveau :00:0d.0: PCI INT A -> Link[LMC9] -> GSI 22 (level, low) -> IRQ 22 [4.807783] nouveau :00:0d.0: setting latency timer to 64 [4.809992] [drm] nouveau :00:0d.0: failed to evaluate _DSM: 5 [4.810217] [drm] nouveau :00:0d.0: Detected an NV40 generation card (0x04c000a2) [4.810513] [drm] nouveau :00:0d.0: Attempting to load BIOS image from PROM [4.810519] [drm] nouveau :00:0d.0: ... BIOS signature not found [4.810520] [drm] nouveau :00:0d.0: Attempting to load BIOS image from PRAMIN [4.854556] [drm] nouveau :00:0d.0: ... appears to be valid [4.854559] [drm] nouveau :00:0d.0: BIT BIOS found [4.854561] [drm] nouveau :00:0d.0: Bios version 05.61.32.28 [4.854563] [drm] nouveau :00:0d.0: BIT table 'd' not found [4.854565] [drm] nouveau :00:0d.0: Found Display Configuration Block version 3.0 [4.854568] [drm] nouveau :00:0d.0: DCB connector table: VHER 0x30 5 10 2 [4.854571] [drm] nouveau :00:0d.0: 0: 0x: type 0x00 idx 0 tag 0xff [4.854573] [drm] nouveau :00:0d.0: 1: 0x1131: type 0x31 idx 1 tag 0x07 [4.854575] [drm] nouveau :00:0d.0: 2: 0x0110: type 0x10 idx 1 tag 0xff [4.854577] [drm] nouveau :00:0d.0: 3: 0x0111: type 0x11 idx 1 tag 0xff [4.854579] [drm] nouveau :00:0d.0: 4: 0x0113: type 0x13 idx 1 tag 0xff [4.854581] [drm] nouveau :00:0d.0: Raw DCB entry 0: 01000310 0023 [4.854583] [drm] nouveau :00:0d.0: Raw DCB entry 1: 00110204 942b0003 [4.854588] [drm] nouveau :00:0d.0: Parsing VBIOS init table 0 at offset 0xD9C9 [4.854591] [drm] nouveau :00:0d.0: === misaligned reg 0x0060081D === [4.854648] [drm] nouveau :00:0d.0: === misaligned reg 0x0060081D === [4.854748] [drm] nouveau :00:0d.0: Parsing VBIOS init table 1 at offset 0xDB17 [4.854749] [drm] nouveau :00:0d.0: Parsing VBIOS init table 2 at offset 0xDB18 [4.854799] [drm] nouveau :00:0d.0: Parsing VBIOS init table 3 at offset 0xDC9A [4.854803] [drm] nouveau :00:0d.0: Parsing VBIOS init table 4 at offset 0xDCE3 [4.861274] lp0: using parport0 (interrupt-driven). [4.865006] [TTM] Zone kernel: Available graphics memory: 444292 kiB. [4.865009] [TTM] Zone highmem: Available graphics memory: 448232 kiB. [4.865018] [drm] nouveau :00:0d.0: 128 MiB VRAM [4.865912] [drm] nouveau :00:0d.0: 64 MiB GART (aperture) [4.868624] [drm] nouveau :00:0d.0:
[Desktop-packages] [Bug 1770913] Re: Software rendering is forced after 18.04 upgrade
** Also affects: xorg (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1770913 Title: Software rendering is forced after 18.04 upgrade Status in xorg package in Ubuntu: New Status in xserver-xorg-video-intel package in Ubuntu: New Bug description: After upgrading to Ubuntu 18.04, my desktop uses software rendering, no matter what I do. As far as I know, all necessary packages are installed. Formerly I had oibaf installed, but suspecting that this may cause the problem, I removed it with ppa-purge. It didn't help. First I noticed the problem when I tried to play HD videos. It was fine before the upgrade. My hardware is capable for 3D acceleration, as it worked on 17.10. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xserver-xorg-video-intel 2:2.99.917+git20171229-1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 13 06:13:09 2018 DistUpgraded: 2018-05-12 22:26:52,663 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu 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 2014-06-10 (1432 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: LENOVO 6474B84 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=hu_HU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=/dev/mapper/thinkvg-rootlv ro rootflags=subvol=@ Renderer: Software SourcePackage: xserver-xorg-video-intel UpgradeStatus: Upgraded to bionic on 2018-05-12 (0 days ago) dmi.bios.date: 10/17/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 7UET94WW (3.24 ) dmi.board.name: 6474B84 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr7UET94WW(3.24):bd10/17/2012:svnLENOVO:pn6474B84:pvrThinkPadT400:rvnLENOVO:rn6474B84:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T400 dmi.product.name: 6474B84 dmi.product.version: ThinkPad T400 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Sun May 13 06:01:23 2018 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1770913/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1766137] Re: [regression] Password accepted but login fails (blank purple screen and mouse pointer only)
As requested I have attached the result. Hopefully this posts in the bug list, not sure? Ken On 05/18/2018 10:25 AM, Marco Trevisan (Treviño) wrote: > Looks weird, can you attach the output of >journalctl /usr/bin/gnome-shell > > ? > -- *Ken Wilson* forest ** Attachment added: "journalctl.txt" https://bugs.launchpad.net/bugs/1766137/+attachment/5141399/+files/journalctl.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1766137 Title: [regression] Password accepted but login fails (blank purple screen and mouse pointer only) Status in gdm: Fix Released Status in Release Notes for Ubuntu: Fix Released Status in gdm3 package in Ubuntu: Fix Released Status in gnome-shell package in Ubuntu: Invalid Status in gdm3 source package in Bionic: Fix Committed Status in gnome-shell source package in Bionic: Invalid Bug description: [ Description ] Due to a refcounting bug, a GDBusConnection was getting disposed when it was still required. The symptom of this was that you couldn't log in if you'd got your password wrong. [ Test case ] 1. Boot to GDM 2. Click your username 3. Type the wrong password a couple of times, pressing enter after each time 4. Type the right password If the bug is happening, after 4. the system hangs at a blank screen with the mouse cursor. If you then switch to a VT or otherwise connect to the machine, you can examine the journal and you'll see a G_IS_DBUS_CONNECTION failure. [ Fix ] Marco and I worked upstream on this fix. We found out that there was a problem like this- The GdmClient has a shared GDBusConnection for its operations. The first time someone calls for it, it is created and stored in the object's private structure. Subsequent calls return *a new reference* to this same object. It turned out that the asynchronous method to get the connection was accidentally unreferencing its object before giving it to the caller if it was returning an already-existing connection. For this to work properly, we need to nullify the pointer we stored when the connection goes away, so we know when to make a new one. There were some cases where we didn't add the weak references required to do that. Those are also fixed. [ Regression potential ] Now we share connections more than we did before. We also more carefully track when to clear our object. If we got this wrong, we might end up leaking the connection or dropping it in even more cases. [ Original report ] WORKAROUND: After typing an incorrect password, click Cancel, then click your name, then enter your password again. --- Trying to log into my session (Gnome, Xorg), if I enter the wrong password before entering it correctly, the session doesn't load and I get a purple screen, a mouse cursor, and an invisible but clickable menu in the top right. If I enter it correctly the first time, there is no problem. I've replicated this from a fresh boot, after logging out and after 'sudo service gdm restart' from the Ctrl-Alt-F4 console. This is a fresh install, and didn't occur when I was using a previous install of 18.04 (until Friday). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Apr 22 20:31:13 2018 InstallationDate: Installed on 2018-04-22 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180421.1) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1766137/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1706939] Re: A live session can't be shut down due to "[ *** ] (2 of 2) A start job is running for ... (22s / no limit)"
@Daniel van Vugt (vanvugt) Does pressing Enter causes the system to reboot, after it hangs? Do you see a plymouth purple screen instructing you to remove installation media and hit enter? Do you see a console text message instructing you to "Remove installation media and reboot" (meaning hard-reset)? ** Also affects: casper (Ubuntu) Importance: Undecided Status: New ** No longer affects: systemd (Ubuntu Bionic) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1706939 Title: A live session can't be shut down due to "[ *** ] (2 of 2) A start job is running for ... (22s / no limit)" Status in Release Notes for Ubuntu: Fix Released Status in casper package in Ubuntu: New Status in gdm3 package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Status in casper source package in Bionic: New Status in gdm3 source package in Bionic: Confirmed Bug description: Test case: Boot to live session using current or recent image Attempt to restart, shutdown or even log out. Hangs basically forever with: [ *** ] (2 of 2) A start job is running for Hold until boot process finishes up (21s / no limit) or [ *** ] (2 of 2) A start job is running for Wait for Network to be Configured (21s / no limit) --- ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gdm3 3.24.2-1ubuntu9 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 ApportVersion: 2.20.6-0ubuntu4 Architecture: amd64 CasperVersion: 1.384 CurrentDesktop: GNOME Date: Thu Jul 27 10:15:57 2017 LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170723) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.custom.conf: 2017-07-27T10:13:04.127685 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1706939/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1766137] Re: [regression] Password accepted but login fails (blank purple screen and mouse pointer only)
Following #51 and #56 from Davide (tarski10) I was able to reproduce. **. gdm3/ 3.28.0-0-0ubuntu1.1 if I enter the wrong password once or twice and then I enter the correct password now I can access, but if I enter the wrong password three times I return to the user choice screen and after clicking on my username ** and entering the correct password the screen freezes ** and nothing happens ** -- 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/1766137 Title: [regression] Password accepted but login fails (blank purple screen and mouse pointer only) Status in gdm: Fix Released Status in Release Notes for Ubuntu: Fix Released Status in gdm3 package in Ubuntu: Fix Released Status in gnome-shell package in Ubuntu: Invalid Status in gdm3 source package in Bionic: Fix Committed Status in gnome-shell source package in Bionic: Invalid Bug description: [ Description ] Due to a refcounting bug, a GDBusConnection was getting disposed when it was still required. The symptom of this was that you couldn't log in if you'd got your password wrong. [ Test case ] 1. Boot to GDM 2. Click your username 3. Type the wrong password a couple of times, pressing enter after each time 4. Type the right password If the bug is happening, after 4. the system hangs at a blank screen with the mouse cursor. If you then switch to a VT or otherwise connect to the machine, you can examine the journal and you'll see a G_IS_DBUS_CONNECTION failure. [ Fix ] Marco and I worked upstream on this fix. We found out that there was a problem like this- The GdmClient has a shared GDBusConnection for its operations. The first time someone calls for it, it is created and stored in the object's private structure. Subsequent calls return *a new reference* to this same object. It turned out that the asynchronous method to get the connection was accidentally unreferencing its object before giving it to the caller if it was returning an already-existing connection. For this to work properly, we need to nullify the pointer we stored when the connection goes away, so we know when to make a new one. There were some cases where we didn't add the weak references required to do that. Those are also fixed. [ Regression potential ] Now we share connections more than we did before. We also more carefully track when to clear our object. If we got this wrong, we might end up leaking the connection or dropping it in even more cases. [ Original report ] WORKAROUND: After typing an incorrect password, click Cancel, then click your name, then enter your password again. --- Trying to log into my session (Gnome, Xorg), if I enter the wrong password before entering it correctly, the session doesn't load and I get a purple screen, a mouse cursor, and an invisible but clickable menu in the top right. If I enter it correctly the first time, there is no problem. I've replicated this from a fresh boot, after logging out and after 'sudo service gdm restart' from the Ctrl-Alt-F4 console. This is a fresh install, and didn't occur when I was using a previous install of 18.04 (until Friday). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Apr 22 20:31:13 2018 InstallationDate: Installed on 2018-04-22 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180421.1) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1766137/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1766137] Re: [regression] Password accepted but login fails (blank purple screen and mouse pointer only)
Really sorry about spamming, but I only now figured out how to get output from relevenant time ( I hope) getUniqueBusNameSync@ /usr/share/gnome-shell/extensions/ ubuntu-appindicat...@ubuntu.com/util.js:58:20 traverseBusNames/<@/usr/share/gnome-shell/extensions/ ubuntu-appindicat...@ubuntu.com/util.js:82:34 touko 18 20:53:49 ThinkPad-X301 gnome-shell[1490]: Error looking up permission: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.fre touko 18 20:53:50 ThinkPad-X301 gnome-shell[1490]: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus with touko 18 20:53:53 ThinkPad-X301 gnome-shell[1490]: GNOME Shell started at Fri May 18 2018 20:53:45 GMT+0300 (EEST) touko 18 20:53:55 ThinkPad-X301 gnome-shell[1490]: Some code accessed the property 'getUniqueBusNameSync' on the module 'util'. That property was defin touko 18 20:53:55 ThinkPad-X301 gnome-shell[1490]: [AppIndicatorSupport-DEBUG] Registering StatusNotifierItem :1.70/StatusNotifierItem touko 18 20:53:58 Thin getUniqueBusNameSync@/usr/share/gnome-shell/extensions/ ubuntu-appindicat...@ubuntu.com/util.js:58:20 traverseBusNames/<@/usr/share/gnome-shell/extensions/ ubuntu-appindicat...@ubuntu.com/util.js:82:34 touko 18 20:53:49 ThinkPad-X301 gnome-shell[1490]: Error looking up permission: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.fre touko 18 20:53:50 ThinkPad-X301 gnome-shell[1490]: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus with touko 18 20:53:53 ThinkPad-X301 gnome-shell[1490]: GNOME Shell started at Fri May 18 2018 20:53:45 GMT+0300 (EEST) touko 18 20:53:55 ThinkPad-X301 gnome-shell[1490]: Some code accessed the property 'getUniqueBusNameSync' on the module 'util'. That property was defin touko 18 20:53:55 ThinkPad-X301 gnome-shell[1490]: [AppIndicatorSupport-DEBUG] Registering StatusNotifierItem :1.70/StatusNotifierItem touko 18 20:53:58 ThinkPad-X301 gnome-shell[1490]: Some code accessed the property 'refreshPropertyOnProxy' on the module 'util'. That property was def touko 18 20:54:08 ThinkPad-X301 gnome-shell[1490]: JS WARNING: [resource:///org/gnome/shell/ui/endSessionDialog.js 763]: reference to undefined propert touko 18 20:54:11 ThinkPad-X301 gnome-shell[1490]: gnome-shell: Fatal IO error 0 (Onnistui) on X server :0. -- Reboot -- touko 18 20:55:42 ThinkPad-X301 org.gnome.Shell.desktop[934]: glamor: EGL version 1.4 (DRI2): touko 18 20:55:44 ThinkPad-X301 gnome-shell[934]: JS WARNING: [resource:///org/gnome/shell/ui/main.js 340]: reference to undefined property "MetaStage" touko 18 20:55:44 ThinkPad-X301 gnome-shell[934]: JS WARNING: [resource:///org/gnome/shell/ui/layout.js 220]: reference to undefined property "MetaWind touko 18 20:55:44 ThinkPad-X301 gnome-shell[934]: JS WARNING: [resource:///org/gnome/shell/ui/osdMonitorLabeler.js 59]: reference to undefined property touko 18 20:55:45 ThinkPad-X301 gnome-shell[934]: JS WARNING: [resource:///org/gnome/shell/ui/slider.js 38]: reference to undefined property "CallyActo touko 18 20:55:46 ThinkPad-X301 gnome-shell[934]: Unable to connect to ibus: Yhdistäminen ei onnistunut: Yhteys torjuttu touko 18 20:55:47 ThinkPad-X301 gnome-shell[934]: Error looking up permission: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.free touko 18 20:55:47 ThinkPad-X301 gnome-shell[934]: JS WARNING: [resource:///org/gnome/shell/ui/windowManager.js 1468]: reference to undefined property " touko 18 20:55:49 ThinkPad-X301 gnome-shell[934]: nma_mobile_providers_database_lookup_cdma_sid: assertion 'sid > 0' failed touko 18 20:56:05 ThinkPad-X301 gnome-shell[1545]: JS WARNING: [resource:///org/gnome/shell/ui/main.js 340]: reference to undefined property "MetaStage touko 18 20:56:05 ThinkPad-X301 gnome-shell[1545]: JS WARNING: [resource:///org/gnome/shell/ui/layout.js 220]: reference to undefined property "MetaWin touko 18 20:56:05 ThinkPad-X301 gnome-shell[1545]: JS WARNING: [resource:///org/gnome/shell/ui/osdMonitorLabeler.js 59]: reference to undefined propert touko 18 20:56:06 ThinkPad-X301 gnome-shell[1545]: JS WARNING: [resource:///org/gnome/shell/ui/slider.js 38]: reference to undefined property "CallyAct touko 18 20:56:07 ThinkPad-X301 gnome-shell[1545]: Telepathy is not available, chat integration will be disabled. touko 18 20:56:09 ThinkPad-X301 gnome-shell[1545]: JS WARNING: [/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/appIcons.js 1027]: unreachable touko 18 20:56:11 ThinkPad-X301 gnome-shell[1545]: JS ERROR: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not get owner getUniqueBusNameSync@ /usr/share/gnome-shell/extensions/ ubuntu-appindicat...@ubuntu.com/util.js:58:20 traverseBusNames/<@/usr/share/gnome-shell/extensions/ ubuntu-appindicat...@ubuntu.com/util.js:82:34 touko 18 20:56:12 ThinkPad-X301
[Desktop-packages] [Bug 1540110] Re: gnome-disk-utility (shown as "Disks") shows SMART option grayed for USB connect disks despite being available.
having same problem and it seems random for my SATA drives 3.28.1-0ubuntu1 ** Attachment added: "Screenshot from 2018-05-19 04-16-21.png" https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1540110/+attachment/5141392/+files/Screenshot%20from%202018-05-19%2004-16-21.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1540110 Title: gnome-disk-utility (shown as "Disks") shows SMART option grayed for USB connect disks despite being available. Status in GNOME Disks: Confirmed Status in gnome-disk-utility package in Ubuntu: Confirmed Bug description: gnome-disk-utility (show as "Disks" on the desktop environment running Unity) systematically does not acknowledge that disks have SMART capabilities when connected through a USB port; SMART capabilities are grayed. However, 'sudo smartctl -a /dev/' works fine confirming that there is no problem reading SMART data through a USB link. gnome- disk-utility acknowledge SMART capabilities if the same disk is connected through a SATA port. Confirmed for Ubuntu 14.04 LTS Trusty Tahr on 2016-01-26, gnome-disk- utility 3.10.0, udisks 2.1.3 (built against 2.1.3) by Hans Deragon. This bug is the same as bug #1092900 which was reported against Ubuntu 10.04 LTS Lucid Lynx. Following user dino99 suggestion, I opened this new bug report to follow the same problem on Ubuntu 14.04 LTS Trusty Tahr. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-disk-utility 3.10.0-1ubuntu3 ProcVersionSignature: Ubuntu 3.13.0-76.120-generic 3.13.11-ckt30 Uname: Linux 3.13.0-76-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 CurrentDesktop: Unity Date: Sun Jan 31 11:30:03 2016 InstallationDate: Installed on 2014-11-01 (456 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) SourcePackage: gnome-disk-utility UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-disk-utility/+bug/1540110/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1771880] Re: Seahorse unable to import certificates in Ubuntu 18.04
When trying to import the certificate via command line I get the following output: $ gnome-keyring import .p12 gnome-keyring: couldn't parse: .p12 gnome-keyring: couldn't find any place to import files That's all I know at the moment. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to seahorse in Ubuntu. https://bugs.launchpad.net/bugs/1771880 Title: Seahorse unable to import certificates in Ubuntu 18.04 Status in gnome-keyring package in Ubuntu: New Status in seahorse package in Ubuntu: New Bug description: seahorse 3.20.0-5 / gnome-keyring 3.28.0.2-1ubuntu1.18.04.1 / Ubuntu 18.04 LTS / GNOME 3.28.1 When trying to import a certificate into seahorse/gnome-keyring on Ubuntu 18.04, seahorse GUI application shows the 'import' button greyed out, while mouse hovering the "import" button shows the message "Cannot import because there are no compatible importers". This problem doesn't occur on Ubuntu 16.04 LTS (Seahorse 3.18.0), as I've just tested on my wife's laptop, but happens in my Laptop with Ubuntu 18.04 LTS (Seahorse 3.20.0-5). Because that problem, it's not possible to digitally sign documents with LibreOffice. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1771880/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1762952] Re: Alternative shortcut for layout switching Alt+Shift unexpectedly set by default
Thanks for looking, Łukasz. Right, it didn't build in PPA for me without those. As regards 'locales', according to the build log it looked for and failed to find /usr/share/i18n/charmaps. As regards the extra install directory in d/rules, it's obviously needed if the conditions for running the subsequent commands are satisfied. Can't explain why it differs from the archive uploads. I just run "debuild -S" and dput'ed (not from a clean chroot, though). I think that $1 is always "configure" at the execution of postinst. Please note that the original code checks for precisely that. I struggled a bit to find a way to check whether we are upgrading, and the proposed way proved to work when I tested. But I'm not a Debian packaging wizard, and would be just as happy if there is a simpler way to check for it. Actually, the fact that keyboard-configuration and g-c-c both write to /etc/default/keyboard, while they have different ideas of what it should contain, appears to be a bit odd. My proposal only addresses the most obvious issue as reported in this bug, i.e. it prevents the keyboard configuration from being changed without the user having asked for it. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1762952 Title: Alternative shortcut for layout switching Alt+Shift unexpectedly set by default Status in console-setup package in Ubuntu: In Progress Status in gnome-control-center package in Ubuntu: Confirmed Bug description: Version: Ubuntu 18.04 Final Beta with default Gnome Shell included in 18.04 Steps to reproduce: 1. Define two keyboard input methods in Settings -> Region & Language -> Input Sources 2. Open several applications 3. Observe that application windows can be iterated with Alt + Tab 4. Once application window iteration was begun with Alt + Tab, try to iterate backwards with Alt + Shift + Tab. 5. Try to change keyboard input method switching hotkeys in Settings -> Region & Language -> Input Sources -> Options. 6. Observe that Keyboard shortcut for "Alternative switch to next source" is set to "Alt + Shift" and that keyboard shortcuts can only be changed in Settings -> Devices -> Keyboard -> Keyboard Shortcuts. 7. Observe that the shortcut for "Alternative switch to next source" is not available for configuration in Settings -> Devices -> Keyboard -> Keyboard Shortcuts. Actual state: * Performing step 4 does not select the previous app in application switcher but instead changes keyboard input method. Expected state: * The shortcut for "Alternative switch to next source" can be changed and / or deactivated in Settings -> Devices -> Keyboard -> Keyboard Shortcuts. Notes: * The above was working fine in Ubuntu 17.10. I assume "Alternative switch to next source" did not exist in that version of Gnome Shell. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1762952/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1766137] Re: [regression] Password accepted but login fails (blank purple screen and mouse pointer only)
Not sure what came out but this is out come of running journalctl right after booting after freeze. I need clear guidance to get something else more relevant. Logs begin at Fri 2018-04-27 22:06:06 EEST, end at Fri 2018-05-18 20:56:33 EE huhti 27 22:06:06 ThinkPad-X301 kernel: Linux version 4.15.0-20-generic (buildd@ huhti 27 22:06:06 ThinkPad-X301 kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-4 huhti 27 22:06:06 ThinkPad-X301 kernel: KERNEL supported cpus: huhti 27 22:06:06 ThinkPad-X301 kernel: Intel GenuineIntel huhti 27 22:06:06 ThinkPad-X301 kernel: AMD AuthenticAMD huhti 27 22:06:06 ThinkPad-X301 kernel: Centaur CentaurHauls huhti 27 22:06:06 ThinkPad-X301 kernel: Disabled fast string operations huhti 27 22:06:06 ThinkPad-X301 kernel: x86/fpu: x87 FPU will use FXSAVE huhti 27 22:06:06 ThinkPad-X301 kernel: e820: BIOS-provided physical RAM map: huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem 0x-0x000 huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem 0x0009ec00-0x000 huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem 0x000dc000-0x000 huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem 0x0010-0x000 huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem 0xbd6a1000-0x000 huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem 0xbd6a7000-0x000 huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem 0xbd7b7000-0x000 huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem 0xbd80f000-0x000 huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem 0xbd8c7000-0x000 huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem 0xbd8d2000-0x000 huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem 0xbd8d5000-0x000 huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem 0xbd8d9000-0x000 huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem 0xbd8dd000-0x000 lines 1-23...skipping... -- Logs begin at Fri 2018-04-27 22:06:06 EEST, end at Fri 2018-05-18 20:56:33 EEST. -- huhti 27 22:06:06 ThinkPad-X301 kernel: Linux version 4.15.0-20-generic (buildd@lgw01-amd64-039) (gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #21-Ubunt huhti 27 22:06:06 ThinkPad-X301 kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=bf89dfab-58a9-4161-a23c-18da35c20198 ro quie huhti 27 22:06:06 ThinkPad-X301 kernel: KERNEL supported cpus: huhti 27 22:06:06 ThinkPad-X301 kernel: Intel GenuineIntel huhti 27 22:06:06 ThinkPad-X301 kernel: AMD AuthenticAMD huhti 27 22:06:06 ThinkPad-X301 kernel: Centaur CentaurHauls huhti 27 22:06:06 ThinkPad-X301 kernel: Disabled fast string operations huhti 27 22:06:06 ThinkPad-X301 kernel: x86/fpu: x87 FPU will use FXSAVE huhti 27 22:06:06 ThinkPad-X301 kernel: e820: BIOS-provided physical RAM map: huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem 0x-0x0009ebff] usable huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem 0x0009ec00-0x0009] reserved huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem 0x000dc000-0x000f] reserved huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem 0x0010-0xbd6a0fff] usable huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem 0xbd6a1000-0xbd6a6fff] reserved huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem 0xbd6a7000-0xbd7b6fff] usable huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem 0xbd7b7000-0xbd80efff] reserved huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem 0xbd80f000-0xbd8c6fff] usable huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem 0xbd8c7000-0xbd8d1fff] ACPI NVS huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem 0xbd8d2000-0xbd8d4fff] ACPI data huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem 0xbd8d5000-0xbd8d8fff] reserved huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem 0xbd8d9000-0xbd8dcfff] ACPI NVS huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem 0xbd8dd000-0xbd8d] reserved huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem 0xbd8e-0xbd906fff] ACPI NVS huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem 0xbd907000-0xbd907fff] ACPI data huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem 0xbd908000-0xbdb0efff] reserved huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem 0xbdb0f000-0xbdb9efff] ACPI NVS huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem 0xbdb9f000-0xbdbfefff] ACPI data huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem 0xbdbff000-0xbdbf] usable huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem 0xbdc0-0xbfff] reserved huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem 0xe000-0xefff] reserved huhti 27
Re: [Desktop-packages] [Bug 1766137] Re: [regression] Password accepted but login fails (blank purple screen and mouse pointer only)
sorry this is the out come of journalctl /usr/bin/gnome-shell -- Logs begin at Fri 2018-04-27 22:06:06 EEST, end at Fri 2018-05-18 21:03:51 EE huhti 27 22:06:13 ThinkPad-X301 org.gnome.Shell.desktop[762]: glamor: EGL versio huhti 27 22:06:16 ThinkPad-X301 gnome-shell[762]: JS WARNING: [resource:///org/g huhti 27 22:06:16 ThinkPad-X301 gnome-shell[762]: JS WARNING: [resource:///org/g huhti 27 22:06:16 ThinkPad-X301 gnome-shell[762]: JS WARNING: [resource:///org/g huhti 27 22:06:17 ThinkPad-X301 gnome-shell[762]: JS WARNING: [resource:///org/g huhti 27 22:06:19 ThinkPad-X301 gnome-shell[762]: Error looking up permission: G huhti 27 22:06:19 ThinkPad-X301 gnome-shell[762]: nma_mobile_providers_database_ huhti 27 22:06:20 ThinkPad-X301 gnome-shell[762]: JS WARNING: [resource:///org/g huhti 27 22:06:44 ThinkPad-X301 gnome-shell[1812]: JS WARNING: [resource:///org/ huhti 27 22:06:44 ThinkPad-X301 gnome-shell[1812]: JS WARNING: [resource:///org/ huhti 27 22:06:44 ThinkPad-X301 gnome-shell[1812]: JS WARNING: [resource:///org/ huhti 27 22:06:46 ThinkPad-X301 gnome-shell[1812]: JS WARNING: [resource:///org/ huhti 27 22:06:46 ThinkPad-X301 gnome-shell[1812]: Telepathy is not available, c huhti 27 22:06:49 ThinkPad-X301 gnome-shell[1812]: JS WARNING: [/usr/share/gnome huhti 27 22:06:54 ThinkPad-X301 gnome-shell[1812]: [AppIndicatorSupport-DEBUG] R huhti 27 22:06:56 ThinkPad-X301 gnome-shell[1812]: Object St.BoxLayout (0x561a90 huhti 27 22:06:56 ThinkPad-X301 org.gnome.Shell.desktop[1812]: == Stack trace fo huhti 27 22:06:56 ThinkPad-X301 org.gnome.Shell.desktop[1812]: #0 0x73031450 huhti 27 22:06:56 ThinkPad-X301 org.gnome.Shell.desktop[1812]: #1 0x730314b0 huhti 27 22:06:56 ThinkPad-X301 org.gnome.Shell.desktop[1812]: #2 0x73031580 huhti 27 22:06:56 ThinkPad-X301 org.gnome.Shell.desktop[1812]: #3 0x730315f0 huhti 27 22:06:56 ThinkPad-X301 org.gnome.Shell.desktop[1812]: #4 0x561a8f6df7a0 pe 18. toukok. 2018 klo 21.01 Heikki Moisander (moisan...@gmail.com) kirjoitti: > Not sure what came out but this is out come of running journalctl right > after booting after freeze. > I need clear guidance to get something else more relevant. > > Logs begin at Fri 2018-04-27 22:06:06 EEST, end at Fri 2018-05-18 20:56:33 > EE > huhti 27 22:06:06 ThinkPad-X301 kernel: Linux version 4.15.0-20-generic > (buildd@ > huhti 27 22:06:06 ThinkPad-X301 kernel: Command line: > BOOT_IMAGE=/boot/vmlinuz-4 > huhti 27 22:06:06 ThinkPad-X301 kernel: KERNEL supported cpus: > huhti 27 22:06:06 ThinkPad-X301 kernel: Intel GenuineIntel > huhti 27 22:06:06 ThinkPad-X301 kernel: AMD AuthenticAMD > huhti 27 22:06:06 ThinkPad-X301 kernel: Centaur CentaurHauls > huhti 27 22:06:06 ThinkPad-X301 kernel: Disabled fast string operations > huhti 27 22:06:06 ThinkPad-X301 kernel: x86/fpu: x87 FPU will use FXSAVE > huhti 27 22:06:06 ThinkPad-X301 kernel: e820: BIOS-provided physical RAM > map: > huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem > 0x-0x000 > huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem > 0x0009ec00-0x000 > huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem > 0x000dc000-0x000 > huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem > 0x0010-0x000 > huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem > 0xbd6a1000-0x000 > huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem > 0xbd6a7000-0x000 > huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem > 0xbd7b7000-0x000 > huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem > 0xbd80f000-0x000 > huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem > 0xbd8c7000-0x000 > huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem > 0xbd8d2000-0x000 > huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem > 0xbd8d5000-0x000 > huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem > 0xbd8d9000-0x000 > huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem > 0xbd8dd000-0x000 > lines 1-23...skipping... > -- Logs begin at Fri 2018-04-27 22:06:06 EEST, end at Fri 2018-05-18 > 20:56:33 EEST. -- > huhti 27 22:06:06 ThinkPad-X301 kernel: Linux version 4.15.0-20-generic > (buildd@lgw01-amd64-039) (gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) > #21-Ubunt > huhti 27 22:06:06 ThinkPad-X301 kernel: Command line: > BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic > root=UUID=bf89dfab-58a9-4161-a23c-18da35c20198 ro quie > huhti 27 22:06:06 ThinkPad-X301 kernel: KERNEL supported cpus: > huhti 27 22:06:06 ThinkPad-X301 kernel: Intel GenuineIntel > huhti 27 22:06:06 ThinkPad-X301 kernel: AMD AuthenticAMD > huhti 27 22:06:06 ThinkPad-X301 kernel: Centaur CentaurHauls > huhti 27 22:06:06 ThinkPad-X301 kernel: Disabled fast string operations > huhti 27 22:06:06 ThinkPad-X301 kernel: x86/fpu: x87 FPU will use FXSAVE > huhti 27 22:06:06 ThinkPad-X301 kernel: e820: BIOS-provided physical RAM > map: > huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem >
[Desktop-packages] [Bug 525119]
http://value.richod.com Cosmin Mazilu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/525119 Title: folders in evolution dont appear , it seams i can subscribe to folders so i can't see any email Status in evolution package in Ubuntu: Invalid Bug description: Binary package hint: evolution folders in evolution dont appear , it seams i can subscribe to folders so i can't see any email .this happens on the evolution that comes with ubuntu 9.10 , i tried to reinstall evolution but it didin't work ProblemType: Bug Architecture: i386 Date: Sun Feb 21 04:23:11 2010 DistroRelease: Ubuntu 9.10 ExecutablePath: /usr/bin/evolution InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5) NonfreeKernelModules: nvidia Package: evolution 2.28.1-0ubuntu2 ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 ProcVersionSignature: Ubuntu 2.6.31-19.56-generic SourcePackage: evolution Uname: Linux 2.6.31-19-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/525119/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1771880] Re: Seahorse unable to import certificates in Ubuntu 18.04
** Also affects: gnome-keyring (Ubuntu) Importance: Undecided Status: New ** Description changed: - Seahorse 3.20.0-5 / Ubuntu 18.04 LTS / GNOME 3.28.1 + seahorse 3.20.0-5 / gnome-keyring 3.28.0.2-1ubuntu1.18.04.1 / Ubuntu + 18.04 LTS / GNOME 3.28.1 When trying to import a certificate into seahorse/gnome-keyring on Ubuntu 18.04, seahorse GUI application shows the 'import' button greyed out, while mouse hovering the "import" button shows the message "Cannot import because there are no compatible importers". This problem doesn't occur on Ubuntu 16.04 LTS (Seahorse 3.18.0), as I've just tested on my wife's laptop, but happens in my Laptop with Ubuntu 18.04 LTS (Seahorse 3.20.0-5). Because that problem, it's not possible to digitally sign documents with LibreOffice. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to seahorse in Ubuntu. https://bugs.launchpad.net/bugs/1771880 Title: Seahorse unable to import certificates in Ubuntu 18.04 Status in gnome-keyring package in Ubuntu: New Status in seahorse package in Ubuntu: New Bug description: seahorse 3.20.0-5 / gnome-keyring 3.28.0.2-1ubuntu1.18.04.1 / Ubuntu 18.04 LTS / GNOME 3.28.1 When trying to import a certificate into seahorse/gnome-keyring on Ubuntu 18.04, seahorse GUI application shows the 'import' button greyed out, while mouse hovering the "import" button shows the message "Cannot import because there are no compatible importers". This problem doesn't occur on Ubuntu 16.04 LTS (Seahorse 3.18.0), as I've just tested on my wife's laptop, but happens in my Laptop with Ubuntu 18.04 LTS (Seahorse 3.20.0-5). Because that problem, it's not possible to digitally sign documents with LibreOffice. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1771880/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1766137] Re: [regression] Password accepted but login fails (blank purple screen and mouse pointer only)
Bodinux after clicking your name, wait a while before entering the correct password. -- 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/1766137 Title: [regression] Password accepted but login fails (blank purple screen and mouse pointer only) Status in gdm: Fix Released Status in Release Notes for Ubuntu: Fix Released Status in gdm3 package in Ubuntu: Fix Released Status in gnome-shell package in Ubuntu: Invalid Status in gdm3 source package in Bionic: Fix Committed Status in gnome-shell source package in Bionic: Invalid Bug description: [ Description ] Due to a refcounting bug, a GDBusConnection was getting disposed when it was still required. The symptom of this was that you couldn't log in if you'd got your password wrong. [ Test case ] 1. Boot to GDM 2. Click your username 3. Type the wrong password a couple of times, pressing enter after each time 4. Type the right password If the bug is happening, after 4. the system hangs at a blank screen with the mouse cursor. If you then switch to a VT or otherwise connect to the machine, you can examine the journal and you'll see a G_IS_DBUS_CONNECTION failure. [ Fix ] Marco and I worked upstream on this fix. We found out that there was a problem like this- The GdmClient has a shared GDBusConnection for its operations. The first time someone calls for it, it is created and stored in the object's private structure. Subsequent calls return *a new reference* to this same object. It turned out that the asynchronous method to get the connection was accidentally unreferencing its object before giving it to the caller if it was returning an already-existing connection. For this to work properly, we need to nullify the pointer we stored when the connection goes away, so we know when to make a new one. There were some cases where we didn't add the weak references required to do that. Those are also fixed. [ Regression potential ] Now we share connections more than we did before. We also more carefully track when to clear our object. If we got this wrong, we might end up leaking the connection or dropping it in even more cases. [ Original report ] WORKAROUND: After typing an incorrect password, click Cancel, then click your name, then enter your password again. --- Trying to log into my session (Gnome, Xorg), if I enter the wrong password before entering it correctly, the session doesn't load and I get a purple screen, a mouse cursor, and an invisible but clickable menu in the top right. If I enter it correctly the first time, there is no problem. I've replicated this from a fresh boot, after logging out and after 'sudo service gdm restart' from the Ctrl-Alt-F4 console. This is a fresh install, and didn't occur when I was using a previous install of 18.04 (until Friday). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Apr 22 20:31:13 2018 InstallationDate: Installed on 2018-04-22 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180421.1) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1766137/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1772067] Re: on-screen keyboard layout is the wrong one and cannot change
** Summary changed: - on-screen keyboard layout is wrong and cannot change + on-screen keyboard layout is the wrong one and cannot change -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to onboard in Ubuntu. https://bugs.launchpad.net/bugs/1772067 Title: on-screen keyboard layout is the wrong one and cannot change Status in onboard package in Ubuntu: New Bug description: What's wrong : The onscreen keyboard layout is set to qwerty even if another layout was selected during install. It is not possible to change the on-screen keyboard layout How to reproduce : on login screen, select user, enable the on-screen keyboard (osk), click on the password box, osk appears. It is in qwerty. Click on Flag, the flag popup appears with the registered layouts, raise the mouse towards the list : the on-screen keyboard disappears too soon to allow clicking. Get used to the on-screen keyboard layout and get fast, Click on Flag, click quickly on the popup to the desired layout : Nothing happens, keyboard layout remains the same. Version : 1.4.1-2ubuntu1 Information : I have two layouts in /etc/default/keyboard, none is in qwerty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/onboard/+bug/1772067/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1306849] Re: Printing error
Still experiencing this in Xubuntu Bionic, with Firefox 60.0.1. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to foomatic-db in Ubuntu. https://bugs.launchpad.net/bugs/1306849 Title: Printing error Status in foomatic-db package in Ubuntu: Confirmed Bug description: I get the message ERROR NAME; stackunderflow COMMAND; pop OPERAND STACK; when I try to print from Firefox or anything that has a picture as part of the file. I am running saucy on an AMD64 system. so far I have tried deleting the printer and setting it up again. No change. Ubuntu 13.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/foomatic-db/+bug/1306849/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1763736] Re: Snaps without icons not showing
As you can see in the attached file, Community Theme snap is found in the store search. Thanks for that ** Attachment added: "Capture du 2018-05-18 18-39-59.png" https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1763736/+attachment/5141313/+files/Capture%20du%202018-05-18%2018-39-59.png ** Tags removed: verification-needed-xenial ** Tags added: verification-done-xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1763736 Title: Snaps without icons not showing Status in gnome-software package in Ubuntu: Fix Released Status in gnome-software source package in Xenial: Fix Committed Status in gnome-software source package in Artful: Won't Fix Status in gnome-software source package in Bionic: Fix Released Bug description: [Impact] Snaps that do not provide icons do not show in GNOME Software. They do show on the snapcraft.io website using a default icon. [Test Case] 1. Open GNOME Software 2. Search for "communitheme" Expected result: Community Theme snap shows, using an appropriate icon. Observed result (2 May 2018): Community Theme snap does not show. Note that if the snap is updated in the store this behaviour will change - so will have to check another snap. [Regression Potential] The fix adds the default icon to snaps that do not have one. This will cause more snaps to show, which could expose new bugs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1763736/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1768232] Re: Stuck at ubuntu logo while booting after installing Ubuntu 18.04 (Resolution 1024x768 after nomodeset, i915 driver issue)
I have a Dell Optiplex 330 workstation with Intel 82G33/G31 Express graphics. It ran Ubuntu 16.04, Ubuntu 17.10, and Ubuntu 18.04 beta2 without any issues. When Ubuntu 18.04 was released I did a clean install and it would boot to the Ubuntu logo screen and stop. I tried several kernels from http://kernel.ubuntu.com/~kernel-ppa/mainline but the issue was not resolved. To resolve the issue I had to disable Wayland in GDM3. sudo vi /etc/gdm3/custom.conf Change #WaylandEnable=false to WaylandEnable=false and reboot Reference: https://linuxconfig.org/how-to-disable-wayland-and-enable- xorg-display-server-on-ubuntu-18-04-bionic-beaver-linux -- 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/1768232 Title: Stuck at ubuntu logo while booting after installing Ubuntu 18.04 (Resolution 1024x768 after nomodeset, i915 driver issue) Status in xorg package in Ubuntu: Confirmed Bug description: My system stuck at ubuntu logo while booting. To resolve it, I've set nomodeset. But now it occurs a resolution issue to 1024x768. Here are the necessary information: lspci -nnk | grep -iA2 vga 00:02.0 VGA compatible controller [0300]: Intel Corporation 82945G/GZ Integrated Graphics Controller [8086:2772] (rev 02) Subsystem: Hewlett-Packard Company 82945G/GZ Integrated Graphics Controller [103c:302a] Kernel modules: i915, intelfb and xrandr xrandr: Failed to get size of gamma for output default Screen 0: minimum 1024 x 768, current 1024 x 768, maximum 1024 x 768 default connected primary 1024x768+0+0 0mm x 0mm 1024x768 76.00* Output of sudo lshw -c display *-display UNCLAIMED description: VGA compatible controller product: 82945G/GZ Integrated Graphics Controller vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 version: 02 width: 32 bits clock: 33MHz capabilities: msi pm vga_controller bus_master cap_list configuration: latency=0 resources: memory:e200-e207 ioport:c000(size=8) memory:d000-dfff memory:e208-e20b memory:c-d This issue occurred only after installing it, not when I choose 'Try without Installing', I don't need to set nomodeset in that case. Intel Graphics Update Tool shows: Checking if Intel graphics card available... • checking for i915 module in /sys/module • i915 module found Checking if Intel graphics card available... OK Retrieving information from 01.org... • fetching https://download.01.org/gfx/ilg-config.cfg • saving to /home/test/.ilg-config • fetched 1626 bytes • fetched 9818 bytes • fetched 12301 bytes • looking up [Ubuntu bionic] configuration Retrieving information from 01.org... OK Checking distribution... Failed ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue May 1 17:16:20 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation 82945G/GZ Integrated Graphics Controller [8086:2772] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company 82945G/GZ Integrated Graphics Controller [103c:302a] InstallationDate: Installed on 2018-05-01 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Hewlett-Packard HP dx2080 MT(KS826PA) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=7ec4f610-9b62-44f3-867d-01abd93de14d ro quiet splash nomodeset vt.handoff=1 Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) XorgConf: Section "Device" Identifier "Intel Graphics" Driver "intel" Option "AccelMethod" "uxa" EndSection dmi.bios.date: 11/28/2007 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: V1.03 dmi.board.name: 0AD8h dmi.board.vendor: Board Manufacturer dmi.chassis.asset.tag: INA8100LFY dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrV1.03:bd11/28/2007:svnHewlett-Packard:pnHPdx2080MT(KS826PA):pvr:rvnBoardManufacturer:rn0AD8h:rvr:cvnHewlett-Packard:ct3:cvr: dmi.product.name: HP dx2080 MT(KS826PA) dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2
[Desktop-packages] [Bug 1772067] Re: on-screen keyboard layout is wrong and cannot change
** Package changed: gdm3 (Ubuntu) => onboard (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to onboard in Ubuntu. https://bugs.launchpad.net/bugs/1772067 Title: on-screen keyboard layout is wrong and cannot change Status in onboard package in Ubuntu: New Bug description: What's wrong : The onscreen keyboard layout is set to qwerty even if another layout was selected during install. It is not possible to change the on-screen keyboard layout How to reproduce : on login screen, select user, enable the on-screen keyboard (osk), click on the password box, osk appears. It is in qwerty. Click on Flag, the flag popup appears with the registered layouts, raise the mouse towards the list : the on-screen keyboard disappears too soon to allow clicking. Get used to the on-screen keyboard layout and get fast, Click on Flag, click quickly on the popup to the desired layout : Nothing happens, keyboard layout remains the same. Version : 1.4.1-2ubuntu1 Information : I have two layouts in /etc/default/keyboard, none is in qwerty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/onboard/+bug/1772067/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1763736] Re: Snaps without icons not showing
Tested with gnome software 3.20-5 0ubuntu0.16.04.11 from proposed -- 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/1763736 Title: Snaps without icons not showing Status in gnome-software package in Ubuntu: Fix Released Status in gnome-software source package in Xenial: Fix Committed Status in gnome-software source package in Artful: Won't Fix Status in gnome-software source package in Bionic: Fix Released Bug description: [Impact] Snaps that do not provide icons do not show in GNOME Software. They do show on the snapcraft.io website using a default icon. [Test Case] 1. Open GNOME Software 2. Search for "communitheme" Expected result: Community Theme snap shows, using an appropriate icon. Observed result (2 May 2018): Community Theme snap does not show. Note that if the snap is updated in the store this behaviour will change - so will have to check another snap. [Regression Potential] The fix adds the default icon to snaps that do not have one. This will cause more snaps to show, which could expose new bugs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1763736/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1772032] Re: [snap /from-source] broken launcher
Tentative fix: https://git.launchpad.net/~chromium-team/chromium- browser/+git/snap-from- source/commit/?id=19d79ddbb8471b789b4e5ed920601c70ae4d26ba A new snap is building and will be published in the candidate/from- source channel when ready. ** Changed in: chromium-browser (Ubuntu) Status: Confirmed => Fix Committed -- 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/1772032 Title: [snap /from-source] broken launcher Status in chromium-browser package in Ubuntu: Fix Committed Bug description: Ran `snap install chromium --channel=candidate/from-source` as suggested in https://community.ubuntu.com/t/intent-to-provide- chromium-as-a-snap-only/5987 and I think it broke my launcher (from searching for Chromium in Activities). Clicking on it produces the notification: Failed to launch "Chromium Web Browser" Desktop file didn't specify exec field Also the launcher has no icon (only the plain executable one) ``` $ snap info chromium tracking: candidate/from-source refreshed: 2018-05-16T22:04:26+01:00 installed: 66.0.3359.181 (331) 238MB - $ snap version snap2.32.8+18.04 snapd 2.32.8+18.04 series 16 ubuntu 18.04 kernel 4.15.0-20-generic $ snap info core tracking: beta refreshed: 2018-05-11T15:51:12+01:00 installed: 16-2.32.8(4650) 90MB core ``` ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: chromium-browser (not installed) ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: communitheme:ubuntu:GNOME Date: Fri May 18 14:09:37 2018 InstallationDate: Installed on 2017-08-03 (287 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: chromium-browser UpgradeStatus: Upgraded to bionic on 2018-04-22 (26 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1772032/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1772066] [NEW] Ubuntu 18.04 Network-Manager-OpenVPN won't connected, worked in 17.10, 17.04
Public bug reported: Under Kubuntu 18.04 and Ubuntu 18.04 (both installed multiboot on a Thinkpad X230T), OpenVPN won't connect to a host that worked under Kubuntu 17.10 and 17.04. This host continues to be accessible under Deepin Linux. Here is a log from today's attempt on Kubuntu 18.04. -- begin paste -- $ grep VPN /var/log/syslog May 18 12:19:28 mycomputer systemd[1]: Stopped OpenVPN service. May 18 12:20:02 mycomputer systemd[1]: Starting OpenVPN service... May 18 12:20:02 mycomputer systemd[1]: Started OpenVPN service. May 18 12:22:19 mycomputer NetworkManager[819]: [1526660539.0028] vpn-connection[0x55b11e5a01a0,d5e7329e-1444-4c96-a4b6-12d4d9e3130b,"UTORvpn",0]: Started the VPN service, PID 3113 May 18 12:22:19 mycomputer NetworkManager[819]: [1526660539.2667] vpn-connection[0x55b11e5a01a0,d5e7329e-1444-4c96-a4b6-12d4d9e3130b,"UTORvpn",0]: VPN plugin: state changed: starting (3) May 18 12:22:19 mycomputer nm-openvpn[3116]: OpenVPN 2.4.4 x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Feb 10 2018 May 18 12:22:19 mycomputer NetworkManager[819]: [1526660539.5365] vpn-connection[0x55b11e5a01a0,d5e7329e-1444-4c96-a4b6-12d4d9e3130b,"UTORvpn",0]: VPN plugin: failed: connect-failed (1) May 18 12:22:19 mycomputer NetworkManager[819]: [1526660539.5365] vpn-connection[0x55b11e5a01a0,d5e7329e-1444-4c96-a4b6-12d4d9e3130b,"UTORvpn",0]: VPN plugin: failed: connect-failed (1) May 18 12:22:19 mycomputer NetworkManager[819]: [1526660539.5370] vpn-connection[0x55b11e5a01a0,d5e7329e-1444-4c96-a4b6-12d4d9e3130b,"UTORvpn",0]: VPN plugin: state changed: stopping (5) May 18 12:22:19 mycomputer NetworkManager[819]: [1526660539.5381] vpn-connection[0x55b11e5a01a0,d5e7329e-1444-4c96-a4b6-12d4d9e3130b,"UTORvpn",0]: VPN plugin: state changed: stopped (6) May 18 12:22:19 mycomputer NetworkManager[819]: [1526660539.5396] vpn-connection[0x55b11e5a01a0,d5e7329e-1444-4c96-a4b6-12d4d9e3130b,"UTORvpn",0]: VPN service disappeared -- end paste -- Just in case it's not included from the ubuntu-bug network-manager- openvpn -- begin paste -- $ lsb_release -rd Description:Ubuntu 18.04 LTS Release:18.04 $ apt-cache policy network-manager-openvpn network-manager-openvpn: Installed: 1.8.2-1 Candidate: 1.8.2-1 Version table: *** 1.8.2-1 500 500 http://ca.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status -- end paste -- And here's the results of an attempt on Ubuntu 18.04 a few days ago. -- begin paste -- daviding@mycomputer:~$ grep VPN /var/log/syslog May 16 13:09:38 mycomputer NetworkManager[935]: [1526490578.0785] keyfile: add connection /etc/NetworkManager/system-connections/UTorVPN (0a3eb80f-80ab-4ffd-81e5-7370c7ceedb6,"UTorVPN") May 16 13:09:38 mycomputer NetworkManager[935]: [1526490578.0794] audit: op="connection-add" uuid="0a3eb80f-80ab-4ffd-81e5-7370c7ceedb6" name="UTorVPN" pid=3635 uid=1000 result="success" May 16 13:11:11 mycomputer gnome-shell[2018]: VPN plugin at /usr/lib/NetworkManager/nm-openvpn-auth-dialog is not executable May 16 13:11:11 mycomputer gnome-shell[2018]: Invalid VPN service type (cannot find authentication binary) May 16 13:11:42 mycomputer NetworkManager[935]: [1526490702.3080] audit: op="connection-activate" uuid="0a3eb80f-80ab-4ffd-81e5-7370c7ceedb6" name="UTorVPN" pid=3635 uid=1000 result="success" May 16 13:11:42 mycomputer NetworkManager[935]: [1526490702.3167] vpn-connection[0x561cde5941c0,0a3eb80f-80ab-4ffd-81e5-7370c7ceedb6,"UTorVPN",0]: Started the VPN service, PID 5807 May 16 13:11:42 mycomputer NetworkManager[935]: [1526490702.3231] vpn-connection[0x561cde5941c0,0a3eb80f-80ab-4ffd-81e5-7370c7ceedb6,"UTorVPN",0]: Saw the service appear; activating connection May 16 13:11:42 mycomputer NetworkManager[935]: [1526490702.3286] vpn-connection[0x561cde5941c0,0a3eb80f-80ab-4ffd-81e5-7370c7ceedb6,"UTorVPN",0]: plugin NeedSecrets request #1 failed: Invalid connection type. May 16 13:11:42 mycomputer NetworkManager[935]: [1526490702.3361] vpn-connection[0x561cde5941c0,0a3eb80f-80ab-4ffd-81e5-7370c7ceedb6,"UTorVPN",0]: VPN service disappeared May 16 13:11:43 mycomputer NetworkManager[935]: [1526490703.3431] audit: op="connection-activate"H uuid="0a3eb80f-80ab-4ffd-81e5-7370c7ceedb6" name="UTorVPN" pid=3635 uid=1000 result="success" May 16 13:11:43 mycomputer NetworkManager[935]: [1526490703.3499] vpn-connection[0x561cde5943c0,0a3eb80f-80ab-4ffd-81e5-7370c7ceedb6,"UTorVPN",0]: Started the VPN service, PID 5813 May 16 13:11:43 mycomputer NetworkManager[935]: [1526490703.3626] vpn-connection[0x561cde5943c0,0a3eb80f-80ab-4ffd-81e5-7370c7ceedb6,"UTorVPN",0]: Saw the service appear; activating connection May 16 13:11:43 mycomputer NetworkManager[935]: [1526490703.3675] vpn-connection[0x561cde5943c0,0a3eb80f-80ab-4ffd-81e5-7370c7ceedb6,"UTorVPN",0]: plugin NeedSecrets request #1 failed: Invalid connection type. May 16 13:11:43
[Desktop-packages] [Bug 1738164] Re: [snap] U2F doesn't work with yubikey
Do you get more useful debug information if you run the snap with the "--enable-logging=stderr" parameter? -- 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/1738164 Title: [snap] U2F doesn't work with yubikey Status in chromium-browser package in Ubuntu: Confirmed Bug description: (initially reported by Daniel at https://forum.snapcraft.io/t/call- for-testing-chromium-62-0-3202-62/2569/50) « U2F (Universal 2nd Factor) isn’t working when signing into my gmail account trying to use my yubikey. This is a USB device which IIRC chromium needs bidirectional communication with. » This requires investigation, but the yubikey I have is too old and doesn't support U2F. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1738164/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1766137] Re: [regression] Password accepted but login fails (blank purple screen and mouse pointer only)
Looks weird, can you attach the output of journalctl /usr/bin/gnome-shell ? -- 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/1766137 Title: [regression] Password accepted but login fails (blank purple screen and mouse pointer only) Status in gdm: Fix Released Status in Release Notes for Ubuntu: Fix Released Status in gdm3 package in Ubuntu: Fix Released Status in gnome-shell package in Ubuntu: Invalid Status in gdm3 source package in Bionic: Fix Committed Status in gnome-shell source package in Bionic: Invalid Bug description: [ Description ] Due to a refcounting bug, a GDBusConnection was getting disposed when it was still required. The symptom of this was that you couldn't log in if you'd got your password wrong. [ Test case ] 1. Boot to GDM 2. Click your username 3. Type the wrong password a couple of times, pressing enter after each time 4. Type the right password If the bug is happening, after 4. the system hangs at a blank screen with the mouse cursor. If you then switch to a VT or otherwise connect to the machine, you can examine the journal and you'll see a G_IS_DBUS_CONNECTION failure. [ Fix ] Marco and I worked upstream on this fix. We found out that there was a problem like this- The GdmClient has a shared GDBusConnection for its operations. The first time someone calls for it, it is created and stored in the object's private structure. Subsequent calls return *a new reference* to this same object. It turned out that the asynchronous method to get the connection was accidentally unreferencing its object before giving it to the caller if it was returning an already-existing connection. For this to work properly, we need to nullify the pointer we stored when the connection goes away, so we know when to make a new one. There were some cases where we didn't add the weak references required to do that. Those are also fixed. [ Regression potential ] Now we share connections more than we did before. We also more carefully track when to clear our object. If we got this wrong, we might end up leaking the connection or dropping it in even more cases. [ Original report ] WORKAROUND: After typing an incorrect password, click Cancel, then click your name, then enter your password again. --- Trying to log into my session (Gnome, Xorg), if I enter the wrong password before entering it correctly, the session doesn't load and I get a purple screen, a mouse cursor, and an invisible but clickable menu in the top right. If I enter it correctly the first time, there is no problem. I've replicated this from a fresh boot, after logging out and after 'sudo service gdm restart' from the Ctrl-Alt-F4 console. This is a fresh install, and didn't occur when I was using a previous install of 18.04 (until Friday). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Apr 22 20:31:13 2018 InstallationDate: Installed on 2018-04-22 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180421.1) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1766137/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1766137] Re: [regression] Password accepted but login fails (blank purple screen and mouse pointer only)
I installed proposed updates. Now it freeze a bit earlier and even more often. Login screen remain visible and no cursor movement while before in looked like progressing with blank screen with cursor movement until final freeze. pe 18. toukok. 2018 klo 19.20 KenWilson (1766...@bugs.launchpad.net) kirjoitti: > Brian, > I attempted to install the proposed package: 3.28.0-0ubuntu1.1 but it > failed. Initially I thought it installed correct but when switching users I > got a notification of a timeout and a package not installed. In the process > of looking at the notification it went away and I don't know how to get it > back. I have included the dpkg log below. I have reverted back to the > standard release and things are working as they were. > > NOTE: the install could be operator error. > > DPKG Log > 2018-05-18 07:53:27 startup archives unpack > 2018-05-18 07:53:38 upgrade gdm3:amd64 3.28.0-0ubuntu1 3.28.0-0ubuntu1.1 > 2018-05-18 07:53:38 status half-configured gdm3:amd64 3.28.0-0ubuntu1 > 2018-05-18 07:53:38 status unpacked gdm3:amd64 3.28.0-0ubuntu1 > 2018-05-18 07:53:38 status half-installed gdm3:amd64 3.28.0-0ubuntu1 > 2018-05-18 07:53:38 status triggers-pending dbus:amd64 1.12.2-1ubuntu1 > 2018-05-18 07:53:38 status triggers-pending systemd:amd64 237-3ubuntu10 > 2018-05-18 07:53:38 status triggers-pending ureadahead:amd64 0.100.0-20 > 2018-05-18 07:53:39 status triggers-pending hicolor-icon-theme:all 0.17-2 > 2018-05-18 07:53:40 status triggers-pending man-db:amd64 2.8.3-2 > 2018-05-18 07:53:40 status half-installed gdm3:amd64 3.28.0-0ubuntu1 > 2018-05-18 07:53:40 status unpacked gdm3:amd64 3.28.0-0ubuntu1.1 > 2018-05-18 07:53:40 status unpacked gdm3:amd64 3.28.0-0ubuntu1.1 > 2018-05-18 07:53:41 upgrade libgdm1:amd64 3.28.0-0ubuntu1 3.28.0-0ubuntu1.1 > 2018-05-18 07:53:41 status triggers-pending libc-bin:amd64 2.27-3ubuntu1 > 2018-05-18 07:53:41 status half-configured libgdm1:amd64 3.28.0-0ubuntu1 > 2018-05-18 07:53:41 status unpacked libgdm1:amd64 3.28.0-0ubuntu1 > 2018-05-18 07:53:41 status half-installed libgdm1:amd64 3.28.0-0ubuntu1 > 2018-05-18 07:53:41 status triggers-pending libglib2.0-0:amd64 > 2.56.1-2ubuntu1 > 2018-05-18 07:53:41 status half-installed libgdm1:amd64 3.28.0-0ubuntu1 > 2018-05-18 07:53:41 status triggers-pending libglib2.0-0:i386 > 2.56.1-2ubuntu1 > 2018-05-18 07:53:41 status half-installed libgdm1:amd64 3.28.0-0ubuntu1 > 2018-05-18 07:53:42 status half-installed libgdm1:amd64 3.28.0-0ubuntu1 > 2018-05-18 07:53:42 status unpacked libgdm1:amd64 3.28.0-0ubuntu1.1 > 2018-05-18 07:53:42 status unpacked libgdm1:amd64 3.28.0-0ubuntu1.1 > 2018-05-18 07:53:42 upgrade gir1.2-gdm-1.0:amd64 3.28.0-0ubuntu1 > 3.28.0-0ubuntu1.1 > 2018-05-18 07:53:42 status half-configured gir1.2-gdm-1.0:amd64 > 3.28.0-0ubuntu1 > 2018-05-18 07:53:42 status unpacked gir1.2-gdm-1.0:amd64 3.28.0-0ubuntu1 > 2018-05-18 07:53:42 status half-installed gir1.2-gdm-1.0:amd64 > 3.28.0-0ubuntu1 > 2018-05-18 07:53:43 status half-installed gir1.2-gdm-1.0:amd64 > 3.28.0-0ubuntu1 > 2018-05-18 07:53:43 status unpacked gir1.2-gdm-1.0:amd64 3.28.0-0ubuntu1.1 > 2018-05-18 07:53:43 status unpacked gir1.2-gdm-1.0:amd64 3.28.0-0ubuntu1.1 > 2018-05-18 07:53:43 startup packages configure > 2018-05-18 07:53:43 trigproc ureadahead:amd64 0.100.0-20 > 2018-05-18 07:53:43 status half-configured ureadahead:amd64 0.100.0-20 > 2018-05-18 07:53:44 status installed ureadahead:amd64 0.100.0-20 > 2018-05-18 07:53:44 trigproc libglib2.0-0:amd64 2.56.1-2ubuntu1 > 2018-05-18 07:53:44 status half-configured libglib2.0-0:amd64 > 2.56.1-2ubuntu1 > 2018-05-18 07:53:46 status installed libglib2.0-0:amd64 2.56.1-2ubuntu1 > 2018-05-18 07:53:46 trigproc libglib2.0-0:i386 2.56.1-2ubuntu1 > 2018-05-18 07:53:46 status half-configured libglib2.0-0:i386 > 2.56.1-2ubuntu1 > 2018-05-18 07:53:47 status installed libglib2.0-0:i386 2.56.1-2ubuntu1 > 2018-05-18 07:53:47 configure libgdm1:amd64 3.28.0-0ubuntu1.1 > 2018-05-18 07:53:47 status unpacked libgdm1:amd64 3.28.0-0ubuntu1.1 > 2018-05-18 07:53:47 status half-configured libgdm1:amd64 3.28.0-0ubuntu1.1 > 2018-05-18 07:53:47 status installed libgdm1:amd64 3.28.0-0ubuntu1.1 > 2018-05-18 07:53:48 trigproc libc-bin:amd64 2.27-3ubuntu1 > 2018-05-18 07:53:48 status half-configured libc-bin:amd64 2.27-3ubuntu1 > 2018-05-18 07:53:48 status installed libc-bin:amd64 2.27-3ubuntu1 > 2018-05-18 07:53:48 trigproc systemd:amd64 237-3ubuntu10 > 2018-05-18 07:53:48 status half-configured systemd:amd64 237-3ubuntu10 > 2018-05-18 07:53:51 status installed systemd:amd64 237-3ubuntu10 > 2018-05-18 07:53:51 trigproc man-db:amd64 2.8.3-2 > 2018-05-18 07:53:51 status half-configured man-db:amd64 2.8.3-2 > 2018-05-18 07:53:54 status installed man-db:amd64 2.8.3-2 > 2018-05-18 07:53:54 trigproc dbus:amd64 1.12.2-1ubuntu1 > 2018-05-18 07:53:54 status half-configured dbus:amd64 1.12.2-1ubuntu1 > 2018-05-18 07:53:54 status installed dbus:amd64 1.12.2-1ubuntu1 > 2018-05-18 07:53:54 trigproc hicolor-icon-theme:all 0.17-2 >
[Desktop-packages] [Bug 1772067] [NEW] on-screen keyboard layout is wrong and cannot change
Public bug reported: What's wrong : The onscreen keyboard layout is set to qwerty even if another layout was selected during install. It is not possible to change the on-screen keyboard layout How to reproduce : on login screen, select user, enable the on-screen keyboard (osk), click on the password box, osk appears. It is in qwerty. Click on Flag, the flag popup appears with the registered layouts, raise the mouse towards the list : the on-screen keyboard disappears too soon to allow clicking. Get used to the on-screen keyboard layout and get fast, Click on Flag, click quickly on the popup to the desired layout : Nothing happens, keyboard layout remains the same. Version : 1.4.1-2ubuntu1 Information : I have two layouts in /etc/default/keyboard, none is in qwerty ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1772067 Title: on-screen keyboard layout is wrong and cannot change Status in gdm3 package in Ubuntu: New Bug description: What's wrong : The onscreen keyboard layout is set to qwerty even if another layout was selected during install. It is not possible to change the on-screen keyboard layout How to reproduce : on login screen, select user, enable the on-screen keyboard (osk), click on the password box, osk appears. It is in qwerty. Click on Flag, the flag popup appears with the registered layouts, raise the mouse towards the list : the on-screen keyboard disappears too soon to allow clicking. Get used to the on-screen keyboard layout and get fast, Click on Flag, click quickly on the popup to the desired layout : Nothing happens, keyboard layout remains the same. Version : 1.4.1-2ubuntu1 Information : I have two layouts in /etc/default/keyboard, none is in qwerty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1772067/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1772032] Re: [snap /from-source] broken launcher
Thanks for the report Ads2. I can confirm the issue, and am working on a fix. ** Changed in: chromium-browser (Ubuntu) Status: New => Confirmed ** Changed in: chromium-browser (Ubuntu) Importance: Undecided => High ** Changed in: chromium-browser (Ubuntu) Assignee: (unassigned) => Olivier Tilloy (osomon) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1772032 Title: [snap /from-source] broken launcher Status in chromium-browser package in Ubuntu: Confirmed Bug description: Ran `snap install chromium --channel=candidate/from-source` as suggested in https://community.ubuntu.com/t/intent-to-provide- chromium-as-a-snap-only/5987 and I think it broke my launcher (from searching for Chromium in Activities). Clicking on it produces the notification: Failed to launch "Chromium Web Browser" Desktop file didn't specify exec field Also the launcher has no icon (only the plain executable one) ``` $ snap info chromium tracking: candidate/from-source refreshed: 2018-05-16T22:04:26+01:00 installed: 66.0.3359.181 (331) 238MB - $ snap version snap2.32.8+18.04 snapd 2.32.8+18.04 series 16 ubuntu 18.04 kernel 4.15.0-20-generic $ snap info core tracking: beta refreshed: 2018-05-11T15:51:12+01:00 installed: 16-2.32.8(4650) 90MB core ``` ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: chromium-browser (not installed) ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: communitheme:ubuntu:GNOME Date: Fri May 18 14:09:37 2018 InstallationDate: Installed on 2017-08-03 (287 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: chromium-browser UpgradeStatus: Upgraded to bionic on 2018-04-22 (26 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1772032/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1762952] Re: Alternative shortcut for layout switching Alt+Shift unexpectedly set by default
Thanks for your patch Gunnar! For now I only had a quick look the changes, was wondering why the debian/control and debian/rules changes were needed for the PPA upload. It didn't build without those? I would expect it to not really differ from what would happen in the archive. Also, from the glimpse I had I saw you were doing `dpkg --compare- versions "$2" lt-nl "$PKGVERSION"` in the postinst - was is the reason for that? I might be missing context, but isn't it enough to just check for "$1" = "upgrade" to see if we're upgrading? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1762952 Title: Alternative shortcut for layout switching Alt+Shift unexpectedly set by default Status in console-setup package in Ubuntu: In Progress Status in gnome-control-center package in Ubuntu: Confirmed Bug description: Version: Ubuntu 18.04 Final Beta with default Gnome Shell included in 18.04 Steps to reproduce: 1. Define two keyboard input methods in Settings -> Region & Language -> Input Sources 2. Open several applications 3. Observe that application windows can be iterated with Alt + Tab 4. Once application window iteration was begun with Alt + Tab, try to iterate backwards with Alt + Shift + Tab. 5. Try to change keyboard input method switching hotkeys in Settings -> Region & Language -> Input Sources -> Options. 6. Observe that Keyboard shortcut for "Alternative switch to next source" is set to "Alt + Shift" and that keyboard shortcuts can only be changed in Settings -> Devices -> Keyboard -> Keyboard Shortcuts. 7. Observe that the shortcut for "Alternative switch to next source" is not available for configuration in Settings -> Devices -> Keyboard -> Keyboard Shortcuts. Actual state: * Performing step 4 does not select the previous app in application switcher but instead changes keyboard input method. Expected state: * The shortcut for "Alternative switch to next source" can be changed and / or deactivated in Settings -> Devices -> Keyboard -> Keyboard Shortcuts. Notes: * The above was working fine in Ubuntu 17.10. I assume "Alternative switch to next source" did not exist in that version of Gnome Shell. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1762952/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1766137] Re: [regression] Password accepted but login fails (blank purple screen and mouse pointer only)
Brian, I attempted to install the proposed package: 3.28.0-0ubuntu1.1 but it failed. Initially I thought it installed correct but when switching users I got a notification of a timeout and a package not installed. In the process of looking at the notification it went away and I don't know how to get it back. I have included the dpkg log below. I have reverted back to the standard release and things are working as they were. NOTE: the install could be operator error. DPKG Log 2018-05-18 07:53:27 startup archives unpack 2018-05-18 07:53:38 upgrade gdm3:amd64 3.28.0-0ubuntu1 3.28.0-0ubuntu1.1 2018-05-18 07:53:38 status half-configured gdm3:amd64 3.28.0-0ubuntu1 2018-05-18 07:53:38 status unpacked gdm3:amd64 3.28.0-0ubuntu1 2018-05-18 07:53:38 status half-installed gdm3:amd64 3.28.0-0ubuntu1 2018-05-18 07:53:38 status triggers-pending dbus:amd64 1.12.2-1ubuntu1 2018-05-18 07:53:38 status triggers-pending systemd:amd64 237-3ubuntu10 2018-05-18 07:53:38 status triggers-pending ureadahead:amd64 0.100.0-20 2018-05-18 07:53:39 status triggers-pending hicolor-icon-theme:all 0.17-2 2018-05-18 07:53:40 status triggers-pending man-db:amd64 2.8.3-2 2018-05-18 07:53:40 status half-installed gdm3:amd64 3.28.0-0ubuntu1 2018-05-18 07:53:40 status unpacked gdm3:amd64 3.28.0-0ubuntu1.1 2018-05-18 07:53:40 status unpacked gdm3:amd64 3.28.0-0ubuntu1.1 2018-05-18 07:53:41 upgrade libgdm1:amd64 3.28.0-0ubuntu1 3.28.0-0ubuntu1.1 2018-05-18 07:53:41 status triggers-pending libc-bin:amd64 2.27-3ubuntu1 2018-05-18 07:53:41 status half-configured libgdm1:amd64 3.28.0-0ubuntu1 2018-05-18 07:53:41 status unpacked libgdm1:amd64 3.28.0-0ubuntu1 2018-05-18 07:53:41 status half-installed libgdm1:amd64 3.28.0-0ubuntu1 2018-05-18 07:53:41 status triggers-pending libglib2.0-0:amd64 2.56.1-2ubuntu1 2018-05-18 07:53:41 status half-installed libgdm1:amd64 3.28.0-0ubuntu1 2018-05-18 07:53:41 status triggers-pending libglib2.0-0:i386 2.56.1-2ubuntu1 2018-05-18 07:53:41 status half-installed libgdm1:amd64 3.28.0-0ubuntu1 2018-05-18 07:53:42 status half-installed libgdm1:amd64 3.28.0-0ubuntu1 2018-05-18 07:53:42 status unpacked libgdm1:amd64 3.28.0-0ubuntu1.1 2018-05-18 07:53:42 status unpacked libgdm1:amd64 3.28.0-0ubuntu1.1 2018-05-18 07:53:42 upgrade gir1.2-gdm-1.0:amd64 3.28.0-0ubuntu1 3.28.0-0ubuntu1.1 2018-05-18 07:53:42 status half-configured gir1.2-gdm-1.0:amd64 3.28.0-0ubuntu1 2018-05-18 07:53:42 status unpacked gir1.2-gdm-1.0:amd64 3.28.0-0ubuntu1 2018-05-18 07:53:42 status half-installed gir1.2-gdm-1.0:amd64 3.28.0-0ubuntu1 2018-05-18 07:53:43 status half-installed gir1.2-gdm-1.0:amd64 3.28.0-0ubuntu1 2018-05-18 07:53:43 status unpacked gir1.2-gdm-1.0:amd64 3.28.0-0ubuntu1.1 2018-05-18 07:53:43 status unpacked gir1.2-gdm-1.0:amd64 3.28.0-0ubuntu1.1 2018-05-18 07:53:43 startup packages configure 2018-05-18 07:53:43 trigproc ureadahead:amd64 0.100.0-20 2018-05-18 07:53:43 status half-configured ureadahead:amd64 0.100.0-20 2018-05-18 07:53:44 status installed ureadahead:amd64 0.100.0-20 2018-05-18 07:53:44 trigproc libglib2.0-0:amd64 2.56.1-2ubuntu1 2018-05-18 07:53:44 status half-configured libglib2.0-0:amd64 2.56.1-2ubuntu1 2018-05-18 07:53:46 status installed libglib2.0-0:amd64 2.56.1-2ubuntu1 2018-05-18 07:53:46 trigproc libglib2.0-0:i386 2.56.1-2ubuntu1 2018-05-18 07:53:46 status half-configured libglib2.0-0:i386 2.56.1-2ubuntu1 2018-05-18 07:53:47 status installed libglib2.0-0:i386 2.56.1-2ubuntu1 2018-05-18 07:53:47 configure libgdm1:amd64 3.28.0-0ubuntu1.1 2018-05-18 07:53:47 status unpacked libgdm1:amd64 3.28.0-0ubuntu1.1 2018-05-18 07:53:47 status half-configured libgdm1:amd64 3.28.0-0ubuntu1.1 2018-05-18 07:53:47 status installed libgdm1:amd64 3.28.0-0ubuntu1.1 2018-05-18 07:53:48 trigproc libc-bin:amd64 2.27-3ubuntu1 2018-05-18 07:53:48 status half-configured libc-bin:amd64 2.27-3ubuntu1 2018-05-18 07:53:48 status installed libc-bin:amd64 2.27-3ubuntu1 2018-05-18 07:53:48 trigproc systemd:amd64 237-3ubuntu10 2018-05-18 07:53:48 status half-configured systemd:amd64 237-3ubuntu10 2018-05-18 07:53:51 status installed systemd:amd64 237-3ubuntu10 2018-05-18 07:53:51 trigproc man-db:amd64 2.8.3-2 2018-05-18 07:53:51 status half-configured man-db:amd64 2.8.3-2 2018-05-18 07:53:54 status installed man-db:amd64 2.8.3-2 2018-05-18 07:53:54 trigproc dbus:amd64 1.12.2-1ubuntu1 2018-05-18 07:53:54 status half-configured dbus:amd64 1.12.2-1ubuntu1 2018-05-18 07:53:54 status installed dbus:amd64 1.12.2-1ubuntu1 2018-05-18 07:53:54 trigproc hicolor-icon-theme:all 0.17-2 2018-05-18 07:53:54 status half-configured hicolor-icon-theme:all 0.17-2 2018-05-18 07:53:55 status installed hicolor-icon-theme:all 0.17-2 2018-05-18 07:53:55 configure gir1.2-gdm-1.0:amd64 3.28.0-0ubuntu1.1 2018-05-18 07:53:55 status unpacked gir1.2-gdm-1.0:amd64 3.28.0-0ubuntu1.1 2018-05-18 07:53:55 status half-configured gir1.2-gdm-1.0:amd64 3.28.0-0ubuntu1.1 2018-05-18 07:53:55 status installed gir1.2-gdm-1.0:amd64 3.28.0-0ubuntu1.1 2018-05-18 07:53:55
[Desktop-packages] [Bug 1766137] Re: [regression] Password accepted but login fails (blank purple screen and mouse pointer only)
I could not reproduce what Davide (tarski10) did. I enter the wrong password three times I return to the user choice screen and after clicking on my username and entering the correct password I could successfully login. -- 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/1766137 Title: [regression] Password accepted but login fails (blank purple screen and mouse pointer only) Status in gdm: Fix Released Status in Release Notes for Ubuntu: Fix Released Status in gdm3 package in Ubuntu: Fix Released Status in gnome-shell package in Ubuntu: Invalid Status in gdm3 source package in Bionic: Fix Committed Status in gnome-shell source package in Bionic: Invalid Bug description: [ Description ] Due to a refcounting bug, a GDBusConnection was getting disposed when it was still required. The symptom of this was that you couldn't log in if you'd got your password wrong. [ Test case ] 1. Boot to GDM 2. Click your username 3. Type the wrong password a couple of times, pressing enter after each time 4. Type the right password If the bug is happening, after 4. the system hangs at a blank screen with the mouse cursor. If you then switch to a VT or otherwise connect to the machine, you can examine the journal and you'll see a G_IS_DBUS_CONNECTION failure. [ Fix ] Marco and I worked upstream on this fix. We found out that there was a problem like this- The GdmClient has a shared GDBusConnection for its operations. The first time someone calls for it, it is created and stored in the object's private structure. Subsequent calls return *a new reference* to this same object. It turned out that the asynchronous method to get the connection was accidentally unreferencing its object before giving it to the caller if it was returning an already-existing connection. For this to work properly, we need to nullify the pointer we stored when the connection goes away, so we know when to make a new one. There were some cases where we didn't add the weak references required to do that. Those are also fixed. [ Regression potential ] Now we share connections more than we did before. We also more carefully track when to clear our object. If we got this wrong, we might end up leaking the connection or dropping it in even more cases. [ Original report ] WORKAROUND: After typing an incorrect password, click Cancel, then click your name, then enter your password again. --- Trying to log into my session (Gnome, Xorg), if I enter the wrong password before entering it correctly, the session doesn't load and I get a purple screen, a mouse cursor, and an invisible but clickable menu in the top right. If I enter it correctly the first time, there is no problem. I've replicated this from a fresh boot, after logging out and after 'sudo service gdm restart' from the Ctrl-Alt-F4 console. This is a fresh install, and didn't occur when I was using a previous install of 18.04 (until Friday). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Apr 22 20:31:13 2018 InstallationDate: Installed on 2018-04-22 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180421.1) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1766137/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1772056] Re: Snap Store Authentication always fails
Sorry, forgot to mention, this is on a brand new install of Ubuntu 18.04. Using I3 as window manager. -- 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/1772056 Title: Snap Store Authentication always fails Status in gnome-software package in Ubuntu: New Bug description: Trying to install "Visual Studio Code" get a dialog to Authenticate: "To continue you need to sign in to Snap Store." I have tried an old login, reset passsword, no luck. Registered new user, same deal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1772056/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1772056] [NEW] Snap Store Authentication always fails
Public bug reported: Trying to install "Visual Studio Code" get a dialog to Authenticate: "To continue you need to sign in to Snap Store." I have tried an old login, reset passsword, no luck. Registered new user, same deal. ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Screenshot from 2018-05-18 08-43-09.png" https://bugs.launchpad.net/bugs/1772056/+attachment/5141286/+files/Screenshot%20from%202018-05-18%2008-43-09.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1772056 Title: Snap Store Authentication always fails Status in gnome-software package in Ubuntu: New Bug description: Trying to install "Visual Studio Code" get a dialog to Authenticate: "To continue you need to sign in to Snap Store." I have tried an old login, reset passsword, no luck. Registered new user, same deal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1772056/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1756619] Re: nautilus-actions package missing in Ubuntu 18.04 beta
This bug should be invalid because currently nautilus-actions was renamed to filemanager-actions, And this is https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1768597 valid bug. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1756619 Title: nautilus-actions package missing in Ubuntu 18.04 beta Status in gedit package in Ubuntu: Invalid Status in nautilus-actions package in Ubuntu: Confirmed Bug description: *** Please change this bug from gedit to the correct package. *** Synaptic no longer offers package nautilus-actions for installation. This package is required for right click custom actions in file manager and the desktop. Please reinstate. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gedit 3.28.0-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Mar 17 19:39:57 2018 InstallationDate: Installed on 2018-03-10 (7 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180310) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1756619/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1761844] Re: Very large emojis displayed in subject line and in the email list
Its true, a very easy workaround is to install the fonts-symbola package: sudo apt-get install fonts-symbola Afterwards, all works fine. +1 to the suggestion of bugrasan, to just add a dependency to the fonts- symbola package (looks better anyways) -- 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/1761844 Title: Very large emojis displayed in subject line and in the email list Status in Mozilla Thunderbird: Invalid Status in thunderbird package in Ubuntu: Confirmed Bug description: The list of emails received from Thunderbird shows emojis. This does not happen with all accounts. It appears to be with the last email address added. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: thunderbird 1:52.6.0+build1-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia AddonCompatCheckDisabled: False ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: diego 1607 F...m pulseaudio /dev/snd/controlC0: diego 1607 F pulseaudio /dev/snd/controlC1: diego 1607 F pulseaudio BuildID: 20180131200234 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Fri Apr 6 15:58:17 2018 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2018-04-05 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) IpRoute: default via 181.31.1.1 dev enp2s0 proto dhcp metric 100 169.254.0.0/16 dev enp2s0 scope link metric 1000 181.31.1.0/24 dev enp2s0 proto kernel scope link src 181.31.1.84 metric 100 IwConfig: lono wireless extensions. enp2s0no wireless extensions. Locales: extensions.sqlite corrupt or missing PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=52.6.0/20180131200234 (In use) RfKill: RunningIncompatibleAddons: False SourcePackage: thunderbird Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/14/2012 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F4 dmi.board.name: GA-78LMT-S2 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF4:bd08/14/2012:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-S2:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-S2:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-78LMT-S2 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1761844/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1731081] Re: Natural Scroll Does Not Work in Ubuntu X.org on 17.10
** Package changed: desktop-base (Ubuntu) => gnome-settings-daemon (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1731081 Title: Natural Scroll Does Not Work in Ubuntu X.org on 17.10 Status in gnome-settings-daemon package in Ubuntu: New Bug description: When logged in using the "Ubuntu X.org" desktop, scrolling is always unnatural regardless of the setting in System Settings or dconf. It works as expected with "Ubuntu" or "Unity" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1731081/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1772032] Re: [snap candidate/from-source] broken launcher
** Summary changed: - [snap] Refresh to chromium/from-source broke launcher + [snap candidate/from-source] broken launcher ** Summary changed: - [snap candidate/from-source] broken launcher + [snap /from-source] broken launcher -- 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/1772032 Title: [snap /from-source] broken launcher Status in chromium-browser package in Ubuntu: New Bug description: Ran `snap install chromium --channel=candidate/from-source` as suggested in https://community.ubuntu.com/t/intent-to-provide- chromium-as-a-snap-only/5987 and I think it broke my launcher (from searching for Chromium in Activities). Clicking on it produces the notification: Failed to launch "Chromium Web Browser" Desktop file didn't specify exec field Also the launcher has no icon (only the plain executable one) ``` $ snap info chromium tracking: candidate/from-source refreshed: 2018-05-16T22:04:26+01:00 installed: 66.0.3359.181 (331) 238MB - $ snap version snap2.32.8+18.04 snapd 2.32.8+18.04 series 16 ubuntu 18.04 kernel 4.15.0-20-generic $ snap info core tracking: beta refreshed: 2018-05-11T15:51:12+01:00 installed: 16-2.32.8(4650) 90MB core ``` ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: chromium-browser (not installed) ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: communitheme:ubuntu:GNOME Date: Fri May 18 14:09:37 2018 InstallationDate: Installed on 2017-08-03 (287 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: chromium-browser UpgradeStatus: Upgraded to bionic on 2018-04-22 (26 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1772032/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1731081] [NEW] Natural Scroll Does Not Work in Ubuntu X.org on 17.10
You have been subscribed to a public bug: When logged in using the "Ubuntu X.org" desktop, scrolling is always unnatural regardless of the setting in System Settings or dconf. It works as expected with "Ubuntu" or "Unity" ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New ** Tags: artful -- Natural Scroll Does Not Work in Ubuntu X.org on 17.10 https://bugs.launchpad.net/bugs/1731081 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon 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 1768597] Re: package filemanager-actions missing
You can use this as base package https://github.com/Daniel-Marynicz /filemanager-actions-debian-packging For debian/ubuntu packing. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1768597 Title: package filemanager-actions missing Status in nautilus package in Ubuntu: Confirmed Bug description: nautilus-actions was deprecated in favour of filemanager-actions (see https://github.com/GNOME/nautilus-actions ). But 18.04 repositories do not have either of the packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1768597/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1772032] Re: [snap] Refresh to chromium/from-source broke launcher
Ran `snap refresh chromium --stable` and the launcher is fine, so this is a bug in /from-source alone. -- 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/1772032 Title: [snap] Refresh to chromium/from-source broke launcher Status in chromium-browser package in Ubuntu: New Bug description: Ran `snap install chromium --channel=candidate/from-source` as suggested in https://community.ubuntu.com/t/intent-to-provide- chromium-as-a-snap-only/5987 and I think it broke my launcher (from searching for Chromium in Activities). Clicking on it produces the notification: Failed to launch "Chromium Web Browser" Desktop file didn't specify exec field Also the launcher has no icon (only the plain executable one) ``` $ snap info chromium tracking: candidate/from-source refreshed: 2018-05-16T22:04:26+01:00 installed: 66.0.3359.181 (331) 238MB - $ snap version snap2.32.8+18.04 snapd 2.32.8+18.04 series 16 ubuntu 18.04 kernel 4.15.0-20-generic $ snap info core tracking: beta refreshed: 2018-05-11T15:51:12+01:00 installed: 16-2.32.8(4650) 90MB core ``` ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: chromium-browser (not installed) ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: communitheme:ubuntu:GNOME Date: Fri May 18 14:09:37 2018 InstallationDate: Installed on 2017-08-03 (287 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: chromium-browser UpgradeStatus: Upgraded to bionic on 2018-04-22 (26 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1772032/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1772032] [NEW] [snap] Refresh to chromium/from-source broke launcher
Public bug reported: Ran `snap install chromium --channel=candidate/from-source` as suggested in https://community.ubuntu.com/t/intent-to-provide-chromium-as-a-snap- only/5987 and I think it broke my launcher (from searching for Chromium in Activities). Clicking on it produces the notification: Failed to launch "Chromium Web Browser" Desktop file didn't specify exec field Also the launcher has no icon (only the plain executable one) ``` $ snap info chromium tracking: candidate/from-source refreshed: 2018-05-16T22:04:26+01:00 installed: 66.0.3359.181 (331) 238MB - $ snap version snap2.32.8+18.04 snapd 2.32.8+18.04 series 16 ubuntu 18.04 kernel 4.15.0-20-generic $ snap info core tracking: beta refreshed: 2018-05-11T15:51:12+01:00 installed: 16-2.32.8(4650) 90MB core ``` ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: chromium-browser (not installed) ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: communitheme:ubuntu:GNOME Date: Fri May 18 14:09:37 2018 InstallationDate: Installed on 2017-08-03 (287 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: chromium-browser UpgradeStatus: Upgraded to bionic on 2018-04-22 (26 days ago) ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic snap wayland-session ** Summary changed: - Refresh to chromium/from-source broke desktop launcher + [snap] Refresh to chromium/from-source broke desktop launcher ** Summary changed: - [snap] Refresh to chromium/from-source broke desktop launcher + [snap] Refresh to chromium/from-source broke launcher ** Description changed: Ran `snap install chromium --channel=candidate/from-source` as suggested in https://community.ubuntu.com/t/intent-to-provide-chromium-as-a-snap- only/5987 and I think it broke my launcher (from searching for Chromium in Activities). Clicking on it produces the notification: Failed to launch "Chromium Web Browser" Desktop file didn't specify exec field + + Also the launcher has no icon (only the plain executable one) ``` $ snap info chromium tracking: candidate/from-source refreshed: 2018-05-16T22:04:26+01:00 installed: 66.0.3359.181 (331) 238MB - $ snap version snap2.32.8+18.04 snapd 2.32.8+18.04 series 16 ubuntu 18.04 kernel 4.15.0-20-generic $ snap info core tracking: beta refreshed: 2018-05-11T15:51:12+01:00 installed: 16-2.32.8(4650) 90MB core ``` ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: chromium-browser (not installed) ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: communitheme:ubuntu:GNOME Date: Fri May 18 14:09:37 2018 InstallationDate: Installed on 2017-08-03 (287 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: chromium-browser UpgradeStatus: Upgraded to bionic on 2018-04-22 (26 days ago) -- 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/1772032 Title: [snap] Refresh to chromium/from-source broke launcher Status in chromium-browser package in Ubuntu: New Bug description: Ran `snap install chromium --channel=candidate/from-source` as suggested in https://community.ubuntu.com/t/intent-to-provide- chromium-as-a-snap-only/5987 and I think it broke my launcher (from searching for Chromium in Activities). Clicking on it produces the notification: Failed to launch "Chromium Web Browser" Desktop file didn't specify exec field Also the launcher has no icon (only the plain executable one) ``` $ snap info chromium tracking: candidate/from-source refreshed: 2018-05-16T22:04:26+01:00 installed: 66.0.3359.181 (331) 238MB - $ snap version snap2.32.8+18.04 snapd 2.32.8+18.04 series 16 ubuntu 18.04 kernel 4.15.0-20-generic $ snap info core tracking: beta refreshed: 2018-05-11T15:51:12+01:00 installed: 16-2.32.8(4650) 90MB core ``` ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: chromium-browser (not installed) ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: communitheme:ubuntu:GNOME Date: Fri May 18 14:09:37 2018 InstallationDate: Installed on 2017-08-03 (287 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: chromium-browser UpgradeStatus: Upgraded to bionic on 2018-04-22 (26 days ago) To manage notifications about this bug go to:
[Desktop-packages] [Bug 1765914] Re: Java windows and fonts are huge running in openjdk-11-jre
** Also affects: unity-settings-daemon (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1765914 Title: Java windows and fonts are huge running in openjdk-11-jre Status in openjdk-lts package in Ubuntu: New Status in unity-settings-daemon package in Ubuntu: New Bug description: If I run a Java application with oracle-java-8 in an X session, the windows and fonts are all normal size. When I run the same application with openjdk-11-jre, everything is scaled up to double size (see attached image, which shows an application on the left running in Java 8 and the same application on the right running in Java 10 (from the package openjdk-11, not openjdk-10 for some reason). My normal screen layout is 1920x1080 with two screens, so the command "xrandr -q | awk -F'current' -F',' 'NR==1 {gsub("( |current)","");print $2}'" shows 1920x2160. One of the screens is 4K, so presumably Java *might* be detecting this and deciding it needs to double everything in size, but this is clearly an error since I'm not even using this mode. If I set the laptop to use a single external 1920x1080 monitor, it makes no difference - the Java applications are still double the size that they should be. There's no problem if I run in a Wayland session - the app windows run at a normal size whether in java 10 or 8. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: openjdk-11-jre 10.0.1+10-1ubuntu2 Uname: Linux 4.17.0-041700rc1-generic x86_64 ApportVersion: 2.20.9-0ubuntu6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 21 14:12:39 2018 InstallationDate: Installed on 2017-08-16 (247 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: openjdk-lts UpgradeStatus: Upgraded to bionic on 2017-11-17 (154 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openjdk-lts/+bug/1765914/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1772023] [NEW] Mobile broadband has IPv6 disabled by default
Public bug reported: To fix this, I had to go to "Mobile broadband settings", click the gearwheel icon, spot the "IPv6 settings" tab and change Method from Ignore to Automatic. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: modemmanager 1.6.8-2ubuntu1 Uname: Linux 4.16.7-041607-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri May 18 16:34:25 2018 InstallationDate: Installed on 2018-04-25 (22 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) SourcePackage: modemmanager UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: modemmanager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1772023 Title: Mobile broadband has IPv6 disabled by default Status in modemmanager package in Ubuntu: New Bug description: To fix this, I had to go to "Mobile broadband settings", click the gearwheel icon, spot the "IPv6 settings" tab and change Method from Ignore to Automatic. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: modemmanager 1.6.8-2ubuntu1 Uname: Linux 4.16.7-041607-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri May 18 16:34:25 2018 InstallationDate: Installed on 2018-04-25 (22 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) SourcePackage: modemmanager UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1772023/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1766137] Re: [regression] Password accepted but login fails (blank purple screen and mouse pointer only)
gdm3/ 3.28.0-0-0ubuntu1.1 if I enter the wrong password once or twice and then I enter the correct password now I can access, but if I enter the wrong password three times I return to the user choice screen and after clicking on my username and entering the correct password the screen freezes and nothing happens. I can still shutdown or restart. -- 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/1766137 Title: [regression] Password accepted but login fails (blank purple screen and mouse pointer only) Status in gdm: Fix Released Status in Release Notes for Ubuntu: Fix Released Status in gdm3 package in Ubuntu: Fix Released Status in gnome-shell package in Ubuntu: Invalid Status in gdm3 source package in Bionic: Fix Committed Status in gnome-shell source package in Bionic: Invalid Bug description: [ Description ] Due to a refcounting bug, a GDBusConnection was getting disposed when it was still required. The symptom of this was that you couldn't log in if you'd got your password wrong. [ Test case ] 1. Boot to GDM 2. Click your username 3. Type the wrong password a couple of times, pressing enter after each time 4. Type the right password If the bug is happening, after 4. the system hangs at a blank screen with the mouse cursor. If you then switch to a VT or otherwise connect to the machine, you can examine the journal and you'll see a G_IS_DBUS_CONNECTION failure. [ Fix ] Marco and I worked upstream on this fix. We found out that there was a problem like this- The GdmClient has a shared GDBusConnection for its operations. The first time someone calls for it, it is created and stored in the object's private structure. Subsequent calls return *a new reference* to this same object. It turned out that the asynchronous method to get the connection was accidentally unreferencing its object before giving it to the caller if it was returning an already-existing connection. For this to work properly, we need to nullify the pointer we stored when the connection goes away, so we know when to make a new one. There were some cases where we didn't add the weak references required to do that. Those are also fixed. [ Regression potential ] Now we share connections more than we did before. We also more carefully track when to clear our object. If we got this wrong, we might end up leaking the connection or dropping it in even more cases. [ Original report ] WORKAROUND: After typing an incorrect password, click Cancel, then click your name, then enter your password again. --- Trying to log into my session (Gnome, Xorg), if I enter the wrong password before entering it correctly, the session doesn't load and I get a purple screen, a mouse cursor, and an invisible but clickable menu in the top right. If I enter it correctly the first time, there is no problem. I've replicated this from a fresh boot, after logging out and after 'sudo service gdm restart' from the Ctrl-Alt-F4 console. This is a fresh install, and didn't occur when I was using a previous install of 18.04 (until Friday). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Apr 22 20:31:13 2018 InstallationDate: Installed on 2018-04-22 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180421.1) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1766137/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1762418] Re: Multiple heap-buffer-overflow in tiff-4.0.9
** Information type changed from Private Security to Public Security ** Changed in: tiff (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tiff in Ubuntu. https://bugs.launchpad.net/bugs/1762418 Title: Multiple heap-buffer-overflow in tiff-4.0.9 Status in tiff package in Ubuntu: Confirmed Bug description: Dear all, The following tiff2ps memory issues were found by a modified version of the kAFL fuzzer (https://github.com/RUB-SysSec/kAFL). I have attached the crashing inputs, each ASAN report and each ASAN report in "halt_on_error=false" mode to this bug report. To reproduce those memory issues, execute an ASAN build of tiff2ps with the crashing inputs as the first argument (./tiff2ps ). We can verify those issues for 4.0.9-4ubuntu1 (Ubuntu 16.04.4 LTS / sources from "pull-lp-source tiff"). Credits: Sergej Schumilo, Cornelius Aschermann (both of Ruhr- Universität Bochum) Best regards, Sergej Schumilo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tiff/+bug/1762418/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1760355] Re: Segmentation fault while converting an empty svg
** Information type changed from Private Security to Public Security ** Changed in: librsvg (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to librsvg in Ubuntu. https://bugs.launchpad.net/bugs/1760355 Title: Segmentation fault while converting an empty svg Status in librsvg package in Ubuntu: Confirmed Bug description: gdb -q --args rsvg crashed2.svg test.png Reading symbols from rsvg...(no debugging symbols found)...done. (gdb) run Starting program: /usr/bin/rsvg crashed2.svg test.png [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". (rsvg:14399): librsvg-CRITICAL **: rsvg_handle_set_size_callback: assertion 'handle != NULL' failed Program received signal SIGSEGV, Segmentation fault. 0x77bc55b0 in rsvg_handle_get_dimensions () from /usr/lib/x86_64-linux-gnu/librsvg-2.so.2 (gdb) backtrace #0 0x77bc55b0 in rsvg_handle_get_dimensions () at /usr/lib/x86_64-linux-gnu/librsvg-2.so.2 #1 0x004025d3 in () #2 0x766d0830 in __libc_start_main (main= 0x401960, argc=3, argv=0x7fffe568, init=, fini=, rtld_fini=, stack_end=0x7fffe558) at ../csu/libc-start.c:291 #3 0x00402989 in () To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/librsvg/+bug/1760355/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1758555] Re: Segmentation fault at rsvg-convert:2414
** Information type changed from Private Security to Public Security ** Changed in: librsvg (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to librsvg in Ubuntu. https://bugs.launchpad.net/bugs/1758555 Title: Segmentation fault at rsvg-convert:2414 Status in librsvg package in Ubuntu: Confirmed Bug description: librsvg throws a segmentation fault when an tried to convert an empty svg using rsvg-convert. Details: $ echo > empty.svg $cat empty.svg $rsvg-convert empty.svg (rsvg-convert:4850): librsvg-CRITICAL **: rsvg_handle_set_size_callback: assertion 'handle != NULL' failed Segmentation fault (core dumped) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/librsvg/+bug/1758555/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1768494] Re: Screen lock doesn't cover the whole screen
Which desktop environment are you using? Could you get a picture of the issue? Thanks! ** Changed in: gnome-screensaver (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1768494 Title: Screen lock doesn't cover the whole screen Status in gnome-screensaver package in Ubuntu: Incomplete Bug description: I noticed a rather alarming bug today. Got a Lenovo T470P with dock and two 1440p screens. The laptop is 1440p but I chose 1080p as scaling didn't want to play along. To reproduce: 1. Have the laptop unlocked without the dock. 2. Lock and/or hibernate, close the lid. 3. Connect to the dock. 4. Power on the laptop trough dock. 5. The connected screens to the dock should light up with the login screen, however.. The secondary screen is only covered about 1/4, guessing the same scale as 1080p. I could open files, browse the web and cause damage trough this method. It also works if I lock my laptop on the dock, and someone undocks it and opens the lid, then does step 2-5 again. I saw a "confirmed" bug from 2014, but felt that this needed to be brought up, again. Running 18.04 LTS gnome-screensaver on 3.6.1-ubuntu3 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-screensaver 3.6.1-8ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed May 2 12:39:19 2018 InstallationDate: Installed on 2018-03-19 (44 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) SourcePackage: gnome-screensaver Symptom: security Title: Screen locking issue UpgradeStatus: Upgraded to bionic on 2018-05-02 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1768494/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1767806] Re: Position of left-tiled windows not restored correctly when another left-tiled window present
Thanks, I've now reported this at: https://gitlab.gnome.org/GNOME/gnome- shell/issues/287 -- 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/1767806 Title: Position of left-tiled windows not restored correctly when another left-tiled window present Status in gnome-shell package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: When another window is maximized or tiled to the left side of the screen, re-opening an application whose window was previously tiled to the left side does not restore that windows' previous position. Instead such windows open at varying distances from the dock, untiled. = Steps to reproduce *expected* behavior (with a newly created user) = 1. open Firefox, drag the window to the left edge of the screen to tile it there (filling up the left half of horizontal screen space) 2. close Firefox 3. open Nautilus, make sure that the window floats (i.e. is unmaximized and not tiled to either side of screen) 4. open Firefox == What happens == As expected, Firefox's window is tiled to the left edge of screen, immediately to the right side of the dock. = Steps to reproduce *unexpected* behavior (with a newly created user) = 1. open Firefox, drag the window to the left edge of the screen to tile it there (filling up the left half of horizontal screen space) 2. close Firefox 3. open Nautilus, *maximize its window* 4. open Firefox == What happens == Firefox's window opens slightly to the right off the right edge of the dock (with a gap between the dock and the window). == What I expect to happen == I expect Firefox's window to be tiled to the left edge of screen, immediately to the right side of the dock, just as it did following the first recipe above. = Further information = Either maximizing or tiling Nautilus' window to the left edge of the screen (at step #3) triggers the issue. Tiling it to the *right* edge of the screen does not. Using Gnome Terminal instead of Nautilus triggers the issue just as well, I suspect any other application will though I've only systematically tested these two so far. From battling with this in my daily use I also know that the distance of incorrectly restored windows from the dock varies: different applications open at different distances. The precise mechanics of this still elude me, though the distances do appear to be multiples of 25 pixels. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: mutter 3.28.1-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Apr 29 16:32:37 2018 InstallationDate: Installed on 2016-10-13 (562 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1767806/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1770765] Re: package libsane 1.0.25+git20150528-1ubuntu2.16.04.1 [modified: lib/udev/rules.d/60-libsane.rules] failed to install/upgrade: trying to overwrite shared '/lib/udev/
** 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/1770765 Title: package libsane 1.0.25+git20150528-1ubuntu2.16.04.1 [modified: lib/udev/rules.d/60-libsane.rules] failed to install/upgrade: trying to overwrite shared '/lib/udev/rules.d/60-libsane.rules', which is different from other instances of package libsane:i386 Status in sane-backends package in Ubuntu: New Bug description: wine installation on xubuntu 16 failed ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libsane 1.0.25+git20150528-1ubuntu2.16.04.1 [modified: lib/udev/rules.d/60-libsane.rules] ProcVersionSignature: Ubuntu 4.13.0-41.46~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-41-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 Date: Sat May 12 05:51:17 2018 DuplicateSignature: package:libsane:1.0.25+git20150528-1ubuntu2.16.04.1 [modified: lib/udev/rules.d/60-libsane.rules] Unpacking libsane:i386 (1.0.25+git20150528-1ubuntu2.16.04.1) ... dpkg: error processing archive /var/cache/apt/archives/libsane_1.0.25+git20150528-1ubuntu2.16.04.1_i386.deb (--unpack): trying to overwrite shared '/lib/udev/rules.d/60-libsane.rules', which is different from other instances of package libsane:i386 ErrorMessage: trying to overwrite shared '/lib/udev/rules.d/60-libsane.rules', which is different from other instances of package libsane:i386 InstallationDate: Installed on 2018-03-12 (60 days ago) InstallationMedia: Xubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: sane-backends Title: package libsane 1.0.25+git20150528-1ubuntu2.16.04.1 [modified: lib/udev/rules.d/60-libsane.rules] failed to install/upgrade: trying to overwrite shared '/lib/udev/rules.d/60-libsane.rules', which is different from other instances of package libsane: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/1770765/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1771219] Re: Screen locking and can't be re login
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1771219 Title: Screen locking and can't be re login Status in gnome-screensaver package in Ubuntu: New Bug description: When you close the screen or exit, and if the system is set to the language you write from right to left (in my case Arabic language). When the login screen appears for the user: The language-writing cursor is in the right position with the English language remaining, and the password can not be entered correctly. Which requires restarting the device so that it can be re-accessed. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-screensaver 3.6.1-8ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon May 14 23:31:07 2018 InstallationDate: Installed on 2015-12-14 (882 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: gnome-screensaver Symptom: security Title: Screen locking issue UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.xdg.autostart.gnome-screensaver.desktop: 2017-12-31T01:11:24.484315 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1771219/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1770765] Re: package libsane 1.0.25+git20150528-1ubuntu2.16.04.1 [modified: lib/udev/rules.d/60-libsane.rules] failed to install/upgrade: trying to overwrite shared '/lib/udev/
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- 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/1770765 Title: package libsane 1.0.25+git20150528-1ubuntu2.16.04.1 [modified: lib/udev/rules.d/60-libsane.rules] failed to install/upgrade: trying to overwrite shared '/lib/udev/rules.d/60-libsane.rules', which is different from other instances of package libsane:i386 Status in sane-backends package in Ubuntu: New Bug description: wine installation on xubuntu 16 failed ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libsane 1.0.25+git20150528-1ubuntu2.16.04.1 [modified: lib/udev/rules.d/60-libsane.rules] ProcVersionSignature: Ubuntu 4.13.0-41.46~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-41-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 Date: Sat May 12 05:51:17 2018 DuplicateSignature: package:libsane:1.0.25+git20150528-1ubuntu2.16.04.1 [modified: lib/udev/rules.d/60-libsane.rules] Unpacking libsane:i386 (1.0.25+git20150528-1ubuntu2.16.04.1) ... dpkg: error processing archive /var/cache/apt/archives/libsane_1.0.25+git20150528-1ubuntu2.16.04.1_i386.deb (--unpack): trying to overwrite shared '/lib/udev/rules.d/60-libsane.rules', which is different from other instances of package libsane:i386 ErrorMessage: trying to overwrite shared '/lib/udev/rules.d/60-libsane.rules', which is different from other instances of package libsane:i386 InstallationDate: Installed on 2018-03-12 (60 days ago) InstallationMedia: Xubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: sane-backends Title: package libsane 1.0.25+git20150528-1ubuntu2.16.04.1 [modified: lib/udev/rules.d/60-libsane.rules] failed to install/upgrade: trying to overwrite shared '/lib/udev/rules.d/60-libsane.rules', which is different from other instances of package libsane: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/1770765/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1772004] Re: package libsane-hpaio 3.17.10+repack0-5 [modified: usr/share/hplip/data/models/models.dat] failed to install/upgrade: trying to overwrite shared '/usr/share/hplip/
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1772004 Title: package libsane-hpaio 3.17.10+repack0-5 [modified: usr/share/hplip/data/models/models.dat] failed to install/upgrade: trying to overwrite shared '/usr/share/hplip/data/models/models.dat', which is different from other instances of package libsane-hpaio:i386 Status in hplip package in Ubuntu: New Bug description: There was no contact to scanner and I don't know, wether installig was successfull. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libsane-hpaio 3.17.10+repack0-5 [modified: usr/share/hplip/data/models/models.dat] ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CupsErrorLog: E [18/May/2018:10:50:34 +0200] [cups-deviced] PID 2102 (gutenprint52+usb) stopped with status 1! E [18/May/2018:13:22:36 +0200] [cups-deviced] PID 1773 (gutenprint52+usb) stopped with status 1! Date: Fri May 18 13:27:04 2018 DuplicateSignature: package:libsane-hpaio:3.17.10+repack0-5 [modified: usr/share/hplip/data/models/models.dat] Unpacking libperl5.26:i386 (5.26.1-6) ... dpkg: error processing archive /tmp/apt-dpkg-install-R8zaBp/30-libperl5.26_5.26.1-6_i386.deb (--unpack): trying to overwrite shared '/usr/share/doc/libperl5.26/changelog.Debian.gz', which is different from other instances of package libperl5.26:i386 ErrorMessage: trying to overwrite shared '/usr/share/hplip/data/models/models.dat', which is different from other instances of package libsane-hpaio:i386 InstallationDate: Installed on 2018-05-13 (5 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lpstat: device for HP-Deskjet-1510-series: hp:/usb/Deskjet_1510_series?serial=CN3AD1HMBD05YR MachineType: HP HP Laptop 15-bs0xx Papersize: a4 PpdFiles: HP-Deskjet-1510-series: HP Deskjet 1510 Series, hpcups 3.17.11 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=b8a33649-d2ca-4387-935e-f6ff3fb1007f ro quiet splash vt.handoff=1 Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 1:, Error: [Errno 2] Nincs ilyen fájl vagy könyvtár: "/root/Error: command ['which', 'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] failed with exit code 1:", unpackaged RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: hplip Title: package libsane-hpaio 3.17.10+repack0-5 [modified: usr/share/hplip/data/models/models.dat] failed to install/upgrade: trying to overwrite shared '/usr/share/hplip/data/models/models.dat', which is different from other instances of package libsane-hpaio:i386 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/01/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.31 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 832A dmi.board.vendor: HP dmi.board.version: 23.45 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.31:bd11/01/2017:svnHP:pnHPLaptop15-bs0xx:pvrType1ProductConfigId:rvnHP:rn832A:rvr23.45:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15-bs0xx dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP mtime.conffile..etc.hp.hplip.conf: 2018-05-18T10:46:18.852174 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1772004/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1772004] [NEW] package libsane-hpaio 3.17.10+repack0-5 [modified: usr/share/hplip/data/models/models.dat] failed to install/upgrade: trying to overwrite shared '/usr/share/hpli
Public bug reported: There was no contact to scanner and I don't know, wether installig was successfull. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libsane-hpaio 3.17.10+repack0-5 [modified: usr/share/hplip/data/models/models.dat] ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CupsErrorLog: E [18/May/2018:10:50:34 +0200] [cups-deviced] PID 2102 (gutenprint52+usb) stopped with status 1! E [18/May/2018:13:22:36 +0200] [cups-deviced] PID 1773 (gutenprint52+usb) stopped with status 1! Date: Fri May 18 13:27:04 2018 DuplicateSignature: package:libsane-hpaio:3.17.10+repack0-5 [modified: usr/share/hplip/data/models/models.dat] Unpacking libperl5.26:i386 (5.26.1-6) ... dpkg: error processing archive /tmp/apt-dpkg-install-R8zaBp/30-libperl5.26_5.26.1-6_i386.deb (--unpack): trying to overwrite shared '/usr/share/doc/libperl5.26/changelog.Debian.gz', which is different from other instances of package libperl5.26:i386 ErrorMessage: trying to overwrite shared '/usr/share/hplip/data/models/models.dat', which is different from other instances of package libsane-hpaio:i386 InstallationDate: Installed on 2018-05-13 (5 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lpstat: device for HP-Deskjet-1510-series: hp:/usb/Deskjet_1510_series?serial=CN3AD1HMBD05YR MachineType: HP HP Laptop 15-bs0xx Papersize: a4 PpdFiles: HP-Deskjet-1510-series: HP Deskjet 1510 Series, hpcups 3.17.11 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=b8a33649-d2ca-4387-935e-f6ff3fb1007f ro quiet splash vt.handoff=1 Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 1:, Error: [Errno 2] Nincs ilyen fájl vagy könyvtár: "/root/Error: command ['which', 'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] failed with exit code 1:", unpackaged RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: hplip Title: package libsane-hpaio 3.17.10+repack0-5 [modified: usr/share/hplip/data/models/models.dat] failed to install/upgrade: trying to overwrite shared '/usr/share/hplip/data/models/models.dat', which is different from other instances of package libsane-hpaio:i386 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/01/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.31 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 832A dmi.board.vendor: HP dmi.board.version: 23.45 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.31:bd11/01/2017:svnHP:pnHPLaptop15-bs0xx:pvrType1ProductConfigId:rvnHP:rn832A:rvr23.45:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15-bs0xx dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP mtime.conffile..etc.hp.hplip.conf: 2018-05-18T10:46:18.852174 ** Affects: hplip (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic package-conflict -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1772004 Title: package libsane-hpaio 3.17.10+repack0-5 [modified: usr/share/hplip/data/models/models.dat] failed to install/upgrade: trying to overwrite shared '/usr/share/hplip/data/models/models.dat', which is different from other instances of package libsane-hpaio:i386 Status in hplip package in Ubuntu: New Bug description: There was no contact to scanner and I don't know, wether installig was successfull. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libsane-hpaio 3.17.10+repack0-5 [modified: usr/share/hplip/data/models/models.dat] ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CupsErrorLog: E [18/May/2018:10:50:34 +0200] [cups-deviced] PID 2102 (gutenprint52+usb) stopped with status 1! E [18/May/2018:13:22:36 +0200] [cups-deviced] PID 1773 (gutenprint52+usb) stopped with status 1! Date: Fri May 18 13:27:04 2018 DuplicateSignature: package:libsane-hpaio:3.17.10+repack0-5 [modified: usr/share/hplip/data/models/models.dat] Unpacking libperl5.26:i386 (5.26.1-6) ... dpkg: error processing archive /tmp/apt-dpkg-install-R8zaBp/30-libperl5.26_5.26.1-6_i386.deb (--unpack): trying to overwrite shared '/usr/share/doc/libperl5.26/changelog.Debian.gz', which is different from other instances of package libperl5.26:i386 ErrorMessage: trying to overwrite shared '/usr/share/hplip/data/models/models.dat', which is different from other
[Desktop-packages] [Bug 1771273] Re: Gnome-shell crashes when wake up after updated to 3.28.1-0ubuntu2
*** This bug is a duplicate of bug 1771788 *** https://bugs.launchpad.net/bugs/1771788 Oh really? I must have missed the "not". Thank you very much Daniel for your help. You are the most patient people I've ever met here. -- 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/1771273 Title: Gnome-shell crashes when wake up after updated to 3.28.1-0ubuntu2 Status in gnome-shell package in Ubuntu: Incomplete Bug description: Hello, After having updated gnome-shell from 3.28.1-0ubuntu1 to 3.28.1-0ubuntu2, I've experienced the gnome-shell crash after every time I wake it up. It seems that it has killed my session. When I wakes my computer up, it shows the very first message usually only appear when starting the computer, like starting the snappy daemon, starting mysql server, etc. I'm using Ubuntu 18.04 LTS, Gnome-shell, Wayland. Please tell me what information I need to provide to confirm this bug. Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1771273/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1738164] Re: [snap] U2F doesn't work with yubikey
It no longer throws an apparmor denied message but it doesn't work. Bot gmail and github throw a 'Something went wrong' error. -- 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/1738164 Title: [snap] U2F doesn't work with yubikey Status in chromium-browser package in Ubuntu: Confirmed Bug description: (initially reported by Daniel at https://forum.snapcraft.io/t/call- for-testing-chromium-62-0-3202-62/2569/50) « U2F (Universal 2nd Factor) isn’t working when signing into my gmail account trying to use my yubikey. This is a USB device which IIRC chromium needs bidirectional communication with. » This requires investigation, but the yubikey I have is too old and doesn't support U2F. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1738164/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1728012] Re: Many 3rd party scanner drivers are broken by a sane change
@Ken Wright: For my scanner (Epson GT-S50 / epkowa driver), I added more in my udev rule file: > SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", MODE=="0666" > SUBSYSTEM=="usb_device", MODE=="0666" > ATTRS{manufacturer}=="EPSON", DRIVERS=="usb", SUBSYSTEMS=="usb", > ATTRS{idVendor}=="04b8", ATTRS{idProduct}=="*", MODE="0666" > ATTRS{idVendor}=="04b8", ATTRS{idProduct}=="0137", MODE="0666", > GROUP="scanner", ENV{libsane_matched}="yes" the last line is important, and is missing in the recommendations of comment #96, that is perhaps what is causing you trouble. NOTE: for your scanner, the line should read (cfr. #124): > ATTRS{idVendor}=="04b8", ATTRS{idProduct}=="0130", MODE="0666", > GROUP="scanner", ENV{libsane_matched}="yes" Hoping this will help. Cheers. -- 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/1728012 Title: Many 3rd party scanner drivers are broken by a sane change Status in sane-backends package in Ubuntu: Confirmed Bug description: Many scanners can no more be used since sane has changed something: The 3rd-party plug-in the vendor provides as .deb package will still install. But the scanner is no more recognized. Scanners that are affected are(besides others): - Epson Perfection V10 - Epson Perfection V1000 - Epson WorkForce GT-1500 - Brother MFC-8510DN - Epson Perfection V33 It is to note that the probability that the scanner manufacturers fix things others broke is below 100%. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libsane1 1.0.27-1~experimental2ubuntu2 Uname: Linux 4.14.0-041400rc5-lowlatency x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 Date: Fri Oct 27 12:35:52 2017 EcryptfsInUse: Yes SourcePackage: sane-backends 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/1728012/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1752053] Re: nvidia-390 fails to boot graphical display
The only working solution for me for the Nvidia graphic card problem in Ubuntu 18.04, was to follow the instructions from this page: https://medium.com/@emtudo/ubuntu-18-04-travamento-com-placa-nvidia- 3720dfe7410a and then start the system through recovery mode. -- 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/1752053 Title: nvidia-390 fails to boot graphical display Status in mesa package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in xserver-xorg-video-nouveau package in Ubuntu: Invalid Bug description: I'm using Bionic with the new 4.15 kernel. I've been using the nvidia-384 driver with no problem for a while. Today I issued "sudo apt-get upgrade" and I was prompted to upgrade the nvidia driver to the nvidia-390. After installing the driver and rebooting, I was only able to boot in to the tty terminal. The graphical display failed to boot. I have had similar problems with nvidia driver version 390 with Arch Linux and with Open Suse Tumbleweed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1771734] Re: gedit abnormally use high CPU
*** This bug is a duplicate of bug 1679226 *** https://bugs.launchpad.net/bugs/1679226 ** This bug has been marked a duplicate of bug 1679226 gedit consumes 100% of cpu when left minimised -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1771734 Title: gedit abnormally use high CPU Status in gedit package in Ubuntu: New Bug description: Gedit trigger an ubuntu high cpu consumption when the mouse is not in the windows of gedit. gnome-shell ate up 50 % of cpu, while Xorg consumed 20 % of cpu, gedit consumed 30 % of cpu. CPU is not able to cool down, when gedit is opened and the location of mouse is in other applications instead of gedit. If the situation goes on, system will hang. When Gedit is turned off in time, everything goes back to normal. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gedit 3.18.3-0ubuntu4 ProcVersionSignature: Ubuntu 4.13.0-41.46~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-41-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 CurrentDesktop: GNOME Date: Thu May 17 12:58:37 2018 ExecutablePath: /usr/bin/gedit InstallationDate: Installed on 2018-04-29 (17 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1771734/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1771976] Re: Collect physical screen size
** Changed in: ubuntu-report Status: Unknown => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-report in Ubuntu. https://bugs.launchpad.net/bugs/1771976 Title: Collect physical screen size Status in ubuntu-report: New Status in ubuntu-report package in Ubuntu: New Bug description: ubuntu-report collects the current resolution, it would be useful to collect the physical screen size and be able to compute pixel density for example. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: ubuntu-report 1.0.11 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri May 18 11:17:10 2018 Dependencies: gcc-8-base 8.1.0-2ubuntu1 libc6 2.27-3ubuntu1 libgcc1 1:8.1.0-2ubuntu1 InstallationDate: Installed on 2014-07-15 (1403 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520) SourcePackage: ubuntu-report UpgradeStatus: Upgraded to cosmic on 2018-03-24 (54 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-report/+bug/1771976/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1771981] [NEW] Sync opus 1.3~beta+20180518-1 (main) from Debian sid (main)
Public bug reported: Please sync opus 1.3~beta+20180518-1 (main) from Debian sid (main) Explanation of the Ubuntu delta and why it can be dropped: * Merge with Debian; remaining changes: - Convert to Debhelper 9 with a simpler rules file. - Build using dh-autoreconf. - Add a watch file. - debian/control: close some Lintian errors. - Pre-depend on multiarch-support. - Add ${misc:Depends} to package dependencies. - Convert to debian source format 3.0 (quilt). - Run the tests. This release brings a lot of quality improvemets since the very old 1.1.2 upstream release in Ubuntu. The Debian changelog has this explanation about debian bug #810258, which had the Ubuntu changes being dropped. * Use dh compat 9, not because it actually brings anything new which we need here, but it hushes the increasingly insistent warnings about deprecated compat levels, and is a baseline supported by all of the releases we still need to be able to support. I'm going to say this Closes: #810258, since the rest of the 'modernisation' there mostly isn't helpful. We've already been running the tests since the very first release, we release directly from upstream git and maintain upstream patches there, so format 3(quilt) adds nothing but pain, and we have upstream build and install targets that are designed to cleanly separate the -arch specific and -indep components, so regressing to make those codependent isn't very appealing either. It would have also broken support for building where m-a wasn't supported, though that's less of a problem today than it was previously. Thanks. Changelog entries since current cosmic version 1.1.2-1ubuntu1: opus (1.3~beta+20180518-1) unstable; urgency=medium * Fix the CELT input NaN test. -- Ron Lee <r...@debian.org> Fri, 18 May 2018 05:04:27 +0930 opus (1.3~beta+20180516-1) unstable; urgency=medium * Snapshot from 652c4559f593d3aad78bd5c85a216eeae7859429 as a preview of patches pending for the 1.3 release. The main motivation for doing this now is to pull in the fix for the PLC regression introduced just before 1.2~alpha2, which Closes: #898690, and to get some broader testing on the new hardening checks before flipping the switch to enable those by default upstream. * Fix celt_pitch_xcorr() ARM jump table compiling error for a bug introduced in 1.2-rc1. * Better rate allocation for stereo SILK in hybrid mode. * Add RNN for VAD and speech/music classification. * Fixing bandwidth detection for 24 kHz analysis. * Enable RFC 8251 changes by default. * Better tuning for low-bitrate music. * Don't set _FORTIFY_SOURCE and -fstack-protector as part of the packaging anymore, the upstream build system will add them where they are supported and needed now. * Build with --enable-hardening, which isn't related to the compile options above, but instead includes additional opus-specific runtime sanity checks which are cheap and certain enough to use in production builds. * Use dh compat 9, not because it actually brings anything new which we need here, but it hushes the increasingly insistent warnings about deprecated compat levels, and is a baseline supported by all of the releases we still need to be able to support. I'm going to say this Closes: #810258, since the rest of the 'modernisation' there mostly isn't helpful. We've already been running the tests since the very first release, we release directly from upstream git and maintain upstream patches there, so format 3(quilt) adds nothing but pain, and we have upstream build and install targets that are designed to cleanly separate the -arch specific and -indep components, so regressing to make those codependent isn't very appealing either. It would have also broken support for building where m-a wasn't supported, though that's less of a problem today than it was previously. -- Ron Lee <r...@debian.org> Thu, 17 May 2018 16:07:39 +0930 opus (1.2.1-1) unstable; urgency=medium * Fixes a bug in surround encoding causing very bad quality on loud signals beyond a certain amplitude. * Speech quality improvements especially in the 12-24 kbit/s range. * Music quality improvements in the 32-48 kb/s range. * More aggressive use of wider speech bandwidth, including fullband speech starting at 14 kbit/s. * Improved VBR encoding for hybrid mode. * SILK CBR improvements. * DTX support for CELT mode. * Support for directly encoding packets up to 120 ms. * Improves quality on files with powerful tones that cause MDCT leakage. * Fixes for speech/music detection at the very beginning of files. * Fixes an issue where the encoder can misdetect that the signal is SWB instead of FB, lowpassing the signal. -- Ron Lee <r...@debian.org> Thu, 28 Sep 2017 01:48:45 +0930 opus (1.2~alpha2-1) unstable; urgency=medium
[Desktop-packages] [Bug 1046609] Re: Font family (fonts-vollkorn) appearing as multiple fonts in LibreOffice
Not seeing the issue in libreoffice 6.0.3 on ubuntu 18.04. "Vollkorn" is listed in libreoffice writer's font list as a unique font (see attached screenshot). I guess the issue was fixed since then. ** Attachment added: "vollkorn.png" https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1046609/+attachment/5141186/+files/vollkorn.png -- 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/1046609 Title: Font family (fonts-vollkorn) appearing as multiple fonts in LibreOffice Status in libreoffice package in Ubuntu: Invalid Bug description: In LibreOffice (at least writer and calc), Vollkorn appears in the font list as "Vollkorn Regular", "Vollkorn Bold", etc. If "Vollkorn Regular" is selected as the font, then made bold/italic, it uses a faux bold/italic, instead of the proper font version. That's the basic problem - here's some additional info: The font works as expected (appears as "Vollkorn", uses e.g. Vollkorn- Bold when made bold) in other applications, such as Inkscape. The files also appears as expected (e.g. Name: Vollkorn, Style: Regular) in Font Viewer. This problem does not occur in LibreOffice with other true type fonts (eg. Liberation Serif and many others) Manually entering "Vollkorn" as the font name in LibreOffice makes the font work as expected when made bold and/or italic, but the basic font does not show correctly (it shows as a default sans-serif font instead). This makes me think something might be wrong with Vollkorn- Regular.ttf specifically? This occurs whether I install the fonts-vollkorn package, or download it from elsewhere (e.g. google fonts) and install it using Font Viewer, or by manually putting it in my .fonts folder or usr/share/fonts. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1046609/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1771976] Re: Collect physical screen size
** Bug watch added: github.com/ubuntu/ubuntu-report/issues #18 https://github.com/ubuntu/ubuntu-report/issues/18 ** Also affects: ubuntu-report via https://github.com/ubuntu/ubuntu-report/issues/18 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-report in Ubuntu. https://bugs.launchpad.net/bugs/1771976 Title: Collect physical screen size Status in ubuntu-report: Unknown Status in ubuntu-report package in Ubuntu: New Bug description: ubuntu-report collects the current resolution, it would be useful to collect the physical screen size and be able to compute pixel density for example. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: ubuntu-report 1.0.11 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri May 18 11:17:10 2018 Dependencies: gcc-8-base 8.1.0-2ubuntu1 libc6 2.27-3ubuntu1 libgcc1 1:8.1.0-2ubuntu1 InstallationDate: Installed on 2014-07-15 (1403 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520) SourcePackage: ubuntu-report UpgradeStatus: Upgraded to cosmic on 2018-03-24 (54 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-report/+bug/1771976/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1771976] [NEW] Collect physical screen size
Public bug reported: ubuntu-report collects the current resolution, it would be useful to collect the physical screen size and be able to compute pixel density for example. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: ubuntu-report 1.0.11 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri May 18 11:17:10 2018 Dependencies: gcc-8-base 8.1.0-2ubuntu1 libc6 2.27-3ubuntu1 libgcc1 1:8.1.0-2ubuntu1 InstallationDate: Installed on 2014-07-15 (1403 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520) SourcePackage: ubuntu-report UpgradeStatus: Upgraded to cosmic on 2018-03-24 (54 days ago) ** Affects: ubuntu-report Importance: Unknown Status: Unknown ** Affects: ubuntu-report (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-report in Ubuntu. https://bugs.launchpad.net/bugs/1771976 Title: Collect physical screen size Status in ubuntu-report: Unknown Status in ubuntu-report package in Ubuntu: New Bug description: ubuntu-report collects the current resolution, it would be useful to collect the physical screen size and be able to compute pixel density for example. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: ubuntu-report 1.0.11 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri May 18 11:17:10 2018 Dependencies: gcc-8-base 8.1.0-2ubuntu1 libc6 2.27-3ubuntu1 libgcc1 1:8.1.0-2ubuntu1 InstallationDate: Installed on 2014-07-15 (1403 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520) SourcePackage: ubuntu-report UpgradeStatus: Upgraded to cosmic on 2018-03-24 (54 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-report/+bug/1771976/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1768794] Re: Snap branches all show with same name
Seems to be fixed in 18.04. Although due to this fix I can't test the fix for the bug #1768779 -- 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/1768794 Title: Snap branches all show with same name Status in gnome-software package in Ubuntu: Fix Released Status in gnome-software source package in Bionic: Fix Committed Status in gnome-software source package in Cosmic: Fix Released Bug description: [Impact] Snaps with multiple branches (e.g. communitheme) all show in GNOME Software with the branches having the same name. Steps to reproduce: 1. Search for ”communitheme” 2. Select ”communitheme” result 3. Click on the channel selection button 4. You will see a popup with loong list of channels Expected result: All branches/channels are shown. Observed result: All branches have the same name. [Regression Potential] Fix was an invalid iterator, unlikely to cause further issues. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1768794/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1752053] Re: nvidia-390 fails to boot graphical display
@bernadette, it baffels me. Today my Xps 15, 9560 works flawlessly fast and nimble. I also nailed the power drain and now have ~5W running on battery, see https://github.com/stockmind/dell-xps-9560-ubuntu- respin/issues/8 Makes me thinking... what BIOS version do you have ? I run 1.9.4 ** Bug watch added: github.com/stockmind/dell-xps-9560-ubuntu-respin/issues #8 https://github.com/stockmind/dell-xps-9560-ubuntu-respin/issues/8 -- 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/1752053 Title: nvidia-390 fails to boot graphical display Status in mesa package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in xserver-xorg-video-nouveau package in Ubuntu: Invalid Bug description: I'm using Bionic with the new 4.15 kernel. I've been using the nvidia-384 driver with no problem for a while. Today I issued "sudo apt-get upgrade" and I was prompted to upgrade the nvidia driver to the nvidia-390. After installing the driver and rebooting, I was only able to boot in to the tty terminal. The graphical display failed to boot. I have had similar problems with nvidia driver version 390 with Arch Linux and with Open Suse Tumbleweed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1769330] Re: 18.04 regression: liberation text highlight is too small in web browsers.
Installing fonts-liberation 1:1.07.4-6 fixes the issue. https://launchpad.net/ubuntu/+archive/primary/+files/fonts- liberation_1.07.4-6_all.deb -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fonts-liberation in Ubuntu. https://bugs.launchpad.net/bugs/1769330 Title: 18.04 regression: liberation text highlight is too small in web browsers. Status in fonts-liberation package in Ubuntu: New Bug description: When Liberation font is selected in Firefox 59 and Chromium 65, the highlight does not cover the top part of the text. On Chromium it affects the first line of a paragraph, on Firefox it affects every line. This is a regression in 1:1.07.4-5, rolling back to the previous version (1:1.07.4-2) restores the correct behavior. The same font in gedit, libreoffice and terminal does not have this problem, however since both browsers are affected and other fonts highlight normally it suggests the fault lies with the font. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-liberation/+bug/1769330/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1765614] Re: Incorrect regex for GPU info
** Changed in: ubuntu-report (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-report in Ubuntu. https://bugs.launchpad.net/bugs/1765614 Title: Incorrect regex for GPU info Status in ubuntu-report package in Ubuntu: Fix Committed Bug description: The regex is incorrect to match the GPU info It should be: ^.* 0300: (.*)(\( rev .*\))?$ to match the cases where there is no revision number. Like: 01:00.0 0300: 1002:68b8 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-report 1.0.11 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Apr 20 09:08:21 2018 Dependencies: gcc-8-base 8-20180414-1ubuntu2 libc6 2.27-3ubuntu1 libgcc1 1:8-20180414-1ubuntu2 InstallationDate: Installed on 2014-07-15 (1374 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520) SourcePackage: ubuntu-report UpgradeStatus: Upgraded to bionic on 2018-03-24 (26 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-report/+bug/1765614/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1480673] Re: [ELAN 3320KD-3100] Asus T300 CHI bluetooth Touchpad is recognized incorrectly
Confirmed as well. Works perfectly. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xinput in Ubuntu. https://bugs.launchpad.net/bugs/1480673 Title: [ELAN 3320KD-3100] Asus T300 CHI bluetooth Touchpad is recognized incorrectly Status in libinput: Won't Fix Status in Linux: Unknown Status in xinput package in Ubuntu: Triaged Bug description: Moved the touchscreen issues to bug #1574341 "[Asus T300 CHI] Synaptics Touch Digitizer V04 - no multitouch". The Asus T300 CHI has a touchscreen and a (bluetooth) keyboard/touchpad combo. Both (touchscreen, touchpad) only work like a mouse (moving pointer, left and right click), scrolling, zooming, etc. is not working. the keyboard works fine. relevant content of /proc/bus/input/devices: [...] I: Bus=0003 Vendor=06cb Product=11f0 Version=0111 N: Name="SYNAPTICS Synaptics Touch Digitizer V04" P: Phys=usb-:00:14.0-7/input0 S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/0003:06CB:11F0.0004/input/input9 U: Uniq= H: Handlers=mouse1 event9 B: PROP=2 B: EV=b B: KEY=400 0 0 0 0 0 B: ABS=2608003 I: Bus=0003 Vendor=06cb Product=11f0 Version=0111 N: Name="SYNAPTICS Synaptics Touch Digitizer V04 Pen" P: Phys=usb-:00:14.0-7/input0 S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/0003:06CB:11F0.0004/input/input10 U: Uniq= H: Handlers=mouse2 event10 B: PROP=0 B: EV=1b B: KEY=c03 1 0 0 0 0 B: ABS=103 B: MSC=10 [...] I: Bus=0005 Vendor=0b05 Product=8502 Version=0001 N: Name="ASUS T300CHI DOCKING" P: Phys=34:02:86:7b:3b:9d S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-4/1-4:1.0/bluetooth/hci0/hci0:256/0005:0B05:8502.0006/input/input18 U: Uniq=1c:b7:2c:15:94:8b H: Handlers=sysrq kbd mouse3 event17 B: PROP=0 B: EV=12001f B: KEY=20 0 0 2000 40 3 10207 ff9f387ad9405fff febeffdfffef fffe B: REL=303 B: ABS=700 B: MSC=10 B: LED=1f output of xinput --list: ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ B16_b_02 USB-PS/2 Optical Mouse id=9[slave pointer (2)] ⎜ ↳ HID 0566:3108 id=11 [slave pointer (2)] ⎜ ↳ SYNAPTICS Synaptics Touch Digitizer V04 Pen id=14 [slave pointer (2)] ⎜ ↳ SYNAPTICS Synaptics Touch Digitizer V04 id=15 [slave pointer (2)] ⎜ ↳ ASUS T300CHI DOCKINGid=18 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Sleep Buttonid=8[slave keyboard (3)] ↳ HID 0566:3108 id=10 [slave keyboard (3)] ↳ C-Media Electronics Inc. USB Multimedia Audio Deviceid=12 [slave keyboard (3)] ↳ USB2.0 HD UVC WebCamid=13 [slave keyboard (3)] ↳ Asus WMI hotkeysid=16 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=17 [slave keyboard (3)] output of synclient is: Couldn't find synaptics properties. No synaptics driver loaded? but I'm unsure if the synaptics driver is the right place to look since basic functionality is working and the "ASUS T300CHI DOCKING" is recognized as "pointer" it seems that the device is recognized by the kernel but only used as a pointing device. I've also attached the xorg.log output of uname -a: Linux xxx 3.19.0-25-generic #26-Ubuntu SMP Fri Jul 24 21:17:31 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux it's a completely fresh install of xubuntu 15.04 with software-updater run once (so no strange hacks or drivers installed) output of lsb_release -rd: Description: Ubuntu 15.04 Release: 15.04 output of apt-cache policy xinput xinput: Installed: 1.6.1-1 Candidate: 1.6.1-1 Version table: *** 1.6.1-1 0 500 http://de.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages 100 /var/lib/dpkg/status expected results: - scrolling on touchpad and touchscreen should work with a two-finger gesture - zooming on touchpad and touchscreen should work with a two-finger gesture actual results: two fingers are not recognized on touchscreen or touchpad Any help would be appreciated, if you need more console output or logs, please let me know. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xinput 1.6.1-1 ProcVersionSignature: Ubuntu 3.19.0-25.26-generic
[Desktop-packages] [Bug 1687246] Re: GNOME Shell should support fractional (non-integer) Hi-DPI scaling
I am having this problem on ubuntu 18.04 on my dell precision m3800 it has built in 13inch 4k screen which is perfectly setup and scaled but i also have external 40in 4k screen on display port , this gets scaled to the same settings as the 13inch screen which is waste. under unity i could scale each independently and it was excellent additionally my external screen now only runs at a horrible 30hz when it used to run at 60hz the internal screen runs at 60hz . xrandr doesn't give me more options I am using the nvidia driver in fulltime optimus mode with the built in -- 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/1687246 Title: GNOME Shell should support fractional (non-integer) Hi-DPI scaling Status in Mutter: In Progress Status in Ubuntu GNOME: Triaged Status in gnome-shell package in Ubuntu: In Progress Bug description: https://trello.com/c/r12LY9iA (for 17.04 was https://trello.com/c/TvwNvXOo) --- I'm using fully updated Ubuntu GNOME 17.04. In Ubuntu Gnome, you only allow for integer scaling of things for high DPI monitors. While in theory this sounds good, on a 27 inch 4k monitor like mine, restricting it to integers is a problem. 1x is annoyingly small, and 2x is WAY too big. You need a 1.5x, and presumably to just allow most noninteger values to future proof the distribution given 8k monitors and all sorts of new and weird things coming out, like windows 10 has. Photos of the two annoying sizes are available here (it won't let me attach two files): http://i.imgur.com/vWrvZxq.jpg http://i.imgur.com/11p19k7.jpg I apologize for my photography skills in advance., you'll have to look at the ruler for scale to see the problem. Please contact me if you need any more information etc. Workaround == You can enable experimental fractional scaling in Ubuntu 17.10 or 18.04 LTS by running the following command in a terminal and then restarting your computer. Note that this is an experimental feature and is not fully supported by either Ubuntu or GNOME. gsettings set org.gnome.mutter experimental-features "['scale-monitor- framebuffer']" After restarting your computer, you should find additional scale options in Settings > Devices > Displays. If you change your mind and want to get back to supported status, run: gsettings reset org.gnome.mutter experimental-features To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1687246/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1767787] Re: prime-select doesn't switch to nvidia after reboot
Using prime indicator plus for switching, and lightDM instead of GDM behaves as it should. With GDM it require sudo systemctl restart display-manager - guess it's a GDM bug. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1767787 Title: prime-select doesn't switch to nvidia after reboot Status in nvidia-prime package in Ubuntu: New Bug description: After sudo prime-select nvidia, recreate new initramfs and reboot I still land on Gnome using Intel gfx card. I have color LED which provides me information about which card is used. When I check which mode is selected with sudo prime-select query I see nvidia but when I check which card is really used with glxheads I see Intel. For the true switch I need log off from Gnome, switch to virtual console and type two commands: sudo modprobe nvidia sudo systemctl restart display-manager.service After these two commands, I'm able to use Nvidia gfx card under Gnome. In my personal opinion, this solution with switching between cards through initramfs and reboot is a huge step back in the usability of Ubuntu. The previous solution with alternatives was much much better for end user. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nvidia-prime 0.8.8 ProcVersionSignature: Ubuntu 4.15.0-20.21-lowlatency 4.15.17 Uname: Linux 4.15.0-20-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Sun Apr 29 13:09:45 2018 Dependencies: InstallationDate: Installed on 2015-02-13 (1170 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) PackageArchitecture: all SourcePackage: nvidia-prime UpgradeStatus: Upgraded to bionic on 2018-04-28 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1767787/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1765261] Re: [regression] Ubuntu 18.04 login screen rejects a valid password on first attempt. Usually works on the second attempt
Sorry but this bug report is not for discussion on the best flavour of Ubuntu - please ask on the forums and don't spam everyone involved in the discussion. -- 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/1765261 Title: [regression] Ubuntu 18.04 login screen rejects a valid password on first attempt. Usually works on the second attempt Status in gnome-shell package in Ubuntu: In Progress Status in gnome-shell source package in Bionic: Confirmed Status in gnome-shell package in Fedora: Fix Released Bug description: Upstream: https://gitlab.gnome.org/GNOME/gnome-shell/issues/240 Ubuntu 18.04 login screen rejects a valid password on first attempt. Always works on the second attempt.. This seems to be a new problem, just started today. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 Date: Thu Apr 19 11:16:17 2018 InstallationDate: Installed on 2017-12-12 (127 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1765261/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1707352] Re: the change from libsane to libsane1 broke many (all?) 3rd party plug-ins for sane
Once again fresh installed Bionic for test. And now it works immediately after installing the brother driver. -- 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/1707352 Title: the change from libsane to libsane1 broke many (all?) 3rd party plug- ins for sane Status in sane-backends package in Ubuntu: Fix Released Status in sane-backends source package in Artful: Fix Released Status in sane-backends package in Debian: Invalid Bug description: Note to SRU Team The first proposed fix (1.0.27-1~experimental2ubuntu2) failed because it needed to be a versioned Provides, not just a Provides. Impact == 1) The Debian maintainer renamed libsane to libsane1-experimental "to match with the soname". This apparently fixes a Lintian warning, but makes installing 3rd-party plug-ins hard, as they typically depend on "libsane", not on "libsane1". The first try to add a "Provides: libsane" to libsane1 (which created a virtual package) didn't make drivers installable that claim to depend on a minimum version of libsane as virtual packages are ignored in this case. 2) The soname change might be justified by the new version breaking (several? most?) 3rd party plug-ins even if the library version number doesn't indicate any bigger change than any ordinary new version of the library - which might indicate that this phenomenon might be an upstream bug. libsane 1.0.25 in zesty includes libsane.so.1.25 libsane1 1.0.27 in artful includes libsane.so.1.27 It is to note that depending on the manufacturer for many old scanners there won't be new versions of the plug-ins that are recompiled like this. Test Case = Visit http://support.epson.net/linux/en/iscan_c.html Download the amd64 deb .tar.gz Unzip it. Install the iscan .deb from the core folder. It won't install before this SRU because it Depends: libsane Regression Potential The fix here was proposed to the Debian maintainer in July but there's been virtually zero response on it. In the meantime the workaround that was proposed initially has started to result in automatically uninstalling gtk - which makes the system basically useless. It doesn't seem like adding the Provides will make things any worse for third-party drivers but it has a goodme chance of making things better for some. Original Bug Report === I don't know if that can be prevented in the long run. But both brscan (for my brother scanner) and iscan (for my epson scanners) have been broken by the change from libsane to libsane1. For iscan I have unpackaged the debian package, changed the dependency it contains from libsane to libsane1 and installed the changed package. But even then my epson scanners no more work leaving me without any scanner => Reporting a bug. Impossibility of workarounds Just installing an old version of libsane is impossible as it uninstalls libgtk (which depends on libsane1 which conflicts with libsane) making the system basically useless. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: libsane1 1.0.27-1~experimental1ubuntu2 Uname: Linux 4.13.0-041300rc2-lowlatency x86_64 ApportVersion: 2.20.6-0ubuntu4 Architecture: amd64 Date: Sat Jul 29 08:38:15 2017 EcryptfsInUse: Yes SourcePackage: sane-backends 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/1707352/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1754886] Re: Eclipse fails to start on fresh 18.04 installation
Have the same problem. Seems root cause is a broken dependcy: eclipse-platform version is 3.8.1-11 it depends on eclipse-rcp version 3.8.1-11 which in turn depends on libequinox-osgi-java (>= 3.9.1). But eclipse-platform-data expects libequinox-osgi-java version 3.8.1-11: $ apt-cache --recurse depends eclipse-platform | less eclipse-platform Depends: eclipse-rcp eclipse-rcp Depends: libequinox-osgi-java $ apt-cache show eclipse-rcp Package: eclipse-rcp Architecture: amd64 Version: 3.8.1-11 Priority: optional Section: universe/devel Source: eclipse Origin: Ubuntu Maintainer: Ubuntu DevelopersOriginal-Maintainer: Debian Orbital Alignment Team Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 8094 Depends: default-jre | java5-runtime | java6-runtime, libequinox-osgi-java (>= 3.9.1), libfelix-gogo-command-java, libfelix-gogo-shell-java, libicu4j-49-java (>= 49.1-2), libswt-gtk-3-java (<< 3.9.0~), libswt-gtk-3-java (>= 3.8.0~), libswt-cairo-gtk-3-jni (>= 3.8.0~), libswt-webkit-gtk-3-jni (>= 3.8.0~), libc6 (>= 2.14) $ dpkg -L eclipse-platform-data | grep config.ini | xargs cat | grep osgi.framework= osgi.framework=file\:plugins/org.eclipse.osgi_3.8.1.dist.jar osgi.framework=file\:plugins/org.eclipse.osgi_3.8.1.dist.jar -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to eclipse in Ubuntu. https://bugs.launchpad.net/bugs/1754886 Title: Eclipse fails to start on fresh 18.04 installation Status in eclipse package in Ubuntu: In Progress Status in eclipse package in Debian: New Bug description: I just installed 18.04 from today's March 10th desktop ISO in a VM with all default settings. I proceeded to install Eclipse and build tools with: sudo apt-get install eclipse git build-essential I then ran `eclipse` in a terminal from my home directory (launcher icon behaves same way). I expected Eclipse to open, but instead I got a popup saying: An error has occurred. See the log file /home/vidar/.eclipse/org.eclipse.platform_3.8_155965261/configuration/1520710304064.log Meanwhile, the following messages are printed on stderr: OpenJDK 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0 Gtk-Message: 11:31:25.572: Failed to load module "canberra-gtk-module" Gtk-Message: 11:31:25.619: Failed to load module "canberra-gtk-module" The file it mentions contains: !SESSION Sat Mar 10 11:31:44 PST 2018 -- !ENTRY org.eclipse.equinox.launcher 4 0 2018-03-10 11:31:44.078 !MESSAGE Exception launching the Eclipse Platform: !STACK java.lang.ClassNotFoundException: org.eclipse.core.runtime.adaptor.EclipseStarter at java.net.URLClassLoader.findClass(URLClassLoader.java:381) at java.lang.ClassLoader.loadClass(ClassLoader.java:424) at java.lang.ClassLoader.loadClass(ClassLoader.java:357) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:626) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:584) at org.eclipse.equinox.launcher.Main.run(Main.java:1438) at org.eclipse.equinox.launcher.Main.main(Main.java:1414) `eclipse`, `eclipse-jdt` and `eclipse-platform` are all version 3.8.1-11. There are no pending updates after an `apt-get update && apt-get upgrade`. Installing libcanberra-gtk-module got rid of those warnings, but the popup and error message remain. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eclipse/+bug/1754886/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1046609] Re: Font family (fonts-vollkorn) appearing as multiple fonts in LibreOffice
That is because the gtk/gnome font dialog is "retarded". Microsoft Office, and its cheap plastic copies called Star Office, OpenOffice, LibreOffice "real-time generate" really bad "italic" or "bold" of fonts not providing that. The LibreOffice is to blame here. More professional software, is perfectly capable to handle it right, see attached screenshot. ** Attachment added: "gnustep-font-dialog.png" https://bugs.launchpad.net/ubuntu/+source/fonts-vollkorn/+bug/1046609/+attachment/5141151/+files/gnustep-font-dialog.png ** Changed in: fonts-vollkorn (Ubuntu) Status: Confirmed => Invalid ** Package changed: fonts-vollkorn (Ubuntu) => libreoffice (Ubuntu) -- 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/1046609 Title: Font family (fonts-vollkorn) appearing as multiple fonts in LibreOffice Status in libreoffice package in Ubuntu: Invalid Bug description: In LibreOffice (at least writer and calc), Vollkorn appears in the font list as "Vollkorn Regular", "Vollkorn Bold", etc. If "Vollkorn Regular" is selected as the font, then made bold/italic, it uses a faux bold/italic, instead of the proper font version. That's the basic problem - here's some additional info: The font works as expected (appears as "Vollkorn", uses e.g. Vollkorn- Bold when made bold) in other applications, such as Inkscape. The files also appears as expected (e.g. Name: Vollkorn, Style: Regular) in Font Viewer. This problem does not occur in LibreOffice with other true type fonts (eg. Liberation Serif and many others) Manually entering "Vollkorn" as the font name in LibreOffice makes the font work as expected when made bold and/or italic, but the basic font does not show correctly (it shows as a default sans-serif font instead). This makes me think something might be wrong with Vollkorn- Regular.ttf specifically? This occurs whether I install the fonts-vollkorn package, or download it from elsewhere (e.g. google fonts) and install it using Font Viewer, or by manually putting it in my .fonts folder or usr/share/fonts. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1046609/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1725807] Re: CPU % sort direction (ascending/descending) indicator reversed
the issue you describe seems in fact a theme "bug" like bug #1282897? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-system-monitor in Ubuntu. https://bugs.launchpad.net/bugs/1725807 Title: CPU % sort direction (ascending/descending) indicator reversed Status in gnome-system-monitor package in Ubuntu: Confirmed Bug description: When sorting on a column (in processes tab) I get the standard pyramid shape to indicate ascending/descending sorting, with ascending sort being a pyramid and descending being an upside down pyramid (through natural mapping -- the base of the pyramid is larger than its top). The cpu % column has the two confused. When showing an upside down pyramid the largest values should be at the top (which is how the other columns work, e.g. the ID column). Instead the smallest values are at the top. Description: Ubuntu 17.10 Release: 17.10 gnome-system-monitor: Installed: 3.26.0-1 Candidate: 3.26.0-1 Version table: *** 3.26.0-1 500 500 http://se.archive.ubuntu.com/ubuntu artful/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1725807/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1765261] Re: [regression] Ubuntu 18.04 login screen rejects a valid password on first attempt. Usually works on the second attempt
and what flavor of ubuntu do you recommend me with less bugs like this thanks -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1765261 Title: [regression] Ubuntu 18.04 login screen rejects a valid password on first attempt. Usually works on the second attempt Status in gnome-shell package in Ubuntu: In Progress Status in gnome-shell source package in Bionic: Confirmed Status in gnome-shell package in Fedora: Fix Released Bug description: Upstream: https://gitlab.gnome.org/GNOME/gnome-shell/issues/240 Ubuntu 18.04 login screen rejects a valid password on first attempt. Always works on the second attempt.. This seems to be a new problem, just started today. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 Date: Thu Apr 19 11:16:17 2018 InstallationDate: Installed on 2017-12-12 (127 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1765261/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1725807] Re: CPU % sort direction (ascending/descending) indicator reversed
ignore that comment, other the theme was fixed and the icon is right in e.g nautilus -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-system-monitor in Ubuntu. https://bugs.launchpad.net/bugs/1725807 Title: CPU % sort direction (ascending/descending) indicator reversed Status in gnome-system-monitor package in Ubuntu: Confirmed Bug description: When sorting on a column (in processes tab) I get the standard pyramid shape to indicate ascending/descending sorting, with ascending sort being a pyramid and descending being an upside down pyramid (through natural mapping -- the base of the pyramid is larger than its top). The cpu % column has the two confused. When showing an upside down pyramid the largest values should be at the top (which is how the other columns work, e.g. the ID column). Instead the smallest values are at the top. Description: Ubuntu 17.10 Release: 17.10 gnome-system-monitor: Installed: 3.26.0-1 Candidate: 3.26.0-1 Version table: *** 3.26.0-1 500 500 http://se.archive.ubuntu.com/ubuntu artful/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1725807/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1766875] Re: Firefox and plugin-container (Chrome_ChildThr): segfault at 0 ip, sp error 6 in plugin-container/libxul.so
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: firefox (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1766875 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: Confirmed Bug description: parent report : https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1656065 from parent: ``` Hello Robie. Unfortunately, this problem appeared again. Today, I have had Firefox enabled with just two tabs: YouTube and Google Translate. Suddenly, system start to slow down, disk diode was... red all the time, mouse cursor moved slowly etc. After a couple of minutes, I managed to start terminal and used '$ killall firefox' command, which helped -- system started to work faster again, clicking e.g. on a file, opened Mousepad almost immediately, in milliseconds etc. Log files (such as '/var/log/syslog' or '/var/log/kern.log') contains: ✓ Sep 4 13:46:00 holycross kernel: [10194.439105] Chrome_~dThread[3599]: segfault at 0 ip b03f6b24 sp afaa1040 error 6 in libxul.so[afb73000+570f000] ✓ Sep 4 13:46:00 holycross kernel: [10195.084439] Chrome_~dThread[4040]: segfault at 0 ip b042fb24 sp afada040 error 6 in libxul.so[afbac000+570f000] As we can see, there is a problem in 'libxul.so'. (See bug title.) Firefox version: 55.0.2 (32-bit), e10s enabled (4. processes; changed from 2. after update), four addons, no Flash. RAM memory checked with memtest64 - no problems. I will keep an eye on this, because of a couple of months without problem. Maybe it was just an accident? Thanks, best regards. ``` I can confirm this bug for > ii firefox 59.0.2+build1-0ubuntu0.16.04.3 amd64Safe and easy web browser from Mozilla at Ubuntu16.04.4 LTS. ``` # dmesg [14428059.786531] Chrome_~dThread[20444]: segfault at 0 ip 7f4c6ce2ac26 sp 7f4c6af2eaf0 error 6 in libxul.so[7f4c6bff8000+580f000] [14428067.756104] Chrome_~dThread[20745]: segfault at 0 ip 7f1a0892ac26 sp 7f1a06a2eaf0 error 6 in libxul.so[7f1a07af8000+580f000] [14428067.756260] Chrome_~dThread[20829]: segfault at 0 ip 7f5fe362ac26 sp 7f5fe172eaf0 error 6 in libxul.so[7f5fe27f8000+580f000] ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1766875/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1046609] [NEW] Font family (fonts-vollkorn) appearing as multiple fonts in LibreOffice
You have been subscribed to a public bug: In LibreOffice (at least writer and calc), Vollkorn appears in the font list as "Vollkorn Regular", "Vollkorn Bold", etc. If "Vollkorn Regular" is selected as the font, then made bold/italic, it uses a faux bold/italic, instead of the proper font version. That's the basic problem - here's some additional info: The font works as expected (appears as "Vollkorn", uses e.g. Vollkorn- Bold when made bold) in other applications, such as Inkscape. The files also appears as expected (e.g. Name: Vollkorn, Style: Regular) in Font Viewer. This problem does not occur in LibreOffice with other true type fonts (eg. Liberation Serif and many others) Manually entering "Vollkorn" as the font name in LibreOffice makes the font work as expected when made bold and/or italic, but the basic font does not show correctly (it shows as a default sans-serif font instead). This makes me think something might be wrong with Vollkorn-Regular.ttf specifically? This occurs whether I install the fonts-vollkorn package, or download it from elsewhere (e.g. google fonts) and install it using Font Viewer, or by manually putting it in my .fonts folder or usr/share/fonts. ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: Invalid ** Tags: bot-comment -- Font family (fonts-vollkorn) appearing as multiple fonts in LibreOffice https://bugs.launchpad.net/bugs/1046609 You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice 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 1765261] Re: [regression] Ubuntu 18.04 login screen rejects a valid password on first attempt. Usually works on the second attempt
The bug is in gnome-shell, so anything other than that :) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1765261 Title: [regression] Ubuntu 18.04 login screen rejects a valid password on first attempt. Usually works on the second attempt Status in gnome-shell package in Ubuntu: In Progress Status in gnome-shell source package in Bionic: Confirmed Status in gnome-shell package in Fedora: Fix Released Bug description: Upstream: https://gitlab.gnome.org/GNOME/gnome-shell/issues/240 Ubuntu 18.04 login screen rejects a valid password on first attempt. Always works on the second attempt.. This seems to be a new problem, just started today. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 Date: Thu Apr 19 11:16:17 2018 InstallationDate: Installed on 2017-12-12 (127 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1765261/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp