[Desktop-packages] [Bug 1906137] Re: gnome-shell on 20.10 crashes all the time
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Bug reporting is mostly about finding & fixing problems thus preventing
future users from hitting the same bug.
If you want a support site ("how do I track down..") you can use
https://answers.launchpad.net/ubuntu. You can also find help with your
problem in the support forum of your local Ubuntu community
http://loco.ubuntu.com/ or asking at https://askubuntu.com or
https://ubuntuforums.org, or for more support options please look at
https://discourse.ubuntu.com/t/community-support/709
--
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/1906137
Title:
gnome-shell on 20.10 crashes all the time
Status in gnome-shell package in Ubuntu:
New
Bug description:
this is probably a dupe of a bunch of other gnome-shell crashing bugs.
just noting that since upgrading to 20.10, both my systems (which use
the nvidia binary X drivers) have gnome-shell crashing multiple times
a day. it restarts fine, but while it's crashing it locks up the whole
system for a minute or two. no idea why the release in 20.10 is so
much more unstable than 20.04, but here we are.
as a starting point, how do I track down what it considers the cause
of the crashes? I can't discern anything particularly useful from
`journalctl` at first glance. is there a specific error message I can
search for in all the noise to find where it crashed and see what
happened right before that? I see a lot of these in the logs, but they
seem to be non-fatal, and they also don't print out any actual stack
traces to examine:
Nov 28 22:07:16 boxxy gnome-shell[222384]: == Stack trace for context
0x55995401f220 ==
Nov 28 22:07:16 boxxy gnome-shell[222384]: == Stack trace for context
0x55995401f220 ==
Nov 28 22:07:16 boxxy gnome-shell[222384]: == Stack trace for context
0x55995401f220 ==
Nov 28 22:07:16 boxxy gnome-shell[222384]: == Stack trace for context
0x55995401f220 ==
Nov 28 22:07:16 boxxy gnome-shell[222384]: == Stack trace for context
0x55995401f220 ==
Nov 28 22:07:16 boxxy gnome-shell[222384]: == Stack trace for context
0x55995401f220 ==
Nov 28 22:07:16 boxxy gnome-shell[222384]: == Stack trace for context
0x55995401f220 ==
Nov 28 22:07:16 boxxy gnome-shell[222384]: == Stack trace for context
0x55995401f220 ==
Nov 28 22:07:16 boxxy gnome-shell[222384]: == Stack trace for context
0x55995401f220 ==
ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: gnome-shell 3.38.1-1ubuntu1.1
ProcVersionSignature: Ubuntu 5.8.0-29.31-lowlatency 5.8.14
Uname: Linux 5.8.0-29-lowlatency x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset
nvidia
ApportVersion: 2.20.11-0ubuntu50.2
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sat Nov 28 22:11:09 2020
DisplayManager: gdm3
InstallationDate: Installed on 2020-07-15 (137 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
RelatedPackageVersions: mutter-common 3.38.1-1ubuntu1
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to groovy on 2020-10-24 (36 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1906137/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1906137] [NEW] gnome-shell on 20.10 crashes all the time
Public bug reported: this is probably a dupe of a bunch of other gnome-shell crashing bugs. just noting that since upgrading to 20.10, both my systems (which use the nvidia binary X drivers) have gnome-shell crashing multiple times a day. it restarts fine, but while it's crashing it locks up the whole system for a minute or two. no idea why the release in 20.10 is so much more unstable than 20.04, but here we are. as a starting point, how do I track down what it considers the cause of the crashes? I can't discern anything particularly useful from `journalctl` at first glance. is there a specific error message I can search for in all the noise to find where it crashed and see what happened right before that? I see a lot of these in the logs, but they seem to be non-fatal, and they also don't print out any actual stack traces to examine: Nov 28 22:07:16 boxxy gnome-shell[222384]: == Stack trace for context 0x55995401f220 == Nov 28 22:07:16 boxxy gnome-shell[222384]: == Stack trace for context 0x55995401f220 == Nov 28 22:07:16 boxxy gnome-shell[222384]: == Stack trace for context 0x55995401f220 == Nov 28 22:07:16 boxxy gnome-shell[222384]: == Stack trace for context 0x55995401f220 == Nov 28 22:07:16 boxxy gnome-shell[222384]: == Stack trace for context 0x55995401f220 == Nov 28 22:07:16 boxxy gnome-shell[222384]: == Stack trace for context 0x55995401f220 == Nov 28 22:07:16 boxxy gnome-shell[222384]: == Stack trace for context 0x55995401f220 == Nov 28 22:07:16 boxxy gnome-shell[222384]: == Stack trace for context 0x55995401f220 == Nov 28 22:07:16 boxxy gnome-shell[222384]: == Stack trace for context 0x55995401f220 == ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.38.1-1ubuntu1.1 ProcVersionSignature: Ubuntu 5.8.0-29.31-lowlatency 5.8.14 Uname: Linux 5.8.0-29-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Nov 28 22:11:09 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-07-15 (137 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) RelatedPackageVersions: mutter-common 3.38.1-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to groovy on 2020-10-24 (36 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy -- 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/1906137 Title: gnome-shell on 20.10 crashes all the time Status in gnome-shell package in Ubuntu: New Bug description: this is probably a dupe of a bunch of other gnome-shell crashing bugs. just noting that since upgrading to 20.10, both my systems (which use the nvidia binary X drivers) have gnome-shell crashing multiple times a day. it restarts fine, but while it's crashing it locks up the whole system for a minute or two. no idea why the release in 20.10 is so much more unstable than 20.04, but here we are. as a starting point, how do I track down what it considers the cause of the crashes? I can't discern anything particularly useful from `journalctl` at first glance. is there a specific error message I can search for in all the noise to find where it crashed and see what happened right before that? I see a lot of these in the logs, but they seem to be non-fatal, and they also don't print out any actual stack traces to examine: Nov 28 22:07:16 boxxy gnome-shell[222384]: == Stack trace for context 0x55995401f220 == Nov 28 22:07:16 boxxy gnome-shell[222384]: == Stack trace for context 0x55995401f220 == Nov 28 22:07:16 boxxy gnome-shell[222384]: == Stack trace for context 0x55995401f220 == Nov 28 22:07:16 boxxy gnome-shell[222384]: == Stack trace for context 0x55995401f220 == Nov 28 22:07:16 boxxy gnome-shell[222384]: == Stack trace for context 0x55995401f220 == Nov 28 22:07:16 boxxy gnome-shell[222384]: == Stack trace for context 0x55995401f220 == Nov 28 22:07:16 boxxy gnome-shell[222384]: == Stack trace for context 0x55995401f220 == Nov 28 22:07:16 boxxy gnome-shell[222384]: == Stack trace for context 0x55995401f220 == Nov 28 22:07:16 boxxy gnome-shell[222384]: == Stack trace for context 0x55995401f220 == ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.38.1-1ubuntu1.1 ProcVersionSignature: Ubuntu 5.8.0-29.31-lowlatency 5.8.14 Uname: Linux 5.8.0-29-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Nov 28 22:11:09 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-07-15 (137 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal F
[Desktop-packages] [Bug 1891684] Re: [amdgpu] Screen flickers after resuming from suspend
[Expired for xserver-xorg-video-amdgpu (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xserver-xorg-video-amdgpu (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1891684 Title: [amdgpu] Screen flickers after resuming from suspend Status in linux package in Ubuntu: Expired Status in xserver-xorg-video-amdgpu package in Ubuntu: Expired Bug description: when computer is coming out of suspension mode, i get terrible screen flickers. Only way i have worked around this is a reboot. This video card is from sapphire Nitro + SE 5700xt ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Aug 14 12:16:42 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] [1002:731f] (rev c1) (prog-if 00 [VGA controller]) Subsystem: Sapphire Technology Limited Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] [1da2:e410] InstallationDate: Installed on 2020-06-08 (66 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: System manufacturer System Product Name ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=de7b87e0-cf04-4f9f-978e-3646f7e7266d ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/17/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2203 dmi.board.asset.tag: Default string dmi.board.name: TUF GAMING X570-PLUS 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.:bvr2203:bd06/17/2020:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGX570-PLUS: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.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-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/linux/+bug/1891684/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1894666] Re: Gnome high CPU preventing login after screen lock
[Expired for gnome-shell-extension-ubuntu-dock (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: Incomplete => Expired -- 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/1894666 Title: Gnome high CPU preventing login after screen lock Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Expired Bug description: I have configured my PC to lock the screen automatically after a period of inactivity. Often when I come back to my PC I'm unable to login due to gnome shell running at 100% CPU (according to htop). The only way I can log in is to SSH to the machine from another PC and kill the gnome shell task running at 100% Other than noting this only happens when I try and unlock the screen I haven't been able to find any pattern which can explain this behaviour. I've never had problems with gnome shell while using the PC. Some info about the machine Ubuntu 20.04, Nvidia drivers, 4k monitors ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55 Uname: Linux 5.4.0-45-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Sep 7 22:01:37 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-09-05 (2 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.4-0ubuntu0.20.04.2 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-extension-ubuntu-dock/+bug/1894666/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1897273] Re: booting ubuntu groovy daily; display unusuable
[Expired for ubuntu-meta (Ubuntu) because there has been no activity for 60 days.] ** Changed in: ubuntu-meta (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1897273 Title: booting ubuntu groovy daily; display unusuable Status in ubuntu-meta package in Ubuntu: Expired Bug description: booting Ubuntu daily on dell [optiplex] 990 (i7-2600, 16gb, nvidia geforce gt 6600 gt) Media validation occurs as expected, passes the Ubuntu logo is as expected then I get a Ubuntu background type color and the session is now unusable The first display (after checks etc) occur is https://photos.app.goo.gl/gHgb98LTgGiWtMEw7 If left, i'll eventually get a purple screen and cursor, however nothing that responds as expected. No usable session, but screen is there, background a solid Ubuntu color, with normal cursor; alas nothing more. By switching to a terminal, I can check that no squashfs errors occurred & explore the system (including file this bug), however switching back gets me screens like https://photos.app.goo.gl/LJg4qvS7VajRny4e8 followed by hitting CTRL+ALT+T to open a terminal and the screen changes to https://photos.app.goo.gl/PJQxSABrNwg6UNGW9 The CTRL+ALT+T was recognized, as the terminal can be seen in the pinky area top left of screen, but it's not usable... I wonder if it's the screensaver kicking in that screws up the session, but I've not worked that up yet. I've been unable to watch the machine the whole time so I've not worked out pattern. ( FYI: this is not the first boot or attempt. This has occurred now three times tried (same iso, just rebooting machine). My intention tonight was explore https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1897173 via install on this box alas I can't install with it performing like this. A number of QA-test installs have been run on this system today, Lubuntu had no issues, Xubuntu failed due 1897173 with readable screens ) ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: ubuntu-desktop 1.457 ProcVersionSignature: Ubuntu 5.8.0-19.20-generic 5.8.8 Uname: Linux 5.8.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu47 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.452 Date: Fri Sep 25 11:58:18 2020 LiveMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200925) ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1897273/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1896815] Re: Old Arabic Fonts are not working
[Expired for xorg (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1896815 Title: Old Arabic Fonts are not working Status in xorg package in Ubuntu: Expired Bug description: Hello, Old Arabic Fonts (not MS fonts) were running on MS Word. they can not working on ubuntu. they listed in LO Writer , but they are not running in all kubuntu 20.10 applications. I used fc-cache for install them. but they are not configured for running. Thank You ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4 Uname: Linux 5.8.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CasperVersion: 1.452 CompositorRunning: None CurrentDesktop: KDE CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Wed Sep 23 18:31:51 2020 DistUpgraded: Fresh install DistroCodename: groovy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1462:7850] LiveMediaBuild: Kubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200922) MachineType: MSI MS-7850 ProcEnviron: LANGUAGE= PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ar_EG.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/02/2013 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V2.4 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B85-G41 PC Mate(MS-7850) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV2.4:bd12/02/2013:br4.6:svnMSI:pnMS-7850:pvr1.0:rvnMSI:rnB85-G41PCMate(MS-7850):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7850 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.1.7-1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-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/+bug/1896815/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1891684] Re: [amdgpu] Screen flickers after resuming from suspend
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1891684 Title: [amdgpu] Screen flickers after resuming from suspend Status in linux package in Ubuntu: Expired Status in xserver-xorg-video-amdgpu package in Ubuntu: Expired Bug description: when computer is coming out of suspension mode, i get terrible screen flickers. Only way i have worked around this is a reboot. This video card is from sapphire Nitro + SE 5700xt ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Aug 14 12:16:42 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] [1002:731f] (rev c1) (prog-if 00 [VGA controller]) Subsystem: Sapphire Technology Limited Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] [1da2:e410] InstallationDate: Installed on 2020-06-08 (66 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: System manufacturer System Product Name ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=de7b87e0-cf04-4f9f-978e-3646f7e7266d ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/17/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2203 dmi.board.asset.tag: Default string dmi.board.name: TUF GAMING X570-PLUS 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.:bvr2203:bd06/17/2020:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGX570-PLUS: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.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-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/linux/+bug/1891684/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1897569] Re: package libx11-6 2:1.6.9-2ubuntu1 failed to install/upgrade: el subproceso dpkg-deb --control devolvió el código de salida de error 2
[Expired for libx11 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: libx11 (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libx11 in Ubuntu. https://bugs.launchpad.net/bugs/1897569 Title: package libx11-6 2:1.6.9-2ubuntu1 failed to install/upgrade: el subproceso dpkg-deb --control devolvió el código de salida de error 2 Status in libx11 package in Ubuntu: Expired Bug description: I was doing things in mu ubuntu,when this problem appears,i don't know more about that problem,thats the problem i had ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libx11-6 2:1.6.9-2ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CompositorRunning: None Date: Mon Sep 28 15:15:50 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DpkgTerminalLog: [1mdpkg-deb:[0m [1;31merror:[0m `/tmp/apt-dpkg-install-aFUkKT/00-libx11-6_2%3a1.6.9-2ubuntu1.1_amd64.deb' no es un archivo en formato Debian [1mdpkg:[0m error al procesar el archivo /tmp/apt-dpkg-install-aFUkKT/00-libx11-6_2%3a1.6.9-2ubuntu1.1_amd64.deb (--unpack): el subproceso dpkg-deb --control devolvió el código de salida de error 2 ErrorMessage: el subproceso dpkg-deb --control devolvió el código de salida de error 2 GraphicsCard: NVIDIA Corporation GP107 [GeForce GTX 1050 3GB] [10de:1c83] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd GP107 [GeForce GTX 1050 3GB] [1458:379d] InstallationDate: Installed on 2020-09-28 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Micro-Star International Co., Ltd. MS-7A38 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=UUID=7fd02831-c266-4953-a0c3-f9d33241485c ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: libx11 Title: package libx11-6 2:1.6.9-2ubuntu1 failed to install/upgrade: el subproceso dpkg-deb --control devolvió el código de salida de error 2 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/22/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P.60 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450M BAZOOKA V2 (MS-7A38) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 5.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 5.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP.60:bd07/22/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A38:pvr5.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450MBAZOOKAV2(MS-7A38):rvr5.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr5.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A38 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 5.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-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/libx11/+bug/1897569/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1904237] Re: [regression] On-screen keyboard (OSK) on touch screen does not seem to work at all under Xorg in Focal
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/1904237 Title: [regression] On-screen keyboard (OSK) on touch screen does not seem to work at all under Xorg in Focal Status in gnome-shell package in Ubuntu: Confirmed Bug description: mutter 3.36.6-1ubuntu0.20.04.2 shows again the incorrect behavior that was fixed in https://bugs.launchpad.net/mutter/+bug/1880596 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-11-13 (2 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Package: mutter 3.36.6-1ubuntu0.20.04.2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ca_ES.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Tags: focal Uname: Linux 5.4.0-54-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-11-13 (3 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ca_ES.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 Tags: focal Uname: Linux 5.4.0-54-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1904237/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1906101] Re: no sound via speakers or headphone port on Carbon X1 6th
** Summary changed: - no sound via speakers or headphone port on Carbon X1 + no sound via speakers or headphone port on Carbon X1 6th -- 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/1906101 Title: no sound via speakers or headphone port on Carbon X1 6th Status in pulseaudio package in Ubuntu: New Bug description: I recently upgraded from 18.04 to 20.04. The sound worked without problems before upgrade, but now I don'get any sound at all from the speakers or the headphone jack. This seems similar to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860697 (although that bug is reported as resolved). I tried adding model=generic dmic_detect=0 to my alsa-base.conf, as reported in that ticket, but it did not help. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.8 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Sat Nov 28 18:36:36 2020 InstallationDate: Installed on 2018-07-27 (855 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: pulseaudio UpgradeStatus: Upgraded to focal on 2020-11-24 (4 days ago) dmi.bios.date: 10/13/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET75W (1.50 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KGCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN23ET75W(1.50):bd10/13/2020:svnLENOVO:pn20KGCTO1WW:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KGCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 6th dmi.product.name: 20KGCTO1WW dmi.product.sku: LENOVO_MT_20KG_BU_Think_FM_ThinkPad X1 Carbon 6th dmi.product.version: ThinkPad X1 Carbon 6th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1906101/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1835024]
Olivier reached out to me on Element. I looked at the patch and it seems the owner of `nsToolkitProfileService.cpp` is :mossop these days[1]. Would you have the bandwidth to review this patch, Dave? [1] https://hg.mozilla.org/mozilla- central/log/93fabad45659d172b723c9606215d3acaab54df1/toolkit/profile/nsToolkitProfileService.cpp -- 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/1835024 Title: firefox fails to use the default profile from classic snaps Status in Mozilla Firefox: Confirmed Status in snapd: Invalid Status in firefox package in Ubuntu: In Progress Bug description: Hi, I've recently made a clean install of Ubuntu 19.10 (development release) and have noticed that whenever I try to open a link from one of the snap apps (being it Slack or Skype) the links although opened in the default browser are being opened in a separate session of the web browser. I am using Firefox and it is installed as a regular deb package (default). This is wrong and causes issues with history, sessions and settings not being shared between these windows. Now I have the default browser I use + a separate session for Slack and another one for Skype. Not to mention Firefox also acts just like another Slack/Skype window so dash displays these as two instances of the same app. To reproduce: * Install Ubuntu 19.10 (not sure if upgrade from 19.04 would lead to the same behaviour). * Confirm FFox is installed as a regular deb package. * Install I suppose almost any snap app, although I've only reproduced this with Slack and Skype and haven't tried to install other apps. System monitor also seems to be installed but when trying to open links from the about window - translators - individual names, it seems to do nothing. On the other hand Gnome calculator which is also installed as a snap package opens the link in the about dialog correctly = in my default browser session. ``` :~# which gnome-calculator /snap/bin/gnome-calculator ``` Thank you very much for looking into that. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1835024/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1835024]
I'm Gtk peer so you can ask me to review linux/gtk code. -- 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/1835024 Title: firefox fails to use the default profile from classic snaps Status in Mozilla Firefox: Confirmed Status in snapd: Invalid Status in firefox package in Ubuntu: In Progress Bug description: Hi, I've recently made a clean install of Ubuntu 19.10 (development release) and have noticed that whenever I try to open a link from one of the snap apps (being it Slack or Skype) the links although opened in the default browser are being opened in a separate session of the web browser. I am using Firefox and it is installed as a regular deb package (default). This is wrong and causes issues with history, sessions and settings not being shared between these windows. Now I have the default browser I use + a separate session for Slack and another one for Skype. Not to mention Firefox also acts just like another Slack/Skype window so dash displays these as two instances of the same app. To reproduce: * Install Ubuntu 19.10 (not sure if upgrade from 19.04 would lead to the same behaviour). * Confirm FFox is installed as a regular deb package. * Install I suppose almost any snap app, although I've only reproduced this with Slack and Skype and haven't tried to install other apps. System monitor also seems to be installed but when trying to open links from the about window - translators - individual names, it seems to do nothing. On the other hand Gnome calculator which is also installed as a snap package opens the link in the about dialog correctly = in my default browser session. ``` :~# which gnome-calculator /snap/bin/gnome-calculator ``` Thank you very much for looking into that. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1835024/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1835024]
(In reply to Virginia Balducci from comment #2) > I'll add this ticket to the Widget GTK component in the hope their team can > take a look at this and share their feedback. Thanks for triaging Virginia. Unfortunately the patch¹ I submitted almost a month ago hasn't received any feedback yet. How do I get someone to look at it? ¹ https://phabricator.services.mozilla.com/D95171 -- 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/1835024 Title: firefox fails to use the default profile from classic snaps Status in Mozilla Firefox: Confirmed Status in snapd: Invalid Status in firefox package in Ubuntu: In Progress Bug description: Hi, I've recently made a clean install of Ubuntu 19.10 (development release) and have noticed that whenever I try to open a link from one of the snap apps (being it Slack or Skype) the links although opened in the default browser are being opened in a separate session of the web browser. I am using Firefox and it is installed as a regular deb package (default). This is wrong and causes issues with history, sessions and settings not being shared between these windows. Now I have the default browser I use + a separate session for Slack and another one for Skype. Not to mention Firefox also acts just like another Slack/Skype window so dash displays these as two instances of the same app. To reproduce: * Install Ubuntu 19.10 (not sure if upgrade from 19.04 would lead to the same behaviour). * Confirm FFox is installed as a regular deb package. * Install I suppose almost any snap app, although I've only reproduced this with Slack and Skype and haven't tried to install other apps. System monitor also seems to be installed but when trying to open links from the about window - translators - individual names, it seems to do nothing. On the other hand Gnome calculator which is also installed as a snap package opens the link in the about dialog correctly = in my default browser session. ``` :~# which gnome-calculator /snap/bin/gnome-calculator ``` Thank you very much for looking into that. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1835024/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode
Anyway, this is the output of hciconfig -a after I tried to switch to hsp/hfp mode from BlueMan Manager. hci0: Type: Primary Bus: USB BD Address: 5C:BA:EF:99:BC:3C ACL MTU: 1021:6 SCO MTU: 255:12 UP RUNNING RX bytes:2950504 acl:61 sco:0 events:421151 errors:0 TX bytes:259267232 acl:420944 sco:0 commands:188 errors:0 Features: 0xff 0xff 0xff 0xfe 0xdb 0xfd 0x7b 0x87 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH HOLD SNIFF PARK Link mode: SLAVE ACCEPT Name: 'RTK_BT_5.0' Class: 0x00 Service Classes: Unspecified Device Class: Miscellaneous, HCI Version: 5.1 (0xa) Revision: 0xc LMP Version: 5.1 (0xa) Subversion: 0x8822 Manufacturer: Realtek Semiconductor Corporation (93) -- 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/1871794 Title: [Bluetooth] No audio output/input in HSP/HFP mode Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: I'm testing with Sony bluetooth headset SBH20, works fine in A2DP profile, but I can't get audio input and output work in HSP/HFP profile. [Reproduce steps] 1. Scan and pair BT headset in Bluetooth setting 2. Switch to HSP/HFP profile in Sound setting 3. Test sound output/input [Machine information] ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Apr 9 16:26:52 2020 InstallationDate: Installed on 2020-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) SourcePackage: pulseaudio Symptom: audio Symptom_Card: SBH20 Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio Symptom_Type: No sound at all Title: [SBH20, recording] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/17/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.13 dmi.board.name: 0188D1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.13:bd09/17/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn0188D1:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 2-in-1 dmi.product.sku: 08B0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1871794/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode
@Hui Wang hsp/hfp mode doesn't fail, because it can't be activated. In Blueman it says that it's impossible to switch the profile. In Pulseaudio I have no options. -- 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/1871794 Title: [Bluetooth] No audio output/input in HSP/HFP mode Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: I'm testing with Sony bluetooth headset SBH20, works fine in A2DP profile, but I can't get audio input and output work in HSP/HFP profile. [Reproduce steps] 1. Scan and pair BT headset in Bluetooth setting 2. Switch to HSP/HFP profile in Sound setting 3. Test sound output/input [Machine information] ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Apr 9 16:26:52 2020 InstallationDate: Installed on 2020-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) SourcePackage: pulseaudio Symptom: audio Symptom_Card: SBH20 Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio Symptom_Type: No sound at all Title: [SBH20, recording] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/17/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.13 dmi.board.name: 0188D1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.13:bd09/17/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn0188D1:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 2-in-1 dmi.product.sku: 08B0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1871794/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1767454] Re: "Other Locations" does not automatically find Samba servers in Ubuntu 18.04
*** This bug is a duplicate of bug 1778322 *** https://bugs.launchpad.net/bugs/1778322 Ubuntu 20.04 LTS samba 2:4.11.6+dfsg-0ubuntu1.6 smbtree lists all my network shares but nautilus 3.36.3 does not see anything ? windows can occasionally see the ubuntu shares and I have to occasionally reload samba for nautilus to see the local share I have tried workgroup = WORKGROUP client min protocol = CORE client min protocol = NT1 server min protocol = NT1 client max protocol = SMB3 client lanman auth = yes ntlm auth = yes local master = yes preferred master = yes wins support = yes never had issues with Ubuntu 18.04 LTS -- 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/1767454 Title: "Other Locations" does not automatically find Samba servers in Ubuntu 18.04 Status in dolphin: Unknown Status in gvfs package in Ubuntu: Fix Released Status in samba package in Ubuntu: Invalid Bug description: Ubuntu: 18.04 clean install Nautilus: 1:3.26.3-0ubuntu4 The actions taken to produce the problem: Click on “Other Locations” in Nautilus. The expected result of these actions: Samba servers to automatically show up under “Networks”. This is the behavior in Ubuntu 17.10 using Nautilus 1:3.26.0-0ub. Also, clicking on “”Windows Network” immediately shows "Folder is Empty". The actual result of these actions: The Samba servers never show up under “Networks” and clicking on "Windows Network" always immediately comes up with "Folder is Empty". Further information: This happens on both machines with a clean Ubuntu 18.04 install. My Ubuntu 17.10 machines still work like expected. I can still manually type in the Samba information in "Connect to Server" and the 18.04 machines connect just fine. From syslog: Apr 27 13:49:34 david-HP-ProBook-440-G2 dbus-daemon[1333]: [session uid=1000 pid=1333] Activating service name='org.gnome.Nautilus' requested by ':1.13' (uid=1000 pid=1468 comm="/usr/bin/gnome-shell " label="unconfined") Apr 27 13:49:34 david-HP-ProBook-440-G2 dbus-daemon[1333]: [session uid=1000 pid=1333] Successfully activated service 'org.gnome.Nautilus' Apr 27 13:49:35 david-HP-ProBook-440-G2 dbus-daemon[754]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.131' (uid=1000 pid=4857 comm="/usr/bin/nautilus --gapplication-service " label="unconfined") Apr 27 13:49:35 david-HP-ProBook-440-G2 systemd[1]: Starting Hostname Service... Apr 27 13:49:35 david-HP-ProBook-440-G2 nautilus[4857]: Called "net usershare info" but it failed: Failed to execute child process “net” (No such file or directory) Apr 27 13:49:35 david-HP-ProBook-440-G2 dbus-daemon[754]: [system] Successfully activated service 'org.freedesktop.hostname1' Apr 27 13:49:35 david-HP-ProBook-440-G2 systemd[1]: Started Hostname Service. Apr 27 13:49:40 david-HP-ProBook-440-G2 gvfsd[1432]: mkdir failed on directory /var/cache/samba: Permission denied To manage notifications about this bug go to: https://bugs.launchpad.net/dolphin/+bug/1767454/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1906130] Re: Terminal: "Use colors from system theme" is gray-on-black
** Attachment added: "Screenshot_20201128_203807.png" https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1906130/+attachment/5439185/+files/Screenshot_20201128_203807.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1906130 Title: Terminal: "Use colors from system theme" is gray-on-black Status in gnome-terminal package in Ubuntu: New Bug description: Since I upgraded to Ubuntu 20.10 from 20.04, GNOME Terminal started showing dark gray text on a black background. I can resolve this issue by unchecking "Use colors from system theme" in Preferences > [Profile] > Colours, and choosing a built-in scheme instead, like GNOME Dark. I am using GNOME Terminal 3.38.0. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1906130/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1906130] [NEW] Terminal: "Use colors from system theme" is gray-on-black
Public bug reported: Since I upgraded to Ubuntu 20.10 from 20.04, GNOME Terminal started showing dark gray text on a black background. I can resolve this issue by unchecking "Use colors from system theme" in Preferences > [Profile] > Colours, and choosing a built-in scheme instead, like GNOME Dark. I am using GNOME Terminal 3.38.0. ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Screenshot_20201128_203744.png" https://bugs.launchpad.net/bugs/1906130/+attachment/5439184/+files/Screenshot_20201128_203744.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1906130 Title: Terminal: "Use colors from system theme" is gray-on-black Status in gnome-terminal package in Ubuntu: New Bug description: Since I upgraded to Ubuntu 20.10 from 20.04, GNOME Terminal started showing dark gray text on a black background. I can resolve this issue by unchecking "Use colors from system theme" in Preferences > [Profile] > Colours, and choosing a built-in scheme instead, like GNOME Dark. I am using GNOME Terminal 3.38.0. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1906130/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1905054]
Could you open about:support, click the "Copy text to clipboard" button, come back to this bug, click the "Attach New File" button above, and paste into the "File:" box and submit that troubleshooting information, please. -- 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/1905054 Title: Firefox 83 Breaks WebGL Status in Mozilla Firefox: New Status in firefox package in Ubuntu: Fix Committed Bug description: Upon upgrading from Firefox 82 to to Firefox 83, WebGL stops working. Ubuntu 20.10 with Wayland. When I try to launch a webGL game: Failed to create WebGL context: failIfMajorPerformanceCaveat: Compositor is not hardware-accelerated. Specifically Pixi says: Error: WebGL unsupported in this browser, use "pixi.js-legacy" for fallback canvas2d support. Downgrading to Firefox 82 works. Not sure if this is an Ubuntu build issue or Firefox, so I also filed upstream as well: https://bugzilla.mozilla.org/show_bug.cgi?id=1678652 I need this functionality for work, and pinning to version 82 will be problematic in the long-term. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1905054/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1905054]
Same problem happens under Windows 10 (1909) with an AMD Radeon HD 6450 graphics card. -- 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/1905054 Title: Firefox 83 Breaks WebGL Status in Mozilla Firefox: New Status in firefox package in Ubuntu: Fix Committed Bug description: Upon upgrading from Firefox 82 to to Firefox 83, WebGL stops working. Ubuntu 20.10 with Wayland. When I try to launch a webGL game: Failed to create WebGL context: failIfMajorPerformanceCaveat: Compositor is not hardware-accelerated. Specifically Pixi says: Error: WebGL unsupported in this browser, use "pixi.js-legacy" for fallback canvas2d support. Downgrading to Firefox 82 works. Not sure if this is an Ubuntu build issue or Firefox, so I also filed upstream as well: https://bugzilla.mozilla.org/show_bug.cgi?id=1678652 I need this functionality for work, and pinning to version 82 will be problematic in the long-term. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1905054/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1905054]
Same problem for me with Firefox 83.0 (64bit) under Fedora Linux, using the official Firefox from the Mozilla website, when trying to load the 3D view of Google Maps. Have to use Google Chrome for that now. :( Graphics Card: GeForce GTX 760 NVIDIA Driver Version: 455.38 -- 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/1905054 Title: Firefox 83 Breaks WebGL Status in Mozilla Firefox: New Status in firefox package in Ubuntu: Fix Committed Bug description: Upon upgrading from Firefox 82 to to Firefox 83, WebGL stops working. Ubuntu 20.10 with Wayland. When I try to launch a webGL game: Failed to create WebGL context: failIfMajorPerformanceCaveat: Compositor is not hardware-accelerated. Specifically Pixi says: Error: WebGL unsupported in this browser, use "pixi.js-legacy" for fallback canvas2d support. Downgrading to Firefox 82 works. Not sure if this is an Ubuntu build issue or Firefox, so I also filed upstream as well: https://bugzilla.mozilla.org/show_bug.cgi?id=1678652 I need this functionality for work, and pinning to version 82 will be problematic in the long-term. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1905054/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1905054]
Can you guys try the Firefox 84b2 build? I tried it from the tarball and it worked perfectly. -- 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/1905054 Title: Firefox 83 Breaks WebGL Status in Mozilla Firefox: New Status in firefox package in Ubuntu: Fix Committed Bug description: Upon upgrading from Firefox 82 to to Firefox 83, WebGL stops working. Ubuntu 20.10 with Wayland. When I try to launch a webGL game: Failed to create WebGL context: failIfMajorPerformanceCaveat: Compositor is not hardware-accelerated. Specifically Pixi says: Error: WebGL unsupported in this browser, use "pixi.js-legacy" for fallback canvas2d support. Downgrading to Firefox 82 works. Not sure if this is an Ubuntu build issue or Firefox, so I also filed upstream as well: https://bugzilla.mozilla.org/show_bug.cgi?id=1678652 I need this functionality for work, and pinning to version 82 will be problematic in the long-term. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1905054/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1905054]
Created attachment 9190103 Attached about:config per instructions -- 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/1905054 Title: Firefox 83 Breaks WebGL Status in Mozilla Firefox: New Status in firefox package in Ubuntu: Fix Committed Bug description: Upon upgrading from Firefox 82 to to Firefox 83, WebGL stops working. Ubuntu 20.10 with Wayland. When I try to launch a webGL game: Failed to create WebGL context: failIfMajorPerformanceCaveat: Compositor is not hardware-accelerated. Specifically Pixi says: Error: WebGL unsupported in this browser, use "pixi.js-legacy" for fallback canvas2d support. Downgrading to Firefox 82 works. Not sure if this is an Ubuntu build issue or Firefox, so I also filed upstream as well: https://bugzilla.mozilla.org/show_bug.cgi?id=1678652 I need this functionality for work, and pinning to version 82 will be problematic in the long-term. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1905054/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1905054]
(In reply to michaelspohn from comment #7) > (In reply to Pat Suwalski from comment #6) > > Can you guys try the Firefox 84b2 build? I tried it from the tarball and it > > worked perfectly. > > No change, still broken on Windows 10... Fun fact: Chrome 87.0.4280.66 and Edge 87.0.664.47 also do not support WebGL on Google Maps anymore No 3D-View available. The "good old" Internet Explorer 11.1198.18362.0 is the only browser that still works just fine. But hey, it's 2020! What do you expect? 🤣 -- 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/1905054 Title: Firefox 83 Breaks WebGL Status in Mozilla Firefox: New Status in firefox package in Ubuntu: Fix Committed Bug description: Upon upgrading from Firefox 82 to to Firefox 83, WebGL stops working. Ubuntu 20.10 with Wayland. When I try to launch a webGL game: Failed to create WebGL context: failIfMajorPerformanceCaveat: Compositor is not hardware-accelerated. Specifically Pixi says: Error: WebGL unsupported in this browser, use "pixi.js-legacy" for fallback canvas2d support. Downgrading to Firefox 82 works. Not sure if this is an Ubuntu build issue or Firefox, so I also filed upstream as well: https://bugzilla.mozilla.org/show_bug.cgi?id=1678652 I need this functionality for work, and pinning to version 82 will be problematic in the long-term. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1905054/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1905054]
(In reply to Pat Suwalski from comment #6) > Can you guys try the Firefox 84b2 build? I tried it from the tarball and it > worked perfectly. No change, still broken on Windows 10... -- 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/1905054 Title: Firefox 83 Breaks WebGL Status in Mozilla Firefox: New Status in firefox package in Ubuntu: Fix Committed Bug description: Upon upgrading from Firefox 82 to to Firefox 83, WebGL stops working. Ubuntu 20.10 with Wayland. When I try to launch a webGL game: Failed to create WebGL context: failIfMajorPerformanceCaveat: Compositor is not hardware-accelerated. Specifically Pixi says: Error: WebGL unsupported in this browser, use "pixi.js-legacy" for fallback canvas2d support. Downgrading to Firefox 82 works. Not sure if this is an Ubuntu build issue or Firefox, so I also filed upstream as well: https://bugzilla.mozilla.org/show_bug.cgi?id=1678652 I need this functionality for work, and pinning to version 82 will be problematic in the long-term. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1905054/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1905946] Re: Mouse stop moving after few seconds. restart at click
Similar issues with Logitech wireless keyboard and mouse after updating Hirsute. Mouse freezes intermittently but is mostly usable. Keyboard is essentially unusable (this is posted via onscreen keyboard). All hardware fully functional on Hirsute with 5.8.0-25 and 5.8.0-26 before updates on 11/27 and/or 11/28. Overlapping updated packages with corradoventu appear to be linux-firmware and apport related ones. Booting in recovery mode on both kernels keyboard is also unusable. No issues in updated Groovy or elementary OS. Intel i9, Asus MB -- 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/1905946 Title: Mouse stop moving after few seconds. restart at click Status in gnome-shell package in Ubuntu: Confirmed Bug description: Mouse stop moving after few seconds if i don't continue moving it, restart moving if i click but after few seconds sstops again. Problem occurs with both X11 and Wayland session. corrado@corrado-x2-hh-1104:~$ inxi -Fx System:Host: corrado-x2-hh-1104 Kernel: 5.8.0-25-generic x86_64 bits: 64 compiler: gcc v: 10.2.0 Desktop: GNOME 3.38.1 Distro: Ubuntu 21.04 (Hirsute Hippo) Machine: Type: Desktop Mobo: ASRock model: H110M-G/M.2 serial: UEFI: American Megatrends v: P1.10 date: 05/11/2017 CPU: Info: Dual Core model: Intel Core i3-7100 bits: 64 type: MT MCP arch: Kaby Lake rev: 9 L2 cache: 3072 KiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 31199 Speed: 800 MHz min/max: 800/3900 MHz Core speeds (MHz): 1: 800 2: 800 3: 800 4: 800 Graphics: Device-1: Intel HD Graphics 630 vendor: ASRock driver: i915 v: kernel bus ID: 00:02.0 Device-2: ARC USB 2.0 Camera type: USB driver: uvcvideo bus ID: 1-1:2 Display: x11 server: X.Org 1.20.9 driver: modesetting unloaded: fbdev,vesa resolution: 1920x1080~60Hz OpenGL: renderer: Mesa Intel HD Graphics 630 (KBL GT2) v: 4.6 Mesa 20.2.2 direct render: Yes Audio: Device-1: Intel 100 Series/C230 Series Family HD Audio vendor: ASRock driver: snd_hda_intel v: kernel bus ID: 00:1f.3 Device-2: Logitech QuickCam Pro 9000 type: USB driver: snd-usb-audio,uvcvideo bus ID: 1-8:5 Sound Server: ALSA v: k5.8.0-25-generic Network: Device-1: Intel Ethernet I219-V vendor: ASRock driver: e1000e v: 3.2.6-k port: f040 bus ID: 00:1f.6 IF: enp0s31f6 state: up speed: 100 Mbps duplex: full mac: 70:85:c2:44:7b:86 Drives:Local Storage: total: 2.05 TiB used: 15.92 GiB (0.8%) ID-1: /dev/nvme0n1 vendor: Kingston model: SKC2000M8250G size: 232.89 GiB ID-2: /dev/sda vendor: Toshiba model: DT01ACA100 size: 931.51 GiB ID-3: /dev/sdb vendor: Hitachi model: HDS721010CLA332 size: 931.51 GiB Partition: ID-1: / size: 31.25 GiB used: 15.91 GiB (50.9%) fs: ext4 dev: /dev/nvme0n1p2 Swap: ID-1: swap-1 type: partition size: 8.00 GiB used: 0 KiB (0.0%) dev: /dev/sda2 Sensors: System Temperatures: cpu: 45.5 C mobo: N/A Fan Speeds (RPM): N/A Info: Processes: 213 Uptime: 1h 31m Memory: 7.48 GiB used: 1.75 GiB (23.4%) Init: systemd runlevel: 5 Compilers: gcc: N/A Packages: 1937 Shell: Bash v: 5.1.0-rc2 inxi: 3.1.09 corrado@corrado-x2-hh-1104:~$ ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.1-1ubuntu2 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu53 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Nov 27 11:12:40 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-11-04 (22 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20201104) RelatedPackageVersions: mutter-common 3.38.1-2ubuntu1 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/1905946/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1878974] Re: Unable to use HP USB Printer in Ubuntu 20.04 - apear to be hplip issues
i did as "Hossein Shahdoost (hshahdoost)" said and it worked with me , thanks all <3 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1878974 Title: Unable to use HP USB Printer in Ubuntu 20.04 - apear to be hplip issues Status in HPLIP: New Status in hplip package in Ubuntu: Incomplete Bug description: Hi, I am unable to connect and print with a HP USB Pinter on Ubuntu 20.04, Spent some time troubleshooting with the default (previously current) drivers hplip ver. 3.20.3 , but Ubuntu 20.04 does not seem to be supported officially due to missing dependencies. Errors about missing pyqt4 dependencies among others. When using the hplip ver. 3.20.3 from the Ubuntu Repo printer is found but fails to print. Just noticed similar bug filed, 690720 , and saw note that new hplip ver. 3.20.5 was just released and supports Ubuntu 20.04 When trying to install new package hplip ver. 3.20.5 with the .run script provided by HP I am unable to complete installatoin as it reports unmet dependency of pyqt5 , even though package python3-pyqt5 is installed on system. https://developers.hp.com/hp-linux-imaging-and-printing/gethplip Maybe the repo just needs to be updated with a newer build (3.20.5) to install on my system, or is there something that can be done in the meantime. Below hp-check -t when using the repo hplip ver. 3.20.3 , == Saving output in log file: /root/hp-check.log HP Linux Imaging and Printing System (ver. 3.20.3) Dependency/Version Check Utility ver. 15.1 Copyright (c) 2001-18 HP Development Company, LP This software comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to distribute it under certain conditions. See COPYING file for more details. Note: hp-check can be run in three modes: 1. Compile-time check mode (-c or --compile): Use this mode before compiling the HPLIP supplied tarball (.tar.gz or .run) to determine if the proper dependencies are installed to successfully compile HPLIP. 2. Run-time check mode (-r or --run): Use this mode to determine if a distro supplied package (.deb, .rpm, etc) or an already built HPLIP supplied tarball has the proper dependencies installed to successfully run. 3. Both compile- and run-time check mode (-b or --both) (Default): This mode will check both of the above cases (both compile- and run-time dependencies). Check types: a. EXTERNALDEP - External Dependencies b. GENERALDEP - General Dependencies (required both at compile and run time) c. COMPILEDEP - Compile time Dependencies d. [All are run-time checks] PYEXT SCANCONF QUEUES PERMISSION Status Types: OK MISSING - Missing Dependency or Permission or Plug-in INCOMPAT - Incompatible dependency-version or Plugin-version warning: ubuntu-20.04 version is not supported. Using ubuntu-19.10 versions dependencies to verify and install... --- | SYSTEM INFO | --- Kernel: 5.4.0-29-generic #33-Ubuntu SMP Wed Apr 29 14:32:27 UTC 2020 GNU/Linux Host: judith-mini Proc: 5.4.0-29-generic #33-Ubuntu SMP Wed Apr 29 14:32:27 UTC 2020 GNU/Linux Distribution: ubuntu 20.04 Bitness: 64 bit --- | HPLIP CONFIGURATION | --- HPLIP-Version: HPLIP 3.20.3 HPLIP-Home: /usr/share/hplip warning: HPLIP-Installation: Auto installation is not su
[Desktop-packages] [Bug 1906073] Re: Syslog generates an error per second - appears to be related to Discord notification icons
Happened again this evening, I've got the log files but they're literally 80GB total, if you need them or want them let me know and I'll find a way to get them to you. ** Attachment added: "Screenshot from 2020-11-28 23-48-16.png" https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1906073/+attachment/5439164/+files/Screenshot%20from%202020-11-28%2023-48-16.png -- 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/1906073 Title: Syslog generates an error per second - appears to be related to Discord notification icons Status in gnome-shell-extension-appindicator package in Ubuntu: New Bug description: My computer recently stopped booting due to a 50GB+ syslog file, so I've had the syslog open in a terminal to follow any errors that repeat. Whilst on a call to some friends I noticed that the following error would generate once per second within the syslog file: Nov 27 23:02:36 jared-MS-7930 ubuntu-appindicat...@ubuntu.com[2305]: discord1, Impossible to lookup icon for 'discord1_53-panel' Nov 27 23:02:36 jared-MS-7930 gnome-shell[2305]: JS ERROR: Exception in callback for signal: icon: Error: Argument 'filename' (type filename) may not be null#012_createIconByName@/usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/appIndicator.js:406:26#012_cacheOrCreateIconByName@/usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/appIndicator.js:368:14#012_updateIconByType@/usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/appIndicator.js:574:18#012_updateIcon@/usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/appIndicator.js:601:14#012_emit@resource:///org/gnome/gjs/modules/core/_signals.js:133:47#012_onPropertiesChanged/<@/usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/appIndicator.js:220:22#012_onPropertiesChanged@/usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/appIndicator.js:214:15#012refreshPropertyOnProxy/<@/usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/util.js:51:19 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell-extension-appindicator 33-1 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Nov 27 23:04:20 2020 InstallationDate: Installed on 2014-12-07 (2182 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) PackageArchitecture: all SourcePackage: gnome-shell-extension-appindicator UpgradeStatus: Upgraded to focal on 2020-09-29 (59 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1906073/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1905637] Re: Games don't go full screen correctly with newer version of libmutter
I think this bug could be related to Debian's bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975453 They already got a fix. ** Bug watch added: Debian Bug tracker #975453 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975453 -- 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/1905637 Title: Games don't go full screen correctly with newer version of libmutter Status in mutter package in Ubuntu: Confirmed Bug description: Some games (I tried using Portal and Tomb Raider 2013, both native games) don't go full screen correctly (even configured for it). I tracked down the problem to a regression on package libmutter-7-0. The problem occurs with latest version, 3.38.1-2ubuntu1, but when I downgrade the package (and also the package gir1.2-mutter-7) to 3.38.1-1ubuntu1 the gomes went full screen normally. I'm using Ubuntu 20.10. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2020-10-23 (33 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) NonfreeKernelModules: nvidia_modeset nvidia Package: libmutter-7-0 3.38.1-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.8.0-30.32-generic 5.8.17 Tags: groovy third-party-packages Uname: Linux 5.8.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1905637/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1905322] Re: LibreOffice crashes under load.
I have done some more testing. I tried the same thing on LMDE (outside the Ubuntu family) and it froze all the LibreOffice apps but didn't crash. It locked them up. They couldn't be closed except by killing them with the system monitor or through the terminal. I don't think the problem is a Lubuntu/Ubuntu thing. I think it's upstream, given that behavior in Linux Mint *Debian* Edition. -- 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/1905322 Title: LibreOffice crashes under load. Status in libreoffice package in Ubuntu: Confirmed Bug description: lsb_release -rd Description:Ubuntu Hirsute Hippo (development branch) Release:21.04 apt-cache policy libreoffice libreoffice: Installed: (none) Candidate: 1:7.0.3-0ubuntu1 Version table: 1:7.0.3-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu hirsute/universe amd64 Packages I expect to be able to open all of LibreOffice's apps at once and use them. If you open all the LibreOffice applications and then select a template for LibreOffice Writer, they all close immediately, reopen, and offer to recover any lost data. Error reports may have been sent. I am not sure as this is Hirsute and I'm testing it. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: libreoffice (not installed) ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu51 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.455 CurrentDesktop: LXQt Date: Mon Nov 23 20:06:19 2020 LiveMediaBuild: Lubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20201123) 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/1905322/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1905209] Re: gnome-screensaver is blocked by an application to lock screen
Sorry don't know how to mark it resolved, thanks ** Changed in: gnome-screensaver (Ubuntu) Status: Incomplete => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1905209 Title: gnome-screensaver is blocked by an application to lock screen Status in gnome-screensaver package in Ubuntu: In Progress Bug description: can't lock screen, gnome screensaver is blocked by an application to lock screen ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-screensaver 3.6.1-11ubuntu4 ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14 Uname: Linux 5.8.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Nov 23 09:18:48 2020 GnomeSessionIdleInhibited: Yes GnomeSessionInhibitors: 1: AppId = firefox, Flags = 8, Reason = video-playing GsettingsGnomeSession: org.gnome.desktop.session session-name 'ubuntu' org.gnome.desktop.session idle-delay uint32 300 InstallationDate: Installed on 2019-08-04 (476 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: gnome-screensaver UpgradeStatus: Upgraded to groovy on 2020-11-20 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1905209/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1752860] Re: hp laserjet 1020 not working
1) First install hplip: sudo apt install hplip 2) Next run hp setup: hp-setup -i In hp-setup, when prompted, type printer connection number. When prompted, type d to download the printer firmware. When prompted, agree to the licence terms. 3) Install hp printer gui: sudo apt install hplip-gui -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1752860 Title: hp laserjet 1020 not working Status in hplip package in Ubuntu: Fix Released Bug description: my hp laserjet 1020 is not printing when im trying to prit a test page ubuntu says that job printed but in my printer nothing happens To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1752860/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1905209] Re: gnome-screensaver is blocked by an application to lock screen
Hi, sorted it, just went to dconf-editor than searched for screen lock down. came on to this: org.gnome.desktop.lockdown The default value was to disable lock down which I changed it to false. Now lock screen works. Thanks for pointing me out to solve it. have a nice day sokol -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1905209 Title: gnome-screensaver is blocked by an application to lock screen Status in gnome-screensaver package in Ubuntu: In Progress Bug description: can't lock screen, gnome screensaver is blocked by an application to lock screen ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-screensaver 3.6.1-11ubuntu4 ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14 Uname: Linux 5.8.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Nov 23 09:18:48 2020 GnomeSessionIdleInhibited: Yes GnomeSessionInhibitors: 1: AppId = firefox, Flags = 8, Reason = video-playing GsettingsGnomeSession: org.gnome.desktop.session session-name 'ubuntu' org.gnome.desktop.session idle-delay uint32 300 InstallationDate: Installed on 2019-08-04 (476 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: gnome-screensaver UpgradeStatus: Upgraded to groovy on 2020-11-20 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1905209/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1905209] Re: gnome-screensaver is blocked by an application to lock screen
Hi Sebastian OS Name Ubuntu 20.10 OS Type 64-bit Gnome Version 3.38.1 Windows system X11 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1905209 Title: gnome-screensaver is blocked by an application to lock screen Status in gnome-screensaver package in Ubuntu: Incomplete Bug description: can't lock screen, gnome screensaver is blocked by an application to lock screen ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-screensaver 3.6.1-11ubuntu4 ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14 Uname: Linux 5.8.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Nov 23 09:18:48 2020 GnomeSessionIdleInhibited: Yes GnomeSessionInhibitors: 1: AppId = firefox, Flags = 8, Reason = video-playing GsettingsGnomeSession: org.gnome.desktop.session session-name 'ubuntu' org.gnome.desktop.session idle-delay uint32 300 InstallationDate: Installed on 2019-08-04 (476 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: gnome-screensaver UpgradeStatus: Upgraded to groovy on 2020-11-20 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1905209/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1906120] [NEW] NetworkManager: error -111 disaptching events on DHCPv4 lease renewal
Public bug reported: Ubuntu 20.04.1 running on armv7 (IFC6410) Occasional network interruption with the following message in journal: Nov 28 12:03:16 drako NetworkManager[4094]: [1606582996.3983] device[dabf59d236aff82b] (enp1s0): activation-stage: complete activate_stage5_ip_config_result_6,v6 (id 51751) Nov 28 12:03:16 drako NetworkManager[4094]: [1606582996.4026] device[dabf59d236aff82b] (enp1s0): ip6-config: update (commit=0, new-config=0x803e6140) Nov 28 12:03:18 drako NetworkManager[4094]: [1606582998.8611] dhcp4 (enp1s0): error -111 dispatching events Nov 28 12:03:18 drako NetworkManager[4094]: [1606582998.8614] dhcp4 (enp1s0): state changed extended -> fail Nov 28 12:03:18 drako NetworkManager[4094]: [1606582998.8622] device (enp1s0): DHCPv4: trying to acquire a new lease within 90 seconds Nov 28 12:04:49 drako NetworkManager[4094]: [1606583089.4023] device (enp1s0): DHCPv4: grace period expired the ipv4 connection is then cut (the interface looses ipc4 address and the ipv4 routes are purged) until NetworkManager is restarted. The networkmanager-dispatcher.service doesn't indicate any error: Nov 28 06:04:05 drako systemd[1]: Started Network Manager Script Dispatcher Service. Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: new request (2 scripts) Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: CONNECTION_DBUS_PATH=/org/freedesktop/NetworkManager/Settings/1 Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: CONNECTION_FILENAME=/etc/NetworkManager/system-connections/Wired Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: CONNECTION_UUID=fe299e22-2b52-43ff-9a60-fa385e239f41 Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: CONNECTION_ID=Wired Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: DEVICE_IFACE=enp1s0 Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: DEVICE_IP_IFACE=enp1s0 Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: IP4_NUM_ADDRESSES=1 Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: IP4_NUM_ROUTES=1 Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: IP6_NUM_ROUTES=3 Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: DHCP4_DHCP_LEASE_TIME=28800 Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: DHCP4_EXPIRY=1606590245 Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: DHCP4_REQUESTED_BROADCAST_ADDRESS=1 Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: DHCP4_REQUESTED_DOMAIN_NAME=1 Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: DHCP4_REQUESTED_DOMAIN_NAME_SERVERS=1 Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: DHCP4_REQUESTED_DOMAIN_SEARCH=1 Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: DHCP4_REQUESTED_HOST_NAME=1 Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: DHCP4_REQUESTED_INTERFACE_MTU=1 Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: DHCP4_REQUESTED_MS_CLASSLESS_STATIC_ROUTES=1 Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: DHCP4_REQUESTED_NIS_DOMAIN=1 Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: DHCP4_REQUESTED_NIS_SERVERS=1 Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: DHCP4_REQUESTED_NTP_SERVERS=1 Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: DHCP4_REQUESTED_RFC3442_CLASSLESS_STATIC_ROUTES=1 Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: DHCP4_REQUESTED_ROOT_PATH=1 Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: DHCP4_REQUESTED_ROUTERS=1 Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: DHCP4_REQUESTED_STATIC_ROUTES=1 Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: DHCP4_REQUESTED_SUBNET_MASK=1 Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: DHCP4_REQUESTED_TIME_OFFSET=1 Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: DHCP4_REQUESTED_WPAD=1 Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: NM_DISPATCHER_ACTION=dhcp4-change Nov 28 06:04:05 drako nm-dispat
[Desktop-packages] [Bug 1652272] Re: Firefox suddenly loses internet connection
Launchpad has imported 24 comments from the remote bug at https://bugzilla.mozilla.org/show_bug.cgi?id=1325588. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2016-12-23T11:05:45+00:00 U552789 wrote: Since earlier today I have found that after about 10 minutes or less of using Firefox that suddenly for no apparent reason pages will refuse to load any contents, and although Firefox does not take me to the page which says it can't reach the site, it doesn't manage to load anything as though its internet connection has suddenly been lost. It won't even let me check for updates for plugins and gives an error for that. I have tested with other applications such as ping and the internet connection is fine, it's just Firefox which loses it. I have noticed that when I run firefox from Terminal that this is the output to begin with: 1482487989643 addons.webextension.fire...@ghostery.com WARN Loading extension 'fire...@ghostery.com': Reading manifest: Error processing background.persistent: Event pages are not currently supported. This will run as a persistent background page. 1482487989666 addons.webextension.fire...@ghostery.com WARN Loading extension 'fire...@ghostery.com': Reading manifest: Error processing author: An unexpected property was found in the WebExtension manifest. 1482487989666 addons.webextension.fire...@ghostery.com WARN Loading extension 'fire...@ghostery.com': Reading manifest: Error processing version_name: An unexpected property was found in the WebExtension manifest. 1482487989666 addons.webextension.fire...@ghostery.com WARN Loading extension 'fire...@ghostery.com': Reading manifest: Error processing options_page: An unexpected property was found in the WebExtension manifest. 1482487989708 addons.webextension.fire...@ghostery.com WARN Please specify whether you want browser_style or not in your browser_action options. Promise resolved after context unloaded Then when the problem starts to occur, I find that the only way to resolve it, if even for a short period, is to restart the browser, so I tell Firefox to quit, however although the window does close, the process carries on and this is the output: tabs.onRemoved event fired after context unloaded. tabs.onRemoved event fired after context unloaded. tabs.onRemoved event fired after context unloaded. console.error: Message: Error: SessionFile is closed Stack: SessionFileInternal.write@resource://app/modules/sessionstore/SessionFile.jsm:315:29 this.SessionFile.write@resource://app/modules/sessionstore/SessionFile.jsm:76:12 SessionSaverInternal._writeState@resource://app/modules/sessionstore/SessionSaver.jsm:259:12 SessionSaverInternal._saveState@resource://app/modules/sessionstore/SessionSaver.jsm:230:12 SessionSaverInternal._saveStateAsync@resource://app/modules/sessionstore/SessionSaver.jsm:243:5 SessionSaverInternal.runDelayed/this._timeoutID<@resource://app/modules/sessionstore/SessionSaver.jsm:147:40 setTimeout_timer@resource://gre/modules/Timer.jsm:30:5 ExceptionHandler::GenerateDump cloned child 12324 ExceptionHandler::SendContinueSignalToChild sent continue signal to child ExceptionHandler::WaitForContinueSignal waiting for continue signal... I am then told that Firefox crashed and asked if I would like to submit a report, so far I have told it to submit a report three times as the crash has occurred that number of times. For that entire period of time this is the output from Firefox in syslog: Dec 23 10:00:42 firefox.desktop[11349]: 1482487242751#011addons.webextension.fire...@ghostery.com#011WARN#011Loading extension 'fire...@ghostery.com': Reading manifest: Error processing background.persistent: Event pages are not currently supported. This will run as a persistent background page. Dec 23 10:00:42 firefox.desktop[11349]: 1482487242778#011addons.webextension.fire...@ghostery.com#011WARN#011Loading extension 'fire...@ghostery.com': Reading manifest: Error processing author: An unexpected property was found in the WebExtension manifest. Dec 23 10:00:42 firefox.desktop[11349]: 1482487242779#011addons.webextension.fire...@ghostery.com#011WARN#011Loading extension 'fire...@ghostery.com': Reading manifest: Error processing version_name: An unexpected property was found in the WebExtension manifest. Dec 23 10:00:42 firefox.desktop[11349]: 1482487242779#011addons.webextension.fire...@ghostery.com#011WARN#011Loading extension 'fire...@ghostery.com': Reading manifest: Error processing options_page: An unexpected property was found in the WebExtension manifest. Dec 23 10:00:42 firefox.desktop[11349]: 1482487242821#011addons.webextension.
[Desktop-packages] [Bug 1897765] Re: gnome-shell crashed with signal 5 in g_log("Error in freeze/thaw accounting") from meta_window_actor_thaw() from WindowManager::_sizeChangedWindow
** Attachment added: "crashed with a different error today"
https://bugs.launchpad.net/mutter/+bug/1897765/+attachment/5439043/+files/%D0%97%D0%BD%D1%96%D0%BC%D0%BE%D0%BA%20%D0%B5%D0%BA%D1%80%D0%B0%D0%BD%D0%B0%20%D0%B7%202020-11-28%2013-59-37.png
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1897765
Title:
gnome-shell crashed with signal 5 in g_log("Error in freeze/thaw
accounting") from meta_window_actor_thaw() from
WindowManager::_sizeChangedWindow
Status in Mutter:
Unknown
Status in gnome-shell package in Ubuntu:
Fix Committed
Bug description:
https://errors.ubuntu.com/problem/2f47b25de323a59b617efbd8ce4b9bc7789848bd
https://errors.ubuntu.com/problem/fc9ef2077ed4ee125d73f018d3f8101a2beb0605
---
Launching terminator crashes gnome-shell, happens on two separate
machines.
ProblemType: Crash
DistroRelease: Ubuntu 20.10
Package: gnome-shell 3.38.0-1ubuntu2
ProcVersionSignature: Ubuntu 5.8.0-19.20-generic 5.8.8
Uname: Linux 5.8.0-19-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu48
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Tue Sep 29 18:05:57 2020
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
ExecutableTimestamp: 1600706451
InstallationDate: Installed on 2019-10-14 (350 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20191012)
ProcCmdline: /usr/bin/gnome-shell
ProcCwd: /home/tjaalton
ProcEnviron:
LANG=fi_FI.UTF-8
PATH=(custom, user)
SHELL=/bin/zsh
XDG_RUNTIME_DIR=
RelatedPackageVersions: mutter-common 3.38.0-1ubuntu1
Signal: 5
SourcePackage: gnome-shell
StacktraceTop:
g_log_structured_array () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
?? ()
g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: gnome-shell crashed with signal 5 in g_log_structured_array()
UpgradeStatus: Upgraded to groovy on 2020-09-29 (0 days ago)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
separator:
To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1897765/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1897562] Re: gedit needs classic confinement
Please don't expire this request. The problem still exists in full. ** Changed in: gedit (Ubuntu) Status: Expired => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1897562 Title: gedit needs classic confinement Status in gedit package in Ubuntu: New Bug description: The snap version of gedit prevents viewing and editing files outside a strictly limited set of folders. For example, it cannot change files in standard folders ~/bin or ~/.local or ~/.config, or standard files such as ~/.bashrc or ~/.profile. Even "sudo -H gedit /etc/fstab" doesn't work. As there is a bug in the non-snap versions [1], the snap version is important, but sadly it is unusable for a certain number of cases. I understand that the only solution is to make gedit available in classic confinement. Please would you do this. Thank you [1] https://gitlab.gnome.org/GNOME/gedit/-/issues/361 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1897562/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1905322] Re: LibreOffice crashes under load.
I did some further testing on the same machine in comment #10 - I think the error is not because of the "load" but somehow related to the template selection in Impress - I noticed that when I selected the apps one by one after Impress opened with the "template selection" dialog if I did nothing and continued on to open "Math" and "Writer" they did not appear in the panel bar .I then (as in the video comment #7" selected a templete (vivid) and received the crash - if I selected a template other than "vivid" then there was no crash. Also tested but this time opened a template when "Impress" started - then no errors, no crash. Lastly I changed the Impress "select a Template dialog box - Show this dialog at startup " button and reran the tests and all worked normally. -- 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/1905322 Title: LibreOffice crashes under load. Status in libreoffice package in Ubuntu: Confirmed Bug description: lsb_release -rd Description:Ubuntu Hirsute Hippo (development branch) Release:21.04 apt-cache policy libreoffice libreoffice: Installed: (none) Candidate: 1:7.0.3-0ubuntu1 Version table: 1:7.0.3-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu hirsute/universe amd64 Packages I expect to be able to open all of LibreOffice's apps at once and use them. If you open all the LibreOffice applications and then select a template for LibreOffice Writer, they all close immediately, reopen, and offer to recover any lost data. Error reports may have been sent. I am not sure as this is Hirsute and I'm testing it. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: libreoffice (not installed) ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu51 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.455 CurrentDesktop: LXQt Date: Mon Nov 23 20:06:19 2020 LiveMediaBuild: Lubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20201123) 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/1905322/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1905322] Re: LibreOffice crashes under load.
I can confirm this bug - testing Lubuntu Hirsute daily 27.11.2020 on the QA site http://cdimage.ubuntu.com/lubuntu/daily-live/20201127/hirsute-desktop- amd64.iso Machine used Acer [Aspire] E3-111-P60S (Pent.N3530, 4GB) Opened all LibreOffice apps one by one and selected Impress templete "Vivid" as in the video posted in comment # 7 and received the same results as KGIII. -- 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/1905322 Title: LibreOffice crashes under load. Status in libreoffice package in Ubuntu: Confirmed Bug description: lsb_release -rd Description:Ubuntu Hirsute Hippo (development branch) Release:21.04 apt-cache policy libreoffice libreoffice: Installed: (none) Candidate: 1:7.0.3-0ubuntu1 Version table: 1:7.0.3-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu hirsute/universe amd64 Packages I expect to be able to open all of LibreOffice's apps at once and use them. If you open all the LibreOffice applications and then select a template for LibreOffice Writer, they all close immediately, reopen, and offer to recover any lost data. Error reports may have been sent. I am not sure as this is Hirsute and I'm testing it. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: libreoffice (not installed) ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu51 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.455 CurrentDesktop: LXQt Date: Mon Nov 23 20:06:19 2020 LiveMediaBuild: Lubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20201123) 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/1905322/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1905322] Re: LibreOffice crashes under load.
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: libreoffice (Ubuntu) Status: New => Confirmed -- 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/1905322 Title: LibreOffice crashes under load. Status in libreoffice package in Ubuntu: Confirmed Bug description: lsb_release -rd Description:Ubuntu Hirsute Hippo (development branch) Release:21.04 apt-cache policy libreoffice libreoffice: Installed: (none) Candidate: 1:7.0.3-0ubuntu1 Version table: 1:7.0.3-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu hirsute/universe amd64 Packages I expect to be able to open all of LibreOffice's apps at once and use them. If you open all the LibreOffice applications and then select a template for LibreOffice Writer, they all close immediately, reopen, and offer to recover any lost data. Error reports may have been sent. I am not sure as this is Hirsute and I'm testing it. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: libreoffice (not installed) ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu51 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.455 CurrentDesktop: LXQt Date: Mon Nov 23 20:06:19 2020 LiveMediaBuild: Lubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20201123) 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/1905322/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1906101] [NEW] no sound via speakers or headphone port on Carbon X1
Public bug reported: I recently upgraded from 18.04 to 20.04. The sound worked without problems before upgrade, but now I don'get any sound at all from the speakers or the headphone jack. This seems similar to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860697 (although that bug is reported as resolved). I tried adding model=generic dmic_detect=0 to my alsa-base.conf, as reported in that ticket, but it did not help. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.8 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Sat Nov 28 18:36:36 2020 InstallationDate: Installed on 2018-07-27 (855 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: pulseaudio UpgradeStatus: Upgraded to focal on 2020-11-24 (4 days ago) dmi.bios.date: 10/13/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET75W (1.50 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KGCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN23ET75W(1.50):bd10/13/2020:svnLENOVO:pn20KGCTO1WW:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KGCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 6th dmi.product.name: 20KGCTO1WW dmi.product.sku: LENOVO_MT_20KG_BU_Think_FM_ThinkPad X1 Carbon 6th dmi.product.version: ThinkPad X1 Carbon 6th dmi.sys.vendor: LENOVO ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- 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/1906101 Title: no sound via speakers or headphone port on Carbon X1 Status in pulseaudio package in Ubuntu: New Bug description: I recently upgraded from 18.04 to 20.04. The sound worked without problems before upgrade, but now I don'get any sound at all from the speakers or the headphone jack. This seems similar to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860697 (although that bug is reported as resolved). I tried adding model=generic dmic_detect=0 to my alsa-base.conf, as reported in that ticket, but it did not help. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.8 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Sat Nov 28 18:36:36 2020 InstallationDate: Installed on 2018-07-27 (855 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: pulseaudio UpgradeStatus: Upgraded to focal on 2020-11-24 (4 days ago) dmi.bios.date: 10/13/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET75W (1.50 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KGCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN23ET75W(1.50):bd10/13/2020:svnLENOVO:pn20KGCTO1WW:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KGCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 6th dmi.product.name: 20KGCTO1WW dmi.product.sku: LENOVO_MT_20KG_BU_Think_FM_ThinkPad X1 Carbon 6th dmi.product.version: ThinkPad X1 Carbon 6th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1906101/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1062888] Re: gedit wrote critical errors on output
Thank you for reporting this bug to Ubuntu. Ubuntu 12.04 (precise) reached end-of-life on April 28, 2017. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in. ** Changed in: gedit (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1062888 Title: gedit wrote critical errors on output Status in gedit package in Ubuntu: Incomplete Bug description: The following was written on the output when gedit was started from the command line. Even though no visible malfunction was observed, maybe one of developers has a couple minutes to fix it. (gedit:4303): LibZeitgeist-CRITICAL **: Failed to create proxy for Zeitgeist daemon: Error calling StartServiceByName for org.gnome.zeitgeist.Engine: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process /usr/bin/zeitgeist-daemon exited with status 1 (gedit:4303): LibZeitgeist-CRITICAL **: Unable to connect to Zeitgeist daemon: Error calling StartServiceByName for org.gnome.zeitgeist.Engine: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process /usr/bin/zeitgeist-daemon exited with status 1 (gedit:4303): GLib-GIO-CRITICAL **: g_dbus_proxy_get_connection: assertion `G_IS_DBUS_PROXY (proxy)' failed (gedit:4303): GLib-GObject-CRITICAL **: g_object_ref: assertion `G_IS_OBJECT (object)' failed (gedit:4303): GLib-GIO-CRITICAL **: g_dbus_connection_signal_subscribe: assertion `G_IS_DBUS_CONNECTION (connection)' failed ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gedit 3.4.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-31.50-generic-pae 3.2.28 Uname: Linux 3.2.0-31-generic-pae i686 ApportVersion: 2.0.1-0ubuntu13 Architecture: i386 Date: Sat Oct 6 17:10:45 2012 InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 (20120817.3) SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1062888/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1325063] Re: Gedit preferences windows is empty
Thank you for reporting this bug to Ubuntu. Ubuntu 14.04 (trusty) reached end-of-life on April 25, 2019. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in. ** Changed in: gedit (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1325063 Title: Gedit preferences windows is empty Status in gedit package in Ubuntu: Incomplete Bug description: When I click the preferences item in menu I get a empty window that is just titled preferences. There is nothing in it and if I drag it to a bigger size an empty plane appears. When starting gedit as root I see the following error in terminal: (gedit:13564): Gtk-CRITICAL **: Error building template class 'GeditPreferencesDialog' for an instance of type 'GeditPreferencesDialog': Invalid object type `PeasGtkPluginManager' (gedit:13564): GLib-GIO-CRITICAL **: g_settings_bind_with_mapping: assertion 'G_IS_OBJECT (object)' failed (gedit:13564): GLib-GIO-CRITICAL **: g_settings_bind_with_mapping: assertion 'G_IS_OBJECT (object)' failed (gedit:13564): GLib-GIO-CRITICAL **: g_settings_bind_with_mapping: assertion 'G_IS_OBJECT (object)' failed ... UBUNTU 14.04, xsfc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1325063/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1902535] Re: Calc freeze when I try to export ods to xlm 2003 format
OK ! But it's not 3 times size but 300 times size ! 112 kB to 350 MB ! And when I open it with Calc, the format is much altered. -- 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/1902535 Title: Calc freeze when I try to export ods to xlm 2003 format Status in libreoffice package in Ubuntu: Invalid Bug description: I have a file saved in ODS format (only 12 sheets with about 60 lines and 20 rows, a planning for a staff) This file was an Excel 2013 file with macro that I opened and modified in LO Calc 7.0.2.2 If I save it in Excel2007-365 with macro format, it works If I export to Excel 2003 xlm format, Calc freezes and once, the system froze ! ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: libreoffice (not installed) ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Nov 2 14:46:51 2020 InstallationDate: Installed on 2020-04-10 (206 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) SourcePackage: libreoffice UpgradeStatus: Upgraded to groovy on 2020-10-24 (8 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1902535/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1906087] Re: Half of the date-time font is hidden when using Language Tamil-india
** Package changed: ubuntu => xorg (Ubuntu) -- 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/1906087 Title: Half of the date-time font is hidden when using Language Tamil-india Status in xorg package in Ubuntu: New Bug description: I am using Tamil(india) as the date-time language from Ubuntu 19. But after upgrading to Ubuntu 20, the date-time is half-hidden (see attachments). before upgrade it was working fine. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Nov 28 10:47:42 2020 DistUpgraded: 2020-06-06 18:27:37,926 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 620 [1028:0792] InstallationDate: Installed on 2018-11-04 (755 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. Vostro 14-3468 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-54-generic root=UUID=6272611c-ab7e-4b80-86ed-8e7dbe8d5396 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-06-06 (174 days ago) acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed with exit code 126: Error executing command as another user: Request dismissed dmi.bios.date: 05/15/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.6.0 dmi.board.name: 0T1X3V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.6.0:bd05/15/2018:svnDellInc.:pnVostro14-3468:pvr:rvnDellInc.:rn0T1X3V:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 14-3468 dmi.product.sku: 0792 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-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/+bug/1906087/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1906087] [NEW] Half of the date-time font is hidden when using Language Tamil-india
You have been subscribed to a public bug: I am using Tamil(india) as the date-time language from Ubuntu 19. But after upgrading to Ubuntu 20, the date-time is half-hidden (see attachments). before upgrade it was working fine. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Nov 28 10:47:42 2020 DistUpgraded: 2020-06-06 18:27:37,926 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 620 [1028:0792] InstallationDate: Installed on 2018-11-04 (755 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. Vostro 14-3468 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-54-generic root=UUID=6272611c-ab7e-4b80-86ed-8e7dbe8d5396 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-06-06 (174 days ago) acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed with exit code 126: Error executing command as another user: Request dismissed dmi.bios.date: 05/15/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.6.0 dmi.board.name: 0T1X3V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.6.0:bd05/15/2018:svnDellInc.:pnVostro14-3468:pvr:rvnDellInc.:rn0T1X3V:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 14-3468 dmi.product.sku: 0792 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-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 focal fonts ubuntu -- Half of the date-time font is hidden when using Language Tamil-india https://bugs.launchpad.net/bugs/1906087 You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg 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
