[Desktop-packages] [Bug 1760338] Re: Touchpad hotkey 'functional' but has no effect in 18.04 (Bionic)
Deleting the synaptics driver resolves the issue. It appears the driver needs to be deleted with the introduction of the libinput driver (now that the synaptics driver has been deprecated). However this issue/bug occurred as the synaptic driver was not deleted during the upgrade to 18.04 from 16.04 (most likely due the the fact that the config file was not empty - however it would be impossible for it to be empty if it was the driver used in 16.04, prior to the introduction of the libinput driver with the 18.04 upgrade). Suggestion: For all future upgrades to 18.04, there is the need to ensure the synaptic driver is removed to avoid breaking this functionality and introducing the conflict. If the user decides he/she needs the deprecated synaptics driver, they can always install it after. This way, Ubuntu 18.04 and beyond would not appear defective in this instance after an upgrade. Affects: Upgrades to 18.04 and newer. Conclusion: This bug can be closed when this is fixed in future releases of Ubuntu. I'm not sure who needs to be communicated about this, can someone please help to see this through to obtain a fix implementation and thus closure? Thanks. -- 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/1760338 Title: Touchpad hotkey 'functional' but has no effect in 18.04 (Bionic) Status in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in xinput package in Ubuntu: Confirmed Status in xserver-xorg-input-synaptics package in Ubuntu: Confirmed Bug description: All the Fn keys are working (audio, mute, bright, volume and even wifi) except for enable/disable touchpad. Does not toggle the touchpad. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xinput 1.6.2-1build1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] É um diretório: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.42 Sat Mar 3 04:10:22 PST 2018 GCC version: gcc version 7.3.0 (Ubuntu 7.3.0-13ubuntu1) ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME Date: Sat Mar 31 15:41:59 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 390.42, 4.15.0-12-generic, x86_64: installed nvidia, 390.42, 4.15.0-13-generic, x86_64: installed virtualbox, 5.2.8, 4.15.0-12-generic, x86_64: installed virtualbox, 5.2.8, 4.15.0-13-generic, x86_64: installed GraphicsCard: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems HD Graphics 530 [1179:f840] InstallationDate: Installed on 2018-03-09 (21 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180309) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 008: ID 04f2:b446 Chicony Electronics Co., Ltd Bus 001 Device 003: ID 248a:8366 Bus 001 Device 002: ID 04f3:2228 Elan Microelectronics Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: TOSHIBA Satellite S55t-C ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic root=UUID=62fa4fcd-f1c6-43f5-a86d-ccaae2565dac ro locale=pt_BR quiet splash vt.handoff=1 SourcePackage: xinput UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/08/2015 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.20 dmi.board.name: 06F4 dmi.board.vendor: FF50 dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis ManuFacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvr1.20:bd10/08/2015:svnTOSHIBA:pnSatelliteS55t-C:pvrPSPUGU-00200D:rvnFF50:rn06F4:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion: dmi.product.family: Type1Family dmi.product.name: Satellite S55t-C dmi.product.version: PSPUGU-00200D dmi.sys.vendor: TOSHIBA version.compiz: compiz N/A 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.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel
[Desktop-packages] [Bug 1795135]
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/xorg/xserver/issues/577. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1795135 Title: XFCE window buttons are not clickable at the top of the screen Status in X.Org X server: Unknown Status in xfce4-panel package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: This bug affects greybird-gtk-theme and xfce4-panel in Xubuntu Cosmic. With Cosmic, it is not possible to click on the window buttons after moving the mouse cursor to the top of the screen. Unlike similar bugs, no amount of moving left or right triggers the hover event or the ability to click on the window button. With Adwaita and Numix, we see the same issues we see elsewhere, where the buttons can sometimes be clicked, but also have issue with the topmost part of the screen. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: greybird-gtk-theme 3.22.9-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5 Uname: Linux 4.18.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Sep 29 09:05:24 2018 InstallationDate: Installed on 2018-09-29 (0 days ago) InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180929) PackageArchitecture: all SourcePackage: greybird-gtk-theme UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1795135/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1795135] Re: XFCE window buttons are not clickable at the top of the screen
** Changed in: xorg-server Status: Confirmed => Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1795135 Title: XFCE window buttons are not clickable at the top of the screen Status in X.Org X server: Unknown Status in xfce4-panel package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: This bug affects greybird-gtk-theme and xfce4-panel in Xubuntu Cosmic. With Cosmic, it is not possible to click on the window buttons after moving the mouse cursor to the top of the screen. Unlike similar bugs, no amount of moving left or right triggers the hover event or the ability to click on the window button. With Adwaita and Numix, we see the same issues we see elsewhere, where the buttons can sometimes be clicked, but also have issue with the topmost part of the screen. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: greybird-gtk-theme 3.22.9-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5 Uname: Linux 4.18.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Sep 29 09:05:24 2018 InstallationDate: Installed on 2018-09-29 (0 days ago) InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180929) PackageArchitecture: all SourcePackage: greybird-gtk-theme UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1795135/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1808927] Re: On fullscreen mode, video playback is somewhat traslucent in Firefox
** Description changed: Description: *In Mozilla Firefox browser and when playing HTML5 fullscreen videos, elements on the Gnome 3 desktop (like floating windows) are somewhat still visible (video isn't 100 % opaque). *The issue occurs only when video is playing, not when paused. Transparency occurs mainly when displaying dark tones (like blues), but not black. *Tested with Youtube, Dailymotion and Vimeo videos. *Tested with official Ubuntu repository package and also with Snap package: issue occurs on both of them. + *chromium-browser package from Ubuntu repository also tested: issue isn't present. System and package details: uname -a Linux * 4.18.0-12-generic #13-Ubuntu SMP Wed Nov 14 15:17:05 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux lsb_release -rd Description: Ubuntu 18.10 Release: 18.10 apt-cache policy firefox firefox: - Instalados: 64.0+build3-0ubuntu0.18.10.1 - Candidato: 64.0+build3-0ubuntu0.18.10.1 - Tabla de versión: - *** 64.0+build3-0ubuntu0.18.10.1 500 - 500 http://archive.ubuntu.com/ubuntu cosmic-updates/main amd64 Packages - 500 http://archive.ubuntu.com/ubuntu cosmic-security/main amd64 Packages - 100 /var/lib/dpkg/status - 63.0+build1-0ubuntu1 500 - 500 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages + Instalados: 64.0+build3-0ubuntu0.18.10.1 + Candidato: 64.0+build3-0ubuntu0.18.10.1 + Tabla de versión: + *** 64.0+build3-0ubuntu0.18.10.1 500 + 500 http://archive.ubuntu.com/ubuntu cosmic-updates/main amd64 Packages + 500 http://archive.ubuntu.com/ubuntu cosmic-security/main amd64 Packages + 100 /var/lib/dpkg/status + 63.0+build1-0ubuntu1 500 + 500 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages Summary: *What is expected to happen: Fullscreen HTML5 video should be 100 % opaque (desktop elements shouldn't be visible at all). *What happened instead: - Desktop elements ares subtly still visible under Fullscreen HTML5 video, only when video is playing (not when paused) and mainly with dark tones, not with black. + Desktop elements are subtly still visible under Fullscreen HTML5 video, only when video is playing (not when paused) and mainly with dark tones, not with black. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: firefox 64.0+build3-0ubuntu0.18.10.1 ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17 Uname: Linux 4.18.0-12-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: julian 3065 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: julian 3065 F pulseaudio BuildID: 20181207224759 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Tue Dec 18 02:02:22 2018 EcryptfsInUse: Yes 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 + # 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-11-15 (32 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) IpRoute: - default via 192.168.0.1 dev wlp2s0 proto dhcp metric 600 - 169.254.0.0/16 dev wlp2s0 scope link metric 1000 - 192.168.0.0/24 dev wlp2s0 proto kernel scope link src 192.168.0.37 metric 600 + default via 192.168.0.1 dev wlp2s0 proto dhcp metric 600 + 169.254.0.0/16 dev wlp2s0 scope link metric 1000 + 192.168.0.0/24 dev wlp2s0 proto kernel scope link src 192.168.0.37 metric 600 Locales: extensions.sqlite corrupt or missing PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=64.0/20181207224759 RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/16/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GL552VW.218 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GL552VW dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGL552VW.218:bd03/16/2016:svnASUSTeKCOMPUTERINC.:pnGL552VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL552VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: GL dmi.product.name: GL552VW dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. -- You received this bug notification because you are a member of Desktop Packages, whic
[Desktop-packages] [Bug 1760338] Re: Touchpad hotkey 'functional' but has no effect in 18.04 (Bionic)
Deleting the synaptics driver resolves the issue. It appears the driver needs to be deleted with the introduction of the libinput driver (now that the synaptics driver has been deprecated). However this issue/bug occurred as the synaptic driver was not deleted during the upgrade to 18.04 from 16.04 (most likely due the the fact that the config file was not empty - however it would be impossible for it to be empty if it was the driver used in 16.04, prior to the introduction of the libinput driver with the 18.04 upgrade). Suggestion: For all future upgrades to 18.04, there is the need to ensure the synaptic driver is removed to avoid breaking this functionality and introducing the conflict. If the user decides he/she needs the deprecated synaptics driver, they can always install it after. This way, Ubuntu 18.04 and beyond would not appear defective in this instance after an upgrade. Affects: Upgrades to 18.04 and newer. Conclusion: This bug can be closed when this is fixed in future releases of Ubuntu. I'm not sure who needs to be communicated about this, can someone help to see this through to ensure fix and thus closure? Thanks. -- 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/1760338 Title: Touchpad hotkey 'functional' but has no effect in 18.04 (Bionic) Status in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in xinput package in Ubuntu: Confirmed Status in xserver-xorg-input-synaptics package in Ubuntu: Confirmed Bug description: All the Fn keys are working (audio, mute, bright, volume and even wifi) except for enable/disable touchpad. Does not toggle the touchpad. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xinput 1.6.2-1build1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] É um diretório: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.42 Sat Mar 3 04:10:22 PST 2018 GCC version: gcc version 7.3.0 (Ubuntu 7.3.0-13ubuntu1) ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME Date: Sat Mar 31 15:41:59 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 390.42, 4.15.0-12-generic, x86_64: installed nvidia, 390.42, 4.15.0-13-generic, x86_64: installed virtualbox, 5.2.8, 4.15.0-12-generic, x86_64: installed virtualbox, 5.2.8, 4.15.0-13-generic, x86_64: installed GraphicsCard: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems HD Graphics 530 [1179:f840] InstallationDate: Installed on 2018-03-09 (21 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180309) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 008: ID 04f2:b446 Chicony Electronics Co., Ltd Bus 001 Device 003: ID 248a:8366 Bus 001 Device 002: ID 04f3:2228 Elan Microelectronics Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: TOSHIBA Satellite S55t-C ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic root=UUID=62fa4fcd-f1c6-43f5-a86d-ccaae2565dac ro locale=pt_BR quiet splash vt.handoff=1 SourcePackage: xinput UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/08/2015 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.20 dmi.board.name: 06F4 dmi.board.vendor: FF50 dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis ManuFacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvr1.20:bd10/08/2015:svnTOSHIBA:pnSatelliteS55t-C:pvrPSPUGU-00200D:rvnFF50:rn06F4:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion: dmi.product.family: Type1Family dmi.product.name: Satellite S55t-C dmi.product.version: PSPUGU-00200D dmi.sys.vendor: TOSHIBA version.compiz: compiz N/A 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.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229
[Desktop-packages] [Bug 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
@sojusnik Yes, you're right, I missed the closing bracket. The correct line to add is: SND_PCI_QUIRK(0x1043, 0x10a1, "ASUS UX391UA", ALC294_FIXUP_ASUS_SPK), You won't find patch_realtek.c anywhere in /lib/modules/ because it's already been compiled and installed. You need to download the source code, apply the patches, then compile and install the kernel. Try downloading the 4.20-rc7 from kernel.org (the patches are already applied to this version), extract it, and then edit /sound/pci/hda/patch_realtek.c Look for this line: SND_PCI_QUIRK(0x1043, 0x14a1, "ASUS UX533FD", ALC294_FIXUP_ASUS_SPK), And beneath it add: SND_PCI_QUIRK(0x1043, 0x10a1, "ASUS UX391UA", ALC294_FIXUP_ASUS_SPK), If you then compile and install the kernel, you should have working sound on your UX391UA. -- 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/1784485 Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: Internal speaker - not sound at all Cable Headphonse - realy quiet disorted sound Bluetooth headphones - sound works fine On Windows 10 everything works fine. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pmichalski 7964 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Jul 30 22:32:10 2018 InstallationDate: Installed on 2018-07-17 (12 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Wbudowany dźwięk - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm2988 F pulseaudio pmichalski 7964 F pulseaudio Symptom_Jack: Mic, Internal Symptom_Type: No sound at all Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX391UA.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX391UA 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.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook S dmi.product.name: ZenBook S UX391UA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1808927] [NEW] On fullscreen mode, video playback is somewhat traslucent in Firefox
Public bug reported: Description: *In Mozilla Firefox browser and when playing HTML5 fullscreen videos, elements on the Gnome 3 desktop (like floating windows) are somewhat still visible (video isn't 100 % opaque). *The issue occurs only when video is playing, not when paused. Transparency occurs mainly when displaying dark tones (like blues), but not black. *Tested with Youtube, Dailymotion and Vimeo videos. *Tested with official Ubuntu repository package and also with Snap package: issue occurs on both of them. *chromium-browser package from Ubuntu repository also tested: issue isn't present. System and package details: uname -a Linux * 4.18.0-12-generic #13-Ubuntu SMP Wed Nov 14 15:17:05 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux lsb_release -rd Description:Ubuntu 18.10 Release:18.10 apt-cache policy firefox firefox: Instalados: 64.0+build3-0ubuntu0.18.10.1 Candidato: 64.0+build3-0ubuntu0.18.10.1 Tabla de versión: *** 64.0+build3-0ubuntu0.18.10.1 500 500 http://archive.ubuntu.com/ubuntu cosmic-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu cosmic-security/main amd64 Packages 100 /var/lib/dpkg/status 63.0+build1-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages Summary: *What is expected to happen: Fullscreen HTML5 video should be 100 % opaque (desktop elements shouldn't be visible at all). *What happened instead: Desktop elements are subtly still visible under Fullscreen HTML5 video, only when video is playing (not when paused) and mainly with dark tones, not with black. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: firefox 64.0+build3-0ubuntu0.18.10.1 ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17 Uname: Linux 4.18.0-12-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: julian 3065 F pulseaudio BuildID: 20181207224759 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Tue Dec 18 02:02:22 2018 EcryptfsInUse: Yes 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-11-15 (32 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) IpRoute: default via 192.168.0.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.0.0/24 dev wlp2s0 proto kernel scope link src 192.168.0.37 metric 600 Locales: extensions.sqlite corrupt or missing PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=64.0/20181207224759 RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/16/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GL552VW.218 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GL552VW dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGL552VW.218:bd03/16/2016:svnASUSTeKCOMPUTERINC.:pnGL552VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL552VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: GL dmi.product.name: GL552VW dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: firefox (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 firefox in Ubuntu. https://bugs.launchpad.net/bugs/1808927 Title: On fullscreen mode, video playback is somewhat traslucent in Firefox Status in firefox package in Ubuntu: New Bug description: Description: *In Mozilla Firefox browser and when playing HTML5 fullscreen videos, elements on the Gnome 3 desktop (like floating windows) are somewhat still visible (video isn't 100 % opaque). *The issue occurs only when video is playing, not when paused. Transparency occurs mainly when displaying dark tones (like blues), but not black. *Tested with Youtube, Dailymotion and Vimeo videos. *Tested with official Ubuntu repository package and also with Snap package: issue occurs on both of them. *chromium-browser package from Ubuntu repository also tested: issue isn't present. System and package details: uname -a Linux * 4.18.0-12-generic #13-Ubuntu SMP Wed Nov 14 15:17:05 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux lsb_release -rd Description: Ubuntu 18.10 Release: 18.10 apt-cache policy firefox fir
[Desktop-packages] [Bug 1749690] Re: hp-setup fails to install plugin
** Changed in: hplip (Ubuntu) Status: Confirmed => Incomplete -- 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/1749690 Title: hp-setup fails to install plugin Status in HPLIP: In Progress Status in hplip package in Ubuntu: Incomplete Status in hplip package in Debian: New Bug description: My HP printer requires a binary driver and the only way to install it is to run hp-setup from hplip package. It was doing job fine for last three years at least, but when I tried to install driver today on a fresh 16.04 installation, it couldn't download it. $ hp-setup -i 192.168.220.10 ... - | PLUG-IN INSTALLATION FOR HPLIP 3.16.3 | - Option Description -- -- d Download plug-in from HP (recommended) p Specify a path to the plug-in (advanced) q Quit hp-plugin (skip installation) Enter option (d=download*, p=specify path, q=quit) ? d --- | DOWNLOAD PLUGIN | --- Checking for network connection... Downloading plug-in from: Downloading plug-in: [\ ] 0% error: Found No Section in /tmp/tmpjeh9zqmg. Please set the http proxy for root and try again. error: file does not match its checksum. File may have been corrupted or altered error: Failed to install Plugin. error: The device you are trying to setup requires a binary plug-in. Some functionalities may not work as expected without plug-ins. Please run 'hp-plugin' as normal user to install plug-ins.Visit http://hplipopensource.com for more infomation. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: hplip 3.16.3+repack0-1 ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CupsErrorLog: CurrentDesktop: Unity Date: Thu Feb 15 14:55:08 2018 InstallationDate: Installed on 2018-01-19 (27 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: Acer Aspire V3-771 Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed root=UUID=07eba8bf-f5de-4911-9574-0416813d1387 ro quiet splash vt.handoff=7 SourcePackage: hplip UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/21/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.28 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA70_HC dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.28:bd10/21/2013:svnAcer:pnAspireV3-771:pvrV2.28:rvnAcer:rnVA70_HC:rvrType2-BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: Type1Family dmi.product.name: Aspire V3-771 dmi.product.version: V2.28 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/1749690/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
@Ben patch_realtek.c is missing under /lib/modules/4.20.0-042000rc7-generic/kernel/sound/pci/hda/ after installing 4.20.0-rc7 kernel. Can't find it elsewhere either. How do you properly applied those 3 patches? And the proper command is: SND_PCI_QUIRK(0x1043, 0x10a1, "ASUS UX391UA", ALC294_FIXUP_ASUS_SPK) You forgot to close the brackets. -- 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/1784485 Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: Internal speaker - not sound at all Cable Headphonse - realy quiet disorted sound Bluetooth headphones - sound works fine On Windows 10 everything works fine. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pmichalski 7964 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Jul 30 22:32:10 2018 InstallationDate: Installed on 2018-07-17 (12 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Wbudowany dźwięk - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm2988 F pulseaudio pmichalski 7964 F pulseaudio Symptom_Jack: Mic, Internal Symptom_Type: No sound at all Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX391UA.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX391UA 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.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook S dmi.product.name: ZenBook S UX391UA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1794282] Re: warning dialog when closing multiple private tabs can become unresponsive
Thanks for following up. I'm closing the report, feel free to re-open it in the future should the problem arise again. ** Changed in: firefox (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1794282 Title: warning dialog when closing multiple private tabs can become unresponsive Status in firefox package in Ubuntu: Invalid Bug description: Affecting Firefox 60 with Ubuntu 18.04.1: (Private Browsing) When closing down Private Browsing with 2 tabs or more, the 'warning' dialog box appears but if no selection is made after a while, the 'Gnome' dialog box appears behind it incorrectly indicating Firefox is 'unresponsive'. This causes the application to freeze as no selection can then be made as the 'Gnome' dialog box's selection is hidden (inactive window) behind Firefox's 'warning' dialog box (active window) which has now frozen (...awaiting the 'Gnome' dialog box's selection which cannot be made!) Thank you for passing this on to the appropriate teams for action. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1794282/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1807127] Re: Fixing bug #1795668 breaks thumbnail creation on 32-bit Ubuntu
This bug was fixed in the package gnome-desktop3 - 3.28.2-0ubuntu1.2 --- gnome-desktop3 (3.28.2-0ubuntu1.2) bionic-security; urgency=medium * Cherry-pick thumbnail-Handle-non-usrmerged-systems.patch: - Fix thumbnailer on 32-bit systems where /lib64 is not available. This fixes a regression introduced in the previous update. (LP: #1807127) -- Jeremy Bicha Tue, 11 Dec 2018 10:19:39 -0500 ** Changed in: gnome-desktop3 (Ubuntu Bionic) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-desktop3 in Ubuntu. https://bugs.launchpad.net/bugs/1807127 Title: Fixing bug #1795668 breaks thumbnail creation on 32-bit Ubuntu Status in gnome-desktop3 package in Ubuntu: Fix Released Status in gnome-desktop3 source package in Bionic: Fix Released Status in gnome-desktop3 source package in Cosmic: In Progress Bug description: Impact == Thumbnailing doesn't work on Ubuntu 18.04 LTS or 18.10 on 32-bit installs. Test Case = Install Ubuntu 18.10 32-bit Install the update. Log out and log back in. Download a picture from the internet. Open your file browser to the directory that contains the picture. The file should show a thumbnail preview. Regression Potential This fix was cherry-picked to the stable gnome-3-30 branch. It was additionally tested by Iain Lane on usrmerged and non-usrmerged systems. (We don't support usrmerge for Ubuntu 18.04 LTS or 18.10.) Other Info == Triaged as Critical for 18.04 LTS since this was a regression introduced in the security update that backported the bubblewrap hardening to the gnome-desktop3 thumbnailer. Original Bug Report === Fixing bug #1795668 breaks thumbnail creation on 32-bit Ubuntu. Looks like same issue in upstream - https://bugzilla.redhat.com/show_bug.cgi?id=1651952 Cause - bubblewrap runs with --ro-bind /lib64 option, then fails. Workaround - create empty /lib64 directory at root. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libgnome-desktop-3-17 3.28.2-0ubuntu1.1 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic i686 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: i386 CurrentDesktop: ubuntu:GNOME Date: Thu Dec 6 12:07:28 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-desktop3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-desktop3/+bug/1807127/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1713448] Re: Adobe Reader doesn't print on OKI C911
[Expired for cups (Ubuntu) because there has been no activity for 60 days.] ** Changed in: cups (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1713448 Title: Adobe Reader doesn't print on OKI C911 Status in cups package in Ubuntu: Expired Status in linux package in Ubuntu: Invalid Bug description: Out and over. I tried whatever I could think of, but whatever I send there, anything will make the printer blink, 'processing', forever, until I cancel the job. The printer, however, prints the same files from okular, and from all other applications that I have tried so far. This would clearly point to acroread. However, acroread prints to all other printers that we have standing about without any problem. Logically, from what I could state so far, we have an AND-combination: everything works, except I print a file from acroread through OKI C911. Since I have other printers and other PDF-software, it is minor. And yet, I wouldn't mind helping to debug this thing. I'm using the OKI-provided ppd with cups. adobereader-enu:i386 9.5.5 cups 2.1.3-4 --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CupsErrorLog: E [31/Aug/2018:11:08:02 +0200] Missing value on line 617 of /var/cache/cups/job.cache. E [31/Aug/2018:11:08:02 +0200] Missing value on line 668 of /var/cache/cups/job.cache. E [31/Aug/2018:11:08:02 +0200] Missing value on line 4277 of /var/cache/cups/job.cache. CurrentDesktop: KDE DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2015-04-01 (1247 days ago) InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.1) Lpstat: device for BrotherColourMFC9970: socket://134.91.100.26:9100 device for Hewlett-Packard_Hewlett-Packard_hp_color_LaserJet_4600: dnssd://hp%20color%20LaserJet%204600%40IC07CA93._printer._tcp.local/ device for OKI_C911: dnssd://OKIC911-BB319._pdl-datastream._tcp.local/ device for Samsung_M262x_282x_Series: dnssd://Samsung%20M262x%20282x%20Series%20(SEC001599EE3069)._printer._tcp.local/ MachineType: LENOVO 2924WEG Package: linux PackageArchitecture: amd64 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/BrotherColourMFC9970.ppd', '/etc/cups/ppd/OKI_C911.ppd', '/etc/cups/ppd/Samsung_M262x_282x_Series.ppd', '/etc/cups/ppd/Hewlett-Packard_Hewlett-Packard_hp_color_LaserJet_4600.ppd'] failed with exit code 2: grep: /etc/cups/ppd/BrotherColourMFC9970.ppd: Permission denied grep: /etc/cups/ppd/OKI_C911.ppd: Permission denied grep: /etc/cups/ppd/Samsung_M262x_282x_Series.ppd: Permission denied grep: /etc/cups/ppd/Hewlett-Packard_Hewlett-Packard_hp_color_LaserJet_4600.ppd: Permission denied ProcCmdline: BOOT_IMAGE=/vmlinuz-4.4.0-134-generic root=UUID=8d3acd2e-2a7f-42ba-b873-b819283b6144 ro quiet splash vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-134-generic root=UUID=8d3acd2e-2a7f-42ba-b873-b819283b6144 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-134.160-generic 4.4.140 Tags: xenial Uname: Linux 4.4.0-134-generic x86_64 UpgradeStatus: Upgraded to xenial on 2018-08-15 (15 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/11/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 6UET70WW (1.50 ) dmi.board.name: 2924WEG 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:bvr6UET70WW(1.50):bd10/11/2012:svnLENOVO:pn2924WEG:pvrThinkPadT410s:rvnLENOVO:rn2924WEG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2924WEG dmi.product.version: ThinkPad T410s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1713448/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1798547] Re: high usage cpu due to /usr/bin/gnome-shell
[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Expired -- 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/1798547 Title: high usage cpu due to /usr/bin/gnome-shell Status in gnome-shell package in Ubuntu: Expired Bug description: PC Specs: i5-6200U 8GB RAM Nvidia GeForce 930m I'm new to Ubuntu, and I just freshly installed Ubuntu 18.04 and I have noticed that my cpu fans are always on. I installed "htop" to see what was the cause, and it turns out that gnome-shell usually goes to 100%, on one core, while ram being at 2.11GB... Is there any fix? PC doesn't slow down but fans constantly spinning is annoying. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.3-0ubuntu0.18.04.2 Uname: Linux 4.18.14-041814-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Oct 18 09:37:39 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-10-16 (1 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1798547/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1798532] Re: DNS setting from Settings/Network GUI does not take effect
[Expired for gnome-control-center (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-control-center (Ubuntu) Status: Incomplete => Expired -- 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/1798532 Title: DNS setting from Settings/Network GUI does not take effect Status in gnome-control-center package in Ubuntu: Expired Bug description: Ubuntu 18.04LTS ThinkPad T480s ThinkPad Dock I'm connected to office network via ethernet cable. The Settings->Network->PCI Ethernet or USB Ethernet shows that the DNS should be 192.168.101.201 This is the correct IP for the Windows Server 2003 nameserver in the office network. See screenshot. However, it seems that this nameserver is not used. Related information: /etc/nsswitch.conf ... hosts: files dns mdns4_minimal [NOTFOUND=return] myhostname ... /etc/resolv.conf only has one nameserver. (If I manually add 192.168.101.201, it works.) nameserver 127.0.0.53 $ nslookup -v etb-git.mcint.local Server: 127.0.0.53 Address: 127.0.0.53#53 ** server can't find etb-git.mcint.local: SERVFAIL $ host -v etb-git.mcint.local Trying "etb-git.mcint.local" Host etb-git.mcint.local not found: 2(SERVFAIL) Received 37 bytes from 127.0.0.53#53 in 0 ms ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.2 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Oct 18 09:46:34 2018 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2018-05-10 (161 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1798532/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1798533] Re: Drucker
[Expired for gnome-control-center (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-control-center (Ubuntu) Status: Incomplete => Expired -- 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/1798533 Title: Drucker Status in gnome-control-center package in Ubuntu: Expired Bug description: Der Drucker kann nicht installiert werden. Filter fehlt (Fehlermeldung) ? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CompositorRunning: None Date: Thu Oct 18 08:47:12 2018 DistUpgraded: 2018-10-17 18:15:17,451 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Kindprozess »./xorg_fix_proprietary.py« konnte nicht ausgeführt werden (No such file or directory) (8)) DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 7340] [1002:9808] (prog-if 00 [VGA controller]) Subsystem: Lenovo Wrestler [Radeon HD 7340] [17aa:365d] InstallationDate: Installed on 2018-03-08 (223 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: LENOVO 6596 ProcEnviron: PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=ae1dcc47-b3c8-4069-bedd-acb8c12fdbfb ro drm.debug=0xe plymouth:debug SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-10-17 (0 days ago) dmi.bios.date: 08/28/2012 dmi.bios.vendor: LENOVO dmi.bios.version: EKKT25BUS dmi.board.name: Remore CRB dmi.board.vendor: LENOVO dmi.board.version: Win8 STD MM DPK IPG dmi.chassis.type: 13 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnLENOVO:bvrEKKT25BUS:bd08/28/2012:svnLENOVO:pn6596:pvrLenovoC445:rvnLENOVO:rnRemoreCRB:rvrWin8STDMMDPKIPG:cvnToBeFilledByO.E.M.:ct13:cvrToBeFilledByO.E.M.: dmi.product.family: IdeaCentre dmi.product.name: 6596 dmi.product.version: Lenovo C445 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.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-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 xserver.bootTime: Wed Oct 17 11:04:23 2018 xserver.configfile: default xserver.devices: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.4-0ubuntu0.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1798533/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1807056] Re: Occasional Keyboard freeze
I installed Cinnamon DE from ppa:embrosyn/cinnamon . I will let you know if the problem happens again. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1807056 Title: Occasional Keyboard freeze Status in gnome-shell package in Ubuntu: Incomplete Bug description: I am using 18.04 and sometimes, whatever I type does not work. It is as if there is no keyboard connected while I have my laptop keyboard and an external keyboard connected to the machine. I even enabled On Screen Keyboard and tried to type through it. Same result. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.3-0ubuntu0.18.04.3 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: communitheme:ubuntu:GNOME Date: Thu Dec 6 05:41:04 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-11-29 (6 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1807056/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1794282] Re: warning dialog when closing multiple private tabs can become unresponsive
Very much appreciate your taking the time to follow up on this. After quite some struggles and hesitation I've gone ahead to re-install Firefox. Having done so, I'm am now no longer able to observe or reproduce the issue reported. In answer to your comments: - I never get a warning when closing normal window with several tabs open, only when closing private windows with multiple tabs. (which appears to be the opposite of what you are seeing) Noted that this has been an on-going inconsistency in implementation requirements/intentions from Mozilla. - 10 minutes is more than enough to have observed the issue. I believe this issue should therefore now be closed here. If it does re-surface in the future, I will re-open it. Thanks. -- 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/1794282 Title: warning dialog when closing multiple private tabs can become unresponsive Status in firefox package in Ubuntu: Incomplete Bug description: Affecting Firefox 60 with Ubuntu 18.04.1: (Private Browsing) When closing down Private Browsing with 2 tabs or more, the 'warning' dialog box appears but if no selection is made after a while, the 'Gnome' dialog box appears behind it incorrectly indicating Firefox is 'unresponsive'. This causes the application to freeze as no selection can then be made as the 'Gnome' dialog box's selection is hidden (inactive window) behind Firefox's 'warning' dialog box (active window) which has now frozen (...awaiting the 'Gnome' dialog box's selection which cannot be made!) Thank you for passing this on to the appropriate teams for action. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1794282/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1808903] Re: cannot connect LG Smart TV using HDMI Cable
This is somewhat expected. TVs have no need to offer many resolution options other than standard broadcast formats. TVs (if using HDMI) are also required to limit colour resolution compared to monitors, but that might not be what you're talking about... What options are missing that you expected? Are you sure this is a bug in Ubuntu? ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1808903 Title: cannot connect LG Smart TV using HDMI Cable Status in gnome-shell package in Ubuntu: Incomplete Bug description: when I tried connecting to the LG smart TV with an HDMI cable. Display options are very limited, unlike when I connect to an LG monitor using a VGA cable. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.3-0ubuntu0.18.04.3 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Dec 18 09:55:20 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-09-28 (80 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1808903/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1808903] Re: cannot connect LG Smart TV using HDMI Cable
** 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-shell in Ubuntu. https://bugs.launchpad.net/bugs/1808903 Title: cannot connect LG Smart TV using HDMI Cable Status in gnome-shell package in Ubuntu: New Bug description: when I tried connecting to the LG smart TV with an HDMI cable. Display options are very limited, unlike when I connect to an LG monitor using a VGA cable. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.3-0ubuntu0.18.04.3 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Dec 18 09:55:20 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-09-28 (80 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1808903/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1716857] Re: gdm3, hybrid nvidia with modeset=1, no external monitors detected
18.10 Lightdm works but GDM works only with the mentioned hack/workaround (but with slowdowns): ExecStartPre=/usr/bin/xinit /usr/share/gdm/generate-config -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1716857 Title: gdm3, hybrid nvidia with modeset=1, no external monitors detected Status in gdm3 package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in gdm3 package in Debian: New Bug description: Context: 17.10 development packages, nvidia binary driver 375, modeset=1 for the nvidia driver. ubuntu desktop (gnome shell), fresh install ThinkPad W520 in Nvidia Optimus bios mode. Nvidia profile. Result: no external monitors are detected. xrandr does not even list them as disconnected (normally it would list five external disconnected monitors) lsmod shows that nvidia driver is loaded and the modesetting is working at some level because there is no tearing on the laptop panel Note: modeset=1 is the only way to get flicker-free graphics on the laptop panel. modeset=1 is not the default setting but it is highly desirable. It works if lightdm is used which is why I have reported this against gdm3 My sessions in this configuration have mostly crashed after a few minutes with a gdm3 fail whale message in syslog but nothing else looks interesting. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1808880] Re: crashes while adding feedback to package
** 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-software in Ubuntu. https://bugs.launchpad.net/bugs/1808880 Title: crashes while adding feedback to package Status in gnome-software package in Ubuntu: New Bug description: see screenshot ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-software 3.28.1-0ubuntu4.18.04.8 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Dec 18 01:25:58 2018 InstallationDate: Installed on 2018-12-16 (1 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-limba N/A gnome-software-plugin-snap3.28.1-0ubuntu4.18.04.8 SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1808880/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1808806] Re: ????
** 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 xorg in Ubuntu. https://bugs.launchpad.net/bugs/1808806 Title: Status in xorg package in Ubuntu: New Bug description: ? ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-140.166-generic 4.4.162 Uname: Linux 4.4.0-140-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Mon Dec 17 13:48:00 2018 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Skylake Integrated Graphics [1028:078c] InstallationDate: Installed on 2018-11-16 (30 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. Inspiron 15-3567 ProcEnviron: LANGUAGE=fr_LU:fr PATH=(custom, no user) LANG=fr_LU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-140-generic.efi.signed root=UUID=12ce8976-9f9f-49bf-ae0c-ba49a024ad56 ro locale=fr_FR quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/20/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.1 dmi.board.name: 0FGN4M dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.4.1:bd04/20/2018:svnDellInc.:pnInspiron15-3567:pvr:rvnDellInc.:rn0FGN4M:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 15-3567 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Mon Dec 17 10:02:54 2018 xserver.configfile: default xserver.errors: evdev: "USB OPTICAL MOUSE ": Unable to open evdev device "/dev/input/event7". PreInit returned 2 for ""USB OPTICAL MOUSE "" SynPS/2 Synaptics TouchPad: Read error 19 xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5595 vendor CMN xserver.version: 2:1.18.4-0ubuntu0.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1808806/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1808607] Re: package tex-common 6.04ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tex-common in Ubuntu. https://bugs.launchpad.net/bugs/1808607 Title: package tex-common 6.04ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in tex-common package in Ubuntu: New Bug description: Guys Ive had this error constantly of ages now. Does anyone know what it means and more importantly how to fix it? Cheers and TIA. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: tex-common 6.04ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-133.159-generic 4.4.134 Uname: Linux 4.4.0-133-generic i686 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.18 Architecture: i386 Date: Sat Dec 15 06:28:14 2018 DpkgHistoryLog: Start-Date: 2018-12-15 06:23:42 Commandline: aptdaemon role='role-upgrade-system' sender=':1.93' Upgrade: update-manager-core:i386 (1:16.04.12, 1:16.04.13), libsystemd0:i386 (229-4ubuntu21.2, 229-4ubuntu21.4), update-manager:i386 (1:16.04.12, 1:16.04.13), gnome-software:i386 (3.20.5-0ubuntu0.16.04.10, 3.20.5-0ubuntu0.16.04.11), udev:i386 (229-4ubuntu21.2, 229-4ubuntu21.4), libudev1:i386 (229-4ubuntu21.2, 229-4ubuntu21.4), libudev-dev:i386 (229-4ubuntu21.2, 229-4ubuntu21.4), ubuntu-software:i386 (3.20.5-0ubuntu0.16.04.10, 3.20.5-0ubuntu0.16.04.11), python3-update-manager:i386 (1:16.04.12, 1:16.04.13), systemd-sysv:i386 (229-4ubuntu21.2, 229-4ubuntu21.4), libpam-systemd:i386 (229-4ubuntu21.2, 229-4ubuntu21.4), systemd:i386 (229-4ubuntu21.2, 229-4ubuntu21.4), gnome-software-common:i386 (3.20.5-0ubuntu0.16.04.10, 3.20.5-0ubuntu0.16.04.11) ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2012-10-14 (2252 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 (20120817.3) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.27 SourcePackage: tex-common Title: package tex-common 6.04ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tex-common/+bug/1808607/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1808607] Re: package tex-common 6.04ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
** 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 tex-common in Ubuntu. https://bugs.launchpad.net/bugs/1808607 Title: package tex-common 6.04ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in tex-common package in Ubuntu: New Bug description: Guys Ive had this error constantly of ages now. Does anyone know what it means and more importantly how to fix it? Cheers and TIA. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: tex-common 6.04ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-133.159-generic 4.4.134 Uname: Linux 4.4.0-133-generic i686 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.18 Architecture: i386 Date: Sat Dec 15 06:28:14 2018 DpkgHistoryLog: Start-Date: 2018-12-15 06:23:42 Commandline: aptdaemon role='role-upgrade-system' sender=':1.93' Upgrade: update-manager-core:i386 (1:16.04.12, 1:16.04.13), libsystemd0:i386 (229-4ubuntu21.2, 229-4ubuntu21.4), update-manager:i386 (1:16.04.12, 1:16.04.13), gnome-software:i386 (3.20.5-0ubuntu0.16.04.10, 3.20.5-0ubuntu0.16.04.11), udev:i386 (229-4ubuntu21.2, 229-4ubuntu21.4), libudev1:i386 (229-4ubuntu21.2, 229-4ubuntu21.4), libudev-dev:i386 (229-4ubuntu21.2, 229-4ubuntu21.4), ubuntu-software:i386 (3.20.5-0ubuntu0.16.04.10, 3.20.5-0ubuntu0.16.04.11), python3-update-manager:i386 (1:16.04.12, 1:16.04.13), systemd-sysv:i386 (229-4ubuntu21.2, 229-4ubuntu21.4), libpam-systemd:i386 (229-4ubuntu21.2, 229-4ubuntu21.4), systemd:i386 (229-4ubuntu21.2, 229-4ubuntu21.4), gnome-software-common:i386 (3.20.5-0ubuntu0.16.04.10, 3.20.5-0ubuntu0.16.04.11) ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2012-10-14 (2252 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 (20120817.3) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.27 SourcePackage: tex-common Title: package tex-common 6.04ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tex-common/+bug/1808607/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1808607] Re: package tex-common 6.04ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Here's the notes from the upgrade logs; I hope this helps. Setting up tex-common (6.04ubuntu1) ... Ignoring /etc/texmf/texmf.d/05TeXMF.cnf during generation of texmf.cnf, please remove manually! Ignoring /etc/texmf/texmf.d/15Plain.cnf during generation of texmf.cnf, please remove manually! Ignoring /etc/texmf/texmf.d/45TeXinputs.cnf during generation of texmf.cnf, please remove manually! Ignoring /etc/texmf/texmf.d/55Fonts.cnf during generation of texmf.cnf, please remove manually! Ignoring /etc/texmf/texmf.d/65BibTeX.cnf during generation of texmf.cnf, please remove manually! Ignoring /etc/texmf/texmf.d/75DviPS.cnf during generation of texmf.cnf, please remove manually! Ignoring /etc/texmf/texmf.d/80DVIPDFMx.cnf during generation of texmf.cnf, please remove manually! Ignoring /etc/texmf/texmf.d/85Misc.cnf during generation of texmf.cnf, please remove manually! Ignoring /etc/texmf/texmf.d/90TeXDoc.cnf during generation of texmf.cnf, please remove manually! Ignoring /etc/texmf/texmf.d/95NonPath.cnf during generation of texmf.cnf, please remove manually! Warning: Old configuration style found in /etc/texmf/updmap.d Warning: For now these files have been included, Warning: but expect inconsistencies. Warning: These packages should be rebuild with tex-common. Warning: Please see /usr/share/doc/tex-common/NEWS.Debian.gz Warning: found file: /etc/texmf/updmap.d/00updmap.cfg Warning: found file: /etc/texmf/updmap.d/10lmodern.cfg Warning: found file: /etc/texmf/updmap.d/10texlive-base.cfg Warning: found file: /etc/texmf/updmap.d/10texlive-games.cfg Warning: found file: /etc/texmf/updmap.d/10texlive-latex-base.cfg Running mktexlsr. This may take some time... done. Running updmap-sys. This may take some time... updmap-sys failed. Output has been stored in /tmp/updmap.IaLbQJwA Please include this file if you report a bug. Sometimes, not accepting conffile updates in /etc/texmf/updmap.d causes updmap-sys to fail. Please check for files with extension .dpkg-dist or .ucf-dist in this directory -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tex-common in Ubuntu. https://bugs.launchpad.net/bugs/1808607 Title: package tex-common 6.04ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in tex-common package in Ubuntu: New Bug description: Guys Ive had this error constantly of ages now. Does anyone know what it means and more importantly how to fix it? Cheers and TIA. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: tex-common 6.04ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-133.159-generic 4.4.134 Uname: Linux 4.4.0-133-generic i686 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.18 Architecture: i386 Date: Sat Dec 15 06:28:14 2018 DpkgHistoryLog: Start-Date: 2018-12-15 06:23:42 Commandline: aptdaemon role='role-upgrade-system' sender=':1.93' Upgrade: update-manager-core:i386 (1:16.04.12, 1:16.04.13), libsystemd0:i386 (229-4ubuntu21.2, 229-4ubuntu21.4), update-manager:i386 (1:16.04.12, 1:16.04.13), gnome-software:i386 (3.20.5-0ubuntu0.16.04.10, 3.20.5-0ubuntu0.16.04.11), udev:i386 (229-4ubuntu21.2, 229-4ubuntu21.4), libudev1:i386 (229-4ubuntu21.2, 229-4ubuntu21.4), libudev-dev:i386 (229-4ubuntu21.2, 229-4ubuntu21.4), ubuntu-software:i386 (3.20.5-0ubuntu0.16.04.10, 3.20.5-0ubuntu0.16.04.11), python3-update-manager:i386 (1:16.04.12, 1:16.04.13), systemd-sysv:i386 (229-4ubuntu21.2, 229-4ubuntu21.4), libpam-systemd:i386 (229-4ubuntu21.2, 229-4ubuntu21.4), systemd:i386 (229-4ubuntu21.2, 229-4ubuntu21.4), gnome-software-common:i386 (3.20.5-0ubuntu0.16.04.10, 3.20.5-0ubuntu0.16.04.11) ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2012-10-14 (2252 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 (20120817.3) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.27 SourcePackage: tex-common Title: package tex-common 6.04ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tex-common/+bug/1808607/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1716857] Re: gdm3, hybrid nvidia with modeset=1, no external monitors detected
** Tags removed: artful ** Tags added: cosmic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1716857 Title: gdm3, hybrid nvidia with modeset=1, no external monitors detected Status in gdm3 package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in gdm3 package in Debian: New Bug description: Context: 17.10 development packages, nvidia binary driver 375, modeset=1 for the nvidia driver. ubuntu desktop (gnome shell), fresh install ThinkPad W520 in Nvidia Optimus bios mode. Nvidia profile. Result: no external monitors are detected. xrandr does not even list them as disconnected (normally it would list five external disconnected monitors) lsmod shows that nvidia driver is loaded and the modesetting is working at some level because there is no tearing on the laptop panel Note: modeset=1 is the only way to get flicker-free graphics on the laptop panel. modeset=1 is not the default setting but it is highly desirable. It works if lightdm is used which is why I have reported this against gdm3 My sessions in this configuration have mostly crashed after a few minutes with a gdm3 fail whale message in syslog but nothing else looks interesting. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1723025] Re: no login screen when booting with an external monitor attached
Thank you for reporting this bug to Ubuntu. Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: gdm3 (Ubuntu) Status: Confirmed => Won't Fix -- 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/1723025 Title: no login screen when booting with an external monitor attached Status in Release Notes for Ubuntu: Fix Released Status in gdm3 package in Ubuntu: Won't Fix Bug description: Setup: Laptop + external monitor On this machine, if an external display is attached it is considered as the primary display and it disables the internal display. Then all the output goes to the external display (including grub and boot messages) But when gdm comes up, it considers the internal display as the primary display. The internal display stays off and the login dialog in not visible. The external display is all purple and it is not possible to switch to the laptop internal monitor either with the keyboard function keys or by unplugging the cable. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gdm3 3.26.1-3ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4 Uname: Linux 4.13.0-15-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 Date: Thu Oct 12 09:40:56 2017 InstallationDate: Installed on 2013-09-03 (1499 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902) ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.custom.conf: 2017-09-06T19:41:19.336760 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1723025/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1766440] Re: GDM does not default to primary monitor
*** This bug is a duplicate of bug 1760849 *** https://bugs.launchpad.net/bugs/1760849 Sorry, this actually sounds like bug 1760849. ** This bug is no longer a duplicate of bug 1723025 no login screen when booting with an external monitor attached ** This bug has been marked a duplicate of bug 1760849 Enhancement: Make the login screen follow the mouse to other monitors -- 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/1766440 Title: GDM does not default to primary monitor Status in gdm3 package in Ubuntu: New Bug description: I have my monitor in the hdmi port of my gtx780 and my tv in the displayport. Something about X seems to have a bias towards the dp output. During the installer I had to unplug the tv (displayport) and continue the installation. When I plug it in I have to use super + p to switch to 'extend' instead of duplicate. This has a high probability to make the mouse unable to click anywhere in gnome. From this point I am able to set my monitor as the primary monitor and gnome works as expected. I rebooted and gdm still defaulted to my secondary (dp) monitor. I blindly logged in (enter + password + enter) and the desktop switched a few times between tv as default and monitor as default. It finally settled on the monitor as default however I could not click anywhere in gnome. I was able to get control again by pressing the window button, typing and opening a program, from here I was able to alt-tab to the program and was able to click on the desktop again. From here I went to settings to verify my settings and saw that my setting of the monitor (hdmi) as the primary monitor was still there. I suspect grub is defaulting to displayport, passing this default to gdm, then once gdm exits and gnome is loaded the proper default is restored. However Gnome is not in 'focus' for some reason and it takes work to fix this. A separate effort should probably be crated around the super + p display switching dialog as it has a high probability of locking a user out of the session. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 NonfreeKernelModules: wl 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 390.48 Thu Mar 22 00:42:57 PDT 2018 GCC version: gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. ApportVersion: 2.20.9-0ubuntu6 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: communitheme:ubuntu:GNOME Date: Tue Apr 24 00:25:36 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.15.0-15-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 4.15.0-19-generic, x86_64: installed nvidia, 390.48, 4.15.0-15-generic, x86_64: installed nvidia, 390.48, 4.15.0-19-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GK110 [GeForce GTX 780] [10de:1004] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GK110 [GeForce GTX 780] [3842:0783] InstallationDate: Installed on 2018-04-22 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) MachineType: System manufacturer System Product Name ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-15-generic.efi.signed root=UUID=559e0f30-0db2-4199-9f55-98c68bfee444 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/20/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1201 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z77-I DELUXE dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1201:bd06/20/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCO
[Desktop-packages] [Bug 1808826] Re: install intel draphic drivers
Ubuntu already comes with Intel graphics drivers and your logs seem to show they are working. What is the problem you are reporting? ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1808826 Title: install intel draphic drivers Status in Ubuntu: Incomplete Bug description: for Ubuntu 16.04 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-140.166-generic 4.4.162 Uname: Linux 4.4.0-140-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: i386 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Dec 17 07:16:01 2018 DistUpgraded: 2018-12-15 10:13:31,867 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0042] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Core Processor Integrated Graphics Controller [103c:170b] InstallationDate: Installed on 2018-11-26 (20 days ago) InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release i386 (20130213) MachineType: Hewlett-Packard HP Z200 Workstation ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-140-generic root=UUID=62803ccc-2439-44dd-bfbd-535f9af3ea72 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2018-12-15 (1 days ago) dmi.bios.date: 03/09/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786H3 v01.13 dmi.board.asset.tag: 2UA12218BX dmi.board.name: 0B40h dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: 2UA12218BX dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr786H3v01.13:bd03/09/2011:svnHewlett-Packard:pnHPZ200Workstation:pvr:rvnHewlett-Packard:rn0B40h:rvr:cvnHewlett-Packard:ct6:cvr: dmi.product.name: HP Z200 Workstation dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Mon Dec 17 06:37:20 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.4-0ubuntu0.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1808826/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1805699] Re: System goes to sleep with external monitor and lid closed after login
** Changed in: gdm3 (Ubuntu) Status: Incomplete => Invalid -- 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/1805699 Title: System goes to sleep with external monitor and lid closed after login Status in gdm3 package in Ubuntu: Invalid Bug description: This is more or less a duplicate of https://bugs.launchpad.net/bugs/1716160 (i just copied the title), I'm opening a new bug as per comment https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716160/comments/31. I'm experiencing the same thing in Ubuntu 18.04: - Boot the laptop with external screen connected - Close the lid - The laptop continues to boot and reaches the login screen - Insert password - The laptop goes to sleep, i have to open and close the lid to make it wake up - Then it works without problems when i close the lid again This happens in the last days, maybe the bug appeared again with some update. Let me know if something can be done to help to debug the issue. lsb_release -rd: Description: Ubuntu 18.04.1 LTS Release: 18.04 apt-cache policy gdm3 gdm3: Installato: 3.28.3-0ubuntu18.04.3 Candidato: 3.28.3-0ubuntu18.04.3 Tabella versione: *** 3.28.3-0ubuntu18.04.3 500 500 http://it.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.28.2-0ubuntu1.4 500 500 http://it.archive.ubuntu.com/ubuntu bionic-security/main amd64 Packages 3.28.0-0ubuntu1 500 500 http://it.archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1805699/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1799242] Re: gnome-shell crashes when locking screen while dock widget is in focus
*** This bug is a duplicate of bug 1725312 *** https://bugs.launchpad.net/bugs/1725312 Thanks. That is bug 1725312, which was fixed in 18.04 updates a month ago. If you have any further issues then please open a new bug. ** This bug has been marked a duplicate of bug 1725312 gnome-shell crashed with SIGSEGV in st_widget_style_changed() from st_scroll_view_style_changed() -- 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/1799242 Title: gnome-shell crashes when locking screen while dock widget is in focus Status in gnome-shell package in Ubuntu: Incomplete Bug description: gnome-shell crashes with signal 11 (segmentation fault) when I try to lock the screen while a widget in the dock is in focus. The end result is that the screen either does not lock, and gnome-shell reloads, or it hangs (can move mouse, but mouse clicks or keyboard presses don't seem to have any effect). Either way no screen lock occurs. This is on a dual-screen setup, where I have the dock visible on both screens. Steps to reproduce: 1) Open a terminal (or any app, terminal is just an example) 2) Open a new terminal with cntrl+N 3) Click on the terminal icon on the dock, so it shows both instances of the terminal app 4) Try to lock the screen with super+L 5) Observe crash Attached is the output of syslog at the exact moment the crash occurs. Output of lsb_release -rd: Description: Ubuntu 18.04.1 LTS Release: 18.04 Output of apt-cache policy gnome-shell: gnome-shell: Installed: 3.28.3-0ubuntu0.18.04.2 Candidate: 3.28.3-0ubuntu0.18.04.2 Version table: *** 3.28.3-0ubuntu0.18.04.2 500 500 http://nl.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.28.1-0ubuntu2 500 500 http://nl.archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1799242/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1766974] Re: (EE) /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied
** Summary changed: - /dev/dri/card0 + (EE) /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied ** Changed in: xorg-server (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1766974 Title: (EE) /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied Status in X.Org X server: New Status in xorg-server package in Ubuntu: New Bug description: There are very many bugs reported recently against xorg with a commmon theme the following are just 2 examples from the various xorg logs (EE) /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied (EE) intel(0): [drm] failed to set drm interface version: Permission denied [13]. --- ProblemType: Bug .tmp.unity_support_test.1: ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: 2018-08-16 10:03:18,003 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo Core Processor Integrated Graphics Controller [17aa:215a] InstallationDate: Installed on 2016-09-24 (757 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: LENOVO 2519Y11 Package: xorg-server (not installed) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=58d362c2-ed1e-479b-84f5-e5d8a782b08f ro quiet nomodeset ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Renderer: Software Tags: bionic ubuntu Uname: Linux 4.15.0-36-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-08-16 (66 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/14/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 6IET85WW (1.45 ) dmi.board.name: 2519Y11 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:bvr6IET85WW(1.45):bd02/14/2013:svnLENOVO:pn2519Y11:pvrThinkPadT410:rvnLENOVO:rn2519Y11:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T410 dmi.product.name: 2519Y11 dmi.product.version: ThinkPad T410 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.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 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 1:18.0.1-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 xserver.bootTime: Mon Oct 22 07:25:26 2018 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory open /dev/dri/card0: No such file or directory Screen 0 deleted because of no matching config section. AIGLX: reverting to software rendering xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.6-1ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1766974/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1747646] Re: Authentication error with google drive
This bug seems to not have been fixed yet. Nobody seems to have posted its
solution on the internet.
Description : I have a weekly backup scheduled. I do this on my google drive of
my gmail account.
The backup happens for about 10 minutes. I'm unable to unmount my google
drive from my computer this time and the computer tells me that some
operations are keeping th volume busy.
Then I get this error message:-
This has been happening since 1 month continously and everytime I get this
error message
Giving up after 5 attempts. Error: gdata-service-error-quark: Authentication
required: {
"error": {
"errors": [
{
"domain": "global",
"reason": "authError",
"message": "Invalid Credentials",
"locationType": "header",
"location": "Authorization"
}
],
"code": 401,
"message": "Invalid Credentials"
}
}
(4)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to deja-dup in Ubuntu.
https://bugs.launchpad.net/bugs/1747646
Title:
Authentication error with google drive
Status in Déjà Dup:
Triaged
Status in deja-dup package in Ubuntu:
Triaged
Bug description:
Hi,
I'm having an issue using deja-dup to back up my laptop to my google
drive.
When backing only a small folder (eg: ~/Documents) every thing works fine.
However when trying to backup my whole home folder (/home/myusername) I get
an "Invalid credentials" error after 5-10 min.
The back up seems to start normally and my destination folder starts
filling with "duplicity-full...difftar.gz" files, but eventually I get
the Invalid Credentials error.
lsb_release -d
Fedora release 27 (Twenty Seven)
rpm -q deja-dup duplicity
deja-dup-37.1-1.fc27.x86_64
duplicity-0.7.16-1.fc27.x86_64
deja-dup.log attached.
I cannot attach deja-dup.gsettings since i can only join 1 file. Will send if
needed.
To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1747646/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1800179] Re: Search in recent files list only works with lowercase letters
This bug was fixed in the package gedit - 3.30.2-2 --- gedit (3.30.2-2) unstable; urgency=medium * debian/patches/document-selector-make-search-caseless.patch: - 'document selector: make search caseless', it makes the filter in the open document work in a more logical way (lp: #1800179) -- Sebastien Bacher Mon, 17 Dec 2018 16:32:49 +0100 ** Changed in: gedit (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1800179 Title: Search in recent files list only works with lowercase letters Status in gedit package in Ubuntu: Fix Released Bug description: * Impact The document filter is case sensitive which is confusing/not convenient * Test case - Open a document with an Uppercase letter - close it - click on 'open' and type the name with an Uppercase -> it should list the document * Regression potential The code change is in the filtering code, just test that. When clicking “Open” and typing to search the recently opened files, any search involving uppercase letters fails to return any result, even if files with uppercase letters in their file names have recently been opened. Searching for the same file names, but using all- lowercase letters, does yield results (see attached screenshot). So it seems that gedit converts the recently used file names to lowercase before comparing to the search term, which is incorrect. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1800179/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1808881] [NEW] Unwanted touchpad movements on tap with Synaptics touchpad on DELL Inspiron-3521
Public bug reported: When using the touchpad, the mouse cursor moves even when keeping the finger still on one point. Triggering the behaviour: this happens when the contact surface is very small, so it gets triggered for example when tapping on a button, right before the finger leaves the touchpad. This makes clicking buttons using the touchpad (for example, the "x" button in the browser tabs) very difficult. In attachment, an evemu-record done keeping the finger on one point, barely touching the touchpad. The recording was done with the command: sudo evemu-record > touchpad.evemu Available devices: /dev/input/event0: Power Button /dev/input/event1: Lid Switch /dev/input/event2: Power Button /dev/input/event3: AT Translated Set 2 keyboard /dev/input/event4: Video Bus /dev/input/event8: SynPS/2 Synaptics TouchPad /dev/input/event9: Dell WMI hotkeys /dev/input/event10: HDA Intel PCH Mic /dev/input/event11: HDA Intel PCH Front Headphone /dev/input/event12: HDA Intel PCH HDMI/DP,pcm=3 /dev/input/event13: Laptop_Integrated_Webcam_HD: In Select the device event number [0-13]: 8 To replay the recording (the strange behaviour is particularly visible in the final part): sudo evemu-play /dev/input/event8 < touchpad.evemu (replace event8 with your input device) System info: lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.04.1 LTS Release:18.04 Codename: bionic apt-cache policy libinput10 libinput10: Installato: 1.10.4-1 Candidato: 1.10.4-1 Tabella versione: *** 1.10.4-1 500 500 http://it.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status apt-cache policy libinput-bin libinput-bin: Installato: 1.10.4-1 Candidato: 1.10.4-1 Tabella versione: *** 1.10.4-1 500 500 http://it.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status ** Affects: libinput (Ubuntu) Importance: Undecided Status: New ** Attachment added: "evemu-record track when keeping the finger still on one point" https://bugs.launchpad.net/bugs/1808881/+attachment/5223096/+files/touchpad.evemu ** Description changed: When using the touchpad, the mouse cursor moves even when keeping the finger still on one point. Triggering the behaviour: this happens when the contact surface is very small, so it gets triggered for example when tapping on a button, right before the finger leaves the touchpad. This makes clicking buttons using the touchpad (for example, the "x" button in the browser tabs) very difficult. In attachment, an evemu-record done keeping the finger on one point, barely touching the touchpad. The recording was done with the command: sudo evemu-record > touchpad.evemu Available devices: /dev/input/event0:Power Button /dev/input/event1:Lid Switch /dev/input/event2:Power Button /dev/input/event3:AT Translated Set 2 keyboard /dev/input/event4:Video Bus /dev/input/event8:SynPS/2 Synaptics TouchPad /dev/input/event9:Dell WMI hotkeys /dev/input/event10: HDA Intel PCH Mic /dev/input/event11: HDA Intel PCH Front Headphone /dev/input/event12: HDA Intel PCH HDMI/DP,pcm=3 /dev/input/event13: Laptop_Integrated_Webcam_HD: In Select the device event number [0-13]: 8 To replay the recording: sudo evemu-play /dev/input/event8 < touchpad.evemu (replace event8 with your input device) + + System info: + + lsb_release -a + No LSB modules are available. + Distributor ID: Ubuntu + Description: Ubuntu 18.04.1 LTS + Release: 18.04 + Codename: bionic + + apt-cache policy libinput10 + libinput10: + Installato: 1.10.4-1 + Candidato: 1.10.4-1 + Tabella versione: + *** 1.10.4-1 500 + 500 http://it.archive.ubuntu.com/ubuntu bionic/main amd64 Packages + 100 /var/lib/dpkg/status + + apt-cache policy libinput-bin + libinput-bin: + Installato: 1.10.4-1 + Candidato: 1.10.4-1 + Tabella versione: + *** 1.10.4-1 500 + 500 http://it.archive.ubuntu.com/ubuntu bionic/main amd64 Packages + 100 /var/lib/dpkg/status ** Description changed: When using the touchpad, the mouse cursor moves even when keeping the finger still on one point. Triggering the behaviour: this happens when the contact surface is very small, so it gets triggered for example when tapping on a button, right before the finger leaves the touchpad. This makes clicking buttons using the touchpad (for example, the "x" button in the browser tabs) very difficult. In attachment, an evemu-record done keeping the finger on one point, barely touching the touchpad. The recording was done with the command: sudo evemu-record > touchpad.evemu Available devices: /dev/input/event0:Power Button /dev/input/event1:Lid Switch /dev/input/event2:Power Button /dev/input/event3
[Desktop-packages] [Bug 1697641] Re: Chromium doesn't open OSK under GNOME Shell
Oliver, is it still works for you with current Chromium builds? -- 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/1697641 Title: Chromium doesn't open OSK under GNOME Shell Status in chromium-browser package in Ubuntu: In Progress Bug description: Other Gtk apps signal the OSK to appear when using touch as the primary navigation method. e.g. Touch in to gedit, and the osk pops up, touch in to eog and it goes away. Chromium doesn't do this (and nor does Firefox). This will be required for good 2-in-1 support. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: chromium-browser 58.0.3029.110-0ubuntu0.16.04.1281 ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67 Uname: Linux 4.4.0-79-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 DRM.card0-DP-1: edid-base64: dpms: Off modes: enabled: disabled status: disconnected DRM.card0-DP-2: edid-base64: AP///wAQrHNATDUxRxAWAQSlMx14O26lo1RPnyYRUFSlSwBxT4GA0cABAQEBAQEBAQEBAjqAGHE4LUBYLEUA/h8RAAAe/wA1OURKUDI0SkcxNUwK/ABERUxMIFUyMzEySE0K/QA4TB5TEQAKICAgICAgAOk= dpms: On modes: 1920x1080 1680x1050 1680x945 1400x1050 1400x1050 1600x900 1280x1024 1280x1024 1440x900 1440x900 1280x960 1366x768 1360x768 1280x800 1280x800 1152x864 1280x768 1280x768 1280x720 1024x768 1024x768 1024x768 1024x576 800x600 800x600 800x600 800x600 848x480 640x480 640x480 640x480 720x400 enabled: enabled status: connected DRM.card0-DP-3: edid-base64: dpms: Off modes: enabled: disabled status: disconnected DRM.card0-HDMI-A-1: edid-base64: dpms: Off modes: enabled: disabled status: disconnected DRM.card0-HDMI-A-2: edid-base64: dpms: Off modes: enabled: disabled status: disconnected DRM.card0-HDMI-A-3: edid-base64: dpms: Off modes: enabled: disabled status: disconnected DRM.card0-LVDS-1: edid-base64: AP///wAw5NgCAAAUAQOAHBB46tTllVlXiyggUFQBAQEBAQEBAQEBAQEBAQEBYB1W2FAAGDAwQEcAFZwQAAAb/gBMRyBEaXNwbGF5CiAg/gBMUDEyNVdIMi1TTEIxAIQ= dpms: On modes: 1366x768 enabled: enabled status: connected DRM.card0-VGA-1: edid-base64: dpms: Off modes: enabled: disabled status: disconnected Date: Tue Jun 13 09:54:41 2017 Desktop-Session: 'None' 'None' 'None' DetectedPlugins: EcryptfsInUse: Yes Env: 'None' 'None' InstallationDate: Installed on 2016-04-22 (416 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Load-Avg-1min: 0.27 Load-Processes-Running-Percent: 0.1% MachineType: LENOVO 4287CTO ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-79-generic root=UUID=3016f766-1b5d-4550-ba62-3373b530cf42 ro quiet splash vt.handoff=7 SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/07/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET50WW (1.20 ) dmi.board.asset.tag: Not Available dmi.board.name: 4287CTO 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:bvr8DET50WW(1.20):bd07/07/2011:svnLENOVO:pn4287CTO:pvrThinkPadX220:rvnLENOVO:rn4287CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4287CTO dmi.product.version: ThinkPad X220 dmi.sys.vendor: LENOVO gconf-keys: /desktop/gnome/applications/browser/exec = b''/desktop/gnome/url-handlers/https/command = b''/desktop/gnome/url-handlers/https/enabled = b''/desktop/gnome/url-handlers/http/command = b''/desktop/gnome/url-handlers/http/enabled = b''/desktop/gnome/session/required_components/windowmanager = b''/apps/metacity/general/compositing_manager = b''/desktop/gnome/interface/icon_theme = b''/desktop/gnome/interface/gtk_theme = b'' modified.conffile..etc.default.chromium-browser: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1697641/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1702873] Re: [snap] artifacts when using HiDPI display
… and both issues are fixed by this trivial PR: https://github.com/ubuntu/snapcraft-desktop-helpers/pull/170. ** Changed in: libreoffice (Ubuntu) Status: Confirmed => In Progress ** Changed in: libreoffice (Ubuntu) Assignee: (unassigned) => Olivier Tilloy (osomon) -- 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/1702873 Title: [snap] artifacts when using HiDPI display Status in libreoffice package in Ubuntu: In Progress Bug description: I am using a HiDPI display. At scale 2. The cursor is tiny when inside the window of the app. Many icons on the toolbar are blurry, more than usual. I report these commands' output as requested: lsb_release -a snap info --verbose libreoffice core luca@xpsluca:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 16.10 Release: 16.10 Codename: yakkety luca@xpsluca:~$ snap info --verbose libreoffice core name: libreoffice summary: "LibreOffice is a powerful office suite including word processing and creation of spreadsheets, slideshows and databases" publisher: canonical contact: http://www.libreoffice.org/get-help/community-support/ description: | LibreOffice is a powerful office suite – its clean interface and feature-rich tools help you unleash your creativity and enhance your productivity. LibreOffice includes several applications that make it the most powerful Free and Open Source office suite on the market: Writer (word processing), Calc (spreadsheets), Impress (presentations), Draw (vector graphics and flowcharts), Base (databases), and Math (formula editing). commands: - libreoffice.base - libreoffice.calc - libreoffice.draw - libreoffice.impress - libreoffice - libreoffice.math - libreoffice.writer notes: private: false confinement: strict devmode: false jailmode: false trymode: false enabled: true broken: false tracking: beta installed: 5.3.4.2 (21) 368MB refreshed: 2017-07-01 19:14:41 +0200 CEST channels: latest/stable:5.3.2.2 (19) 375MB - latest/candidate: 5.3.2.2 (19) 375MB - latest/beta: 5.3.4.2 (21) 368MB - latest/edge: 5.3.2.2 (19) 375MB - --- name: core summary: "snapd runtime environment" publisher: canonical contact: snappy-canonical-storeacco...@canonical.com description: | The core runtime environment for snapd type: core notes: private: false confinement: strict devmode: false jailmode: false trymode: false enabled: true broken: false tracking: stable installed: 16-2 (2312) 83MB refreshed: 2017-04-11 14:28:54 +0200 CEST channels: latest/stable:16-2 (2312) 83MB - latest/candidate: 16-2.26.8(2329) 84MB - latest/beta: 16-2.26.8(2329) 84MB - latest/edge: 16-2.26.8+git258.fa4bcff (2343) 85MB - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1702873/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1766974] Re: /dev/dri/card0
I got the same error too on linux 16.04.5 how do I send you the needed info ** Also affects: xorg-server Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1766974 Title: /dev/dri/card0 Status in X.Org X server: New Status in xorg-server package in Ubuntu: Incomplete Bug description: There are very many bugs reported recently against xorg with a commmon theme the following are just 2 examples from the various xorg logs (EE) /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied (EE) intel(0): [drm] failed to set drm interface version: Permission denied [13]. --- ProblemType: Bug .tmp.unity_support_test.1: ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: 2018-08-16 10:03:18,003 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo Core Processor Integrated Graphics Controller [17aa:215a] InstallationDate: Installed on 2016-09-24 (757 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: LENOVO 2519Y11 Package: xorg-server (not installed) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=58d362c2-ed1e-479b-84f5-e5d8a782b08f ro quiet nomodeset ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Renderer: Software Tags: bionic ubuntu Uname: Linux 4.15.0-36-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-08-16 (66 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/14/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 6IET85WW (1.45 ) dmi.board.name: 2519Y11 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:bvr6IET85WW(1.45):bd02/14/2013:svnLENOVO:pn2519Y11:pvrThinkPadT410:rvnLENOVO:rn2519Y11:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T410 dmi.product.name: 2519Y11 dmi.product.version: ThinkPad T410 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.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 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 1:18.0.1-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 xserver.bootTime: Mon Oct 22 07:25:26 2018 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory open /dev/dri/card0: No such file or directory Screen 0 deleted because of no matching config section. AIGLX: reverting to software rendering xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.6-1ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1766974/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1767648] Re: Top bar and shell dialogs are not displayed properly when zoom is enabled
I'm also having this bug and for people with sightloss it's a massive issue, some things I wasn't able to do on my laptop because of it - I didn't realise the bluetooth was always on, - I couldn't figure out the date or time - There's a weird menu that's open on the top left of my screen I can't get rid of The bluetooth issue is a serious security issue, This bug makes ubuntu unsafe to use for people with sightloss. I picked the wrong time to switch and am thinking of moving back to windows. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1767648 Title: Top bar and shell dialogs are not displayed properly when zoom is enabled Status in Mutter: In Progress Status in mutter package in Ubuntu: In Progress Status in mutter source package in Bionic: In Progress Bug description: When zoom is enabled, the top bar and some shell dialogs (wireless network selection, shutdown dialog, etc.) are not displayed properly. (See the attached screenshots.) Steps to reproduce the issue: 1. Enable Zoom in Setting > Universal Access 2. (Optional) Set zoom factor to around 3 (or higher) 3. Look at the top bar. You will notice that all texts and icons are now gone. If you move your cursor to the right of the top bar, and then click on the status menu, you will see that only a portion of the menu is shown. 4. For the shell dialogs, go to the Settings app. In the Wifi section, choose one of the secured network available. You will see that the password dialog is not displayed in its entirety. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CasperVersion: 1.394 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 28 12:54:24 2018 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'cursor-size' b'96' LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1767648/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1808874] Re: nvidia-detector doesn't seem to detect nvidia
** Tags added: cosmic disco rls-dd-incoming -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1808874 Title: nvidia-detector doesn't seem to detect nvidia Status in ubuntu-drivers-common package in Ubuntu: New Bug description: bdmurray@flash:~$ grep nvidia /proc/modules nvidia_uvm 757760 0 - Live 0x (POE) nvidia_drm 40960 1 - Live 0x (POE) nvidia_modeset 1110016 3 nvidia_drm, Live 0x (POE) nvidia 14360576 84 nvidia_uvm,nvidia_modeset, Live 0x (POE) drm_kms_helper 172032 1 nvidia_drm, Live 0x drm 401408 4 nvidia_drm,drm_kms_helper, Live 0x ipmi_msghandler 53248 2 nvidia,ipmi_devintf, Live 0x bdmurray@flash:~$ nvidia-detector none bdmurray@flash:~$ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=18.04 DISTRIB_CODENAME=bionic DISTRIB_DESCRIPTION="Ubuntu 18.04.1 LTS" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1808874/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1702873] Re: [snap] artifacts when using HiDPI display
Relevant logs when stracing the test snap execution: openat(AT_FDCWD, "/snap/gtk-hello-world/x1/usr/share/icons/Yaru/cursors/text", O_RDONLY) = -1 ENOENT (No such file or directory) openat(AT_FDCWD, "/snap/gtk-hello-world/x1/usr/share/icons/default/cursors/text", O_RDONLY) = -1 ENOENT (No such file or directory) openat(AT_FDCWD, "/snap/gtk-hello-world/x1/usr/share/icons/Yaru/cursors/xterm", O_RDONLY) = -1 ENOENT (No such file or directory) openat(AT_FDCWD, "/snap/gtk-hello-world/x1/usr/share/icons/default/cursors/xterm", O_RDONLY) = -1 ENOENT (No such file or directory) And indeed even at a scale factor of 1.0, cursors are not the ones provided by the theme. They're likely the default X fallback versions. -- 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/1702873 Title: [snap] artifacts when using HiDPI display Status in libreoffice package in Ubuntu: Confirmed Bug description: I am using a HiDPI display. At scale 2. The cursor is tiny when inside the window of the app. Many icons on the toolbar are blurry, more than usual. I report these commands' output as requested: lsb_release -a snap info --verbose libreoffice core luca@xpsluca:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 16.10 Release: 16.10 Codename: yakkety luca@xpsluca:~$ snap info --verbose libreoffice core name: libreoffice summary: "LibreOffice is a powerful office suite including word processing and creation of spreadsheets, slideshows and databases" publisher: canonical contact: http://www.libreoffice.org/get-help/community-support/ description: | LibreOffice is a powerful office suite – its clean interface and feature-rich tools help you unleash your creativity and enhance your productivity. LibreOffice includes several applications that make it the most powerful Free and Open Source office suite on the market: Writer (word processing), Calc (spreadsheets), Impress (presentations), Draw (vector graphics and flowcharts), Base (databases), and Math (formula editing). commands: - libreoffice.base - libreoffice.calc - libreoffice.draw - libreoffice.impress - libreoffice - libreoffice.math - libreoffice.writer notes: private: false confinement: strict devmode: false jailmode: false trymode: false enabled: true broken: false tracking: beta installed: 5.3.4.2 (21) 368MB refreshed: 2017-07-01 19:14:41 +0200 CEST channels: latest/stable:5.3.2.2 (19) 375MB - latest/candidate: 5.3.2.2 (19) 375MB - latest/beta: 5.3.4.2 (21) 368MB - latest/edge: 5.3.2.2 (19) 375MB - --- name: core summary: "snapd runtime environment" publisher: canonical contact: snappy-canonical-storeacco...@canonical.com description: | The core runtime environment for snapd type: core notes: private: false confinement: strict devmode: false jailmode: false trymode: false enabled: true broken: false tracking: stable installed: 16-2 (2312) 83MB refreshed: 2017-04-11 14:28:54 +0200 CEST channels: latest/stable:16-2 (2312) 83MB - latest/candidate: 16-2.26.8(2329) 84MB - latest/beta: 16-2.26.8(2329) 84MB - latest/edge: 16-2.26.8+git258.fa4bcff (2343) 85MB - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1702873/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1767711] Re: Nvidia+XFCE: Totem window is see-through during playback, colours washed out
Same problem on Ubuntu 18.04 (with Gnome Shell). "turn off FXAA" workaround works here too. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1767711 Title: Nvidia+XFCE: Totem window is see-through during playback, colours washed out Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in totem package in Ubuntu: Confirmed Status in xfce4 package in Ubuntu: Invalid Bug description: Since the upgrade to Ubuntu 18.04, the Totem player will show everything behind it during playback, and the colours of the video are washed-out. https://i.imgur.com/0AwJMmf.jpg I did not find 'tranparency' nor 'opacity' setting in the program preferences, and the colour adjudgement settings are pinned to +/-0. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: totem 3.26.0-0ubuntu6 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Apr 28 14:56:29 2018 InstallationDate: Installed on 2016-06-05 (692 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: totem UpgradeStatus: Upgraded to bionic on 2018-04-27 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1767711/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1702873] Re: [snap] artifacts when using HiDPI display
We have at least a couple of separate issues here: 1) Standard GTK+ apps scale only the arrow cursor, other cursors (such as text caret) are not scaled properly 2) Custom apps (including chromium, libreoffice, firefox) do not scale any cursor -- 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/1702873 Title: [snap] artifacts when using HiDPI display Status in libreoffice package in Ubuntu: Confirmed Bug description: I am using a HiDPI display. At scale 2. The cursor is tiny when inside the window of the app. Many icons on the toolbar are blurry, more than usual. I report these commands' output as requested: lsb_release -a snap info --verbose libreoffice core luca@xpsluca:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 16.10 Release: 16.10 Codename: yakkety luca@xpsluca:~$ snap info --verbose libreoffice core name: libreoffice summary: "LibreOffice is a powerful office suite including word processing and creation of spreadsheets, slideshows and databases" publisher: canonical contact: http://www.libreoffice.org/get-help/community-support/ description: | LibreOffice is a powerful office suite – its clean interface and feature-rich tools help you unleash your creativity and enhance your productivity. LibreOffice includes several applications that make it the most powerful Free and Open Source office suite on the market: Writer (word processing), Calc (spreadsheets), Impress (presentations), Draw (vector graphics and flowcharts), Base (databases), and Math (formula editing). commands: - libreoffice.base - libreoffice.calc - libreoffice.draw - libreoffice.impress - libreoffice - libreoffice.math - libreoffice.writer notes: private: false confinement: strict devmode: false jailmode: false trymode: false enabled: true broken: false tracking: beta installed: 5.3.4.2 (21) 368MB refreshed: 2017-07-01 19:14:41 +0200 CEST channels: latest/stable:5.3.2.2 (19) 375MB - latest/candidate: 5.3.2.2 (19) 375MB - latest/beta: 5.3.4.2 (21) 368MB - latest/edge: 5.3.2.2 (19) 375MB - --- name: core summary: "snapd runtime environment" publisher: canonical contact: snappy-canonical-storeacco...@canonical.com description: | The core runtime environment for snapd type: core notes: private: false confinement: strict devmode: false jailmode: false trymode: false enabled: true broken: false tracking: stable installed: 16-2 (2312) 83MB refreshed: 2017-04-11 14:28:54 +0200 CEST channels: latest/stable:16-2 (2312) 83MB - latest/candidate: 16-2.26.8(2329) 84MB - latest/beta: 16-2.26.8(2329) 84MB - latest/edge: 16-2.26.8+git258.fa4bcff (2343) 85MB - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1702873/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1702873] Re: [snap] artifacts when using HiDPI display
I built a simple test snap with the Gtk hello world application (https://developer.gnome.org/gtk3/stable/gtk-getting- started.html#id-1.2.3.5, slightly modified to add a GtkEntry), built against core18 on bionic (Gtk 3.22.30). With this snap, my observations are consistent with what I'm seeing with the gnome-characters and gnome-calculator snaps: the arrow cursor is scaled correctly, but other cursors (such as text caret) aren't. This test snap uses the desktop-gtk3 part, plugs into the theme interfaces provided by gtk-common-themes, additionally to desktop, gsettings, unity7 and x11. -- 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/1702873 Title: [snap] artifacts when using HiDPI display Status in libreoffice package in Ubuntu: Confirmed Bug description: I am using a HiDPI display. At scale 2. The cursor is tiny when inside the window of the app. Many icons on the toolbar are blurry, more than usual. I report these commands' output as requested: lsb_release -a snap info --verbose libreoffice core luca@xpsluca:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 16.10 Release: 16.10 Codename: yakkety luca@xpsluca:~$ snap info --verbose libreoffice core name: libreoffice summary: "LibreOffice is a powerful office suite including word processing and creation of spreadsheets, slideshows and databases" publisher: canonical contact: http://www.libreoffice.org/get-help/community-support/ description: | LibreOffice is a powerful office suite – its clean interface and feature-rich tools help you unleash your creativity and enhance your productivity. LibreOffice includes several applications that make it the most powerful Free and Open Source office suite on the market: Writer (word processing), Calc (spreadsheets), Impress (presentations), Draw (vector graphics and flowcharts), Base (databases), and Math (formula editing). commands: - libreoffice.base - libreoffice.calc - libreoffice.draw - libreoffice.impress - libreoffice - libreoffice.math - libreoffice.writer notes: private: false confinement: strict devmode: false jailmode: false trymode: false enabled: true broken: false tracking: beta installed: 5.3.4.2 (21) 368MB refreshed: 2017-07-01 19:14:41 +0200 CEST channels: latest/stable:5.3.2.2 (19) 375MB - latest/candidate: 5.3.2.2 (19) 375MB - latest/beta: 5.3.4.2 (21) 368MB - latest/edge: 5.3.2.2 (19) 375MB - --- name: core summary: "snapd runtime environment" publisher: canonical contact: snappy-canonical-storeacco...@canonical.com description: | The core runtime environment for snapd type: core notes: private: false confinement: strict devmode: false jailmode: false trymode: false enabled: true broken: false tracking: stable installed: 16-2 (2312) 83MB refreshed: 2017-04-11 14:28:54 +0200 CEST channels: latest/stable:16-2 (2312) 83MB - latest/candidate: 16-2.26.8(2329) 84MB - latest/beta: 16-2.26.8(2329) 84MB - latest/edge: 16-2.26.8+git258.fa4bcff (2343) 85MB - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1702873/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1808874] [NEW] nvidia-detector doesn't seem to detect nvidia
Public bug reported: bdmurray@flash:~$ grep nvidia /proc/modules nvidia_uvm 757760 0 - Live 0x (POE) nvidia_drm 40960 1 - Live 0x (POE) nvidia_modeset 1110016 3 nvidia_drm, Live 0x (POE) nvidia 14360576 84 nvidia_uvm,nvidia_modeset, Live 0x (POE) drm_kms_helper 172032 1 nvidia_drm, Live 0x drm 401408 4 nvidia_drm,drm_kms_helper, Live 0x ipmi_msghandler 53248 2 nvidia,ipmi_devintf, Live 0x bdmurray@flash:~$ nvidia-detector none bdmurray@flash:~$ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=18.04 DISTRIB_CODENAME=bionic DISTRIB_DESCRIPTION="Ubuntu 18.04.1 LTS" ** Affects: ubuntu-drivers-common (Ubuntu) Importance: Undecided Status: New ** Tags: bionic ** Tags added: bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1808874 Title: nvidia-detector doesn't seem to detect nvidia Status in ubuntu-drivers-common package in Ubuntu: New Bug description: bdmurray@flash:~$ grep nvidia /proc/modules nvidia_uvm 757760 0 - Live 0x (POE) nvidia_drm 40960 1 - Live 0x (POE) nvidia_modeset 1110016 3 nvidia_drm, Live 0x (POE) nvidia 14360576 84 nvidia_uvm,nvidia_modeset, Live 0x (POE) drm_kms_helper 172032 1 nvidia_drm, Live 0x drm 401408 4 nvidia_drm,drm_kms_helper, Live 0x ipmi_msghandler 53248 2 nvidia,ipmi_devintf, Live 0x bdmurray@flash:~$ nvidia-detector none bdmurray@flash:~$ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=18.04 DISTRIB_CODENAME=bionic DISTRIB_DESCRIPTION="Ubuntu 18.04.1 LTS" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1808874/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1808873] [NEW] gdm3 no greeter with two monitors
Public bug reported: Hello, Ubuntu 18.10, Intel integrated video, a monitor connected by DVI, a projector connected by HDMI. While all the boot messages appear on both devices (if they are turned on) the gdm3 greeter doesn't appear at all (black screens) UNTIL I switch to a virtual console and back (Ctrl+Alt+F2, Ctrl+Alt+F1). ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Attachment added: "apport-bug info" https://bugs.launchpad.net/bugs/1808873/+attachment/5223090/+files/gdm3bug ** Package changed: console-setup (Ubuntu) => gdm3 (Ubuntu) -- 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/1808873 Title: gdm3 no greeter with two monitors Status in gdm3 package in Ubuntu: New Bug description: Hello, Ubuntu 18.10, Intel integrated video, a monitor connected by DVI, a projector connected by HDMI. While all the boot messages appear on both devices (if they are turned on) the gdm3 greeter doesn't appear at all (black screens) UNTIL I switch to a virtual console and back (Ctrl+Alt+F2, Ctrl+Alt+F1). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1808873/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1808873] [NEW] gdm3 no greeter with two monitors
You have been subscribed to a public bug: Hello, Ubuntu 18.10, Intel integrated video, a monitor connected by DVI, a projector connected by HDMI. While all the boot messages appear on both devices (if they are turned on) the gdm3 greeter doesn't appear at all (black screens) UNTIL I switch to a virtual console and back (Ctrl+Alt+F2, Ctrl+Alt+F1). ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New -- gdm3 no greeter with two monitors https://bugs.launchpad.net/bugs/1808873 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 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 1768291] Re: lirc is flooding the syslog with two lines each second
I had this same problem I used sudo apt-get remove lirc That stoped the logs I never installed lirc So it must have installed during upgrade to 18.04 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lirc in Ubuntu. https://bugs.launchpad.net/bugs/1768291 Title: lirc is flooding the syslog with two lines each second Status in lirc package in Ubuntu: New Bug description: Hello, in the syslog every second two lines are written: May 1 18:05:19 flupp lircd[1323]: lircd-0.10.0[1323]: Error: Cannot glob /sys/class/rc/rc0/input[0-9]*/event[0-9]* May 1 18:05:19 flupp lircd-0.10.0[1323]: Error: Cannot glob /sys/class/rc/rc0/input[0-9]*/event[0-9]* May 1 18:05:20 flupp lircd[1323]: lircd-0.10.0[1323]: Error: Cannot glob /sys/class/rc/rc0/input[0-9]*/event[0-9]* May 1 18:05:20 flupp lircd-0.10.0[1323]: Error: Cannot glob /sys/class/rc/rc0/input[0-9]*/event[0-9]* May 1 18:05:21 flupp lircd[1323]: lircd-0.10.0[1323]: Error: Cannot glob /sys/class/rc/rc0/input[0-9]*/event[0-9]* May 1 18:05:21 flupp lircd-0.10.0[1323]: Error: Cannot glob /sys/class/rc/rc0/input[0-9]*/event[0-9]* May 1 18:05:22 flupp lircd[1323]: lircd-0.10.0[1323]: Error: Cannot glob /sys/class/rc/rc0/input[0-9]*/event[0-9]* May 1 18:05:22 flupp lircd-0.10.0[1323]: Error: Cannot glob /sys/class/rc/rc0/input[0-9]*/event[0-9]* May 1 18:05:23 flupp lircd[1323]: lircd-0.10.0[1323]: Error: Cannot glob /sys/class/rc/rc0/input[0-9]*/event[0-9]* May 1 18:05:23 flupp lircd-0.10.0[1323]: Error: Cannot glob /sys/class/rc/rc0/input[0-9]*/event[0-9]* May 1 18:05:24 flupp lircd[1323]: lircd-0.10.0[1323]: Error: Cannot glob /sys/class/rc/rc0/input[0-9]*/event[0-9]* May 1 18:05:24 flupp lircd-0.10.0[1323]: Error: Cannot glob /sys/class/rc/rc0/input[0-9]*/event[0-9]* May 1 18:05:25 flupp lircd[1323]: lircd-0.10.0[1323]: Error: Cannot glob /sys/class/rc/rc0/input[0-9]*/event[0-9]* May 1 18:05:25 flupp lircd-0.10.0[1323]: Error: Cannot glob /sys/class/rc/rc0/input[0-9]*/event[0-9]* May 1 18:05:26 flupp lircd[1323]: lircd-0.10.0[1323]: Error: Cannot glob /sys/class/rc/rc0/input[0-9]*/event[0-9]* May 1 18:05:26 flupp lircd-0.10.0[1323]: Error: Cannot glob /sys/class/rc/rc0/input[0-9]*/event[0-9]* May 1 18:05:27 flupp lircd[1323]: lircd-0.10.0[1323]: Error: Cannot glob /sys/class/rc/rc0/input[0-9]*/event[0-9]* May 1 18:05:27 flupp lircd-0.10.0[1323]: Error: Cannot glob /sys/class/rc/rc0/input[0-9]*/event[0-9]* May 1 18:05:28 flupp lircd[1323]: lircd-0.10.0[1323]: Error: Cannot glob /sys/class/rc/rc0/input[0-9]*/event[0-9]* May 1 18:05:28 flupp lircd-0.10.0[1323]: Error: Cannot glob /sys/class/rc/rc0/input[0-9]*/event[0-9]* This is not only annoying as it makes it difficult to use the syslog for checking the system, but also it writes too much data into the log (18MB each day). Also it keeps the hard disc awaken what is bad for standby. Kubuntu 18.04 ii liblirc-client0:amd64 0.10.0-2 amd64infra-red remote control support - client library ii liblirc0:amd640.10.0-2 amd64Infra-red remote control support - Run-time libraries ii lirc 0.10.0-2 amd64Infra-red remote control support - daemons and utils I do not have infrared remote control hardware. But I cannot purge the packages as other packages I want to keep would be removed as well. Deactivating the services in systemd does not help (or I am doing something wrong?) Greetings Gert To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/1768291/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1794033] Re: i965: Failed to submit batchbuffer: Bad address
Just hit me, kernel 4.19.8-liquorix-amd64, Ubuntu 18.10. I was running with modesetting, but decided to change to intel driver (freshly compiled from git) to see if I run into it again (it seems pretty rare though so will probably be tough to hit). Has anyone definitely hit it on xf86-video-intel or only modesetting? -- 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/1794033 Title: i965: Failed to submit batchbuffer: Bad address Status in mesa package in Ubuntu: Confirmed Status in xserver-xorg-video-intel package in Fedora: Incomplete Bug description: cpu: Intel® Core™ i5-7500 CPU @ 3.40GHz × 4 gpu: Intel® HD Graphics 630 (Kaby Lake GT2) 00:00.0 Host bridge: Intel Corporation Intel Kaby Lake Host Bridge (rev 05) 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 630 (rev 04) 00:08.0 System peripheral: Intel Corporation Skylake Gaussian Mixture Model xserver-xorg-video-intel: Installed: 2:2.99.917+git20171229-1 Candidate: 2:2.99.917+git20171229-1 ubuntu: 18.04 LTS bionic gnome: 3.28.2 gdm3: Installed: 3.28.2-0ubuntu1.4 Candidate: 3.28.2-0ubuntu1.4 os type: 64 bit kernel: Linux eva1 4.15.0-30-generic #32-Ubuntu SMP Thu Jul 26 17:42:43 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux mesa-va-drivers: Installed: 18.0.5-0ubuntu0~18.04.1 Candidate: 18.0.5-0ubuntu0~18.04.1 from syslog: Sep 24 04:08:16 eva /usr/lib/gdm3/gdm-x-session[1170]: i965: Failed to submit batchbuffer: Bad address Sep 24 04:08:21 eva gnome-terminal-[2597]: gnome-terminal-server: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Sep 24 04:08:22 eva [2541]: update-notifier: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Sep 24 04:08:22 eva at-spi-bus-launcher[1274]: XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0" - but (followed by pages upon pages of applications within gnome failing.) nothing in kern.log around that time. Singular gnome crash, taking down all applications running within it. Not yet reproduced. gdm successfully started a new session afterwards. Was definitely in a palermoon session on some website or other. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1794033/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1794033] Re: i965: Failed to submit batchbuffer: Bad address
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mesa (Ubuntu) Status: New => Confirmed -- 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/1794033 Title: i965: Failed to submit batchbuffer: Bad address Status in mesa package in Ubuntu: Confirmed Status in xserver-xorg-video-intel package in Fedora: Incomplete Bug description: cpu: Intel® Core™ i5-7500 CPU @ 3.40GHz × 4 gpu: Intel® HD Graphics 630 (Kaby Lake GT2) 00:00.0 Host bridge: Intel Corporation Intel Kaby Lake Host Bridge (rev 05) 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 630 (rev 04) 00:08.0 System peripheral: Intel Corporation Skylake Gaussian Mixture Model xserver-xorg-video-intel: Installed: 2:2.99.917+git20171229-1 Candidate: 2:2.99.917+git20171229-1 ubuntu: 18.04 LTS bionic gnome: 3.28.2 gdm3: Installed: 3.28.2-0ubuntu1.4 Candidate: 3.28.2-0ubuntu1.4 os type: 64 bit kernel: Linux eva1 4.15.0-30-generic #32-Ubuntu SMP Thu Jul 26 17:42:43 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux mesa-va-drivers: Installed: 18.0.5-0ubuntu0~18.04.1 Candidate: 18.0.5-0ubuntu0~18.04.1 from syslog: Sep 24 04:08:16 eva /usr/lib/gdm3/gdm-x-session[1170]: i965: Failed to submit batchbuffer: Bad address Sep 24 04:08:21 eva gnome-terminal-[2597]: gnome-terminal-server: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Sep 24 04:08:22 eva [2541]: update-notifier: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Sep 24 04:08:22 eva at-spi-bus-launcher[1274]: XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0" - but (followed by pages upon pages of applications within gnome failing.) nothing in kern.log around that time. Singular gnome crash, taking down all applications running within it. Not yet reproduced. gdm successfully started a new session afterwards. Was definitely in a palermoon session on some website or other. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1794033/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
The fixes in the 4.20-rc kernels are for other laptops, not the UX391UA. You'll need to add: SND_PCI_QUIRK(0x1043, 0x10a1, "ASUS UX391UA", ALC294_FIXUP_ASUS_SPK to /sound/pci/hda/patch_realtek.c to get sound working on this laptop. I used the 4.19.9 kernel, applied the 3 linked patches and added the line above. If you're using 4.20-rc6 / 7, you may only need to add the line to patch_realtek.c -- 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/1784485 Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: Internal speaker - not sound at all Cable Headphonse - realy quiet disorted sound Bluetooth headphones - sound works fine On Windows 10 everything works fine. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pmichalski 7964 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Jul 30 22:32:10 2018 InstallationDate: Installed on 2018-07-17 (12 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Wbudowany dźwięk - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm2988 F pulseaudio pmichalski 7964 F pulseaudio Symptom_Jack: Mic, Internal Symptom_Type: No sound at all Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX391UA.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX391UA 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.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook S dmi.product.name: ZenBook S UX391UA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1768078] Re: gnome-control-center network panel missing DNS search
** Changed in: gnome-control-center Status: Unknown => Confirmed ** Changed in: gnome-control-center Importance: Unknown => High -- 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/1768078 Title: gnome-control-center network panel missing DNS search Status in gnome-control-center: Confirmed Status in gnome-control-center package in Ubuntu: Triaged Bug description: The Unity network panel offered a means to set DNS search data on fixed IP connections maintained via NetworkManager in /etc/NetworkManager/system-coonections/ dns-search variable. This feature is absent in 18.04 Gnome's gnome-control-center network panel. Lack of the feature means the dns-search variable is unset which also causes /etc/resolv.conf to leave the search to be unset. This is unacceptable in a assigned IP address Enterprise environment. One workaround is to manually edit the NetworkManager system- connections file after its creation to set the variable. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1:3.28.1-0ubuntu1 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 Date: Mon Apr 30 12:36:30 2018 InstallationDate: Installed on 2018-04-30 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1768078/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1808861] Re: chromium-browser crash Unreportable - Invalid core dump: BFD: warning: apport_core is truncated
** Description changed: Trying to report a crash in chromium-browser, get Unreportable reason Invalid core dump: BFD: warning apport_core is truncated (see screenshot, can't copy message from apport dialog - bug # 1273752). + UnreportableReason: + Invalid core dump: BFD: warning: /tmp/apport_core_6yb3cl_7 is truncated: expected core file size >= 1245646848, found: 760283136 + warning: core file may not match specified executable file. + + Expected: able to report ? + ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: apport 2.20.9-0ubuntu7.5 ProcVersionSignature: User Name 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 ApportLog: - ERROR: apport (pid 31805) Mon Dec 17 15:14:09 2018: called for pid 15848, signal 5, core limit 0, dump mode 1 - ERROR: apport (pid 31805) Mon Dec 17 15:14:09 2018: executable: /usr/lib/chromium-browser/chromium-browser (command line "/usr/lib/chromium-browser/chromium-browser\ --enable-pinch") - ERROR: apport (pid 31805) Mon Dec 17 15:14:09 2018: is_closing_session(): no DBUS_SESSION_BUS_ADDRESS in environment - ERROR: apport (pid 31805) Mon Dec 17 15:15:23 2018: wrote report /var/crash/_usr_lib_chromium-browser_chromium-browser.1000.crash + ERROR: apport (pid 31805) Mon Dec 17 15:14:09 2018: called for pid 15848, signal 5, core limit 0, dump mode 1 + ERROR: apport (pid 31805) Mon Dec 17 15:14:09 2018: executable: /usr/lib/chromium-browser/chromium-browser (command line "/usr/lib/chromium-browser/chromium-browser\ --enable-pinch") + ERROR: apport (pid 31805) Mon Dec 17 15:14:09 2018: is_closing_session(): no DBUS_SESSION_BUS_ADDRESS in environment + ERROR: apport (pid 31805) Mon Dec 17 15:15:23 2018: wrote report /var/crash/_usr_lib_chromium-browser_chromium-browser.1000.crash ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Dec 17 15:30:28 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2018-09-12 (96 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) PackageArchitecture: all ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash SourcePackage: apport UpgradeStatus: Upgraded to bionic on 2018-09-28 (80 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/1808861 Title: chromium-browser crash Unreportable - Invalid core dump: BFD: warning: apport_core is truncated Status in apport package in Ubuntu: New Status in chromium-browser package in Ubuntu: New Bug description: Trying to report a crash in chromium-browser, get Unreportable reason Invalid core dump: BFD: warning apport_core is truncated (see screenshot, can't copy message from apport dialog - bug # 1273752). UnreportableReason: Invalid core dump: BFD: warning: /tmp/apport_core_6yb3cl_7 is truncated: expected core file size >= 1245646848, found: 760283136 warning: core file may not match specified executable file. Expected: able to report ? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: apport 2.20.9-0ubuntu7.5 ProcVersionSignature: User Name 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 ApportLog: ERROR: apport (pid 31805) Mon Dec 17 15:14:09 2018: called for pid 15848, signal 5, core limit 0, dump mode 1 ERROR: apport (pid 31805) Mon Dec 17 15:14:09 2018: executable: /usr/lib/chromium-browser/chromium-browser (command line "/usr/lib/chromium-browser/chromium-browser\ --enable-pinch") ERROR: apport (pid 31805) Mon Dec 17 15:14:09 2018: is_closing_session(): no DBUS_SESSION_BUS_ADDRESS in environment ERROR: apport (pid 31805) Mon Dec 17 15:15:23 2018: wrote report /var/crash/_usr_lib_chromium-browser_chromium-browser.1000.crash ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Dec 17 15:30:28 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2018-09-12 (96 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: apport UpgradeStatus: Upgraded to bionic on 2018-09-28 (80 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1808861/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1808861] [NEW] chromium-browser crash Unreportable - Invalid core dump: BFD: warning: apport_core is truncated
Public bug reported: Trying to report a crash in chromium-browser, get Unreportable reason Invalid core dump: BFD: warning apport_core is truncated (see screenshot, can't copy message from apport dialog - bug # 1273752). Expected: able to report ? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: apport 2.20.9-0ubuntu7.5 ProcVersionSignature: User Name 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 ApportLog: ERROR: apport (pid 31805) Mon Dec 17 15:14:09 2018: called for pid 15848, signal 5, core limit 0, dump mode 1 ERROR: apport (pid 31805) Mon Dec 17 15:14:09 2018: executable: /usr/lib/chromium-browser/chromium-browser (command line "/usr/lib/chromium-browser/chromium-browser\ --enable-pinch") ERROR: apport (pid 31805) Mon Dec 17 15:14:09 2018: is_closing_session(): no DBUS_SESSION_BUS_ADDRESS in environment ERROR: apport (pid 31805) Mon Dec 17 15:15:23 2018: wrote report /var/crash/_usr_lib_chromium-browser_chromium-browser.1000.crash ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Dec 17 15:30:28 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2018-09-12 (96 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: apport UpgradeStatus: Upgraded to bionic on 2018-09-28 (80 days ago) ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Attachment added: "chromium-browser_invalid_core_dump.png" https://bugs.launchpad.net/bugs/1808861/+attachment/5223066/+files/chromium-browser_invalid_core_dump.png ** Also affects: chromium-browser (Ubuntu) Importance: Undecided Status: New -- 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/1808861 Title: chromium-browser crash Unreportable - Invalid core dump: BFD: warning: apport_core is truncated Status in apport package in Ubuntu: New Status in chromium-browser package in Ubuntu: New Bug description: Trying to report a crash in chromium-browser, get Unreportable reason Invalid core dump: BFD: warning apport_core is truncated (see screenshot, can't copy message from apport dialog - bug # 1273752). Expected: able to report ? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: apport 2.20.9-0ubuntu7.5 ProcVersionSignature: User Name 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 ApportLog: ERROR: apport (pid 31805) Mon Dec 17 15:14:09 2018: called for pid 15848, signal 5, core limit 0, dump mode 1 ERROR: apport (pid 31805) Mon Dec 17 15:14:09 2018: executable: /usr/lib/chromium-browser/chromium-browser (command line "/usr/lib/chromium-browser/chromium-browser\ --enable-pinch") ERROR: apport (pid 31805) Mon Dec 17 15:14:09 2018: is_closing_session(): no DBUS_SESSION_BUS_ADDRESS in environment ERROR: apport (pid 31805) Mon Dec 17 15:15:23 2018: wrote report /var/crash/_usr_lib_chromium-browser_chromium-browser.1000.crash ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Dec 17 15:30:28 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2018-09-12 (96 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: apport UpgradeStatus: Upgraded to bionic on 2018-09-28 (80 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1808861/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1768637] Re: /etc/modprobe.d is not a file
** Tags added: rls-dd-incoming -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1768637 Title: /etc/modprobe.d is not a file Status in ubuntu-drivers-common package in Ubuntu: Confirmed Bug description: Hello, I noticed the following entries in my journal after upgrading to 18.04 LTS from 16.04 LTS: May 02 12:06:31 hunt gpu-manager[1112]: /etc/modprobe.d is not a file May 02 12:06:31 hunt gpu-manager[1112]: /etc/modprobe.d is not a file May 02 12:06:31 hunt gpu-manager[1112]: /etc/modprobe.d is not a file May 02 12:06:31 hunt gpu-manager[1112]: /etc/modprobe.d is not a file May 02 12:06:31 hunt gpu-manager[1112]: Error: can't open /lib/modules/4.15.0-20-generic/updates/dkms May 02 12:06:31 hunt audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=gpu-manager comm="systemd" exe="/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' May 02 12:06:31 hunt audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=gpu-manager comm="systemd" exe="/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' May 02 12:06:32 hunt gpu-manager[1170]: /etc/modprobe.d is not a file May 02 12:06:32 hunt gpu-manager[1170]: /etc/modprobe.d is not a file May 02 12:06:32 hunt gpu-manager[1170]: /etc/modprobe.d is not a file May 02 12:06:32 hunt gpu-manager[1170]: /etc/modprobe.d is not a file May 02 12:06:32 hunt gpu-manager[1170]: Error: can't open /lib/modules/4.15.0-20-generic/updates/dkms May 02 12:06:32 hunt audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=gpu-manager comm="systemd" exe="/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' May 02 12:06:32 hunt audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=gpu-manager comm="systemd" exe="/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' May 02 12:06:32 hunt gpu-manager[1254]: /etc/modprobe.d is not a file May 02 12:06:32 hunt gpu-manager[1254]: /etc/modprobe.d is not a file May 02 12:06:32 hunt gpu-manager[1254]: /etc/modprobe.d is not a file May 02 12:06:32 hunt gpu-manager[1254]: /etc/modprobe.d is not a file May 02 12:06:32 hunt gpu-manager[1254]: Error: can't open /lib/modules/4.15.0-20-generic/updates/dkms May 02 12:06:32 hunt audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=gpu-manager comm="systemd" exe="/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' May 02 12:06:32 hunt audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=gpu-manager comm="systemd" exe="/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' May 02 12:06:32 hunt gpu-manager[1316]: /etc/modprobe.d is not a file May 02 12:06:32 hunt gpu-manager[1316]: /etc/modprobe.d is not a file May 02 12:06:32 hunt gpu-manager[1316]: /etc/modprobe.d is not a file May 02 12:06:32 hunt gpu-manager[1316]: /etc/modprobe.d is not a file May 02 12:06:32 hunt gpu-manager[1316]: Error: can't open /lib/modules/4.15.0-20-generic/updates/dkms May 02 12:06:33 hunt audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=gpu-manager comm="systemd" exe="/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' May 02 12:06:33 hunt audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=gpu-manager comm="systemd" exe="/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' May 02 12:06:33 hunt systemd[1]: gpu-manager.service: Start request repeated too quickly. May 02 12:06:33 hunt systemd[1]: gpu-manager.service: Failed with result 'start-limit-hit'. The referenced dkms path does not exist: sarnold@hunt:~$ ls -l /lib/modules/4.15.0-20-generic/updates/dkms ls: cannot access '/lib/modules/4.15.0-20-generic/updates/dkms': No such file or directory sarnold@hunt:~$ ls -l /lib/modules/4.15.0-20-generic/updates/ ls: cannot access '/lib/modules/4.15.0-20-generic/updates/': No such file or directory sarnold@hunt:~$ ls -l /lib/modules/4.15.0-20-generic/ total 5292 lrwxrwxrwx 1 root root 40 Apr 23 21:56 build -> /usr/src/linux-headers-4.15.0-20-generic drwxr-xr-x 2 root root4096 Apr 23 21:56 initrd drwxr-xr-x 15 root root4096 May 1 18:23 kernel -rw-r--r-- 1 root root 1253762 May 1 18:36 modules.alias -rw-r--r-- 1 root root 1235639 May 1 18:36 modules.alias.bin -rw-r--r-- 1 root root7594 Apr 23 21:56 modules.builtin -rw-r--r-- 1 root root9600 May 1 18:36 modules.builtin.bin -rw-r--r-- 1 root root 552117 May 1 18:36 modules.dep -rw-r--r-- 1 root root 780401 May 1 18:36 modules.dep.bin -rw-r--r-- 1 root root 317 May 1 18:36 modules.devname -rw-r--r-- 1 root root 206162 Apr 23 21:56 modules.order -rw-r--r-- 1 root root 515 May 1 18:36 modules.softdep -rw-r--r-- 1 r
[Desktop-packages] [Bug 1769383] Re: Ubuntu dock/launcher is shown on the lock screen
Eric I have this version and I experienced the issue 2 days ago. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1769383 Title: Ubuntu dock/launcher is shown on the lock screen Status in gnome-shell package in Ubuntu: Invalid Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Status in gnome-shell source package in Bionic: Invalid Status in gnome-shell-extension-ubuntu-dock source package in Bionic: In Progress Status in gnome-shell source package in Cosmic: Invalid Status in gnome-shell-extension-ubuntu-dock source package in Cosmic: In Progress Status in gnome-shell source package in Disco: Invalid Status in gnome-shell-extension-ubuntu-dock source package in Disco: Fix Released Bug description: [Impact] When entering the lock-screen mode, gnome-shell disables all the extensions. It can happen that under certain conditions ubuntu-dock re-enables itself, causing the ubuntu-dock to appear in the lock-screen, exposing sensitive information. One possible way to reproduce this is to enable dash-to-dock and ubuntu-dock at the same time. [Test Case] 1. Make sure ubuntu-dock is enabled 2. Enable dash-to-dock too 3. Lock the screen 4. Make sure the dock does not appear on the lock screen 5. Make sure there is no warning is the journal [Possible Regressions] Even if it's something we don't really support please make sure that you can use dash-to-dock without uninstalling ubuntu-dock. [Original Bug] After an update from ubuntu 16.04 to 18.04 the dock is aviable on the lockscreen after user login. I did not configure this knowingly. Also i can start every application which is available on the dock. Settings, virtual box, visualstudio code and so on. After the update to 18.04 i just configure the screen frequency to 144Hz and the night mode on. And attach the dock on bottom. I later undid these customizations back to configuration before, but the dock is stil aviable on lockscreen. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-settings-daemon 3.28.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat May 5 18:30:16 2018 InstallationDate: Installed on 2018-04-08 (27 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: gnome-settings-daemon UpgradeStatus: Upgraded to bionic on 2018-05-01 (3 days ago) --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-08 (27 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell-extension-ubuntu-dock 0.9.1 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-05-01 (4 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1769383/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1769383] Re: Ubuntu dock/launcher is shown on the lock screen
I used to encounter this issue frequently on 18.10. However, I have not encountered it since I upgraded gnome-shell to 3.30.1-2ubuntu1.18.10.1 approximately five days ago. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1769383 Title: Ubuntu dock/launcher is shown on the lock screen Status in gnome-shell package in Ubuntu: Invalid Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Status in gnome-shell source package in Bionic: Invalid Status in gnome-shell-extension-ubuntu-dock source package in Bionic: In Progress Status in gnome-shell source package in Cosmic: Invalid Status in gnome-shell-extension-ubuntu-dock source package in Cosmic: In Progress Status in gnome-shell source package in Disco: Invalid Status in gnome-shell-extension-ubuntu-dock source package in Disco: Fix Released Bug description: [Impact] When entering the lock-screen mode, gnome-shell disables all the extensions. It can happen that under certain conditions ubuntu-dock re-enables itself, causing the ubuntu-dock to appear in the lock-screen, exposing sensitive information. One possible way to reproduce this is to enable dash-to-dock and ubuntu-dock at the same time. [Test Case] 1. Make sure ubuntu-dock is enabled 2. Enable dash-to-dock too 3. Lock the screen 4. Make sure the dock does not appear on the lock screen 5. Make sure there is no warning is the journal [Possible Regressions] Even if it's something we don't really support please make sure that you can use dash-to-dock without uninstalling ubuntu-dock. [Original Bug] After an update from ubuntu 16.04 to 18.04 the dock is aviable on the lockscreen after user login. I did not configure this knowingly. Also i can start every application which is available on the dock. Settings, virtual box, visualstudio code and so on. After the update to 18.04 i just configure the screen frequency to 144Hz and the night mode on. And attach the dock on bottom. I later undid these customizations back to configuration before, but the dock is stil aviable on lockscreen. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-settings-daemon 3.28.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat May 5 18:30:16 2018 InstallationDate: Installed on 2018-04-08 (27 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: gnome-settings-daemon UpgradeStatus: Upgraded to bionic on 2018-05-01 (3 days ago) --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-08 (27 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell-extension-ubuntu-dock 0.9.1 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-05-01 (4 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1769383/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
Installed 4.20.0-rc7 kernel through UKUU, but still no sound on ASUS UX391U :/ -- 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/1784485 Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: Internal speaker - not sound at all Cable Headphonse - realy quiet disorted sound Bluetooth headphones - sound works fine On Windows 10 everything works fine. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pmichalski 7964 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Jul 30 22:32:10 2018 InstallationDate: Installed on 2018-07-17 (12 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Wbudowany dźwięk - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm2988 F pulseaudio pmichalski 7964 F pulseaudio Symptom_Jack: Mic, Internal Symptom_Type: No sound at all Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX391UA.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX391UA 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.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook S dmi.product.name: ZenBook S UX391UA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1808853] [NEW] Buggy WhatsApp misdetects Chromium with Ubuntu's patched useragent
Public bug reported: Starting about a week ago, https://web.whatsapp.com stopped working with Ubuntu's Chromium, it suggests to install Google Chrome. If change useragent from userAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Ubuntu Chromium/70.0.3538.110 Chrome/70.0.3538.110 Safari/537.36 to userAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.110 Safari/537.36 or rebuild chromium-browser without chromium_useragent.patch, than this piece of buggy shit starts to work with Chromium I tried to reach WhatsApp monkeys by writing to webclient_...@support.whatsapp.com, but did not get an answer from human. Sorry, but I hate WhatsApp. I've made this bug just to inform you about the problems that the patched useragent may cause and to help other people solve the problem. ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New -- 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/1808853 Title: Buggy WhatsApp misdetects Chromium with Ubuntu's patched useragent Status in chromium-browser package in Ubuntu: New Bug description: Starting about a week ago, https://web.whatsapp.com stopped working with Ubuntu's Chromium, it suggests to install Google Chrome. If change useragent from userAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Ubuntu Chromium/70.0.3538.110 Chrome/70.0.3538.110 Safari/537.36 to userAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.110 Safari/537.36 or rebuild chromium-browser without chromium_useragent.patch, than this piece of buggy shit starts to work with Chromium I tried to reach WhatsApp monkeys by writing to webclient_...@support.whatsapp.com, but did not get an answer from human. Sorry, but I hate WhatsApp. I've made this bug just to inform you about the problems that the patched useragent may cause and to help other people solve the problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1808853/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1808851] [NEW] Snap applications crush wayland session
*** This bug is a duplicate of bug 1808340 *** https://bugs.launchpad.net/bugs/1808340 Public bug reported: When you attempt opening a snap application the Wayland session crushes and you return to the login screen. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: mutter 3.30.2-1~ubuntu18.10.1 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Dec 17 15:52:10 2018 InstallationDate: Installed on 2018-09-21 (86 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180920) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic third-party-packages ** This bug has been marked a duplicate of bug 1808340 Snap applications crush wayland session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1808851 Title: Snap applications crush wayland session Status in mutter package in Ubuntu: New Bug description: When you attempt opening a snap application the Wayland session crushes and you return to the login screen. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: mutter 3.30.2-1~ubuntu18.10.1 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Dec 17 15:52:10 2018 InstallationDate: Installed on 2018-09-21 (86 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180920) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1808851/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
Audio fixes start with Linux 4.20-rc6, not 4.19 -- 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/1784485 Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: Internal speaker - not sound at all Cable Headphonse - realy quiet disorted sound Bluetooth headphones - sound works fine On Windows 10 everything works fine. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pmichalski 7964 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Jul 30 22:32:10 2018 InstallationDate: Installed on 2018-07-17 (12 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Wbudowany dźwięk - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm2988 F pulseaudio pmichalski 7964 F pulseaudio Symptom_Jack: Mic, Internal Symptom_Type: No sound at all Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX391UA.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX391UA 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.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook S dmi.product.name: ZenBook S UX391UA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
@Greg (buchovagabond) Without adding those 3 patches and the SND_PCI_QUIRK(0x1043, 0x10a1, "ASUS UX391UA", ALC294_FIXUP_ASUS_SPK) tweak to to /sound/pci/hda/patch_realtek.c ? So only updating with UKUU will work? -- 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/1784485 Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: Internal speaker - not sound at all Cable Headphonse - realy quiet disorted sound Bluetooth headphones - sound works fine On Windows 10 everything works fine. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pmichalski 7964 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Jul 30 22:32:10 2018 InstallationDate: Installed on 2018-07-17 (12 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Wbudowany dźwięk - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm2988 F pulseaudio pmichalski 7964 F pulseaudio Symptom_Jack: Mic, Internal Symptom_Type: No sound at all Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX391UA.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX391UA 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.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook S dmi.product.name: ZenBook S UX391UA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1702873] Re: [snap] artifacts when using HiDPI display
- evince snap: the arrow cursor is big, but other cursors (hand for clicking links in PDFs, text caret) are not scaled -- 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/1702873 Title: [snap] artifacts when using HiDPI display Status in libreoffice package in Ubuntu: Confirmed Bug description: I am using a HiDPI display. At scale 2. The cursor is tiny when inside the window of the app. Many icons on the toolbar are blurry, more than usual. I report these commands' output as requested: lsb_release -a snap info --verbose libreoffice core luca@xpsluca:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 16.10 Release: 16.10 Codename: yakkety luca@xpsluca:~$ snap info --verbose libreoffice core name: libreoffice summary: "LibreOffice is a powerful office suite including word processing and creation of spreadsheets, slideshows and databases" publisher: canonical contact: http://www.libreoffice.org/get-help/community-support/ description: | LibreOffice is a powerful office suite – its clean interface and feature-rich tools help you unleash your creativity and enhance your productivity. LibreOffice includes several applications that make it the most powerful Free and Open Source office suite on the market: Writer (word processing), Calc (spreadsheets), Impress (presentations), Draw (vector graphics and flowcharts), Base (databases), and Math (formula editing). commands: - libreoffice.base - libreoffice.calc - libreoffice.draw - libreoffice.impress - libreoffice - libreoffice.math - libreoffice.writer notes: private: false confinement: strict devmode: false jailmode: false trymode: false enabled: true broken: false tracking: beta installed: 5.3.4.2 (21) 368MB refreshed: 2017-07-01 19:14:41 +0200 CEST channels: latest/stable:5.3.2.2 (19) 375MB - latest/candidate: 5.3.2.2 (19) 375MB - latest/beta: 5.3.4.2 (21) 368MB - latest/edge: 5.3.2.2 (19) 375MB - --- name: core summary: "snapd runtime environment" publisher: canonical contact: snappy-canonical-storeacco...@canonical.com description: | The core runtime environment for snapd type: core notes: private: false confinement: strict devmode: false jailmode: false trymode: false enabled: true broken: false tracking: stable installed: 16-2 (2312) 83MB refreshed: 2017-04-11 14:28:54 +0200 CEST channels: latest/stable:16-2 (2312) 83MB - latest/candidate: 16-2.26.8(2329) 84MB - latest/beta: 16-2.26.8(2329) 84MB - latest/edge: 16-2.26.8+git258.fa4bcff (2343) 85MB - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1702873/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
Confirmed 4.19 fixes audio! Excellent work guys! -- 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/1784485 Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: Internal speaker - not sound at all Cable Headphonse - realy quiet disorted sound Bluetooth headphones - sound works fine On Windows 10 everything works fine. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pmichalski 7964 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Jul 30 22:32:10 2018 InstallationDate: Installed on 2018-07-17 (12 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Wbudowany dźwięk - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm2988 F pulseaudio pmichalski 7964 F pulseaudio Symptom_Jack: Mic, Internal Symptom_Type: No sound at all Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX391UA.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX391UA 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.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook S dmi.product.name: ZenBook S UX391UA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 388547]
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/xorg/xserver/issues/564. -- 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/388547 Title: Volume keys don't work inside a full-screen game Status in One Hundred Papercuts: Confirmed Status in X.Org X server: Unknown Status in gnome-settings-daemon package in Ubuntu: Confirmed Bug description: When I'm playing games in fullscreen mode, I cannot change the volume (laptop, HP tx2115nr with Jaunty) using my notebook keys. It's not possible to use my Play/Pause/Stop hotkeys (right side of my screen). I would like to change my volume without have to exit the game. To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/388547/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 388547] Re: Volume keys don't work inside a full-screen game
** Changed in: xorg-server Status: Confirmed => Unknown -- 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/388547 Title: Volume keys don't work inside a full-screen game Status in One Hundred Papercuts: Confirmed Status in X.Org X server: Unknown Status in gnome-settings-daemon package in Ubuntu: Confirmed Bug description: When I'm playing games in fullscreen mode, I cannot change the volume (laptop, HP tx2115nr with Jaunty) using my notebook keys. It's not possible to use my Play/Pause/Stop hotkeys (right side of my screen). I would like to change my volume without have to exit the game. To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/388547/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 388547]
This issue got *much* worse recently, it now affects keyboard layout switching as well, so many applications like tuxpaint became completely unusable. Example: In Ubuntu 14.04, I run `tuxpaint --fullscreen`. I press Win+Space, the Gnome-defined method to switch my keyboard layout from "us,gr" to "gr,us". unity-settings-daemon cannot read the layout change because tuxpaint has the keyboard grab. (It's the same in other distros too, it's not Ubuntu specific) So I can't type Greek with the tuxpaint Text tool, making tuxpaint completely useless in fullscreen mode. Until some years ago, Gnome allowed XKB to manage the layout switching, which worked fine even in fullscreen applications. It no longer allows it, they try to manage it with gnome-settings-daemon etc. If there's no intention to fix this in Xorg, please mention it here, so that we can show that response to Gnome developers and tell them to let XKB manage the keyboard layouts instead. -- 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/388547 Title: Volume keys don't work inside a full-screen game Status in One Hundred Papercuts: Confirmed Status in X.Org X server: Unknown Status in gnome-settings-daemon package in Ubuntu: Confirmed Bug description: When I'm playing games in fullscreen mode, I cannot change the volume (laptop, HP tx2115nr with Jaunty) using my notebook keys. It's not possible to use my Play/Pause/Stop hotkeys (right side of my screen). I would like to change my volume without have to exit the game. To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/388547/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
I just saw that the fix is included in the new 4.19.10 kernel. You can use UKUU to install. --- Jian-Hong Pan (2): ALSA: hda/realtek: Enable audio jacks of ASUS UX533FD with ALC294 ALSA: hda/realtek: Enable audio jacks of ASUS UX433FN/UX333FA with ALC294 -- 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/1784485 Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: Internal speaker - not sound at all Cable Headphonse - realy quiet disorted sound Bluetooth headphones - sound works fine On Windows 10 everything works fine. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pmichalski 7964 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Jul 30 22:32:10 2018 InstallationDate: Installed on 2018-07-17 (12 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Wbudowany dźwięk - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm2988 F pulseaudio pmichalski 7964 F pulseaudio Symptom_Jack: Mic, Internal Symptom_Type: No sound at all Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX391UA.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX391UA 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.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook S dmi.product.name: ZenBook S UX391UA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1767445] Re: Uninstalled snaps show most recent channel version, not version to be installed by default
** No longer affects: snapstore -- 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/1767445 Title: Uninstalled snaps show most recent channel version, not version to be installed by default Status in snapd: Won't Fix Status in gnome-software package in Ubuntu: Fix Released Status in gnome-software source package in Xenial: Fix Released Status in gnome-software source package in Bionic: Fix Released Status in gnome-software source package in Cosmic: Fix Released Bug description: [Impact] GNOME Software can show incorrect version of snap that will be installed on details page. [Test Case] 1. Open GNOME Software. Ensure blender or spotify snap is not installed. 2. Select blender or spotify snap (tried 28-04-2018, may change if store versions are changed) Expected result: Version label shows version to be installed (stable channel by default) Observed result: Version label shows most recently uploaded version, i.e. from the edge channel. This is not the version that will be installed when clicking install. [Regression Potential] The logic around choosing which version value to show was changed. Could create other bugs with this data. Orignial text: Ubuntu Software, when showing metadata about a snap package, is most of the time, likely to get information which is misleading, since it shows info from the *most recently* uploaded snap, regardless of which channel the snap was uploaded to. An example of this is to search for blender, and see that the version shows the edge channel - 2.80-4de142e0b7b and not the stable channel - 2.79. After actually installing the application, the correct metadata is shown. See https://forum.snapcraft.io/t/unexpected-revision-information- exposed-in-some-situations/5163 for more details. To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1767445/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1702873] Re: [snap] artifacts when using HiDPI display
I don't have a HiDPI-capable monitor, however I am able to observe and confirm the issue by setting the display scale to 200% (on the display control panel, `gnome-control-center display`). All UI elements become big, except for the cursors in some snaps. Interestingly, not all snaps are affected: - libreoffice, chromium and firefox have small cursors - telegram-desktop behaves correctly (big cursors) - gnome-characters behaves correctly (big cursors) - gnome-calculators has mixed results: the arrow cursor is big, but the text caret cursor is small -- 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/1702873 Title: [snap] artifacts when using HiDPI display Status in libreoffice package in Ubuntu: Confirmed Bug description: I am using a HiDPI display. At scale 2. The cursor is tiny when inside the window of the app. Many icons on the toolbar are blurry, more than usual. I report these commands' output as requested: lsb_release -a snap info --verbose libreoffice core luca@xpsluca:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 16.10 Release: 16.10 Codename: yakkety luca@xpsluca:~$ snap info --verbose libreoffice core name: libreoffice summary: "LibreOffice is a powerful office suite including word processing and creation of spreadsheets, slideshows and databases" publisher: canonical contact: http://www.libreoffice.org/get-help/community-support/ description: | LibreOffice is a powerful office suite – its clean interface and feature-rich tools help you unleash your creativity and enhance your productivity. LibreOffice includes several applications that make it the most powerful Free and Open Source office suite on the market: Writer (word processing), Calc (spreadsheets), Impress (presentations), Draw (vector graphics and flowcharts), Base (databases), and Math (formula editing). commands: - libreoffice.base - libreoffice.calc - libreoffice.draw - libreoffice.impress - libreoffice - libreoffice.math - libreoffice.writer notes: private: false confinement: strict devmode: false jailmode: false trymode: false enabled: true broken: false tracking: beta installed: 5.3.4.2 (21) 368MB refreshed: 2017-07-01 19:14:41 +0200 CEST channels: latest/stable:5.3.2.2 (19) 375MB - latest/candidate: 5.3.2.2 (19) 375MB - latest/beta: 5.3.4.2 (21) 368MB - latest/edge: 5.3.2.2 (19) 375MB - --- name: core summary: "snapd runtime environment" publisher: canonical contact: snappy-canonical-storeacco...@canonical.com description: | The core runtime environment for snapd type: core notes: private: false confinement: strict devmode: false jailmode: false trymode: false enabled: true broken: false tracking: stable installed: 16-2 (2312) 83MB refreshed: 2017-04-11 14:28:54 +0200 CEST channels: latest/stable:16-2 (2312) 83MB - latest/candidate: 16-2.26.8(2329) 84MB - latest/beta: 16-2.26.8(2329) 84MB - latest/edge: 16-2.26.8+git258.fa4bcff (2343) 85MB - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1702873/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1799242] Re: gnome-shell crashes when locking screen while dock widget is in focus
Hello Daniel, My apologies for the late reply. This is the link I get from errors.ubuntu.com for this issue: https://errors.ubuntu.com/oops/a46fb0ae-d608-11e8-9484-fa163ee63de6 -- 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/1799242 Title: gnome-shell crashes when locking screen while dock widget is in focus Status in gnome-shell package in Ubuntu: Incomplete Bug description: gnome-shell crashes with signal 11 (segmentation fault) when I try to lock the screen while a widget in the dock is in focus. The end result is that the screen either does not lock, and gnome-shell reloads, or it hangs (can move mouse, but mouse clicks or keyboard presses don't seem to have any effect). Either way no screen lock occurs. This is on a dual-screen setup, where I have the dock visible on both screens. Steps to reproduce: 1) Open a terminal (or any app, terminal is just an example) 2) Open a new terminal with cntrl+N 3) Click on the terminal icon on the dock, so it shows both instances of the terminal app 4) Try to lock the screen with super+L 5) Observe crash Attached is the output of syslog at the exact moment the crash occurs. Output of lsb_release -rd: Description: Ubuntu 18.04.1 LTS Release: 18.04 Output of apt-cache policy gnome-shell: gnome-shell: Installed: 3.28.3-0ubuntu0.18.04.2 Candidate: 3.28.3-0ubuntu0.18.04.2 Version table: *** 3.28.3-0ubuntu0.18.04.2 500 500 http://nl.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.28.1-0ubuntu2 500 500 http://nl.archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1799242/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1808833] [NEW] /usr/lib/geoclue-2.0/demos/where-am-i:*** stack smashing detected ***: terminated
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding geoclue-2.0. This problem was most recently seen with package version 2.4.7-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/e71f932716a2cf0fc3e6d66988e7ecc2943fdc97 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: geoclue-2.0 (Ubuntu) Importance: Undecided Status: New ** Tags: artful bionic kylin-17.10 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to geoclue-2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1808833 Title: /usr/lib/geoclue-2.0/demos/where-am-i:*** stack smashing detected ***: terminated Status in geoclue-2.0 package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding geoclue-2.0. This problem was most recently seen with package version 2.4.7-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/e71f932716a2cf0fc3e6d66988e7ecc2943fdc97 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/geoclue-2.0/+bug/1808833/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
I have a ASUS UX391UA and finally want to get the sound working. Is it theoretically possible to apply the above mentioned fix using the Kernel Update Utility for Ubuntu (https://github.com/teejee2008/ukuu)? What's the proper way to apply the following patches afterwards? https://lkml.org/lkml/2018/12/7/158 https://lkml.org/lkml/2018/12/7/160 https://lkml.org/lkml/2018/12/7/159 -- 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/1784485 Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: Internal speaker - not sound at all Cable Headphonse - realy quiet disorted sound Bluetooth headphones - sound works fine On Windows 10 everything works fine. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pmichalski 7964 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Jul 30 22:32:10 2018 InstallationDate: Installed on 2018-07-17 (12 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Wbudowany dźwięk - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm2988 F pulseaudio pmichalski 7964 F pulseaudio Symptom_Jack: Mic, Internal Symptom_Type: No sound at all Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX391UA.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX391UA 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.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook S dmi.product.name: ZenBook S UX391UA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1800179] Re: Search in recent files list only works with lowercase letters
** Description changed: + * Impact + The document filter is case sensitive which is confusing/not convenient + + * Test case + - Open a document with an Uppercase letter + - close it + - click on 'open' and type the name with a lowercase + + -> it should list the document + + * Regression potential + The code change is in the filtering code, just test that. Also it's a small behaviour change but the new way should be easier/less confusing + + + When clicking “Open” and typing to search the recently opened files, any search involving uppercase letters fails to return any result, even if files with uppercase letters in their file names have recently been opened. Searching for the same file names, but using all-lowercase letters, does yield results (see attached screenshot). So it seems that gedit converts the recently used file names to lowercase before comparing to the search term, which is incorrect. ** Description changed: * Impact The document filter is case sensitive which is confusing/not convenient * Test case - Open a document with an Uppercase letter - close it - - click on 'open' and type the name with a lowercase + - click on 'open' and type the name with an Uppercase -> it should list the document * Regression potential - The code change is in the filtering code, just test that. Also it's a small behaviour change but the new way should be easier/less confusing + The code change is in the filtering code, just test that. When clicking “Open” and typing to search the recently opened files, any search involving uppercase letters fails to return any result, even if files with uppercase letters in their file names have recently been opened. Searching for the same file names, but using all-lowercase letters, does yield results (see attached screenshot). So it seems that gedit converts the recently used file names to lowercase before comparing to the search term, which is incorrect. -- 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/1800179 Title: Search in recent files list only works with lowercase letters Status in gedit package in Ubuntu: Fix Committed Bug description: * Impact The document filter is case sensitive which is confusing/not convenient * Test case - Open a document with an Uppercase letter - close it - click on 'open' and type the name with an Uppercase -> it should list the document * Regression potential The code change is in the filtering code, just test that. When clicking “Open” and typing to search the recently opened files, any search involving uppercase letters fails to return any result, even if files with uppercase letters in their file names have recently been opened. Searching for the same file names, but using all- lowercase letters, does yield results (see attached screenshot). So it seems that gedit converts the recently used file names to lowercase before comparing to the search term, which is incorrect. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1800179/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1745032] Re: AC adapter status not detected on Asus ZenBook UX410UAK
** Also affects: gnome-control-center (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: gnome-shell (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: upower (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: gnome-control-center (Ubuntu) Status: Confirmed => Fix Committed ** Changed in: gnome-shell (Ubuntu) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1745032 Title: AC adapter status not detected on Asus ZenBook UX410UAK Status in gnome-control-center package in Ubuntu: Fix Committed Status in gnome-shell package in Ubuntu: Fix Committed Status in linux package in Ubuntu: In Progress Status in upower package in Ubuntu: Confirmed Status in gnome-control-center source package in Bionic: New Status in gnome-shell source package in Bionic: New Status in linux source package in Bionic: New Status in upower source package in Bionic: New Bug description: === SRU Justification === [Impact] Some Asus laptops report "discharging" when the battery is full and AC is plugged [Test] Charge battery to full, the issue appears. Users report with the patch the behaviour is correct. [Fix] The discharge rate is 0 on those machines. Use that to detect the wrong status report. [Regression Potential] Low. The quirk uses strict DMI to match affected systems. === Original Bug Report === The AC adapter status is incorrectly reported when the battery is fully charged. It always shows as if the adapter is not plugged in. If the battery is drained for a while, the adapter status is shown correctly (both connects and disconnects are shown). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-31-generic 4.13.0-31.34 ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13 Uname: Linux 4.13.0-31-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: abarto 1388 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Jan 23 18:26:18 2018 InstallationDate: Installed on 2018-01-23 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 04f2:b57a Chicony Electronics Co., Ltd Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX410UAK ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed root=UUID=58ea0561-3f74-4566-9332-5e7021275160 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-31-generic N/A linux-backports-modules-4.13.0-31-generic N/A linux-firmware 1.169.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX410UAK.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX410UAK 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.:bvrUX410UAK.306:bd08/08/2017:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX410UAK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1745032/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1808826] [NEW] install intel draphic drivers
Public bug reported: for Ubuntu 16.04 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-140.166-generic 4.4.162 Uname: Linux 4.4.0-140-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: i386 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Dec 17 07:16:01 2018 DistUpgraded: 2018-12-15 10:13:31,867 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0042] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Core Processor Integrated Graphics Controller [103c:170b] InstallationDate: Installed on 2018-11-26 (20 days ago) InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release i386 (20130213) MachineType: Hewlett-Packard HP Z200 Workstation ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-140-generic root=UUID=62803ccc-2439-44dd-bfbd-535f9af3ea72 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2018-12-15 (1 days ago) dmi.bios.date: 03/09/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786H3 v01.13 dmi.board.asset.tag: 2UA12218BX dmi.board.name: 0B40h dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: 2UA12218BX dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr786H3v01.13:bd03/09/2011:svnHewlett-Packard:pnHPZ200Workstation:pvr:rvnHewlett-Packard:rn0B40h:rvr:cvnHewlett-Packard:ct6:cvr: dmi.product.name: HP Z200 Workstation dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Mon Dec 17 06:37:20 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.4-0ubuntu0.8 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug compiz-0.9 i386 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/1808826 Title: install intel draphic drivers Status in xorg package in Ubuntu: New Bug description: for Ubuntu 16.04 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-140.166-generic 4.4.162 Uname: Linux 4.4.0-140-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: i386 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Dec 17 07:16:01 2018 DistUpgraded: 2018-12-15 10:13:31,867 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0042] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Core Processor Integrated Graphics Controller [103c:170b] InstallationDate: Installed on 2018-11-26 (20 days ago) InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release i386 (20130213) MachineType: Hewlett-Packard HP Z200 Workstation ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-140-generic root=UUID=62803ccc-2439-44dd-bfbd-535f9af3ea72 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2018-12-15 (1 days ago) dmi.bios.date: 03/09/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786H3 v01.13 dmi.board.asset.tag: 2UA12218BX dmi.board.name: 0B40h dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: 2UA12218BX dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlet
[Desktop-packages] [Bug 1804685] Re: Icon View Captions display in the wrong positions
(Uploaded SRU to bionic & cosmic) -- 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/1804685 Title: Icon View Captions display in the wrong positions Status in nautilus package in Ubuntu: Fix Released Bug description: * Impact The nautilus view doesn't display the informations with the selected layout * Test case 1. Change to 100% zoom 2. Go to Preferences > Icon View Captions 3. There are three captions: First, Second & Third When selecting details for those they should reflect in the right order * Regression potential The code change is only the order of the widget in the preference, check that the preferency/views tab is not buggy --- In the Preferences for Nautilus, under the Views tab, the user has the option to select information to appear in the "First", "Second", and "Third" position beneath icons. However, in icon view, whatever the user selects to appear in the "First" position will appear in the second location beneath the icon. Whatever the user selects to appear in the "Second" position will appear in the third, or bottom, position. Whatever the user selects to appear in the "Third" position will appear in the first, or top, position. I'm on Ubuntu 18.04.1 LTS Nautilus 3.26.4-0~ubuntu18.04.2 Thanks! Upstream bugs: https://gitlab.gnome.org/GNOME/nautilus/issues/343 https://gitlab.gnome.org/GNOME/nautilus/issues/766 Upstream Fix: https://gitlab.gnome.org/GNOME/nautilus/commit/86080e646a81679761e09aee4071abf68a2dac3b Steps to reproduce: 1. Change to 100% zoom 2. Go to Preferences > Icon View Captions 3. There are three captions: First, Second & Third I expect to see that the 1st caption is displayed just below the file/folder name, 2nd is below 1st and 3rd is below 2nd. Current behaviour: The order of the captions is mixed up. The current order is this: - File/Folder Name - Third caption - First caption - Second caption Expected behaviour: - File/Folder Name - First caption - Second caption - Third caption To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1804685/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 113338] Re: Cannot close a tab in Gedit by middle clicking the tab bar
The issue was fixed upstream in commit ad121f65 ** Changed in: gedit (Ubuntu) Status: Triaged => Fix Committed -- 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/113338 Title: Cannot close a tab in Gedit by middle clicking the tab bar Status in gedit: New Status in gedit package in Ubuntu: Fix Committed Bug description: Binary package hint: gedit See title. This is in 7.04 final. It is inconsistent with Firefox's behavior. To manage notifications about this bug go to: https://bugs.launchpad.net/gedit/+bug/113338/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1724921] Re: VLANs get incorrectly listed under Bluetooth
*** This bug is a duplicate of bug 1785311 *** https://bugs.launchpad.net/bugs/1785311 ** This bug has been marked a duplicate of bug 1785311 VLAN in GUI's network setting is under Bluetooth section -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1724921 Title: VLANs get incorrectly listed under Bluetooth Status in gnome-control-center package in Ubuntu: Confirmed Status in network-manager-applet package in Ubuntu: Confirmed Bug description: I expected them to show up under Wired because the VLANs' associated adapter is wired. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: network-manager-gnome 1.8.4-1ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Oct 19 11:25:17 2017 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-10-19 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) IpRoute: default via 192.168.50.253 dev vlan757 proto static metric 400 169.254.0.0/16 dev vlan757 scope link metric 1000 192.168.50.0/24 dev vlan757 proto kernel scope link src 192.168.50.222 metric 400 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager-applet UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE VLAN Camera 1a430a37-b4b3-461c-87bd-d60b547dd369 vlan 1508437383 Thu 19 Oct 2017 11:23:03 AM PDT yes 0 no/org/freedesktop/NetworkManager/Settings/4 yes vlan757 activated /org/freedesktop/NetworkManager/ActiveConnection/8 -- Wired connection 1 23ca82a4-d9c5-3d59-ac84-56db17873201 802-3-ethernet 1508433170 Thu 19 Oct 2017 10:12:50 AM PDT no 4294966297 no/org/freedesktop/NetworkManager/Settings/1 no -- -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.8.4connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1724921/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1808764] Re: It switches to English mode after I type the numbers from the numpad.
** Summary changed: - It switches to English mode after I type in the numbers on the numpad. + It switches to English mode after I type the numbers from the numpad. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus-chewing in Ubuntu. https://bugs.launchpad.net/bugs/1808764 Title: It switches to English mode after I type the numbers from the numpad. Status in ibus-chewing package in Ubuntu: New Bug description: I need to keep switching the English and Chinese mode to output Chinese. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: ibus-chewing 1.5.1-3 Uname: Linux 4.19.9-041909-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Dec 17 17:04:57 2018 InstallationDate: Installed on 2018-12-10 (6 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: ibus-chewing UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus-chewing/+bug/1808764/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1697183] Re: Unable to select realm for Juniper SSL VPN conntworkManaer Openconnectection in Ne
*** This bug is a duplicate of bug 1764047 *** https://bugs.launchpad.net/bugs/1764047 The issue looks similar to bug #1764047 ** Changed in: network-manager-applet (Ubuntu) Importance: Undecided => Low ** This bug has been marked a duplicate of bug 1764047 Unable to switch realm on authentication dialog -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1697183 Title: Unable to select realm for Juniper SSL VPN conntworkManaer Openconnectection in Ne Status in network-manager-applet package in Ubuntu: Confirmed Bug description: Under Ubuntu 17.04, with openconnect, I am attempting to log into a Juniper ssl vpn. I am prompted for my credentials and realm, but I am unable to select the realm. Any option I select is ignored, and the first realm is selected. # apt-cache policy network-manager-openconnect network-manager-openconnect: Installed: 1.2.4-1 Candidate: 1.2.4-1 Version table: *** 1.2.4-1 500 500 http://us.archive.ubuntu.com/ubuntu zesty/universe amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1697183/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1807460] Re: Filenames with spaces not accepted when connecting to certificate-authenticated wifi
The bug is fixed in 1.8.18 which is in cosmic/disco, let's SRU that to bionic ** Changed in: network-manager-applet (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1807460 Title: Filenames with spaces not accepted when connecting to certificate- authenticated wifi Status in network-manager-applet package in Ubuntu: Fix Released Bug description: This bug was encountered on a fresh install of Ubuntu 18.04.1 LTS When connecting to a certificate-authenticated wifi network (WPA/WPA2 Enterprise, authentication TLS) for the first time, the "Wi-Fi Network Authentication Required" dialogue is displayed, prompting the user to select their CA and user certificates. Unexpected behaviour: If any of the files have spaces in their filenames, after choosing them in the file picker the field is highlighted by a red box, and the 'Connect' button is greyed out. This is depicted in the attachment network-authentication-red-box- spaces-filename.png There is also no explanation offered for why the red box highlight is present - no tooltip, no help from pressing F1, no popup, and as far as I can find no logs. If you move/rename the file, so there are no spaces in the filename, the problem is worked around. The problem is not present on the edit connection dialogue; filenames with spaces are acceptable there. The problem was also not present on Ubuntu 16.04, and users who upgrade from 16.04 to 18.04 will find their connection keeps working. It is only when creating an entirely new connection (or after forgetting the connection and recreating it) that the problem dialog appears. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1807460/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1748839] Re: Problem to connect to WPA2/PEAP WIFI - gnome-shell
Bug #1761003 also may be related. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1748839 Title: Problem to connect to WPA2/PEAP WIFI - gnome-shell Status in network-manager package in Ubuntu: Confirmed Bug description: This problem is also happened on my desktop. After upgrading OS from Ubuntu 16.04 to Ubuntu 18.04.1 LTS, my PC could not connect and authenticate on WiFi with WPA2/PEAP/MSCHAPv2/no CA certificate/true username and password. I tried to solve the problem following URL link; however, it could not help me also. https://askubuntu.com/questions/279762/how-to-connect-to-wpa2-peap-mschapv2-enterprise-wifi-networks-that-dont-use-a-c My PC is HP Compaq Pro 4300, CPU: Intel® Core™ i3-3220 CPU @ 3.30GHz × 4, OS: Ubuntu 18.04.1 (64-bit). root@joe-UBTPC:/root # lspci 00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor DRAM Controller (rev 09) 00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller (rev 09) 00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 (rev 04) 00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 (rev 05) 00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller (rev 05) 00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 1 (rev b5) 00:1c.1 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 2 (rev b5) 00:1c.2 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 3 (rev b5) 00:1c.3 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 4 (rev b5) 00:1c.4 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 5 (rev b5) 00:1c.5 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 6 (rev b5) 00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 (rev 05) 00:1f.0 ISA bridge: Intel Corporation H61 Express Chipset Family LPC Controller (rev 05) 00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset Family SATA AHCI Controller (rev 05) 00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family SMBus Controller (rev 05) 03:00.0 Network controller: Ralink corp. RT5392 PCIe Wireless Network Adapter 06:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 07) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1748839/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1761003] Re: Bionic Beaver - not able to connect to WPA Enterprise EAP-TLS
Yes, may be related to Bug #1748839 reported by Petr Michalec on 2018-02-12! Almost a year ago! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1761003 Title: Bionic Beaver - not able to connect to WPA Enterprise EAP-TLS Status in NetworkManager: Confirmed Status in network-manager package in Ubuntu: Triaged Bug description: Hello, since update to Bionic Beaver I can't connect to my WPA2-Entertrise EAP TLS network. Running Freeradius 2.29 on a DDWRT router. In 16.04 it worked, in the dual boot Windows 10 environment it is still working with the same certificates. It is a hidden network, adding it by "connect to a hidden network" entering SSID, UserID, ca.pem as CA cert, user cert xxx.p12 file and user certificate password. Tried a lot not getting it working. The password entry dialog for the network is always popping up upon connection trials. The password is for sure the correct one, checked it very often. If I'm able to I'll attach a syslog and kern.log of error occurense. Thanks for investigation and inputs. Best regards Kitsab ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1:3.28.0-0ubuntu6 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Apr 3 23:52:23 2018 EcryptfsInUse: Yes ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2015-02-14 (1144 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1761003/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1804685] Re: Icon View Captions display in the wrong positions
That's fixed in disco with https://launchpad.net/ubuntu/+source/nautilus/1:3.30.4-1ubuntu1 ** Changed in: nautilus (Ubuntu) Status: Fix Committed => Fix Released ** Description changed: - In the Preferences for Nautilus, under the Views tab, the user has the - option to select information to appear in the "First", "Second", and - "Third" position beneath icons. However, in icon view, whatever the - user selects to appear in the "First" position will appear in the second - location beneath the icon. Whatever the user selects to appear in the - "Second" position will appear in the third, or bottom, position. - Whatever the user selects to appear in the "Third" position will appear - in the first, or top, position. + * Impact + The nautilus view doesn't display the informations with the selected layout + + * Test case + 1. Change to 100% zoom + 2. Go to Preferences > Icon View Captions + 3. There are three captions: First, Second & Third + + When selecting details for those they should reflect in the right order + + * Regression potential + The code change is only the order of the widget in the preference, check that the preferency/views tab is not buggy + + --- + + + In the Preferences for Nautilus, under the Views tab, the user has the option to select information to appear in the "First", "Second", and "Third" position beneath icons. However, in icon view, whatever the user selects to appear in the "First" position will appear in the second location beneath the icon. Whatever the user selects to appear in the "Second" position will appear in the third, or bottom, position. Whatever the user selects to appear in the "Third" position will appear in the first, or top, position. I'm on Ubuntu 18.04.1 LTS Nautilus 3.26.4-0~ubuntu18.04.2 Thanks! Upstream bugs: https://gitlab.gnome.org/GNOME/nautilus/issues/343 https://gitlab.gnome.org/GNOME/nautilus/issues/766 Upstream Fix: https://gitlab.gnome.org/GNOME/nautilus/commit/86080e646a81679761e09aee4071abf68a2dac3b Steps to reproduce: 1. Change to 100% zoom 2. Go to Preferences > Icon View Captions 3. There are three captions: First, Second & Third I expect to see that the 1st caption is displayed just below the file/folder name, 2nd is below 1st and 3rd is below 2nd. Current behaviour: The order of the captions is mixed up. The current order is this: - File/Folder Name - Third caption - First caption - Second caption Expected behaviour: - File/Folder Name - First caption - Second caption - Third caption -- 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/1804685 Title: Icon View Captions display in the wrong positions Status in nautilus package in Ubuntu: Fix Released Bug description: * Impact The nautilus view doesn't display the informations with the selected layout * Test case 1. Change to 100% zoom 2. Go to Preferences > Icon View Captions 3. There are three captions: First, Second & Third When selecting details for those they should reflect in the right order * Regression potential The code change is only the order of the widget in the preference, check that the preferency/views tab is not buggy --- In the Preferences for Nautilus, under the Views tab, the user has the option to select information to appear in the "First", "Second", and "Third" position beneath icons. However, in icon view, whatever the user selects to appear in the "First" position will appear in the second location beneath the icon. Whatever the user selects to appear in the "Second" position will appear in the third, or bottom, position. Whatever the user selects to appear in the "Third" position will appear in the first, or top, position. I'm on Ubuntu 18.04.1 LTS Nautilus 3.26.4-0~ubuntu18.04.2 Thanks! Upstream bugs: https://gitlab.gnome.org/GNOME/nautilus/issues/343 https://gitlab.gnome.org/GNOME/nautilus/issues/766 Upstream Fix: https://gitlab.gnome.org/GNOME/nautilus/commit/86080e646a81679761e09aee4071abf68a2dac3b Steps to reproduce: 1. Change to 100% zoom 2. Go to Preferences > Icon View Captions 3. There are three captions: First, Second & Third I expect to see that the 1st caption is displayed just below the file/folder name, 2nd is below 1st and 3rd is below 2nd. Current behaviour: The order of the captions is mixed up. The current order is this: - File/Folder Name - Third caption - First caption - Second caption Expected behaviour: - File/Folder Name - First caption - Second caption - Third caption To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1804685/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages
[Desktop-packages] [Bug 1748839] Re: Problem to connect to WPA2/PEAP WIFI - gnome-shell
OK, how'd this slip through? No WPA options anywhere? Only 2 WEP options. 2 new installs, on different machines, I can not connect to my WPA (TKIP+AES) network wirelessly!!! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1748839 Title: Problem to connect to WPA2/PEAP WIFI - gnome-shell Status in network-manager package in Ubuntu: Confirmed Bug description: This problem is also happened on my desktop. After upgrading OS from Ubuntu 16.04 to Ubuntu 18.04.1 LTS, my PC could not connect and authenticate on WiFi with WPA2/PEAP/MSCHAPv2/no CA certificate/true username and password. I tried to solve the problem following URL link; however, it could not help me also. https://askubuntu.com/questions/279762/how-to-connect-to-wpa2-peap-mschapv2-enterprise-wifi-networks-that-dont-use-a-c My PC is HP Compaq Pro 4300, CPU: Intel® Core™ i3-3220 CPU @ 3.30GHz × 4, OS: Ubuntu 18.04.1 (64-bit). root@joe-UBTPC:/root # lspci 00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor DRAM Controller (rev 09) 00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller (rev 09) 00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 (rev 04) 00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 (rev 05) 00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller (rev 05) 00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 1 (rev b5) 00:1c.1 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 2 (rev b5) 00:1c.2 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 3 (rev b5) 00:1c.3 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 4 (rev b5) 00:1c.4 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 5 (rev b5) 00:1c.5 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 6 (rev b5) 00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 (rev 05) 00:1f.0 ISA bridge: Intel Corporation H61 Express Chipset Family LPC Controller (rev 05) 00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset Family SATA AHCI Controller (rev 05) 00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family SMBus Controller (rev 05) 03:00.0 Network controller: Ralink corp. RT5392 PCIe Wireless Network Adapter 06:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 07) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1748839/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1803142] Proposed package upload rejected
An upload of libreoffice to cosmic-proposed has been rejected from the upload queue for the following reason: "Includes unexpected config file change.". -- 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/1803142 Title: [SRU] libreoffice 6.1.3 for cosmic Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice-l10n package in Ubuntu: Fix Released Status in libreoffice source package in Cosmic: Fix Committed Status in libreoffice-l10n source package in Cosmic: Fix Committed Bug description: [Impact] * LibreOffice 6.1.3 is the third bugfix release of the fresh 6.1 line. Version 6.1.2 is currently in cosmic. For a list of fixed bugs compared to 6.1.2 see the list of bugs fixed in the two release candidates: https://wiki.documentfoundation.org/Releases/6.1.3/RC1#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/6.1.3/RC2#List_of_fixed_bugs (that's a total of 66 bugs) * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Test Case] * No specific test case, bugs fixed upstream hopefully come with unit/regression tests, and the release itself is extensively exercised upstream (both in an automated manner and manually) by a community of testers. Each minor release normally goes through two release candidates. * The libreoffice packages include autopkgtests, those should be run and verified to pass. * General smoke testing of all the applications in the office suite should be carried out. [Regression Potential] * A minor release with a total of 66 bug fixes always carries the potential for introducing regressions, even though it is a bugfix-only release, meaning that no new features were added, and no existing features were removed. * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1803142/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1808147] Proposed package upload rejected
An upload of libreoffice to cosmic-proposed has been rejected from the upload queue for the following reason: "Includes unexpected config file change.". -- 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/1808147 Title: autopkgtests fail on s390x Status in libreoffice package in Ubuntu: Fix Released Bug description: libreoffice autopkgtests on s390x started failing reliably on 2018-12-11. This corresponds to when a new version of autopkgtest was deployed to the production infrastructure: https://lists.ubuntu.com/archives /ubuntu-devel/2018-December/040564.html The failing test is "smoketest". It has the "skippable" restriction, which was previously unknown, and as a result the test was skipped altogether. "skippable" is now a valid and understood restriction, so the test is being run, but it fails: […] mkdir -p /tmp/autopkgtest.A1jy64/build.urp/src/workdir/CustomTarget/i18npool/textconversion/ S=/tmp/autopkgtest.A1jy64/build.urp/src && I=$S/instdir && W=$S/workdir && touch $W/Headers/Library/libcollator_data.so S=/tmp/autopkgtest.A1jy64/build.urp/src && I=$S/instdir && W=$S/workdir && touch $W/Headers/Library/libdict_ja.so S=/tmp/autopkgtest.A1jy64/build.urp/src && I=$S/instdir && W=$S/workdir && touch $W/Headers/Library/libdict_zh.so S=/tmp/autopkgtest.A1jy64/build.urp/src && I=$S/instdir && W=$S/workdir && touch $W/Headers/Library/libindex_data.so S=/tmp/autopkgtest.A1jy64/build.urp/src && I=$S/instdir && W=$S/workdir && touch $W/Headers/Library/liblocaledata_en.so /tmp/autopkgtest.A1jy64/build.urp/src/solenv/gbuild/Package.mk:82: *** Something depends on package test_unittest which does not exist.. Stop. make[1]: *** Waiting for unfinished jobs S=/tmp/autopkgtest.A1jy64/build.urp/src && I=$S/instdir && W=$S/workdir && touch $W/Headers/Library/libtextconv_dict.so [build PKG] test_unittest make[1]: Leaving directory '/tmp/autopkgtest.A1jy64/build.urp/src' make: *** [Makefile:112: i18npool.all] Error 2 autopkgtest [13:27:33]: test smoketest: ---] autopkgtest [13:27:34]: test smoketest: - - - - - - - - - - results - - - - - - - - - - smoketestFAIL non-zero exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1808147/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1793410] Re: [Acer Swift SF315-52, Realtek ALC256, Mic, Internal] Internal microphone not working
Sorry you are right. I'm not really familiar with alsa much but triaged a few similar issues recently and tried to help a bit. https://git.kernel.org/pub/scm/linux/kernel/git/next/linux- next.git/tree/sound/pci/hda/patch_realtek.c has mention of hacks with the ALC256 but for asus configs, unsure they would adapt well. https://bugzilla.kernel.org/show_bug.cgi?id=201251 is an upstream kernel bug that mentions swift configurations so maybe it's worth following/commenting there ** Bug watch added: Linux Kernel Bug Tracker #201251 https://bugzilla.kernel.org/show_bug.cgi?id=201251 -- 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/1793410 Title: [Acer Swift SF315-52, Realtek ALC256, Mic, Internal] Internal microphone not working Status in alsa-driver package in Ubuntu: Confirmed Bug description: Recently bought a new Acer Swift 3 laptop and installed Ubuntu 18.04 on it. Everything works except the internal microphone. I have also tested with an external microphone and this didn't work either. I have worked my way through all the suggested solutions I could find, including trying to reconfigure the pins using hdajacketask. In pavucontrol I have options for Internal Microphone and Microphone (unplugged) but the internal mic only captures static noise. The latest HD-Audio Codec-Specific Models has configurations for alc255-acer and alc256 for some other models, but setting options snd- hda-intel model=MODEL in /etc/modprobe.d/alsa-base.conf does not solve the issue with any of these. Some info - lspci | grep -I audio: 00:1f.3 Multimedia audio controller: Intel Corporation Sunrise Point- LP HD Audio (rev 21) cat /proc/asound/cards: 0 [PCH ]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0xdf1a8000 irq 127 dmesg | grep snd: [3.944593] snd_hda_core: loading out-of-tree module taints kernel. [3.956337] snd_soc_skl: Unknown symbol snd_hdac_display_power (err 0) [3.956422] snd_soc_skl: Unknown symbol snd_hdac_i915_exit (err 0) [4.000880] snd_hda_intel :00:1f.3: Probing card using HDA DKMS, version 0.201808050301~ubuntu18.04.1 [4.000895] snd_hda_intel :00:1f.3: enabling device ( -> 0002) [4.013061] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC256: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker [4.013063] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [4.013065] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) [4.013066] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 [4.013066] snd_hda_codec_realtek hdaudioC0D0:inputs: [4.013068] snd_hda_codec_realtek hdaudioC0D0: Mic=0x18 [4.013069] snd_hda_codec_realtek hdaudioC0D0: Internal Mic=0x12 info on node 12 from cat /proc/asound/card*/codec\#*: Node 0x12 [Pin Complex] wcaps 0x40040b: Stereo Amp-In Control: name="Internal Mic Boost Volume", index=0, device=0 ControlAmp: chs=3, dir=In, idx=0, ofs=0 Amp-In caps: ofs=0x00, nsteps=0x03, stepsize=0x27, mute=0 Amp-In vals: [0x02 0x02] Pincap 0x0020: IN Pin Default 0x4000: [N/A] Line Out at Ext N/A Conn = Unknown, Color = Unknown DefAssociation = 0x0, Sequence = 0x0 Pin-ctls: 0x20: IN Power states: D0 D1 D2 D3 EPSS Power: setting=D0, actual=D0 Let me know if you need any other information. James --- Tags: bionic Uname: Linux 4.15.0-34-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) _MarkForUpload: True dmi.bios.date: 06/22/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V1.04 dmi.board.asset.tag: Default string dmi.board.name: Erdinger_KL dmi.board.vendor: KBL dmi.board.version: V1.04 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.04 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV1.04:bd06/22/2018:svnAcer:pnSwiftSF315-52:pvrV1.04:rvnKBL:rnErdinger_KL:rvrV1.04:cvnAcer:ct10:cvrV1.04: dmi.product.family: Swift 3 dmi.product.name: Swift SF315-52 dmi.product.version: V1.04 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1793410/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1784485] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1784485 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1784485 Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: Internal speaker - not sound at all Cable Headphonse - realy quiet disorted sound Bluetooth headphones - sound works fine On Windows 10 everything works fine. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pmichalski 7964 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Jul 30 22:32:10 2018 InstallationDate: Installed on 2018-07-17 (12 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Wbudowany dźwięk - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm2988 F pulseaudio pmichalski 7964 F pulseaudio Symptom_Jack: Mic, Internal Symptom_Type: No sound at all Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX391UA.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX391UA 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.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook S dmi.product.name: ZenBook S UX391UA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1808705] Re: printing on remote printer from GTK applications fails using duplex
** Changed in: cups-filters (Ubuntu) Assignee: (unassigned) => Till Kamppeter (till-kamppeter) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups-filters in Ubuntu. https://bugs.launchpad.net/bugs/1808705 Title: printing on remote printer from GTK applications fails using duplex Status in cups-filters package in Ubuntu: New Bug description: Steps to reproduce: 1. add remote ipp printer (remote is running ubuntu cups) using system-config-printer -> shows printer type "remote printer", printers setting in system-config-printer shows duplex, paper and other options from remote ppd, there is no local ppd in /etc/cups/ppd/ for this printer and no MakeModel in printers.conf. 2. try to print from firefox -> Duplex, Paper Type and other options are greyed out and shown as "not available" Workaround: 1. copy ppd from remote cups server, though this may not always work (filters not available locally or remote cups not accepted binary blob already processed by cupsFilter) 2. use generic ipp profile (does not support all target features) 3. use driverless to generate ppd (may not catch all target features) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cups-filters 1.20.2-0ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic i686 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: i386 Date: Sun Dec 16 13:36:17 2018 InstallationDate: Installed on 2015-09-14 (1189 days ago) InstallationMedia: Lubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805) Lpstat: device for HLL2300D: ipp://172.16.1.20:631/printers/HLL2300D device for Kyocera-Mita-FS-1020D: socket://172.16.1.21 Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 006: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox Papersize: a4 PpdFiles: Kyocera-Mita-FS-1020D: Kyocera Mita FS-1020D HLL2300D: Brother HL-L2300D for CUPS (remote) ProcEnviron: LANGUAGE=de_DE TERM=xterm-256color PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic root=UUID=c34300f7-d295-40ce-8c33-586987f5f41f ro quiet splash SourcePackage: cups-filters UpgradeStatus: Upgraded to bionic on 2018-09-09 (97 days ago) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1808705/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1784485 Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Status in linux package in Ubuntu: New Bug description: Internal speaker - not sound at all Cable Headphonse - realy quiet disorted sound Bluetooth headphones - sound works fine On Windows 10 everything works fine. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pmichalski 7964 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Jul 30 22:32:10 2018 InstallationDate: Installed on 2018-07-17 (12 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Wbudowany dźwięk - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm2988 F pulseaudio pmichalski 7964 F pulseaudio Symptom_Jack: Mic, Internal Symptom_Type: No sound at all Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX391UA.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX391UA 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.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook S dmi.product.name: ZenBook S UX391UA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1808785] Re: Searching for emoji in the snap yields no results 😭
** Tags added: snap -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-characters in Ubuntu. https://bugs.launchpad.net/bugs/1808785 Title: Searching for emoji in the snap yields no results 😭 Status in gnome-characters package in Ubuntu: Confirmed Bug description: In the snap version, searching for an emoji by name does not generate any results. If I do the same search in the deb version then things work as expected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-characters/+bug/1808785/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1769383] Re: Ubuntu dock/launcher is shown on the lock screen
Dom Hudson But this (https://bugs.launchpad.net/ubuntu/cosmic/+source /gnome-shell-extension-ubuntu-dock/+bug/1769383/comments/48) says it is released on Ubuntu Disco. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1769383 Title: Ubuntu dock/launcher is shown on the lock screen Status in gnome-shell package in Ubuntu: Invalid Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Status in gnome-shell source package in Bionic: Invalid Status in gnome-shell-extension-ubuntu-dock source package in Bionic: In Progress Status in gnome-shell source package in Cosmic: Invalid Status in gnome-shell-extension-ubuntu-dock source package in Cosmic: In Progress Status in gnome-shell source package in Disco: Invalid Status in gnome-shell-extension-ubuntu-dock source package in Disco: Fix Released Bug description: [Impact] When entering the lock-screen mode, gnome-shell disables all the extensions. It can happen that under certain conditions ubuntu-dock re-enables itself, causing the ubuntu-dock to appear in the lock-screen, exposing sensitive information. One possible way to reproduce this is to enable dash-to-dock and ubuntu-dock at the same time. [Test Case] 1. Make sure ubuntu-dock is enabled 2. Enable dash-to-dock too 3. Lock the screen 4. Make sure the dock does not appear on the lock screen 5. Make sure there is no warning is the journal [Possible Regressions] Even if it's something we don't really support please make sure that you can use dash-to-dock without uninstalling ubuntu-dock. [Original Bug] After an update from ubuntu 16.04 to 18.04 the dock is aviable on the lockscreen after user login. I did not configure this knowingly. Also i can start every application which is available on the dock. Settings, virtual box, visualstudio code and so on. After the update to 18.04 i just configure the screen frequency to 144Hz and the night mode on. And attach the dock on bottom. I later undid these customizations back to configuration before, but the dock is stil aviable on lockscreen. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-settings-daemon 3.28.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat May 5 18:30:16 2018 InstallationDate: Installed on 2018-04-08 (27 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: gnome-settings-daemon UpgradeStatus: Upgraded to bionic on 2018-05-01 (3 days ago) --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-08 (27 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell-extension-ubuntu-dock 0.9.1 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-05-01 (4 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1769383/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1790757] Re: Don't sync gnome-user-share 3.28.0-1 from Debian (needs new nautilus)
** Changed in: gnome-user-share (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-user-share in Ubuntu. https://bugs.launchpad.net/bugs/1790757 Title: Don't sync gnome-user-share 3.28.0-1 from Debian (needs new nautilus) Status in gnome-user-share package in Ubuntu: Fix Released Bug description: gnome-user-share 3.28 requires nautilus >= 3.28 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-user-share/+bug/1790757/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1769383] Re: Ubuntu dock/launcher is shown on the lock screen
I don't believe there is a fix yet. Best workaround I've found is to purge the extension and install upstream as shown here https://github.com/micheleg/dash-to- dock/issues/649#issuecomment-424182892 ** Bug watch added: github.com/micheleg/dash-to-dock/issues #649 https://github.com/micheleg/dash-to-dock/issues/649 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1769383 Title: Ubuntu dock/launcher is shown on the lock screen Status in gnome-shell package in Ubuntu: Invalid Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Status in gnome-shell source package in Bionic: Invalid Status in gnome-shell-extension-ubuntu-dock source package in Bionic: In Progress Status in gnome-shell source package in Cosmic: Invalid Status in gnome-shell-extension-ubuntu-dock source package in Cosmic: In Progress Status in gnome-shell source package in Disco: Invalid Status in gnome-shell-extension-ubuntu-dock source package in Disco: Fix Released Bug description: [Impact] When entering the lock-screen mode, gnome-shell disables all the extensions. It can happen that under certain conditions ubuntu-dock re-enables itself, causing the ubuntu-dock to appear in the lock-screen, exposing sensitive information. One possible way to reproduce this is to enable dash-to-dock and ubuntu-dock at the same time. [Test Case] 1. Make sure ubuntu-dock is enabled 2. Enable dash-to-dock too 3. Lock the screen 4. Make sure the dock does not appear on the lock screen 5. Make sure there is no warning is the journal [Possible Regressions] Even if it's something we don't really support please make sure that you can use dash-to-dock without uninstalling ubuntu-dock. [Original Bug] After an update from ubuntu 16.04 to 18.04 the dock is aviable on the lockscreen after user login. I did not configure this knowingly. Also i can start every application which is available on the dock. Settings, virtual box, visualstudio code and so on. After the update to 18.04 i just configure the screen frequency to 144Hz and the night mode on. And attach the dock on bottom. I later undid these customizations back to configuration before, but the dock is stil aviable on lockscreen. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-settings-daemon 3.28.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat May 5 18:30:16 2018 InstallationDate: Installed on 2018-04-08 (27 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: gnome-settings-daemon UpgradeStatus: Upgraded to bionic on 2018-05-01 (3 days ago) --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-08 (27 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell-extension-ubuntu-dock 0.9.1 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-05-01 (4 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1769383/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
I booted **manjaro-kde-18.0-stable-x86_64.iso** nd sounds works (internal speakers) like a charm. Sound details: ``` [manjaro@manjaro ~]$ sudo hwinfo --sound 20: PCI 1f.3: 0403 Audio device [Created at pci.378] Unique ID: nS1_.b28td23g3aB SysFS ID: /devices/pci:00/:00:1f.3 SysFS BusID: :00:1f.3 Hardware Class: sound Model: "Intel Audio device" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0x9d71 SubVendor: pci 0x1043 "ASUSTeK Computer Inc." SubDevice: pci 0x1a00 Revision: 0x21 Driver: "snd_hda_intel" Driver Modules: "snd_hda_intel" Memory Range: 0xef528000-0xef52bfff (rw,non-prefetchable) Memory Range: 0xef50-0xef50 (rw,non-prefetchable) IRQ: 130 (615 events) Module Alias: "pci:v8086d9D71sv1043sd1A00bc04sc03i00" Driver Info #0: Driver Status: snd_hda_intel is active Driver Activation Cmd: "modprobe snd_hda_intel" Driver Info #1: Driver Status: snd_soc_skl is active Driver Activation Cmd: "modprobe snd_soc_skl" Config Status: cfg=new, avail=yes, need=no, active=unknown ``` This ISO included patches for ALSA, Patches for ASUS sound issues was applied in **4.19.8-2** release via this commit > https://gitlab.manjaro.org/packages/core/linux419/commit/ef116a4b40754fa3f08e605c9e30fca35f0d6f03 Naming taken from this: https://gitlab.manjaro.org/packages/core/linux419/commit/082db04a3e3d904e13e1550ae80f553dd1a0cba6 -- 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/1784485 Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Bug description: Internal speaker - not sound at all Cable Headphonse - realy quiet disorted sound Bluetooth headphones - sound works fine On Windows 10 everything works fine. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pmichalski 7964 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Jul 30 22:32:10 2018 InstallationDate: Installed on 2018-07-17 (12 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Wbudowany dźwięk - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm2988 F pulseaudio pmichalski 7964 F pulseaudio Symptom_Jack: Mic, Internal Symptom_Type: No sound at all Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX391UA.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX391UA 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.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook S dmi.product.name: ZenBook S UX391UA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1769383] Re: Ubuntu dock/launcher is shown on the lock screen
Is this fix released for Ubuntu 18.10? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1769383 Title: Ubuntu dock/launcher is shown on the lock screen Status in gnome-shell package in Ubuntu: Invalid Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Status in gnome-shell source package in Bionic: Invalid Status in gnome-shell-extension-ubuntu-dock source package in Bionic: In Progress Status in gnome-shell source package in Cosmic: Invalid Status in gnome-shell-extension-ubuntu-dock source package in Cosmic: In Progress Status in gnome-shell source package in Disco: Invalid Status in gnome-shell-extension-ubuntu-dock source package in Disco: Fix Released Bug description: [Impact] When entering the lock-screen mode, gnome-shell disables all the extensions. It can happen that under certain conditions ubuntu-dock re-enables itself, causing the ubuntu-dock to appear in the lock-screen, exposing sensitive information. One possible way to reproduce this is to enable dash-to-dock and ubuntu-dock at the same time. [Test Case] 1. Make sure ubuntu-dock is enabled 2. Enable dash-to-dock too 3. Lock the screen 4. Make sure the dock does not appear on the lock screen 5. Make sure there is no warning is the journal [Possible Regressions] Even if it's something we don't really support please make sure that you can use dash-to-dock without uninstalling ubuntu-dock. [Original Bug] After an update from ubuntu 16.04 to 18.04 the dock is aviable on the lockscreen after user login. I did not configure this knowingly. Also i can start every application which is available on the dock. Settings, virtual box, visualstudio code and so on. After the update to 18.04 i just configure the screen frequency to 144Hz and the night mode on. And attach the dock on bottom. I later undid these customizations back to configuration before, but the dock is stil aviable on lockscreen. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-settings-daemon 3.28.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat May 5 18:30:16 2018 InstallationDate: Installed on 2018-04-08 (27 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: gnome-settings-daemon UpgradeStatus: Upgraded to bionic on 2018-05-01 (3 days ago) --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-08 (27 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell-extension-ubuntu-dock 0.9.1 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-05-01 (4 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1769383/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1808796] Re: gnome-settings-daemon FTBFS in cosmic-proposed due to circular relationship involving mutter
Hello Iain, or anyone else affected,
Accepted mutter into cosmic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mutter/3.30.2-1~ubuntu18.10.2 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-cosmic to verification-done-cosmic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-cosmic. In either case, without details of
your testing we will not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
** Changed in: mutter (Ubuntu Cosmic)
Status: In Progress => Fix Committed
** Tags added: verification-needed verification-needed-cosmic
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1808796
Title:
gnome-settings-daemon FTBFS in cosmic-proposed due to circular
relationship involving mutter
Status in mutter package in Ubuntu:
Fix Released
Status in mutter source package in Cosmic:
Fix Committed
Bug description:
[ Description ]
Currently gnome-settings-daemon can't be built in cosmic-proposed for
arm64 and armhf:
The following packages have unmet dependencies:
sbuild-build-depends-gnome-settings-daemon-dummy : Depends: mutter (>=
3.27.90) but it is not going to be installed
analysing the situation with chdist shows:
The following packages have unmet dependencies.
mutter : Depends: gnome-settings-daemon but it is not going to be installed
and then diving further:
The following packages have unmet dependencies.
gnome-settings-daemon : Depends: gnome-settings-daemon-schemas (=
3.30.1.2-1ubuntu2) but 3.30.1.2-1ubuntu3 is to be installed
What has happened is that gnome-settings-daemon indirectly ends up
Build-Depending on gnome-settings-daemon again:
src:g-s-d - (BD) -> mutter - (D) -> g-s-d
gnome-settings-daemon has "Depends: gnome-settings-daemon-schemas (=
${source:Version})". This in itself is correct, but when the arch:all
gnome-settings-daemon-schemas is published before an arch-only build
is picked up, we have skew that results in this failure. g-s-d-schemas
3.30.1.2-1ubuntu3 is available, but g-s-d 3.30.1.2-1ubuntu2, the
strict dependency means it is uninstallable.
Presumably we'd gotten lucky up until now and never had a newer
g-s-d-schemas published before all other arches at least started
building.
[ Fix ]
Cut the arch:any part of the circular dependency. We make mutter
Depend on gnome-settings-daemon-schemas instead, since it only needs
the schemas and not running daemons. We still have a circular BD/D
chain from g-s-d to itself, but now it looks like:
src:g-s-d - (BD) -> mutter - (D) -> g-s-d-schemas
...importantly there are no strict version requirements any more, so
this kind of skew isn't a problem. If mutter ever changes to have
"Depends: gnome-settings-daemon-schemas (>= some-version)", this
should also work - since the arch:all gnome-settings-daemon-schemas
will be installable everywhere.
[ QA ]
I tested this in a bileto silo and it worked:
https://launchpad.net/~ci-train-ppa-
service/+archive/ubuntu/3567/+packages
Once the fixed mutter is published, we should be able to retry the
g-s-d builds.
[ Regression potential ]
mutter will no longer Depend on gnome-settings-daemon itself (the
daemons). This might expose missing g-s-d dependencies from other
packages. These could only be out-of-archive packages though:
laney@raleigh> reverse-depends -r cosmic mutter
Reverse-Depends
===
* gnome-shell
* vanilla-gnome-desktop
and both of these depend on gnome-settings-daemon already.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1808796/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1808796] Re: Circular relationship between gnome-settings-daemon and mutter
This was fixed in debian by introducing a g-s-d-common package. That's
synced to disco, so disco is good too.
** Description changed:
- Currently g-s-d can't be built in cosmic-proposed.
+ [ Description ]
+
+ Currently gnome-settings-daemon can't be built in cosmic-proposed for
+ arm64 and armhf:
+
+ The following packages have unmet dependencies:
+ sbuild-build-depends-gnome-settings-daemon-dummy : Depends: mutter (>=
3.27.90) but it is not going to be installed
+
+ analysing the situation with chdist shows:
+
+ The following packages have unmet dependencies.
+ mutter : Depends: gnome-settings-daemon but it is not going to be installed
+
+ and then diving further:
+
+ The following packages have unmet dependencies.
+ gnome-settings-daemon : Depends: gnome-settings-daemon-schemas (=
3.30.1.2-1ubuntu2) but 3.30.1.2-1ubuntu3 is to be installed
+
+ What has happened is that gnome-settings-daemon indirectly ends up
+ Build-Depending on gnome-settings-daemon again:
+
+ src:g-s-d - (BD) -> mutter - (D) -> g-s-d
+
+ gnome-settings-daemon has "Depends: gnome-settings-daemon-schemas (=
+ ${source:Version})". This in itself is correct, but when the arch:all
+ gnome-settings-daemon-schemas is published before an arch-only build is
+ picked up, we have skew that results in this failure. g-s-d-schemas
+ 3.30.1.2-1ubuntu3 is available, but g-s-d 3.30.1.2-1ubuntu2, the strict
+ dependency means it is uninstallable.
+
+ Presumably we'd gotten lucky up until now and never had a newer
+ g-s-d-schemas published before all other arches at least started
+ building.
+
+ [ Fix ]
+
+ Cut the arch:any part of the circular dependency. We make mutter Depend
+ on gnome-settings-daemon-schemas instead, since it only needs the
+ schemas and not running daemons. We still have a circular BD/D chain
+ from g-s-d to itself, but now it looks like:
+
+ src:g-s-d - (BD) -> mutter - (D) -> g-s-d-schemas
+
+ ...importantly there are no strict version requirements any more, so
+ this kind of skew isn't a problem. If mutter ever changes to have
+ "Depends: gnome-settings-daemon-schemas (>= some-version)", this should
+ also work - since the arch:all gnome-settings-daemon-schemas will be
+ installable everywhere.
+
+ [ QA ]
+
+ I tested this in a bileto silo and it worked:
+
+ https://launchpad.net/~ci-train-ppa-
+ service/+archive/ubuntu/3567/+packages
+
+ Once the fixed mutter is published, we should be able to retry the g-s-d
+ builds.
+
+ [ Regression potential ]
+
+ mutter will no longer Depend on gnome-settings-daemon itself (the
+ daemons). This might expose missing g-s-d dependencies from other
+ packages. These could only be out-of-archive packages though:
+
+ laney@raleigh> reverse-depends -r cosmic mutter
+ Reverse-Depends
+ ===
+ * gnome-shell
+ * vanilla-gnome-desktop
+
+ and both of these depend on gnome-settings-daemon already.
** Changed in: mutter (Ubuntu)
Status: New => Fix Released
** Also affects: mutter (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Changed in: mutter (Ubuntu Cosmic)
Status: New => Incomplete
** Changed in: mutter (Ubuntu Cosmic)
Status: Incomplete => In Progress
** Changed in: mutter (Ubuntu Cosmic)
Assignee: (unassigned) => Iain Lane (laney)
** Summary changed:
- Circular relationship between gnome-settings-daemon and mutter
+ gnome-settings-daemon FTBFS in cosmic-proposed due to circular relationship
involving mutter
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1808796
Title:
gnome-settings-daemon FTBFS in cosmic-proposed due to circular
relationship involving mutter
Status in mutter package in Ubuntu:
Fix Released
Status in mutter source package in Cosmic:
In Progress
Bug description:
[ Description ]
Currently gnome-settings-daemon can't be built in cosmic-proposed for
arm64 and armhf:
The following packages have unmet dependencies:
sbuild-build-depends-gnome-settings-daemon-dummy : Depends: mutter (>=
3.27.90) but it is not going to be installed
analysing the situation with chdist shows:
The following packages have unmet dependencies.
mutter : Depends: gnome-settings-daemon but it is not going to be installed
and then diving further:
The following packages have unmet dependencies.
gnome-settings-daemon : Depends: gnome-settings-daemon-schemas (=
3.30.1.2-1ubuntu2) but 3.30.1.2-1ubuntu3 is to be installed
What has happened is that gnome-settings-daemon indirectly ends up
Build-Depending on gnome-settings-daemon again:
src:g-s-d - (BD) -> mutter - (D) -> g-s-d
gnome-settings-daemon has "Depends: gnome-settings-daemon-schemas (=
${source:Version})". This in itself is correct, but when the arch:all
gnome-settings-daemon-schemas is published before an arch-only build
is picked up, we have skew that results in this failure. g-s-d-schemas
3.30
