[Desktop-packages] [Bug 1846930] Re: [HDA-Intel - HD-Audio Generic, playback] No sound at all nor audio record at all too
hh@hh-desktop:~$ uname -a Linux hh-desktop 5.4.0-050400rc2-generic #201910062030 SMP Mon Oct 7 00:33:58 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux hh@hh-desktop:~$ before plugging in headset https://pastebin.com/PGhQD60T after https://pastebin.com/TsqEtuJG -- 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/1846930 Title: [HDA-Intel - HD-Audio Generic, playback] No sound at all nor audio record at all too Status in alsa-driver package in Ubuntu: New Bug description: Any progress? Cannot hear anything nor record anything out my asrock fm2a75m-dgs ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-65.74-generic 4.15.18 Uname: Linux 4.15.0-65-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: hh 1267 F pulseaudio /dev/snd/controlC0: hh 1267 F pulseaudio CurrentDesktop: XFCE Date: Sun Oct 6 09:27:53 2019 InstallationDate: Installed on 2019-03-31 (188 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: LANGUAGE=it PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: GP107GL High Definition Audio Controller - HDA NVidia Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: hh 1267 F pulseaudio /dev/snd/controlC0: hh 1267 F pulseaudio Symptom_Type: No sound at all Title: [HDA-Intel - HD-Audio Generic, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.70 dmi.board.name: FM2A75M-DGS dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.70:bd12/01/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A75M-DGS:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-04-25T18:19:18.090642 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1846930/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1847713] [NEW] Asus ZenBook 13 UX331UAL touchpad feels sloppy and slow to change direction
Public bug reported: Asus ZenBook 13 UX331UAL touchpad feels sloppy and slow to change direction. For comparison I then installed the old synaptics Xorg driver and disabled hysteresis using 'synclient'. It felt much better. So it seems libinput's hysteresis radius is too big. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: libinput10 1.14.1-2 ProcVersionSignature: Ubuntu 5.3.0-17.18-generic 5.3.1 Uname: Linux 5.3.0-17-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Fri Oct 11 10:50:40 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. UHD Graphics 620 [1043:1cd0] InstallationDate: Installed on 2019-09-06 (34 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190830) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 13d3:5a09 IMC Networks USB2.0 VGA UVC WebCam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. ZenBook 13 UX331UAL ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-17-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: libinput UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/03/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX331UAL.307 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX331UAL 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.:bvrUX331UAL.307:bd09/03/2018:svnASUSTeKCOMPUTERINC.:pnZenBook13UX331UAL:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX331UAL:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook 13 UX331UAL dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.0-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: libinput Importance: Unknown Status: New ** Affects: libinput (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan ubuntu ** Bug watch added: gitlab.freedesktop.org/libinput/libinput/issues #373 https://gitlab.freedesktop.org/libinput/libinput/issues/373 ** Also affects: libinput via https://gitlab.freedesktop.org/libinput/libinput/issues/373 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libinput in Ubuntu. https://bugs.launchpad.net/bugs/1847713 Title: Asus ZenBook 13 UX331UAL touchpad feels sloppy and slow to change direction Status in libinput: New Status in libinput package in Ubuntu: New Bug description: Asus ZenBook 13 UX331UAL touchpad feels sloppy and slow to change direction. For comparison I then installed the old synaptics Xorg driver and disabled hysteresis using 'synclient'. It felt much better. So it seems libinput's hysteresis radius is too big. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: libinput10 1.14.1-2 ProcVersionSignature: Ubuntu 5.3.0-17.18-generic 5.3.1 Uname: Linux 5.3.0-17-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Fri Oct 11 10:50:40 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. UHD Graphics 620 [1043:1cd0] InstallationDate: Installed on 2019-09-06 (34 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190830) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 13d3:5a09 IMC Networks USB2.0 VGA UVC WebCam Bus 001 Device
[Desktop-packages] [Bug 1847712] Re: Desktop icons vanishing when in Activities Overview is jarring and looks ugly
** Changed in: gnome-shell-extension-desktop-icons Status: Unknown => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1847712 Title: Desktop icons vanishing when in Activities Overview is jarring and looks ugly Status in gnome-shell-extension-desktop-icons: New Status in Ubuntu UX: New Status in gnome-shell-extension-desktop-icons package in Ubuntu: New Bug description: Desktop icons vanishing and reappearing when in Activities Overview is jarring and looks ugly. Suggestions: * Don't hide them in AO, because they will be well shaded anyway; or * Fade them out and in smoothly. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell-extension-desktop-icons 19.01.4-1 ProcVersionSignature: Ubuntu 5.3.0-17.18-generic 5.3.1 Uname: Linux 5.3.0-17-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 Date: Fri Oct 11 14:24:42 2019 InstallationDate: Installed on 2019-05-02 (162 days ago) InstallationMedia: Ubuntu 19.10 "Eoan EANIMAL" - Alpha amd64 (20190501) PackageArchitecture: all SourcePackage: gnome-shell-extension-desktop-icons UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1847712/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1844739] Re: Latest Firefox update freezing my system
** Attachment removed: "journal.txt" https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1844739/+attachment/5296407/+files/journal.txt -- 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/1844739 Title: Latest Firefox update freezing my system Status in firefox package in Ubuntu: Incomplete Bug description: The latest updates of firefox renders my machine useless. I'm sending it as is hopefully before it freezes completely. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: firefox 69.0+build2-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-62.69-generic 4.15.18 Uname: Linux 4.15.0-62-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.20.9-0ubuntu7.7 Architecture: i386 BuildID: 20190828152935 CurrentDesktop: ubuntu:GNOME Date: Fri Sep 20 01:22:17 2019 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:997 DefaultProfileThemes: extensions.sqlite corrupt or missing InstallationDate: Installed on 2018-05-01 (506 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release i386 (20170412) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US SHELL=/bin/bash Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=69.0/20190828152935 (In use) SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1844739/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1847712] Re: Desktop icons vanishing when in Activities Overview is jarring and looks ugly
** Changed in: gnome-shell-extension-desktop-icons (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-shell-extension-desktop-icons (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1847712 Title: Desktop icons vanishing when in Activities Overview is jarring and looks ugly Status in gnome-shell-extension-desktop-icons: New Status in Ubuntu UX: New Status in gnome-shell-extension-desktop-icons package in Ubuntu: Triaged Bug description: Desktop icons vanishing and reappearing when in Activities Overview is jarring and looks ugly. Suggestions: * Don't hide them in AO, because they will be well shaded anyway; or * Fade them out and in smoothly. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell-extension-desktop-icons 19.01.4-1 ProcVersionSignature: Ubuntu 5.3.0-17.18-generic 5.3.1 Uname: Linux 5.3.0-17-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 Date: Fri Oct 11 14:24:42 2019 InstallationDate: Installed on 2019-05-02 (162 days ago) InstallationMedia: Ubuntu 19.10 "Eoan EANIMAL" - Alpha amd64 (20190501) PackageArchitecture: all SourcePackage: gnome-shell-extension-desktop-icons UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1847712/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1847102] Re: Dragging icons around the dock only fully works once. After that they stick to the mouse pointer.
** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided => High -- 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/1847102 Title: Dragging icons around the dock only fully works once. After that they stick to the mouse pointer. Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: In Progress Bug description: The first time it seemed to work fine, then I stopped being able to drop the icon and had to hit escape. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell-extension-ubuntu-dock 66ubuntu19.10.2 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 7 15:29:20 2019 InstallationDate: Installed on 2019-09-27 (10 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926.1) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1847102/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1844422] Re: WPA3-SAE support
The n-m patch has been backported and gnome-shell updated to 3.34.1, do we need another patch? -- 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/1844422 Title: WPA3-SAE support Status in gnome-shell package in Ubuntu: Fix Released Status in network-manager package in Ubuntu: Fix Committed Bug description: After some user feedback WPA3 support for NetworkManager has been finalized upstream: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/e1608030c6614d8dfd86122e9df81fdaad9453c9 https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/84a86ce55f1e70cb32217d2c74242ff848db8cd7 https://gitlab.freedesktop.org/NetworkManager/NetworkManager/merge_requests/276/diffs?commit_id=8d4497088fff562773b9c05260e810833bfc9c85 At this time NetworkManager will not associate with Wifi-networks using WPA3. Tested using Ubuntu Ubuntu Eoan Ermine [development branch] with NetworkManager 1.20.2-1ubuntu1 and WPA_Supplicant 2:2.9-1ubuntu1. It would be great if the aforementioned commits where backported to Eoan before release, so that Eoan based systems will associate with WiFi-networks using WPA3. == Update 09-10-2019: So it has come to my attention that NetworkManager needs one additional commit backported from upstream to make WPA3-SAE work: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/e36c297fd8c6b1b57cd120739cc5ee8eab57aa08 Without this latest commit connecting to WPA3-personal networks will still fail because of a lack of 802.11w support in the network-manager settings. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1844422/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1847597] Re: gnome-control-center cannot access google account
Yes of course. I will attach my screenshot (which is in Italian) with the English version. My gnome-control-center version is: ii gnome-control-center 1:3.18.2-1ubuntu6.1 amd64utilities to configure the GNOME desktop ii gnome-control-center-data 1:3.18.2-1ubuntu6.1 all configuration applets for GNOME - data files Thanks in advance. ** Attachment added: "merge_from_ofoct.jpg" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1847597/+attachment/5296473/+files/merge_from_ofoct.jpg -- 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/1847597 Title: gnome-control-center cannot access google account Status in gnome-control-center package in Ubuntu: Incomplete Bug description: Good morning, If I run "gnome-control-center online-accounts" from the terminal and trying to add a Google account, I get this error: "Sign in with Google is temporarily disabled for this app. This app has not been verified yet by Google in order to use Google sign in". On the web, Google suggests to contact you, so here I am. Can you fix please? I would use my drive folders on my ubuntu 16.04. Thanks in advance. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1847597/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1846930] Re: [HDA-Intel - HD-Audio Generic, playback] No sound at all nor audio record at all too
also have the problem that alsamixer cannot store correctly modules enabled and volume settings after reboot -- 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/1846930 Title: [HDA-Intel - HD-Audio Generic, playback] No sound at all nor audio record at all too Status in alsa-driver package in Ubuntu: New Bug description: Any progress? Cannot hear anything nor record anything out my asrock fm2a75m-dgs ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-65.74-generic 4.15.18 Uname: Linux 4.15.0-65-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: hh 1267 F pulseaudio /dev/snd/controlC0: hh 1267 F pulseaudio CurrentDesktop: XFCE Date: Sun Oct 6 09:27:53 2019 InstallationDate: Installed on 2019-03-31 (188 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: LANGUAGE=it PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: GP107GL High Definition Audio Controller - HDA NVidia Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: hh 1267 F pulseaudio /dev/snd/controlC0: hh 1267 F pulseaudio Symptom_Type: No sound at all Title: [HDA-Intel - HD-Audio Generic, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.70 dmi.board.name: FM2A75M-DGS dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.70:bd12/01/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A75M-DGS:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-04-25T18:19:18.090642 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1846930/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1846930] Re: [HDA-Intel - HD-Audio Generic, playback] No sound at all nor audio record at all too
According to #17, still can't detect the plugging event on headphone jack. So please open a bug on bugzilla for mainline kernel. -- 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/1846930 Title: [HDA-Intel - HD-Audio Generic, playback] No sound at all nor audio record at all too Status in alsa-driver package in Ubuntu: New Bug description: Any progress? Cannot hear anything nor record anything out my asrock fm2a75m-dgs ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-65.74-generic 4.15.18 Uname: Linux 4.15.0-65-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: hh 1267 F pulseaudio /dev/snd/controlC0: hh 1267 F pulseaudio CurrentDesktop: XFCE Date: Sun Oct 6 09:27:53 2019 InstallationDate: Installed on 2019-03-31 (188 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: LANGUAGE=it PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: GP107GL High Definition Audio Controller - HDA NVidia Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: hh 1267 F pulseaudio /dev/snd/controlC0: hh 1267 F pulseaudio Symptom_Type: No sound at all Title: [HDA-Intel - HD-Audio Generic, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.70 dmi.board.name: FM2A75M-DGS dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.70:bd12/01/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A75M-DGS:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-04-25T18:19:18.090642 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1846930/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1847597] Re: gnome-control-center cannot access google account
thank you for the screenshot, it's not clear it's a control center UI though. How do you start it? Could you maybe do xprop on the application and copy the log there? -- 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/1847597 Title: gnome-control-center cannot access google account Status in gnome-control-center package in Ubuntu: Incomplete Bug description: Good morning, If I run "gnome-control-center online-accounts" from the terminal and trying to add a Google account, I get this error: "Sign in with Google is temporarily disabled for this app. This app has not been verified yet by Google in order to use Google sign in". On the web, Google suggests to contact you, so here I am. Can you fix please? I would use my drive folders on my ubuntu 16.04. Thanks in advance. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1847597/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1847603] Re: After upgrading Ubuntu 19.10 second screen not detected
I suppose it is related to the missing extra modules -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1847603 Title: After upgrading Ubuntu 19.10 second screen not detected Status in lightdm package in Ubuntu: Invalid Bug description: After upgrading Ubuntu 19.10 second screen not detected ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: lightdm 1.30.0-0ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-13.14+lp1845454v201909260743-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Oct 10 14:56:33 2019 LightdmConfig: [Seat:*] #autologin-guest=false #autologin-user=caiofior #autologin-user-timeout=0 SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1847603/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1847603] Re: After upgrading Ubuntu 19.10 second screen not detected
Missing linux kernel extra modules ** Changed in: lightdm (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1847603 Title: After upgrading Ubuntu 19.10 second screen not detected Status in lightdm package in Ubuntu: Invalid Bug description: After upgrading Ubuntu 19.10 second screen not detected ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: lightdm 1.30.0-0ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-13.14+lp1845454v201909260743-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Oct 10 14:56:33 2019 LightdmConfig: [Seat:*] #autologin-guest=false #autologin-user=caiofior #autologin-user-timeout=0 SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1847603/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1800260] Re: [snap] with CSD and Yaru, background color of the header bar is incorrect
As pointed out by Nicolás in https://forum.snapcraft.io/t/call-for- testing-chromium-browser-deb-to-snap-transition/11772/14, the gtk- common-themes snap in the candidate channel appears to fix the problem. I am now trying to bisect what change fixed the problem, and I will talk to the maintainers to have it promoted to stable. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1800260 Title: [snap] with CSD and Yaru, background color of the header bar is incorrect Status in chromium-browser package in Ubuntu: Confirmed Bug description: Description: Ubuntu 18.04.1 LTS Release: 18.04 Channel:Stable Version:70.0.3538.67 Updated:10/19/2018 License:Free Developer: Canonical Source: Snap Store Installed Size: 148.2 MB Settings -> Appearance: "Use system title bar and borders" was turned off. Close, minimize, maximize buttons became oval (more of stretched down) instead of circle. Turned back it on, buttons went back to normal shape (circle). It's a repeatable action. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1800260/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1847729] [NEW] Memory leak of gnome-shell after sleep mode
Public bug reported: Whenever I put my laptop to sleep mode, the memory used by the gnome-shell process (usr/bin/gnome-shell) increase! each time something around 50 to 100MB. So after 10 to 15 times of sleeping and waking up, it takes more than 1GB of RAM and the whole system becomes laggy! I'm using Ubuntu 18.04.03 LTS with GNOME 3.28.2. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.4-0ubuntu18.04.2 ProcVersionSignature: Ubuntu 5.0.0-31.33~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-31-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 11 11:26:29 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-02-15 (237 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic third-party-packages -- 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/1847729 Title: Memory leak of gnome-shell after sleep mode Status in gnome-shell package in Ubuntu: New Bug description: Whenever I put my laptop to sleep mode, the memory used by the gnome-shell process (usr/bin/gnome-shell) increase! each time something around 50 to 100MB. So after 10 to 15 times of sleeping and waking up, it takes more than 1GB of RAM and the whole system becomes laggy! I'm using Ubuntu 18.04.03 LTS with GNOME 3.28.2. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.4-0ubuntu18.04.2 ProcVersionSignature: Ubuntu 5.0.0-31.33~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-31-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 11 11:26:29 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-02-15 (237 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) 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/1847729/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1800260] Re: [snap] with CSD and Yaru, background color of the header bar is incorrect
I am not sure exactly which commit fixed the problem, but I suspect it's an update in Yaru itself. Possibly one of those: https://github.com/ubuntu/yaru/commit/4a6484deaa19c284344923efb1ccdc1998325aef https://github.com/ubuntu/yaru/commit/a0ff34f379d2b2d4673f4910970fdb02756b03b3 -- 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/1800260 Title: [snap] with CSD and Yaru, background color of the header bar is incorrect Status in chromium-browser package in Ubuntu: Confirmed Bug description: Description: Ubuntu 18.04.1 LTS Release: 18.04 Channel:Stable Version:70.0.3538.67 Updated:10/19/2018 License:Free Developer: Canonical Source: Snap Store Installed Size: 148.2 MB Settings -> Appearance: "Use system title bar and borders" was turned off. Close, minimize, maximize buttons became oval (more of stretched down) instead of circle. Turned back it on, buttons went back to normal shape (circle). It's a repeatable action. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1800260/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1847735] [NEW] thunderbird can't send anymore (when enigmail is enabled)
Public bug reported: Hi, after this morning's ubuntu 18.04 package updates my thunderbird can't send mails anymore, just nothing happens when pushing the send button. Reason: I have installed the ubuntu enigmail package as well. When disabling enigmail in thunderbird's add-ons manager menu, sending works as normal, but, of course, without pgp encryption. So the thunderbird and enigmail packages are currently incompatible. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: thunderbird 1:60.9.0+build1-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-65.74-generic 4.15.18 Uname: Linux 4.15.0-65-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair AddonCompatCheckDisabled: False ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hadmut 5762 F pulseaudio BuildID: 20191007090452 Channel: Unavailable CurrentDesktop: XFCE Date: Fri Oct 11 11:28:43 2019 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # ifupdown has been replaced by netplan(5) on this system. See # /etc/netplan for current configuration. # To re-enable ifupdown on this system, you can run: #sudo apt install ifupdown IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2018-06-09 (488 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Locales: extensions.sqlite corrupt or missing MostRecentCrashID: bp-491d26ca-c698-4761-9b14-5282d0191011 PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=60.9.0/20191007090452 (In use) RunningIncompatibleAddons: False SourcePackage: thunderbird Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/12/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: H61TIW08.111 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H61H2-TI2 dmi.board.vendor: Medion dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Medion dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrH61TIW08.111:bd10/12/2012:svnMedion:pnG24:pvr1.0:rvnMedion:rnH61H2-TI2:rvr1.0:cvnMedion:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: G24 dmi.product.version: 1.0 dmi.sys.vendor: Medion ** Affects: thunderbird (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1847735 Title: thunderbird can't send anymore (when enigmail is enabled) Status in thunderbird package in Ubuntu: New Bug description: Hi, after this morning's ubuntu 18.04 package updates my thunderbird can't send mails anymore, just nothing happens when pushing the send button. Reason: I have installed the ubuntu enigmail package as well. When disabling enigmail in thunderbird's add-ons manager menu, sending works as normal, but, of course, without pgp encryption. So the thunderbird and enigmail packages are currently incompatible. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: thunderbird 1:60.9.0+build1-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-65.74-generic 4.15.18 Uname: Linux 4.15.0-65-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair AddonCompatCheckDisabled: False ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hadmut 5762 F pulseaudio BuildID: 20191007090452 Channel: Unavailable CurrentDesktop: XFCE Date: Fri Oct 11 11:28:43 2019 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # ifupdown has been replaced by netplan(5) on this system. See # /etc/netplan for current configuration. # To re-enable ifupdown on this system, you can run: #sudo apt install ifupdown IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2018-06-09 (488 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Locales: extensions.sqlite corrupt or missing MostRecentCrashID: bp-491d26ca-c698-4761-9b14-5282d0191011 PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=60.9.0/20191007090452 (In use) RunningIncompatibleAddons: False SourcePackage: thunderbird Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/12/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: H61TIW08.111 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H61H2-TI2
[Desktop-packages] [Bug 1847729] Re: Memory leak of gnome-shell after sleep mode
We find a large number of bugs are caused by shell extensions so please start by uninstalling these ones you have installed: 'system_moni...@bghome.gmail.com' 'weatherinthecl...@jasonlg1979.github.io' 'move_cl...@rmy.pobox.com' 'alternate-...@gnome-shell-extensions.gcampax.github.com' 'arc-m...@linxgem33.com' 'dash-to-pa...@jderose9.github.com' 'places-m...@gnome-shell-extensions.gcampax.github.com' 'system-moni...@paradoxxx.zero.gmail.com' 'workspace-indica...@gnome-shell-extensions.gcampax.github.com' 'user-th...@gnome-shell-extensions.gcampax.github.com']" Be sure to uninstall them and don't just disable them. Then reboot and retest to see if the bug persists. ** 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/1847729 Title: Memory leak of gnome-shell after sleep mode Status in gnome-shell package in Ubuntu: Incomplete Bug description: Whenever I put my laptop to sleep mode, the memory used by the gnome-shell process (usr/bin/gnome-shell) increase! each time something around 50 to 100MB. So after 10 to 15 times of sleeping and waking up, it takes more than 1GB of RAM and the whole system becomes laggy! I'm using Ubuntu 18.04.03 LTS with GNOME 3.28.2. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.4-0ubuntu18.04.2 ProcVersionSignature: Ubuntu 5.0.0-31.33~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-31-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 11 11:26:29 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-02-15 (237 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) 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/1847729/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1847736] [NEW] examples.desktop file in home dir is opening in gedit
Public bug reported: The "examples.desktop" file in the home directory should open /usr/share /example-content but instead it opens the .desktop file in gedit. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: rls-ee-incoming ** Tags added: rls-ee-incoming ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1847736 Title: examples.desktop file in home dir is opening in gedit Status in gnome-shell package in Ubuntu: Confirmed Bug description: The "examples.desktop" file in the home directory should open /usr/share/example-content but instead it opens the .desktop file in gedit. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1847736/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1846319] Re: Gnome battery indicator turns red at 50%
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-power-manager (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/1846319 Title: Gnome battery indicator turns red at 50% Status in gnome-power-manager package in Ubuntu: Confirmed Bug description: I am running Ubuntu Eoan Beta on a Dell XPS13 9630. When running on battery, the Gnome power indicator in the top bar turns red when the charge falls to 50% or lower. This seems a bit early as I still have hours worth of battery left. Should this not happen around 10-15% instead? This is reproducible 100% of the time. Thanks Nick ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-power-manager 3.32.0-1 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Oct 2 10:54:20 2019 InstallationDate: Installed on 2019-09-23 (8 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: gnome-power-manager UpgradeStatus: Upgraded to eoan on 2019-09-27 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1846319/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1846319] Re: Gnome battery indicator turns red at 50%
Same issue. Dell XPS 15 9560 here. Fresh install of Eoan from the Beta ISO a few days ago (and kept up to date with the repos). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/1846319 Title: Gnome battery indicator turns red at 50% Status in gnome-power-manager package in Ubuntu: Confirmed Bug description: I am running Ubuntu Eoan Beta on a Dell XPS13 9630. When running on battery, the Gnome power indicator in the top bar turns red when the charge falls to 50% or lower. This seems a bit early as I still have hours worth of battery left. Should this not happen around 10-15% instead? This is reproducible 100% of the time. Thanks Nick ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-power-manager 3.32.0-1 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Oct 2 10:54:20 2019 InstallationDate: Installed on 2019-09-23 (8 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: gnome-power-manager UpgradeStatus: Upgraded to eoan on 2019-09-27 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1846319/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1847736] Re: examples.desktop file in home dir is opening in gedit
My interpretation of that upstream bug is that .desktop files of type=link are not supported any more. -- 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/1847736 Title: examples.desktop file in home dir is opening in gedit Status in gnome-shell package in Ubuntu: Confirmed Bug description: The "examples.desktop" file in the home directory should open /usr/share/example-content but instead it opens the .desktop file in gedit. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1847736/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1847736] Re: examples.desktop file in home dir is opening in gedit
Possibly related: https://gitlab.gnome.org/GNOME/nautilus/issues/448 ** Bug watch added: gitlab.gnome.org/GNOME/nautilus/issues #448 https://gitlab.gnome.org/GNOME/nautilus/issues/448 -- 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/1847736 Title: examples.desktop file in home dir is opening in gedit Status in gnome-shell package in Ubuntu: Confirmed Bug description: The "examples.desktop" file in the home directory should open /usr/share/example-content but instead it opens the .desktop file in gedit. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1847736/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1847729] Re: Memory leak of gnome-shell after sleep mode
The problem was with 'ARC menu' shell extension. As you said just disabling is not enough and I do need to uninstall it. Thank you. -- 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/1847729 Title: Memory leak of gnome-shell after sleep mode Status in gnome-shell package in Ubuntu: Incomplete Bug description: Whenever I put my laptop to sleep mode, the memory used by the gnome-shell process (usr/bin/gnome-shell) increase! each time something around 50 to 100MB. So after 10 to 15 times of sleeping and waking up, it takes more than 1GB of RAM and the whole system becomes laggy! I'm using Ubuntu 18.04.03 LTS with GNOME 3.28.2. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.4-0ubuntu18.04.2 ProcVersionSignature: Ubuntu 5.0.0-31.33~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-31-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 11 11:26:29 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-02-15 (237 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) 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/1847729/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1847738] [NEW] Empty item in folder context menu
Public bug reported: Installed 19.10 from a daily image today (also issue on my current laptop which was upgraded from 19.04). Steps to reproduce Open nautilus Right click a file (example.desktop for example) Note the context menu looks okay Right click a folder (such as Downloads) Note the context menu has a blank entry at the bottom, beneath "Properties" Expected No blank line ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: nautilus 1:3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-17.18-generic 5.3.1 Uname: Linux 5.3.0-17-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 11 11:01:25 2019 GsettingsChanges: b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" InstallationDate: Installed on 2019-10-11 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20191011) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan ** Attachment added: "Screenshot from 2019-10-11 11-01-55.png" https://bugs.launchpad.net/bugs/1847738/+attachment/5296545/+files/Screenshot%20from%202019-10-11%2011-01-55.png -- 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/1847738 Title: Empty item in folder context menu Status in nautilus package in Ubuntu: New Bug description: Installed 19.10 from a daily image today (also issue on my current laptop which was upgraded from 19.04). Steps to reproduce Open nautilus Right click a file (example.desktop for example) Note the context menu looks okay Right click a folder (such as Downloads) Note the context menu has a blank entry at the bottom, beneath "Properties" Expected No blank line ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: nautilus 1:3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-17.18-generic 5.3.1 Uname: Linux 5.3.0-17-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 11 11:01:25 2019 GsettingsChanges: b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" InstallationDate: Installed on 2019-10-11 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20191011) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1847738/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1847740] [NEW] Auto-hide dock causes clock/notification to move
Public bug reported: When disabling / enabling hiding of the dock - or indeed changing the width of the dock - in system settings - the clock / notification area moves. These feels wrong. The clock is not related to the dock size, and should not move with it. The clock should be in the centre of the display, not the centre of the usable area of the desktop I believe. Steps to reproduce Open system settings Select dock change the toggle to auto-hide the dock Observe the clock move with the toggle Expected behaviour Clock/notification are is locked to the middle of the screen. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-17.18-generic 5.3.1 Uname: Linux 5.3.0-17-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 11 11:11:44 2019 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.desktop.app-folders' b'folder-children' b"['Utilities', 'Sundry', 'YaST']" b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'gb')]" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.notifications' b'application-children' b"['org-gnome-screenshot', 'update-manager']" b'org.gnome.desktop.privacy' b'report-technical-problems' b'true' InstallationDate: Installed on 2019-10-11 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20191011) RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan ** Attachment added: "Screenshot from 2019-10-11 11-11-16.png" https://bugs.launchpad.net/bugs/1847740/+attachment/5296549/+files/Screenshot%20from%202019-10-11%2011-11-16.png -- 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/1847740 Title: Auto-hide dock causes clock/notification to move Status in gnome-shell package in Ubuntu: New Bug description: When disabling / enabling hiding of the dock - or indeed changing the width of the dock - in system settings - the clock / notification area moves. These feels wrong. The clock is not related to the dock size, and should not move with it. The clock should be in the centre of the display, not the centre of the usable area of the desktop I believe. Steps to reproduce Open system settings Select dock change the toggle to auto-hide the dock Observe the clock move with the toggle Expected behaviour Clock/notification are is locked to the middle of the screen. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-17.18-generic 5.3.1 Uname: Linux 5.3.0-17-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 11 11:11:44 2019 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.desktop.app-folders' b'folder-children' b"['Utilities', 'Sundry', 'YaST']" b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'gb')]" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.notifications' b'application-children' b"['org-gnome-screenshot', 'update-manager']" b'org.gnome.desktop.privacy' b'report-technical-problems' b'true' InstallationDate: Installed on 2019-10-11 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20191011) RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1 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/1847740/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1847740] Re: Auto-hide dock causes clock/notification to move
** Attachment added: "Screenshot from 2019-10-11 11-11-14.png" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1847740/+attachment/5296554/+files/Screenshot%20from%202019-10-11%2011-11-14.png -- 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/1847740 Title: Auto-hide dock causes clock/notification to move Status in gnome-shell package in Ubuntu: New Bug description: When disabling / enabling hiding of the dock - or indeed changing the width of the dock - in system settings - the clock / notification area moves. These feels wrong. The clock is not related to the dock size, and should not move with it. The clock should be in the centre of the display, not the centre of the usable area of the desktop I believe. Steps to reproduce Open system settings Select dock change the toggle to auto-hide the dock Observe the clock move with the toggle Expected behaviour Clock/notification are is locked to the middle of the screen. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-17.18-generic 5.3.1 Uname: Linux 5.3.0-17-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 11 11:11:44 2019 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.desktop.app-folders' b'folder-children' b"['Utilities', 'Sundry', 'YaST']" b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'gb')]" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.notifications' b'application-children' b"['org-gnome-screenshot', 'update-manager']" b'org.gnome.desktop.privacy' b'report-technical-problems' b'true' InstallationDate: Installed on 2019-10-11 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20191011) RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1 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/1847740/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1847706] Re: Deja Dup still tells python-gi (python 2) is required while duplicity is now python3
Hello everyone. The Dependencies.txt states duplicity 0.8.04-2ubuntu1 which does indeed seem to be python3. So confirming on grounds of technical information given by the original reporter. ** Changed in: deja-dup Status: New => Triaged ** Changed in: deja-dup (Ubuntu) Status: New => Triaged ** Changed in: deja-dup Importance: Undecided => Critical ** Changed in: deja-dup (Ubuntu) Importance: Undecided => High ** Also affects: deja-dup (Ubuntu Eoan) Importance: High Status: Triaged ** Changed in: deja-dup (Ubuntu Eoan) Milestone: None => eoan-updates ** Tags added: regression-proposed -- 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/1847706 Title: Deja Dup still tells python-gi (python 2) is required while duplicity is now python3 Status in Déjà Dup: Triaged Status in deja-dup package in Ubuntu: Triaged Status in deja-dup source package in Eoan: Triaged Bug description: Please see the screenshot attached. When running a backup operation against a remote server with SSH, Deja Dup stops by saying "python-gi" package is required. However, duplicity is updated with Python3 now, so it doesn't make sense to install Python 2 based package. The prerequisite check needs to be updated probably with python3-gi instead. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: deja-dup 40.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 11 12:34:15 2019 InstallationDate: Installed on 2019-08-28 (43 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190822) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: deja-dup UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/deja-dup/+bug/1847706/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1847735] Re: thunderbird can't send anymore (when enigmail is enabled)
I just tested in a fully up-to-date 18.04 VM, I configured thunderbird to use a test gmail account and used enigmail to generate a new keypair. After that I was able to correctly send plain e-mails, e-mails with a signature, and encrypted e-mails. Can you make sure you don't have another version of enigmail locally installed in your profile? What version number does the extension report? What is the output of `apt policy enigmail`? Can you copy-paste the contents of the developer console (which you can open in Thunderbird with Ctrl+Maj+J)? Thanks! ** Changed in: thunderbird (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1847735 Title: thunderbird can't send anymore (when enigmail is enabled) Status in thunderbird package in Ubuntu: Incomplete Bug description: Hi, after this morning's ubuntu 18.04 package updates my thunderbird can't send mails anymore, just nothing happens when pushing the send button. Reason: I have installed the ubuntu enigmail package as well. When disabling enigmail in thunderbird's add-ons manager menu, sending works as normal, but, of course, without pgp encryption. So the thunderbird and enigmail packages are currently incompatible. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: thunderbird 1:60.9.0+build1-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-65.74-generic 4.15.18 Uname: Linux 4.15.0-65-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair AddonCompatCheckDisabled: False ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hadmut 5762 F pulseaudio BuildID: 20191007090452 Channel: Unavailable CurrentDesktop: XFCE Date: Fri Oct 11 11:28:43 2019 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # ifupdown has been replaced by netplan(5) on this system. See # /etc/netplan for current configuration. # To re-enable ifupdown on this system, you can run: #sudo apt install ifupdown IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2018-06-09 (488 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Locales: extensions.sqlite corrupt or missing MostRecentCrashID: bp-491d26ca-c698-4761-9b14-5282d0191011 PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=60.9.0/20191007090452 (In use) RunningIncompatibleAddons: False SourcePackage: thunderbird Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/12/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: H61TIW08.111 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H61H2-TI2 dmi.board.vendor: Medion dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Medion dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrH61TIW08.111:bd10/12/2012:svnMedion:pnG24:pvr1.0:rvnMedion:rnH61H2-TI2:rvr1.0:cvnMedion:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: G24 dmi.product.version: 1.0 dmi.sys.vendor: Medion To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1847735/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1832869] Re: gnome-shell crashed with SIGSEGV in g_hash_table_iter_next → meta_display_list_windows → meta_workspace_list_windows → ffi_call_SYSV → ffi_call()
Confirm no crash on restarting 3.28.4-0ubuntu18.04.2 ** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done verification-done-bionic -- 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/1832869 Title: gnome-shell crashed with SIGSEGV in g_hash_table_iter_next → meta_display_list_windows → meta_workspace_list_windows → ffi_call_SYSV → ffi_call() Status in gnome-shell package in Ubuntu: Triaged Status in gnome-shell-extension-dashtodock package in Ubuntu: Invalid Status in mutter package in Ubuntu: Won't Fix Status in mutter source package in Bionic: Fix Committed Status in mutter source package in Disco: Won't Fix Bug description: [ Description ] GNOME shell crashes on restart when some window actors are opened [ Test case ] - Run gnome-shell in Xorg, start some windows - Hit Alt+F2 - Write 'r' and press Enter - The shell should restart without crashing in meta_workspace_list_windows [ Regression potential ] Javascript errors might be emitted when trying to access to invalidated data, but nothing really harmful. [ Note ] This crash doesn't affect versions after 3.28 for various reasons: - The JS code triggering it isn't there anymore - MetaScreen doesn't exist anymore. Similar crashes might happen in newer versions, but as per different code paths, and so to be reported as different bugs. --- The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.28.4-0ubuntu18.04.1, the problem page at https://errors.ubuntu.com/problem/d3f9725b7fae2763643521acfc58c734f829dd64 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/. https://errors.ubuntu.com/problem/ac8df0b1e2d67e423c634fde1a3acecd3c381d58 https://errors.ubuntu.com/problem/d3f9725b7fae2763643521acfc58c734f829dd64 https://errors.ubuntu.com/problem/1e69eadeb69f4e2b8aa933205d2be3a8db4af36c https://errors.ubuntu.com/problem/6f7810166a3ae02cc8025514d6ffbbde10063e76 https://errors.ubuntu.com/problem/1bfbc00c70cfe6f4f2b66b4efc86f5c089c28680 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1832869/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1827401] Re: gnome-shell crashed in meta_workspace_index -> meta_workspace_activate_with_focus -> meta_window_activate_full
Verified for 3.28.4-0ubuntu18.04.2 ** Tags removed: verification-needed ** Tags added: verification-done verification-done-bionic ** Tags removed: verification-needed-bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1827401 Title: gnome-shell crashed in meta_workspace_index -> meta_workspace_activate_with_focus -> meta_window_activate_full Status in Mutter: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Bionic: Fix Committed Status in mutter source package in Disco: Fix Released Bug description: [ Description ] Shell crashes on meta_workspace_index [ Test case ] No clear way to reproduce this, although we consider fixed monitoring the presence of automatic reports at: https://errors.ubuntu.com/problem/f98d5edcc7588c443201f119bc2c4b586a897cfd [ Regression potential ] None, a window might not be focused although it's an unmanaging one so, not really a regression. --- The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.30.1-2ubuntu1.18.10.2, the problem page at https://errors.ubuntu.com/problem/f98d5edcc7588c443201f119bc2c4b586a897cfd 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/. --- The gjs part of this is actually the same of bug #1812527 To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1827401/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1847742] [NEW] "sudo apt remove libpcsclite1" tries to remove network-manager and more
Public bug reported: I recently needed to remove and reinstall libpcsclite1_1.8.23-1_amd64.deb. I noticed that the removal of this package would result in the removal of various network-relevant packages (see below). I saw bug report #949912 which reported a similar thing in 2012 and marked it fixed. I understand that report dealt with the support of multiarch, but the behaviour of apt in the case of removal of libpcsclite1 seems undesirable to me. Here's the console output I got when trying to remove libpcsclite1 (sorry for the German output): sudo apt remove libpcsclite1 [sudo] Passwort für clemens: Paketlisten werden gelesen... Fertig Abhängigkeitsbaum wird aufgebaut. Statusinformationen werden eingelesen Fertig Die folgenden Pakete wurden automatisch installiert und werden nicht mehr benötigt: fonts-dejavu-extra java-common libatk-wrapper-java libatk-wrapper-java-jni libccid libcolord-gtk1 libgif7 libgssglue1 libnss-myhostname libstoken1 libteamdctl0 libtomcrypt1 libtommath1 vpnc-scripts Verwenden Sie »sudo apt autoremove«, um sie zu entfernen. Die folgenden Pakete werden ENTFERNT: ca-certificates-java gnome-control-center libfreerdp-plugins-standard libopenconnect5 libpcsclite1 network-manager network-manager-config-connectivity-ubuntu network-manager-gnome network-manager openconnect network-manager-openconnect-gnome network-manager-pptp network-manager-pptp-gnome openconnect openjdk-8-jre openjdk-8-jre-headless pcscd plainbox-provider-checkbox plainbox-provider-resource-generic rdesktop tlp-rdw ubuntu-desktop wpasupplicant 0 aktualisiert, 0 neu installiert, 22 zu entfernen und 30 nicht aktualisiert. Nach dieser Operation werden 126 MB Plattenplatz freigegeben. Möchten Sie fortfahren? [J/n] The crucial part is all those packages which apt wants to remove ("werden ENTFERNT"). I guess I could be doing a stupid thing trying to remove the libpcsclite1, but it really seems like unwanted behaviour since continuing this package removal as suggested by apt would result in an offline computer. Cheers, Hans ** Affects: pcsc-lite (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1847742 Title: "sudo apt remove libpcsclite1" tries to remove network-manager and more Status in pcsc-lite package in Ubuntu: New Bug description: I recently needed to remove and reinstall libpcsclite1_1.8.23-1_amd64.deb. I noticed that the removal of this package would result in the removal of various network-relevant packages (see below). I saw bug report #949912 which reported a similar thing in 2012 and marked it fixed. I understand that report dealt with the support of multiarch, but the behaviour of apt in the case of removal of libpcsclite1 seems undesirable to me. Here's the console output I got when trying to remove libpcsclite1 (sorry for the German output): sudo apt remove libpcsclite1 [sudo] Passwort für clemens: Paketlisten werden gelesen... Fertig Abhängigkeitsbaum wird aufgebaut. Statusinformationen werden eingelesen Fertig Die folgenden Pakete wurden automatisch installiert und werden nicht mehr benötigt: fonts-dejavu-extra java-common libatk-wrapper-java libatk-wrapper-java-jni libccid libcolord-gtk1 libgif7 libgssglue1 libnss-myhostname libstoken1 libteamdctl0 libtomcrypt1 libtommath1 vpnc-scripts Verwenden Sie »sudo apt autoremove«, um sie zu entfernen. Die folgenden Pakete werden ENTFERNT: ca-certificates-java gnome-control-center libfreerdp-plugins-standard libopenconnect5 libpcsclite1 network-manager network-manager-config-connectivity-ubuntu network-manager-gnome network-manager openconnect network-manager-openconnect-gnome network-manager-pptp network-manager-pptp-gnome openconnect openjdk-8-jre openjdk-8-jre-headless pcscd plainbox-provider-checkbox plainbox-provider-resource-generic rdesktop tlp-rdw ubuntu-desktop wpasupplicant 0 aktualisiert, 0 neu installiert, 22 zu entfernen und 30 nicht aktualisiert. Nach dieser Operation werden 126 MB Plattenplatz freigegeben. Möchten Sie fortfahren? [J/n] The crucial part is all those packages which apt wants to remove ("werden ENTFERNT"). I guess I could be doing a stupid thing trying to remove the libpcsclite1, but it really seems like unwanted behaviour since continuing this package removal as suggested by apt would result in an offline computer. Cheers, Hans To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1847742/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1791574] Re: gnome-shell crashed with SIGABRT: assertion failed "window->display->focus_window != window" in meta_window_unmanage
Test case works here with 3.28.4-0ubuntu18.04.2, e.u.c is not much helpful though since it tracks gnome-shell version only (bionic doesn't provide such infos to us yet) ** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done verification-done-bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1791574 Title: gnome-shell crashed with SIGABRT: assertion failed "window->display->focus_window != window" in meta_window_unmanage Status in Mutter: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Bionic: Fix Committed Status in mutter source package in Disco: Fix Released Bug description: [ Description ] GNOME Shell crashes when interacting with some "take-input" windows such as the jetbrains products (you can snap install the 2008 versions which are affected), see https://gitlab.gnome.org/GNOME/mutter/issues/308 [ Test case ] Run this script: $ wget -O - https://gitlab.gnome.org/3v1n0/mutter/snippets/453/raw | python3 - The shell should not crash when the windows are closed. [ Regression potential ] The patch introduces changes to the window focus handling, so a window might not be properly focused in some cases. [ Notes to the SRU team ] This fix is still in process of being released to eoan / disco too. https://errors.ubuntu.com/problem/9b0e145ca11443bc44b35a2050317dd51f5ab5c5 Upstream issue: https://gitlab.gnome.org/GNOME/mutter/issues/308 Originally reported as bug 1422253 and fixed in 18.04, but that crash (fixed) was due to a different condition. Test case: https://gitlab.gnome.org/3v1n0/mutter/snippets/453 --- gnome-shell crashed and restarted while I was using it. ProblemType: CrashDistroRelease: Ubuntu 18.10 Package: gnome-shell 3.30.0-1ubuntu1 Uname: Linux 4.19.0-041900rc3-generic x86_64 ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Sep 10 12:39:16 2018 DisplayManager: gdm3 EcryptfsInUse: Yes ExecutablePath: /usr/bin/gnome-shell ExecutableTimestamp: 1536081658 InstallationDate: Installed on 2017-08-16 (389 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcCmdline: /usr/bin/gnome-shell ProcCwd: /home/rocko ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bashSignal: 6SourcePackage: gnome-shell StacktraceTop: () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 meta_window_unmanage () at /usr/lib/x86_64-linux-gnu/libmutter-3.so.0 () at /usr/lib/x86_64-linux-gnu/libmutter-3.so.0 () at /usr/lib/x86_64-linux-gnu/libmutter-3.so.0 Title: gnome-shell crashed with SIGABRT UpgradeStatus: Upgraded to cosmic on 2018-08-15 (25 days ago) UserGroups: adm bumblebee cdrom dip kvm lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1791574/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1847618] Re: language selector ignores input methods other than xim and none in my current locale
I don't know it's an architecture dependent issue because some users who reported this bug which I also have: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/996791 mentioned architecture specific issues. I am running Ubuntu 16.04.6 with multiarch support, I installed it as 32 bit OS but switched to 64 bit OS by means of `dpkg --add-architecture amd64` and I installed 64 bit kernel and libc stuff. I have been running it for three years without problem. I am also suffering from this bug may be related to the current bug: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1350393/ I filed this bug some time ago : https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1773517 If I run the following command `im-config -l` I only get: xim unless I run it like `LANGUAGE=en_US.utf8 im-config -l` in which case I get :ibus uim scim xim -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/1847618 Title: language selector ignores input methods other than xim and none in my current locale Status in language-selector package in Ubuntu: Incomplete Bug description: I use Ubuntu 16.04.6 LTS. I can not reach other input methods such as ibus, fcitx in my current locale which is LANGUAGE=tr_TR.UTF-8. It's not listed in unity-control-center>Language Support>Keyboard Input Method System. If I launch unity-control-center from terminal which is using different locale "LANGUAGE=en_US.utf8 unity-control-center" then there is no problem, all of the installed input methods are in the list. I also tested "python3 /usr/lib/python3/dist-packages/LanguageSelector/ImConfig.py" it also ignores input methods other than xim and none. If I export "LANGUAGE=en_US.utf8" it lists all the other input methods. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/1847618/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1847760] [NEW] package nvidia-dkms-430 430.50-0ubuntu1 failed to install/upgrade: o subprocesso instalado, do pacote nvidia-dkms-430, o script post-installation retornou erro d
Public bug reported: Error when i updated from version 19.04 to 19.10 ProblemType: Package DistroRelease: Ubuntu 19.10 Package: nvidia-dkms-430 430.50-0ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-17.18-generic 5.3.1 Uname: Linux 5.3.0-17-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 Date: Thu Oct 10 15:52:43 2019 ErrorMessage: o subprocesso instalado, do pacote nvidia-dkms-430, o script post-installation retornou erro do status de saída 10 InstallationDate: Installed on 2019-07-08 (94 days ago) InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 (20190227) Python3Details: /usr/bin/python3.7, Python 3.7.5rc1, python3-minimal, 3.7.3-1 PythonDetails: /usr/bin/python2.7, Python 2.7.16+, python-minimal, 2.7.16-1 RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.4 SourcePackage: nvidia-graphics-drivers-430 Title: package nvidia-dkms-430 430.50-0ubuntu1 failed to install/upgrade: o subprocesso instalado, do pacote nvidia-dkms-430, o script post-installation retornou erro do status de saída 10 UpgradeStatus: Upgraded to eoan on 2019-10-10 (0 days ago) ** Affects: nvidia-graphics-drivers-430 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package eoan third-party-packages -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-430 in Ubuntu. https://bugs.launchpad.net/bugs/1847760 Title: package nvidia-dkms-430 430.50-0ubuntu1 failed to install/upgrade: o subprocesso instalado, do pacote nvidia-dkms-430, o script post- installation retornou erro do status de saída 10 Status in nvidia-graphics-drivers-430 package in Ubuntu: New Bug description: Error when i updated from version 19.04 to 19.10 ProblemType: Package DistroRelease: Ubuntu 19.10 Package: nvidia-dkms-430 430.50-0ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-17.18-generic 5.3.1 Uname: Linux 5.3.0-17-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 Date: Thu Oct 10 15:52:43 2019 ErrorMessage: o subprocesso instalado, do pacote nvidia-dkms-430, o script post-installation retornou erro do status de saída 10 InstallationDate: Installed on 2019-07-08 (94 days ago) InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 (20190227) Python3Details: /usr/bin/python3.7, Python 3.7.5rc1, python3-minimal, 3.7.3-1 PythonDetails: /usr/bin/python2.7, Python 2.7.16+, python-minimal, 2.7.16-1 RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.4 SourcePackage: nvidia-graphics-drivers-430 Title: package nvidia-dkms-430 430.50-0ubuntu1 failed to install/upgrade: o subprocesso instalado, do pacote nvidia-dkms-430, o script post-installation retornou erro do status de saída 10 UpgradeStatus: Upgraded to eoan on 2019-10-10 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-430/+bug/1847760/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1847738] Re: Empty item in folder context menu
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nautilus (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1847738 Title: Empty item in folder context menu Status in nautilus package in Ubuntu: Confirmed Bug description: Installed 19.10 from a daily image today (also issue on my current laptop which was upgraded from 19.04). Steps to reproduce Open nautilus Right click a file (example.desktop for example) Note the context menu looks okay Right click a folder (such as Downloads) Note the context menu has a blank entry at the bottom, beneath "Properties" Expected No blank line ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: nautilus 1:3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-17.18-generic 5.3.1 Uname: Linux 5.3.0-17-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 11 11:01:25 2019 GsettingsChanges: b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" InstallationDate: Installed on 2019-10-11 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20191011) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1847738/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1847765] [NEW] network manager using small timeout polling timeouts
Public bug reported: I've been trying to identify wakeup events that cause the CPU to wakeup from idle on a "idle" laptop on Ubuntu Eoan. The good news is that NetworkManager doesn't utilize much CPU when idle, however, it does seem to wakeup from poll()/epool_wait() system calls once every 4-5 seconds on timer timeouts and I was wondering if those are necessary as they keep the CPU from being idle. I ran heath-check [1] for 1 hour to monitor NetworkManager. See the attached output. Look at the "Top polling system calls:" section and you see that poll() and epoll_wait() are polling with timeouts set to be 0.0 seconds, 6.0 and 4.0 seconds. Also look at the "Polling system call analysis:" section and you see a breakdown of the poll()/epoll_wait() calls. Recommendation: 1. Are the 4.0/6.0 poll waits necessary? Why a timeout every 4.0/6.0 seconds? 2. Why are there so many polls with zero timeouts? These normally occur when a quick peek at busy pool events on file descriptors occurs. Are these necessary? Anyhow, this is quite low in priority, but it would be nice to get investigated and fixed just to reduce CPU wakeups. References [1] https://kernel.ubuntu.com/~cking/health-check/ ** Affects: network-manager (Ubuntu) Importance: Low Status: New ** Attachment added: "network manager health-check report log file." https://bugs.launchpad.net/bugs/1847765/+attachment/5296572/+files/network-manager-health-check.log ** Changed in: network-manager (Ubuntu) Importance: Undecided => Low ** Summary changed: - network manager using non-blocking zero timeout polling + network manager using small timeout polling timeouts -- 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/1847765 Title: network manager using small timeout polling timeouts Status in network-manager package in Ubuntu: New Bug description: I've been trying to identify wakeup events that cause the CPU to wakeup from idle on a "idle" laptop on Ubuntu Eoan. The good news is that NetworkManager doesn't utilize much CPU when idle, however, it does seem to wakeup from poll()/epool_wait() system calls once every 4-5 seconds on timer timeouts and I was wondering if those are necessary as they keep the CPU from being idle. I ran heath-check [1] for 1 hour to monitor NetworkManager. See the attached output. Look at the "Top polling system calls:" section and you see that poll() and epoll_wait() are polling with timeouts set to be 0.0 seconds, 6.0 and 4.0 seconds. Also look at the "Polling system call analysis:" section and you see a breakdown of the poll()/epoll_wait() calls. Recommendation: 1. Are the 4.0/6.0 poll waits necessary? Why a timeout every 4.0/6.0 seconds? 2. Why are there so many polls with zero timeouts? These normally occur when a quick peek at busy pool events on file descriptors occurs. Are these necessary? Anyhow, this is quite low in priority, but it would be nice to get investigated and fixed just to reduce CPU wakeups. References [1] https://kernel.ubuntu.com/~cking/health-check/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1847765/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1847742] Re: "sudo apt remove libpcsclite1" tries to remove network-manager and more
Just do not remove libpcsclite1. You can reinstall it with: sudo apt install --reinstall libpcsclite1 If you *really* think it is a bug then please report it to wpasupplicant that depends on libpcsclite1. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1847742 Title: "sudo apt remove libpcsclite1" tries to remove network-manager and more Status in pcsc-lite package in Ubuntu: New Bug description: I recently needed to remove and reinstall libpcsclite1_1.8.23-1_amd64.deb. I noticed that the removal of this package would result in the removal of various network-relevant packages (see below). I saw bug report #949912 which reported a similar thing in 2012 and marked it fixed. I understand that report dealt with the support of multiarch, but the behaviour of apt in the case of removal of libpcsclite1 seems undesirable to me. Here's the console output I got when trying to remove libpcsclite1 (sorry for the German output): sudo apt remove libpcsclite1 [sudo] Passwort für clemens: Paketlisten werden gelesen... Fertig Abhängigkeitsbaum wird aufgebaut. Statusinformationen werden eingelesen Fertig Die folgenden Pakete wurden automatisch installiert und werden nicht mehr benötigt: fonts-dejavu-extra java-common libatk-wrapper-java libatk-wrapper-java-jni libccid libcolord-gtk1 libgif7 libgssglue1 libnss-myhostname libstoken1 libteamdctl0 libtomcrypt1 libtommath1 vpnc-scripts Verwenden Sie »sudo apt autoremove«, um sie zu entfernen. Die folgenden Pakete werden ENTFERNT: ca-certificates-java gnome-control-center libfreerdp-plugins-standard libopenconnect5 libpcsclite1 network-manager network-manager-config-connectivity-ubuntu network-manager-gnome network-manager openconnect network-manager-openconnect-gnome network-manager-pptp network-manager-pptp-gnome openconnect openjdk-8-jre openjdk-8-jre-headless pcscd plainbox-provider-checkbox plainbox-provider-resource-generic rdesktop tlp-rdw ubuntu-desktop wpasupplicant 0 aktualisiert, 0 neu installiert, 22 zu entfernen und 30 nicht aktualisiert. Nach dieser Operation werden 126 MB Plattenplatz freigegeben. Möchten Sie fortfahren? [J/n] The crucial part is all those packages which apt wants to remove ("werden ENTFERNT"). I guess I could be doing a stupid thing trying to remove the libpcsclite1, but it really seems like unwanted behaviour since continuing this package removal as suggested by apt would result in an offline computer. Cheers, Hans To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1847742/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1706460] Re: Outdated Totem documentation describes and mentions features absent from the software
Upstream report closed 20190131 as user docs updated in version 3.32 I can't check with totem 3.32 in Ubuntu 19.04 but... Online help and man page both updated in Ubuntu 19.10 with totem 3.34.1 ** Changed in: totem (Ubuntu) Status: Triaged => Fix Released -- 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/1706460 Title: Outdated Totem documentation describes and mentions features absent from the software Status in Totem: Expired Status in totem package in Ubuntu: Fix Released Bug description: 'man totem' mentions "F9 toggle display of the playlist" and the Help document in totem often describes choosing the "sidebar" option from the "View" menu. Pressing F9 does nothing. There is no "sidebar" option in the "View" menu. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: totem 3.24.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17 Uname: Linux 4.10.0-26-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 CurrentDesktop: XFCE Date: Tue Jul 25 18:47:38 2017 InstallationDate: Installed on 2016-06-05 (415 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: totem UpgradeStatus: Upgraded to zesty on 2017-04-13 (103 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/totem/+bug/1706460/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1399307] Re: totem dims screen off
This release of Ubuntu is no longer receiving maintenance updates. If this is still an issue using a maintained version of Ubuntu please let us know otherwise this report can be left to expire in approximately 60 days time. Paul White [Ubuntu Bug Squad] ** Tags added: trusty ** Changed in: totem (Ubuntu) Status: New => Incomplete -- 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/1399307 Title: totem dims screen off Status in totem package in Ubuntu: Incomplete Bug description: On Ubuntu 14.04 LTS, when playing more than one video with totem on a playlist (not simultaneously ofcourse ) . The screen dims off when then second video starts. Even though the option to disable the screen-saver while playing video/audio. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1399307/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1846882] Re: Thunderbird crashes when clicking on menu item
As asked, I have removed the Enigmail add-on installed from the add-on store, clased Thunderbird, installed Enigmail 2:2.1.2-0ubuntu1 from the Ubuntu archive and the problem persists, now in Thunderbird 1:68.1.2+build1-0ubuntu1. I still can’t reproduce the issue with the Thunderbird version downloaded directly from Mozilla. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1846882 Title: Thunderbird crashes when clicking on menu item Status in thunderbird package in Ubuntu: Incomplete Bug description: Thunderbird 1:68.1.1+build1-0ubuntu1 On Ubuntu 19.10 fully updated. When writing an email, upon clicking on Enigmail in the menu bar, Thunderbird crashes. I contacted Enigmail’s lead dev about the issue who wrote: "…but even if the crash is initiated by Enigmail, the cause is certainly in Thunderbird. Enigmail is purely JavaScript and XUL - and by definition of the programming languages, these two cannot crash Thunderbird." I tried Thunderbird 68.1.1 from Mozilla’s site, and can’t reproduce the problem with it. Here is Thunderbird’s log upon crashing: AdapterDeviceID: 0x1912 AdapterDriverVendor: mesa/i965 AdapterDriverVersion: 19.3.0.0 AdapterVendorID: 0x8086 Add-ons: %7Be2fda1a4-762b-4020-b5ad-a41df1933103%7D:68.1.1,%7B847b3a00-7ab1-11d4-8f02-006008948af5%7D:2.1.2,antidote7_linux_thunderbird_102%40druide.com:10.1.30,en-CA%40dictionaries.addons.mozilla.org:3.1.0,fr-dicollecte%40dictionaries.addons.mozilla.org:6.3.1webext,wetransfer%40extensions.thunderbird.net:2.0.0,thunderbird-compact-dark%40mozilla.org:1.0,google%40search.mozilla.org:1.0,bing%40search.mozilla.org:1.0,amazon%40search.mozilla.org:1.1,ddg%40search.mozilla.org:1.0,qwant%40search.mozilla.org:1.0,wikipedia%40search.mozilla.org:1.0,twitter%40search.mozilla.org:1.0,langpack-fr%40thunderbird.mozilla.org:68.0,wetransfer%40extensions.thunderbird.net:2.0.0 BuildID: 20191001201558 ContentSandboxCapabilities: 119 ContentSandboxCapable: 1 ContentSandboxLevel: 0 CrashTime: 1570225903 EventLoopNestingLevel: 1 FramePoisonBase: 9223372036600930304 FramePoisonSize: 4096 InstallTime: 1570020285 IsWayland: 0 Notes: Ubuntu Eoan Ermine (development branch)FP(D00-L1000-W-T000) WR? WR- OMTP? OMTP+3 ProductID: {3550f703-e582-4d05-9a08-453d09bdfdc6} ProductName: Thunderbird ReleaseChannel: release SafeMode: 0 SecondsSinceLastCrash: 383 StartupCrash: 0 StartupTime: 1570225565 ThreadIdNameMapping: 20357:"Gecko_IOThread",20358:"JS Watchdog",20359:"JS Helper",20360:"JS Helper",20361:"JS Helper",20362:"JS Helper",20363:"Link Monitor",20364:"Socket Thread",20372:"Timer",20373:"Cache2 I/O",20375:"DataStorage",20376:"Cookie",20379:"GMPThread",20380:"Worker Launcher",20381:"SoftwareVsyncThread",20382:"Compositor",20383:"ImgDecoder #1",20384:"ImageIO",20390:"ImageBridgeChild",20391:"IPDL Background",20392:"DOM Worker",20394:"HTML5 Parser",20397:"StyleThread#1",20396:"StyleThread#0",20398:"StyleThread#2",20401:"mozStorage #1",20407:"localStorage DB",20408:"ImgDecoder #2",20410:"Cache I/O",20411:"DNS Resolver #1",20412:"URL Classifier",20413:"Classifier Update",20415:"QuotaManager IO",20426:"DNS Resolver #2",20427:"DNS Resolver #3",20429:"ImgDecoder #3",20439:"mozStorage #3",20452:"DOM Worker",20467:"mozStorage #5",20468:"mozStorage #6",20469:"mozStorage #7",20479:"DOM Worker",20500:"mozStorage #8",27048:"StreamTrans #18", Throttleable: 1 UptimeTS: 337.7284093 Vendor: Version: 68.1.1 useragent_locale: fr This is what I get when running Thunderbird from the console and after the crash occurred: 1570277554871 addons.xpi WARNCan't get modified time of /usr/lib/thunderbird/features/wetrans...@extensions.thunderbird.net 1570277554912 addons.xpi-utilsWARNupdateMetadata: Add-on wetrans...@extensions.thunderbird.net is invalid: [Exception... "Component returned failure code: 0x80520006 (NS_ERROR_FILE_TARGET_DOES_NOT_EXIST) [nsIFile.isFile]" nsresult: "0x80520006 (NS_ERROR_FILE_TARGET_DOES_NOT_EXIST)" location: "JS frame :: resource://gre/modules/addons/XPIInstall.jsm :: get :: line 235" data: no] Stack trace: get()@resource://gre/modules/addons/XPIInstall.jsm:235 syncLoadManifest()@resource://gre/modules/addons/XPIInstall.jsm:745 updateMetadata()@resource://gre/modules/addons/XPIDatabase.jsm:2821 updateExistingAddon()@resource://gre/modules/addons/XPIDatabase.jsm:3036 processFileChanges()@resource://gre/modules/addons/XPIDatabase.jsm:3125 checkForChanges()@resource://gre/modules/addons/XPIProvider.jsm:2946 startup()@resource://gre/modules/addons/XPIProvider.jsm:2406 callProvider()@resource://gre/modules/AddonManager.jsm:213 _startProvider()@resource://gre/modules/AddonManager.jsm:649 startup()@resource://gre/modules/AddonManager.jsm:873 startup()@resource://gre/modules/AddonManage
[Desktop-packages] [Bug 1847772] [NEW] English in the localized version of Tb 68
Public bug reported: After updating to Thunderbird 68.1.1 from the Ubuntu archive, folder names Inbox, Drafts, Sent, Archives, Spam, Trash all appear in English in the French UI. The rest of the UI is in French. This issue is still present in Thunderbird 1:68.1.2+build1-0ubuntu1. This problem does exist in Thunderbird 68.1.1 nor 68.1.2 downloaded directly from Mozilla. ** Affects: thunderbird (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1847772 Title: English in the localized version of Tb 68 Status in thunderbird package in Ubuntu: New Bug description: After updating to Thunderbird 68.1.1 from the Ubuntu archive, folder names Inbox, Drafts, Sent, Archives, Spam, Trash all appear in English in the French UI. The rest of the UI is in French. This issue is still present in Thunderbird 1:68.1.2+build1-0ubuntu1. This problem does exist in Thunderbird 68.1.1 nor 68.1.2 downloaded directly from Mozilla. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1847772/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1800260] Re: [snap] with CSD and Yaru, background color of the header bar is incorrect
The gtk-common-theme snap in the candidate channel has now been promoted to stable, so I'm closing this bug. ** Changed in: chromium-browser (Ubuntu) Status: Confirmed => Fix Released -- 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/1800260 Title: [snap] with CSD and Yaru, background color of the header bar is incorrect Status in chromium-browser package in Ubuntu: Fix Released Bug description: Description: Ubuntu 18.04.1 LTS Release: 18.04 Channel:Stable Version:70.0.3538.67 Updated:10/19/2018 License:Free Developer: Canonical Source: Snap Store Installed Size: 148.2 MB Settings -> Appearance: "Use system title bar and borders" was turned off. Close, minimize, maximize buttons became oval (more of stretched down) instead of circle. Turned back it on, buttons went back to normal shape (circle). It's a repeatable action. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1800260/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1847618] Re: language selector ignores input methods other than xim and none in my current locale
Thanks! On 2019-10-11 14:15, kenn wrote: > If I run the following command `im-config -l` I only get: > xim > unless I run it like `LANGUAGE=en_US.utf8 im-config -l` > in which case I get :ibus uim scim xim That was odd. But then this is an im-config bug. The other bugs you mentioned seem to be unrelated to this one, and im-config consists of architecture independent shell code. Can you please open a terminal window, run the commands below, and show in a comment here what they output: locale locale -a ** Summary changed: - language selector ignores input methods other than xim and none in my current locale + im-config ignores input methods other than xim in my current locale ** Package changed: language-selector (Ubuntu) => im-config (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/1847618 Title: im-config ignores input methods other than xim in my current locale Status in im-config package in Ubuntu: Incomplete Bug description: I use Ubuntu 16.04.6 LTS. I can not reach other input methods such as ibus, fcitx in my current locale which is LANGUAGE=tr_TR.UTF-8. It's not listed in unity-control-center>Language Support>Keyboard Input Method System. If I launch unity-control-center from terminal which is using different locale "LANGUAGE=en_US.utf8 unity-control-center" then there is no problem, all of the installed input methods are in the list. I also tested "python3 /usr/lib/python3/dist-packages/LanguageSelector/ImConfig.py" it also ignores input methods other than xim and none. If I export "LANGUAGE=en_US.utf8" it lists all the other input methods. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/im-config/+bug/1847618/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1847711] Re: Move zsys tags from org.zsys to com.ubuntu.zsys
** Also affects: grub2 (Ubuntu) Importance: Undecided Status: New ** Also affects: grubzfs-testsuite (Ubuntu) Importance: Undecided Status: New ** Changed in: grub2 (Ubuntu) Status: New => Fix Committed ** Changed in: grubzfs-testsuite (Ubuntu) Status: New => Fix Committed ** Changed in: ubiquity (Ubuntu) Status: New => Fix Committed ** Changed in: zfs-linux (Ubuntu) Status: New => Fix Committed ** Changed in: zsys (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to zsys in Ubuntu. https://bugs.launchpad.net/bugs/1847711 Title: Move zsys tags from org.zsys to com.ubuntu.zsys Status in grub2 package in Ubuntu: Fix Committed Status in grubzfs-testsuite package in Ubuntu: Fix Committed Status in ubiquity package in Ubuntu: Fix Committed Status in zfs-linux package in Ubuntu: Fix Committed Status in zsys package in Ubuntu: Fix Committed Bug description: As we are not going to own in the end org.zsys, move our identifier tags to com.ubuntu.zsys. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1847711/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1847742] Re: "sudo apt remove libpcsclite1" tries to remove network-manager and more
OK, sorry. I just found it odd that removing a library for smart card stuff also removes things like ubuntu-desktop or rdesktop. Thanks for your work and your quick reply, though! Am October 11, 2019 1:02:09 PM UTC schrieb Ludovic Rousseau : >Just do not remove libpcsclite1. > >You can reinstall it with: >sudo apt install --reinstall libpcsclite1 > >If you *really* think it is a bug then please report it to >wpasupplicant >that depends on libpcsclite1. > >-- >You received this bug notification because you are subscribed to the >bug >report. >https://bugs.launchpad.net/bugs/1847742 > >Title: > "sudo apt remove libpcsclite1" tries to remove network-manager and > more > >Status in pcsc-lite package in Ubuntu: > New > >Bug description: > I recently needed to remove and reinstall > libpcsclite1_1.8.23-1_amd64.deb. I noticed that the removal of this > package would result in the removal of various network-relevant > packages (see below). I saw bug report #949912 which reported a > similar thing in 2012 and marked it fixed. I understand that report > dealt with the support of multiarch, but the behaviour of apt in the > case of removal of libpcsclite1 seems undesirable to me. Here's the > console output I got when trying to remove libpcsclite1 (sorry for the > German output): > > sudo apt remove libpcsclite1 > [sudo] Passwort für clemens: > Paketlisten werden gelesen... Fertig > Abhängigkeitsbaum wird aufgebaut. > Statusinformationen werden eingelesen Fertig >Die folgenden Pakete wurden automatisch installiert und werden nicht >mehr benötigt: >fonts-dejavu-extra java-common libatk-wrapper-java >libatk-wrapper-java-jni libccid libcolord-gtk1 > libgif7 libgssglue1 libnss-myhostname libstoken1 libteamdctl0 > libtomcrypt1 libtommath1 vpnc-scripts > Verwenden Sie »sudo apt autoremove«, um sie zu entfernen. > Die folgenden Pakete werden ENTFERNT: >ca-certificates-java gnome-control-center libfreerdp-plugins-standard >libopenconnect5 libpcsclite1 >network-manager network-manager-config-connectivity-ubuntu >network-manager-gnome network-manager >openconnect network-manager-openconnect-gnome network-manager-pptp >network-manager-pptp-gnome >openconnect openjdk-8-jre openjdk-8-jre-headless pcscd >plainbox-provider-checkbox >plainbox-provider-resource-generic rdesktop tlp-rdw ubuntu-desktop >wpasupplicant >0 aktualisiert, 0 neu installiert, 22 zu entfernen und 30 nicht >aktualisiert. > Nach dieser Operation werden 126 MB Plattenplatz freigegeben. > Möchten Sie fortfahren? [J/n] > > The crucial part is all those packages which apt wants to remove > ("werden ENTFERNT"). I guess I could be doing a stupid thing trying to > remove the libpcsclite1, but it really seems like unwanted behaviour > since continuing this package removal as suggested by apt would result > in an offline computer. > > Cheers, > > Hans > >To manage notifications about this bug go to: >https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1847742/+subscriptions -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1847742 Title: "sudo apt remove libpcsclite1" tries to remove network-manager and more Status in pcsc-lite package in Ubuntu: New Bug description: I recently needed to remove and reinstall libpcsclite1_1.8.23-1_amd64.deb. I noticed that the removal of this package would result in the removal of various network-relevant packages (see below). I saw bug report #949912 which reported a similar thing in 2012 and marked it fixed. I understand that report dealt with the support of multiarch, but the behaviour of apt in the case of removal of libpcsclite1 seems undesirable to me. Here's the console output I got when trying to remove libpcsclite1 (sorry for the German output): sudo apt remove libpcsclite1 [sudo] Passwort für clemens: Paketlisten werden gelesen... Fertig Abhängigkeitsbaum wird aufgebaut. Statusinformationen werden eingelesen Fertig Die folgenden Pakete wurden automatisch installiert und werden nicht mehr benötigt: fonts-dejavu-extra java-common libatk-wrapper-java libatk-wrapper-java-jni libccid libcolord-gtk1 libgif7 libgssglue1 libnss-myhostname libstoken1 libteamdctl0 libtomcrypt1 libtommath1 vpnc-scripts Verwenden Sie »sudo apt autoremove«, um sie zu entfernen. Die folgenden Pakete werden ENTFERNT: ca-certificates-java gnome-control-center libfreerdp-plugins-standard libopenconnect5 libpcsclite1 network-manager network-manager-config-connectivity-ubuntu network-manager-gnome network-manager openconnect network-manager-openconnect-gnome network-manager-pptp network-manager-pptp-gnome openconnect openjdk-8-jre openjdk-8-jre-headless pcscd plainbox-provider-checkbox plainbox-provider-resource-generic rdesktop tlp-rdw ubuntu-desktop wpasupplicant 0 aktualisiert, 0 neu installiert, 22 zu entfernen und
[Desktop-packages] [Bug 1844422] Re: WPA3-SAE support
well, those running KDE (like me) will still have problems but it should solve it for many. (Lots of reasons, but suffice the gnome shell UI is intensely counter-productive for me). Any chance of it being supported on LTS or disco? -- 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/1844422 Title: WPA3-SAE support Status in gnome-shell package in Ubuntu: Fix Released Status in network-manager package in Ubuntu: Fix Committed Bug description: After some user feedback WPA3 support for NetworkManager has been finalized upstream: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/e1608030c6614d8dfd86122e9df81fdaad9453c9 https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/84a86ce55f1e70cb32217d2c74242ff848db8cd7 https://gitlab.freedesktop.org/NetworkManager/NetworkManager/merge_requests/276/diffs?commit_id=8d4497088fff562773b9c05260e810833bfc9c85 At this time NetworkManager will not associate with Wifi-networks using WPA3. Tested using Ubuntu Ubuntu Eoan Ermine [development branch] with NetworkManager 1.20.2-1ubuntu1 and WPA_Supplicant 2:2.9-1ubuntu1. It would be great if the aforementioned commits where backported to Eoan before release, so that Eoan based systems will associate with WiFi-networks using WPA3. == Update 09-10-2019: So it has come to my attention that NetworkManager needs one additional commit backported from upstream to make WPA3-SAE work: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/e36c297fd8c6b1b57cd120739cc5ee8eab57aa08 Without this latest commit connecting to WPA3-personal networks will still fail because of a lack of 802.11w support in the network-manager settings. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1844422/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1847706] Re: Deja Dup still tells python-gi (python 2) is required while duplicity is now python3
FWIW, "python-gi" is probably from: debian/rules override_dh_auto_configure: dh_auto_configure -- \ --libexecdir=/usr/lib \ -Dgvfs_pkgs=gvfs-backends,python-gi,gir1.2-glib-2.0 \ -Dboto_pkgs=python-boto \ -Dcloudfiles_pkgs=python-cloudfiles \ -Dswiftclient_pkgs=python-swiftclient and it seems the definition of gvfs_pkgs is: meson_options.txt option('gvfs_pkgs', type: 'string', value: '', description: 'Distro package names to install giobackend duplicity support, separated by commas') -- 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/1847706 Title: Deja Dup still tells python-gi (python 2) is required while duplicity is now python3 Status in Déjà Dup: Triaged Status in deja-dup package in Ubuntu: Triaged Status in deja-dup source package in Eoan: Triaged Bug description: Please see the screenshot attached. When running a backup operation against a remote server with SSH, Deja Dup stops by saying "python-gi" package is required. However, duplicity is updated with Python3 now, so it doesn't make sense to install Python 2 based package. The prerequisite check needs to be updated probably with python3-gi instead. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: deja-dup 40.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 11 12:34:15 2019 InstallationDate: Installed on 2019-08-28 (43 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190822) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: deja-dup UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/deja-dup/+bug/1847706/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1847742] Re: "sudo apt remove libpcsclite1" tries to remove network-manager and more
** Changed in: pcsc-lite (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1847742 Title: "sudo apt remove libpcsclite1" tries to remove network-manager and more Status in pcsc-lite package in Ubuntu: Fix Released Bug description: I recently needed to remove and reinstall libpcsclite1_1.8.23-1_amd64.deb. I noticed that the removal of this package would result in the removal of various network-relevant packages (see below). I saw bug report #949912 which reported a similar thing in 2012 and marked it fixed. I understand that report dealt with the support of multiarch, but the behaviour of apt in the case of removal of libpcsclite1 seems undesirable to me. Here's the console output I got when trying to remove libpcsclite1 (sorry for the German output): sudo apt remove libpcsclite1 [sudo] Passwort für clemens: Paketlisten werden gelesen... Fertig Abhängigkeitsbaum wird aufgebaut. Statusinformationen werden eingelesen Fertig Die folgenden Pakete wurden automatisch installiert und werden nicht mehr benötigt: fonts-dejavu-extra java-common libatk-wrapper-java libatk-wrapper-java-jni libccid libcolord-gtk1 libgif7 libgssglue1 libnss-myhostname libstoken1 libteamdctl0 libtomcrypt1 libtommath1 vpnc-scripts Verwenden Sie »sudo apt autoremove«, um sie zu entfernen. Die folgenden Pakete werden ENTFERNT: ca-certificates-java gnome-control-center libfreerdp-plugins-standard libopenconnect5 libpcsclite1 network-manager network-manager-config-connectivity-ubuntu network-manager-gnome network-manager openconnect network-manager-openconnect-gnome network-manager-pptp network-manager-pptp-gnome openconnect openjdk-8-jre openjdk-8-jre-headless pcscd plainbox-provider-checkbox plainbox-provider-resource-generic rdesktop tlp-rdw ubuntu-desktop wpasupplicant 0 aktualisiert, 0 neu installiert, 22 zu entfernen und 30 nicht aktualisiert. Nach dieser Operation werden 126 MB Plattenplatz freigegeben. Möchten Sie fortfahren? [J/n] The crucial part is all those packages which apt wants to remove ("werden ENTFERNT"). I guess I could be doing a stupid thing trying to remove the libpcsclite1, but it really seems like unwanted behaviour since continuing this package removal as suggested by apt would result in an offline computer. Cheers, Hans To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1847742/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1845847] Re: Programs don't scale properly on 1366x768 monitor. On a dual monitor setup, moving app from 1920x1080 monitor to 1366x768 monitor the left 2cm is missing because t
I never tested it on 19.04 but I'm sure that I would have tripped over it if there was a problem. I have been using 9.10 regularly now for about 2 weeks. (I noticed that Gnome went from 3.33xxx to 3.34.1). The problem reported is no longer present. PROBLEM FIXED, THANKS. Tested on Firefox, Rythmbox, System Monitor, LibreOffice 6.3, and Thunderbird. Please close this bug report. -- 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/1845847 Title: Programs don't scale properly on 1366x768 monitor. On a dual monitor setup, moving app from 1920x1080 monitor to 1366x768 monitor the left 2cm is missing because the window is too big. Tested with firefox and also Rythmbox. Status in firefox package in Ubuntu: Incomplete Bug description: This is the Sept. 28 beta version of Ubuntu 19.10. lsb_release -rd Description: Ubuntu Eoan Ermine (development branch) Release: 19.10 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: firefox 69.0.1+build1-0ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 BuildID: 20190918155341 CurrentDesktop: ubuntu:GNOME Date: Sun Sep 29 09:23:01 2019 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:997 DefaultProfileThemes: extensions.sqlite corrupt or missing InstallationDate: Installed on 2019-09-28 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926.1) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=69.0.1/20190918155341 (In use) SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1845847/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1760818] Re: gedit and gnome-calculator transparency/graphics corruption issue when GTK_IM_MODULE=xim is set
I'm able to reproduce the faulty on bionic (not upgraded from xenial), with GTK_IM_MODULE=xim and an empty .xinputrc. Can also confirm the workaround suggested by Heiko L seems to fix this issue, by changing /usr/share/themes/Ambiance/gtk-3.20/gtk.css to this: > textview text { >background-color: white; > } > scrollbar { >background-color: white; > } > @import url("gtk-main.css"); This worked immediately after restarting gnome-calculator (installed from deb, not snap) and gedit, no other system changes were required. ** Package changed: gtk+3.0 (Ubuntu) => ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to im-config in Ubuntu. https://bugs.launchpad.net/bugs/1760818 Title: gedit and gnome-calculator transparency/graphics corruption issue when GTK_IM_MODULE=xim is set Status in Ubuntu: Confirmed Status in im-config package in Ubuntu: Confirmed Bug description: In a "Ubuntu" (Xorg) session on 18.04 gedit and gnome-calculator suffer from a graphics issue where parts of their windows hold parts of wallpaper or other windows' contents as background. See attached screenshot. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: light-themes 16.10+18.04.20180328-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 3 09:12:31 2018 PackageArchitecture: all SourcePackage: ubuntu-themes UpgradeStatus: Upgraded to bionic on 2018-02-07 (54 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1760818/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1847069] Re: [snap] Chromium snap starts slowly
It cannot be corrected, can it? -- 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/1847069 Title: [snap] Chromium snap starts slowly Status in chromium-browser package in Ubuntu: New Bug description: The problem is shown here, https://discourse.ubuntu.com/t/call-for- testing-chromium-browser-deb-to-snap-transition/11179/141 more graphically. Chromium snap takes quite a while to start and doesn't carry the system theme, whereas the chromium-browser folder taken off the snap/chromium starts practically immediately. The libcanberra-gtk3-module is missing inside the snap, and cannot use the module in the system. The Chromium snap is 607.3 MB, while the standalone Chromium is 237.2 MB, taken off the snap. Conclusion on Chromium snap on Ubuntu Eoan; Two bugs and a missing module 1) Starts slowly, 2) Cannot carry the system theme, 3) Doesn't have libcanberra-gtk3-module To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1847069/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1847069] Re: [snap] Chromium snap starts slowly
The status is NOT incomplete, as I am writing from the Chromium browser taken OFF the snap, leaner and snappier. Have a good day! -- 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/1847069 Title: [snap] Chromium snap starts slowly Status in chromium-browser package in Ubuntu: New Bug description: The problem is shown here, https://discourse.ubuntu.com/t/call-for- testing-chromium-browser-deb-to-snap-transition/11179/141 more graphically. Chromium snap takes quite a while to start and doesn't carry the system theme, whereas the chromium-browser folder taken off the snap/chromium starts practically immediately. The libcanberra-gtk3-module is missing inside the snap, and cannot use the module in the system. The Chromium snap is 607.3 MB, while the standalone Chromium is 237.2 MB, taken off the snap. Conclusion on Chromium snap on Ubuntu Eoan; Two bugs and a missing module 1) Starts slowly, 2) Cannot carry the system theme, 3) Doesn't have libcanberra-gtk3-module To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1847069/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1835639] Re: During boot - System bootorder not found
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-terminal (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1835639 Title: During boot - System bootorder not found Status in Ubuntu: Confirmed Bug description: On HP Laptop Elitebook G1 after upgrade from 18.04 to 19.04 I get displayed very early on System Bootorder not found, Initializing defaults (next line) Creating boot entry "boot0001" with label "ubuntu" for file /EFI/ubuntu/shimx64.efi then it waits 30sec and boots Next boot it sais boot0002 and so on rbeerli@GS6:~$ efibootmgr .v BootCurrent: Timeout: 0 seconds BootOrder: 0004 Boot* Notebook Hard Drive Boot0001* Notebook Ethernet Boot0002* ubuntu Boot0003* ubuntu Boot0004* ubuntu ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-terminal 3.32.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jul 7 05:45:25 2019 ExecutablePath: /usr/lib/gnome-terminal/gnome-terminal-server InstallationDate: Installed on 2019-04-03 (94 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-terminal UpgradeStatus: Upgraded to disco on 2019-07-06 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1835639/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1835639] Re: During boot - System bootorder not found
** Package changed: gnome-terminal (Ubuntu) => ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1835639 Title: During boot - System bootorder not found Status in Ubuntu: Confirmed Bug description: On HP Laptop Elitebook G1 after upgrade from 18.04 to 19.04 I get displayed very early on System Bootorder not found, Initializing defaults (next line) Creating boot entry "boot0001" with label "ubuntu" for file /EFI/ubuntu/shimx64.efi then it waits 30sec and boots Next boot it sais boot0002 and so on rbeerli@GS6:~$ efibootmgr .v BootCurrent: Timeout: 0 seconds BootOrder: 0004 Boot* Notebook Hard Drive Boot0001* Notebook Ethernet Boot0002* ubuntu Boot0003* ubuntu Boot0004* ubuntu ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-terminal 3.32.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jul 7 05:45:25 2019 ExecutablePath: /usr/lib/gnome-terminal/gnome-terminal-server InstallationDate: Installed on 2019-04-03 (94 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-terminal UpgradeStatus: Upgraded to disco on 2019-07-06 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1835639/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1847618] Re: im-config ignores input methods other than xim in my current locale
I figured out a way to reproduce the problem: $ im-config -l ibus fcitx xim $ LC_MESSAGES=tr_TR.UTF-8 LANGUAGE= im-config -l xim $ By now I'm pretty sure that you have explicitly set either LC_MESSAGES or LC_ALL to "tr_TR.UTF-8". While I'd advise you from doing so on an Ubuntu desktop (none of those variables would have been explicitly set if you had relied on Language Support for handling your locale), it still makes no sense that it causes the 'im-config -l' command to fail. So I submitted a merge request to Debian: https://salsa.debian.org/input-method-team/im-config/merge_requests/3/diffs You should be able to fix it for yourself either by not setting LC_MESSAGES and/or LC_ALL explicitly, or by editing the /usr/share/im- config/xinputrc.common file in accordance with the merge request. Would appreciate your confirmation that this is it. ** Changed in: im-config (Ubuntu) Importance: Undecided => Low ** Changed in: im-config (Ubuntu) Status: Incomplete => In Progress ** Changed in: im-config (Ubuntu) Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to im-config in Ubuntu. https://bugs.launchpad.net/bugs/1847618 Title: im-config ignores input methods other than xim in my current locale Status in im-config package in Ubuntu: In Progress Bug description: I use Ubuntu 16.04.6 LTS. I can not reach other input methods such as ibus, fcitx in my current locale which is LANGUAGE=tr_TR.UTF-8. It's not listed in unity-control-center>Language Support>Keyboard Input Method System. If I launch unity-control-center from terminal which is using different locale "LANGUAGE=en_US.utf8 unity-control-center" then there is no problem, all of the installed input methods are in the list. I also tested "python3 /usr/lib/python3/dist-packages/LanguageSelector/ImConfig.py" it also ignores input methods other than xim and none. If I export "LANGUAGE=en_US.utf8" it lists all the other input methods. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/im-config/+bug/1847618/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1847706] Re: Deja Dup still tells python-gi (python 2) is required while duplicity is now python3
** Tags removed: regression-proposed ** Changed in: deja-dup (Ubuntu Eoan) Milestone: eoan-updates => None -- 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/1847706 Title: Deja Dup still tells python-gi (python 2) is required while duplicity is now python3 Status in Déjà Dup: Triaged Status in deja-dup package in Ubuntu: Triaged Status in deja-dup source package in Eoan: Triaged Bug description: Please see the screenshot attached. When running a backup operation against a remote server with SSH, Deja Dup stops by saying "python-gi" package is required. However, duplicity is updated with Python3 now, so it doesn't make sense to install Python 2 based package. The prerequisite check needs to be updated probably with python3-gi instead. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: deja-dup 40.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 11 12:34:15 2019 InstallationDate: Installed on 2019-08-28 (43 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190822) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: deja-dup UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/deja-dup/+bug/1847706/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1847618] Re: im-config ignores input methods other than xim in my current locale
Thank you for responding and quick coverage. I added my current locale in the attachment. Ironically `LC_MESSAGES=tr_TR.UTF-8 LANGUAGE= im-config -l` prints full list: ibus uim scim xim but not this `LC_MESSAGES=tr_TR.UTF-8 im-config -l`, this prints: xim I am happy to hear that you pinpoint the bug. I thought it was a more complicated issue. I can apply the workaround you suggested. Cheers ** Attachment added: "mylocale.txt" https://bugs.launchpad.net/ubuntu/+source/im-config/+bug/1847618/+attachment/5296618/+files/mylocale.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to im-config in Ubuntu. https://bugs.launchpad.net/bugs/1847618 Title: im-config ignores input methods other than xim in my current locale Status in im-config package in Ubuntu: In Progress Bug description: I use Ubuntu 16.04.6 LTS. I can not reach other input methods such as ibus, fcitx in my current locale which is LANGUAGE=tr_TR.UTF-8. It's not listed in unity-control-center>Language Support>Keyboard Input Method System. If I launch unity-control-center from terminal which is using different locale "LANGUAGE=en_US.utf8 unity-control-center" then there is no problem, all of the installed input methods are in the list. I also tested "python3 /usr/lib/python3/dist-packages/LanguageSelector/ImConfig.py" it also ignores input methods other than xim and none. If I export "LANGUAGE=en_US.utf8" it lists all the other input methods. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/im-config/+bug/1847618/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1846140] Re: Realtek RTL8723BU doesn't work well in ubuntu
Is the fix on the link a patch proposed for the kernel? Sorry, I don't understand. -- 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/1846140 Title: Realtek RTL8723BU doesn't work well in ubuntu Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: New Bug description: I have one laptop with Realtek RTL8723BU wifi card. It runs, but signal is weak (it only works if the router is less than a meter away), and even if it gets signal it's slow and it gets interrupted frequently. In windows it works normally, and with a much stronger signal. I tested it on Ubuntu 18.04.3 and 19.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1846140/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1847706] Re: Deja Dup still tells python-gi (python 2) is required while duplicity is now python3
** Changed in: deja-dup (Ubuntu Eoan) Assignee: (unassigned) => Dimitri John Ledkov (xnox) -- 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/1847706 Title: Deja Dup still tells python-gi (python 2) is required while duplicity is now python3 Status in Déjà Dup: Triaged Status in deja-dup package in Ubuntu: Triaged Status in deja-dup source package in Eoan: Triaged Bug description: Please see the screenshot attached. When running a backup operation against a remote server with SSH, Deja Dup stops by saying "python-gi" package is required. However, duplicity is updated with Python3 now, so it doesn't make sense to install Python 2 based package. The prerequisite check needs to be updated probably with python3-gi instead. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: deja-dup 40.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 11 12:34:15 2019 InstallationDate: Installed on 2019-08-28 (43 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190822) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: deja-dup UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/deja-dup/+bug/1847706/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1847618] Re: im-config ignores input methods other than xim in my current locale
I confirm that replacing LANG with LC_ALL in /usr/share/im-config/xinputrc.common fixes the bug. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to im-config in Ubuntu. https://bugs.launchpad.net/bugs/1847618 Title: im-config ignores input methods other than xim in my current locale Status in im-config package in Ubuntu: In Progress Bug description: I use Ubuntu 16.04.6 LTS. I can not reach other input methods such as ibus, fcitx in my current locale which is LANGUAGE=tr_TR.UTF-8. It's not listed in unity-control-center>Language Support>Keyboard Input Method System. If I launch unity-control-center from terminal which is using different locale "LANGUAGE=en_US.utf8 unity-control-center" then there is no problem, all of the installed input methods are in the list. I also tested "python3 /usr/lib/python3/dist-packages/LanguageSelector/ImConfig.py" it also ignores input methods other than xim and none. If I export "LANGUAGE=en_US.utf8" it lists all the other input methods. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/im-config/+bug/1847618/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1810176] Re: libmtp error could not get object handles
I am experiencing the same issue on Ubuntu Budgie 18.04.3 LTS bug when trying to copy .mp3 files via USB to an encrypted SD inside a Sony Xperia ZX2. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libmtp in Ubuntu. https://bugs.launchpad.net/bugs/1810176 Title: libmtp error could not get object handles Status in libmtp package in Ubuntu: Expired Bug description: When connecting my android galaxy s7 phone via usb, I am unable to access my Music folder, which contains 380 subfolders. The file manager is inactive for a long time, and finally displays the error: Sorry, could not display all the contents of "Music": libmtp error: could not get object handles. Adding one more subfolder on the android side seems to work around the issue, so the issue is related to the number of items. Given this, my issue appears to be a specific example of the issue described in the link below. https://sourceforge.net/p/libmtp/bugs/1808/ Observed in linux mint 18.3 64 bit / ubuntu 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmtp/+bug/1810176/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1847618] Re: im-config ignores input methods other than xim in my current locale
On 2019-10-11 20:13, kenn wrote: > Ironically `LC_MESSAGES=tr_TR.UTF-8 LANGUAGE= im-config -l` prints > full list: > ibus uim scim xim > > but not this `LC_MESSAGES=tr_TR.UTF-8 im-config -l`, this prints: > xim Well, since you have set LC_ALL=C.UTF-8 your case is a bit different compared to what I guessed and described in the merge request. (I would recommend you to drop that setting. It makes no sense on an Ubuntu system, and - as you just noticed - it may cause surprise behavior.) > I confirm that replacing LANG with LC_ALL in > /usr/share/im-config/xinputrc.common fixes the bug. Great, thanks for confirming! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to im-config in Ubuntu. https://bugs.launchpad.net/bugs/1847618 Title: im-config ignores input methods other than xim in my current locale Status in im-config package in Ubuntu: In Progress Bug description: I use Ubuntu 16.04.6 LTS. I can not reach other input methods such as ibus, fcitx in my current locale which is LANGUAGE=tr_TR.UTF-8. It's not listed in unity-control-center>Language Support>Keyboard Input Method System. If I launch unity-control-center from terminal which is using different locale "LANGUAGE=en_US.utf8 unity-control-center" then there is no problem, all of the installed input methods are in the list. I also tested "python3 /usr/lib/python3/dist-packages/LanguageSelector/ImConfig.py" it also ignores input methods other than xim and none. If I export "LANGUAGE=en_US.utf8" it lists all the other input methods. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/im-config/+bug/1847618/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1847069] Re: [snap] Chromium snap starts slowly
I'm not following you. What cannot be corrected? -- 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/1847069 Title: [snap] Chromium snap starts slowly Status in chromium-browser package in Ubuntu: New Bug description: The problem is shown here, https://discourse.ubuntu.com/t/call-for- testing-chromium-browser-deb-to-snap-transition/11179/141 more graphically. Chromium snap takes quite a while to start and doesn't carry the system theme, whereas the chromium-browser folder taken off the snap/chromium starts practically immediately. The libcanberra-gtk3-module is missing inside the snap, and cannot use the module in the system. The Chromium snap is 607.3 MB, while the standalone Chromium is 237.2 MB, taken off the snap. Conclusion on Chromium snap on Ubuntu Eoan; Two bugs and a missing module 1) Starts slowly, 2) Cannot carry the system theme, 3) Doesn't have libcanberra-gtk3-module To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1847069/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1847102] Re: Dragging icons around the dock only fully works once. After that they stick to the mouse pointer.
This bug was fixed in the package gnome-shell-extension-ubuntu-dock - 67ubuntu19.10.1 --- gnome-shell-extension-ubuntu-dock (67ubuntu19.10.1) eoan; urgency=medium [ Marco Trevisan (Treviño) ] * utils: Use GObject.NotImplementedError for such errors * utils: Allow to pass flags to SignalsHandler's * locations: Handle Trash Errors * locations: Ensure volume monitor is destroyed on destruction * dash: Destroy Removables and Trash if disabled * DockManager: Keep a fm1Client reference and destroy it when unneeded * docking: Use CONNNECT_AFTER for mounts changes in docked dash * dash: Remove the show label timeout if actor got destroyed * windowPreviewMenuItem: Disconnect to signals on destroy * cleanup: Replace Mainloop functions with GLib ones * DashSlideContainer: Inherit from St.Bin instead of widget * MyAppIcon: Inherit from Dash.DashIcon (LP: #1846477, #1847102) * debian/control: Depend on gnome-shell 3.34.0 [ Michele Gaio ] * Fix a regression due to variable renaming. * New upstream release (v67). [ Twille ] * add missing translation [ Philip Langdale ] * dash: Add Trash Icon * dash: Add Removable drive/device icons * prefs: Add prefs to toggle showing Trash and Mounted Volumes * appIcons: Implement window tracking for removable devices and trash * fileManager1API: Deduplicate window with related locations in tabs * locations: Fix a remaining use of `nautilus` vs `gio open` [ sicklylife.jp ] * Update Japanese translation. -- Marco Trevisan (Treviño) Wed, 09 Oct 2019 17:30:41 +0200 ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: In Progress => Fix Released -- 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/1847102 Title: Dragging icons around the dock only fully works once. After that they stick to the mouse pointer. Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Bug description: The first time it seemed to work fine, then I stopped being able to drop the icon and had to hit escape. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell-extension-ubuntu-dock 66ubuntu19.10.2 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 7 15:29:20 2019 InstallationDate: Installed on 2019-09-27 (10 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926.1) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1847102/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1847711] Re: Move zsys tags from org.zsys to com.ubuntu.zsys
This bug was fixed in the package ubiquity - 19.10.19 --- ubiquity (19.10.19) eoan; urgency=medium [ Sebastien Bacher ] * Update the 'Skip' string to '_Skip', matching the change done to ubiquity.ui some years ago. The template needs to be manual updated which wasn't done at the time, should make it translatable again (LP: #1731070) [ Mathieu Trudel-Lapierre ] * Update translations from Launchpad. * debian/real-po/templates.pot: update template using debconf-updatepo. [ Jean-Baptiste Lallement ] * Switch zpool sync property back to standard after installation * zfsutils-linux and zfs-initramfs moved to the live task, don't remove them at the end of installation (LP: #1847739) * Change partition types to Solaris Boot and Root types [ Didier Roche ] * As we are not going to own in the end org.zsys, move our identifier tags to com.ubuntu.zsys (LP: #1847711) -- Jean-Baptiste Lallement Fri, 11 Oct 2019 12:05:23 +0200 ** Changed in: ubiquity (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to zsys in Ubuntu. https://bugs.launchpad.net/bugs/1847711 Title: Move zsys tags from org.zsys to com.ubuntu.zsys Status in grub2 package in Ubuntu: Fix Committed Status in grubzfs-testsuite package in Ubuntu: Fix Committed Status in ubiquity package in Ubuntu: Fix Released Status in zfs-linux package in Ubuntu: Fix Released Status in zsys package in Ubuntu: Fix Committed Bug description: As we are not going to own in the end org.zsys, move our identifier tags to com.ubuntu.zsys. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1847711/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1846477] Re: Dragging icons in launcher is slow until shell restarted
This bug was fixed in the package gnome-shell-extension-ubuntu-dock - 67ubuntu19.10.1 --- gnome-shell-extension-ubuntu-dock (67ubuntu19.10.1) eoan; urgency=medium [ Marco Trevisan (Treviño) ] * utils: Use GObject.NotImplementedError for such errors * utils: Allow to pass flags to SignalsHandler's * locations: Handle Trash Errors * locations: Ensure volume monitor is destroyed on destruction * dash: Destroy Removables and Trash if disabled * DockManager: Keep a fm1Client reference and destroy it when unneeded * docking: Use CONNNECT_AFTER for mounts changes in docked dash * dash: Remove the show label timeout if actor got destroyed * windowPreviewMenuItem: Disconnect to signals on destroy * cleanup: Replace Mainloop functions with GLib ones * DashSlideContainer: Inherit from St.Bin instead of widget * MyAppIcon: Inherit from Dash.DashIcon (LP: #1846477, #1847102) * debian/control: Depend on gnome-shell 3.34.0 [ Michele Gaio ] * Fix a regression due to variable renaming. * New upstream release (v67). [ Twille ] * add missing translation [ Philip Langdale ] * dash: Add Trash Icon * dash: Add Removable drive/device icons * prefs: Add prefs to toggle showing Trash and Mounted Volumes * appIcons: Implement window tracking for removable devices and trash * fileManager1API: Deduplicate window with related locations in tabs * locations: Fix a remaining use of `nautilus` vs `gio open` [ sicklylife.jp ] * Update Japanese translation. -- Marco Trevisan (Treviño) Wed, 09 Oct 2019 17:30:41 +0200 ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: Incomplete => Fix Released -- 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/1846477 Title: Dragging icons in launcher is slow until shell restarted Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Bug description: Today I noticed that dragging icons up and down the launcher is painfully slow, to the point where it feels like the desktop has locked up. The gnome-shell process is pegged at 100% while this is happening. Restarting gnome shell (alt+f2, r) makes it faster to refresh the move of the icon but still super slow at drawing the line where you drop it. However, it's super fast on clean boot of a separate machine - x220 (7 years old i7) and another nvidia 960 gpu equipped i7 laptop. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-12.13-generic 5.3.0 Uname: Linux 5.3.0-12-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Oct 3 12:24:48 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-02-04 (605 days ago) InstallationMedia: neon userlts "Xenial" - Build amd64 LIVE Binary 20180202-11:07 RelatedPackageVersions: mutter-common 3.34.0-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-09-19 (13 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1846477/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1847711] Re: Move zsys tags from org.zsys to com.ubuntu.zsys
This bug was fixed in the package zfs-linux - 0.8.1-1ubuntu14 --- zfs-linux (0.8.1-1ubuntu14) eoan; urgency=medium * debian/patches/4000-zsys-support.patch: - As we are not going to own in the end org.zsys, move our identifier tags to com.ubuntu.zsys (LP: #1847711) -- Didier Roche Fri, 11 Oct 2019 08:28:05 +0200 ** Changed in: zfs-linux (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to zsys in Ubuntu. https://bugs.launchpad.net/bugs/1847711 Title: Move zsys tags from org.zsys to com.ubuntu.zsys Status in grub2 package in Ubuntu: Fix Committed Status in grubzfs-testsuite package in Ubuntu: Fix Committed Status in ubiquity package in Ubuntu: Fix Released Status in zfs-linux package in Ubuntu: Fix Released Status in zsys package in Ubuntu: Fix Committed Bug description: As we are not going to own in the end org.zsys, move our identifier tags to com.ubuntu.zsys. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1847711/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 207220]
Dear Christopher M. Penalver, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- 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/207220 Title: [Upstream] cursor does not change to arrow hovering over "X" box Status in LibreOffice: Confirmed Status in OpenOffice: Invalid Status in libreoffice package in Ubuntu: Confirmed Status in openoffice.org package in Ubuntu: Won't Fix Bug description: Binary package hint: openoffice.org 1) lsb_release -rd Description: Ubuntu 11.04 Release: 11.04 2) apt-cache policy libreoffice-writer libreoffice-writer: Installed: 1:3.3.2-1ubuntu5 Candidate: 1:3.3.2-1ubuntu5 Version table: *** 1:3.3.2-1ubuntu5 0 500 http://us.archive.ubuntu.com/ubuntu/ natty-updates/main i386 Packages 500 http://us.archive.ubuntu.com/ubuntu/ natty-proposed/main i386 Packages 100 /var/lib/dpkg/status 1:3.3.2-1ubuntu4 0 500 http://us.archive.ubuntu.com/ubuntu/ natty/main i386 Packages 3) What is expected to happen in LibreOffice Writer via the Terminal: cd ~/Desktop && wget https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/207220/+attachment/2134007/+files/Unbenannt%201.doc && lowriter -nologo Unbenannt\ 1.doc hover ones mouse cursor over the checkbox and it changes from the I to an arrow. 4) What happens instead is it remains an I. Original Reporter Comments: Ubuntu hardy beta, OOo 2.4.0-rc2-1ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/207220/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1846776] Re: Renaming a desktop item causes the shell to hang
This bug was fixed in the package gnome-shell-extension-desktop-icons - 19.10.2-1 --- gnome-shell-extension-desktop-icons (19.10.2-1) unstable; urgency=medium * New upstream release + createFolderDialog: Use native GObject for new Shell 3.34 versions + desktopGrid: Derive the RenamePoup from PopupMenu + desktopGrid: Don't emit deprecation warnings when using native objects + desktopGrid.js: fix rename button + desktopGrid: Open the rename popup only when item menu is closed (LP: #1846776) + desktopGrid: Properly inherit Placeholder from a GObject class + desktopGrid: Use default upstream styling for rename popup + General: Fix thumbnails not centered + general: Pass the actor to PopupManuManager constructor in new shell + metadata.json Compatibility only with Gnome Shell 3.34 * debian/patches: Remove patches as now upstream gnome-shell-extension-desktop-icons (19.01.4-2) unstable; urgency=medium * Build-Depend on debhelper-comapt 12 and drop debian/compat * Build-Depend on dh-sequence-gnome instead of gnome-pkg-tools * Bump Standards-Version to 4.4.0 * Release to unstable -- Iain Lane Thu, 10 Oct 2019 09:51:36 +0100 ** Changed in: gnome-shell-extension-desktop-icons (Ubuntu Eoan) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1846776 Title: Renaming a desktop item causes the shell to hang Status in gnome-shell-extension-desktop-icons: Fix Released Status in gnome-shell-extension-desktop-icons package in Ubuntu: Fix Released Status in gnome-shell-extension-desktop-icons source package in Eoan: Fix Released Bug description: Right click on a desktop icon and rename it: - The shell will hang and there's no way to recover it To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1846776/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1844422] Re: WPA3-SAE support
This bug was fixed in the package network-manager - 1.20.4-2ubuntu2 --- network-manager (1.20.4-2ubuntu2) eoan; urgency=medium * debian/patches/git_wpa_sae.patch: - PMF can be used with SAE, allow it, fixes WPA3 handling (lp: #1844422) -- Sebastien Bacher Fri, 11 Oct 2019 00:06:27 +0200 ** Changed in: network-manager (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1844422 Title: WPA3-SAE support Status in gnome-shell package in Ubuntu: Fix Released Status in network-manager package in Ubuntu: Fix Released Bug description: After some user feedback WPA3 support for NetworkManager has been finalized upstream: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/e1608030c6614d8dfd86122e9df81fdaad9453c9 https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/84a86ce55f1e70cb32217d2c74242ff848db8cd7 https://gitlab.freedesktop.org/NetworkManager/NetworkManager/merge_requests/276/diffs?commit_id=8d4497088fff562773b9c05260e810833bfc9c85 At this time NetworkManager will not associate with Wifi-networks using WPA3. Tested using Ubuntu Ubuntu Eoan Ermine [development branch] with NetworkManager 1.20.2-1ubuntu1 and WPA_Supplicant 2:2.9-1ubuntu1. It would be great if the aforementioned commits where backported to Eoan before release, so that Eoan based systems will associate with WiFi-networks using WPA3. == Update 09-10-2019: So it has come to my attention that NetworkManager needs one additional commit backported from upstream to make WPA3-SAE work: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/e36c297fd8c6b1b57cd120739cc5ee8eab57aa08 Without this latest commit connecting to WPA3-personal networks will still fail because of a lack of 802.11w support in the network-manager settings. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1844422/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1847706] Re: Deja Dup still tells python-gi (python 2) is required while duplicity is now python3
This bug was fixed in the package deja-dup - 40.1-1ubuntu2 --- deja-dup (40.1-1ubuntu2) eoan; urgency=medium * Bump dynamic dependenices to python3. LP: #1847706 -- Dimitri John Ledkov Fri, 11 Oct 2019 19:23:42 +0100 ** Changed in: deja-dup (Ubuntu Eoan) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to deja-dup in Ubuntu. https://bugs.launchpad.net/bugs/1847706 Title: Deja Dup still tells python-gi (python 2) is required while duplicity is now python3 Status in Déjà Dup: Triaged Status in deja-dup package in Ubuntu: Fix Released Status in deja-dup source package in Eoan: Fix Released Bug description: Please see the screenshot attached. When running a backup operation against a remote server with SSH, Deja Dup stops by saying "python-gi" package is required. However, duplicity is updated with Python3 now, so it doesn't make sense to install Python 2 based package. The prerequisite check needs to be updated probably with python3-gi instead. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: deja-dup 40.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 11 12:34:15 2019 InstallationDate: Installed on 2019-08-28 (43 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190822) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: deja-dup UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/deja-dup/+bug/1847706/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1847829] [NEW] Three finger tap to middle click stopped working
Public bug reported: I haven't expereinced this before, though a google search shows complaints from at least 2016. Three fingers results in a right-click now for whatever reason. I have the appropriate settings enabled in KDE (I haven't changed them). Middle click works sometimes after restarting the device via xinput, but this is very rare. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xserver-xorg-input-libinput 0.28.2-2 ProcVersionSignature: Ubuntu 5.0.0-31.33-generic 5.0.21 Uname: Linux 5.0.0-31-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CurrentDesktop: KDE Date: Sat Oct 12 03:40:48 2019 DistUpgraded: 2019-04-27 18:56:54,539 DEBUG new topwidget None DistroCodename: disco DistroVariant: ubuntu InstallationDate: Installed on 2018-11-15 (330 days ago) InstallationMedia: Kubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) MachineType: LENOVO 20AQCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-31-generic root=/dev/mapper/kubuntu--vg-root ro psmouse.synaptics_intertouch=0 quiet splash vt.handoff=1 SourcePackage: xserver-xorg-input-libinput UpgradeStatus: Upgraded to disco on 2019-04-27 (167 days ago) dmi.bios.date: 03/20/2018 dmi.bios.vendor: LENOVO dmi.bios.version: GJET98WW (2.48 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AQCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 PRO dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGJET98WW(2.48):bd03/20/2018:svnLENOVO:pn20AQCTO1WW:pvrThinkPadT440s:rvnLENOVO:rn20AQCTO1WW:rvrSDK0E50510PRO:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T440s dmi.product.name: 20AQCTO1WW dmi.product.sku: LENOVO_MT_20AQ_BU_Think_FM_ThinkPad T440s dmi.product.version: ThinkPad T440s dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~19.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~19.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xserver-xorg-input-libinput (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu. https://bugs.launchpad.net/bugs/1847829 Title: Three finger tap to middle click stopped working Status in xserver-xorg-input-libinput package in Ubuntu: New Bug description: I haven't expereinced this before, though a google search shows complaints from at least 2016. Three fingers results in a right-click now for whatever reason. I have the appropriate settings enabled in KDE (I haven't changed them). Middle click works sometimes after restarting the device via xinput, but this is very rare. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xserver-xorg-input-libinput 0.28.2-2 ProcVersionSignature: Ubuntu 5.0.0-31.33-generic 5.0.21 Uname: Linux 5.0.0-31-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CurrentDesktop: KDE Date: Sat Oct 12 03:40:48 2019 DistUpgraded: 2019-04-27 18:56:54,539 DEBUG new topwidget None DistroCodename: disco DistroVariant: ubuntu InstallationDate: Installed on 2018-11-15 (330 days ago) InstallationMedia: Kubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) MachineType: LENOVO 20AQCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-31-generic root=/dev/mapper/kubuntu--vg-root ro psmouse.synaptics_intertouch=0 quiet splash vt.handoff=1 SourcePackage: xserver-xorg-input-libinput UpgradeStatus: Upgraded to disco on 2019-04-27 (167 days ago) dmi.bios.date: 03/20/2018 dmi.bios.vendor: LENOVO dmi.bios.version: GJET98WW (2.48 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AQCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 PRO dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGJET98WW(2.48):bd03/20/2018:svnLENOVO:pn20AQCTO1WW:pvrThinkPadT440s:rvnLENOVO:rn20AQCTO1WW:rvrSDK0E50510PRO:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T440s dmi.product.name: 20AQCTO1WW dmi.product.sku: LENOVO_MT_20AQ_BU_Think_FM_ThinkPad T440s dmi.product.version: ThinkPad T440s dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4
[Desktop-packages] [Bug 1847675] Re: Lenovo thinkpad T440s Trackpoint doesn't work properly
I don't know if these are related: bug/1836237 bug/1847829 (probably not, but it's possible that some touchpad drivers are just bad. Note that the first one affects every input device, including any mouse you're using. Inputs stop working so often that I have a hotkey to disable/enable them - this gets them working again. Otherwise I just wouldn't be able to use the computer). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu. https://bugs.launchpad.net/bugs/1847675 Title: Lenovo thinkpad T440s Trackpoint doesn't work properly Status in libinput package in Ubuntu: New Status in xserver-xorg-input-libinput package in Ubuntu: New Bug description: 1. middle click scroll doesn't work at all. Holding down the the middle scroll button while pushing the trackpoint results in the cursor freezing for a couple seconds. 2. Trackpoint motion is extremely slow. 3. Right-click doesn't work. I hadn't observed these problems with ubuntu 18.04. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xserver-xorg-input-libinput 0.28.2-2 ProcVersionSignature: Ubuntu 5.0.0-29.31-generic 5.0.21 Uname: Linux 5.0.0-29-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CurrentDesktop: KDE Date: Fri Oct 11 00:34:54 2019 DistUpgraded: 2019-04-27 18:56:54,539 DEBUG new topwidget None DistroCodename: disco DistroVariant: ubuntu InstallationDate: Installed on 2018-11-15 (329 days ago) InstallationMedia: Kubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) MachineType: LENOVO 20AQCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-29-generic root=/dev/mapper/kubuntu--vg-root ro psmouse.synaptics_intertouch=0 quiet splash vt.handoff=1 SourcePackage: xserver-xorg-input-libinput UpgradeStatus: Upgraded to disco on 2019-04-27 (166 days ago) dmi.bios.date: 03/20/2018 dmi.bios.vendor: LENOVO dmi.bios.version: GJET98WW (2.48 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AQCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 PRO dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGJET98WW(2.48):bd03/20/2018:svnLENOVO:pn20AQCTO1WW:pvrThinkPadT440s:rvnLENOVO:rn20AQCTO1WW:rvrSDK0E50510PRO:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T440s dmi.product.name: 20AQCTO1WW dmi.product.sku: LENOVO_MT_20AQ_BU_Think_FM_ThinkPad T440s dmi.product.version: ThinkPad T440s dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~19.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~19.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1847675/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1754671] Re: Full-tunnel VPN DNS leakage regression
This fix was first included in upstream 1.12.0, so this was actually fixed in Cosmic with network-manager 1.12.2-0ubuntu3 ** Changed in: network-manager (Ubuntu Cosmic) Importance: Undecided => High ** Changed in: network-manager (Ubuntu Cosmic) Status: Won't Fix => Fix Released -- 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/1754671 Title: Full-tunnel VPN DNS leakage regression Status in NetworkManager: Confirmed Status in network-manager package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in network-manager source package in Xenial: Confirmed Status in systemd source package in Xenial: Invalid Status in network-manager source package in Bionic: In Progress Status in systemd source package in Bionic: Fix Released Status in network-manager source package in Cosmic: Fix Released Status in systemd source package in Cosmic: Fix Released Bug description: [Impact] When using a VPN the DNS requests might still be sent to a DNS server outside the VPN when they should not [Test case] 1) Set up a VPN with split tunneling: a) Configure VPN normally (set up remote host, any ports and options needed for the VPN to work) b) Under the IPv4 tab: enable "Use this connection only for the resources on its network". c) Under the IPv6 tab: enable "Use this connection only for the resources on its network". 2) Connect to the VPN. 3) Run 'systemd-resolve --status'; note the DNS servers configured: a) For the VPN; under a separate link (probably tun0), note down the IP of the DNS server(s). Also note the name of the interface (link). b) For the "main" connection; under the link for your ethernet or wireless devices (wl*, en*, whatever it may be), note down the IP of the DNS server(s). Also note the name of the interface (link). 4) In a separate terminal, run 'sudo tcpdump -ni port 53'; let it run. 5) In a separate terminal, run 'sudo tcpdump -ni port 53'; let it run. 6) In yet another terminal, issue name resolution requests using dig: a) For a name known to be reachable via the public network: 'dig www.yahoo.com' b) For a name known to be reachable only via the VPN: 'dig ' 7) Check the output of each terminal running tcpdump. When requesting the public name, traffic can go through either. When requesting the "private" name (behind the VPN), traffic should only be going through the interface for the VPN. Additionally, ensure the IP receiving the requests for the VPN name is indeed the IP address noted above for the VPN's DNS server. If you see no traffic showing in tcpdump output when requesting a name, it may be because it is cached by systemd-resolved. Use a different name you have not tried before. [Regression potential] The code change the handling of DNS servers when using a VPN, we should check that name resolution still work whne using a VPN in different configurations - In 16.04 the NetworkManager package used to carry this patch: http://bazaar.launchpad.net/~network-manager/network-manager/ubuntu/view/head:/debian/patches/Filter-DNS-servers-to-add-to-dnsmasq-based-on-availa.patch It fixed the DNS setup so that when I'm on the VPN, I am not sending unencrypted DNS queries to the (potentially hostile) local nameservers. This patch disappeared in an update. I think it was present in 1.2.2-0ubuntu0.16.04.4 but was dropped some time later. This security bug exists upstream too: https://bugzilla.gnome.org/show_bug.cgi?id=746422 It's not a *regression* there though, as they didn't fix it yet (unfortunately!) To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1754671/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1489632] Re: gedit fails to display line with > 1000000 characters
The bug is reproducible on my Ubuntu 18.04.3 system with gedit 3.28.1-1ubuntu1.2 -- 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/1489632 Title: gedit fails to display line with > 100 characters Status in gedit package in Ubuntu: Confirmed Bug description: steps to reproduce: 1. start `gedit` 2. produce a line with > 100 characters, e.g. with `ipython` in `gnome-terminal` where you can run `"1" * 100` and select all output and copy it 3. paste into `gedit` Parts of the line seems to be rendered over other parts of the line. This doesn't occur with 10 characters. See attached screenshot for an example. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: gedit 3.10.4-0ubuntu10 Uname: Linux 4.1.4-040104-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.3 Architecture: amd64 CurrentDesktop: Unity Date: Thu Aug 27 23:56:50 2015 InstallationDate: Installed on 2015-06-08 (80 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: gedit UpgradeStatus: Upgraded to vivid on 2015-06-09 (79 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1489632/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp