[Desktop-packages] [Bug 1520033] Re: ftbfs on s390x
so can someone with permissions please drop support for s390x, so that Mono builds again for Ubuntu? Or anyone going to try the settings to make it build again for s390x? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mono in Ubuntu. https://bugs.launchpad.net/bugs/1520033 Title: ftbfs on s390x Status in mono package in Ubuntu: Confirmed Bug description: ftbfs on s390x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mono/+bug/1520033/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1846941] Re: Since upgrading to Eoan Ermine the screen doesn't dim progressively before turning off and locking the PC, but at once.
** Changed in: gnome-shell Status: Unknown => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1846941 Title: Since upgrading to Eoan Ermine the screen doesn't dim progressively before turning off and locking the PC, but at once. Status in GNOME Shell: New Status in gnome-shell package in Ubuntu: Confirmed Bug description: It wasn't behaving that way in Disco. Not sure if this issue belongs to X.org, but as that was the place for suspend/resume, i decided to place this bug here. If it's the wrong package, please help me in finding the correct one. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1) ApportVersion: 2.20.11-0ubuntu7 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' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Oct 6 13:46:25 2019 DistUpgraded: 2019-09-28 01:59:57,153 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] UHD Graphics 620 [1025:1193] Subsystem: Acer Incorporated [ALI] GP108M [GeForce MX150] [1025:119a] InstallationDate: Installed on 2019-07-23 (74 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04f2:b5f7 Chicony Electronics Co., Ltd HD WebCam Bus 001 Device 003: ID 8087:0aa7 Intel Corp. Bus 001 Device 002: ID :0538 USB OPTICAL MOUSE Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire A515-51G ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-13-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to eoan on 2019-09-27 (8 days ago) dmi.bios.date: 01/03/2019 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.02 dmi.board.asset.tag: Type2 - Board Serial Number dmi.board.name: Charmander_KL dmi.board.vendor: KBL dmi.board.version: V2.02 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.02 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.02:bd01/03/2019:svnAcer:pnAspireA515-51G:pvrV2.02:rvnKBL:rnCharmander_KL:rvrV2.02:cvnAcer:ct10:cvrV2.02: dmi.product.family: Aspire 5 dmi.product.name: Aspire A515-51G dmi.product.sku: dmi.product.version: V2.02 dmi.sys.vendor: Acer 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 19.2.0-1ubuntu2 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20190820-0ubuntu3 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 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1846941/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1846988] Re: [Audio playback] No 'Speaker - Built-in Audio'
Please test mainline kernel v5.3, let us see if this kernel works or not. https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.3/ -- 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/1846988 Title: [Audio playback] No 'Speaker - Built-in Audio' Status in alsa-driver package in Ubuntu: New Bug description: Installation details: Ubuntu 19.04 alsa-base: Installed: 1.0.25+dfsg-0ubuntu5 Candidate: 1.0.25+dfsg-0ubuntu5 Version table: *** 1.0.25+dfsg-0ubuntu5 500 500 http://au.archive.ubuntu.com/ubuntu disco/main amd64 Packages 500 http://au.archive.ubuntu.com/ubuntu disco/main i386 Packages 100 /var/lib/dpkg/status Expected behaviour: Expected a 'Speaker - Built-in Audio' option in my Audio settings. Actual behaviour: Seems the 'Speakers - Built-in Audio' playback device is not available in my settings. Instead there is 'Headphones - Built-in Audio' which obviously shouldn't exist. When actual headphones are attached, the do not playback either. Playback only works when connected via bluetooth or HDMI, but there are extra options, that do not work... not sure what it is detecting, as there is only one HDMI output. I followed this document to debug myself: https://help.ubuntu.com/community/SoundTroubleshooting. However, the second step works fine when connected via bluetooth or HDMI, as stated before. I have tried booting the Live USB, and audio works perfectly fine here, so this is not a hardware issue. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-29.31-generic 5.0.21 Uname: Linux 5.0.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: lawrence 2033 F pulseaudio /dev/snd/controlC0: lawrence 2033 F pulseaudio lawrence 23649 F alsamixer /dev/snd/pcmC0D0c: lawrence 2033 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Oct 7 09:27:18 2019 InstallationDate: Installed on 2019-09-07 (29 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: HDA NVidia - HDA NVidia Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: lawrence 2033 F pulseaudio /dev/snd/controlC0: lawrence 2033 F pulseaudio lawrence 23649 F alsamixer Symptom_Type: No sound at all Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/10/2019 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.06TMB dmi.board.asset.tag: Tag 12345 dmi.board.name: P95_96_97Ex,Rx dmi.board.vendor: IT Channel Pty Ltd dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: IT Channel Pty Ltd dmi.chassis.version: N/A dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.06TMB:bd04/10/2019:svnITChannelPtyLtd:pnP95_96_97Ex,Rx:pvrNotApplicable:rvnITChannelPtyLtd:rnP95_96_97Ex,Rx:rvrNotApplicable:cvnITChannelPtyLtd:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: P95_96_97Ex,Rx dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: IT Channel Pty Ltd mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-09-07T11:50:26.934452 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1846988/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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
Do you mean the you can't hear sound from headphone or lineout jack? -- 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 1844944] Re: Ubuntu 19.10 switching users broken
Confirmed with Intel graphics too. ** Tags removed: nouveau ** Tags added: rls-ee-incoming -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1844944 Title: Ubuntu 19.10 switching users broken Status in gdm3 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: I've performed an upgrade from Ubuntu 19.04 to 19.10 5 days ago by running the command "sudo do-release-upgrade". The upgrade went well, without errors. I've installed all updates to date (22 sept 2019). One thing seems broken since the upgrade to 19.10: it is not possible to switch users when using the Nouveau driver. Prerequisites: - Use Ubuntu 19.10 - You need at least 2 users (e.g. user1 and user2) - The Nouveau drivers must be used Step to reproduce: - Start your computer - At the graphical login prompt, log in with user1: user1 is able to log in, its desktop is shown - While logged into the desktop of user1, choose "Switch user" - When back at the user selection screen, choose the profile of user2 - Provide the password for user2 and attempt log in RESULT: the desktop of user2 is never shown. Instead, the lock screen is shown. After pressing [Enter] to hide the lock screen, the login prompt for user1 is displayed. On that screen, it is possible to press "Log in as another user" and provide the password for user2 again. A login attempt results again in the lock screen being displayed. it is never possible to login in as user2. NOTE 1: the same happens when user2 was the first to log in after a reboot of the system. User2 is able to log in, and user1 is then stuck in a login loop. NOTE 2: this bug doesn't happen when the proprietary NVidia driver is used (the version which can be installed via the Software & updates screen, version 340.107). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1844944/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1844944] Re: Ubuntu 19.10 switching users broken
** Summary changed: - Ubuntu 19.10 switching users broken with Nouveau driver + Ubuntu 19.10 switching users broken -- 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/1844944 Title: Ubuntu 19.10 switching users broken Status in gdm3 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: I've performed an upgrade from Ubuntu 19.04 to 19.10 5 days ago by running the command "sudo do-release-upgrade". The upgrade went well, without errors. I've installed all updates to date (22 sept 2019). One thing seems broken since the upgrade to 19.10: it is not possible to switch users when using the Nouveau driver. Prerequisites: - Use Ubuntu 19.10 - You need at least 2 users (e.g. user1 and user2) - The Nouveau drivers must be used Step to reproduce: - Start your computer - At the graphical login prompt, log in with user1: user1 is able to log in, its desktop is shown - While logged into the desktop of user1, choose "Switch user" - When back at the user selection screen, choose the profile of user2 - Provide the password for user2 and attempt log in RESULT: the desktop of user2 is never shown. Instead, the lock screen is shown. After pressing [Enter] to hide the lock screen, the login prompt for user1 is displayed. On that screen, it is possible to press "Log in as another user" and provide the password for user2 again. A login attempt results again in the lock screen being displayed. it is never possible to login in as user2. NOTE 1: the same happens when user2 was the first to log in after a reboot of the system. User2 is able to log in, and user1 is then stuck in a login loop. NOTE 2: this bug doesn't happen when the proprietary NVidia driver is used (the version which can be installed via the Software & updates screen, version 340.107). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1844944/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1844944] Re: Ubuntu 19.10 switching users broken
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1844944 Title: Ubuntu 19.10 switching users broken Status in gdm3 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: I've performed an upgrade from Ubuntu 19.04 to 19.10 5 days ago by running the command "sudo do-release-upgrade". The upgrade went well, without errors. I've installed all updates to date (22 sept 2019). One thing seems broken since the upgrade to 19.10: it is not possible to switch users when using the Nouveau driver. Prerequisites: - Use Ubuntu 19.10 - You need at least 2 users (e.g. user1 and user2) - The Nouveau drivers must be used Step to reproduce: - Start your computer - At the graphical login prompt, log in with user1: user1 is able to log in, its desktop is shown - While logged into the desktop of user1, choose "Switch user" - When back at the user selection screen, choose the profile of user2 - Provide the password for user2 and attempt log in RESULT: the desktop of user2 is never shown. Instead, the lock screen is shown. After pressing [Enter] to hide the lock screen, the login prompt for user1 is displayed. On that screen, it is possible to press "Log in as another user" and provide the password for user2 again. A login attempt results again in the lock screen being displayed. it is never possible to login in as user2. NOTE 1: the same happens when user2 was the first to log in after a reboot of the system. User2 is able to log in, and user1 is then stuck in a login loop. NOTE 2: this bug doesn't happen when the proprietary NVidia driver is used (the version which can be installed via the Software & updates screen, version 340.107). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1844944/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1844944] Re: Ubuntu 19.10 switching users broken
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mutter (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/1844944 Title: Ubuntu 19.10 switching users broken Status in gdm3 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: I've performed an upgrade from Ubuntu 19.04 to 19.10 5 days ago by running the command "sudo do-release-upgrade". The upgrade went well, without errors. I've installed all updates to date (22 sept 2019). One thing seems broken since the upgrade to 19.10: it is not possible to switch users when using the Nouveau driver. Prerequisites: - Use Ubuntu 19.10 - You need at least 2 users (e.g. user1 and user2) - The Nouveau drivers must be used Step to reproduce: - Start your computer - At the graphical login prompt, log in with user1: user1 is able to log in, its desktop is shown - While logged into the desktop of user1, choose "Switch user" - When back at the user selection screen, choose the profile of user2 - Provide the password for user2 and attempt log in RESULT: the desktop of user2 is never shown. Instead, the lock screen is shown. After pressing [Enter] to hide the lock screen, the login prompt for user1 is displayed. On that screen, it is possible to press "Log in as another user" and provide the password for user2 again. A login attempt results again in the lock screen being displayed. it is never possible to login in as user2. NOTE 1: the same happens when user2 was the first to log in after a reboot of the system. User2 is able to log in, and user1 is then stuck in a login loop. NOTE 2: this bug doesn't happen when the proprietary NVidia driver is used (the version which can be installed via the Software & updates screen, version 340.107). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1844944/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1844944] Re: Ubuntu 19.10 switching users broken
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gdm3 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1844944 Title: Ubuntu 19.10 switching users broken Status in gdm3 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: I've performed an upgrade from Ubuntu 19.04 to 19.10 5 days ago by running the command "sudo do-release-upgrade". The upgrade went well, without errors. I've installed all updates to date (22 sept 2019). One thing seems broken since the upgrade to 19.10: it is not possible to switch users when using the Nouveau driver. Prerequisites: - Use Ubuntu 19.10 - You need at least 2 users (e.g. user1 and user2) - The Nouveau drivers must be used Step to reproduce: - Start your computer - At the graphical login prompt, log in with user1: user1 is able to log in, its desktop is shown - While logged into the desktop of user1, choose "Switch user" - When back at the user selection screen, choose the profile of user2 - Provide the password for user2 and attempt log in RESULT: the desktop of user2 is never shown. Instead, the lock screen is shown. After pressing [Enter] to hide the lock screen, the login prompt for user1 is displayed. On that screen, it is possible to press "Log in as another user" and provide the password for user2 again. A login attempt results again in the lock screen being displayed. it is never possible to login in as user2. NOTE 1: the same happens when user2 was the first to log in after a reboot of the system. User2 is able to log in, and user1 is then stuck in a login loop. NOTE 2: this bug doesn't happen when the proprietary NVidia driver is used (the version which can be installed via the Software & updates screen, version 340.107). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1844944/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1847008] Re: Xorg crashed with SIGABRT in OsAbort()
*** This bug is a duplicate of bug 1546541 *** https://bugs.launchpad.net/bugs/1546541 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1546541, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1847008/+attachment/5294948/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1847008/+attachment/5294951/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1847008/+attachment/5294960/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1847008/+attachment/5294962/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1847008/+attachment/5294963/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1847008/+attachment/5294964/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1847008/+attachment/5294965/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1546541 Xorg crashed with SIGABRT in OsAbort() from AbortServer() from FatalError() from CreateWellKnownSockets() ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1847008 Title: Xorg crashed with SIGABRT in OsAbort() Status in xorg-server package in Ubuntu: New Bug description: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1846807 https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1847007 ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: xserver-xorg-core 2:1.20.5+git20190820-0ubuntu3 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 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CrashCounter: 1 Date: Mon Oct 7 01:59:27 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu ExecutablePath: /usr/lib/xorg/Xorg ExecutableTimestamp: 1567693411 GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:225c] InstallationDate: Installed on 2019-01-22 (256 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190122) MachineType: LENOVO 20KH007UVA ProcCmdline: /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch ProcCwd: / ProcEnviron: PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-13-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: xorg-server StacktraceTop: OsAbort () ?? () FatalError () CreateWellKnownSockets () ?? () UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 09/02/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET66W (1.41 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KH007UVA dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN23ET66W(1.41):bd09/02/2019:svnLENOVO:pn20KH007UVA:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KH007UVA:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 6th dmi.product.name: 20KH007UVA dmi.product.sku: LENOVO_MT_20KH_BU_Think_FM_ThinkPad X1 Carbon 6th dmi.product.version: ThinkPad X1 Carbon 6th dmi.sys.vendor: LENOVO separator: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99+git1909241510.0c4275~oibaf~d version.libgl1-mesa-dri: libgl1-mesa-dri 19.3~git1909260954.031752~oibaf~d version.libgl1-mesa-glx: libgl1-mesa-glx 19.3~git1909260954.031752~oibaf~d version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20190820-0ubuntu3 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 To manage
[Desktop-packages] [Bug 1844944] Re: Ubuntu 19.10 switching users broken with Nouveau driver
I wonder if this bug really is Nouveau specific, or if it's just KMS- specific. -- 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/1844944 Title: Ubuntu 19.10 switching users broken with Nouveau driver Status in gdm3 package in Ubuntu: New Status in gnome-shell package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: I've performed an upgrade from Ubuntu 19.04 to 19.10 5 days ago by running the command "sudo do-release-upgrade". The upgrade went well, without errors. I've installed all updates to date (22 sept 2019). One thing seems broken since the upgrade to 19.10: it is not possible to switch users when using the Nouveau driver. Prerequisites: - Use Ubuntu 19.10 - You need at least 2 users (e.g. user1 and user2) - The Nouveau drivers must be used Step to reproduce: - Start your computer - At the graphical login prompt, log in with user1: user1 is able to log in, its desktop is shown - While logged into the desktop of user1, choose "Switch user" - When back at the user selection screen, choose the profile of user2 - Provide the password for user2 and attempt log in RESULT: the desktop of user2 is never shown. Instead, the lock screen is shown. After pressing [Enter] to hide the lock screen, the login prompt for user1 is displayed. On that screen, it is possible to press "Log in as another user" and provide the password for user2 again. A login attempt results again in the lock screen being displayed. it is never possible to login in as user2. NOTE 1: the same happens when user2 was the first to log in after a reboot of the system. User2 is able to log in, and user1 is then stuck in a login loop. NOTE 2: this bug doesn't happen when the proprietary NVidia driver is used (the version which can be installed via the Software & updates screen, version 340.107). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1844944/+subscriptions -- Mailing list: https://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 1846807] Re: Xorg crash
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1847008 On Mon, Oct 7, 2019 at 9:57 AM Ko Ko Ye` wrote: > https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1847007 > > On Mon, Oct 7, 2019 at 9:30 AM Daniel van Vugt < > daniel.van.v...@canonical.com> wrote: > >> Thank you for taking the time to report this bug and helping to make >> Ubuntu better. It sounds like some part of the system has crashed. To >> help us find the cause of the crash please follow these steps: >> >> 1. Look in /var/crash for crash files and if found run: >> ubuntu-bug YOURFILE.crash >> Then tell us the ID of the newly-created bug. >> >> 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where >> ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. >> Do you find any links to recent problems on that page? If so then please >> send the links to us. >> >> 3. If step 2 also failed then apply the workaround from bug 994921, >> reboot, reproduce the crash, and retry step 1. >> >> Please take care to avoid attaching .crash files to bugs as we are >> unable to process them as file attachments. It would also be a security >> risk for yourself. >> >> ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) >> >> ** Changed in: xorg-server (Ubuntu) >>Status: New => Incomplete >> >> -- >> You received this bug notification because you are subscribed to the bug >> report. >> https://bugs.launchpad.net/bugs/1846807 >> >> Title: >> Xorg crash >> >> Status in xorg-server package in Ubuntu: >> Incomplete >> >> Bug description: >> When upgrade (include firmware update) >> >> can't see login screen >> when i use startx >> looping login screen >> >> Upgrade to 19.10 and install lightdm >> still again >> >> when i use wayland is ok. >> other gnome, gnome-classic, ubuntu is looping >> >> ProblemType: Bug >> DistroRelease: Ubuntu 19.10 >> Package: xorg 1:7.7+19ubuntu12 >> 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 >> BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' >> CompizPlugins: No value set for >> `/apps/compiz-1/general/screen0/options/active_plugins' >> CompositorRunning: None >> CurrentDesktop: ubuntu:GNOME >> Date: Sat Oct 5 00:50:39 2019 >> DistUpgraded: Fresh install >> DistroCodename: eoan >> DistroVariant: ubuntu >> GraphicsCard: >>Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 >> [VGA controller]) >> Subsystem: Lenovo UHD Graphics 620 [17aa:225c] >> InstallationDate: Installed on 2019-01-22 (254 days ago) >> InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190122) >> MachineType: LENOVO 20KH007UVA >> ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-13-generic >> root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 >> SourcePackage: xorg >> Symptom: display >> Title: Xorg crash >> UpgradeStatus: No upgrade log present (probably fresh install) >> dmi.bios.date: 09/02/2019 >> dmi.bios.vendor: LENOVO >> dmi.bios.version: N23ET66W (1.41 ) >> dmi.board.asset.tag: Not Available >> dmi.board.name: 20KH007UVA >> dmi.board.vendor: LENOVO >> dmi.board.version: Not Defined >> dmi.chassis.asset.tag: No Asset Information >> dmi.chassis.type: 10 >> dmi.chassis.vendor: LENOVO >> dmi.chassis.version: None >> dmi.modalias: >> dmi:bvnLENOVO:bvrN23ET66W(1.41):bd09/02/2019:svnLENOVO:pn20KH007UVA:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KH007UVA:rvrNotDefined:cvnLENOVO:ct10:cvrNone: >> dmi.product.family: ThinkPad X1 Carbon 6th >> dmi.product.name: 20KH007UVA >> dmi.product.sku: LENOVO_MT_20KH_BU_Think_FM_ThinkPad X1 Carbon 6th >> dmi.product.version: ThinkPad X1 Carbon 6th >> dmi.sys.vendor: LENOVO >> version.compiz: compiz N/A >> version.libdrm2: libdrm2 2.4.99+git1909241510.0c4275~oibaf~d >> version.libgl1-mesa-dri: libgl1-mesa-dri >> 19.3~git1909260954.031752~oibaf~d >> version.libgl1-mesa-glx: libgl1-mesa-glx >> 19.3~git1909260954.031752~oibaf~d >> version.xserver-xorg-core: xserver-xorg-core >> 2:1.20.5+git20190820-0ubuntu3 >> version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A >> version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1 >> 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 >> >> To manage notifications about this bug go to: >> >> https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1846807/+subscriptions >> > > > -- > > with regards *Ko Ko Ye`* > > +95 97989 22022 > +95 94500 22022 > +95 9731 47907 > kokoye2...@gmail.com > kokoye2...@ubuntu.com > > skype: kokoye2007 > jitsi: kokoye2007 > > http://ubuntu-mm.net > http://wiki.ubuntu.com/kokoye2007 > http://wiki.ubuntu.com/MyanmarTeam http://loco.ubuntu.com/teams/ubuntu-mm > -- with regards
[Desktop-packages] [Bug 1846955] Re: Gnome crashes on adding system title bars to Chrome under Wayland in EOAN
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Tags added: eoan ** 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/1846955 Title: Gnome crashes on adding system title bars to Chrome under Wayland in EOAN Status in gnome-shell package in Ubuntu: Incomplete Bug description: To reproduce: 1. Open Chrome under Wayland session in 19.10 beta 2. Maximize Chrome 3. Right click on empty space beside tabs and from the menu select "Use system titlebar and borders" Chrome immediately crashes and gnome begins to become less and less responsive until it finally freezes. Does not occur when doing the equivalent in Firefox BTW - Gnome is super responsive in Eoan! Keep up the good work. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1846955/+subscriptions -- Mailing list: https://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 1846807] Re: Xorg crash
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1847007 On Mon, Oct 7, 2019 at 9:30 AM Daniel van Vugt < daniel.van.v...@canonical.com> wrote: > Thank you for taking the time to report this bug and helping to make > Ubuntu better. It sounds like some part of the system has crashed. To > help us find the cause of the crash please follow these steps: > > 1. Look in /var/crash for crash files and if found run: > ubuntu-bug YOURFILE.crash > Then tell us the ID of the newly-created bug. > > 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where > ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. > Do you find any links to recent problems on that page? If so then please > send the links to us. > > 3. If step 2 also failed then apply the workaround from bug 994921, > reboot, reproduce the crash, and retry step 1. > > Please take care to avoid attaching .crash files to bugs as we are > unable to process them as file attachments. It would also be a security > risk for yourself. > > ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) > > ** Changed in: xorg-server (Ubuntu) >Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1846807 > > Title: > Xorg crash > > Status in xorg-server package in Ubuntu: > Incomplete > > Bug description: > When upgrade (include firmware update) > > can't see login screen > when i use startx > looping login screen > > Upgrade to 19.10 and install lightdm > still again > > when i use wayland is ok. > other gnome, gnome-classic, ubuntu is looping > > ProblemType: Bug > DistroRelease: Ubuntu 19.10 > Package: xorg 1:7.7+19ubuntu12 > 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 > BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' > CompizPlugins: No value set for > `/apps/compiz-1/general/screen0/options/active_plugins' > CompositorRunning: None > CurrentDesktop: ubuntu:GNOME > Date: Sat Oct 5 00:50:39 2019 > DistUpgraded: Fresh install > DistroCodename: eoan > DistroVariant: ubuntu > GraphicsCard: >Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 > [VGA controller]) > Subsystem: Lenovo UHD Graphics 620 [17aa:225c] > InstallationDate: Installed on 2019-01-22 (254 days ago) > InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190122) > MachineType: LENOVO 20KH007UVA > ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-13-generic > root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 > SourcePackage: xorg > Symptom: display > Title: Xorg crash > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 09/02/2019 > dmi.bios.vendor: LENOVO > dmi.bios.version: N23ET66W (1.41 ) > dmi.board.asset.tag: Not Available > dmi.board.name: 20KH007UVA > dmi.board.vendor: LENOVO > dmi.board.version: Not Defined > dmi.chassis.asset.tag: No Asset Information > dmi.chassis.type: 10 > dmi.chassis.vendor: LENOVO > dmi.chassis.version: None > dmi.modalias: > dmi:bvnLENOVO:bvrN23ET66W(1.41):bd09/02/2019:svnLENOVO:pn20KH007UVA:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KH007UVA:rvrNotDefined:cvnLENOVO:ct10:cvrNone: > dmi.product.family: ThinkPad X1 Carbon 6th > dmi.product.name: 20KH007UVA > dmi.product.sku: LENOVO_MT_20KH_BU_Think_FM_ThinkPad X1 Carbon 6th > dmi.product.version: ThinkPad X1 Carbon 6th > dmi.sys.vendor: LENOVO > version.compiz: compiz N/A > version.libdrm2: libdrm2 2.4.99+git1909241510.0c4275~oibaf~d > version.libgl1-mesa-dri: libgl1-mesa-dri > 19.3~git1909260954.031752~oibaf~d > version.libgl1-mesa-glx: libgl1-mesa-glx > 19.3~git1909260954.031752~oibaf~d > version.xserver-xorg-core: xserver-xorg-core > 2:1.20.5+git20190820-0ubuntu3 > version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A > version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1 > 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 > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1846807/+subscriptions > -- with regards *Ko Ko Ye`* +95 97989 22022 +95 94500 22022 +95 9731 47907 kokoye2...@gmail.com kokoye2...@ubuntu.com skype: kokoye2007 jitsi: kokoye2007 http://ubuntu-mm.net http://wiki.ubuntu.com/kokoye2007 http://wiki.ubuntu.com/MyanmarTeam http://loco.ubuntu.com/teams/ubuntu-mm -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1846807 Title: Xorg crash Status in xorg-server package in Ubuntu: Incomplete Bug description: When upgrade (include
[Desktop-packages] [Bug 1846899] Re: X won't start at boot with either nvidia driver on GeForce GT 730 (bionic)
Searching nvidia.com for that GPU seems to recommend installing driver '430.50'. So please try: sudo apt install nvidia-driver-430 At present that will give you 430.26 but version 430.50 is in bionic- proposed so will come in a future update for Ubuntu 18.04, soonish. ** Summary changed: - X won't start at boot with either nvidia driver + X won't start at boot with either nvidia driver on GeForce GT 730 (bionic) ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Also affects: nvidia-graphics-drivers-390 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1846899 Title: X won't start at boot with either nvidia driver on GeForce GT 730 (bionic) Status in nvidia-graphics-drivers-390 package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: The video card is a GeForce GT 730, which worked well with Ubuntu 16.04. After changing to Xubuntu 18.04, I can only run the Nouveau driver and the lack of acceleration is quite noticeable. When I try to enable the "tested" NVidia driver (390), the system never presents a log-in prompt, I just get a colorful display of large blinking gibberish. I have to go to the boot options, go directly to root prompt, and remove the NVidia driver. This make the system usable again, but I'm back to the Nouveau driver. I get similar symptoms with version 340.107 of the NVidia driver. It's a little hard to collect debug information when I can't get to a prompt to look at log files... Suggestions are welcome. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CompositorRunning: None Date: Sat Oct 5 13:56:41 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GF108 [GeForce GT 730] [10de:0f02] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. GF108 [GeForce GT 730] [19da:8199] InstallationDate: Installed on 2019-04-13 (175 days ago) InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-29-generic root=UUID=d19b5e72-689e-4877-93dd-0d4bf5f7cc98 ro drm.debug=0xe plymouth:debug SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/07/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4024 dmi.board.asset.tag: Default string dmi.board.name: PRIME X470-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4024:bd09/07/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX470-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Sat Oct 5 13:56:03 2019 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1846899/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1846941] Re: Since upgrading to Eoan Ermine the screen doesn't dim progressively before turning off and locking the PC, but at once.
** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu) ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #1463 https://gitlab.gnome.org/GNOME/gnome-shell/issues/1463 ** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/gnome-shell/issues/1463 Importance: Unknown Status: Unknown ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Low ** 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/1846941 Title: Since upgrading to Eoan Ermine the screen doesn't dim progressively before turning off and locking the PC, but at once. Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Confirmed Bug description: It wasn't behaving that way in Disco. Not sure if this issue belongs to X.org, but as that was the place for suspend/resume, i decided to place this bug here. If it's the wrong package, please help me in finding the correct one. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1) ApportVersion: 2.20.11-0ubuntu7 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' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Oct 6 13:46:25 2019 DistUpgraded: 2019-09-28 01:59:57,153 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] UHD Graphics 620 [1025:1193] Subsystem: Acer Incorporated [ALI] GP108M [GeForce MX150] [1025:119a] InstallationDate: Installed on 2019-07-23 (74 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04f2:b5f7 Chicony Electronics Co., Ltd HD WebCam Bus 001 Device 003: ID 8087:0aa7 Intel Corp. Bus 001 Device 002: ID :0538 USB OPTICAL MOUSE Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire A515-51G ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-13-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to eoan on 2019-09-27 (8 days ago) dmi.bios.date: 01/03/2019 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.02 dmi.board.asset.tag: Type2 - Board Serial Number dmi.board.name: Charmander_KL dmi.board.vendor: KBL dmi.board.version: V2.02 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.02 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.02:bd01/03/2019:svnAcer:pnAspireA515-51G:pvrV2.02:rvnKBL:rnCharmander_KL:rvrV2.02:cvnAcer:ct10:cvrV2.02: dmi.product.family: Aspire 5 dmi.product.name: Aspire A515-51G dmi.product.sku: dmi.product.version: V2.02 dmi.sys.vendor: Acer 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 19.2.0-1ubuntu2 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20190820-0ubuntu3 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 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1846941/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1846858] Re: Media keys stopped working
Hmm, my media keys and Ctrl+Alt+T still work perfectly in a fully- updated 19.10 install. I wonder what's different about yours... -- 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/1846858 Title: Media keys stopped working Status in gnome-shell package in Ubuntu: Incomplete Bug description: Media keys (volume keys or CTRL+Alt+T) stopped working on october 4th. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.0-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: Sat Oct 5 07:49:58 2019 DisplayManager: gdm3 InstallationDate: Installed on 2014-07-15 (1907 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520) RelatedPackageVersions: mutter-common 3.34.0-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2018-03-24 (559 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1846858/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1846858] Re: Media keys stopped working
Can you try uninstalling the extensions? 'bettervol...@tudmotu.com' 'dash-to-d...@micxgx.gmail.com' 'mediapla...@patapon.info' 'nohotcor...@azuri.free.fr' 'sound-output-device-choo...@kgshank.net' 'topic...@phocean.net' 'user-th...@gnome-shell-extensions.gcampax.github.com' 'alternate-...@gnome-shell-extensions.gcampax.github.com' 'system-moni...@paradoxxx.zero.gmail.com' ** 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/1846858 Title: Media keys stopped working Status in gnome-shell package in Ubuntu: Incomplete Bug description: Media keys (volume keys or CTRL+Alt+T) stopped working on october 4th. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.0-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: Sat Oct 5 07:49:58 2019 DisplayManager: gdm3 InstallationDate: Installed on 2014-07-15 (1907 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520) RelatedPackageVersions: mutter-common 3.34.0-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2018-03-24 (559 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1846858/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1847006] Re: /usr/sbin/gdm3:5:get_fallback_session_name:get_session_filename:gdm_session_is_wayland_session:update_session_type:gdm_session_setup_for_user
*** This bug is a duplicate of bug 1717878 *** https://bugs.launchpad.net/bugs/1717878 ** This bug is no longer a duplicate of bug 1846895 gdm-session-worker crashed with SIGTRAP in _g_log_abort() from g_logv() from g_log() from get_fallback_session_name() from get_session_filename() from gdm_session_is_wayland_session() ** This bug has been marked a duplicate of bug 1717878 gdm3 crashed with SIGTRAP in _g_log_abort from g_logv from g_log from get_fallback_session_name from get_default_session_name from get_session_name from get_session_filename from gdm_session_is_wayland_session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1847006 Title: /usr/sbin/gdm3:5:get_fallback_session_name:get_session_filename:gdm_session_is_wayland_session:update_session_type:gdm_session_setup_for_user Status in gdm3 package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gdm3. This problem was most recently seen with package version 3.34.0-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/55afdb022e0f09e32692656f5ec80985acf385cc contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1847006/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1847006] [NEW] /usr/sbin/gdm3:5:get_fallback_session_name:get_session_filename:gdm_session_is_wayland_session:update_session_type:gdm_session_setup_for_user
*** This bug is a duplicate of bug 1717878 *** https://bugs.launchpad.net/bugs/1717878 Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding gdm3. This problem was most recently seen with package version 3.34.0-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/55afdb022e0f09e32692656f5ec80985acf385cc contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: disco eoan -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1847006 Title: /usr/sbin/gdm3:5:get_fallback_session_name:get_session_filename:gdm_session_is_wayland_session:update_session_type:gdm_session_setup_for_user Status in gdm3 package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gdm3. This problem was most recently seen with package version 3.34.0-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/55afdb022e0f09e32692656f5ec80985acf385cc contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1847006/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 158973] Re: nautilus does not mount sshfs volume when set in /etc/fstab
** Changed in: nautilus (Debian) Status: Confirmed => Fix Released -- 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/158973 Title: nautilus does not mount sshfs volume when set in /etc/fstab Status in Nautilus: Expired Status in nautilus package in Ubuntu: Invalid Status in nautilus package in Debian: Fix Released Bug description: Binary package hint: nautilus #In My /etc/fstab there is : (...) sshfs#hamacker@192.168.1.3:/home/vol/caixa_entrada /media/caixa_entrada fuse rw,users,user,nosuid,auto,nodev,allow_other,umask=000 0 0 # Then create mount point and permitions mkdir -p /media/caixa_entrada chmod 777 /media/caixa_entrada/ # Add to /etc/modules (is default in Ubuntu Gutsy, but not default in Feisty) fuse # Add to /etc/fuse.conf user_allow_other # Add my user to group `fuse` (not default in Ubuntu Gutsy) adduser hamacker fuse # set my login `hamacker` to login in 192.168.1.3 without a password (ssh-keygen -t dsa) and OK. Testing to mount /media/caixa_entrada without password via terminal is OK. Go to nautilus, open address bar and type sshfs://hamacker@192.168.1.3:/home/vol/caixa_entrada is OK too. Go to Nautilus, open left panel, choose `caixa_entrada` and right click and set 'Mount' does not run, a icon representing harddrive `caixa_entrada` appear in desktop area and disapear too fast and /media/caixa_entrada are not mounted. No log in /var/log/messages and no any message on screen to describe whats happen. The same method runs OK in nautilus when Ubuntu Feisty. Any idea whats happen ? It's a nautiilus error or the same method does not run anymore ? To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/158973/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1846853] Re: Mouse scroll should control VOLUME NOT TIME
** Changed in: totem (Ubuntu) Importance: Undecided => Wishlist -- 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/1846853 Title: Mouse scroll should control VOLUME NOT TIME Status in Totem: New Status in totem package in Ubuntu: New Bug description: I want the mouse scroll to scroll the volume up and down, not the time forward and back. This is a non-standard behavior that I consider to be a BUG within Totem, and I preferentially use VNC because of this BUG. Fix it so mouse scroll controls volume instead of time please. To manage notifications about this bug go to: https://bugs.launchpad.net/totem/+bug/1846853/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1846837] Re: totem-video-thumbnailer in Ubuntu 19.10 is currently broken on aarch64
Yes, libgomp is from source package gcc-9. ** Package changed: totem (Ubuntu) => gst-libav1.0 (Ubuntu) ** No longer affects: ffmpeg (Ubuntu) -- 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/1846837 Title: totem-video-thumbnailer in Ubuntu 19.10 is currently broken on aarch64 Status in gcc-9 package in Ubuntu: New Status in gst-libav1.0 package in Ubuntu: New Bug description: Hello! I found that totem-video-thumbnailer is broken on aarch64. It fail with following error: (totem-video-thumbnailer:12136): GStreamer-WARNING **: 00:43:52.740: Failed to load plugin '/usr/lib/aarch64-linux- gnu/gstreamer-1.0/libgstlibav.so': /lib/aarch64-linux- gnu/libgomp.so.1: cannot allocate memory in static TLS block (totem-video-thumbnailer:12136): GStreamer-WARNING **: 00:43:52.764: Failed to load plugin '/usr/lib/aarch64-linux- gnu/gstreamer-1.0/libgstlibav.so': /lib/aarch64-linux- gnu/libgomp.so.1: cannot allocate memory in static TLS block (totem-video-thumbnailer:12136): GStreamer-WARNING **: 00:43:52.788: Failed to load plugin '/usr/lib/aarch64-linux- gnu/gstreamer-1.0/libgstlibav.so': /lib/aarch64-linux- gnu/libgomp.so.1: cannot allocate memory in static TLS block I tried to rollback all related packages I could think of (totem, gcc-9, ffmpeg) to previous releases, but for some reason this doesn't help. I remember video thumbnail generation on aarch64 worked fine few weeks ago. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-9/+bug/1846837/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1846807] Re: Xorg crash
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1846807 Title: Xorg crash Status in xorg-server package in Ubuntu: Incomplete Bug description: When upgrade (include firmware update) can't see login screen when i use startx looping login screen Upgrade to 19.10 and install lightdm still again when i use wayland is ok. other gnome, gnome-classic, ubuntu is looping ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 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 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Oct 5 00:50:39 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:225c] InstallationDate: Installed on 2019-01-22 (254 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190122) MachineType: LENOVO 20KH007UVA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-13-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/02/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET66W (1.41 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KH007UVA dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN23ET66W(1.41):bd09/02/2019:svnLENOVO:pn20KH007UVA:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KH007UVA:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 6th dmi.product.name: 20KH007UVA dmi.product.sku: LENOVO_MT_20KH_BU_Think_FM_ThinkPad X1 Carbon 6th dmi.product.version: ThinkPad X1 Carbon 6th dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99+git1909241510.0c4275~oibaf~d version.libgl1-mesa-dri: libgl1-mesa-dri 19.3~git1909260954.031752~oibaf~d version.libgl1-mesa-glx: libgl1-mesa-glx 19.3~git1909260954.031752~oibaf~d version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20190820-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1846807/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1846718] Re: Pressing and holding the Super key should display numbers [1-9] on the dock icons before pressing any number key
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: New => Confirmed -- 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/1846718 Title: Pressing and holding the Super key should display numbers [1-9] on the dock icons before pressing any number key Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Bug description: Currently, this feature is incomplete, pressing and holding the Super key should display numbers [1-9] on the dock icons before actually pressing any number key. Steps to reproduce the bug: 1. Press and hold the Super key 2. Notice that no numbers appear on the dock icons 3. Press 0 (zero) key while still holding the Super key 4. Numbers appear on the dock icons for 2 seconds then disappear 5. Press any number key [1-9] that corresponds to an icon 6. Numbers appear on the dock icons for 2 seconds then disappear and the app launches What should happen: Numbers should appear on the dock icons while holding the Super key before pressing any number key in order to choose which number key to press to launch the corresponding app. I believe that's how this feature is supposed to work. And that's how it is working in Unity7 in Ubuntu 16.04 LTS. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell-extension-ubuntu-dock 0.9.1ubuntu18.04.3 ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: communitheme:ubuntu:GNOME Date: Fri Oct 4 13:21:32 2019 InstallationDate: Installed on 2018-11-29 (308 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) 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/1846718/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1846177] Re: 1910 Tap the sensor in the login window
Can you please explain in more detail what the problem is? Also what do you mean by "the sensor"? ** 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/1846177 Title: 1910 Tap the sensor in the login window Status in gnome-shell package in Ubuntu: Incomplete Bug description: Description: Ubuntu Eoan Ermine (development branch) Release: 19.10 Dell Inspiron 3180 Laptop Touch on the sensor does not work in the login window. Pressing works only with the buttons on the sensor. It works in the system itself. This issue always occurs when the computer starts or when you log out of the account. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1846177/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1846718] Re: Pressing and holding the Super key should display numbers [1-9] on the dock icons before pressing any number key
** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided => Wishlist ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Wishlist => Medium -- 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/1846718 Title: Pressing and holding the Super key should display numbers [1-9] on the dock icons before pressing any number key Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Bug description: Currently, this feature is incomplete, pressing and holding the Super key should display numbers [1-9] on the dock icons before actually pressing any number key. Steps to reproduce the bug: 1. Press and hold the Super key 2. Notice that no numbers appear on the dock icons 3. Press 0 (zero) key while still holding the Super key 4. Numbers appear on the dock icons for 2 seconds then disappear 5. Press any number key [1-9] that corresponds to an icon 6. Numbers appear on the dock icons for 2 seconds then disappear and the app launches What should happen: Numbers should appear on the dock icons while holding the Super key before pressing any number key in order to choose which number key to press to launch the corresponding app. I believe that's how this feature is supposed to work. And that's how it is working in Unity7 in Ubuntu 16.04 LTS. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell-extension-ubuntu-dock 0.9.1ubuntu18.04.3 ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: communitheme:ubuntu:GNOME Date: Fri Oct 4 13:21:32 2019 InstallationDate: Installed on 2018-11-29 (308 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) 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/1846718/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1842882] Re: gnome-control-center no longer shows all the xrandr resolutions
Rocko, Please report the problem upstream here: https://gitlab.gnome.org/GNOME/mutter/issues and then tell us the new bug ID. -- 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/1842882 Title: gnome-control-center no longer shows all the xrandr resolutions Status in mutter package in Ubuntu: New Bug description: Very recently gnome-control-center started only showing a subset of the available screen resolutions. I'll attach a screenshot and also the xrandr dump to show what I mean, eg you can see that the 2048x1152 (16:9) resolution is now missing. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-control-center 1:3.33.90-1ubuntu2 ProcVersionSignature: Ubuntu 5.2.0-15.16-generic 5.2.9 Uname: Linux 5.2.0-15-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Sep 5 15:56:47 2019 InstallationDate: Installed on 2019-07-01 (65 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190606) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1842882/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1834967] Re: Activities overview doesn't shrink some windows adequately and they are partially off screen
** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Low ** 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-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1834967 Title: Activities overview doesn't shrink some windows adequately and they are partially off screen Status in gnome-shell package in Ubuntu: Confirmed Status in gnome-shell-extension-dashtodock package in Ubuntu: Confirmed Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Bug description: Details in my screenshot: https://photos.app.goo.gl/BR6H56eug7JFMGU37 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.32.2-2ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8 Uname: Linux 5.0.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jul 1 20:38:43 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-07-01 (0 days ago) InstallationMedia: ProcEnviron: LANGUAGE=ru_UA:ru PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_UA.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.32.2+git20190626-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/1834967/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1181666] Re: gnome-shell randomly blocks mouse clicks from working in app windows
The possible fix I mentioned in comment #68: https://gitlab.gnome.org/GNOME/mutter/merge_requests/189 is in Gnome 3.34 and Ubuntu 19.10 now. However, since this bug became quiet long before that, it seems like something else fixed it already for most people(?) ** Tags added: disco -- 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/1181666 Title: gnome-shell randomly blocks mouse clicks from working in app windows Status in GNOME Shell: Confirmed Status in Ubuntu GNOME: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: Under GNOME 3, the use of the mouse-click stops occasionally, though I can still move the mouse around and can still click on items in the Activities screen and the top-bar. I can use alt-tab to cycle windows and can still type into already- active textboxes in windows, but I cannot click within the windows, and the mouse is not picked up at all by the windows. I can open the alt-f2 "run command" dialogue, but cannot type into it. The workaround I'm using is to open terminal (ctrl-alt-T) and run "gnome-shell -r", and restarting that command every time I have the problem again. Please ask if there's anything I forgot to mention. ADDITIONAL: The error tends to happen randomly, but it seems to happen upon opening a new window, changing windows, closing windows, or opening the activities pane (whether a change of window is thus instigated or not) ADDITIONAL 2: (sorry, it's early) The other workaround is to log out and to log in again, but that is also less than ideal ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: gnome-shell 3.6.3.1-0ubuntu6 ProcVersionSignature: Ubuntu 3.8.0-22.33-generic 3.8.11 Uname: Linux 3.8.0-22-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Sun May 19 07:02:18 2013 DisplayManager: gdm GsettingsChanges: b'org.gnome.desktop.interface' b'clock-show-date' b'true' b'org.gnome.desktop.interface' b'clock-show-seconds' b'true' b'org.gnome.desktop.interface' b'document-font-name' b"'Sans 10'" b'org.gnome.desktop.interface' b'font-name' b"'Cantarell 10'" b'org.gnome.desktop.interface' b'monospace-font-name' b"'Ubuntu Mono 12'" InstallationDate: Installed on 2013-05-04 (14 days ago) InstallationMedia: Ubuntu-GNOME 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1181666/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1846148] Re: Realtek ALC256M with DTS Audio Processing internal microphone doesn't work on Redmi Book 14 2019
sorry for getting back to you late. Tried to collect the logs under windows with RtHDDump but error reported: "The HD audio codec could not be found in your system" But the mic is working. Attached the error message. ** Attachment added: "error_pic.png" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1846148/+attachment/5294928/+files/error_pic.png -- 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/1846148 Title: Realtek ALC256M with DTS Audio Processing internal microphone doesn't work on Redmi Book 14 2019 Status in alsa-driver package in Ubuntu: Confirmed Bug description: Sound works okay but the internal mic doesn't work. When I plug in headset, the mic on headset also doens't work. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-29-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lilian 1689 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Oct 1 12:27:10 2019 InstallationDate: Installed on 2019-09-21 (9 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/19/2019 dmi.bios.vendor: TIMI dmi.bios.version: RMRCM400P0100 dmi.board.name: TM1901 dmi.board.vendor: TIMI dmi.chassis.type: 10 dmi.chassis.vendor: TIMI dmi.modalias: dmi:bvnTIMI:bvrRMRCM400P0100:bd08/19/2019:svnTIMI:pnRedmiBook14:pvr:rvnTIMI:rnTM1901:rvr:cvnTIMI:ct10:cvr: dmi.product.family: Mi Laptop dmi.product.name: RedmiBook 14 dmi.product.sku: TM1901-24822 dmi.sys.vendor: TIMI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1846148/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1846988] [NEW] [Audio playback] No 'Speaker - Built-in Audio'
Public bug reported: Installation details: Ubuntu 19.04 alsa-base: Installed: 1.0.25+dfsg-0ubuntu5 Candidate: 1.0.25+dfsg-0ubuntu5 Version table: *** 1.0.25+dfsg-0ubuntu5 500 500 http://au.archive.ubuntu.com/ubuntu disco/main amd64 Packages 500 http://au.archive.ubuntu.com/ubuntu disco/main i386 Packages 100 /var/lib/dpkg/status Expected behaviour: Expected a 'Speaker - Built-in Audio' option in my Audio settings. Actual behaviour: Seems the 'Speakers - Built-in Audio' playback device is not available in my settings. Instead there is 'Headphones - Built-in Audio' which obviously shouldn't exist. When actual headphones are attached, the do not playback either. Playback only works when connected via bluetooth or HDMI, but there are extra options, that do not work... not sure what it is detecting, as there is only one HDMI output. I followed this document to debug myself: https://help.ubuntu.com/community/SoundTroubleshooting. However, the second step works fine when connected via bluetooth or HDMI, as stated before. I have tried booting the Live USB, and audio works perfectly fine here, so this is not a hardware issue. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-29.31-generic 5.0.21 Uname: Linux 5.0.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: lawrence 2033 F pulseaudio /dev/snd/controlC0: lawrence 2033 F pulseaudio lawrence 23649 F alsamixer /dev/snd/pcmC0D0c: lawrence 2033 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Oct 7 09:27:18 2019 InstallationDate: Installed on 2019-09-07 (29 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: HDA NVidia - HDA NVidia Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: lawrence 2033 F pulseaudio /dev/snd/controlC0: lawrence 2033 F pulseaudio lawrence 23649 F alsamixer Symptom_Type: No sound at all Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/10/2019 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.06TMB dmi.board.asset.tag: Tag 12345 dmi.board.name: P95_96_97Ex,Rx dmi.board.vendor: IT Channel Pty Ltd dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: IT Channel Pty Ltd dmi.chassis.version: N/A dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.06TMB:bd04/10/2019:svnITChannelPtyLtd:pnP95_96_97Ex,Rx:pvrNotApplicable:rvnITChannelPtyLtd:rnP95_96_97Ex,Rx:rvrNotApplicable:cvnITChannelPtyLtd:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: P95_96_97Ex,Rx dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: IT Channel Pty Ltd mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-09-07T11:50:26.934452 ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco -- 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/1846988 Title: [Audio playback] No 'Speaker - Built-in Audio' Status in alsa-driver package in Ubuntu: New Bug description: Installation details: Ubuntu 19.04 alsa-base: Installed: 1.0.25+dfsg-0ubuntu5 Candidate: 1.0.25+dfsg-0ubuntu5 Version table: *** 1.0.25+dfsg-0ubuntu5 500 500 http://au.archive.ubuntu.com/ubuntu disco/main amd64 Packages 500 http://au.archive.ubuntu.com/ubuntu disco/main i386 Packages 100 /var/lib/dpkg/status Expected behaviour: Expected a 'Speaker - Built-in Audio' option in my Audio settings. Actual behaviour: Seems the 'Speakers - Built-in Audio' playback device is not available in my settings. Instead there is 'Headphones - Built-in Audio' which obviously shouldn't exist. When actual headphones are attached, the do not playback either. Playback only works when connected via bluetooth or HDMI, but there are extra options, that do not work... not sure what it is detecting, as there is only one HDMI output. I followed this document to debug myself: https://help.ubuntu.com/community/SoundTroubleshooting. However, the second step works fine when connected via bluetooth or HDMI, as stated before. I have tried booting the Live USB, and audio works perfectly fine here, so this is not a hardware issue. ProblemType:
[Desktop-packages] [Bug 1758653] Re: gvfsd[1366]: mkdir failed on directory /var/cache/samba: Permission denied
** Changed in: gnome-vfs (Debian) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1758653 Title: gvfsd[1366]: mkdir failed on directory /var/cache/samba: Permission denied Status in gvfs package in Ubuntu: Confirmed Status in gnome-vfs package in Debian: Fix Released Bug description: gvfsd[1366]: mkdir failed on directory /var/cache/samba: Permission denied /var/cache/ has no 'samba' subdir nor file. oem@ubuntu:~$ ls -la /var/cache/ total 80 drwxr-xr-x 18 root root 4096 Feb 19 18:57 . drwxr-xr-x 14 root root 4096 Dec 1 20:15 .. drwxr-xr-x 2 root root 4096 Sep 15 2017 apparmor drwxr-xr-x 4 root root 4096 Dec 1 20:15 app-info drwxr-xr-x 3 root root 4096 Mar 25 14:11 apt drwxr-xr-x 3 root root 4096 Feb 19 18:00 apt-xapian-index drwxr-xr-x 2 root root 4096 Dec 1 20:15 cracklib drwxrwx--- 3 root lp4096 Mar 25 07:35 cups drwxr-xr-x 2 root root 4096 Mar 23 04:41 debconf drwxr-xr-x 2 root root 4096 Dec 1 18:55 dictionaries-common drwxr-xr-x 2 root root 12288 Mar 19 04:28 fontconfig drwxr-xr-x 2 root root 4096 Oct 9 19:50 gdm drwx-- 2 root root 4096 Mar 25 14:11 ldconfig drwxr-xr-x 2 root root 4096 Dec 1 19:13 localepurge drwxr-xr-x 13 man man 4096 Mar 25 14:11 man -rw-r--r-- 1 root root 0 Mar 25 08:24 motd-news drwxr-xr-x 3 root root 4096 Dec 1 19:57 PackageKit drwxr-xr-x 2 root root 4096 Mar 24 14:56 snapd drwxr-xr-x 2 root root 4096 Feb 20 04:57 ubuntu-advantage-tools ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gvfs 1.36.0-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Mar 25 14:28:21 2018 EcryptfsInUse: Yes ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gvfs UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1758653/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1846890] Re: Pluma: unable to enable plugins External tools, Python Console, Quick Open, Snippets) because of missed /usr/lib/x86_64-linux-gnu/libpeas-1.0/loaders/libpythonload
** Changed in: libpeas (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libpeas in Ubuntu. https://bugs.launchpad.net/bugs/1846890 Title: Pluma: unable to enable plugins External tools, Python Console, Quick Open, Snippets) because of missed /usr/lib/x86_64-linux- gnu/libpeas-1.0/loaders/libpythonloader.so Status in libpeas package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Install Ubuntu 19.10 2. Launch Pluma 3. Go to Edit -> Preferences, switch to Plugins tab 4. Try enable all plugins by checking their checkmarks Expected results: * all plugins are enabled without errors or warnings; Actual results: * plugin(s) are not enabled, show the following errors in `pluma`'s terminal: ``` $ pluma (pluma:1685): libpeas-WARNING **: 19:20:59.204: Failed to load module 'pythonloader': /usr/lib/x86_64-linux- gnu/libpeas-1.0/loaders/libpythonloader.so: cannot open shared object file: No such file or directory (pluma:1685): libpeas-WARNING **: 19:20:59.205: Could not load plugin loader 'python' ``` Note: in previous releases the `libpythonloader.so` was located in libpeas-1.0-python2loader package (see https://packages.ubuntu.com/search?suite=disco=amd64=exactfilename=contents=libpythonloader.so ) but this file is missed in 19.10 repository. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: pluma 1.22.2-0ubuntu1 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: MATE Date: Sat Oct 5 19:23:02 2019 InstallationDate: Installed on 2019-10-05 (0 days ago) InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20191004) SourcePackage: pluma UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libpeas/+bug/1846890/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1841545] Re: Don't update to 0.7.15 this cycle
Seb, by the way, appstream-glib will probably cause several packages to FTBFS because the new version has increased the validation requirements. So projects blindly running `appstream-util validate` in their test suite may need to be updated. One workaround is to use `appstream-util validate-relax` but actually fixing the AppStream metadata is better. I found a project today, gpaste, which got the appstream validation test "for free" by using the @APPSTREAM_XML_RULES@ autotools macro from https://github.com/hughsie/appstream-glib/blob/master/data/appstream- xml.m4 . See https://bugs.debian.org/941731 ** Bug watch added: Debian Bug tracker #941731 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941731 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to appstream-glib in Ubuntu. https://bugs.launchpad.net/bugs/1841545 Title: Don't update to 0.7.15 this cycle Status in appstream-glib package in Ubuntu: Triaged Bug description: The update includes features so the version is blocked for eoan of needs an exception To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream-glib/+bug/1841545/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1846371] Re: firefox 70.0 beta 11 isn't fully translated
** Changed in: firefox Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1846371 Title: firefox 70.0 beta 11 isn't fully translated Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Triaged Bug description: (this was initially spotted by ricotz) I'm running firefox 70.0~b11+build1-0ubuntu0.19.10.1 from ppa:mozillateam/firefox-next with a French locale, and the UI is not fully translated to French. The chrome (menu items and address bar help text) as well as other parts of the UI (new tab page) are correctly translated, but other parts aren't, such as the about:preferences settings page. Other about: pages (such as about:mozilla or about:robots) are correctly translated. about:addons is partially translated. Fully translated: - menu items - address bar - about:mozilla - about:robots - about:compat - about:welcome - about:newtab - about:webrtc Partially translated: - about:addons Not translated: - about:preferences - about:cache - "new extensions won't work in private mode" popover - "what's new" popover - about firefox dialog ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: firefox 70.0~b11+build1-0ubuntu0.19.10.1 [origin: LP-PPA-mozillateam-firefox-next] 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: 20190930191143 CurrentDesktop: ubuntu:GNOME Date: Wed Oct 2 18:27:45 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:930 DefaultProfilePrefSources: /usr/lib/firefox/defaults/pref/vendor-gre.js /usr/lib/firefox/defaults/pref/channel-prefs.js DefaultProfilePrefs: network.manage-offline-status: true (/usr/lib/firefox/defaults/pref/vendor-gre.js) DefaultProfileThemes: extensions.sqlite corrupt or missing InstallationDate: Installed on 2018-08-21 (407 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180821) Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=70.0/20190930191143 (In use) SourcePackage: firefox UpgradeStatus: Upgraded to eoan on 2019-06-05 (119 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1846371/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1846371]
Mossop - I remember you saying that we do purge XUL cache on language change, I think this bug indicates that we don't? Or is there something else in play? -- 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/1846371 Title: firefox 70.0 beta 11 isn't fully translated Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Triaged Bug description: (this was initially spotted by ricotz) I'm running firefox 70.0~b11+build1-0ubuntu0.19.10.1 from ppa:mozillateam/firefox-next with a French locale, and the UI is not fully translated to French. The chrome (menu items and address bar help text) as well as other parts of the UI (new tab page) are correctly translated, but other parts aren't, such as the about:preferences settings page. Other about: pages (such as about:mozilla or about:robots) are correctly translated. about:addons is partially translated. Fully translated: - menu items - address bar - about:mozilla - about:robots - about:compat - about:welcome - about:newtab - about:webrtc Partially translated: - about:addons Not translated: - about:preferences - about:cache - "new extensions won't work in private mode" popover - "what's new" popover - about firefox dialog ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: firefox 70.0~b11+build1-0ubuntu0.19.10.1 [origin: LP-PPA-mozillateam-firefox-next] 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: 20190930191143 CurrentDesktop: ubuntu:GNOME Date: Wed Oct 2 18:27:45 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:930 DefaultProfilePrefSources: /usr/lib/firefox/defaults/pref/vendor-gre.js /usr/lib/firefox/defaults/pref/channel-prefs.js DefaultProfilePrefs: network.manage-offline-status: true (/usr/lib/firefox/defaults/pref/vendor-gre.js) DefaultProfileThemes: extensions.sqlite corrupt or missing InstallationDate: Installed on 2018-08-21 (407 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180821) Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=70.0/20190930191143 (In use) SourcePackage: firefox UpgradeStatus: Upgraded to eoan on 2019-06-05 (119 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1846371/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1846371]
(In reply to Zibi Braniecki [:zbraniecki][:gandalf] from comment #10) > Can you revert that change in L10nRegistry.jsm and see if you can still > reproduce? I doubt that this is the culprit because this change doesn't > really affect anything except of protecting against race between sync/async. Artifact build from current mozilla-central tip 1) Build and run 2) Create a new profile 3) In `about:config` set `intl.multilingual.enabled` to true 4) Install French language pack from the latest mozilla-central-l10n available, luckily there might not be new DTD strings loaded on startup…. In my case this worked http://archive.mozilla.org/pub/firefox/nightly/2019/10/2019-10-04-09-46-56-mozilla-central-l10n/linux-x86_64/xpi/ 5) Open preferences, switch the language to French and restart. At this point, the browser should reopen on Preferences in French, but they're in English, even after reloading the page. I tried undoing the changes to L10nRegistry.jsm, but it didn't solve the issue. But removing `data-l10n-sync="true"` from `browser/base/content/browser.xhtml` seems to do it. https://hg.mozilla.org/integration/autoland/rev/1f622156e9eab1d2c58d5d77bb5908fcc83db253#l4.13 -- 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/1846371 Title: firefox 70.0 beta 11 isn't fully translated Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Triaged Bug description: (this was initially spotted by ricotz) I'm running firefox 70.0~b11+build1-0ubuntu0.19.10.1 from ppa:mozillateam/firefox-next with a French locale, and the UI is not fully translated to French. The chrome (menu items and address bar help text) as well as other parts of the UI (new tab page) are correctly translated, but other parts aren't, such as the about:preferences settings page. Other about: pages (such as about:mozilla or about:robots) are correctly translated. about:addons is partially translated. Fully translated: - menu items - address bar - about:mozilla - about:robots - about:compat - about:welcome - about:newtab - about:webrtc Partially translated: - about:addons Not translated: - about:preferences - about:cache - "new extensions won't work in private mode" popover - "what's new" popover - about firefox dialog ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: firefox 70.0~b11+build1-0ubuntu0.19.10.1 [origin: LP-PPA-mozillateam-firefox-next] 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: 20190930191143 CurrentDesktop: ubuntu:GNOME Date: Wed Oct 2 18:27:45 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:930 DefaultProfilePrefSources: /usr/lib/firefox/defaults/pref/vendor-gre.js /usr/lib/firefox/defaults/pref/channel-prefs.js DefaultProfilePrefs: network.manage-offline-status: true (/usr/lib/firefox/defaults/pref/vendor-gre.js) DefaultProfileThemes: extensions.sqlite corrupt or missing InstallationDate: Installed on 2018-08-21 (407 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180821) Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=70.0/20190930191143 (In use) SourcePackage: firefox UpgradeStatus: Upgraded to eoan on 2019-06-05 (119 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1846371/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1846371]
(In reply to Zibi Braniecki [:zbraniecki][:gandalf] from comment #12) > thank you! My best guess is that bringing Fluent to browser.xhtml causes > Fluent to kick-off earlier than langpacks are registered. > ... > Kris - Does it sound plausible? can we make langpacks register prior to > browser.xhtml? No, langpacks are initialized about as early as it's possible for anything that requires the profile to be initialized, and the process is entirely synchronous: https://searchfox.org/mozilla- central/rev/2f29d53865cb895bf16c91336cc575aecd996a17/toolkit/components/extensions/Extension.jsm#2501-2534 Unless the langpacks aren't already installed at startup, anyway. In that case, they'd become available whenever they happen to be detected/installed. But after the next restart, they should still always be available immediately at startup. -- 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/1846371 Title: firefox 70.0 beta 11 isn't fully translated Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Triaged Bug description: (this was initially spotted by ricotz) I'm running firefox 70.0~b11+build1-0ubuntu0.19.10.1 from ppa:mozillateam/firefox-next with a French locale, and the UI is not fully translated to French. The chrome (menu items and address bar help text) as well as other parts of the UI (new tab page) are correctly translated, but other parts aren't, such as the about:preferences settings page. Other about: pages (such as about:mozilla or about:robots) are correctly translated. about:addons is partially translated. Fully translated: - menu items - address bar - about:mozilla - about:robots - about:compat - about:welcome - about:newtab - about:webrtc Partially translated: - about:addons Not translated: - about:preferences - about:cache - "new extensions won't work in private mode" popover - "what's new" popover - about firefox dialog ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: firefox 70.0~b11+build1-0ubuntu0.19.10.1 [origin: LP-PPA-mozillateam-firefox-next] 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: 20190930191143 CurrentDesktop: ubuntu:GNOME Date: Wed Oct 2 18:27:45 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:930 DefaultProfilePrefSources: /usr/lib/firefox/defaults/pref/vendor-gre.js /usr/lib/firefox/defaults/pref/channel-prefs.js DefaultProfilePrefs: network.manage-offline-status: true (/usr/lib/firefox/defaults/pref/vendor-gre.js) DefaultProfileThemes: extensions.sqlite corrupt or missing InstallationDate: Installed on 2018-08-21 (407 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180821) Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=70.0/20190930191143 (In use) SourcePackage: firefox UpgradeStatus: Upgraded to eoan on 2019-06-05 (119 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1846371/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1846371]
(In reply to Zibi Braniecki [:zbraniecki][:gandalf] from comment #7) > Mossop - I remember you saying that we do purge XUL cache on language change, > I think this bug indicates that we don't? Or is there something else in play? If starting with -purgecaches isn't helping then I don't think the startup cache is a problem here. -- 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/1846371 Title: firefox 70.0 beta 11 isn't fully translated Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Triaged Bug description: (this was initially spotted by ricotz) I'm running firefox 70.0~b11+build1-0ubuntu0.19.10.1 from ppa:mozillateam/firefox-next with a French locale, and the UI is not fully translated to French. The chrome (menu items and address bar help text) as well as other parts of the UI (new tab page) are correctly translated, but other parts aren't, such as the about:preferences settings page. Other about: pages (such as about:mozilla or about:robots) are correctly translated. about:addons is partially translated. Fully translated: - menu items - address bar - about:mozilla - about:robots - about:compat - about:welcome - about:newtab - about:webrtc Partially translated: - about:addons Not translated: - about:preferences - about:cache - "new extensions won't work in private mode" popover - "what's new" popover - about firefox dialog ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: firefox 70.0~b11+build1-0ubuntu0.19.10.1 [origin: LP-PPA-mozillateam-firefox-next] 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: 20190930191143 CurrentDesktop: ubuntu:GNOME Date: Wed Oct 2 18:27:45 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:930 DefaultProfilePrefSources: /usr/lib/firefox/defaults/pref/vendor-gre.js /usr/lib/firefox/defaults/pref/channel-prefs.js DefaultProfilePrefs: network.manage-offline-status: true (/usr/lib/firefox/defaults/pref/vendor-gre.js) DefaultProfileThemes: extensions.sqlite corrupt or missing InstallationDate: Installed on 2018-08-21 (407 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180821) Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=70.0/20190930191143 (In use) SourcePackage: firefox UpgradeStatus: Upgraded to eoan on 2019-06-05 (119 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1846371/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1846371]
Can you revert that change in L10nRegistry.jsm and see if you can still reproduce? I doubt that this is the culprit because this change doesn't really affect anything except of protecting against race between sync/async. -- 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/1846371 Title: firefox 70.0 beta 11 isn't fully translated Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Triaged Bug description: (this was initially spotted by ricotz) I'm running firefox 70.0~b11+build1-0ubuntu0.19.10.1 from ppa:mozillateam/firefox-next with a French locale, and the UI is not fully translated to French. The chrome (menu items and address bar help text) as well as other parts of the UI (new tab page) are correctly translated, but other parts aren't, such as the about:preferences settings page. Other about: pages (such as about:mozilla or about:robots) are correctly translated. about:addons is partially translated. Fully translated: - menu items - address bar - about:mozilla - about:robots - about:compat - about:welcome - about:newtab - about:webrtc Partially translated: - about:addons Not translated: - about:preferences - about:cache - "new extensions won't work in private mode" popover - "what's new" popover - about firefox dialog ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: firefox 70.0~b11+build1-0ubuntu0.19.10.1 [origin: LP-PPA-mozillateam-firefox-next] 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: 20190930191143 CurrentDesktop: ubuntu:GNOME Date: Wed Oct 2 18:27:45 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:930 DefaultProfilePrefSources: /usr/lib/firefox/defaults/pref/vendor-gre.js /usr/lib/firefox/defaults/pref/channel-prefs.js DefaultProfilePrefs: network.manage-offline-status: true (/usr/lib/firefox/defaults/pref/vendor-gre.js) DefaultProfileThemes: extensions.sqlite corrupt or missing InstallationDate: Installed on 2018-08-21 (407 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180821) Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=70.0/20190930191143 (In use) SourcePackage: firefox UpgradeStatus: Upgraded to eoan on 2019-06-05 (119 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1846371/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1846371]
Even starting with `-purgecaches` doesn't help. Requested locales is correct `["fr","it"]`, but even about:support stays in the language of the build (Italian in my case). -- 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/1846371 Title: firefox 70.0 beta 11 isn't fully translated Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Triaged Bug description: (this was initially spotted by ricotz) I'm running firefox 70.0~b11+build1-0ubuntu0.19.10.1 from ppa:mozillateam/firefox-next with a French locale, and the UI is not fully translated to French. The chrome (menu items and address bar help text) as well as other parts of the UI (new tab page) are correctly translated, but other parts aren't, such as the about:preferences settings page. Other about: pages (such as about:mozilla or about:robots) are correctly translated. about:addons is partially translated. Fully translated: - menu items - address bar - about:mozilla - about:robots - about:compat - about:welcome - about:newtab - about:webrtc Partially translated: - about:addons Not translated: - about:preferences - about:cache - "new extensions won't work in private mode" popover - "what's new" popover - about firefox dialog ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: firefox 70.0~b11+build1-0ubuntu0.19.10.1 [origin: LP-PPA-mozillateam-firefox-next] 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: 20190930191143 CurrentDesktop: ubuntu:GNOME Date: Wed Oct 2 18:27:45 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:930 DefaultProfilePrefSources: /usr/lib/firefox/defaults/pref/vendor-gre.js /usr/lib/firefox/defaults/pref/channel-prefs.js DefaultProfilePrefs: network.manage-offline-status: true (/usr/lib/firefox/defaults/pref/vendor-gre.js) DefaultProfileThemes: extensions.sqlite corrupt or missing InstallationDate: Installed on 2018-08-21 (407 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180821) Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=70.0/20190930191143 (In use) SourcePackage: firefox UpgradeStatus: Upgraded to eoan on 2019-06-05 (119 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1846371/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1846371]
(In reply to Francesco Lodolo [:flod] from comment #11) > I tried undoing the changes to L10nRegistry.jsm, but it didn't solve the > issue. I can confirm that undoing the changes to L10nRegistry.jsm doesn't fix the problem (tested by building Ubuntu packages with that change reverted). -- 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/1846371 Title: firefox 70.0 beta 11 isn't fully translated Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Triaged Bug description: (this was initially spotted by ricotz) I'm running firefox 70.0~b11+build1-0ubuntu0.19.10.1 from ppa:mozillateam/firefox-next with a French locale, and the UI is not fully translated to French. The chrome (menu items and address bar help text) as well as other parts of the UI (new tab page) are correctly translated, but other parts aren't, such as the about:preferences settings page. Other about: pages (such as about:mozilla or about:robots) are correctly translated. about:addons is partially translated. Fully translated: - menu items - address bar - about:mozilla - about:robots - about:compat - about:welcome - about:newtab - about:webrtc Partially translated: - about:addons Not translated: - about:preferences - about:cache - "new extensions won't work in private mode" popover - "what's new" popover - about firefox dialog ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: firefox 70.0~b11+build1-0ubuntu0.19.10.1 [origin: LP-PPA-mozillateam-firefox-next] 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: 20190930191143 CurrentDesktop: ubuntu:GNOME Date: Wed Oct 2 18:27:45 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:930 DefaultProfilePrefSources: /usr/lib/firefox/defaults/pref/vendor-gre.js /usr/lib/firefox/defaults/pref/channel-prefs.js DefaultProfilePrefs: network.manage-offline-status: true (/usr/lib/firefox/defaults/pref/vendor-gre.js) DefaultProfileThemes: extensions.sqlite corrupt or missing InstallationDate: Installed on 2018-08-21 (407 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180821) Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=70.0/20190930191143 (In use) SourcePackage: firefox UpgradeStatus: Upgraded to eoan on 2019-06-05 (119 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1846371/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1846371]
Disabling and re-enabling the language packs seems to trigger something, and things start to get localized as expected. -- 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/1846371 Title: firefox 70.0 beta 11 isn't fully translated Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Triaged Bug description: (this was initially spotted by ricotz) I'm running firefox 70.0~b11+build1-0ubuntu0.19.10.1 from ppa:mozillateam/firefox-next with a French locale, and the UI is not fully translated to French. The chrome (menu items and address bar help text) as well as other parts of the UI (new tab page) are correctly translated, but other parts aren't, such as the about:preferences settings page. Other about: pages (such as about:mozilla or about:robots) are correctly translated. about:addons is partially translated. Fully translated: - menu items - address bar - about:mozilla - about:robots - about:compat - about:welcome - about:newtab - about:webrtc Partially translated: - about:addons Not translated: - about:preferences - about:cache - "new extensions won't work in private mode" popover - "what's new" popover - about firefox dialog ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: firefox 70.0~b11+build1-0ubuntu0.19.10.1 [origin: LP-PPA-mozillateam-firefox-next] 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: 20190930191143 CurrentDesktop: ubuntu:GNOME Date: Wed Oct 2 18:27:45 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:930 DefaultProfilePrefSources: /usr/lib/firefox/defaults/pref/vendor-gre.js /usr/lib/firefox/defaults/pref/channel-prefs.js DefaultProfilePrefs: network.manage-offline-status: true (/usr/lib/firefox/defaults/pref/vendor-gre.js) DefaultProfileThemes: extensions.sqlite corrupt or missing InstallationDate: Installed on 2018-08-21 (407 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180821) Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=70.0/20190930191143 (In use) SourcePackage: firefox UpgradeStatus: Upgraded to eoan on 2019-06-05 (119 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1846371/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1846371]
thank you! My best guess is that bringing Fluent to browser.xhtml causes Fluent to kick-off earlier than langpacks are registered. Unfortunately, I'll be on PTO next week, which is unfortunate if we want to take it into 70 :( Kris - Does it sound plausible? can we make langpacks register prior to browser.xhtml? -- 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/1846371 Title: firefox 70.0 beta 11 isn't fully translated Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Triaged Bug description: (this was initially spotted by ricotz) I'm running firefox 70.0~b11+build1-0ubuntu0.19.10.1 from ppa:mozillateam/firefox-next with a French locale, and the UI is not fully translated to French. The chrome (menu items and address bar help text) as well as other parts of the UI (new tab page) are correctly translated, but other parts aren't, such as the about:preferences settings page. Other about: pages (such as about:mozilla or about:robots) are correctly translated. about:addons is partially translated. Fully translated: - menu items - address bar - about:mozilla - about:robots - about:compat - about:welcome - about:newtab - about:webrtc Partially translated: - about:addons Not translated: - about:preferences - about:cache - "new extensions won't work in private mode" popover - "what's new" popover - about firefox dialog ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: firefox 70.0~b11+build1-0ubuntu0.19.10.1 [origin: LP-PPA-mozillateam-firefox-next] 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: 20190930191143 CurrentDesktop: ubuntu:GNOME Date: Wed Oct 2 18:27:45 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:930 DefaultProfilePrefSources: /usr/lib/firefox/defaults/pref/vendor-gre.js /usr/lib/firefox/defaults/pref/channel-prefs.js DefaultProfilePrefs: network.manage-offline-status: true (/usr/lib/firefox/defaults/pref/vendor-gre.js) DefaultProfileThemes: extensions.sqlite corrupt or missing InstallationDate: Installed on 2018-08-21 (407 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180821) Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=70.0/20190930191143 (In use) SourcePackage: firefox UpgradeStatus: Upgraded to eoan on 2019-06-05 (119 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1846371/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1846371]
[Tracking Requested - why for this release]: It's very late, but we're providing users with language packs a very poor experience. I'm trying to run mozregression to identify the bug causing this, but it's the most painful process imaginable. -- 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/1846371 Title: firefox 70.0 beta 11 isn't fully translated Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Triaged Bug description: (this was initially spotted by ricotz) I'm running firefox 70.0~b11+build1-0ubuntu0.19.10.1 from ppa:mozillateam/firefox-next with a French locale, and the UI is not fully translated to French. The chrome (menu items and address bar help text) as well as other parts of the UI (new tab page) are correctly translated, but other parts aren't, such as the about:preferences settings page. Other about: pages (such as about:mozilla or about:robots) are correctly translated. about:addons is partially translated. Fully translated: - menu items - address bar - about:mozilla - about:robots - about:compat - about:welcome - about:newtab - about:webrtc Partially translated: - about:addons Not translated: - about:preferences - about:cache - "new extensions won't work in private mode" popover - "what's new" popover - about firefox dialog ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: firefox 70.0~b11+build1-0ubuntu0.19.10.1 [origin: LP-PPA-mozillateam-firefox-next] 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: 20190930191143 CurrentDesktop: ubuntu:GNOME Date: Wed Oct 2 18:27:45 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:930 DefaultProfilePrefSources: /usr/lib/firefox/defaults/pref/vendor-gre.js /usr/lib/firefox/defaults/pref/channel-prefs.js DefaultProfilePrefs: network.manage-offline-status: true (/usr/lib/firefox/defaults/pref/vendor-gre.js) DefaultProfileThemes: extensions.sqlite corrupt or missing InstallationDate: Installed on 2018-08-21 (407 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180821) Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=70.0/20190930191143 (In use) SourcePackage: firefox UpgradeStatus: Upgraded to eoan on 2019-06-05 (119 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1846371/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1846371]
That said ... we don't flush the startup cache when the locales change, but we do flush the xul prototype cache: https://searchfox.org/mozilla- central/source/chrome/nsChromeRegistryChrome.cpp#201 which means whatever this is caching is not getting flushed (thought -purgecaches would flush it so maybe a red herring): https://searchfox.org/mozilla- central/source/toolkit/components/extensions/ExtensionParent.jsm#2004. >From what I can see registering a new source should be causing the available locales to change and so the prototype cache to get flushed: https://searchfox.org/mozilla- central/source/intl/l10n/L10nRegistry.jsm#198. It should also cause us to retranslate any documents: https://searchfox.org/mozilla- central/source/intl/l10n/Localization.cpp#. I wonder what order those happen in though. -- 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/1846371 Title: firefox 70.0 beta 11 isn't fully translated Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Triaged Bug description: (this was initially spotted by ricotz) I'm running firefox 70.0~b11+build1-0ubuntu0.19.10.1 from ppa:mozillateam/firefox-next with a French locale, and the UI is not fully translated to French. The chrome (menu items and address bar help text) as well as other parts of the UI (new tab page) are correctly translated, but other parts aren't, such as the about:preferences settings page. Other about: pages (such as about:mozilla or about:robots) are correctly translated. about:addons is partially translated. Fully translated: - menu items - address bar - about:mozilla - about:robots - about:compat - about:welcome - about:newtab - about:webrtc Partially translated: - about:addons Not translated: - about:preferences - about:cache - "new extensions won't work in private mode" popover - "what's new" popover - about firefox dialog ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: firefox 70.0~b11+build1-0ubuntu0.19.10.1 [origin: LP-PPA-mozillateam-firefox-next] 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: 20190930191143 CurrentDesktop: ubuntu:GNOME Date: Wed Oct 2 18:27:45 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:930 DefaultProfilePrefSources: /usr/lib/firefox/defaults/pref/vendor-gre.js /usr/lib/firefox/defaults/pref/channel-prefs.js DefaultProfilePrefs: network.manage-offline-status: true (/usr/lib/firefox/defaults/pref/vendor-gre.js) DefaultProfileThemes: extensions.sqlite corrupt or missing InstallationDate: Installed on 2018-08-21 (407 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180821) Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=70.0/20190930191143 (In use) SourcePackage: firefox UpgradeStatus: Upgraded to eoan on 2019-06-05 (119 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1846371/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1846371]
I can't narrow down further, because all language packs on FTP for that day cause a YSOD. @zibi The only relevant bug seems to be the one migrating menubar to Fluent (it does touch L10nRegistry.jsm, no clue if that could be the cause of this) https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=e78733e0ffcfe52903aba0a02952cd800b89ca8d=ff0125384d06fefae3ca60435b85a9be0fd9744e -- 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/1846371 Title: firefox 70.0 beta 11 isn't fully translated Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Triaged Bug description: (this was initially spotted by ricotz) I'm running firefox 70.0~b11+build1-0ubuntu0.19.10.1 from ppa:mozillateam/firefox-next with a French locale, and the UI is not fully translated to French. The chrome (menu items and address bar help text) as well as other parts of the UI (new tab page) are correctly translated, but other parts aren't, such as the about:preferences settings page. Other about: pages (such as about:mozilla or about:robots) are correctly translated. about:addons is partially translated. Fully translated: - menu items - address bar - about:mozilla - about:robots - about:compat - about:welcome - about:newtab - about:webrtc Partially translated: - about:addons Not translated: - about:preferences - about:cache - "new extensions won't work in private mode" popover - "what's new" popover - about firefox dialog ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: firefox 70.0~b11+build1-0ubuntu0.19.10.1 [origin: LP-PPA-mozillateam-firefox-next] 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: 20190930191143 CurrentDesktop: ubuntu:GNOME Date: Wed Oct 2 18:27:45 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:930 DefaultProfilePrefSources: /usr/lib/firefox/defaults/pref/vendor-gre.js /usr/lib/firefox/defaults/pref/channel-prefs.js DefaultProfilePrefs: network.manage-offline-status: true (/usr/lib/firefox/defaults/pref/vendor-gre.js) DefaultProfileThemes: extensions.sqlite corrupt or missing InstallationDate: Installed on 2018-08-21 (407 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180821) Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=70.0/20190930191143 (In use) SourcePackage: firefox UpgradeStatus: Upgraded to eoan on 2019-06-05 (119 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1846371/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1846371]
(In reply to Francesco Lodolo [:flod] from comment #11) > But removing `data-l10n-sync="true"` from > `browser/base/content/browser.xhtml` seems to do it. > https://hg.mozilla.org/integration/autoland/rev/1f622156e9eab1d2c58d5d77bb5908fcc83db253#l4.13 And I can confirm that removing `data-l10n-sync="true"` from `browser/base/content/browser.xhtml` fixes the issue for me (tested by building Ubuntu packages with that change reverted). -- 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/1846371 Title: firefox 70.0 beta 11 isn't fully translated Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Triaged Bug description: (this was initially spotted by ricotz) I'm running firefox 70.0~b11+build1-0ubuntu0.19.10.1 from ppa:mozillateam/firefox-next with a French locale, and the UI is not fully translated to French. The chrome (menu items and address bar help text) as well as other parts of the UI (new tab page) are correctly translated, but other parts aren't, such as the about:preferences settings page. Other about: pages (such as about:mozilla or about:robots) are correctly translated. about:addons is partially translated. Fully translated: - menu items - address bar - about:mozilla - about:robots - about:compat - about:welcome - about:newtab - about:webrtc Partially translated: - about:addons Not translated: - about:preferences - about:cache - "new extensions won't work in private mode" popover - "what's new" popover - about firefox dialog ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: firefox 70.0~b11+build1-0ubuntu0.19.10.1 [origin: LP-PPA-mozillateam-firefox-next] 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: 20190930191143 CurrentDesktop: ubuntu:GNOME Date: Wed Oct 2 18:27:45 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:930 DefaultProfilePrefSources: /usr/lib/firefox/defaults/pref/vendor-gre.js /usr/lib/firefox/defaults/pref/channel-prefs.js DefaultProfilePrefs: network.manage-offline-status: true (/usr/lib/firefox/defaults/pref/vendor-gre.js) DefaultProfileThemes: extensions.sqlite corrupt or missing InstallationDate: Installed on 2018-08-21 (407 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180821) Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=70.0/20190930191143 (In use) SourcePackage: firefox UpgradeStatus: Upgraded to eoan on 2019-06-05 (119 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1846371/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1846371]
Thanks for the detailed report, I can confirm the behavior on 70.0b11 (64 bit). @zibi Did anything change in the caching system? That's all Fluent elements, which should even change without a restart. -- 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/1846371 Title: firefox 70.0 beta 11 isn't fully translated Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Triaged Bug description: (this was initially spotted by ricotz) I'm running firefox 70.0~b11+build1-0ubuntu0.19.10.1 from ppa:mozillateam/firefox-next with a French locale, and the UI is not fully translated to French. The chrome (menu items and address bar help text) as well as other parts of the UI (new tab page) are correctly translated, but other parts aren't, such as the about:preferences settings page. Other about: pages (such as about:mozilla or about:robots) are correctly translated. about:addons is partially translated. Fully translated: - menu items - address bar - about:mozilla - about:robots - about:compat - about:welcome - about:newtab - about:webrtc Partially translated: - about:addons Not translated: - about:preferences - about:cache - "new extensions won't work in private mode" popover - "what's new" popover - about firefox dialog ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: firefox 70.0~b11+build1-0ubuntu0.19.10.1 [origin: LP-PPA-mozillateam-firefox-next] 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: 20190930191143 CurrentDesktop: ubuntu:GNOME Date: Wed Oct 2 18:27:45 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:930 DefaultProfilePrefSources: /usr/lib/firefox/defaults/pref/vendor-gre.js /usr/lib/firefox/defaults/pref/channel-prefs.js DefaultProfilePrefs: network.manage-offline-status: true (/usr/lib/firefox/defaults/pref/vendor-gre.js) DefaultProfileThemes: extensions.sqlite corrupt or missing InstallationDate: Installed on 2018-08-21 (407 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180821) Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=70.0/20190930191143 (In use) SourcePackage: firefox UpgradeStatus: Upgraded to eoan on 2019-06-05 (119 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1846371/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1846140 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to 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: Incomplete 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 1846140] Re: Realtek RTL8723BU doesn't work well in ubuntu
For me it looks more like a kernel issue, as the Wi-Fi principally works (network-manager must have set it up correctly). The weak signal issue looks more like something in the driver. ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to 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: New 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 1846477] Re: Dragging icons in launcher is slow until shell restarted
As a separate test I have reproduced this on my X220 which has now got an uptime of 3 days with zero applications running besides gnome terminal. When originally booted it was fast as expected. But now, after a number of lock/unlock cycles and 3 days uptime, it's slow to move icons around the launcher. -- 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: New 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 1842882] Re: gnome-control-center no longer shows all the xrandr resolutions
Even with the POP OS! PPA removed, this is still happening. Sometimes the resolutions are all there and sometimes not. ** Changed in: mutter (Ubuntu) Status: Invalid => New -- 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/1842882 Title: gnome-control-center no longer shows all the xrandr resolutions Status in mutter package in Ubuntu: New Bug description: Very recently gnome-control-center started only showing a subset of the available screen resolutions. I'll attach a screenshot and also the xrandr dump to show what I mean, eg you can see that the 2048x1152 (16:9) resolution is now missing. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-control-center 1:3.33.90-1ubuntu2 ProcVersionSignature: Ubuntu 5.2.0-15.16-generic 5.2.9 Uname: Linux 5.2.0-15-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Sep 5 15:56:47 2019 InstallationDate: Installed on 2019-07-01 (65 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190606) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1842882/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1768625] Re: Bluetooth headset HSP/HFP mode not working in Bionic
*** This bug is a duplicate of bug 1576559 *** https://bugs.launchpad.net/bugs/1576559 I get the following for the Logitech H800 wireless headset (without "headset"): Device 00:0D:44:D2:71:61 (public) Name: H800 Logitech Headset Alias: H800 Logitech Headset Class: 0x00240404 Icon: audio-card Paired: yes Trusted: yes Blocked: no Connected: yes LegacyPairing: no UUID: Audio Sink(110b--1000-8000-00805f9b34fb) UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb) UUID: Advanced Audio Distribu.. (110d--1000-8000-00805f9b34fb) UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb) UUID: Handsfree (111e--1000-8000-00805f9b34fb) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1768625 Title: Bluetooth headset HSP/HFP mode not working in Bionic Status in pulseaudio package in Ubuntu: Incomplete Bug description: There is a previous bug with almost the same title, but for Xenial (https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1549163). I have had this issue in Artful, and when commented on the old bug, I was asked to raise a new one instead. I waited to see if Bionic fixed it for me, but it does not seem to work still. So! Steps to reproduce: 1. enable bluetooth on computer and switch on the headset. 2. pair and connect the headset 3. go to settings to switch headset to HSP/HFP mode to enable mic 4. save and close window. Expected behaviour: 1. mic should be enabled and headset should be usable to attend calls on laptop. Behaviour in error: 1. Headset profile switches back to A2DP and mic is not enabled. I am using a generic bluetooth headset on a fresh updated Kubuntu 18.04 bionic with plasma DE. Software versions: Kernel: 4.15.0-20-generic Bluez version: 5.48-0ubuntu3 pulseaudio: 1:11.1-1ubuntu7 pulseaudio-module-bluetooth: 1:11.1-1ubuntu7 Additional information: Running "pacmd list-cards" says that HSF/HFP is 'not available' on the headset: Output from Headset section: profiles: a2dp_sink: High Fidelity Playback (A2DP Sink) (priority 40, available: unknown) headset_head_unit: Headset Head Unit (HSP/HFP) (priority 30, available: no) off: Off (priority 0, available: yes) active profile: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1768625/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1846955] [NEW] Gnome crashes on adding system title bars to Chrome under Wayland in EOAN
Public bug reported: To reproduce: 1. Open Chrome under Wayland session in 19.10 beta 2. Maximize Chrome 3. Right click on empty space beside tabs and from the menu select "Use system titlebar and borders" Chrome immediately crashes and gnome begins to become less and less responsive until it finally freezes. Does not occur when doing the equivalent in Firefox BTW - Gnome is super responsive in Eoan! Keep up the good work. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Attachment added: "journalctl output for the specified event" https://bugs.launchpad.net/bugs/1846955/+attachment/5294771/+files/journal.txt ** Summary changed: - Gnome crashes on adding system title bars under Wayland in EOAN + Gnome crashes on adding system title bars to Chrome under Wayland in EOAN -- 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/1846955 Title: Gnome crashes on adding system title bars to Chrome under Wayland in EOAN Status in gnome-shell package in Ubuntu: New Bug description: To reproduce: 1. Open Chrome under Wayland session in 19.10 beta 2. Maximize Chrome 3. Right click on empty space beside tabs and from the menu select "Use system titlebar and borders" Chrome immediately crashes and gnome begins to become less and less responsive until it finally freezes. Does not occur when doing the equivalent in Firefox BTW - Gnome is super responsive in Eoan! Keep up the good work. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1846955/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1798400] Re: Regression: cannot use impress remote over bluetooth with ubuntu bionic
Here is a link to the code (& log) regarding the impress remote project: https://cgit.freedesktop.org/libreoffice/impress_remote/ I have a presentation upcoming in three days and really would have liked to use the remote feature to impress/wow the audience. There's not enough time for me to dig into the code and try to determine the state of bluetooth vis-a-vis Android and Impress. Looks like something that might require 10-20 hours to master just to assess. Agree: it doesn't behoove the project to advertise features which may not work, e.g. remote impress. Using Gentoo Linux (4.19.72-gentoo) on a Dell Inspiron 17 5000 laptop purchased October 2018 (Bluetooth 4) with net-wireless/bluez 5.50-r2 against an Android 7.0, kernel version 3.10.49, model LGL158VL -- 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/1798400 Title: Regression: cannot use impress remote over bluetooth with ubuntu bionic Status in LibreOffice: New Status in bluez package in Ubuntu: Confirmed Status in libreoffice package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in libreoffice package in Fedora: Unknown Bug description: Trying to use the impress remote (https://wiki.documentfoundation.org/Impress_Remote) over bluetooth with libreoffice over ubuntu bionic fails. The handset errors out that it cannot connect with Libreoffice on the computer even if the bluetooth adapter on the handset and on the computer are correctly paired. This does not seem to be an issue in the Libreoffice or in the impress remote code: - I have tested also past LibO versions - The Impress remote codebase has not changed recently This used to work on the same hardware (headset and laptop) with ubuntu 16.04. Hence the issue seems to be in a regression in the ubuntu bluetooth stack. To replicate: 1) Install Libreoffice on Ubuntu bionic (either from the ubuntu repo or with the deb packages from the document fundation) 2) Assure that your computer has bluetooth 3) Install impress remote on an android handset (either from the play store of via fdroid) 4) Assure that "remote control" is enabled in impress Tools>Options>Impress>General 5) Pair the bluetooth adapters in the laptop and in the computer 6) Open a presentation on the laptop 7) Open the remote on the handset, got to the bluetooth pane see the computer there, touch it 8) See the impress remote erroring out Most likely you will also get a bluetooth error on dmesg RFCOMM server failed for LibreOffice Impress Remote: rfcomm_bind: Address already in use (98) Same issue was reported for fedora ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: KDE Date: Wed Oct 17 16:57:29 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-12 (1769 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Notebook W740SU ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-36-generic root=/dev/mapper/zagar_ssd--vg-root ro quiet splash resume=/dev/zagar_ssd-vg/swap_1 acpi_backlight=vendor vt.handoff=1 SourcePackage: bluez UpgradeStatus: Upgraded to bionic on 2018-06-08 (131 days ago) dmi.bios.date: 10/02/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W740SU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd10/02/2013:svnNotebook:pnW740SU:pvrNotApplicable:rvnNotebook:rnW740SU:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: W740SU dmi.product.version: Not Applicable dmi.sys.vendor: Notebook hciconfig: hci0:Type: Primary Bus: USB BD Address: 00:C2:C6:1A:28:71 ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN ISCAN RX bytes:245088 acl:15156 sco:0 events:1266 errors:0 TX bytes:15571 acl:402 sco:1 commands:131 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1798400/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1846944] [NEW] Nextcloud client app indicator icon not visible in 19.10 Eoan Beta
Public bug reported: When running the Nextcloud Client (flatpak or PPA) in Eoan Beta, its app indicator icon is never displayed in the notification area. Other apps sch as Steam and Skype have their indicator icons displayed fine. Output from the command line when running the flatpak produces the following error: Qt: Session management error: None of the authentication protocols specified are supported I can duplicate this issue 100% of the time. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell-extension-appindicator 30-1 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: Sun Oct 6 13:35:44 2019 InstallationDate: Installed on 2019-09-23 (12 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all SourcePackage: gnome-shell-extension-appindicator UpgradeStatus: Upgraded to eoan on 2019-09-27 (8 days ago) ** Affects: gnome-shell-extension-appindicator (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1846944 Title: Nextcloud client app indicator icon not visible in 19.10 Eoan Beta Status in gnome-shell-extension-appindicator package in Ubuntu: New Bug description: When running the Nextcloud Client (flatpak or PPA) in Eoan Beta, its app indicator icon is never displayed in the notification area. Other apps sch as Steam and Skype have their indicator icons displayed fine. Output from the command line when running the flatpak produces the following error: Qt: Session management error: None of the authentication protocols specified are supported I can duplicate this issue 100% of the time. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell-extension-appindicator 30-1 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: Sun Oct 6 13:35:44 2019 InstallationDate: Installed on 2019-09-23 (12 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all SourcePackage: gnome-shell-extension-appindicator UpgradeStatus: Upgraded to eoan on 2019-09-27 (8 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1846944/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1844853] Re: IBus no longer works in Qt applications after upgrade
The issue is present in ibus version 1.5.17-3ubuntu5.2 running in KDE Neon (based on Ubuntu 18.04) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1844853 Title: IBus no longer works in Qt applications after upgrade Status in ibus: New Status in ibus package in Ubuntu: Fix Released Status in ibus package in Debian: Confirmed Bug description: Kubuntu Release 18.04.3 LTS Expected behavior: ibus continues working as before after applying security update 1.5.17-ubuntu5.1 from version 1.5.17-ubuntu5. Observed behavior: ibus is not usable anymore in Qt applications. After updating ibus and the related packages ibus-gtk, ibus-gtk3, libibus-1.0-5 and gir1.2-ibus-1.0 all from version 1.5.17-ubuntu5 to 1.5.17-ubuntu5.1, I can no longer use ibus in Qt applications. Using shift-space no longer changes the selected input method and even when i switch to the mozc input method in a gtk application, i can not use it in any Qt applications. When starting qtconfig in a terminal, I also get the following message: Bus::open: Connect ibus failed! IBusInputContext::createInputContext: no connection to ibus-daemon This bug was not present in version 1.5.17-3ubuntu5 and I also confirmed that downgrading the packages to version 1.5.17-3ubuntu4 restores ibus functionality in Qt applications. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ibus 1.5.17-3ubuntu5.1 ProcVersionSignature: Ubuntu 5.0.0-30.32~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: KDE Date: Sat Sep 21 07:58:56 2019 InstallationDate: Installed on 2019-06-28 (84 days ago) InstallationMedia: Kubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: ibus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ibus/+bug/1844853/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1846890] Re: Pluma: unable to enable plugins External tools, Python Console, Quick Open, Snippets) because of missed /usr/lib/x86_64-linux-gnu/libpeas-1.0/loaders/libpythonload
The attachment "Debdiff to fix Python 2 loader name" seems to be a debdiff. The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff. If the attachment isn't a patch, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issue please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libpeas in Ubuntu. https://bugs.launchpad.net/bugs/1846890 Title: Pluma: unable to enable plugins External tools, Python Console, Quick Open, Snippets) because of missed /usr/lib/x86_64-linux- gnu/libpeas-1.0/loaders/libpythonloader.so Status in libpeas package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Install Ubuntu 19.10 2. Launch Pluma 3. Go to Edit -> Preferences, switch to Plugins tab 4. Try enable all plugins by checking their checkmarks Expected results: * all plugins are enabled without errors or warnings; Actual results: * plugin(s) are not enabled, show the following errors in `pluma`'s terminal: ``` $ pluma (pluma:1685): libpeas-WARNING **: 19:20:59.204: Failed to load module 'pythonloader': /usr/lib/x86_64-linux- gnu/libpeas-1.0/loaders/libpythonloader.so: cannot open shared object file: No such file or directory (pluma:1685): libpeas-WARNING **: 19:20:59.205: Could not load plugin loader 'python' ``` Note: in previous releases the `libpythonloader.so` was located in libpeas-1.0-python2loader package (see https://packages.ubuntu.com/search?suite=disco=amd64=exactfilename=contents=libpythonloader.so ) but this file is missed in 19.10 repository. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: pluma 1.22.2-0ubuntu1 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: MATE Date: Sat Oct 5 19:23:02 2019 InstallationDate: Installed on 2019-10-05 (0 days ago) InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20191004) SourcePackage: pluma UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libpeas/+bug/1846890/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1846890] Re: Pluma: unable to enable plugins External tools, Python Console, Quick Open, Snippets) because of missed /usr/lib/x86_64-linux-gnu/libpeas-1.0/loaders/libpythonload
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: libpeas (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libpeas in Ubuntu. https://bugs.launchpad.net/bugs/1846890 Title: Pluma: unable to enable plugins External tools, Python Console, Quick Open, Snippets) because of missed /usr/lib/x86_64-linux- gnu/libpeas-1.0/loaders/libpythonloader.so Status in libpeas package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Install Ubuntu 19.10 2. Launch Pluma 3. Go to Edit -> Preferences, switch to Plugins tab 4. Try enable all plugins by checking their checkmarks Expected results: * all plugins are enabled without errors or warnings; Actual results: * plugin(s) are not enabled, show the following errors in `pluma`'s terminal: ``` $ pluma (pluma:1685): libpeas-WARNING **: 19:20:59.204: Failed to load module 'pythonloader': /usr/lib/x86_64-linux- gnu/libpeas-1.0/loaders/libpythonloader.so: cannot open shared object file: No such file or directory (pluma:1685): libpeas-WARNING **: 19:20:59.205: Could not load plugin loader 'python' ``` Note: in previous releases the `libpythonloader.so` was located in libpeas-1.0-python2loader package (see https://packages.ubuntu.com/search?suite=disco=amd64=exactfilename=contents=libpythonloader.so ) but this file is missed in 19.10 repository. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: pluma 1.22.2-0ubuntu1 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: MATE Date: Sat Oct 5 19:23:02 2019 InstallationDate: Installed on 2019-10-05 (0 days ago) InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20191004) SourcePackage: pluma UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libpeas/+bug/1846890/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1846890] Re: Pluma: unable to enable plugins External tools, Python Console, Quick Open, Snippets) because of missed /usr/lib/x86_64-linux-gnu/libpeas-1.0/loaders/libpythonload
This issue is due to an upstream (erroneous) change in libpeas 1.24.
The only reference to python loader is at https://github.com/mate-
desktop/pluma/blob/1.22/pluma/pluma-plugins-engine.c#L63
```
pluma/pluma-plugins-engine.c:63
peas_engine_enable_loader (PEAS_ENGINE (engine), "python");
```
Looking at the blibpeas code here's that function:
https://github.com/GNOME/libpeas/blob/master/libpeas/peas-engine.c#L943
```
libpeas/peas-engine.c:943
* peas_engine_enable_loader:
```
It still references `python` as Python 2 loader and then it calls
peas_utils_get_loader_id to get loader id by name
https://github.com/GNOME/libpeas/blob/master/libpeas/peas-utils.c#L257
```
libpeas/peas-utils.c:257
peas_utils_get_loader_id (const gchar *loader)
```
That function looks at all_plugin_loaders array with all known loaders
names
```
static const gchar *all_plugin_loaders[] = {
"c", "lua5.1", "python", "python3"
};
```
The Python 2 loader is still named `python` this means, if we change python
loader name to python2 in Pluma, libpeas won't find it.

This is where the loader library name was changed without changing the loader
name in the list of loaders:
https://github.com/GNOME/libpeas/commit/dabb83a2e217694220a55c2019a081365a4a1288#diff-ad34de593e22ad307274456f3b4724a3
After that, they dropped autotools build files where you can see that the
library was called libpythonloader in the makefile:
https://github.com/GNOME/libpeas/commit/eadd10dbdd5b9b6b0488aeb41d4bf1592ba9d5d2#diff-f2abb793309b0ed9d8e63c1e038b1e31

Here is a test case:
```
#include
int
main (int argc, char **argv) {
PeasEngine *engine = peas_engine_get_default ();
peas_engine_enable_loader (engine, "python2");
return 0;
}
```
Build the above with:
```
gcc -Wall -o peas-test peas-test.c `pkg-config --cflags libpeas-1.0`
`pkg-config --libs libpeas-1.0`
```
And run it:
```
$ ./peas-test
```
You'll get this output:
```
(process:13201): libpeas-WARNING **: 13:25:09.920: Failed to enable unknown
plugin loader 'python2'
```
And with that, we can confirm that the `python2` loader won't be found
by libpeas and that the debdiff above is the correct way to fix this
issue.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libpeas in Ubuntu.
https://bugs.launchpad.net/bugs/1846890
Title:
Pluma: unable to enable plugins External tools, Python Console, Quick
Open, Snippets) because of missed /usr/lib/x86_64-linux-
gnu/libpeas-1.0/loaders/libpythonloader.so
Status in libpeas package in Ubuntu:
Confirmed
Bug description:
Steps to reproduce:
1. Install Ubuntu 19.10
2. Launch Pluma
3. Go to Edit -> Preferences, switch to Plugins tab
4. Try enable all plugins by checking their checkmarks
Expected results:
* all plugins are enabled without errors or warnings;
Actual results:
* plugin(s) are not enabled, show the following errors in `pluma`'s terminal:
```
$ pluma
(pluma:1685): libpeas-WARNING **: 19:20:59.204: Failed to load module
'pythonloader': /usr/lib/x86_64-linux-
gnu/libpeas-1.0/loaders/libpythonloader.so: cannot open shared object
file: No such file or directory
(pluma:1685): libpeas-WARNING **: 19:20:59.205: Could not load plugin loader
'python'
```
Note: in previous releases the `libpythonloader.so` was located in
libpeas-1.0-python2loader package (see
https://packages.ubuntu.com/search?suite=disco=amd64=exactfilename=contents=libpythonloader.so
) but this file is missed in 19.10 repository.
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: pluma 1.22.2-0ubuntu1
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: MATE
Date: Sat Oct 5 19:23:02 2019
InstallationDate: Installed on 2019-10-05 (0 days ago)
InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20191004)
SourcePackage: pluma
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libpeas/+bug/1846890/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1846890] Re: Pluma: unable to enable plugins External tools, Python Console, Quick Open, Snippets) because of missed /usr/lib/x86_64-linux-gnu/libpeas-1.0/loaders/libpythonload
** Attachment added: "Debdiff to fix Python 2 loader name" https://bugs.launchpad.net/ubuntu/+source/libpeas/+bug/1846890/+attachment/5294753/+files/libpeas-debdiff-eoan -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libpeas in Ubuntu. https://bugs.launchpad.net/bugs/1846890 Title: Pluma: unable to enable plugins External tools, Python Console, Quick Open, Snippets) because of missed /usr/lib/x86_64-linux- gnu/libpeas-1.0/loaders/libpythonloader.so Status in libpeas package in Ubuntu: New Bug description: Steps to reproduce: 1. Install Ubuntu 19.10 2. Launch Pluma 3. Go to Edit -> Preferences, switch to Plugins tab 4. Try enable all plugins by checking their checkmarks Expected results: * all plugins are enabled without errors or warnings; Actual results: * plugin(s) are not enabled, show the following errors in `pluma`'s terminal: ``` $ pluma (pluma:1685): libpeas-WARNING **: 19:20:59.204: Failed to load module 'pythonloader': /usr/lib/x86_64-linux- gnu/libpeas-1.0/loaders/libpythonloader.so: cannot open shared object file: No such file or directory (pluma:1685): libpeas-WARNING **: 19:20:59.205: Could not load plugin loader 'python' ``` Note: in previous releases the `libpythonloader.so` was located in libpeas-1.0-python2loader package (see https://packages.ubuntu.com/search?suite=disco=amd64=exactfilename=contents=libpythonloader.so ) but this file is missed in 19.10 repository. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: pluma 1.22.2-0ubuntu1 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: MATE Date: Sat Oct 5 19:23:02 2019 InstallationDate: Installed on 2019-10-05 (0 days ago) InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20191004) SourcePackage: pluma UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libpeas/+bug/1846890/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1846890] Re: Unable to enable plugins External tools, Python Console, Quick Open, Snippets) because of missed /usr/lib/x86_64-linux-gnu/libpeas-1.0/loaders/libpythonloader.so
** Package changed: pluma (Ubuntu) => libpeas (Ubuntu) ** Summary changed: - Unable to enable plugins External tools, Python Console, Quick Open, Snippets) because of missed /usr/lib/x86_64-linux-gnu/libpeas-1.0/loaders/libpythonloader.so + Pluma: unable to enable plugins External tools, Python Console, Quick Open, Snippets) because of missed /usr/lib/x86_64-linux-gnu/libpeas-1.0/loaders/libpythonloader.so -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libpeas in Ubuntu. https://bugs.launchpad.net/bugs/1846890 Title: Pluma: unable to enable plugins External tools, Python Console, Quick Open, Snippets) because of missed /usr/lib/x86_64-linux- gnu/libpeas-1.0/loaders/libpythonloader.so Status in libpeas package in Ubuntu: New Bug description: Steps to reproduce: 1. Install Ubuntu 19.10 2. Launch Pluma 3. Go to Edit -> Preferences, switch to Plugins tab 4. Try enable all plugins by checking their checkmarks Expected results: * all plugins are enabled without errors or warnings; Actual results: * plugin(s) are not enabled, show the following errors in `pluma`'s terminal: ``` $ pluma (pluma:1685): libpeas-WARNING **: 19:20:59.204: Failed to load module 'pythonloader': /usr/lib/x86_64-linux- gnu/libpeas-1.0/loaders/libpythonloader.so: cannot open shared object file: No such file or directory (pluma:1685): libpeas-WARNING **: 19:20:59.205: Could not load plugin loader 'python' ``` Note: in previous releases the `libpythonloader.so` was located in libpeas-1.0-python2loader package (see https://packages.ubuntu.com/search?suite=disco=amd64=exactfilename=contents=libpythonloader.so ) but this file is missed in 19.10 repository. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: pluma 1.22.2-0ubuntu1 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: MATE Date: Sat Oct 5 19:23:02 2019 InstallationDate: Installed on 2019-10-05 (0 days ago) InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20191004) SourcePackage: pluma UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libpeas/+bug/1846890/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1846890] [NEW] Unable to enable plugins External tools, Python Console, Quick Open, Snippets) because of missed /usr/lib/x86_64-linux-gnu/libpeas-1.0/loaders/libpythonloader.so
You have been subscribed to a public bug: Steps to reproduce: 1. Install Ubuntu 19.10 2. Launch Pluma 3. Go to Edit -> Preferences, switch to Plugins tab 4. Try enable all plugins by checking their checkmarks Expected results: * all plugins are enabled without errors or warnings; Actual results: * plugin(s) are not enabled, show the following errors in `pluma`'s terminal: ``` $ pluma (pluma:1685): libpeas-WARNING **: 19:20:59.204: Failed to load module 'pythonloader': /usr/lib/x86_64-linux- gnu/libpeas-1.0/loaders/libpythonloader.so: cannot open shared object file: No such file or directory (pluma:1685): libpeas-WARNING **: 19:20:59.205: Could not load plugin loader 'python' ``` Note: in previous releases the `libpythonloader.so` was located in libpeas-1.0-python2loader package (see https://packages.ubuntu.com/search?suite=disco=amd64=exactfilename=contents=libpythonloader.so ) but this file is missed in 19.10 repository. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: pluma 1.22.2-0ubuntu1 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: MATE Date: Sat Oct 5 19:23:02 2019 InstallationDate: Installed on 2019-10-05 (0 days ago) InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20191004) SourcePackage: pluma UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libpeas (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- Unable to enable plugins External tools, Python Console, Quick Open, Snippets) because of missed /usr/lib/x86_64-linux-gnu/libpeas-1.0/loaders/libpythonloader.so https://bugs.launchpad.net/bugs/1846890 You received this bug notification because you are a member of Desktop Packages, which is subscribed to libpeas in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1846940] [NEW] Loop in libreoffice-calc when scrolling to top of spreadsheet
Public bug reported: Have a spreadsheet used in many past release of calc that is now failing. When opening this sheet and if not currently at the top of the sheet using the mouse wheel to move to the top (top line to the top of the window) soffice.bin goes to 100% cpu and stays there. Can't use the mouse wheel to move off of the top line. Can move off the top line by using the mouse and scroll bar. As soon as you are off the top line the loop in soffice.bin stops. This is the only sheet I can find that fails but it does fail on this laptop and also my desktop which is also running Ubuntu 19.10/libreoffice-calc-6.3.2.2. Adding failing spreadsheet file to this bug report. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: libreoffice-calc 1:6.3.2-0ubuntu2 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 nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Oct 6 06:35:42 2019 InstallationDate: Installed on 2019-10-03 (2 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20191001.2) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan ** Attachment added: "TheGrid.ods" https://bugs.launchpad.net/bugs/1846940/+attachment/5294731/+files/TheGrid.ods -- 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/1846940 Title: Loop in libreoffice-calc when scrolling to top of spreadsheet Status in libreoffice package in Ubuntu: New Bug description: Have a spreadsheet used in many past release of calc that is now failing. When opening this sheet and if not currently at the top of the sheet using the mouse wheel to move to the top (top line to the top of the window) soffice.bin goes to 100% cpu and stays there. Can't use the mouse wheel to move off of the top line. Can move off the top line by using the mouse and scroll bar. As soon as you are off the top line the loop in soffice.bin stops. This is the only sheet I can find that fails but it does fail on this laptop and also my desktop which is also running Ubuntu 19.10/libreoffice- calc-6.3.2.2. Adding failing spreadsheet file to this bug report. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: libreoffice-calc 1:6.3.2-0ubuntu2 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 nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Oct 6 06:35:42 2019 InstallationDate: Installed on 2019-10-03 (2 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20191001.2) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1846940/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1846941] [NEW] Since upgrading to Eoan Ermine the screen doesn't dim progressively before turning off and locking the PC, but at once.
Public bug reported: It wasn't behaving that way in Disco. Not sure if this issue belongs to X.org, but as that was the place for suspend/resume, i decided to place this bug here. If it's the wrong package, please help me in finding the correct one. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1) ApportVersion: 2.20.11-0ubuntu7 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' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Oct 6 13:46:25 2019 DistUpgraded: 2019-09-28 01:59:57,153 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] UHD Graphics 620 [1025:1193] Subsystem: Acer Incorporated [ALI] GP108M [GeForce MX150] [1025:119a] InstallationDate: Installed on 2019-07-23 (74 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04f2:b5f7 Chicony Electronics Co., Ltd HD WebCam Bus 001 Device 003: ID 8087:0aa7 Intel Corp. Bus 001 Device 002: ID :0538 USB OPTICAL MOUSE Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire A515-51G ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-13-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to eoan on 2019-09-27 (8 days ago) dmi.bios.date: 01/03/2019 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.02 dmi.board.asset.tag: Type2 - Board Serial Number dmi.board.name: Charmander_KL dmi.board.vendor: KBL dmi.board.version: V2.02 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.02 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.02:bd01/03/2019:svnAcer:pnAspireA515-51G:pvrV2.02:rvnKBL:rnCharmander_KL:rvrV2.02:cvnAcer:ct10:cvrV2.02: dmi.product.family: Aspire 5 dmi.product.name: Aspire A515-51G dmi.product.sku: dmi.product.version: V2.02 dmi.sys.vendor: Acer 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 19.2.0-1ubuntu2 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20190820-0ubuntu3 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: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan possible-manual-nvidia-install third-party-packages ubuntu ** Summary changed: - Since upgrading to Eoan Ermine the screen doesn't dim progressively before going to sleep, but at once. + Since upgrading to Eoan Ermine the screen doesn't dim progressively before turning off and locking the PC, but at once. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1846941 Title: Since upgrading to Eoan Ermine the screen doesn't dim progressively before turning off and locking the PC, but at once. Status in xorg package in Ubuntu: New Bug description: It wasn't behaving that way in Disco. Not sure if this issue belongs to X.org, but as that was the place for suspend/resume, i decided to place this bug here. If it's the wrong package, please help me in finding the correct one. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume
[Desktop-packages] [Bug 1846094] Re: package nvidia-dkms-430 430.50-0ubuntu1 failed to install/upgrade: »installiertes nvidia-dkms-430-Skript des Paketes post-installation«-Unterprozess gab den Fehler
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-430 (Ubuntu) Status: New => Confirmed -- 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/1846094 Title: package nvidia-dkms-430 430.50-0ubuntu1 failed to install/upgrade: »installiertes nvidia-dkms-430-Skript des Paketes post- installation«-Unterprozess gab den Fehlerwert 10 zurück Status in nvidia-graphics-drivers-430 package in Ubuntu: Confirmed Bug description: E: Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 3989 (apt) - open (11: Die Ressource ist zur Zeit nicht verfügbar) N: Be aware that removing the lock file is not a solution and may break your system. E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it? ProblemType: Package DistroRelease: Ubuntu 19.10 Package: nvidia-dkms-430 430.50-0ubuntu1 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 Date: Mon Sep 30 20:56:20 2019 ErrorMessage: »installiertes nvidia-dkms-430-Skript des Paketes post-installation«-Unterprozess gab den Fehlerwert 10 zurück InstallationDate: Installed on 2019-08-14 (47 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Python3Details: /usr/bin/python3.7, Python 3.7.4+, 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: »installiertes nvidia-dkms-430-Skript des Paketes post-installation«-Unterprozess gab den Fehlerwert 10 zurück UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-430/+bug/1846094/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1842882] Re: gnome-control-center no longer shows all the xrandr resolutions
I think this might have been caused by the Pop OS! PPA (ppa:system76/pop). I think I must have installed it months ago for some icon set without realising that it loads a ton of other stuff. Its latest iteration of g-c-c segfaults, which is how I realised what was going on. Purging the PPA and using g-c-c 1:3.34.0.1-1ubuntu2, I can now see all the resolutions again. ** Changed in: mutter (Ubuntu) Status: New => Invalid -- 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/1842882 Title: gnome-control-center no longer shows all the xrandr resolutions Status in mutter package in Ubuntu: Invalid Bug description: Very recently gnome-control-center started only showing a subset of the available screen resolutions. I'll attach a screenshot and also the xrandr dump to show what I mean, eg you can see that the 2048x1152 (16:9) resolution is now missing. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-control-center 1:3.33.90-1ubuntu2 ProcVersionSignature: Ubuntu 5.2.0-15.16-generic 5.2.9 Uname: Linux 5.2.0-15-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Sep 5 15:56:47 2019 InstallationDate: Installed on 2019-07-01 (65 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190606) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1842882/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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] [NEW] [HDA-Intel - HD-Audio Generic, playback] No sound at all nor audio record at all too
Public bug reported: 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 ** Affects: alsa-driver (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 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 :
