[Desktop-packages] [Bug 1993592] Re: GNOME becomes unresponsive after wiping down touchscreen
[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1993592 Title: GNOME becomes unresponsive after wiping down touchscreen Status in gnome-shell package in Ubuntu: Expired Bug description: After I wiped down my laptop's touchscreen with a wipe, GNOME went to the "Activities" screen (I must've hit the button while wiping down the screen), then GNOME became unresponsive. By unresponsive, I don't mean it froze. The mouse cursor still moved smoothly. It even recognized touch events by hiding the cursor when I tapped the screen. But it ignored literally everything else. The one other thing that changed the UI was changing my keyboard's backlight, which caused a volume-esque dialog to show up notifying me of the change, before quickly fading. I couldn't even use the Fn-Ctrl-Alt-X keys to switch to a TTY. I then closed my laptop's lid to put it to sleep and reopened it a little while later. The lockscreen was perfectly functional, but once I logged back in, the problem remained. Although Fn-Ctrl-Alt-X keys worked again. At that point I gave up and restarted my laptop. It's a good thing I didn't have anything important unsaved, or I could've just lost my data because I wiped down my touchscreen. I'm using Ubuntu 22.04 Wayland, GNOME Shell 42.2 (according to gnome-shell --version). --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-06-14 (493 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Package: gnome-shell 42.2-0ubuntu0.2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.17.0-1017.18-oem 5.17.15 RelatedPackageVersions: mutter-common 42.2-0ubuntu1 Tags: wayland-session jammy Uname: Linux 5.17.0-1017-oem x86_64 UpgradeStatus: Upgraded to jammy on 2022-05-10 (162 days ago) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1993592/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2000033] [NEW] When I want to connect to wifi with name "Galaxy A7 (2018)" The password panel open and immediately closed and not connected.
Public bug reported: Just for more information, I think before that I have connected to the hotspot and after password changed this bug appeared, I also tested without password for hotspot and connected without problem. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:41.7-0ubuntu0.22.04.5 ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64 Uname: Linux 5.15.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Dec 19 07:38:17 2022 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2022-11-04 (45 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/233 Title: When I want to connect to wifi with name "Galaxy A7 (2018)" The password panel open and immediately closed and not connected. Status in gnome-control-center package in Ubuntu: New Bug description: Just for more information, I think before that I have connected to the hotspot and after password changed this bug appeared, I also tested without password for hotspot and connected without problem. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:41.7-0ubuntu0.22.04.5 ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64 Uname: Linux 5.15.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Dec 19 07:38:17 2022 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2022-11-04 (45 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/233/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1605319] Re: Nvida does wierd
good day I updated my bios. I hope the problem is fixed. tnx for the response Op ma 12 dec. 2022 om 13:29 schreef Paul White <1605...@bugs.launchpad.net>: > Thank you for taking the time to report this bug and helping to make > Ubuntu better. We are sorry that we do not always have the capacity to > review all reported bugs in a timely manner. > > Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021. > > I'm setting the status of this bug to 'Incomplete' as it's not seen any > activity for some time. If this is still an issue when using a currently > maintained release of Ubuntu then please let us know which one(s) > otherwise this bug report can be left to expire in approximately 60 days > time. > > ** Changed in: xorg (Ubuntu) >Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1605319 > > Title: > Nvida does wierd > > Status in xorg package in Ubuntu: > Incomplete > > Bug description: > when i start the nvidia x servers it dont show me the full settings > list, try to reinstall it but it dint change > > ProblemType: Bug > DistroRelease: Ubuntu 16.04 > Package: xorg 1:7.7+13ubuntu3 > ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 > Uname: Linux 4.4.0-31-generic x86_64 > .tmp.unity_support_test.0: > > ApportVersion: 2.20.1-0ubuntu2.1 > Architecture: amd64 > BootLog: >[ [0;32m OK [0m] Started LSB: Speech Dispatcher. >[ [0;32m OK [0m] Started LSB: Set the CPU Frequency Scaling governor > to "ondemand". > CompizPlugins: No value set for > `/apps/compiz-1/general/screen0/options/active_plugins' > CompositorRunning: compiz > CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' > CompositorUnredirectFSW: true > CurrentDesktop: Unity > Date: Thu Jul 21 18:44:29 2016 > DistUpgraded: Fresh install > DistroCodename: xenial > DistroVariant: ubuntu > DkmsStatus: >bbswitch, 0.8, 4.4.0-21-generic, x86_64: installed >bbswitch, 0.8, 4.4.0-31-generic, x86_64: installed >nvidia-361, 361.42, 4.4.0-31-generic, x86_64: installed > ExtraDebuggingInterest: Yes > GraphicsCard: >Intel Corporation Haswell-ULT Integrated Graphics Controller > [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) > Subsystem: Acer Incorporated [ALI] Haswell-ULT Integrated Graphics > Controller [1025:0971] > Subsystem: Acer Incorporated [ALI] GK208M [GeForce 920M] [1025:0971] > InstallationDate: Installed on 2016-07-17 (4 days ago) > InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 > (20160420.1) > MachineType: Acer Aspire E5-772G > ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-31-generic > root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 > SourcePackage: xorg > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 07/28/2015 > dmi.bios.vendor: Insyde Corp. > dmi.bios.version: V1.09 > dmi.board.asset.tag: No Asset Tag > dmi.board.name: Aspire E5-772G > dmi.board.vendor: Acer > dmi.board.version: V1.09 > dmi.chassis.asset.tag: No Asset Tag > dmi.chassis.type: 10 > dmi.chassis.vendor: Acer > dmi.chassis.version: V1.09 > dmi.modalias: > dmi:bvnInsydeCorp.:bvrV1.09:bd07/28/2015:svnAcer:pnAspireE5-772G:pvrV1.09:rvnAcer:rnAspireE5-772G:rvrV1.09:cvnAcer:ct10:cvrV1.09: > dmi.product.name: Aspire E5-772G > dmi.product.version: V1.09 > dmi.sys.vendor: Acer > version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1 > version.ia32-libs: ia32-libs N/A > version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1 > version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2 > version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A > version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2 > version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2 > version.xserver-xorg-input-evdev: xserver-xorg-input-evdev > 1:2.10.1-1ubuntu2 > version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 > version.xserver-xorg-video-intel: xserver-xorg-video-intel > 2:2.99.917+git20160325-1ubuntu1 > version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A > xserver.bootTime: Thu Jul 21 18:36:47 2016 > xserver.configfile: default > xserver.errors: >Failed to load module "nvidia" (module does not exist, 0) >Failed to load module "nouveau" (module does not exist, 0) >Failed to load module "nvidia" (module does not exist, 0) >Failed to load module "nouveau" (module does not exist, 0) > xserver.logfile: /var/log/Xorg.0.log > xserver.outputs: >product id4509 >vendor AUO > xserver.version: 2:1.18.3-1ubuntu2.2 > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1605319/+subscriptions > > -- You received this bug notification because you are a member of
[Desktop-packages] [Bug 375395]
*** Bug 152566 has been marked as a duplicate of this bug. *** -- 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/375395 Title: [Upstream] scrolling only by full line height Status in LibreOffice: Confirmed Status in OpenOffice: Unknown Status in libreoffice package in Ubuntu: Confirmed Status in openoffice.org package in Ubuntu: Won't Fix Bug description: Binary package hint: openoffice.org If I have spreadsheet document with large, multiline cells, I can't scroll to distance equal some part of line. full line is scrolled at once. There is no option in preferences about scrolling by line (as in Excel) and scrolling by pixels (as in Word). Please add such option, or tell me where to find it, if it exists. ProblemType: Bug Architecture: i386 DistroRelease: Ubuntu 9.04 Package: openoffice.org-core 1:3.0.1-9ubuntu3 ProcEnviron: PATH=(custom, user) LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: openoffice.org Uname: Linux 2.6.28-11-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/375395/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1902094] Re: High Xorg and gnome-shell CPU usage while Sound Settings opened
** Changed in: gnome-control-center Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1902094 Title: High Xorg and gnome-shell CPU usage while Sound Settings opened Status in gnome-control-center: Fix Released Status in gnome-control-center package in Ubuntu: Triaged Bug description: Several days ago I found huge lags over all system on my Ubuntu 20.04.1 LTS. Today I think found the problem, but not the reason. So when I open Settings -> Sound menu, the CPU usage comes to about 100%. If I close Settings window or go to other tab, it becomes OK. Nothing special in my sound configuration - monitor and notebook with built in audio and Bluetooth headset. Same worked just fine on Ubuntu 18.04 LTS. xorg: Installed: 1:7.7+19ubuntu14 Candidate: 1:7.7+19ubuntu14 Version table: *** 1:7.7+19ubuntu14 500 500 http://ru.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 450.80.02 Wed Sep 23 01:13:39 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Oct 29 18:27:20 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 450.80.02, 5.4.0-52-generic, x86_64: installed virtualbox, 6.1.10, 5.4.0-51-generic, x86_64: installed virtualbox, 6.1.10, 5.4.0-52-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 630 (Mobile) [1028:0824] Subsystem: Dell GP107M [GeForce GTX 1050 Ti Mobile] [1028:0824] InstallationDate: Installed on 2020-09-12 (47 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. G5 5587 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic root=UUID=ef73abac-57c7-4134-90f3-1f52f41127a8 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/11/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.9.0 dmi.board.name: 03PVDF dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.9.0:bd02/11/2019:svnDellInc.:pnG55587:pvr:rvnDellInc.:rn03PVDF:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: GSeries dmi.product.name: G5 5587 dmi.product.sku: 0824 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 N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A 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/gnome-control-center/+bug/1902094/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2000025] [NEW] day of week not displayed
Public bug reported: in date and time program ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.9-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.15.0-56.62~20.04.1-generic 5.15.64 Uname: Linux 5.15.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Sun Dec 18 17:30:09 2022 DisplayManager: lightdm GsettingsChanges: b'org.gnome.desktop.app-folders' b'folder-children' b"['Utilities', 'YaST']" b'org.gnome.desktop.interface' b'clock-show-seconds' b'true' b'org.gnome.desktop.interface' b'clock-show-weekday' b'true' InstallationDate: Installed on 2022-12-14 (4 days ago) InstallationMedia: Ubuntu-MATE 20.04.5 LTS "Focal Fossa" - Release amd64 (20220831) RelatedPackageVersions: mutter-common 3.36.9-0ubuntu0.20.04.2 ShellJournal: -- Logs begin at Wed 2022-12-14 10:50:57 CST, end at Sun 2022-12-18 17:30:01 CST. -- -- No entries -- SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2022-12-14T13:38:44.189415 ** Affects: gnome-shell (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 gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/225 Title: day of week not displayed Status in gnome-shell package in Ubuntu: New Bug description: in date and time program ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.9-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.15.0-56.62~20.04.1-generic 5.15.64 Uname: Linux 5.15.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Sun Dec 18 17:30:09 2022 DisplayManager: lightdm GsettingsChanges: b'org.gnome.desktop.app-folders' b'folder-children' b"['Utilities', 'YaST']" b'org.gnome.desktop.interface' b'clock-show-seconds' b'true' b'org.gnome.desktop.interface' b'clock-show-weekday' b'true' InstallationDate: Installed on 2022-12-14 (4 days ago) InstallationMedia: Ubuntu-MATE 20.04.5 LTS "Focal Fossa" - Release amd64 (20220831) RelatedPackageVersions: mutter-common 3.36.9-0ubuntu0.20.04.2 ShellJournal: -- Logs begin at Wed 2022-12-14 10:50:57 CST, end at Sun 2022-12-18 17:30:01 CST. -- -- No entries -- SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2022-12-14T13:38:44.189415 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/225/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2000024] [NEW] Font alignment/search bar size issue when using scaling factor > 1
Public bug reported: When using 'gsettings set org.gnome.desktop.interface text-scaling- factor' command to set the scaling factor to something greater than 1, the text gets misaligned in the search bar, which seems to be too small (shown in an attachment here). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64 Uname: Linux 5.15.0-56-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 525.60.11 Wed Nov 23 23:04:03 UTC 2022 GCC version: ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Dec 18 18:07:13 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GA102 [GeForce RTX 3090] [10de:2204] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GA102 [GeForce RTX 3090] [1043:87b3] InstallationDate: Installed on 2022-12-18 (0 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: ASUS System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-56-generic root=UUID=fc0c0197-bcc1-4eb2-abf4-af87b54ca0e2 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/30/2022 dmi.bios.release: 22.4 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2204 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX Z690-E GAMING WIFI dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2204:bd11/30/2022:br22.4:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXZ690-EGAMINGWIFI:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: 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: ASUS version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.5 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ubuntu ** Attachment added: "font alignment issue" https://bugs.launchpad.net/bugs/224/+attachment/5636288/+files/Screenshot%20from%202022-12-18%2018-10-45.png -- 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/224 Title: Font alignment/search bar size issue when using scaling factor > 1 Status in xorg package in Ubuntu: New Bug description: When using 'gsettings set org.gnome.desktop.interface text-scaling- factor' command to set the scaling factor to something greater than 1, the text gets misaligned in the search bar, which seems to be too small (shown in an attachment here). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64 Uname: Linux 5.15.0-56-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 525.60.11 Wed Nov 23 23:04:03 UTC 2022 GCC version: ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied:
[Desktop-packages] [Bug 2000023] [NEW] Can not load images from external devices
Public bug reported: I'm using the snap version, 42.3 with latest stable Ubuntu. When I try to open a file from a external device (let's say something I mounted in /media/) I can not open that file using EOG. I tried with the snap of Shotwell (0.30.16) and seems like it's possible to see the image so it seems related with permissions of the snapcraft build ** Affects: eog (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to eog in Ubuntu. https://bugs.launchpad.net/bugs/223 Title: Can not load images from external devices Status in eog package in Ubuntu: New Bug description: I'm using the snap version, 42.3 with latest stable Ubuntu. When I try to open a file from a external device (let's say something I mounted in /media/) I can not open that file using EOG. I tried with the snap of Shotwell (0.30.16) and seems like it's possible to see the image so it seems related with permissions of the snapcraft build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eog/+bug/223/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2000022] [NEW] app icon highlighting is glitched when a file is opened in the file explorer
Public bug reported: When I open a text file in Files with an application that has not been added to favorites, the app highlighting (white rounded rectangle around the icon) is glitched. For example, I have attached a screenshot showing the app highlighting when I open a text file from files without having 'gedit' added to favorites. The gedit icon in the dock is glitched. Other app icons will also glitch in this way. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell-extension-ubuntu-dock 72~ubuntu5.22.04.1 ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64 Uname: Linux 5.15.0-56-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Dec 18 17:49:46 2022 InstallationDate: Installed on 2022-12-18 (0 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ** Attachment added: "app highlighting glitch for gedit" https://bugs.launchpad.net/bugs/222/+attachment/5636284/+files/Screenshot%20from%202022-12-18%2017-54-58.png -- 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/222 Title: app icon highlighting is glitched when a file is opened in the file explorer Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: When I open a text file in Files with an application that has not been added to favorites, the app highlighting (white rounded rectangle around the icon) is glitched. For example, I have attached a screenshot showing the app highlighting when I open a text file from files without having 'gedit' added to favorites. The gedit icon in the dock is glitched. Other app icons will also glitch in this way. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell-extension-ubuntu-dock 72~ubuntu5.22.04.1 ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64 Uname: Linux 5.15.0-56-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Dec 18 17:49:46 2022 InstallationDate: Installed on 2022-12-18 (0 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/222/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1978838] Re: Couldn't connect to accessibility bus
Fully patched Ubuntu 22.04, Dec 18, evince 43.3.2 runs fine until a print or print preview is tried on a ps file, resulting in the same error: $ evince fern.ps GPL Ghostscript 9.55.0: Unrecoverable error, exit code 1 (libspectre) ghostscript reports: fatal internal error -100 (evince-previewer:13644): dbind-WARNING **: 11:49:59.120: Couldn't connect to accessibility bus: Failed to connect to socket /run/user/1000/at-spi/bus_1: Permission denied The print icon shows the correct printers, the preview produces a blank window and the error, the Print produces a blank page and the error. Several ps files tried, resulting in the same error. No edits of system files were done. Patches mentioned seem to have been applied successfully. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1978838 Title: Couldn't connect to accessibility bus Status in evince package in Ubuntu: Fix Released Status in evince source package in Jammy: Fix Released Bug description: * Impact the apparmor profile blocks the connection to the accessibility bus since it hasn't been updated for the new socket location, https://gitlab.gnome.org/GNOME/at-spi2-core/-/issues/43 * Test Case start evince, it shouldn't print the warning dbind-WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /run/user/UID/at-spi/bus_0: Permission denied start orca, it should be able to read the content of evince * Regression potential The change is only allowing an extra location in the apparmor profile, we kept also the old path for compatibility reasons and for making the profile easier to share between series. Allowing the extra location shouldn't create a regression but if the change was incorrect it is possible that evince would still bot be able to connect to the bus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1978838/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1968622] Re: [NBD-WXX9, Intel Tigerlake HDMI, Digital Out, HDMI] Pulseaudio fails to detect card.
the same problem Distributor ID: Ubuntu Description:Ubuntu 22.04.1 LTS Release:22.04 Codename: jammy description: Notebook product: NBD-WXX9 (C100) vendor: HUAWEI version: M1010 width: 64 bits capabilities: smbios-3.3.0 dmi-3.3.0 smp vsyscall32 configuration: chassis=notebook family=MateBook D sku=C100 uuid=582d4292-1432-43ee-960e-5554e3d9992d 00:1f.3 Multimedia audio controller: Intel Corporation Tiger Lake-LP Smart Sound Technology Audio Controller (rev 20) Subsystem: QUANTA Computer Inc Tiger Lake-LP Smart Sound Technology Audio Controller Flags: bus master, fast devsel, latency 32, IRQ 146 Memory at 600112 (64-bit, non-prefetchable) [size=16K] Memory at 600100 (64-bit, non-prefetchable) [size=1M] Capabilities: Kernel driver in use: sof-audio-pci-intel-tgl Kernel modules: snd_hda_intel, snd_sof_pci_intel_tgl -- 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/1968622 Title: [NBD-WXX9, Intel Tigerlake HDMI, Digital Out, HDMI] Pulseaudio fails to detect card. Status in pulseaudio package in Ubuntu: Confirmed Bug description: Audio only had "Dummy output" as output but after running: $ echo "options snd-hda-intel model=generic" | sudo tee -a /etc/modprobe.d/alsa-base.conf $ echo "options snd-hda-intel dmic_detect=0" | sudo tee -a /etc/modprobe.d/alsa-base.conf $ echo "blacklist snd_soc_skl" | sudo tee -a /etc/modprobe.d/blacklist.conf audio output changed to HDMI/Built-in-Audio however the sound is still not working sound ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.13 ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2p', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D7c', '/dev/snd/pcmC0D6c', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Apr 11 22:58:11 2022 InstallationDate: Installed on 2022-03-23 (19 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) SourcePackage: pulseaudio Symptom: audio Symptom_Card: sof-hda-dsp - sof-hda-dsp Symptom_Jack: Digital Out, HDMI Title: [NBD-WXX9, Intel Tigerlake HDMI, Digital Out, HDMI] Pulseaudio fails to detect card UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/09/2021 dmi.bios.release: 2.19 dmi.bios.vendor: HUAWEI dmi.bios.version: 2.19 dmi.board.asset.tag: N/A dmi.board.name: NBD-WXX9-PCB-B4 dmi.board.vendor: HUAWEI dmi.board.version: M1010 dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: HUAWEI dmi.chassis.version: M1010 dmi.ec.firmware.release: 2.19 dmi.modalias: dmi:bvnHUAWEI:bvr2.19:bd12/09/2021:br2.19:efr2.19:svnHUAWEI:pnNBD-WXX9:pvrM1010:rvnHUAWEI:rnNBD-WXX9-PCB-B4:rvrM1010:cvnHUAWEI:ct10:cvrM1010:skuC100: dmi.product.family: MateBook D dmi.product.name: NBD-WXX9 dmi.product.sku: C100 dmi.product.version: M1010 dmi.sys.vendor: HUAWEI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1968622/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1999993] Re: The following packages have been kept back (ubuntu-wallpapers)
Status changed to 'Fix Released' because the packages now can be updated with the Software Updater tool. ** Changed in: xorg (Ubuntu) Status: Confirmed => Fix Released -- 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/193 Title: The following packages have been kept back (ubuntu-wallpapers) Status in xorg package in Ubuntu: Fix Released Bug description: Ubuntu version: 22.10 Version of the packages: ubuntu-wallpapers: Installed: 22.10.2-0ubuntu1. Candidate: 22.10.2ubuntu1-0ubuntu1 ubuntu-wallpapers-kinetic: Installed: 22.10.2-0ubuntu1. Candidate: 22.10.2ubuntu1-0ubuntu1 What is expected to happen: upgrade packages via apt-get upgrade. What happened instead: packages not upgrading, with a message saying "the following packages have been kept back: ubuntu-wallpapers ubuntu- wallpapers-kinetic. apt-get install ubuntu-wallpapers ubuntu- wallpapers-kinetic or other workarounds don't work as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/193/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1977715]
Looks fixed to me. I've been cleaning up some more mail and it hasn't
hung once. LGTM :)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to thunderbird in Ubuntu.
https://bugs.launchpad.net/bugs/1977715
Title:
thunderbird 91.9.1 (jammy) sometimes deadlocks when moving mails from
INBOX
Status in Mozilla Thunderbird:
New
Status in thunderbird package in Ubuntu:
Triaged
Bug description:
SUMMARY
---
When moving e-mail from my INBOX to subfolders Thunderbird hangs and
goes into an unusable state. The '"Thunderbird Mail" is not
responding' pops up, and there is no option but to 'Force Quit'
(because 'Wait' isn't helping).
This does not happen for every move. But yesterday when sorting my
INBOX, it happened more than 5 times in total.
DESCRIPTION
---
When moving mail,
- I select one or more from the middle pane;
- drag it/them to the left (folder pane).
- There, I hover above the right folder and wait for it to highlight.
- Upon highlight, I release the mouse.
Normally this moves the e-mail(s) to that folder, but now I get a
deadlock in about 1 out of 20 moves.
On Focal, I used all versions, including
- 1:91.7.0+build2-0ubuntu0.20.04.1
- 1:91.8.1+build1-0ubuntu0.20.04.1
- 1:91.9.1+build1-0ubuntu0.20.04.1
On Jammy, I'm at:
- 1:91.9.1+build1-0ubuntu0.22.04.1
The first time I noticed this issue, was while I'm on Jammy. But, I
hadn't cleaned my mailbox in a while, so it _might_ be related to the
Thunderbird version. Although I my money would be on the version in
conjunction with Jammy (Wayland?).)
OBSERVATIONS
- My INBOX is not big. It contained 2,500 mails or so. (And very few
large e-mails.) The destination folders aren't particularly big
either. And I didn't see a pattern related to which destination
folder.
- When starting thunderbird from the command line, I get lots of
these:
###!!! [Parent][DispatchAsyncMessage] Error:
PClientManager::Msg_ExpectFutureClientSource Processing error: message was
deserialized, but the handler returned false (indicating failure)
IPDL protocol error: Handler returned error code!
###!!! [Parent][DispatchAsyncMessage] Error:
PClientManager::Msg_ForgetFutureClientSource Processing error: message was
deserialized, but the handler returned false (indicating failure)
Unsupported modifier, resource creation failed.
XXX: resource creation failed
IPDL protocol error: Handler returned error code!
(But I have no idea what they mean, or whether those log lines were
emitted in the Focal version.)
- Thunderbird runs as a family of three:
/usr/lib/thunderbird/thunderbird
\_ /usr/lib/thunderbird/thunderbird -contentproc -childID 1 -isForBrowser
-prefsLen 1 -prefMapSize 263514 -jsInit 285636 -parentBuildID 20220520005021
-appdir /usr/lib/thunderbird 549186 true tab
\_ /usr/lib/thunderbird/thunderbird -contentproc -childID 2 -isForBrowser
-prefsLen 1 -prefMapSize 263514 -jsInit 285636 -parentBuildID 20220520005021
-appdir /usr/lib/thunderbird 549186 true tab
- Main PID has 248 threads, child 1 has 23, child 2 has 22.
ENVIRONMENT
---
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 22.04 LTS
Release: 22.04
Codename: jammy
$ env | grep ^[GXW] | sort | grep -v GPG
GDMSESSION=ubuntu
GNOME_DESKTOP_SESSION_ID=this-is-deprecated
GNOME_SETUP_DISPLAY=:1
GNOME_SHELL_SESSION_MODE=ubuntu
GNOME_TERMINAL_SCREEN=/org/gnome/Terminal/screen/6a49f69b_ac07_4c6d_b681_a0dada8d38d3
GNOME_TERMINAL_SERVICE=:1.704
GTK_MODULES=gail:atk-bridge
WAYLAND_DISPLAY=wayland-0
XAUTHORITY=/run/user/1000/.mutter-Xwaylandauth.0J31M1
XDG_CONFIG_DIRS=/etc/xdg/xdg-ubuntu:/etc/xdg
XDG_CURRENT_DESKTOP=ubuntu:GNOME
XDG_DATA_DIRS=/usr/share/ubuntu:/usr/local/share/:/usr/share/:/var/lib/snapd/desktop
XDG_MENU_PREFIX=gnome-
XDG_RUNTIME_DIR=/run/user/1000
XDG_SESSION_CLASS=user
XDG_SESSION_DESKTOP=ubuntu
XDG_SESSION_TYPE=wayland
XMODIFIERS=@im=ibus
CHILD 1 STRACE
--
(the following keeps repeating every 2 or 3 seconds)
$ sudo strace -tt -fp 549263 -e'!futex,poll,epoll_wait,restart_syscall'
strace: Process 549263 attached with 23 threads
[pid 549277] 11:04:12.121020 write(9, "\372", 1) = 1
[pid 549263] 11:04:12.121709 read(8, "\372", 1) = 1
[pid 549263] 11:04:12.122327 write(9, "\372", 1) = 1
[pid 549263] 11:04:12.122635 write(13, "\0", 1) = 1
[pid 549265] 11:04:12.122921 read(12, "\0", 1) = 1
[pid 549265] 11:04:12.123142 sendmsg(3, {msg_name=NULL, msg_namelen=0,
msg_iov=[{iov_base="8\0\0\0\24\0\0\0\4\0^\0\1\0\0\0\0\0\0\0\377\377\377\377\377\377\377\377\2733\377\377"...,
iov_len=64},
{iov_base="\10\223\2\351\0\230\264f\372\";9E\314\0\0\0\0\0\0\0\0\0\0\0\0\0\0",
iov_len=28}], msg_iovlen=2, msg_controllen=0, msg_flags=0}, MSG_DONTWAIT
[pid 549263]
[Desktop-packages] [Bug 1999308] Re: Snap keeps uninstalling apt Firefox, and reinstalling snap Firefox
This happened again this morning. Before uninstalling the snap, I typed apt policy firefox which reported: firefox: Installed: 1:1snap1-0ubuntu2 Candidate: 108.0.1+build1-0ubuntu0.22.04.1~mt1 Version table: *** 1:1snap1-0ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status 108.0.1+build1-0ubuntu0.22.04.1~mt1 1001 1001 https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu jammy/main amd64 Packages So note, from 'Candidate', it knows it wasn't supposed to install the snap, but did anyway for some reason and the 'snap' version had been installed. After 'snap remove --purge firefox' and 'apt-get remove firefox' followed by 'apt-get install firefox', apt policy firefox is now showing: firefox: Installed: 108.0.1+build1-0ubuntu0.22.04.1~mt1 Candidate: 108.0.1+build1-0ubuntu0.22.04.1~mt1 Version table: 1:1snap1-0ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages *** 108.0.1+build1-0ubuntu0.22.04.1~mt1 1001 1001 https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status As far as I'm aware nothing happened this morning (or last night - I'm checking every morning) to cause Firefox to install. I didn't run any updates, Software Updater did not come up. It feels as if there's a cron job installed in the system somewhere that forcibly installs the snap version, but I have absolutely no clue what that would be because root's is empty, and none of the /etc/cron* scripts appear to be related to this. Was anything pushed last night that might have triggered this? -- 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/1999308 Title: Snap keeps uninstalling apt Firefox, and reinstalling snap Firefox Status in firefox package in Ubuntu: New Bug description: I have looked on various forums including the search features of Launchpad, help.ubuntu..com, and Google for answers on this but not been able to. I have uninstalled the snap of firefox multiple times, installing the real Firefox from ppa.launchpadcontent.net/mozillateam/ppa/ubuntu/, only for a few days later (once hours later) for snap to uninstall the real thing and install its snap version instead. I have tried a basic sudo snap remove firefox and when that didn't work sudo snap disable firefox sudo snap remove --purget firefox The former should be enough - that's a direct expression of my preferences, some thing like "You should have typed sudo snap remove --do-not-reinstall --disable-auto-ignore-preferences firefox" would not resolve this bug. When installing using apt-get, the correct version is being installed, and snap afterwards does not show the presence of firefox: Get:1 http://us.archive.ubuntu.com/ubuntu jammy/universe amd64 xul-ext-ubufox all 3.4-0ubuntu1.17.10.1 [3,320 B] Get:2 https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu jammy/main amd64 firefox-locale-en amd64 108.0+build2-0ubuntu0.22.04.1~mt1 [831 kB] Get:3 https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu jammy/main amd64 firefox amd64 108.0+build2-0ubuntu0.22.04.1~mt1 [64.9 MB] Name Version RevTracking Publisher Notes authy 2.2.2 12 latest/stable twilio-authy - bare 1.0 5 latest/stable canonical✓ base chromium 108.0.5359.94 2238 latest/stable canonical✓ - code 5235c6bb114latest/stable vscode✓classic core 16-2.57.6 14399 latest/stable canonical✓ core core18 202211032632 latest/stable canonical✓ base core20 202211231738 latest/stable canonical✓ base cups 2.4.2-4 836latest/stable openprinting✓ - gnome-3-28-18043.28.0-19-g98f9e67.98f9e67 161latest/stable canonical✓ - gnome-3-38-20040+git.6f39565 119latest/stable canonical✓ - gtk-common-themes 0.1-81-g442e511 1535 latest/stable/… canonical✓ - onlyoffice-desktopeditors 7.2.1 133latest/stable onlyoffice✓- snap-store 41.3-66-gfe1e325638 latest/stable/… canonical✓ - snapd 2.57.6 17883 latest/stable canonical✓ snapd /var/lib/snapd/seed/snaps contains (once firefox is removed): core18_1880.snap gnome-3-34-1804_36.snap gtk-common-themes_1506.snap
[Desktop-packages] [Bug 1999852] Re: xserver-xorg-core_21.1.3-2ubuntu2.5 segfaults
** Attachment added: "xorg log good" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1999852/+attachment/5636275/+files/xorg-good.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1999852 Title: xserver-xorg-core_21.1.3-2ubuntu2.5 segfaults Status in xorg-server package in Ubuntu: New Bug description: Running xserver-xorg-core_21.1.3-2ubuntu2.3_amd64.deb was fine. Since the recent update to xserver-xorg-core_21.1.3-2ubuntu2.5_amd64.deb Xorg always segfaults at startup. Going back to xserver-xorg-core_21.1.3-2ubuntu2.3_amd64.deb works again. (Tried it multiple times and it is reproducable.) The errors from the last Xorg.log: [54.562] (EE) Backtrace: [54.563] (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x139) [0x560707b09719] [54.564] (EE) 1: /lib/x86_64-linux-gnu/libc.so.6 (__sigaction+0x50) [0x7f40658cd520] [54.564] (EE) 2: /usr/lib/xorg/Xorg (xf86ModeVRefresh+0x4) [0x560707a0e724] [54.565] (EE) unw_get_proc_name failed: no unwind info found [-10] [54.565] (EE) 3: /usr/lib/xorg/modules/drivers/modesetting_drv.so (?+0x0) [0x7f406513b9b0] [54.565] (EE) 4: /usr/lib/xorg/Xorg (xf86ProbeOutputModes+0x147) [0x560707a07e47] [54.565] (EE) 5: /usr/lib/xorg/Xorg (xf86InitialConfiguration+0x191) [0x560707a089b1] [54.565] (EE) unw_get_proc_name failed: no unwind info found [-10] [54.565] (EE) 6: /usr/lib/xorg/modules/drivers/modesetting_drv.so (?+0x0) [0x7f406513f07c] [54.566] (EE) unw_get_proc_name failed: no unwind info found [-10] [54.566] (EE) 7: /usr/lib/xorg/modules/drivers/modesetting_drv.so (?+0x0) [0x7f40651374bf] [54.566] (EE) 8: /usr/lib/xorg/Xorg (InitOutput+0xb8b) [0x5607079d73ab] [54.566] (EE) 9: /usr/lib/xorg/Xorg (InitFonts+0x1dc) [0x56070799734c] [54.567] (EE) 10: /lib/x86_64-linux-gnu/libc.so.6 (__libc_init_first+0x90) [0x7f40658b4d90] [54.567] (EE) 11: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0x80) [0x7f40658b4e40] [54.568] (EE) 12: /usr/lib/xorg/Xorg (_start+0x25) [0x560707980605] [54.568] (EE) [54.568] (EE) Segmentation fault at address 0xa8 [54.568] (EE) Fatal server error: [54.568] (EE) Caught signal 11 (Segmentation fault). Server aborting [54.568] (EE) [54.568] (EE) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1999852/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1999852] Re: xserver-xorg-core_21.1.3-2ubuntu2.5 segfaults
** Attachment added: "xorg log crash" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1999852/+attachment/5636274/+files/xorg-crash.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1999852 Title: xserver-xorg-core_21.1.3-2ubuntu2.5 segfaults Status in xorg-server package in Ubuntu: New Bug description: Running xserver-xorg-core_21.1.3-2ubuntu2.3_amd64.deb was fine. Since the recent update to xserver-xorg-core_21.1.3-2ubuntu2.5_amd64.deb Xorg always segfaults at startup. Going back to xserver-xorg-core_21.1.3-2ubuntu2.3_amd64.deb works again. (Tried it multiple times and it is reproducable.) The errors from the last Xorg.log: [54.562] (EE) Backtrace: [54.563] (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x139) [0x560707b09719] [54.564] (EE) 1: /lib/x86_64-linux-gnu/libc.so.6 (__sigaction+0x50) [0x7f40658cd520] [54.564] (EE) 2: /usr/lib/xorg/Xorg (xf86ModeVRefresh+0x4) [0x560707a0e724] [54.565] (EE) unw_get_proc_name failed: no unwind info found [-10] [54.565] (EE) 3: /usr/lib/xorg/modules/drivers/modesetting_drv.so (?+0x0) [0x7f406513b9b0] [54.565] (EE) 4: /usr/lib/xorg/Xorg (xf86ProbeOutputModes+0x147) [0x560707a07e47] [54.565] (EE) 5: /usr/lib/xorg/Xorg (xf86InitialConfiguration+0x191) [0x560707a089b1] [54.565] (EE) unw_get_proc_name failed: no unwind info found [-10] [54.565] (EE) 6: /usr/lib/xorg/modules/drivers/modesetting_drv.so (?+0x0) [0x7f406513f07c] [54.566] (EE) unw_get_proc_name failed: no unwind info found [-10] [54.566] (EE) 7: /usr/lib/xorg/modules/drivers/modesetting_drv.so (?+0x0) [0x7f40651374bf] [54.566] (EE) 8: /usr/lib/xorg/Xorg (InitOutput+0xb8b) [0x5607079d73ab] [54.566] (EE) 9: /usr/lib/xorg/Xorg (InitFonts+0x1dc) [0x56070799734c] [54.567] (EE) 10: /lib/x86_64-linux-gnu/libc.so.6 (__libc_init_first+0x90) [0x7f40658b4d90] [54.567] (EE) 11: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0x80) [0x7f40658b4e40] [54.568] (EE) 12: /usr/lib/xorg/Xorg (_start+0x25) [0x560707980605] [54.568] (EE) [54.568] (EE) Segmentation fault at address 0xa8 [54.568] (EE) Fatal server error: [54.568] (EE) Caught signal 11 (Segmentation fault). Server aborting [54.568] (EE) [54.568] (EE) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1999852/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1999852] Re: xserver-xorg-core_21.1.3-2ubuntu2.5 segfaults
Did some manual builds: build xserver-xorg-core_21.1.3-2ubuntu2.5 as installed => it segfaults removed all patches that were added 2.3 => worked bisecting ended with the bad patch being re-calculate-the-clock-and- refresh-rate.diff. Verified with xserver-xorg-core_21.1.3-2ubuntu2.5 and only disabled that patch => worked -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1999852 Title: xserver-xorg-core_21.1.3-2ubuntu2.5 segfaults Status in xorg-server package in Ubuntu: New Bug description: Running xserver-xorg-core_21.1.3-2ubuntu2.3_amd64.deb was fine. Since the recent update to xserver-xorg-core_21.1.3-2ubuntu2.5_amd64.deb Xorg always segfaults at startup. Going back to xserver-xorg-core_21.1.3-2ubuntu2.3_amd64.deb works again. (Tried it multiple times and it is reproducable.) The errors from the last Xorg.log: [54.562] (EE) Backtrace: [54.563] (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x139) [0x560707b09719] [54.564] (EE) 1: /lib/x86_64-linux-gnu/libc.so.6 (__sigaction+0x50) [0x7f40658cd520] [54.564] (EE) 2: /usr/lib/xorg/Xorg (xf86ModeVRefresh+0x4) [0x560707a0e724] [54.565] (EE) unw_get_proc_name failed: no unwind info found [-10] [54.565] (EE) 3: /usr/lib/xorg/modules/drivers/modesetting_drv.so (?+0x0) [0x7f406513b9b0] [54.565] (EE) 4: /usr/lib/xorg/Xorg (xf86ProbeOutputModes+0x147) [0x560707a07e47] [54.565] (EE) 5: /usr/lib/xorg/Xorg (xf86InitialConfiguration+0x191) [0x560707a089b1] [54.565] (EE) unw_get_proc_name failed: no unwind info found [-10] [54.565] (EE) 6: /usr/lib/xorg/modules/drivers/modesetting_drv.so (?+0x0) [0x7f406513f07c] [54.566] (EE) unw_get_proc_name failed: no unwind info found [-10] [54.566] (EE) 7: /usr/lib/xorg/modules/drivers/modesetting_drv.so (?+0x0) [0x7f40651374bf] [54.566] (EE) 8: /usr/lib/xorg/Xorg (InitOutput+0xb8b) [0x5607079d73ab] [54.566] (EE) 9: /usr/lib/xorg/Xorg (InitFonts+0x1dc) [0x56070799734c] [54.567] (EE) 10: /lib/x86_64-linux-gnu/libc.so.6 (__libc_init_first+0x90) [0x7f40658b4d90] [54.567] (EE) 11: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0x80) [0x7f40658b4e40] [54.568] (EE) 12: /usr/lib/xorg/Xorg (_start+0x25) [0x560707980605] [54.568] (EE) [54.568] (EE) Segmentation fault at address 0xa8 [54.568] (EE) Fatal server error: [54.568] (EE) Caught signal 11 (Segmentation fault). Server aborting [54.568] (EE) [54.568] (EE) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1999852/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1977715] Re: thunderbird 91.9.1 (jammy) sometimes deadlocks when moving mails from INBOX
No it does not.
I've been cleaning up my inbox a bit, and I got it to crash really fast
before. Now I've been running for days without issues.
LGTM
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to thunderbird in Ubuntu.
https://bugs.launchpad.net/bugs/1977715
Title:
thunderbird 91.9.1 (jammy) sometimes deadlocks when moving mails from
INBOX
Status in Mozilla Thunderbird:
New
Status in thunderbird package in Ubuntu:
Triaged
Bug description:
SUMMARY
---
When moving e-mail from my INBOX to subfolders Thunderbird hangs and
goes into an unusable state. The '"Thunderbird Mail" is not
responding' pops up, and there is no option but to 'Force Quit'
(because 'Wait' isn't helping).
This does not happen for every move. But yesterday when sorting my
INBOX, it happened more than 5 times in total.
DESCRIPTION
---
When moving mail,
- I select one or more from the middle pane;
- drag it/them to the left (folder pane).
- There, I hover above the right folder and wait for it to highlight.
- Upon highlight, I release the mouse.
Normally this moves the e-mail(s) to that folder, but now I get a
deadlock in about 1 out of 20 moves.
On Focal, I used all versions, including
- 1:91.7.0+build2-0ubuntu0.20.04.1
- 1:91.8.1+build1-0ubuntu0.20.04.1
- 1:91.9.1+build1-0ubuntu0.20.04.1
On Jammy, I'm at:
- 1:91.9.1+build1-0ubuntu0.22.04.1
The first time I noticed this issue, was while I'm on Jammy. But, I
hadn't cleaned my mailbox in a while, so it _might_ be related to the
Thunderbird version. Although I my money would be on the version in
conjunction with Jammy (Wayland?).)
OBSERVATIONS
- My INBOX is not big. It contained 2,500 mails or so. (And very few
large e-mails.) The destination folders aren't particularly big
either. And I didn't see a pattern related to which destination
folder.
- When starting thunderbird from the command line, I get lots of
these:
###!!! [Parent][DispatchAsyncMessage] Error:
PClientManager::Msg_ExpectFutureClientSource Processing error: message was
deserialized, but the handler returned false (indicating failure)
IPDL protocol error: Handler returned error code!
###!!! [Parent][DispatchAsyncMessage] Error:
PClientManager::Msg_ForgetFutureClientSource Processing error: message was
deserialized, but the handler returned false (indicating failure)
Unsupported modifier, resource creation failed.
XXX: resource creation failed
IPDL protocol error: Handler returned error code!
(But I have no idea what they mean, or whether those log lines were
emitted in the Focal version.)
- Thunderbird runs as a family of three:
/usr/lib/thunderbird/thunderbird
\_ /usr/lib/thunderbird/thunderbird -contentproc -childID 1 -isForBrowser
-prefsLen 1 -prefMapSize 263514 -jsInit 285636 -parentBuildID 20220520005021
-appdir /usr/lib/thunderbird 549186 true tab
\_ /usr/lib/thunderbird/thunderbird -contentproc -childID 2 -isForBrowser
-prefsLen 1 -prefMapSize 263514 -jsInit 285636 -parentBuildID 20220520005021
-appdir /usr/lib/thunderbird 549186 true tab
- Main PID has 248 threads, child 1 has 23, child 2 has 22.
ENVIRONMENT
---
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 22.04 LTS
Release: 22.04
Codename: jammy
$ env | grep ^[GXW] | sort | grep -v GPG
GDMSESSION=ubuntu
GNOME_DESKTOP_SESSION_ID=this-is-deprecated
GNOME_SETUP_DISPLAY=:1
GNOME_SHELL_SESSION_MODE=ubuntu
GNOME_TERMINAL_SCREEN=/org/gnome/Terminal/screen/6a49f69b_ac07_4c6d_b681_a0dada8d38d3
GNOME_TERMINAL_SERVICE=:1.704
GTK_MODULES=gail:atk-bridge
WAYLAND_DISPLAY=wayland-0
XAUTHORITY=/run/user/1000/.mutter-Xwaylandauth.0J31M1
XDG_CONFIG_DIRS=/etc/xdg/xdg-ubuntu:/etc/xdg
XDG_CURRENT_DESKTOP=ubuntu:GNOME
XDG_DATA_DIRS=/usr/share/ubuntu:/usr/local/share/:/usr/share/:/var/lib/snapd/desktop
XDG_MENU_PREFIX=gnome-
XDG_RUNTIME_DIR=/run/user/1000
XDG_SESSION_CLASS=user
XDG_SESSION_DESKTOP=ubuntu
XDG_SESSION_TYPE=wayland
XMODIFIERS=@im=ibus
CHILD 1 STRACE
--
(the following keeps repeating every 2 or 3 seconds)
$ sudo strace -tt -fp 549263 -e'!futex,poll,epoll_wait,restart_syscall'
strace: Process 549263 attached with 23 threads
[pid 549277] 11:04:12.121020 write(9, "\372", 1) = 1
[pid 549263] 11:04:12.121709 read(8, "\372", 1) = 1
[pid 549263] 11:04:12.122327 write(9, "\372", 1) = 1
[pid 549263] 11:04:12.122635 write(13, "\0", 1) = 1
[pid 549265] 11:04:12.122921 read(12, "\0", 1) = 1
[pid 549265] 11:04:12.123142 sendmsg(3, {msg_name=NULL, msg_namelen=0,
msg_iov=[{iov_base="8\0\0\0\24\0\0\0\4\0^\0\1\0\0\0\0\0\0\0\377\377\377\377\377\377\377\377\2733\377\377"...,
iov_len=64},
{iov_base="\10\223\2\351\0\230\264f\372\";9E\314\0\0\0\0\0\0\0\0\0\0\0\0\0\0",
iov_len=28}], msg_iovlen=2,
[Desktop-packages] [Bug 1934579] Re: Nautilus crashes when opening places from the dock context menu [SIGSEGV in delete_outdated_error_traps() from gdk_x11_display_error_trap_push()]
Bug fixed after updating to kinetic-proposed/nautilus/1:43.0-1ubuntu2 Testing procedure: Booted with Wayland Reproduced bug (as described in test case above) Updated to kinetic-proposed/nautilus/1:43.0-1ubuntu2 Rebooted with Wayland Performed test case as above Already open Nautilus windows remain and window for selected place opens as expected ** Tags removed: verification-needed-kinetic ** Tags added: verification-done-kinetic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1934579 Title: Nautilus crashes when opening places from the dock context menu [SIGSEGV in delete_outdated_error_traps() from gdk_x11_display_error_trap_push()] Status in nautilus package in Ubuntu: Fix Released Status in nautilus source package in Jammy: Fix Committed Status in nautilus source package in Kinetic: Fix Committed Bug description: [ Impact ] Nautilus crashes when a bookmarked place is opened from dock icon context menu [ Test case ] 1. Open Nautilus (and ensure you've a location in the sidebar bookmarks) 2. Right-click ubuntu dock nautilus icon 3. Activate one of the bookmarks 4. Nautilus should open that location without crashing. [ Regression potential ] A window may not be raised when opened under wayland. --- After updating to Ubuntu 21.04, Nautilus crashes every time I try to open a second folder by right-clicking on the Nautilus icon in the "Favorites" left sidebar (i.e., launch panel) and selecting a bookmarked "Places" folder. Normally, this would open a second Nautilus window for the selected folder, but instead, any open Nautilus windows disappear and no window opens for the selected folder. In other words, Nautilus crashes. This did not occur on Ubuntu 20.10. This AskUbuntu post describes the same issue: https://askubuntu.com/questions/1344175/nautilus-crashes-when-trying- to-open-another-window-by-right-clicking-the-nautil If, instead, I right-click the Nautilus icon, select "New Window" and then select the desired "Places" folder from the left sidebar of the newly opened window, Nautilus does not crash. ProblemType: BugDistroRelease: Ubuntu 21.04 Package: nautilus 1:3.38.2-1ubuntu2 ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Jul 4 13:36:13 2021 InstallationDate: Installed on 2020-02-05 (514 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)SourcePackage: nautilus UpgradeStatus: Upgraded to hirsute on 2021-06-30 (4 days ago) usr_lib_nautilus: evince40.1-1 file-roller 3.38.1-1 nautilus-extension-gnome-terminal 3.38.1-1ubuntu1 nautilus-share0.7.3-2ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1934579/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1999993] Re: The following packages have been kept back (ubuntu-wallpapers)
my 5 cents: ``` # apt list --upgradable Listing... Done ubuntu-wallpapers-kinetic/kinetic-updates,kinetic-updates 22.10.2ubuntu1-0ubuntu1 all [upgradable from: 22.10.2-0ubuntu1] ubuntu-wallpapers/kinetic-updates,kinetic-updates 22.10.2ubuntu1-0ubuntu1 all [upgradable from: 22.10.2-0ubuntu1] ``` -- 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/193 Title: The following packages have been kept back (ubuntu-wallpapers) Status in xorg package in Ubuntu: Confirmed Bug description: Ubuntu version: 22.10 Version of the packages: ubuntu-wallpapers: Installed: 22.10.2-0ubuntu1. Candidate: 22.10.2ubuntu1-0ubuntu1 ubuntu-wallpapers-kinetic: Installed: 22.10.2-0ubuntu1. Candidate: 22.10.2ubuntu1-0ubuntu1 What is expected to happen: upgrade packages via apt-get upgrade. What happened instead: packages not upgrading, with a message saying "the following packages have been kept back: ubuntu-wallpapers ubuntu- wallpapers-kinetic. apt-get install ubuntu-wallpapers ubuntu- wallpapers-kinetic or other workarounds don't work as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/193/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1999993] Re: The following packages have been kept back (ubuntu-wallpapers)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xorg (Ubuntu) Status: New => Confirmed -- 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/193 Title: The following packages have been kept back (ubuntu-wallpapers) Status in xorg package in Ubuntu: Confirmed Bug description: Ubuntu version: 22.10 Version of the packages: ubuntu-wallpapers: Installed: 22.10.2-0ubuntu1. Candidate: 22.10.2ubuntu1-0ubuntu1 ubuntu-wallpapers-kinetic: Installed: 22.10.2-0ubuntu1. Candidate: 22.10.2ubuntu1-0ubuntu1 What is expected to happen: upgrade packages via apt-get upgrade. What happened instead: packages not upgrading, with a message saying "the following packages have been kept back: ubuntu-wallpapers ubuntu- wallpapers-kinetic. apt-get install ubuntu-wallpapers ubuntu- wallpapers-kinetic or other workarounds don't work as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/193/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2000001] [NEW] Wifi AX dropped randomly if ipv6 is enabled no Error on Logs!
Private bug reported: Hi Support i disabled all ipv6 on my Subnet LAN Routers, and my Laptop loses "randomly" 20times a day the Internet but the Signal is 100% to the WIFI-Routers, no ping, no nslookup to first DSL-WAN Router possible. No dmesg Errors seen.. After i manual enable/disable WIFI by switch is works again fast. After some search on Net i disabled ipv6 in sysctl.conf ! Seen on network-manager/network-manager-gnome/wicd Managers I tested / changed 3 different old wifi-5+ new wifi-6 intel AX 7260 HMW mini-pci-cards same problem! Now testing again.. Thanks Linuxonlinehelp_eu ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1.4 ProcVersionSignature: Ubuntu 5.4.0-135.152~18.04.2-generic 5.4.212 Uname: Linux 5.4.0-135-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.28 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Dec 18 11:24:20 2022 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2021-08-19 (486 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IpRoute: default via 192.168.71.1 dev wlp3s0b1 proto dhcp metric 600 169.254.0.0/16 dev wlp3s0b1 scope link metric 1000 192.168.71.0/24 dev wlp3s0b1 proto kernel scope link src 192.168.71.123 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: http_proxy: http://127.0.0.1:8118/ modified.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf: [connection] wifi.powersave = 2 mtime.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf: 2022-06-30T19:17:37.737049 nmcli-dev: DEVICETYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlp3s0b1 wifi connected/org/freedesktop/NetworkManager/Devices/3 AXWIFI71bec4545b-24e6-40ef-a933-43121b9b819b /org/freedesktop/NetworkManager/ActiveConnection/3 enp2s0ethernet unavailable /org/freedesktop/NetworkManager/Devices/2 -- ---- loloopback unmanaged/org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected started full enabled enabled enabled enabled enabled no_proxy: ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Affects: network-manager-applet (Ubuntu) Importance: Undecided Status: New ** Affects: wicd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Information type changed from Public to Private ** Also affects: network-manager-applet (Ubuntu) Importance: Undecided Status: New ** Also affects: wicd (Ubuntu) Importance: Undecided Status: New ** Description changed: Hi Support - i disables all ipv6 on my Subnet LAN Routers, - and my Laptop loses Internet but the Signal is 100% to - the Routers, no ping, no nslookup to first DSL-WAN Router possible. + i disabled all ipv6 on my Subnet LAN Routers, + and my Laptop loses "randomly" 20times a day the Internet but the Signal is 100% to the WIFI-Routers, no ping, no nslookup to first DSL-WAN Router possible. + + No dmesg Errors seen.. + After i manual enable/disable WIFI by switch is works again fast. - After some search on Net i disabled ipv6 in sysctl.conf - seen on network-manager/network-manager-gnome/wicd - changed 3 different mini-pci-cards same problem! + After some search on Net i disabled ipv6 in sysctl.conf ! + + Seen on network-manager/network-manager-gnome/wicd Managers + + I tested / changed 3 different old wifi-5+ new wifi-6 intel AX 7260 HMW + mini-pci-cards same problem! Now testing again.. - + Thanks Linuxonlinehelp_eu ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1.4 ProcVersionSignature: Ubuntu 5.4.0-135.152~18.04.2-generic 5.4.212 Uname: Linux 5.4.0-135-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.28 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Dec 18 11:24:20 2022 IfupdownConfig: - # interfaces(5) file used by ifup(8) and ifdown(8) - auto lo - iface lo inet loopback + # interfaces(5) file used by ifup(8) and ifdown(8) + auto lo + iface lo inet loopback InstallationDate: Installed on 2021-08-19 (486 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IpRoute: - default via 192.168.71.1 dev wlp3s0b1 proto dhcp metric 600 - 169.254.0.0/16 dev wlp3s0b1 scope link metric 1000 - 192.168.71.0/24 dev wlp3s0b1
