[Desktop-packages] [Bug 848183]
Created attachment 9426227 WIP: Bug 11013 - Implement drag and drop of attached messages to mail folders. -- 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/848183 Title: RFC822 Attachments and .EML files cannot be moved to folders Status in Mozilla Thunderbird: Confirmed Status in thunderbird package in Ubuntu: Confirmed Bug description: From https://wiki.mozilla.org/Thunderbird:Fix_some_longstanding_bugs#RFC822_Attachments_and_.EML_files: "It should be possible to file (import) the attachment or the .EML file directly into a mail folder (bug 11013 / bug 226877, bug 204612). The menu action Message | Copy To | folder would be an elegant way to implement this." ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: thunderbird 3.1.13+build1+nobinonly-0ubuntu0.11.04.1 ProcVersionSignature: Ubuntu 2.6.38-11.48-generic 2.6.38.8 Uname: Linux 2.6.38-11-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Mon Sep 12 15:02:59 2011 InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100427.1) ProcEnviron: LANGUAGE=en_CA:en LANG=en_CA.UTF-8 SHELL=/bin/zsh SourcePackage: thunderbird UpgradeStatus: Upgraded to natty on 2011-04-30 (135 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/848183/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2078866] [NEW] Laptop will not charge, will charge when powered down or on Windows
Public bug reported: I have tried Ubuntu 20.04, 22.04, 24.04.01. Also tried Debian and Mint. Will not charge on any variant of Debian. Charge indicator stays at whatever value was present before booting Linux. Shows 0 charge rate. Tried multiple acpi settings and changing kernels. Will only not charge in Ubuntu. Purchased a new battery and have the same results as previous battery. native-path: BAT0 vendor: 13-42 model:HS04041 serial: 5938 power supply: yes updated: Mon 02 Sep 2024 12:27:07 PM PDT (48 seconds ago) has history: yes has statistics: yes battery present: yes rechargeable:yes state: charging warning-level: none energy: 24.7392 Wh energy-empty:0 Wh energy-full: 37.9872 Wh energy-full-design: 37.9872 Wh energy-rate: 0 W voltage: 15.251 V charge-cycles: N/A percentage: 65% capacity:100% technology: lithium-ion icon-name: 'battery-full-charging-symbolic' ** Affects: upower (Ubuntu) Importance: Undecided Status: New ** Description changed: - I have tried Ubuntu 20.04, 22.04, 24.04.01. Also tried Debian and Mint. - Will not charge on any variant of Debian. Charge indicator stays at - whatever value was present before booting Linux. Shows 0 charge rate. - Tried multiple acpi settings and changing kernels. Will only not charge - in Ubuntu. + I have tried Ubuntu 20.04, 22.04, 24.04.01. Also tried Debian and Mint. Will not charge on any variant of Debian. Charge indicator stays at whatever value was present before booting Linux. Shows 0 charge rate. Tried multiple acpi settings and changing kernels. Will only not charge in Ubuntu. + Purchased a new battery and have the same results as previous battery. native-path: BAT0 - vendor: 13-42 - model:HS04041 - serial: 5938 - power supply: yes - updated: Mon 02 Sep 2024 12:27:07 PM PDT (48 seconds ago) - has history: yes - has statistics: yes - battery - present: yes - rechargeable:yes - state: charging - warning-level: none - energy: 24.7392 Wh - energy-empty:0 Wh - energy-full: 37.9872 Wh - energy-full-design: 37.9872 Wh - energy-rate: 0 W - voltage: 15.251 V - charge-cycles: N/A - percentage: 65% - capacity:100% - technology: lithium-ion - icon-name: 'battery-full-charging-symbolic' + vendor: 13-42 + model:HS04041 + serial: 5938 + power supply: yes + updated: Mon 02 Sep 2024 12:27:07 PM PDT (48 seconds ago) + has history: yes + has statistics: yes + battery + present: yes + rechargeable:yes + state: charging + warning-level: none + energy: 24.7392 Wh + energy-empty:0 Wh + energy-full: 37.9872 Wh + energy-full-design: 37.9872 Wh + energy-rate: 0 W + voltage: 15.251 V + charge-cycles: N/A + percentage: 65% + capacity:100% + technology: lithium-ion + icon-name: 'battery-full-charging-symbolic' -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/2078866 Title: Laptop will not charge, will charge when powered down or on Windows Status in upower package in Ubuntu: New Bug description: I have tried Ubuntu 20.04, 22.04, 24.04.01. Also tried Debian and Mint. Will not charge on any variant of Debian. Charge indicator stays at whatever value was present before booting Linux. Shows 0 charge rate. Tried multiple acpi settings and changing kernels. Will only not charge in Ubuntu. Purchased a new battery and have the same results as previous battery. native-path: BAT0 vendor: 13-42 model:HS04041 serial: 5938 power supply: yes updated: Mon 02 Sep 2024 12:27:07 PM PDT (48 seconds ago) has history: yes has statistics: yes battery present: yes rechargeable:yes state: charging warning-level: none energy: 24.7392 Wh energy-empty:0 Wh energy-full: 37.9872 Wh energy-full-design: 37.9872 Wh energy-rate: 0 W voltage: 15.251 V charge-cycles: N/A percentage:
[Desktop-packages] [Bug 2078500] [NEW] Problems in updating programs over Discover on 24.04LTS
Public bug reported: After updating the system to 24.04 LTS I wanted to update over 2000 programs, but first I get the following message: Systempaket kann nicht entfernt werden: WARNING: You are trying to remove the following essential packages: libapt-pkg6.0 (due to apt) libgnutls30 (due to apt) libext2fs2 (due to e2fsprogs) So I can't update anything. ** Affects: sane-backends (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Problems in updating programs over Doscover on 24.04LTS + Problems in updating programs over Discover on 24.04LTS -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/2078500 Title: Problems in updating programs over Discover on 24.04LTS Status in sane-backends package in Ubuntu: New Bug description: After updating the system to 24.04 LTS I wanted to update over 2000 programs, but first I get the following message: Systempaket kann nicht entfernt werden: WARNING: You are trying to remove the following essential packages: libapt-pkg6.0 (due to apt) libgnutls30 (due to apt) libext2fs2 (due to e2fsprogs) So I can't update anything. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/2078500/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2056543] Re: Ubuntu 24.04 breaking gnome, showing "Oops.." requesting logout, and several instabilities when using GDM3 instead of Waylan after upgrading from 22.04 to 24.04
*** This bug is a duplicate of bug 2056506 *** https://bugs.launchpad.net/bugs/2056506 OK =) -- 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/2056543 Title: Ubuntu 24.04 breaking gnome, showing "Oops.." requesting logout, and several instabilities when using GDM3 instead of Waylan after upgrading from 22.04 to 24.04 Status in gnome-shell package in Ubuntu: Incomplete Bug description: Ubuntu 24.04 breaking gnome, showing "Oops.." requesting logout, and several instabilities when using GDM3 instead of Waylan after upgrading from 22.04 to 24.04. > Oh no! Something has gone worng; A problem has occurred and the system cant recover. Please log out and try again. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gdm3 45.0.1-1ubuntu2 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 Uname: Linux 6.8.0-11-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Mar 8 07:50:09 2024 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+loki-n3-v3-whl+X32 InstallationDate: Installed on 2020-12-12 (1182 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 ProcEnviron: LANG=pt_BR.UTF-8 LANGUAGE=pt_BR:pt:en PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color SourcePackage: gdm3 UpgradeStatus: Upgraded to noble on 2024-02-28 (9 days ago) mtime.conffile..etc.init.d.apport: 2024-02-22T11:20:00 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2056543/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2056543] Re: Ubuntu 24.04 breaking gnome, showing "Oops.." requesting logout, and several instabilities when using GDM3 instead of Waylan after upgrading from 22.04 to 24.04
Yes. I reproduced it exactly here to validate, when trying to close an APP by clicking on the dock, when closing, the session was immediately logged out. A few days ago, I tried to disable Waylan, but the problems seem to recur more often. But it happens anyway. In some cases, for example, if you try to just block the current session, it also generates behavior. Below is the result of journalctl attached to this. Thanks! ** Attachment added: "prevboot.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2056543/+attachment/5754998/+files/prevboot.txt -- 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/2056543 Title: Ubuntu 24.04 breaking gnome, showing "Oops.." requesting logout, and several instabilities when using GDM3 instead of Waylan after upgrading from 22.04 to 24.04 Status in gnome-shell package in Ubuntu: Incomplete Bug description: Ubuntu 24.04 breaking gnome, showing "Oops.." requesting logout, and several instabilities when using GDM3 instead of Waylan after upgrading from 22.04 to 24.04. > Oh no! Something has gone worng; A problem has occurred and the system cant recover. Please log out and try again. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gdm3 45.0.1-1ubuntu2 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 Uname: Linux 6.8.0-11-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Mar 8 07:50:09 2024 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+loki-n3-v3-whl+X32 InstallationDate: Installed on 2020-12-12 (1182 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 ProcEnviron: LANG=pt_BR.UTF-8 LANGUAGE=pt_BR:pt:en PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color SourcePackage: gdm3 UpgradeStatus: Upgraded to noble on 2024-02-28 (9 days ago) mtime.conffile..etc.init.d.apport: 2024-02-22T11:20:00 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2056543/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2056543] [NEW] Ubuntu 24.04 breaking gnome, showing "Oops.." requesting logout, and several instabilities when using GDM3 instead of Waylan after upgrading from 22.04 to 24.04
Public bug reported: Ubuntu 24.04 breaking gnome, showing "Oops.." requesting logout, and several instabilities when using GDM3 instead of Waylan after upgrading from 22.04 to 24.04. > Oh no! Something has gone worng; A problem has occurred and the system cant recover. Please log out and try again. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gdm3 45.0.1-1ubuntu2 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 Uname: Linux 6.8.0-11-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Mar 8 07:50:09 2024 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+loki-n3-v3-whl+X32 InstallationDate: Installed on 2020-12-12 (1182 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 ProcEnviron: LANG=pt_BR.UTF-8 LANGUAGE=pt_BR:pt:en PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color SourcePackage: gdm3 UpgradeStatus: Upgraded to noble on 2024-02-28 (9 days ago) mtime.conffile..etc.init.d.apport: 2024-02-22T11:20:00 ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble ** Description changed: - Ubuntu 24.04 quebrando o gnome, apresetando "Ops.." solicitando logout, - e varias instabilidades ao usar o GDM3 ao inves de Waylan apos atualizar - do 22.04 para 24.04 + Ubuntu 24.04 breaking gnome, showing "Oops.." requesting logout, and + several instabilities when using GDM3 instead of Waylan after upgrading + from 22.04 to 24.04. + + > Oh no! Something has gone worng; A problem has occurred and the system + cant recover. Please log out and try again. + ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gdm3 45.0.1-1ubuntu2 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 Uname: Linux 6.8.0-11-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Mar 8 07:50:09 2024 DistributionChannelDescriptor: - # This is the distribution channel descriptor for the OEM CDs - # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor - canonical-oem-somerville-bionic-amd64-20180608-47+loki-n3-v3-whl+X32 + # This is the distribution channel descriptor for the OEM CDs + # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor + canonical-oem-somerville-bionic-amd64-20180608-47+loki-n3-v3-whl+X32 InstallationDate: Installed on 2020-12-12 (1182 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 ProcEnviron: - LANG=pt_BR.UTF-8 - LANGUAGE=pt_BR:pt:en - PATH=(custom, no user) - SHELL=/bin/bash - TERM=xterm-256color + LANG=pt_BR.UTF-8 + LANGUAGE=pt_BR:pt:en + PATH=(custom, no user) + SHELL=/bin/bash + TERM=xterm-256color SourcePackage: gdm3 UpgradeStatus: Upgraded to noble on 2024-02-28 (9 days ago) mtime.conffile..etc.init.d.apport: 2024-02-22T11:20:00 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/2056543 Title: Ubuntu 24.04 breaking gnome, showing "Oops.." requesting logout, and several instabilities when using GDM3 instead of Waylan after upgrading from 22.04 to 24.04 Status in gdm3 package in Ubuntu: New Bug description: Ubuntu 24.04 breaking gnome, showing "Oops.." requesting logout, and several instabilities when using GDM3 instead of Waylan after upgrading from 22.04 to 24.04. > Oh no! Something has gone worng; A problem has occurred and the system cant recover. Please log out and try again. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gdm3 45.0.1-1ubuntu2 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 Uname: Linux 6.8.0-11-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Mar 8 07:50:09 2024 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+loki-n3-v3-whl+X32 InstallationDate: Installed on 2020-12-12 (1182 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 ProcEnviron: LANG=pt_BR.UTF-8 LANGUAGE=pt_BR:pt:en PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color SourcePackage: gdm3 UpgradeStatus: Upgraded to noble on 2024-02-28 (9 days ago) mtime.conffile..etc.init.d.apport: 2024-02-22T11:20:00 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2056543/+subscriptions
[Desktop-packages] [Bug 2051875] [NEW] monitor goes to sleep (power save) mode as soon as the system attempts to display the graphical login screen. Attempting to switch to a character console wakes t
Public bug reported: https://askubuntu.com/questions/1500676/is-there-a-solution- for-22-04-and-kernel-6-5-0-14-or-6-5-0-15-22-04-for-users?noredirect=1 I'm running 22.04 LTS with an Asus NVidia GeForce GT 730. I'm using the Ubuntu provided video driver (Nouveau). Since upgrading my kernel to 6.5, I notice that my monitor goes to sleep (power save) mode as soon as the system attempts to display the graphical login screen. Attempting to switch to a character console wakes the monitor but I still have a blank screen. Switching back to the graphical login screen puts the monitor back to sleep. My current solution is to use my previous 6.2 kernel. I've been reading in the forums about users having problems with recompiling their driver source, gcc version mismatches v11 (6.2 kernel) vs v12 (6.5 kernel) and some driver source incompatibilities with the new compiler. I'm wondering how soon users might expect a fix for the stock driver or if we should expect a fix? I've got a 2nd Linux systems also 22.04 with a GT 610 that has no issues with the latest 6.5 kernel. The command dkms status returns nothing. And apt-cache policy gcc-12 returns gcc-12: Installed: (none) Candidate: 12.3.0-1ubuntu1~22.04 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xserver-xorg-video-nouveau 1:1.0.17-2build1 ProcVersionSignature: Ubuntu 6.5.0-15.15~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-15-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDmesg: Error: command ['pkexec', 'dmesg'] failed with exit code 127: Error creating textual authentication agent: Error opening current controlling terminal for the process (`/dev/tty'): No such device or address Date: Wed Jan 31 11:18:16 2024 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GK208B [GeForce GT 730] [10de:1287] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GK208B [GeForce GT 730] [1043:881a] ASPEED Technology, Inc. ASPEED Graphics Family [1a03:2000] (rev 21) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd ASPEED Graphics Family [1458:2000] InstallationDate: Installed on 2023-05-05 (271 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Cirrascale VB1416 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-15-generic root=UUID=8138fb3d-3187-4185-9154-470cb45cf4c4 ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-video-nouveau UpgradeStatus: No upgrade log present (probably fresh install) acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed with exit code 127: Error creating textual authentication agent: Error opening current controlling terminal for the process (`/dev/tty'): No such device or address dmi.bios.date: 06/26/2018 dmi.bios.release: 4.6 dmi.bios.vendor: GIGABYTE dmi.bios.version: R17 dmi.board.asset.tag: 01234567890123456789AN dmi.board.name: GA-7PESH2 dmi.board.vendor: GIGABYTE dmi.board.version: 0001 dmi.chassis.asset.tag: 01234567890123456789AN dmi.chassis.type: 17 dmi.chassis.vendor: Cirrascale dmi.chassis.version: 240272-101 dmi.modalias: dmi:bvnGIGABYTE:bvrR17:bd06/26/2018:br4.6:svnCirrascale:pnVB1416:pvr0002:rvnGIGABYTE:rnGA-7PESH2:rvr0001:cvnCirrascale:ct17:cvr240272-101:sku: dmi.product.family: GIGABYTE Server dmi.product.name: VB1416 dmi.product.version: 0002 dmi.sys.vendor: Cirrascale version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xserver-xorg-video-nouveau (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/2051875 Title: monitor goes to sleep (power save) mode as soon as the system attempts to display the graphical login screen. Attempting to switch to a character console wakes the monitor but I still have a blank screen. Switching back to the graphical login screen puts the monitor back to sleep. Status in xserver-xorg-video-nouveau package in Ubuntu: New Bug description: https://askubuntu.com/questions/15
[Desktop-packages] [Bug 2049306] Re: error update from Ubuntu 20.04 to 22.04 on Raspberry Pi 2B
the approximate translation of the error message would be "subprocess 'new firefox script of package pre-installation' returned error value 1" -- 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/2049306 Title: error update from Ubuntu 20.04 to 22.04 on Raspberry Pi 2B Status in firefox package in Ubuntu: New Bug description: The attached error was generated while I was trying update my Raspberry Pi 2B from Ubuntu 20.04 to 22.04. It somehow appears to be related to firefox. (In the upgrade from 20.04 to 22.04, the firefox debian package appears to be removed in favour of a snap package, but I don't know if this is what causes the error.) ProblemType: Package DistroRelease: Ubuntu 22.04 Package: firefox 120.0.1+build1-0ubuntu0.20.04.1 Uname: Linux 4.4.38-v7+ armv7l AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.27 Architecture: armhf AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lightdm1253 F pulseaudio BuildID: 20231129155202 CasperMD5CheckResult: skip Channel: Unavailable Date: Sun Jan 14 13:44:47 2024 ErrorMessage: »neues firefox-Skript des Paketes pre-installation«-Unterprozess gab den Fehlerwert 1 zurück ForcedLayersAccel: False IpRoute: default via 192.168.1.1 dev enxb827eb50e944 proto static metric 100 169.254.0.0/16 dev enxb827eb50e944 scope link metric 1000 192.168.1.0/24 dev enxb827eb50e944 proto kernel scope link src 192.168.1.17 metric 100 NoProfiles: True PciNetwork: PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.11 RunningIncompatibleAddons: False SourcePackage: firefox Title: package firefox 120.0.1+build1-0ubuntu0.20.04.1 failed to install/upgrade: »neues firefox-Skript des Paketes pre-installation«-Unterprozess gab den Fehlerwert 1 zurück UpgradeStatus: Upgraded to jammy on 2024-01-14 (0 days ago) modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2017-02-11T19:21:47.356345 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2049306/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2049306] [NEW] error update from Ubuntu 20.04 to 22.04 on Raspberry Pi 2B
Public bug reported: The attached error was generated while I was trying update my Raspberry Pi 2B from Ubuntu 20.04 to 22.04. It somehow appears to be related to firefox. (In the upgrade from 20.04 to 22.04, the firefox debian package appears to be removed in favour of a snap package, but I don't know if this is what causes the error.) ProblemType: Package DistroRelease: Ubuntu 22.04 Package: firefox 120.0.1+build1-0ubuntu0.20.04.1 Uname: Linux 4.4.38-v7+ armv7l AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.27 Architecture: armhf AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lightdm1253 F pulseaudio BuildID: 20231129155202 CasperMD5CheckResult: skip Channel: Unavailable Date: Sun Jan 14 13:44:47 2024 ErrorMessage: »neues firefox-Skript des Paketes pre-installation«-Unterprozess gab den Fehlerwert 1 zurück ForcedLayersAccel: False IpRoute: default via 192.168.1.1 dev enxb827eb50e944 proto static metric 100 169.254.0.0/16 dev enxb827eb50e944 scope link metric 1000 192.168.1.0/24 dev enxb827eb50e944 proto kernel scope link src 192.168.1.17 metric 100 NoProfiles: True PciNetwork: PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.11 RunningIncompatibleAddons: False SourcePackage: firefox Title: package firefox 120.0.1+build1-0ubuntu0.20.04.1 failed to install/upgrade: »neues firefox-Skript des Paketes pre-installation«-Unterprozess gab den Fehlerwert 1 zurück UpgradeStatus: Upgraded to jammy on 2024-01-14 (0 days ago) modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2017-02-11T19:21:47.356345 ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package armhf jammy -- 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/2049306 Title: error update from Ubuntu 20.04 to 22.04 on Raspberry Pi 2B Status in firefox package in Ubuntu: New Bug description: The attached error was generated while I was trying update my Raspberry Pi 2B from Ubuntu 20.04 to 22.04. It somehow appears to be related to firefox. (In the upgrade from 20.04 to 22.04, the firefox debian package appears to be removed in favour of a snap package, but I don't know if this is what causes the error.) ProblemType: Package DistroRelease: Ubuntu 22.04 Package: firefox 120.0.1+build1-0ubuntu0.20.04.1 Uname: Linux 4.4.38-v7+ armv7l AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.27 Architecture: armhf AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lightdm1253 F pulseaudio BuildID: 20231129155202 CasperMD5CheckResult: skip Channel: Unavailable Date: Sun Jan 14 13:44:47 2024 ErrorMessage: »neues firefox-Skript des Paketes pre-installation«-Unterprozess gab den Fehlerwert 1 zurück ForcedLayersAccel: False IpRoute: default via 192.168.1.1 dev enxb827eb50e944 proto static metric 100 169.254.0.0/16 dev enxb827eb50e944 scope link metric 1000 192.168.1.0/24 dev enxb827eb50e944 proto kernel scope link src 192.168.1.17 metric 100 NoProfiles: True PciNetwork: PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.11 RunningIncompatibleAddons: False SourcePackage: firefox Title: package firefox 120.0.1+build1-0ubuntu0.20.04.1 failed to install/upgrade: »neues firefox-Skript des Paketes pre-installation«-Unterprozess gab den Fehlerwert 1 zurück UpgradeStatus: Upgraded to jammy on 2024-01-14 (0 days ago) modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2017-02-11T19:21:47.356345 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2049306/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1950703] Re: Keyboard input does't work in several apps with iBus running
After today's package upgrade and a reboot, I can now type into Firefox again without having to kill iBus first. 😊 -- 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/1950703 Title: Keyboard input does't work in several apps with iBus running Status in snapd: New Status in firefox package in Ubuntu: New Bug description: If installed through Snap and with iBus running the keyboard doesn't work in Standard Notes, XMind and Chromium apps on Manjaro 21.1. Killing iBus fixes the issue. The keyboard works in Visual Studio, however snap 2.51.3-2 snapd 2.51.3-2 series 16 manjaro - kernel 5.10.70-1-MANJARO sudo snap connections chromium Interface PlugSlot Notes audio-playbackchromium:audio-playback :audio-playback - audio-record chromium:audio-record :audio-record- bluez chromium:bluez :bluez - browser-support chromium:browser-sandbox :browser-support - camerachromium:camera :camera - content[gnome-3-28-1804] chromium:gnome-3-28-1804 gnome-3-28-1804:gnome-3-28-1804 - content[gtk-3-themes] chromium:gtk-3-themes gtk-common-themes:gtk-3-themes - content[icon-themes] chromium:icon-themes gtk-common-themes:icon-themes- content[sound-themes] chromium:sound-themes gtk-common-themes:sound-themes - cups-control chromium:cups-control :cups-control- desktop chromium:desktop:desktop - desktop-legacychromium:desktop-legacy :desktop-legacy - gsettings chromium:gsettings :gsettings - home chromium:home :home - joystick chromium:joystick :joystick - mount-observe chromium:mount-observe - - mpris - chromium:mpris - network chromium:network:network - network-bind chromium:network-bind :network-bind- network-manager chromium:network-manager- - openglchromium:opengl :opengl - password-manager-service chromium:password-manager-service - - personal-fileschromium:chromium-config :personal-files - pulseaudiochromium:pulseaudio - - raw-usb chromium:raw-usb- - removable-media chromium:removable-media :removable-media - screen-inhibit-controlchromium:screen-inhibit-control :screen-inhibit-control - system-files chromium:etc-chromium-browser-policies :system-files- system-packages-doc chromium:system-packages-doc :system-packages-doc - u2f-devices chromium:u2f-devices :u2f-devices - unity7chromium:unity7 :unity7 - upower-observechromium:upower-observe :upower-observe - wayland chromium:wayland:wayland - x11 chromium:x11:x11 - sudo snap connections standard-notes Interface Plug Slot Notes audio-playbackstandard-notes:audio-playback :audio-playback - browser-support standard-notes:browser-support :browser-support - content[gnome-3-28-1804] standard-notes:gnome-3-28-1804 gnome-3-28-1804:gnome-3-28-1804 - content[gtk-3-themes] standard-notes:gtk-3-themes gtk
[Desktop-packages] [Bug 1950703] Re: Keyboard input does't work in several apps with iBus running
** Also affects: firefox (Ubuntu) Importance: Undecided Status: New -- 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/1950703 Title: Keyboard input does't work in several apps with iBus running Status in snapd: New Status in firefox package in Ubuntu: New Bug description: If installed through Snap and with iBus running the keyboard doesn't work in Standard Notes, XMind and Chromium apps on Manjaro 21.1. Killing iBus fixes the issue. The keyboard works in Visual Studio, however snap 2.51.3-2 snapd 2.51.3-2 series 16 manjaro - kernel 5.10.70-1-MANJARO sudo snap connections chromium Interface PlugSlot Notes audio-playbackchromium:audio-playback :audio-playback - audio-record chromium:audio-record :audio-record- bluez chromium:bluez :bluez - browser-support chromium:browser-sandbox :browser-support - camerachromium:camera :camera - content[gnome-3-28-1804] chromium:gnome-3-28-1804 gnome-3-28-1804:gnome-3-28-1804 - content[gtk-3-themes] chromium:gtk-3-themes gtk-common-themes:gtk-3-themes - content[icon-themes] chromium:icon-themes gtk-common-themes:icon-themes- content[sound-themes] chromium:sound-themes gtk-common-themes:sound-themes - cups-control chromium:cups-control :cups-control- desktop chromium:desktop:desktop - desktop-legacychromium:desktop-legacy :desktop-legacy - gsettings chromium:gsettings :gsettings - home chromium:home :home - joystick chromium:joystick :joystick - mount-observe chromium:mount-observe - - mpris - chromium:mpris - network chromium:network:network - network-bind chromium:network-bind :network-bind- network-manager chromium:network-manager- - openglchromium:opengl :opengl - password-manager-service chromium:password-manager-service - - personal-fileschromium:chromium-config :personal-files - pulseaudiochromium:pulseaudio - - raw-usb chromium:raw-usb- - removable-media chromium:removable-media :removable-media - screen-inhibit-controlchromium:screen-inhibit-control :screen-inhibit-control - system-files chromium:etc-chromium-browser-policies :system-files- system-packages-doc chromium:system-packages-doc :system-packages-doc - u2f-devices chromium:u2f-devices :u2f-devices - unity7chromium:unity7 :unity7 - upower-observechromium:upower-observe :upower-observe - wayland chromium:wayland:wayland - x11 chromium:x11:x11 - sudo snap connections standard-notes Interface Plug Slot Notes audio-playbackstandard-notes:audio-playback :audio-playback - browser-support standard-notes:browser-support :browser-support - content[gnome-3-28-1804] standard-notes:gnome-3-28-1804 gnome-3-28-1804:gnome-3-28-1804 - content[gtk-3-themes] standard-notes:gtk-3-themes gtk-common-themes:gtk-3-themes - con
[Desktop-packages] [Bug 2047585] [NEW] gnome-remote-desktop-daemon stops responding to mouse input
Public bug reported: Using Ubuntu 23.10 mantic, RDClient on MacOS or even Windows Remote Desktop Client, the RDP session suddenly freezes with the following entries in logs 2023-12-27T14:15:57.255492-05:00 ubuntuvm gnome-remote-desktop-daemon[1685]: [14:14:10:011] [1685:140241] [INFO][ 14:15:57 | #033[0;31mERROR#033[0m | 🪲 Bug: ei_device_pointer_motion_absolute: device is not not emulating 2023-12-27T14:15:57.256197-05:00 ubuntuvm gnome-remote-desktop-daemon[1685]: ... | #033[0;31mERROR#033[0m | 🪲 Bug: ei_device_pointer_motion_absolute: device is not not emulating 2023-12-27T14:15:57.379168-05:00 ubuntuvm gnome-remote-desktop-daemon[1685]: message repeated 119 times: [ ... | #033[0;31mERROR#033[0m | 🪲 Bug: ei_device_pointer_motion_absolute: device is not not emulating] 2023-12-27T14:15:57.379816-05:00 ubuntuvm gnome-shell[1772]: Client error: socket disconnected 2023-12-27T14:15:57.379912-05:00 ubuntuvm gnome-shell[1772]: Failed to add device, disconnecting client 2023-12-27T14:15:57.380164-05:00 ubuntuvm gnome-remote-desktop-daemon[1685]: ... | #033[0;31mERROR#033[0m | 🪲 Bug: ei_device_pointer_motion_absolute: device is not not emulating 2023-12-27T14:15:57.380837-05:00 ubuntuvm gnome-shell[1772]: Window manager warning: Ping serial 912996857 was reused for window W5, previous use was for window W4. 2023-12-27T14:15:57.381471-05:00 ubuntuvm gnome-shell[1772]: message repeated 17 times: [ Window manager warning: Ping serial 912996857 was reused for window W5, previous use was for window W4.] 2023-12-27T14:15:57.381510-05:00 ubuntuvm gnome-remote-desktop-daemon[1685]: ... | #033[0;31mERROR#033[0m | 🪲 Bug: ei_device_pointer_motion_absolute: device is not not emulating 2023-12-27T14:15:57.381586-05:00 ubuntuvm gnome-shell[1772]: Window manager warning: Ping serial 912996857 was reused for window W5, previous use was for window W4. 2023-12-27T14:15:57.382172-05:00 ubuntuvm gnome-shell[1772]: message repeated 19 times: [ Window manager warning: Ping serial 912996857 was reused for window W5, previous use was for window W4.] 2023-12-27T14:15:57.382205-05:00 ubuntuvm gnome-remote-desktop-daemon[1685]: ... | #033[0;31mERROR#033[0m | 🪲 Bug: ei_device_pointer_motion_absolute: device is not not emulating 2023-12-27T14:15:57.947437-05:00 ubuntuvm gnome-remote-desktop-daemon[1685]: message repeated 345 times: [ ... | #033[0;31mERROR#033[0m | 🪲 Bug: ei_device_pointer_motion_absolute: device is not not emulating] 2023-12-27T14:15:58.067012-05:00 ubuntuvm gnome-remote-desktop-daemon[1685]: 14:15:58 | #033[0;31mERROR#033[0m | 🪲 Bug: ei_device_pointer_motion_absolute: device is not not emulating 2023-12-27T14:15:58.096724-05:00 ubuntuvm gnome-remote-desktop-daemon[1685]: ... | #033[0;31mERROR#033[0m | 🪲 Bug: ei_device_pointer_motion_absolute: device is not not emulating 2023-12-27T14:15:58.930342-05:00 ubuntuvm gnome-remote-desktop-daemon[1685]: message repeated 404 times: [ ... | #033[0;31mERROR#033[0m | 🪲 Bug: ei_device_pointer_motion_absolute: device is not not emulating] 2023-12-27T14:15:59.006279-05:00 ubuntuvm gnome-remote-desktop-daemon[1685]: 14:15:59 | #033[0;31mERROR#033[0m | 🪲 Bug: ei_device_pointer_motion_absolute: device is not not emulating 2023-12-27T14:15:59.008501-05:00 ubuntuvm gnome-remote-desktop-daemon[1685]: ... | #033[0;31mERROR#033[0m | 🪲 Bug: ei_device_pointer_motion_absolute: device is not not emulating 2023-12-27T14:15:59.539393-05:00 ubuntuvm gnome-remote-desktop-daemon[1685]: message repeated 208 times: [ ... | #033[0;31mERROR#033[0m | 🪲 Bug: ei_device_pointer_motion_absolute: device is not not emulating] 2023-12-27T14:15:59.543880-05:00 ubuntuvm dbus-daemon[1521]: apparmor="DENIED" operation="dbus_method_call" bus="session" path="/org/gnome/Mutter/IdleMonitor/Core" interface="org.gnome.Mutter.IdleMonitor" member="GetIdletime" mask="send" name=":1.26" pid=3585 label="snap.firefox.firefox" peer_pid=1772 peer_label="unconfined" 2023-12-27T14:15:59.550634-05:00 ubuntuvm gnome-remote-desktop-daemon[1685]: ... | #033[0;31mERROR#033[0m | 🪲 Bug: ei_device_pointer_motion_absolute: device is not not emulating 2023-12-27T14:15:59.988595-05:00 ubuntuvm gnome-remote-desktop-daemon[1685]: message repeated 227 times: [ ... | #033[0;31mERROR#033[0m | 🪲 Bug: ei_device_pointer_motion_absolute: device is not not emulating] 2023-12-27T14:16:00.112724-05:00 ubuntuvm gnome-remote-desktop-daemon[1685]: 14:16:00 | #033[0;31mERROR#033[0m | 🪲 Bug: ei_device_pointer_motion_absolute: device is not not emulating 2023-12-27T14:16:00.116829-05:00 ubuntuvm gnome-remote-desktop-daemon[1685]: ... | #033[0;31mERROR#033[0m | 🪲 Bug: ei_device_pointer_motion_absolute: device is not not emulating 2023-12-27T14:16:00.188927-05:00 ubuntuvm gnome-remote-desktop-daemon[1685]: message repeated 30 times: [ ... | #033[0;31mERROR#033[0m | 🪲 Bug: ei_device_pointer_motion_absolute: devi
[Desktop-packages] [Bug 1973084] Re: transmission-daemon high RAM usage
All good for over 24 hours with Lunar on the proposed package. I tested it with the Ubuntu Server LTS 22.04 torrent and had at least a few encrypted connections. Memory was stable throughout. @ubuntu-2304-test:~$ apt-cache policy transmission-daemon transmission-daemon: Installed: 3.00-2.1ubuntu0.1 Candidate: 3.00-2.1ubuntu0.1 Version table: *** 3.00-2.1ubuntu0.1 100 100 /var/lib/dpkg/status 3.00-2.1build1 500 500 http://us.archive.ubuntu.com/ubuntu lunar/universe amd64 Packages -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to transmission in Ubuntu. https://bugs.launchpad.net/bugs/1973084 Title: transmission-daemon high RAM usage Status in transmission package in Ubuntu: Fix Released Status in transmission source package in Jammy: Fix Committed Status in transmission source package in Lunar: Fix Committed Status in transmission package in Debian: New Bug description: [ Impact ] There is a memory leak in transmission-daemon that was introduced by a faulty openssl3 patch. It has been reported that it's noticeable after a few hours of seeding/downloading torrent files, less than a day. [ Test Plan ] Being a memory leak, there is no immediate/quick test that can be performed, other than letting it run for a few hours and measure memory consumption "before" and "after". comment #5 mentions about 1Gb of RAM after 18h of runtime. #comment 14 mentions 12Gb of RAM, but not for how long it was running. comment #20 says that after 24h using the patched version from a PPA build, the memory consumption was steady at 300Mb. I'd suggest a 24h test and that it should stay under 1Gb of RAM. [ Where problems could occur ] The patch loads the default and legacy openssl3 providers. This will potentially change the set of algorithms available to the application, compared to what was there before. That being said, the legacy provider is a conservative approach, and the likely result is that *more* algorithms will become available, and not less. This is also the approach I have seen in other applications that were rebuilt using openssl3 instead of openssl1.1. It does seem safer than the original patch, which was manually handling ciphers, in particular RC4, and, well, introduced the memory leak. [ Other Info ] Patch came from gentoo. [ Original Description ] Transmission uses a lot of RAM in ubuntu 22.04 server (arm64) runnign on a Raspberry Pi 4. It "eats" RAM and the RAM usage grows each hour until it crashes the system. I sideloaded transmission-daemon and its dependancies from debian 11 (arm64) locked the packages so apt won't update them and, ever since, this issue hasn't happened. Description:Ubuntu 22.04 LTS Release:22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1973084/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1973084] Re: transmission-daemon high RAM usage
I've installed a clean Lunar and am testing out the proposed package. Will report back in ~3 days. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to transmission in Ubuntu. https://bugs.launchpad.net/bugs/1973084 Title: transmission-daemon high RAM usage Status in transmission package in Ubuntu: Fix Released Status in transmission source package in Jammy: Fix Committed Status in transmission source package in Lunar: Fix Committed Status in transmission package in Debian: New Bug description: [ Impact ] There is a memory leak in transmission-daemon that was introduced by a faulty openssl3 patch. It has been reported that it's noticeable after a few hours of seeding/downloading torrent files, less than a day. [ Test Plan ] Being a memory leak, there is no immediate/quick test that can be performed, other than letting it run for a few hours and measure memory consumption "before" and "after". comment #5 mentions about 1Gb of RAM after 18h of runtime. #comment 14 mentions 12Gb of RAM, but not for how long it was running. comment #20 says that after 24h using the patched version from a PPA build, the memory consumption was steady at 300Mb. I'd suggest a 24h test and that it should stay under 1Gb of RAM. [ Where problems could occur ] The patch loads the default and legacy openssl3 providers. This will potentially change the set of algorithms available to the application, compared to what was there before. That being said, the legacy provider is a conservative approach, and the likely result is that *more* algorithms will become available, and not less. This is also the approach I have seen in other applications that were rebuilt using openssl3 instead of openssl1.1. It does seem safer than the original patch, which was manually handling ciphers, in particular RC4, and, well, introduced the memory leak. [ Other Info ] Patch came from gentoo. [ Original Description ] Transmission uses a lot of RAM in ubuntu 22.04 server (arm64) runnign on a Raspberry Pi 4. It "eats" RAM and the RAM usage grows each hour until it crashes the system. I sideloaded transmission-daemon and its dependancies from debian 11 (arm64) locked the packages so apt won't update them and, ever since, this issue hasn't happened. Description:Ubuntu 22.04 LTS Release:22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1973084/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1973084] Re: transmission-daemon high RAM usage
Sure here is the output: root@gw:~# apt-cache policy transmission-daemon transmission-daemon: Installed: 3.00-2ubuntu2.1 Candidate: 3.00-2ubuntu2.1 Version table: *** 3.00-2ubuntu2.1 100 100 /var/lib/dpkg/status 3.00-2ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to transmission in Ubuntu. https://bugs.launchpad.net/bugs/1973084 Title: transmission-daemon high RAM usage Status in transmission package in Ubuntu: Fix Released Status in transmission source package in Jammy: Fix Committed Status in transmission source package in Lunar: Fix Committed Status in transmission package in Debian: New Bug description: [ Impact ] There is a memory leak in transmission-daemon that was introduced by a faulty openssl3 patch. It has been reported that it's noticeable after a few hours of seeding/downloading torrent files, less than a day. [ Test Plan ] Being a memory leak, there is no immediate/quick test that can be performed, other than letting it run for a few hours and measure memory consumption "before" and "after". comment #5 mentions about 1Gb of RAM after 18h of runtime. #comment 14 mentions 12Gb of RAM, but not for how long it was running. comment #20 says that after 24h using the patched version from a PPA build, the memory consumption was steady at 300Mb. I'd suggest a 24h test and that it should stay under 1Gb of RAM. [ Where problems could occur ] The patch loads the default and legacy openssl3 providers. This will potentially change the set of algorithms available to the application, compared to what was there before. That being said, the legacy provider is a conservative approach, and the likely result is that *more* algorithms will become available, and not less. This is also the approach I have seen in other applications that were rebuilt using openssl3 instead of openssl1.1. It does seem safer than the original patch, which was manually handling ciphers, in particular RC4, and, well, introduced the memory leak. [ Other Info ] Patch came from gentoo. [ Original Description ] Transmission uses a lot of RAM in ubuntu 22.04 server (arm64) runnign on a Raspberry Pi 4. It "eats" RAM and the RAM usage grows each hour until it crashes the system. I sideloaded transmission-daemon and its dependancies from debian 11 (arm64) locked the packages so apt won't update them and, ever since, this issue hasn't happened. Description:Ubuntu 22.04 LTS Release:22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1973084/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1973084] Re: transmission-daemon high RAM usage
I was also experiencing the memory leak / crash issue and the proposed package appears to have corrected it along with running stable for over 72 hours now. I've performed a variety of actions such as verifying files and downloading large torrents (>300GB) with many peers. I'm on latest jammy. I think it's okay to push to release. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to transmission in Ubuntu. https://bugs.launchpad.net/bugs/1973084 Title: transmission-daemon high RAM usage Status in transmission package in Ubuntu: Fix Released Status in transmission source package in Jammy: Fix Committed Status in transmission source package in Lunar: Fix Committed Status in transmission package in Debian: New Bug description: [ Impact ] There is a memory leak in transmission-daemon that was introduced by a faulty openssl3 patch. It has been reported that it's noticeable after a few hours of seeding/downloading torrent files, less than a day. [ Test Plan ] Being a memory leak, there is no immediate/quick test that can be performed, other than letting it run for a few hours and measure memory consumption "before" and "after". comment #5 mentions about 1Gb of RAM after 18h of runtime. #comment 14 mentions 12Gb of RAM, but not for how long it was running. comment #20 says that after 24h using the patched version from a PPA build, the memory consumption was steady at 300Mb. I'd suggest a 24h test and that it should stay under 1Gb of RAM. [ Where problems could occur ] The patch loads the default and legacy openssl3 providers. This will potentially change the set of algorithms available to the application, compared to what was there before. That being said, the legacy provider is a conservative approach, and the likely result is that *more* algorithms will become available, and not less. This is also the approach I have seen in other applications that were rebuilt using openssl3 instead of openssl1.1. It does seem safer than the original patch, which was manually handling ciphers, in particular RC4, and, well, introduced the memory leak. [ Other Info ] Patch came from gentoo. [ Original Description ] Transmission uses a lot of RAM in ubuntu 22.04 server (arm64) runnign on a Raspberry Pi 4. It "eats" RAM and the RAM usage grows each hour until it crashes the system. I sideloaded transmission-daemon and its dependancies from debian 11 (arm64) locked the packages so apt won't update them and, ever since, this issue hasn't happened. Description:Ubuntu 22.04 LTS Release:22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1973084/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 912706]
*** Bug 1856184 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 thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/912706 Title: 'Show items that contain' disabled in subscribe dialog Status in Mozilla Thunderbird: Confirmed Status in thunderbird package in Ubuntu: Confirmed Bug description: * Create an imap account * Go to File -> Subscribe Expect to be able filter folder list using 'Show items that contain' text box. Actually the text box is disabled. Present in 9.0 and 10.0 To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/912706/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2028711] [NEW] Feature Request: out-of-date browser notification
Public bug reported: On the top right side of the Chromium tab bar, could you display the following red text watermark, if the browser is out-of-date: “This version is NOT secure. Update to stay secure.” ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2028711 Title: Feature Request: out-of-date browser notification Status in chromium-browser package in Ubuntu: New Bug description: On the top right side of the Chromium tab bar, could you display the following red text watermark, if the browser is out-of-date: “This version is NOT secure. Update to stay secure.” To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2028711/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2028710] [NEW] Feature Request: Browser not up-to-date notification
Public bug reported: On the top right side of the Firefox tab bar, could you display the following red text watermark, if the browser is out-of-date: “This version is NOT secure. Update to stay secure.” ** Affects: firefox (Ubuntu) Importance: Undecided Status: New -- 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/2028710 Title: Feature Request: Browser not up-to-date notification Status in firefox package in Ubuntu: New Bug description: On the top right side of the Firefox tab bar, could you display the following red text watermark, if the browser is out-of-date: “This version is NOT secure. Update to stay secure.” To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2028710/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1066529] Re: All jobs stopped, epson_inkjet_printer_filter failed
sudo chmod -Rc 755 /opt/epson-inkjet-printer-escpr2 worked for me. There is a temptation when writing under /opt to go 777 when untaring to make the drag and drop. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1066529 Title: All jobs stopped, epson_inkjet_printer_filter failed Status in cups package in Ubuntu: Confirmed Bug description: Kubuntu 12.04.1 64bit Cups 1.5.3-0ubuntu4 EPSON WF-7520 - epson-inkjet-printer 1.0.0-1lsb3.2 - the last driver from Epson. Connected via USB. The printer just stopped to print - every job added in "stopped" state and this error: "/opt/epson-inkjet-printer-201115w/cups/lib/filter/epson_inkjet_printer_filter failed" The printer screen says "Printing" endless. Will happy to provide additional info to resolve this issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1066529/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2022322] [NEW] Gnome right butons bug
Public bug reported: In the superior right corner, there are a region (about 5x5 cm2) that mouse do nothing, mainly in minimize and close butons, but ocouring to in menus, just in this corner. Double click in title bar force the restore and then, moving the software window to far of this corner, works properly. Thanks. Mr. Wagner Yaegashi ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jun 2 06:13:24 2023 DistUpgraded: 2023-05-12 23:47:44,660 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: lunar DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd UHD Graphics 620 [144d:c804] InstallationDate: Installed on 2022-05-01 (396 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: SAMSUNG ELECTRONICS CO., LTD. 340XAA/350XAA/550XAA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=21a2de05-0384-44e8-9367-ab55a551cc2d ro quiet splash vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to lunar on 2023-05-13 (20 days ago) dmi.bios.date: 07/14/2021 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P04REP.035.210714.ZW dmi.board.asset.tag: No Asset Tag dmi.board.name: NP350XAA-KD1BR dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SGL9477A0K-C01-G001-S0001+10.0.17134 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP04REP.035.210714.ZW:bd07/14/2021:br5.12:svnSAMSUNGELECTRONICSCO.,LTD.:pn340XAA/350XAA/550XAA:pvrP04REP:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP350XAA-KD1BR:rvrSGL9477A0K-C01-G001-S0001+10.0.17134:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:skuSCAI-A5A5-A5A5-A5A5-PREP: dmi.product.family: Notebook 3 Series dmi.product.name: 340XAA/350XAA/550XAA dmi.product.sku: SCAI-A5A5-A5A5-A5A5-PREP dmi.product.version: P04REP dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 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 corruption lunar ubuntu wayland-session -- 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/2022322 Title: Gnome right butons bug Status in xorg package in Ubuntu: New Bug description: In the superior right corner, there are a region (about 5x5 cm2) that mouse do nothing, mainly in minimize and close butons, but ocouring to in menus, just in this corner. Double click in title bar force the restore and then, moving the software window to far of this corner, works properly. Thanks. Mr. Wagner Yaegashi ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jun 2 06:13:24 2023 DistUpgraded: 2023-05-12 23:47:44,660 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: lunar DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd UHD Graphics 620 [144d:c804] InstallationDate: Installed on 2022-05-01 (396 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: SAMSUNG ELECTRONICS CO., LTD. 340XAA/350XAA/550XAA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=21a2de05-0384-44e8-9367-ab55a551cc2d ro quiet splash vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. S
[Desktop-packages] [Bug 1844453]
*** Bug 154605 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/1844453
Title:
[upstream] Access to the Google remote account does not work
Status in LibreOffice:
In Progress
Status in libreoffice package in Ubuntu:
Confirmed
Bug description:
I have a Google account with 2FA login, from LibreOffice I try to add the
remote account, but it doesn't work, it asks me for a 6-digit PIN.
Investigating to see if it was just my problem, I discovered that this is a
long-standing LibreOffice bug (1) and seems unresolved.
The last report confirms this: "2019-07-04 04:44:41 UTC
This feature doesn't work with my Google account _w/o_
2FA.
Bug hasn't be resolved for about 3 years and "very soon"
we may celebrate 5 years anniversary. %-("
1) https://bugs.documentfoundation.org/show_bug.cgi?id=101630
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: libreoffice (not installed)
ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
Uname: Linux 5.3.0-10-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Sep 17 23:00:10 2019
InstallationDate: Installed on 2019-02-18 (210 days ago)
InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190130)
ProcEnviron:
TERM=screen-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=it_IT.UTF-8
SHELL=/bin/bash
SourcePackage: libreoffice
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1844453/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1961508] Re: Dock displaying over window after resuming from blank screen
Hi, affected. Notebook. Ubuntu 22.04.2 LTS, Wayland. Gnome Version 42.5 Affected apps: Firefox, gnome-terminal. Hardware: HP EliteBook 850 G8 Notebook PC 11th Gen Intel® Core™ i7-1185G7 @ 3.00GHz × 8 Mesa Intel® Xe Graphics (TGL GT2) It happened once with this flow but I couldn't reproduce it immediately after: 1. Locking the screen by closing my notebook. 2. Opening my notebook and unlocking the login screen 3. Switching from a window like Firefox with Alt+Tab to the terminal 4. At that point, the dock overlapped the terminal and when alt-tabbing again, it also overlapped Firefox. -- 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/1961508 Title: Dock displaying over window after resuming from blank screen Status in Dash to dock: Unknown Status in Mutter: New Status in gnome-shell package in Ubuntu: Confirmed Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in gnome-desktop package in Fedora: Confirmed Bug description: I have Blank Screen set to happen after 2 minutes of inactivity. When resuming from a Blank Screen (by moving the mouse or touching the keyboard), the Dock is displayed over the top of the current program. To get it back to normal I need to click "Restore Down" on the current programs window and then "Maximize" so that the Dock no longer overlaps it. (Note: I have Auto-hide dock turned off.) This only happens sometimes. I can't reproduce the bug it every time. - 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu - Ubuntu 21.10 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center - Not sure (I guess the Dock is part of the Gnome interface?) 3) What you expected to happen - Dock should not overlap the current program on resume from screen blank. 4) What happened instead - The Dock overlaps the current program on resume from screen blank. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2022-02-18 (24 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Package: gnome-shell-extension-ubuntu-dock PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19 RelatedPackageVersions: mutter-common 40.5-1ubuntu3~21.10.1 Tags: wayland-session impish Uname: Linux 5.13.0-35-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.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2022-02-18 (328 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Package: mutter PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.19.0-28.29-generic 5.19.17 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 43.0-1ubuntu4 Tags: wayland-session third-party-packages kinetic Uname: Linux 5.19.0-28-generic x86_64 UpgradeStatus: Upgraded to kinetic on 2022-10-25 (79 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1961508/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1995238] Re: repeatedly crashes on attempting to load "bumble.com" or "web.whatsapp.com"
My only recourse seems to be rebooting. Once Firefox crashes, there seems to be no mechanism to restart it (the Chromium snap fails too) from the snap binary. For whatever reason, Firefox running from my Startup Applications succeeds. Once the tabs start crashing, no more web activity will be possible until I reboot. lsof -p [Firefox PID] | grep -E '(COMMAND|libdl)' returns: COMMAND PID USERFD TYPE DEVICE SIZE/OFF NODE NAME firefox 3239 donald mem REG 7,7 6024 /usr/lib/x86_64-linux-gnu/libdl-2.31.so (stat: No such file or directory) sudo grep libdl /proc/3239/maps | less 7f1ecaf5f000-7f1ecaf6 r--p 07:07 6024 /usr/lib/x86_64-linux-gnu/libdl-2.31.so 7f1ecaf6-7f1ecaf62000 r-xp 1000 07:07 6024 /usr/lib/x86_64-linux-gnu/libdl-2.31.so 7f1ecaf62000-7f1ecaf63000 r--p 3000 07:07 6024 /usr/lib/x86_64-linux-gnu/libdl-2.31.so 7f1ecaf63000-7f1ecaf64000 r--p 3000 07:07 6024 /usr/lib/x86_64-linux-gnu/libdl-2.31.so 7f1ecaf64000-7f1ecaf65000 rw-p 4000 07:07 6024 /usr/lib/x86_64-linux-gnu/libdl-2.31.so -- 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/1995238 Title: repeatedly crashes on attempting to load "bumble.com" or "web.whatsapp.com" Status in firefox package in Ubuntu: Confirmed Bug description: When I load the web interfaces to these two services, firefox will immediately crash. Attempting to run from the command-line produces an error message as follows: Oct 31 18:15:47 darwin gnome-panel.desktop[6771]: /snap/firefox/2015/usr/lib/firefox/firefox: error while loading shared libraries: /lib/x86_64-linux-gnu/libdl.so.2: unsupported version 0 of Verneed record Oct 31 18:15:47 darwin gnome-panel.desktop[6771]: message repeated 2 times: [ /snap/firefox/2015/usr/lib/firefox/firefox: /lib/x86_64-linux-gnu/libdl.so.2: unsupported version 0 of Verdef record] The only way to restart firefox is to restart the computer! Logging out and in again, then running firefox, produces the same errors. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox 1:1snap1-0ubuntu2 Uname: Linux 6.0.6-060006-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME-Flashback:GNOME Date: Mon Oct 31 19:41:21 2022 InstallationDate: Installed on 2019-05-26 (1253 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: firefox UpgradeStatus: Upgraded to jammy on 2022-04-29 (184 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1995238/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1970663]
(In reply to Alexandre LISSY :gerard-majax from comment #24) > (In reply to Victor from comment #23) > > I can conform that running the following code, fixed the issue with the > > icon sizes. > > > sudo snap connect firefox:icon-themes gtk-common-themes:icon-themes > > > > But now I have a different issue where the icon is offset by 10 pixels, > > here is a [gif animation](https://imgur.com/a/JKIZRko) that shows the > > problerm. > > Is this with xwayland (firefox snap stable) ? Does it goes away with forcing > `MOZ_ENABLE_WAYLAND=1` ? Either way, please file a new issue for that This is happening with Ubuntu 22.04.1 under Wayland , firefox snap stable, with MOZ_ENABLED_WAYLAND=1, but seems like I have found a way around it, my display is 4k and using resolution 3840x2400 with scale of 300% would trigger this issue, I have change resolution to 2560x1600 with scale 200% and the cursor position is now correct. -- 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/1970663 Title: Tiny mouse cursor in firefox snap Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Confirmed Bug description: Since a few day I've updated to Ubuntu Mate 22.04 with the firefox snap. Since then I've been having this strange bug. I have a 4k screen which I'm running at a 2180p resolution with scaling on HiDPI. This runs just fine except for in firefox. In the new firefox snap I get a really tiny mouse cursor. I also checked other snap, it is not the case there. Regards, Chris --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: MATE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-02-02 (83 days ago) InstallationMedia: Ubuntu-MATE 21.10 "Impish Indri" - Release amd64 (20211012) NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: ubuntu-mate-artwork ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Snap: firefox 99.0.1-1 (stable) Snap.Changes: no changes found Tags: jammy Uname: Linux 5.15.0-27-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-19 (7 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: MATE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-02-02 (83 days ago) InstallationMedia: Ubuntu-MATE 21.10 "Impish Indri" - Release amd64 (20211012) NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: ubuntu-mate-artwork ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Snap: firefox 99.0.1-1 (stable) Snap.Changes: no changes found Tags: jammy Uname: Linux 5.15.0-27-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-19 (7 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1970663/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1970663]
I can conform that running the following code, fixed the issue with the icon sizes. > sudo snap connect firefox:icon-themes gtk-common-themes:icon-themes But now I have a different issue where the icon is offset by 10 pixels, here is a [gif animation](https://imgur.com/a/JKIZRko) that shows the problerm. -- 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/1970663 Title: Tiny mouse cursor in firefox snap Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Confirmed Bug description: Since a few day I've updated to Ubuntu Mate 22.04 with the firefox snap. Since then I've been having this strange bug. I have a 4k screen which I'm running at a 2180p resolution with scaling on HiDPI. This runs just fine except for in firefox. In the new firefox snap I get a really tiny mouse cursor. I also checked other snap, it is not the case there. Regards, Chris --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: MATE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-02-02 (83 days ago) InstallationMedia: Ubuntu-MATE 21.10 "Impish Indri" - Release amd64 (20211012) NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: ubuntu-mate-artwork ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Snap: firefox 99.0.1-1 (stable) Snap.Changes: no changes found Tags: jammy Uname: Linux 5.15.0-27-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-19 (7 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: MATE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-02-02 (83 days ago) InstallationMedia: Ubuntu-MATE 21.10 "Impish Indri" - Release amd64 (20211012) NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: ubuntu-mate-artwork ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Snap: firefox 99.0.1-1 (stable) Snap.Changes: no changes found Tags: jammy Uname: Linux 5.15.0-27-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-19 (7 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1970663/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1970663]
I have the same issue. Running Ubuntu 22.04.1 under Wayland and Firefox 105.0.1. Cursor is very tiny, logs shows the following: (firefox:11410): Gdk-WARNING **: 09:31:43.276: ../src/gdk/wayland/gdkcursor-wayland.c:242 cursor image size (9x16) not an integermultiple of scale (2) Gdk-Message: 09:31:43.408: Unable to load hand2 from the cursor theme Gdk-Message: 09:31:43.531: Unable to load hand2 from the cursor theme Gdk-Message: 09:31:43.826: Unable to load hand2 from the cursor theme Gdk-Message: 09:31:43.875: Unable to load hand2 from the cursor theme -- 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/1970663 Title: Tiny mouse cursor in firefox snap Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Confirmed Bug description: Since a few day I've updated to Ubuntu Mate 22.04 with the firefox snap. Since then I've been having this strange bug. I have a 4k screen which I'm running at a 2180p resolution with scaling on HiDPI. This runs just fine except for in firefox. In the new firefox snap I get a really tiny mouse cursor. I also checked other snap, it is not the case there. Regards, Chris --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: MATE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-02-02 (83 days ago) InstallationMedia: Ubuntu-MATE 21.10 "Impish Indri" - Release amd64 (20211012) NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: ubuntu-mate-artwork ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Snap: firefox 99.0.1-1 (stable) Snap.Changes: no changes found Tags: jammy Uname: Linux 5.15.0-27-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-19 (7 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: MATE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-02-02 (83 days ago) InstallationMedia: Ubuntu-MATE 21.10 "Impish Indri" - Release amd64 (20211012) NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: ubuntu-mate-artwork ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Snap: firefox 99.0.1-1 (stable) Snap.Changes: no changes found Tags: jammy Uname: Linux 5.15.0-27-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-19 (7 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1970663/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1989976] [NEW] wishlist: Passkeys should be supported
Public bug reported: Starting from 2022 the main big tech companies introduce Passkeys. Or in the more official name Fido Multi-device credentials. Basically this is a webauthn login, but the private key is distributed among all the devices in a persons Google, Microsoft and iCloud account. If a person wants to login in on a device not in the account a QR code should be scanned after which the computers do some cryptographic magic via Bluetooth. And the new device also has the private key. This method is supposed to be a lot safer and more convenient than the usual passwords. As far as I know this system is open. My wish is that Ubuntu and Linux in general also will support this Passkeys thing. Regards, Martijn. See : https://fidoalliance.org/multi-device-fido-credentials/ https://developers.google.com/identity/fido https://developer.apple.com/passkeys/ ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: fido passkeys webauthn wishlist -- 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/1989976 Title: wishlist: Passkeys should be supported Status in firefox package in Ubuntu: New Bug description: Starting from 2022 the main big tech companies introduce Passkeys. Or in the more official name Fido Multi-device credentials. Basically this is a webauthn login, but the private key is distributed among all the devices in a persons Google, Microsoft and iCloud account. If a person wants to login in on a device not in the account a QR code should be scanned after which the computers do some cryptographic magic via Bluetooth. And the new device also has the private key. This method is supposed to be a lot safer and more convenient than the usual passwords. As far as I know this system is open. My wish is that Ubuntu and Linux in general also will support this Passkeys thing. Regards, Martijn. See : https://fidoalliance.org/multi-device-fido-credentials/ https://developers.google.com/identity/fido https://developer.apple.com/passkeys/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1989976/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1987040] [NEW] Max resolution for FullHD monitor is 1024x768
Public bug reported: I have 1 external monitor, and the max resolution for this FullHD monitor which I can configure is 1024x768 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Aug 19 08:40:15 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21f3] InstallationDate: Installed on 2022-06-04 (75 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: LENOVO 2349AV6 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=b8deb0ab-b1f3-469e-85fe-3cf4a56dc624 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/21/2016 dmi.bios.release: 2.70 dmi.bios.vendor: LENOVO dmi.bios.version: G1ETB0WW (2.70 ) dmi.board.asset.tag: Not Available dmi.board.name: 2349AV6 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: BB70374050 dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.13 dmi.modalias: dmi:bvnLENOVO:bvrG1ETB0WW(2.70):bd01/21/2016:br2.70:efr1.13:svnLENOVO:pn2349AV6:pvrThinkPadT430:rvnLENOVO:rn2349AV6:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:skuLENOVO_MT_2349: dmi.product.family: ThinkPad T430 dmi.product.name: 2349AV6 dmi.product.sku: LENOVO_MT_2349 dmi.product.version: ThinkPad T430 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 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 wayland-session -- 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/1987040 Title: Max resolution for FullHD monitor is 1024x768 Status in xorg package in Ubuntu: New Bug description: I have 1 external monitor, and the max resolution for this FullHD monitor which I can configure is 1024x768 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Aug 19 08:40:15 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21f3] InstallationDate: Installed on 2022-06-04 (75 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: LENOVO 2349AV6 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=b8deb0ab-b1f3-469e-85fe-3cf4a56dc624 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/21/2016 dmi.bios.release: 2.70 dmi.bios.vendor: LENOVO dmi.bios.version: G1ETB0WW (2.70 ) dmi.board.asset.tag: Not Available dmi.board.name: 2349AV6 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: BB70374050 dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.13 dmi.modalias: dmi:bvnLENOVO:bvrG1ETB0WW(2.70):bd01/21/2016:br2.70:efr1.13:svnLENOVO:pn2349AV6:pvrThinkPadT430:rvnLENOVO:rn2349AV6:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:skuLENOVO_MT_2349: dmi.product.family: ThinkPad T430 dmi.product.name: 2349AV6 dmi.product.sku: LENOVO_MT_2349 dmi.product.version: ThinkPad T430 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri
[Desktop-packages] [Bug 1958267] Re: wpa can't connect to servers using TLS 1.1 or older
Added -proposed, updated, and eduroam is happy again. Nice to have something to tell the Ubuntu-wielding students/faculty/staff until we get 'round to upgrading our Radius servers. Thank you for the fix! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1958267 Title: wpa can't connect to servers using TLS 1.1 or older Status in wpa package in Ubuntu: Fix Released Status in wpa source package in Jammy: Fix Committed Status in wpa package in Debian: New Bug description: * Impact wpa built with in openssl3 fails to connect to TLS 1.1 or lower server * Test case try to connect to a TLS <= 1.1 access point * Regression potential the patch lowers the security level in some situation for compatibility, it shouldn't prevent connecting to newer hardware, still try to connect to different type of wifi with different security levels --- those uses MD5-SHA1 as digest in its signature algorithm which no longer meets OpenSSL default level of security of 80 bits http://lists.infradead.org/pipermail/hostap/2022-May/040563.html Workaround are described in #22 and #36 by basically using CipherString = DEFAULT@SECLEVEL=0 which lowers the security level --- With the current jammy version of wpasupplicant (2:2.10-1), I cannot connect to the WPA Enterprise network eduroam, which is used by Universities worldwide. I get a "Connection failed" message or a request to re-enter the password. - I've re-tried the credentials: no fix ;-) - Tried a 21.10 live session on the same machine: works fine! - Manually downgraded wpasupplicant to the impish version (2:2.9.0-21build1): connected normally. - Upgraded wpasupplicant to the latest version: fails to connect again. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: wpasupplicant 2:2.10-1 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Jan 18 09:56:23 2022 InstallationDate: Installed on 2021-11-30 (48 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: wpa UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1677050] GOOD DAY!
Hope this email finds you well! Been thinking of you lately. Please let me know when you get this, I'd like to ask you something. Stay safe and healthy, Jim -- 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/1677050 Title: Youtube video will not run Status in xorg package in Ubuntu: Invalid Bug description: When I first set up ubuntu I was able to look at youtube videos, but then they just stopped running. I have no real idea why. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-82.90-generic 3.19.8-ckt22 Uname: Linux 3.19.0-82-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Tue Mar 28 16:44:30 2017 DistUpgraded: 2017-02-13 13:49:16,446 DEBUG enabling apt cron job DistroCodename: vivid DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 82945G/GZ Integrated Graphics Controller [8086:2772] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:2a5e] InstallationDate: Installed on 2015-12-03 (481 days ago) InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: HP-Pavilion GC670AA-ABA a6120n ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-82-generic root=UUID=38cc240f-f1a8-40ed-98a0-6c59680dea14 ro quiet splash vt.handoff=7 SourcePackage: xorg UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: Upgraded to vivid on 2017-02-13 (43 days ago) dmi.bios.date: 06/07/2007 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 5.20 dmi.board.name: Leonite2 dmi.board.vendor: ASUSTek Computer INC. dmi.board.version: 6.00 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr5.20:bd06/07/2007:svnHP-Pavilion:pnGC670AA-ABAa6120n:pvr:rvnASUSTekComputerINC.:rnLeonite2:rvr6.00:cvnHewlett-Packard:ct3:cvr: dmi.product.name: GC670AA-ABA a6120n dmi.sys.vendor: HP-Pavilion version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.9-2ubuntu1~vivid2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.9-2ubuntu1~vivid2 version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2.3 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Tue Mar 28 15:50:33 2017 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputAT Translated Set 2 keyboard KEYBOARD, id 8 inputGenPS/2 Genius Mouse MOUSE, id 9 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 27137 vendor VSC xserver.version: 2:1.17.1-0ubuntu3.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1677050/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1970148] Re: Brave & Chrome browsers freezes on download and print to pdf
I have the same issue on Windows 11, Chrome/Edge freezing for about 3-4 seconds when you save any file to disk. This started a few days ago. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1970148 Title: Brave & Chrome browsers freezes on download and print to pdf Status in chromium-browser package in Ubuntu: Invalid Bug description: Whenever any file is downloaded, the browser will freeze. Similarly, the browser will freeze when a page is printed to pdf. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1970148/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1959508] Re: enable BMFF support in exiv2
Many thanks! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to exiv2 in Ubuntu. https://bugs.launchpad.net/bugs/1959508 Title: enable BMFF support in exiv2 Status in exiv2 package in Ubuntu: Fix Released Status in exiv2 package in Debian: Fix Released Bug description: On https://answers.launchpad.net/ubuntu/jammy/+source/exiv2 I see that Ubuntu 22.04 currently includes exiv2 0.27.3 Exiv2 v0.27.5 includes support for Canon *.CR3 image files. The CR3 file format has been the Canon camera-raw file format since mid 2018, and is probably one of the most common raw image file formats today. Applications such as darktable, amongst others, use exiv2 to extract image metadata, thumbnails and previews, and can only open CR3 files when linked with exiv2 0.27.5 or later. Note that exiv2 0.27.5 needs to be built with -DEXIV2_ENABLE_BMFF=On to enable *.CR3 support. Would it be possible to get Exiv2 v0.27.5 with BMFF support enabled included in Ubuntu 22.04? Note that a similar request exists for Debian in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000788 References https://github.com/exiv2/exiv2#2-19 https://github.com/Exiv2/exiv2/issues/1229 https://github.com/darktable-org/darktable/pull/10332 https://github.com/Beep6581/RawTherapee/issues/6248#issuecomment-869208918 https://answers.launchpad.net/ubuntu/+source/exiv2/+question/700398 Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/exiv2/+bug/1959508/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 662840]
*** Bug 1759018 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 firefox in Ubuntu. https://bugs.launchpad.net/bugs/662840 Title: Spell checking more than one language in Firefox Status in Mozilla Firefox: In Progress Status in firefox package in Ubuntu: Triaged Bug description: Binary package hint: firefox After upgrading to Ubuntu 10.10 x64 with Firefox 3.6.10 I lost Firefox capability to spell check for multiple languages in text forms. This is very annoying as I use two or three different languages in a single form when composing emails for example, and also switch between tabs/firefox windows to fill out forms in different languages, and now I have to switch between dictionaries back and forth. Never was an issue before. There is a need to set up multiple dictionaries/languages to be used at once for seamless spell check on a text form. Am I missing something? ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: firefox 3.6.10+build1+nobinonly-0ubuntu3 ProcVersionSignature: Ubuntu 2.6.35-22.34-generic 2.6.35.4 Uname: Linux 2.6.35-22-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Mon Oct 18 21:59:46 2010 FirefoxPackages: firefox 3.6.10+build1+nobinonly-0ubuntu3 firefox-gnome-support 3.6.10+build1+nobinonly-0ubuntu3 firefox-branding 3.6.10+build1+nobinonly-0ubuntu3 abroswer N/A abrowser-branding N/A InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) ProcEnviron: LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: firefox To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/662840/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1844453]
Can confirm that 2FA does not work. Even the GNOME Settings application
has this feature.
---
Version: 7.2.5.2.0+
Build ID: 20(Build:2)
CPU threads: 24; OS: Linux 5.16; UI render: default; VCL: gtk3
Locale: en-US (en_US.UTF-8); UI: en-US
Calc: threaded
--
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/1844453
Title:
[upstream] Access to the Google remote account does not work
Status in LibreOffice:
In Progress
Status in libreoffice package in Ubuntu:
Confirmed
Bug description:
I have a Google account with 2FA login, from LibreOffice I try to add the
remote account, but it doesn't work, it asks me for a 6-digit PIN.
Investigating to see if it was just my problem, I discovered that this is a
long-standing LibreOffice bug (1) and seems unresolved.
The last report confirms this: "2019-07-04 04:44:41 UTC
This feature doesn't work with my Google account _w/o_
2FA.
Bug hasn't be resolved for about 3 years and "very soon"
we may celebrate 5 years anniversary. %-("
1) https://bugs.documentfoundation.org/show_bug.cgi?id=101630
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: libreoffice (not installed)
ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
Uname: Linux 5.3.0-10-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Sep 17 23:00:10 2019
InstallationDate: Installed on 2019-02-18 (210 days ago)
InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190130)
ProcEnviron:
TERM=screen-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=it_IT.UTF-8
SHELL=/bin/bash
SourcePackage: libreoffice
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1844453/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 662840]
There is some work happening here currently. See bug 1402822 -- 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/662840 Title: Spell checking more than one language in Firefox Status in Mozilla Firefox: Invalid Status in firefox package in Ubuntu: Triaged Bug description: Binary package hint: firefox After upgrading to Ubuntu 10.10 x64 with Firefox 3.6.10 I lost Firefox capability to spell check for multiple languages in text forms. This is very annoying as I use two or three different languages in a single form when composing emails for example, and also switch between tabs/firefox windows to fill out forms in different languages, and now I have to switch between dictionaries back and forth. Never was an issue before. There is a need to set up multiple dictionaries/languages to be used at once for seamless spell check on a text form. Am I missing something? ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: firefox 3.6.10+build1+nobinonly-0ubuntu3 ProcVersionSignature: Ubuntu 2.6.35-22.34-generic 2.6.35.4 Uname: Linux 2.6.35-22-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Mon Oct 18 21:59:46 2010 FirefoxPackages: firefox 3.6.10+build1+nobinonly-0ubuntu3 firefox-gnome-support 3.6.10+build1+nobinonly-0ubuntu3 firefox-branding 3.6.10+build1+nobinonly-0ubuntu3 abroswer N/A abrowser-branding N/A InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) ProcEnviron: LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: firefox To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/662840/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1961488] [NEW] radeon module unloaded with 20.04 after upgrade from 18.04
Public bug reported: I upgraded a computer running Ubuntu 18.04 with AMD ATI RS482/RS485 Radeon Xpress 1100/1150 without problem. After upgrade to 20.04, resolution is virtual size of 1400x1050 which doesn't fit in screen. With 18.04 I had in xorg.o.log [ 6647.940] (II) RADEON(0): Creating default Display subsection in Screen section "Default Screen Section" for depth/fbbpp 24/32 [ 6647.940] (==) RADEON(0): Depth 24, (--) framebuffer bpp 32 [ 6647.940] (II) RADEON(0): Pixel depth = 24 bits stored in 4 bytes (32 bpp pixmaps) [ 6647.940] (==) RADEON(0): Default visual is TrueColor [ 6647.940] (==) RADEON(0): RGB weight 888 [ 6647.940] (II) RADEON(0): Using 8 bits per RGB (8 bit DAC) [ 6647.940] (--) RADEON(0): Chipset: "ATI Radeon 3100 Graphics" (ChipID = 0x9611) [ 6647.940] (II) Loading sub module "fb" [ 6647.940] (II) LoadModule: "fb" [ 6647.960] (II) Loading /usr/lib/xorg/modules/libfb.so [ 6647.971] (II) Module fb: vendor="X.Org Foundation" [ 6647.971]compiled for 1.18.4, module version = 1.0.0 [ 6647.971]ABI class: X.Org ANSI C Emulation, version 0.4 [ 6647.971] (II) Loading sub module "dri2" [ 6647.971] (II) LoadModule: "dri2" [ 6647.971] (II) Module "dri2" already built-in [ 6647.971] (II) Loading sub module "exa" [ 6647.971] (II) LoadModule: "exa" [ 6647.972] (II) Loading /usr/lib/xorg/modules/libexa.so [ 6647.976] (II) Module exa: vendor="X.Org Foundation" [ 6647.976]compiled for 1.18.4, module version = 2.6.0 [ 6647.976]ABI class: X.Org Video Driver, version 20.0 [ 6647.976] (II) RADEON(0): KMS Color Tiling: enabled [ 6647.976] (II) RADEON(0): KMS Color Tiling 2D: enabled [ 6647.976] (II) RADEON(0): KMS Pageflipping: enabled [ 6647.976] (II) RADEON(0): SwapBuffers wait for vsync: enabled [ 6648.008] (II) RADEON(0): Output VGA-0 has no monitor section [...] and now [ 789.949] (II) FBDEV(0): using default device [ 789.949] (==) FBDEV(0): Depth 24, (==) framebuffer bpp 32 [ 789.949] (==) FBDEV(0): RGB weight 888 [ 789.949] (==) FBDEV(0): Default visual is TrueColor [ 789.949] (==) FBDEV(0): Using gamma correction (1.0, 1.0, 1.0) [ 789.949] (II) FBDEV(0): hardware: VESA VGA (video memory: 5760kB) [ 789.949] (DB) xf86MergeOutputClassOptions unsupported bus type 0 [ 789.949] (II) FBDEV(0): checking modes against framebuffer device... [ 789.949] (II) FBDEV(0): checking modes against monitor... [ 789.949] (II) FBDEV(0): Virtual size is 1400x1050 (pitch 1400) [ 789.949] (**) FBDEV(0): Built-in mode "current": 147.0 MHz, 83.2 kHz, 77.4 Hz [ 789.949] (II) FBDEV(0): Modeline "current"x0.0 147.04 1400 1432 1600 1768 1050 1054 1058 1074 -hsync -vsync -csync (83.2 kHz b) [ 789.949] (==) FBDEV(0): DPI set to (96, 96) [ 789.949] (II) Loading sub module "fb" [ 789.949] (II) LoadModule: "fb" [ 789.949] (II) Loading /usr/lib/xorg/modules/libfb.so [ 789.950] (II) Module fb: vendor="X.Org Foundation" [ 789.950]compiled for 1.20.13, module version = 1.0.0 [ 789.950]ABI class: X.Org ANSI C Emulation, version 0.4 [ 789.950] (**) FBDEV(0): using shadow framebuffer [ 789.950] (II) Loading sub module "shadow" [ 789.950] (II) LoadModule: "shadow" [ 789.962] (II) Loading /usr/lib/xorg/modules/libshadow.so [ 789.962] (II) Module shadow: vendor="X.Org Foundation" [ 789.962]compiled for 1.20.13, module version = 1.1.0 [ 789.962]ABI class: X.Org ANSI C Emulation, version 0.4 [ 789.962] (II) UnloadModule: "radeon" [ 789.962] (II) Unloading radeon [ 789.963] (II) UnloadModule: "modesetting" [ 789.963] (II) Unloading modesetting [...] ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity:Unity7:ubuntu Date: Sat Feb 19 18:29:21 2022 DistUpgraded: 2021-03-08 13:38:14,332 DEBUG package 'libcpanel-json-xs-perl' produces an unwanted removal 'gnome-software-plugin-snap', skipping DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RS482/RS485 [Radeon Xpress 1100/1150] [1002:5974] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company DC5750 Microtower [103c:280a] Subsystem: Hewlett-Packard Company RS480 [Radeon Xpress 1150] (Secondary) [103c:280b] InstallationDate: Installed on 2015-11-26 (2276 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: Hewlett-Packard HP Compaq dc5750 Small Form Factor ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-30-generic root=UUID=681c938b-c95d-48de-886f-bc784bb57787 ro nomodeset quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStat
[Desktop-packages] [Bug 1959508] Re: enable BMFF support in exiv2
> > I am uploading exiv2 now to Ubuntu as packaged in Debian. > I just looked at https://ftp.debian.org/debian/pool/main/e/exiv2/exiv2_0.27.5-1.debian.tar.xz and I don't think it enables BMFF at build time, so I don't think this will enable CR3 support: $ grep ENABLE debian/rules -DEXIV2_ENABLE_NLS=ON \ -DEXIV2_ENABLE_VIDEO=ON \ -DEXIV2_ENABLE_WEBREADY=ON \ > Could you ask exiv2 why they don't enable the feature by default? > BMFF support was not enabled by default in 0.27-5 out of an abundance of caution at the time that this feature was being worked on and possible legal implications were being investigated. The situation has clarified since then and it will be enabled by default in future Exiv2 versions. See the discussion at https://github.com/Exiv2/exiv2/issues/1679 Thanks On Fri, Feb 11, 2022 at 9:20 AM Jeremy Bicha <1959...@bugs.launchpad.net> wrote: > I am uploading exiv2 now to Ubuntu as packaged in Debian. > > Could you ask exiv2 why they don't enable the feature by default? > > ** Summary changed: > > - Proposal to include exiv2 0.27.5 in Ubuntu 22.04 LTS > + enable BMFF support in exiv2 > > ** Changed in: exiv2 (Ubuntu) >Status: Confirmed => Incomplete > > ** Tags removed: upgrade-software-version > ** Tags added: jammy > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1959508 > > Title: > enable BMFF support in exiv2 > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/exiv2/+bug/1959508/+subscriptions > > ** Bug watch added: github.com/Exiv2/exiv2/issues #1679 https://github.com/Exiv2/exiv2/issues/1679 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to exiv2 in Ubuntu. https://bugs.launchpad.net/bugs/1959508 Title: enable BMFF support in exiv2 Status in exiv2 package in Ubuntu: Incomplete Status in exiv2 package in Debian: New Bug description: On https://answers.launchpad.net/ubuntu/jammy/+source/exiv2 I see that Ubuntu 22.04 currently includes exiv2 0.27.3 Exiv2 v0.27.5 includes support for Canon *.CR3 image files. The CR3 file format has been the Canon camera-raw file format since mid 2018, and is probably one of the most common raw image file formats today. Applications such as darktable, amongst others, use exiv2 to extract image metadata, thumbnails and previews, and can only open CR3 files when linked with exiv2 0.27.5 or later. Note that exiv2 0.27.5 needs to be built with -DEXIV2_ENABLE_BMFF=On to enable *.CR3 support. Would it be possible to get Exiv2 v0.27.5 with BMFF support enabled included in Ubuntu 22.04? Note that a similar request exists for Debian in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000788 References https://github.com/exiv2/exiv2#2-19 https://github.com/Exiv2/exiv2/issues/1229 https://github.com/darktable-org/darktable/pull/10332 https://github.com/Beep6581/RawTherapee/issues/6248#issuecomment-869208918 https://answers.launchpad.net/ubuntu/+source/exiv2/+question/700398 Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/exiv2/+bug/1959508/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1959508] [NEW] Proposal to include exiv2 0.27.5 in Ubuntu 22.04 LTS
Public bug reported: On https://answers.launchpad.net/ubuntu/jammy/+source/exiv2 I see that Ubuntu 22.04 currently includes exiv2 0.27.3 Exiv2 v0.27.5 includes support for Canon *.CR3 image files. The CR3 file format has been the Canon camera-raw file format since mid 2018, and is probably one of the most common raw image file formats today. Applications such as darktable, amongst others, use exiv2 to extract image metadata, thumbnails and previews, and can only open CR3 files when linked with exiv2 0.27.5 or later. Note that exiv2 0.27.5 needs to be built with -DEXIV2_ENABLE_BMFF=On to enable *.CR3 support. Would it be possible to get Exiv2 v0.27.5 with BMFF support enabled included in Ubuntu 22.04? Note that a similar request exists for Debian in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000788 References https://github.com/exiv2/exiv2#2-19 https://github.com/Exiv2/exiv2/issues/1229 https://github.com/darktable-org/darktable/pull/10332 https://github.com/Beep6581/RawTherapee/issues/6248#issuecomment-869208918 https://answers.launchpad.net/ubuntu/+source/exiv2/+question/700398 Thanks ** Affects: exiv2 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to exiv2 in Ubuntu. https://bugs.launchpad.net/bugs/1959508 Title: Proposal to include exiv2 0.27.5 in Ubuntu 22.04 LTS Status in exiv2 package in Ubuntu: New Bug description: On https://answers.launchpad.net/ubuntu/jammy/+source/exiv2 I see that Ubuntu 22.04 currently includes exiv2 0.27.3 Exiv2 v0.27.5 includes support for Canon *.CR3 image files. The CR3 file format has been the Canon camera-raw file format since mid 2018, and is probably one of the most common raw image file formats today. Applications such as darktable, amongst others, use exiv2 to extract image metadata, thumbnails and previews, and can only open CR3 files when linked with exiv2 0.27.5 or later. Note that exiv2 0.27.5 needs to be built with -DEXIV2_ENABLE_BMFF=On to enable *.CR3 support. Would it be possible to get Exiv2 v0.27.5 with BMFF support enabled included in Ubuntu 22.04? Note that a similar request exists for Debian in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000788 References https://github.com/exiv2/exiv2#2-19 https://github.com/Exiv2/exiv2/issues/1229 https://github.com/darktable-org/darktable/pull/10332 https://github.com/Beep6581/RawTherapee/issues/6248#issuecomment-869208918 https://answers.launchpad.net/ubuntu/+source/exiv2/+question/700398 Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/exiv2/+bug/1959508/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1811724] Re: libbd_mdraid.so.2: cannot open shared object file
I encountered something very similar to this issue (maybe even this issue?) when my docker containers could not start (using snap on Ubuntu 20.04.3 LTS under VirtualBox with a Windows 10 host). Similar to others, `sudo apt install libblockdev-mdraid2` seems to have fixed it. In case these log lines are useful context, they came from `sudo grep fail /var/log/syslog` (just trying to filter out some of the noise and I suspect that the devmapper/containerd/cni bits are not directly related): Nov 4 05:22:48 docker kernel: [0.305507] acpi PNP0A03:00: fail to add MMCONFIG information, can't access extended PCI configuration space under this bridge. Nov 4 05:22:48 docker systemd[1]: Starting GRUB failed boot detection... Nov 4 05:22:48 docker systemd[1]: Finished GRUB failed boot detection. Nov 4 05:22:48 docker udisksd[731]: failed to load module mdraid: libbd_mdraid.so.2: cannot open shared object file: No such file or directory Nov 4 05:22:48 docker containerd[733]: time="2021-11-04T05:22:48.627329367Z" level=warning msg="failed to load plugin io.containerd.snapshotter.v1.devmapper" error="devmapper not configured" Nov 4 05:22:48 docker containerd[733]: time="2021-11-04T05:22:48.635107136Z" level=error msg="failed to load cni during init, please check CRI plugin status before setting up network for pods" error="cni config load failed: no network config found in /etc/cni/net.d: cni plugin not initialized: failed to load cni config" Nov 4 05:22:49 docker docker.dockerd[719]: snap-update-ns failed with code 1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to udisks2 in Ubuntu. https://bugs.launchpad.net/bugs/1811724 Title: libbd_mdraid.so.2: cannot open shared object file Status in udisks2 package in Ubuntu: Confirmed Bug description: Had some (probably unrelated?) trouble typing input into login console, and went looking through /var/log/syslog : found Jan 14 21:10:21 vps39184 udisksd[611]: udisks daemon version 2.8.1 starting Jan 14 21:10:22 vps39184 udisksd[611]: failed to load module mdraid: libbd_mdraid.so.2: cannot open shared object file: No such file or directory Jan 14 21:10:22 vps39184 udisksd[611]: Failed to load the 'mdraid' libblockdev plugin Seems to give this warning every time I boot. udisks2: Installed: 2.8.1-3 Candidate: 2.8.1-3 ubuntu: 19.04 disco ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: udisks2 2.8.1-3 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu18 Architecture: amd64 CustomUdevRuleFiles: 80-net-setup-link.rules Date: Mon Jan 14 21:31:52 2019 Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Red Hat KVM ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: root=/dev/vda1 ro vga16fb.modeset=0 quiet splash SourcePackage: udisks2 UpgradeStatus: Upgraded to disco on 2018-11-23 (52 days ago) dmi.bios.date: 01/01/2007 dmi.bios.vendor: Seabios dmi.bios.version: 0.5.1 dmi.chassis.type: 1 dmi.chassis.vendor: Red Hat dmi.modalias: dmi:bvnSeabios:bvr0.5.1:bd01/01/2007:svnRedHat:pnKVM:pvrRHEL6.6.0PC:cvnRedHat:ct1:cvr: dmi.product.family: Red Hat Enterprise Linux dmi.product.name: KVM dmi.product.version: RHEL 6.6.0 PC dmi.sys.vendor: Red Hat To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1811724/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1945367] [NEW] Xorg crash with Nvidia drivers after installation
Public bug reported: i open a second bug report because i have already freeze problem after the installation of nvidia drivers and reboot. Freeze become generally when i am using firefox and visioning a video with youtube. I specify that since the last bug report, i re install ubuntu with official .iso without other package non official. To create the report, i have to connect to the PC from another one with ssh. When i use ubuntu-bug, it is not possible to join nvidia-bug-report because the application dont give me the hand to finish the report. When i try to execute nvidia-bug-report, i have the same thing. To use the PC, i have to use nouveau drivers and intel Xe GPU with poor performances ... Thanks for help. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-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 470.63.01 Tue Aug 3 20:44:16 UTC 2021 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip Date: Tue Sep 28 21:13:05 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 470.63.01, 5.11.0-37-generic, x86_64: installed virtualbox, 6.1.26, 5.11.0-36-generic, x86_64: installed virtualbox, 6.1.26, 5.11.0-37-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Device [8086:2090] NVIDIA Corporation TU106 [GeForce RTX 2060] [10de:1f15] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Device [8086:2090] InstallationDate: Installed on 2021-09-26 (1 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: Intel(R) Client Systems NUC11PHi7 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-37-generic root=UUID=24658b6f-3e37-4376-bc2e-2207e961c9c8 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/07/2021 dmi.bios.release: 5.19 dmi.bios.vendor: Intel Corp. dmi.bios.version: PHTGL579.0063.2021.0707.1057 dmi.board.name: NUC11PHBi7 dmi.board.vendor: Intel Corporation dmi.board.version: M26151-402 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.ec.firmware.release: 12.19 dmi.modalias: dmi:bvnIntelCorp.:bvrPHTGL579.0063.2021.0707.1057:bd07/07/2021:br5.19:efr12.19:svnIntel(R)ClientSystems:pnNUC11PHi7:pvrM26149-403:skuSWNUC11PHKi7C00:rvnIntelCorporation:rnNUC11PHBi7:rvrM26151-402:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: PH dmi.product.name: NUC11PHi7 dmi.product.sku: SWNUC11PHKi7C00 dmi.product.version: M26149-403 dmi.sys.vendor: Intel(R) Client Systems version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.2 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.11-1ubuntu1~20.04.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 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug crash focal 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/1945367 Title: Xorg crash with Nvidia drivers after installation Status in xorg package in Ubuntu: New Bug description: i open a second bug report because i have already freeze problem after the installation of nvidia drivers and reboot. Freeze become generally when i am using firefox and visioning a video with youtube. I specify that since the last bug report, i re install ubuntu with official .iso without other package non official. To create the report, i have to connect to the PC from another one with ssh. When i use ubuntu-bug, it is no
[Desktop-packages] [Bug 1925266] [NEW] Ubuntu should have two web browsers installed by default.
Public bug reported: Users should be encouraged to use one web browser for general web browsing. Another secure web browser with private mode enabled by default, should be used for sensitive(accessing financial accounts and accessing an email address used exclusively for financial accounts) browsing. Addons and plug-ins should be blocked, because they can contain security flaws which would weaken the secure browser. Cookie files should be erased when the tab or browser is closed to prevent bad actor from stealing cookie files. A user might not know the danger of using a single web browser for everything. There are undiscovered security flaws in web browsers. If a user visits a webpage that is infected with JavaScript malware, a user’s web browser will become infected with malware. If the user uses that same browser to access sensitive accounts, sensitive data can be stolen. Webpage content might be modified. ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New ** Description changed: Users should be encouraged to use one web browser for general web browsing. Another secure web browser with private mode enabled by default, should be used for sensitive(accessing financial accounts and accessing an email address used exclusively for financial accounts) browsing. Addons and plug-ins should be blocked, because they can - contain security flaws which would weaken the secure browser. + contain security flaws which would weaken the secure browser. Cookie + files should be erased when the tab or browser is closed to prevent bad + actor from stealing cookie files. A user might not know the danger of using a single web browser for everything. There are undiscovered security flaws in web browsers. If a user visits a webpage that is infected with JavaScript malware, a user’s web browser will become infected with malware. If the user uses that same browser to access sensitive accounts, sensitive data can be stolen. Webpage content might be modified. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1925266 Title: Ubuntu should have two web browsers installed by default. Status in gnome-software package in Ubuntu: New Bug description: Users should be encouraged to use one web browser for general web browsing. Another secure web browser with private mode enabled by default, should be used for sensitive(accessing financial accounts and accessing an email address used exclusively for financial accounts) browsing. Addons and plug-ins should be blocked, because they can contain security flaws which would weaken the secure browser. Cookie files should be erased when the tab or browser is closed to prevent bad actor from stealing cookie files. A user might not know the danger of using a single web browser for everything. There are undiscovered security flaws in web browsers. If a user visits a webpage that is infected with JavaScript malware, a user’s web browser will become infected with malware. If the user uses that same browser to access sensitive accounts, sensitive data can be stolen. Webpage content might be modified. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1925266/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1925264] [NEW] Create a gnome applet that would display Ubuntu security news, data breaches, scams, etc.
Public bug reported: Could you create a gnome applet for Ubuntu that would display security news from: www.threatpost.com www.securelist.com usa.kaspersky.com/blog/ Ubuntu should be focused on security and privacy. The applet could be bundled with Ubuntu. ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1925264 Title: Create a gnome applet that would display Ubuntu security news, data breaches, scams, etc. Status in gnome-software package in Ubuntu: New Bug description: Could you create a gnome applet for Ubuntu that would display security news from: www.threatpost.com www.securelist.com usa.kaspersky.com/blog/ Ubuntu should be focused on security and privacy. The applet could be bundled with Ubuntu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1925264/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1920665] Re: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected"
I understand, thanks Rik. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1920665 Title: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected" Status in mesa package in Ubuntu: Fix Released Status in ubiquity package in Ubuntu: Incomplete Status in mesa source package in Hirsute: Fix Released Status in ubiquity source package in Hirsute: Incomplete Bug description: ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity 21.04.11 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.460 CurrentDesktop: KDE Date: Sun Mar 21 11:53:44 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210321) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) Since approximately 16/03/2021 ubiquity from maybe-ubiquity (try install screen) and from the live session is crashing on launch or shortly after. Cases where the crash can be triggered: - Using a Virtualbox VM, where graphics acceleration is handled by mesa with LLVMPIPE - Start the ISO on real hardware in 'safe graphics mode' Cases where the crash is not encountered: - Start the ISO on real intel (HD graphics) hardware with full acceleration. NOTE: The crash can be avoided by downgrading MESA 21.0.x packages to the previous 20.3.4 in hirsute. Try/Install crash: Screen fails to start, or starts then crashes on any user action. The user is presented with: "Installation failed - The installer encountered an unrecoverable error. A desktop session will now be run so that you may investigate the problem or try installing again" Live session crash: The installer does not start from the desktop icon. Starting ubiquity from the terminal results in an "Aborted (core dumped)" message and nothing else. The crash is most commonly "malloc(): unaligned tcache chunk detected", but inevitably from this sort of memory issue can be something like "realloc(): invalid next size" An example /var/log/installer/debug log from a session where both crashes were triggered is below. /var/log/installer/debug Ubiquity 21.04.11 TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. QSocketNotifier: Invalid socket 17 and type 'Read', disabling... QSocketNotifier: Invalid socket 17 and type 'Write', disabling... QSocketNotifier: Invalid socket 17 and type 'Exception', disabling... Your console font configuration will be updated the next time your system boots. If you want to update it now, run 'setupcon' from a virtual console. update-initramfs is disabled since running on read-only media debconf: DbDriver "passwords" warning: could not open /var/cache/debconf/passwords.dat: Permission denied munmap_chunk(): invalid pointer Ubiquity 21.04.11 QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. malloc(): unaligned tcache chunk detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1920665/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1920665] Re: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected"
I downloaded Kubuntu daily build for 2021-04-09 and put the iso on a thumb drive I am using the 'safe graphics' option needed by my system. The on screen display of the initial file check process, with option to skip, still doesn't show. A splash screen eventually shows and flickers a few times before the screen with 'try live' and 'install now' buttons appears. I can now successfully access with the 'live screen' option, also the 'install now' button works. I successfully installed Kubuntu Hippo via the 'install now' button. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1920665 Title: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected" Status in mesa package in Ubuntu: Fix Released Status in ubiquity package in Ubuntu: Incomplete Status in mesa source package in Hirsute: Fix Released Status in ubiquity source package in Hirsute: Incomplete Bug description: ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity 21.04.11 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.460 CurrentDesktop: KDE Date: Sun Mar 21 11:53:44 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210321) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) Since approximately 16/03/2021 ubiquity from maybe-ubiquity (try install screen) and from the live session is crashing on launch or shortly after. Cases where the crash can be triggered: - Using a Virtualbox VM, where graphics acceleration is handled by mesa with LLVMPIPE - Start the ISO on real hardware in 'safe graphics mode' Cases where the crash is not encountered: - Start the ISO on real intel (HD graphics) hardware with full acceleration. NOTE: The crash can be avoided by downgrading MESA 21.0.x packages to the previous 20.3.4 in hirsute. Try/Install crash: Screen fails to start, or starts then crashes on any user action. The user is presented with: "Installation failed - The installer encountered an unrecoverable error. A desktop session will now be run so that you may investigate the problem or try installing again" Live session crash: The installer does not start from the desktop icon. Starting ubiquity from the terminal results in an "Aborted (core dumped)" message and nothing else. The crash is most commonly "malloc(): unaligned tcache chunk detected", but inevitably from this sort of memory issue can be something like "realloc(): invalid next size" An example /var/log/installer/debug log from a session where both crashes were triggered is below. /var/log/installer/debug Ubiquity 21.04.11 TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. QSocketNotifier: Invalid socket 17 and type 'Read', disabling... QSocketNotifier: Invalid socket 17 and type 'Write', disabling... QSocketNotifier: Invalid socket 17 and type 'Exception', disabling... Your console font configuration will be updated the next time your system boots. If you want to update it now, run 'setupcon' from a virtual console. update-initramfs is disabled since running on read-only media debconf: DbDriver "passwords" warning: could not open /var/cache/debconf/passwords.dat: Permission denied munmap_chunk(): invalid pointer Ubiquity 21.04.11 QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. malloc(): unaligned tcache chunk detected To manage notifications about this bug go to: https:
[Desktop-packages] [Bug 1920665] Re: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected"
Will the mesa fix be available on a daily build? I would like to test it on my hardware. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1920665 Title: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected" Status in mesa package in Ubuntu: Fix Committed Status in ubiquity package in Ubuntu: Incomplete Status in mesa source package in Hirsute: Fix Committed Status in ubiquity source package in Hirsute: Incomplete Bug description: ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity 21.04.11 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.460 CurrentDesktop: KDE Date: Sun Mar 21 11:53:44 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210321) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) Since approximately 16/03/2021 ubiquity from maybe-ubiquity (try install screen) and from the live session is crashing on launch or shortly after. Cases where the crash can be triggered: - Using a Virtualbox VM, where graphics acceleration is handled by mesa with LLVMPIPE - Start the ISO on real hardware in 'safe graphics mode' Cases where the crash is not encountered: - Start the ISO on real intel (HD graphics) hardware with full acceleration. NOTE: The crash can be avoided by downgrading MESA 21.0.x packages to the previous 20.3.4 in hirsute. Try/Install crash: Screen fails to start, or starts then crashes on any user action. The user is presented with: "Installation failed - The installer encountered an unrecoverable error. A desktop session will now be run so that you may investigate the problem or try installing again" Live session crash: The installer does not start from the desktop icon. Starting ubiquity from the terminal results in an "Aborted (core dumped)" message and nothing else. The crash is most commonly "malloc(): unaligned tcache chunk detected", but inevitably from this sort of memory issue can be something like "realloc(): invalid next size" An example /var/log/installer/debug log from a session where both crashes were triggered is below. /var/log/installer/debug Ubiquity 21.04.11 TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. QSocketNotifier: Invalid socket 17 and type 'Read', disabling... QSocketNotifier: Invalid socket 17 and type 'Write', disabling... QSocketNotifier: Invalid socket 17 and type 'Exception', disabling... Your console font configuration will be updated the next time your system boots. If you want to update it now, run 'setupcon' from a virtual console. update-initramfs is disabled since running on read-only media debconf: DbDriver "passwords" warning: could not open /var/cache/debconf/passwords.dat: Permission denied munmap_chunk(): invalid pointer Ubiquity 21.04.11 QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. malloc(): unaligned tcache chunk detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1920665/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1920665] Re: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected"
Having installed Ubuntu Hippo Beta [or a recent daily build version] successfully as in post #32 it is possible to install the Kubuntu desktop over it resulting in a working version of Kubuntu Hippo. I suppose this could be seen as a workaround to install a working Kubuntu 2104. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1920665 Title: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected" Status in mesa package in Ubuntu: Confirmed Status in ubiquity package in Ubuntu: Incomplete Status in mesa source package in Hirsute: Confirmed Status in ubiquity source package in Hirsute: Incomplete Bug description: ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity 21.04.11 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.460 CurrentDesktop: KDE Date: Sun Mar 21 11:53:44 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210321) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) Since approximately 16/03/2021 ubiquity from maybe-ubiquity (try install screen) and from the live session is crashing on launch or shortly after. Cases where the crash can be triggered: - Using a Virtualbox VM, where graphics acceleration is handled by mesa with LLVMPIPE - Start the ISO on real hardware in 'safe graphics mode' Cases where the crash is not encountered: - Start the ISO on real intel (HD graphics) hardware with full acceleration. NOTE: The crash can be avoided by downgrading MESA 21.0.x packages to the previous 20.3.4 in hirsute. Try/Install crash: Screen fails to start, or starts then crashes on any user action. The user is presented with: "Installation failed - The installer encountered an unrecoverable error. A desktop session will now be run so that you may investigate the problem or try installing again" Live session crash: The installer does not start from the desktop icon. Starting ubiquity from the terminal results in an "Aborted (core dumped)" message and nothing else. The crash is most commonly "malloc(): unaligned tcache chunk detected", but inevitably from this sort of memory issue can be something like "realloc(): invalid next size" An example /var/log/installer/debug log from a session where both crashes were triggered is below. /var/log/installer/debug Ubiquity 21.04.11 TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. QSocketNotifier: Invalid socket 17 and type 'Read', disabling... QSocketNotifier: Invalid socket 17 and type 'Write', disabling... QSocketNotifier: Invalid socket 17 and type 'Exception', disabling... Your console font configuration will be updated the next time your system boots. If you want to update it now, run 'setupcon' from a virtual console. update-initramfs is disabled since running on read-only media debconf: DbDriver "passwords" warning: could not open /var/cache/debconf/passwords.dat: Permission denied munmap_chunk(): invalid pointer Ubiquity 21.04.11 QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. malloc(): unaligned tcache chunk detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1920665/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.la
[Desktop-packages] [Bug 1920665] Re: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected"
I've tried, out of interest, an install of Ubuntu (which incidentally also carries the mesa files) from recent daily builds and also of the recently released beta. Ubuntu is not displaying the behaviour that appears with Kubuntu. It is possible to transfer the iso to a usb stick, run it from there in safe graphics mode and do an install to a partition on the PC. As we know at this time this is not possible for Kubuntu. I post this thinking it might be relevant. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1920665 Title: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected" Status in mesa package in Ubuntu: Confirmed Status in ubiquity package in Ubuntu: Confirmed Status in mesa source package in Hirsute: Confirmed Status in ubiquity source package in Hirsute: Confirmed Bug description: ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity 21.04.11 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.460 CurrentDesktop: KDE Date: Sun Mar 21 11:53:44 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210321) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) Since approximately 16/03/2021 ubiquity from maybe-ubiquity (try install screen) and from the live session is crashing on launch or shortly after. Cases where the crash can be triggered: - Using a Virtualbox VM, where graphics acceleration is handled by mesa with LLVMPIPE - Start the ISO on real hardware in 'safe graphics mode' Cases where the crash is not encountered: - Start the ISO on real intel (HD graphics) hardware with full acceleration. NOTE: The crash can be avoided by downgrading MESA 21.0.x packages to the previous 20.3.4 in hirsute. Try/Install crash: Screen fails to start, or starts then crashes on any user action. The user is presented with: "Installation failed - The installer encountered an unrecoverable error. A desktop session will now be run so that you may investigate the problem or try installing again" Live session crash: The installer does not start from the desktop icon. Starting ubiquity from the terminal results in an "Aborted (core dumped)" message and nothing else. The crash is most commonly "malloc(): unaligned tcache chunk detected", but inevitably from this sort of memory issue can be something like "realloc(): invalid next size" An example /var/log/installer/debug log from a session where both crashes were triggered is below. /var/log/installer/debug Ubiquity 21.04.11 TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. QSocketNotifier: Invalid socket 17 and type 'Read', disabling... QSocketNotifier: Invalid socket 17 and type 'Write', disabling... QSocketNotifier: Invalid socket 17 and type 'Exception', disabling... Your console font configuration will be updated the next time your system boots. If you want to update it now, run 'setupcon' from a virtual console. update-initramfs is disabled since running on read-only media debconf: DbDriver "passwords" warning: could not open /var/cache/debconf/passwords.dat: Permission denied munmap_chunk(): invalid pointer Ubiquity 21.04.11 QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. malloc(): unaligned tcache chunk detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1920665/+subscriptions -- M
[Desktop-packages] [Bug 1920665] Re: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected"
** Changed in: mesa (Ubuntu Hirsute) Status: Confirmed => Opinion -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1920665 Title: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected" Status in mesa package in Ubuntu: Opinion Status in ubiquity package in Ubuntu: Confirmed Status in mesa source package in Hirsute: Opinion Status in ubiquity source package in Hirsute: Confirmed Bug description: ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity 21.04.11 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.460 CurrentDesktop: KDE Date: Sun Mar 21 11:53:44 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210321) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) Since approximately 16/03/2021 ubiquity from maybe-ubiquity (try install screen) and from the live session is crashing on launch or shortly after. Cases where the crash can be triggered: - Using a Virtualbox VM, where graphics acceleration is handled by mesa with LLVMPIPE - Start the ISO on real hardware in 'safe graphics mode' Cases where the crash is not encountered: - Start the ISO on real intel (HD graphics) hardware with full acceleration. NOTE: The crash can be avoided by downgrading MESA 21.0.x packages to the previous 20.3.4 in hirsute. Try/Install crash: Screen fails to start, or starts then crashes on any user action. The user is presented with: "Installation failed - The installer encountered an unrecoverable error. A desktop session will now be run so that you may investigate the problem or try installing again" Live session crash: The installer does not start from the desktop icon. Starting ubiquity from the terminal results in an "Aborted (core dumped)" message and nothing else. The crash is most commonly "malloc(): unaligned tcache chunk detected", but inevitably from this sort of memory issue can be something like "realloc(): invalid next size" An example /var/log/installer/debug log from a session where both crashes were triggered is below. /var/log/installer/debug Ubiquity 21.04.11 TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. QSocketNotifier: Invalid socket 17 and type 'Read', disabling... QSocketNotifier: Invalid socket 17 and type 'Write', disabling... QSocketNotifier: Invalid socket 17 and type 'Exception', disabling... Your console font configuration will be updated the next time your system boots. If you want to update it now, run 'setupcon' from a virtual console. update-initramfs is disabled since running on read-only media debconf: DbDriver "passwords" warning: could not open /var/cache/debconf/passwords.dat: Permission denied munmap_chunk(): invalid pointer Ubiquity 21.04.11 QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. malloc(): unaligned tcache chunk detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1920665/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1920665] Re: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected"
Unfortunately what Rik is experiencing on a "live session" in his virtual machine with intel graphics using an unnecessary 'safe graphics' mode is slightly different to my necessary use of 'safe graphics' to unsuccessfully boot from a thumbdrive containing the iso. I'm sorry I am not a bug hunter, I am not aware of the protocols. All I can repeat is that a thumb drive containing either a current daily build or the recent beta does not boot correctly. I would guess in my untutored way that some change to the boot process occurred during March. Up until then I had performed test installs without a hitch. I would be happy to give any assistance/info I can but my programming experience is severely limited. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1920665 Title: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected" Status in mesa package in Ubuntu: Confirmed Status in ubiquity package in Ubuntu: Confirmed Status in mesa source package in Hirsute: Confirmed Status in ubiquity source package in Hirsute: Confirmed Bug description: ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity 21.04.11 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.460 CurrentDesktop: KDE Date: Sun Mar 21 11:53:44 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210321) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) Since approximately 16/03/2021 ubiquity from maybe-ubiquity (try install screen) and from the live session is crashing on launch or shortly after. Cases where the crash can be triggered: - Using a Virtualbox VM, where graphics acceleration is handled by mesa with LLVMPIPE - Start the ISO on real hardware in 'safe graphics mode' Cases where the crash is not encountered: - Start the ISO on real intel (HD graphics) hardware with full acceleration. NOTE: The crash can be avoided by downgrading MESA 21.0.x packages to the previous 20.3.4 in hirsute. Try/Install crash: Screen fails to start, or starts then crashes on any user action. The user is presented with: "Installation failed - The installer encountered an unrecoverable error. A desktop session will now be run so that you may investigate the problem or try installing again" Live session crash: The installer does not start from the desktop icon. Starting ubiquity from the terminal results in an "Aborted (core dumped)" message and nothing else. The crash is most commonly "malloc(): unaligned tcache chunk detected", but inevitably from this sort of memory issue can be something like "realloc(): invalid next size" An example /var/log/installer/debug log from a session where both crashes were triggered is below. /var/log/installer/debug Ubiquity 21.04.11 TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. QSocketNotifier: Invalid socket 17 and type 'Read', disabling... QSocketNotifier: Invalid socket 17 and type 'Write', disabling... QSocketNotifier: Invalid socket 17 and type 'Exception', disabling... Your console font configuration will be updated the next time your system boots. If you want to update it now, run 'setupcon' from a virtual console. update-initramfs is disabled since running on read-only media debconf: DbDriver "passwords" warning: could not open /var/cache/debconf/passwords.dat: Permission denied munmap_chunk(): invalid pointer Ubiquity 21.04.11 QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT E
[Desktop-packages] [Bug 1920665] Re: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected"
"malloc(): unaligned tcache chunk detected" does not appear on my PC. I am trying to install from an iso of hippo on a thumb drive. The boot fails before any 'live session' appears. I am not trying to install from a live session, boot fails before that point. I do not think this is the same as the bug reported here. Rik it appears is attemptig to boot from a live session of some sort. My installation breaks down before reaching this point. The iso in the daily build was not failing until some time in March. It has not been right since. There were a number of updates on a regular basis in March. The change is in the boot process rather than in actual installation as the installation has not been begun at the point the bug occurs. I'm no programmer but I can see that installation has not been offered, let alone begun when things go astray. Please review any conclusions so far. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1920665 Title: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected" Status in mesa package in Ubuntu: Confirmed Status in ubiquity package in Ubuntu: Confirmed Status in mesa source package in Hirsute: Confirmed Status in ubiquity source package in Hirsute: Confirmed Bug description: ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity 21.04.11 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.460 CurrentDesktop: KDE Date: Sun Mar 21 11:53:44 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210321) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) Since approximately 16/03/2021 ubiquity from maybe-ubiquity (try install screen) and from the live session is crashing on launch or shortly after. Cases where the crash can be triggered: - Using a Virtualbox VM, where graphics acceleration is handled by mesa with LLVMPIPE - Start the ISO on real hardware in 'safe graphics mode' Cases where the crash is not encountered: - Start the ISO on real intel (HD graphics) hardware with full acceleration. NOTE: The crash can be avoided by downgrading MESA 21.0.x packages to the previous 20.3.4 in hirsute. Try/Install crash: Screen fails to start, or starts then crashes on any user action. The user is presented with: "Installation failed - The installer encountered an unrecoverable error. A desktop session will now be run so that you may investigate the problem or try installing again" Live session crash: The installer does not start from the desktop icon. Starting ubiquity from the terminal results in an "Aborted (core dumped)" message and nothing else. The crash is most commonly "malloc(): unaligned tcache chunk detected", but inevitably from this sort of memory issue can be something like "realloc(): invalid next size" An example /var/log/installer/debug log from a session where both crashes were triggered is below. /var/log/installer/debug Ubiquity 21.04.11 TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. QSocketNotifier: Invalid socket 17 and type 'Read', disabling... QSocketNotifier: Invalid socket 17 and type 'Write', disabling... QSocketNotifier: Invalid socket 17 and type 'Exception', disabling... Your console font configuration will be updated the next time your system boots. If you want to update it now, run 'setupcon' from a virtual console. update-initramfs is disabled since running on read-only media debconf: DbDriver "passwords" warning: could not open /var/cache/debconf/passwords.dat: Permission denied munmap_chunk(): invalid pointer Ubiquity 21.04.11 QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' TEXT If more than one person will use this computer, you can set up mult
[Desktop-packages] [Bug 1920665] Re: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected"
Is there somewhere or somehow I can test your modified version of Kubuntu by downloading it and attempting an install Rik? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1920665 Title: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected" Status in mesa package in Ubuntu: Confirmed Status in ubiquity package in Ubuntu: Confirmed Status in mesa source package in Hirsute: Confirmed Status in ubiquity source package in Hirsute: Confirmed Bug description: ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity 21.04.11 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.460 CurrentDesktop: KDE Date: Sun Mar 21 11:53:44 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210321) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) Since approximately 16/03/2021 ubiquity from maybe-ubiquity (try install screen) and from the live session is crashing on launch or shortly after. Cases where the crash can be triggered: - Using a Virtualbox VM, where graphics acceleration is handled by mesa with LLVMPIPE - Start the ISO on real hardware in 'safe graphics mode' Cases where the crash is not encountered: - Start the ISO on real intel (HD graphics) hardware with full acceleration. NOTE: The crash can be avoided by downgrading MESA 21.0.x packages to the previous 20.3.4 in hirsute. Try/Install crash: Screen fails to start, or starts then crashes on any user action. The user is presented with: "Installation failed - The installer encountered an unrecoverable error. A desktop session will now be run so that you may investigate the problem or try installing again" Live session crash: The installer does not start from the desktop icon. Starting ubiquity from the terminal results in an "Aborted (core dumped)" message and nothing else. An example /var/log/installer/debug log from a session where both crashes were triggered is below. /var/log/installer/debug Ubiquity 21.04.11 TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. QSocketNotifier: Invalid socket 17 and type 'Read', disabling... QSocketNotifier: Invalid socket 17 and type 'Write', disabling... QSocketNotifier: Invalid socket 17 and type 'Exception', disabling... Your console font configuration will be updated the next time your system boots. If you want to update it now, run 'setupcon' from a virtual console. update-initramfs is disabled since running on read-only media debconf: DbDriver "passwords" warning: could not open /var/cache/debconf/passwords.dat: Permission denied munmap_chunk(): invalid pointer Ubiquity 21.04.11 QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. malloc(): unaligned tcache chunk detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1920665/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1920665] Re: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected"
It is possible on my PC to install Ubuntu2104beta without encountering this behaviour and I can successfully install the Ubuntu flavour. This bug does happen with the Kubuntu beta and I find it is impossible to install the Kubuntu flavour from the beta iso. It is worth noting that mesa is present in both Ubuntu and Kubuntu. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1920665 Title: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected" Status in mesa package in Ubuntu: Confirmed Status in ubiquity package in Ubuntu: Confirmed Status in mesa source package in Hirsute: Confirmed Status in ubiquity source package in Hirsute: Confirmed Bug description: ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity 21.04.11 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.460 CurrentDesktop: KDE Date: Sun Mar 21 11:53:44 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210321) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) Since approximately 16/03/2021 ubiquity from maybe-ubiquity (try install screen) and from the live session is crashing on launch or shortly after. Cases where the crash can be triggered: - Using a Virtualbox VM, where graphics acceleration is handled by mesa with LLVMPIPE - Start the ISO on real hardware in 'safe graphics mode' Cases where the crash is not encountered: - Start the ISO on real intel (HD graphics) hardware with full acceleration. NOTE: The crash can be avoided by downgrading MESA 21.0.x packages to the previous 20.3.4 in hirsute. Try/Install crash: Screen fails to start, or starts then crashes on any user action. The user is presented with: "Installation failed - The installer encountered an unrecoverable error. A desktop session will now be run so that you may investigate the problem or try installing again" Live session crash: The installer does not start from the desktop icon. Starting ubiquity from the terminal results in an "Aborted (core dumped)" message and nothing else. An example /var/log/installer/debug log from a session where both crashes were triggered is below. /var/log/installer/debug Ubiquity 21.04.11 TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. QSocketNotifier: Invalid socket 17 and type 'Read', disabling... QSocketNotifier: Invalid socket 17 and type 'Write', disabling... QSocketNotifier: Invalid socket 17 and type 'Exception', disabling... Your console font configuration will be updated the next time your system boots. If you want to update it now, run 'setupcon' from a virtual console. update-initramfs is disabled since running on read-only media debconf: DbDriver "passwords" warning: could not open /var/cache/debconf/passwords.dat: Permission denied munmap_chunk(): invalid pointer Ubiquity 21.04.11 QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. malloc(): unaligned tcache chunk detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1920665/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1920665] Re: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected"
This is to confirm that kubuntu-21.04-beta-desktop-amd64.iso fails as an installation media on my PC. I have nvidia graphics, amd m/board and am using 'safe graphics' when attempting to boot up the installation media from a thumb drive. The usual "Installation failed" message is displayed. If more info would help please give me any further instructions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1920665 Title: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected" Status in mesa package in Ubuntu: Confirmed Status in ubiquity package in Ubuntu: Confirmed Status in mesa source package in Hirsute: Confirmed Status in ubiquity source package in Hirsute: Confirmed Bug description: ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity 21.04.11 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.460 CurrentDesktop: KDE Date: Sun Mar 21 11:53:44 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210321) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) Since approximately 16/03/2021 ubiquity from maybe-ubiquity (try install screen) and from the live session is crashing on launch or shortly after. Cases where the crash can be triggered: - Using a Virtualbox VM, where graphics acceleration is handled by mesa with LLVMPIPE - Start the ISO on real hardware in 'safe graphics mode' Cases where the crash is not encountered: - Start the ISO on real intel (HD graphics) hardware with full acceleration. NOTE: The crash can be avoided by downgrading MESA 21.0.x packages to the previous 20.3.4 in hirsute. Try/Install crash: Screen fails to start, or starts then crashes on any user action. The user is presented with: "Installation failed - The installer encountered an unrecoverable error. A desktop session will now be run so that you may investigate the problem or try installing again" Live session crash: The installer does not start from the desktop icon. Starting ubiquity from the terminal results in an "Aborted (core dumped)" message and nothing else. An example /var/log/installer/debug log from a session where both crashes were triggered is below. /var/log/installer/debug Ubiquity 21.04.11 TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. QSocketNotifier: Invalid socket 17 and type 'Read', disabling... QSocketNotifier: Invalid socket 17 and type 'Write', disabling... QSocketNotifier: Invalid socket 17 and type 'Exception', disabling... Your console font configuration will be updated the next time your system boots. If you want to update it now, run 'setupcon' from a virtual console. update-initramfs is disabled since running on read-only media debconf: DbDriver "passwords" warning: could not open /var/cache/debconf/passwords.dat: Permission denied munmap_chunk(): invalid pointer Ubiquity 21.04.11 QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. malloc(): unaligned tcache chunk detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1920665/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1920665] Re: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected"
kubuntu hirsute daily build 21-03-28 also fails if safe graphics mode is used on a machine with nVidia graphics -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1920665 Title: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected" Status in mesa package in Ubuntu: Confirmed Status in ubiquity package in Ubuntu: Confirmed Status in mesa source package in Hirsute: Confirmed Status in ubiquity source package in Hirsute: Confirmed Bug description: ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity 21.04.11 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.460 CurrentDesktop: KDE Date: Sun Mar 21 11:53:44 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210321) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) Since approximately 16/03/2021 ubiquity from maybe-ubiquity (try install screen) and from the live session is crashing on launch or shortly after. Try/Install crash: Screen fails to start, or starts then crashes on any user action. The user is presented with: "Installation failed - The installer encountered an unrecoverable error. A desktop session will now be run so that you may investigate the problem or try installing again" Live session crash: The installer does not start from the desktop icon. Starting ubiquity from the terminal results in an "Aborted (core dumped)" message and nothing else. An example /var/log/installer/debug log from a session where both crashes were triggered is below. /var/log/installer/debug Ubiquity 21.04.11 TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. QSocketNotifier: Invalid socket 17 and type 'Read', disabling... QSocketNotifier: Invalid socket 17 and type 'Write', disabling... QSocketNotifier: Invalid socket 17 and type 'Exception', disabling... Your console font configuration will be updated the next time your system boots. If you want to update it now, run 'setupcon' from a virtual console. update-initramfs is disabled since running on read-only media debconf: DbDriver "passwords" warning: could not open /var/cache/debconf/passwords.dat: Permission denied munmap_chunk(): invalid pointer Ubiquity 21.04.11 QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. malloc(): unaligned tcache chunk detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1920665/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1920665] Re: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected"
I should repeat, I am performing the installation using 'Safe Graphics' mode. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1920665 Title: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected" Status in mesa package in Ubuntu: Confirmed Status in ubiquity package in Ubuntu: Confirmed Status in mesa source package in Hirsute: Confirmed Status in ubiquity source package in Hirsute: Confirmed Bug description: ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity 21.04.11 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.460 CurrentDesktop: KDE Date: Sun Mar 21 11:53:44 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210321) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) Since approximately 16/03/2021 ubiquity from maybe-ubiquity (try install screen) and from the live session is crashing on launch or shortly after. Try/Install crash: Screen fails to start, or starts then crashes on any user action. The user is presented with: "Installation failed - The installer encountered an unrecoverable error. A desktop session will now be run so that you may investigate the problem or try installing again" Live session crash: The installer does not start from the desktop icon. Starting ubiquity from the terminal results in an "Aborted (core dumped)" message and nothing else. An example /var/log/installer/debug log from a session where both crashes were triggered is below. /var/log/installer/debug Ubiquity 21.04.11 TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. QSocketNotifier: Invalid socket 17 and type 'Read', disabling... QSocketNotifier: Invalid socket 17 and type 'Write', disabling... QSocketNotifier: Invalid socket 17 and type 'Exception', disabling... Your console font configuration will be updated the next time your system boots. If you want to update it now, run 'setupcon' from a virtual console. update-initramfs is disabled since running on read-only media debconf: DbDriver "passwords" warning: could not open /var/cache/debconf/passwords.dat: Permission denied munmap_chunk(): invalid pointer Ubiquity 21.04.11 QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. malloc(): unaligned tcache chunk detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1920665/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1920665] Re: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected"
I have attempted to install from kubuntu hirsute daily build 21-03-22 kubuntu hirsute daily build 21-03-23 kubuntu hirsute daily build 21-03-24 each version the insstallation fails. Incidentally I noticed another change. While the daily builds were installing correctly a procedure appeared on screen, this no longer happens. After booting the installation media, a self check ran with an on screen display showing the stages the check was passing through. The word Kubuntu appeared on screen and this display was beneath it. Since the installation began to fail, the file check no longer shows and although the word Kubuntu appears it disappears shortly after. As it changed when installation began to fail, maybe there is a connection? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1920665 Title: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected" Status in mesa package in Ubuntu: Confirmed Status in ubiquity package in Ubuntu: Confirmed Status in mesa source package in Hirsute: Confirmed Status in ubiquity source package in Hirsute: Confirmed Bug description: ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity 21.04.11 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.460 CurrentDesktop: KDE Date: Sun Mar 21 11:53:44 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210321) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) Since approximately 16/03/2021 ubiquity from maybe-ubiquity (try install screen) and from the live session is crashing on launch or shortly after. Try/Install crash: Screen fails to start, or starts then crashes on any user action. The user is presented with: "Installation failed - The installer encountered an unrecoverable error. A desktop session will now be run so that you may investigate the problem or try installing again" Live session crash: The installer does not start from the desktop icon. Starting ubiquity from the terminal results in an "Aborted (core dumped)" message and nothing else. An example /var/log/installer/debug log from a session where both crashes were triggered is below. /var/log/installer/debug Ubiquity 21.04.11 TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. QSocketNotifier: Invalid socket 17 and type 'Read', disabling... QSocketNotifier: Invalid socket 17 and type 'Write', disabling... QSocketNotifier: Invalid socket 17 and type 'Exception', disabling... Your console font configuration will be updated the next time your system boots. If you want to update it now, run 'setupcon' from a virtual console. update-initramfs is disabled since running on read-only media debconf: DbDriver "passwords" warning: could not open /var/cache/debconf/passwords.dat: Permission denied munmap_chunk(): invalid pointer Ubiquity 21.04.11 QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. malloc(): unaligned tcache chunk detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1920665/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1920665] Re: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected"
It turns out I don't have my latest successful installation of Kubuntu Hirsute. I did a successful install of Ubuntu Hirsute to confirm whether it was only the Kubuntu version that was affected. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1920665 Title: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected" Status in mesa package in Ubuntu: Confirmed Status in ubiquity package in Ubuntu: Confirmed Status in mesa source package in Hirsute: Confirmed Status in ubiquity source package in Hirsute: Confirmed Bug description: ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity 21.04.11 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.460 CurrentDesktop: KDE Date: Sun Mar 21 11:53:44 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210321) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) Since approximately 16/03/2021 ubiquity from maybe-ubiquity (try install screen) and from the live session is crashing on launch or shortly after. Try/Install crash: Screen fails to start, or starts then crashes on any user action. The user is presented with: "Installation failed - The installer encountered an unrecoverable error. A desktop session will now be run so that you may investigate the problem or try installing again" Live session crash: The installer does not start from the desktop icon. Starting ubiquity from the terminal results in an "Aborted (core dumped)" message and nothing else. An example /var/log/installer/debug log from a session where both crashes were triggered is below. /var/log/installer/debug Ubiquity 21.04.11 TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. QSocketNotifier: Invalid socket 17 and type 'Read', disabling... QSocketNotifier: Invalid socket 17 and type 'Write', disabling... QSocketNotifier: Invalid socket 17 and type 'Exception', disabling... Your console font configuration will be updated the next time your system boots. If you want to update it now, run 'setupcon' from a virtual console. update-initramfs is disabled since running on read-only media debconf: DbDriver "passwords" warning: could not open /var/cache/debconf/passwords.dat: Permission denied munmap_chunk(): invalid pointer Ubiquity 21.04.11 QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. malloc(): unaligned tcache chunk detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1920665/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1920665] Re: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected"
My nvidia graphics card needs safe mode, but generally installations proceed without problems. The Hirsute daily builds were installing without a hitch until recently. I'll check my most recent successful installation and see if I can find a version number. It was after this that the bug appeared. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1920665 Title: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected" Status in mesa package in Ubuntu: Confirmed Status in ubiquity package in Ubuntu: Confirmed Status in mesa source package in Hirsute: Confirmed Status in ubiquity source package in Hirsute: Confirmed Bug description: ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity 21.04.11 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.460 CurrentDesktop: KDE Date: Sun Mar 21 11:53:44 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210321) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) Since approximately 16/03/2021 ubiquity from maybe-ubiquity (try install screen) and from the live session is crashing on launch or shortly after. Try/Install crash: Screen fails to start, or starts then crashes on any user action. The user is presented with: "Installation failed - The installer encountered an unrecoverable error. A desktop session will now be run so that you may investigate the problem or try installing again" Live session crash: The installer does not start from the desktop icon. Starting ubiquity from the terminal results in an "Aborted (core dumped)" message and nothing else. An example /var/log/installer/debug log from a session where both crashes were triggered is below. /var/log/installer/debug Ubiquity 21.04.11 TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. QSocketNotifier: Invalid socket 17 and type 'Read', disabling... QSocketNotifier: Invalid socket 17 and type 'Write', disabling... QSocketNotifier: Invalid socket 17 and type 'Exception', disabling... Your console font configuration will be updated the next time your system boots. If you want to update it now, run 'setupcon' from a virtual console. update-initramfs is disabled since running on read-only media debconf: DbDriver "passwords" warning: could not open /var/cache/debconf/passwords.dat: Permission denied munmap_chunk(): invalid pointer Ubiquity 21.04.11 QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. malloc(): unaligned tcache chunk detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1920665/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1920665] Re: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected"
correction tp post #11: I just re-attempted installing from thumb drive on my hardware with ISO 2021-03-23 crash as with ISO 2021-03-22 and earlier I have nVidia graphics [using safe mode install option] my hardware is home built PC -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1920665 Title: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected" Status in mesa package in Ubuntu: Confirmed Status in ubiquity package in Ubuntu: Confirmed Status in mesa source package in Hirsute: Confirmed Status in ubiquity source package in Hirsute: Confirmed Bug description: ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity 21.04.11 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.460 CurrentDesktop: KDE Date: Sun Mar 21 11:53:44 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210321) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) Since approximately 16/03/2021 ubiquity from maybe-ubiquity (try install screen) and from the live session is crashing on launch or shortly after. Try/Install crash: Screen fails to start, or starts then crashes on any user action. The user is presented with: "Installation failed - The installer encountered an unrecoverable error. A desktop session will now be run so that you may investigate the problem or try installing again" Live session crash: The installer does not start from the desktop icon. Starting ubiquity from the terminal results in an "Aborted (core dumped)" message and nothing else. An example /var/log/installer/debug log from a session where both crashes were triggered is below. /var/log/installer/debug Ubiquity 21.04.11 TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. QSocketNotifier: Invalid socket 17 and type 'Read', disabling... QSocketNotifier: Invalid socket 17 and type 'Write', disabling... QSocketNotifier: Invalid socket 17 and type 'Exception', disabling... Your console font configuration will be updated the next time your system boots. If you want to update it now, run 'setupcon' from a virtual console. update-initramfs is disabled since running on read-only media debconf: DbDriver "passwords" warning: could not open /var/cache/debconf/passwords.dat: Permission denied munmap_chunk(): invalid pointer Ubiquity 21.04.11 QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. malloc(): unaligned tcache chunk detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1920665/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1920665] Re: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected"
crash on my hardware with ISO 2021-03-23 no error message appears now I just get a black screen mouse pointer visible -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1920665 Title: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected" Status in mesa package in Ubuntu: Confirmed Status in ubiquity package in Ubuntu: Confirmed Status in mesa source package in Hirsute: Confirmed Status in ubiquity source package in Hirsute: Confirmed Bug description: ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity 21.04.11 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.460 CurrentDesktop: KDE Date: Sun Mar 21 11:53:44 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210321) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) Since approximately 16/03/2021 ubiquity from maybe-ubiquity (try install screen) and from the live session is crashing on launch or shortly after. Try/Install crash: Screen fails to start, or starts then crashes on any user action. The user is presented with: "Installation failed - The installer encountered an unrecoverable error. A desktop session will now be run so that you may investigate the problem or try installing again" Live session crash: The installer does not start from the desktop icon. Starting ubiquity from the terminal results in an "Aborted (core dumped)" message and nothing else. An example /var/log/installer/debug log from a session where both crashes were triggered is below. /var/log/installer/debug Ubiquity 21.04.11 TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. QSocketNotifier: Invalid socket 17 and type 'Read', disabling... QSocketNotifier: Invalid socket 17 and type 'Write', disabling... QSocketNotifier: Invalid socket 17 and type 'Exception', disabling... Your console font configuration will be updated the next time your system boots. If you want to update it now, run 'setupcon' from a virtual console. update-initramfs is disabled since running on read-only media debconf: DbDriver "passwords" warning: could not open /var/cache/debconf/passwords.dat: Permission denied munmap_chunk(): invalid pointer Ubiquity 21.04.11 QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. malloc(): unaligned tcache chunk detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1920665/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1920665] Re: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected"
Unfortunately iso 20210322 is producing a crash on my hardware. [see bug 1920712] -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1920665 Title: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected" Status in mesa package in Ubuntu: New Status in ubiquity package in Ubuntu: New Status in mesa source package in Hirsute: New Status in ubiquity source package in Hirsute: New Bug description: ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity 21.04.11 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.460 CurrentDesktop: KDE Date: Sun Mar 21 11:53:44 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210321) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) Since approximately 16/03/2021 ubiquity from maybe-ubiquity (try install screen) and from the live session is crashing on launch or shortly after. Try/Install crash: Screen fails to start, or starts then crashes on any user action. The user is presented with: "Installation failed - The installer encountered an unrecoverable error. A desktop session will now be run so that you may investigate the problem or try installing again" Live session crash: The installer does not start from the desktop icon. Starting ubiquity from the terminal results in an "Aborted (core dumped)" message and nothing else. An example /var/log/installer/debug log from a session where both crashes were triggered is below. /var/log/installer/debug Ubiquity 21.04.11 TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. QSocketNotifier: Invalid socket 17 and type 'Read', disabling... QSocketNotifier: Invalid socket 17 and type 'Write', disabling... QSocketNotifier: Invalid socket 17 and type 'Exception', disabling... Your console font configuration will be updated the next time your system boots. If you want to update it now, run 'setupcon' from a virtual console. update-initramfs is disabled since running on read-only media debconf: DbDriver "passwords" warning: could not open /var/cache/debconf/passwords.dat: Permission denied munmap_chunk(): invalid pointer Ubiquity 21.04.11 QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. malloc(): unaligned tcache chunk detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1920665/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1920665] Re: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected"
successfully create a thumb drive from: hirsute-desktop-amd64.iso 2021-03-21 05:492.7GDesktop image for 64-bit PC (AMD64) computers (standard download) boot from thumb drive: "Installation failed - KDialog \n The installer encountered an unrecoverable error. A desktop session will now be run so that you may investigate the problem or try installing again" Installation cannot proceed. I don't have the know how to be able to investigate, unfortunately. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1920665 Title: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected" Status in mesa package in Ubuntu: New Status in ubiquity package in Ubuntu: New Status in mesa source package in Hirsute: New Status in ubiquity source package in Hirsute: New Bug description: ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity 21.04.11 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.460 CurrentDesktop: KDE Date: Sun Mar 21 11:53:44 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210321) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) Since approximately 16/03/2021 ubiquity from maybe-ubiquity (try install screen) and from the live session is crashing on launch or shortly after. An example /var/log/installer/debug log from a session where both crashes were triggered is below. /var/log/installer/debug Ubiquity 21.04.11 TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. QSocketNotifier: Invalid socket 17 and type 'Read', disabling... QSocketNotifier: Invalid socket 17 and type 'Write', disabling... QSocketNotifier: Invalid socket 17 and type 'Exception', disabling... Your console font configuration will be updated the next time your system boots. If you want to update it now, run 'setupcon' from a virtual console. update-initramfs is disabled since running on read-only media debconf: DbDriver "passwords" warning: could not open /var/cache/debconf/passwords.dat: Permission denied munmap_chunk(): invalid pointer Ubiquity 21.04.11 QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu' TEXT If more than one person will use this computer, you can set up multiple accounts after installation. TEXT Enter the same password twice, so that it can be checked for typing errors. TEXT The name it uses when it talks to other computers. TEXT Enter the same password twice, so that it can be checked for typing errors. malloc(): unaligned tcache chunk detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1920665/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1864178] Re: Rhythmbox crashes when trying to connect to iPhone
Same problem in 20.04.1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1864178 Title: Rhythmbox crashes when trying to connect to iPhone Status in Rhythmbox: New Status in rhythmbox package in Ubuntu: Triaged Bug description: I connected my iPhone to my laptop running Ubuntu 19.10. Nautilus and Shotwell loaded the device fine. But when I open Rhythmbox, it crashes. I opened Rhythmbox from the terminal to see the error and I got this ``` (rhythmbox:15045): Gtk-WARNING **: 09:47:19.122: actionhelper: action app.play-repeat can't be activated due to parameter type mismatch (parameter type NULL, target type b) (rhythmbox:15045): Gtk-WARNING **: 09:47:19.122: actionhelper: action app.play-shuffle can't be activated due to parameter type mismatch (parameter type NULL, target type b) ** Rhythmbox:ERROR:rb-ipod-helpers.c:359:rb_ipod_helpers_is_ipod: assertion failed: (strlen (uri) >= 46) Bail out! Rhythmbox:ERROR:rb-ipod-helpers.c:359:rb_ipod_helpers_is_ipod: assertion failed: (strlen (uri) >= 46) [1]15045 abort (core dumped) rhythmbox ``` Details of the current system: ``` lsb_release -rd Description: Ubuntu 19.10 Release: 19.10 ``` ``` apt-cache policy rhythmbox rhythmbox: Installed: 3.4.3-2ubuntu1 Candidate: 3.4.3-2ubuntu1 Version table: *** 3.4.3-2ubuntu1 500 500 http://gb.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status ``` What I expected to happen: I was expected Rhythmbox to show my iPhone under "devices" What actually happned: Rhythmbox just crashed To manage notifications about this bug go to: https://bugs.launchpad.net/rhythmbox/+bug/1864178/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1910480] Re: no audio on fresh install kubuntu groovy
** Changed in: alsa-driver (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1910480 Title: no audio on fresh install kubuntu groovy Status in alsa-driver package in Ubuntu: Invalid Bug description: on installing Kubuntu Groovy 'no output or input devices found' sound appears to be disabled running ubuntu-debug -s audio does produce sound in both headphone channels in first part of test but no sound in second part sound is recognised and working okay if Kubuntu Focal is installed ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.8.0-34.37-generic 5.8.18 Uname: Linux 5.8.0-34-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bob1071 F pulseaudio bob1074 F pipewire-media- /dev/snd/controlC1: bob1074 F pipewire-media- /dev/snd/seq:bob1070 F pipewire CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Thu Jan 7 03:19:48 2021 PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:SB successful Symptom_Card: Built-in Audio - HDA ATI SB Symptom_Jack: SPDIF Out, Internal Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: None of the above Title: [MBB-895908, Realtek ALC892, SPDIF Out, Internal] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2014 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2501 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M5A99FX PRO R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: 7354844-001 dmi.chassis.type: 3 dmi.chassis.vendor: NOVATECH LTD dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2501:bd04/07/2014:br4.6:svnNOVATECHLTD:pnMBB-895908:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnM5A99FXPROR2.0:rvrRev1.xx:cvnNOVATECHLTD:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MBB-895908 dmi.product.sku: SKU dmi.product.version: 1.0 dmi.sys.vendor: NOVATECH LTD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1910480/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1910480] Re: no audio on fresh install kubuntu groovy
When I submitted this report I wasn't aware that this issue had been mentioned in the Release Notes (which weren't available at the time) ...that means this report is not required. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1910480 Title: no audio on fresh install kubuntu groovy Status in alsa-driver package in Ubuntu: New Bug description: on installing Kubuntu Groovy 'no output or input devices found' sound appears to be disabled running ubuntu-debug -s audio does produce sound in both headphone channels in first part of test but no sound in second part sound is recognised and working okay if Kubuntu Focal is installed ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.8.0-34.37-generic 5.8.18 Uname: Linux 5.8.0-34-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bob1071 F pulseaudio bob1074 F pipewire-media- /dev/snd/controlC1: bob1074 F pipewire-media- /dev/snd/seq:bob1070 F pipewire CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Thu Jan 7 03:19:48 2021 PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:SB successful Symptom_Card: Built-in Audio - HDA ATI SB Symptom_Jack: SPDIF Out, Internal Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: None of the above Title: [MBB-895908, Realtek ALC892, SPDIF Out, Internal] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2014 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2501 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M5A99FX PRO R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: 7354844-001 dmi.chassis.type: 3 dmi.chassis.vendor: NOVATECH LTD dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2501:bd04/07/2014:br4.6:svnNOVATECHLTD:pnMBB-895908:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnM5A99FXPROR2.0:rvrRev1.xx:cvnNOVATECHLTD:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MBB-895908 dmi.product.sku: SKU dmi.product.version: 1.0 dmi.sys.vendor: NOVATECH LTD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1910480/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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 1854682] Re: Feature request: Add option to "Privacy" in Ubuntu Settings that would enable/disable software installation outside trusted app stores.
I think this feature would make Ubuntu more secure. Most computers get infected with malware because people download software from untrusted sources. If a user downloads an infected .deb file and then enters their root password to install the software, could the malware take control over their computer? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1854682 Title: Feature request: Add option to "Privacy" in Ubuntu Settings that would enable/disable software installation outside trusted app stores. Status in ubuntu-settings package in Ubuntu: Opinion Bug description: 1) Ubuntu 19.10 2) Gnome Settings 1:3.34.1-1ubuntu2 3) Ability to block installation of untrusted software not in trusted app stores(Ubuntu Software Center, Steam, etc). 4) Unable to block installation of untrusted software not in trusted app stores. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1854682/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1854682] Re: Feature request: Add option to "Privacy" in Ubuntu Settings that would enable/disable software installation outside trusted app stores.
** Summary changed: - Add option to "Privacy" in Ubuntu Settings that would enable/disable software installation outside trusted app stores. + Feature request: Add option to "Privacy" in Ubuntu Settings that would enable/disable software installation outside trusted app stores. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1854682 Title: Feature request: Add option to "Privacy" in Ubuntu Settings that would enable/disable software installation outside trusted app stores. Status in ubuntu-settings package in Ubuntu: Opinion Bug description: 1) Ubuntu 19.10 2) Gnome Settings 1:3.34.1-1ubuntu2 3) Ability to block installation of untrusted software not in trusted app stores(Ubuntu Software Center, Steam, etc). 4) Unable to block installation of untrusted software not in trusted app stores. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1854682/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1897192] [NEW] Put search box in top center of Activities panel, move date/time to right corner of panel.
Public bug reported: 1) Ubuntu 20.04 2) Gnome 3.36 3) If there was a search box in the top center of the Activities panel, it would make it easy for a user to quickly search for an app or information on the internet. Canonical could collect referral fees from Google or another search provider, when users search and buy products. The referral fees could be used to improve Ubuntu. 4) There is not a search box in the top center of the Activities panel. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1897192 Title: Put search box in top center of Activities panel, move date/time to right corner of panel. Status in gnome-shell package in Ubuntu: New Bug description: 1) Ubuntu 20.04 2) Gnome 3.36 3) If there was a search box in the top center of the Activities panel, it would make it easy for a user to quickly search for an app or information on the internet. Canonical could collect referral fees from Google or another search provider, when users search and buy products. The referral fees could be used to improve Ubuntu. 4) There is not a search box in the top center of the Activities panel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1897192/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1883886]
(In reply to Alex Thurgood from comment #111) > > Note that LibreOffice Vanilla appears to diplay the dialog correctly, > whereas LO7001rc and my test on 7100alpha, do not display the dialog > correctly. Also tested on Version: 6.4.6.2 Build ID: 0ce51a4fd21bff07a5c061082cc82c5ed232f115 CPU threads: 4; OS: Mac OS X 10.15.6; UI render: default; VCL: osx; Locale: fr-FR (fr_FR.UTF-8); UI-Language: en-US Calc: threaded problem reproducible there too. -- 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/1883886 Title: Print dialogue's height in Libreoffice Writer is too high to see and click buttons. Status in LibreOffice: Confirmed Status in libreoffice package in Ubuntu: Fix Released Bug description: Hello, I have the bug that is denoted here https://ask.libreoffice.org/en/question/240651/print-dialogue-too- large-to-select-ok-to-print/ and here https://bugs.documentfoundation.org/show_bug.cgi?id=127782#c67. Essentially, the libreoffice writer print's dialog box is too high for me to view and press the buttons with the mouse. A workaround is to just press ENTER to print. Please see the following screenshot for an example: https://snipboard.io/vc1X0f.jpg My information is as follows: Results of lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 Results of apt-cache policy libreoffice-writer libreoffice-writer: Installed: 1:6.4.3-0ubuntu0.20.04.1 Candidate: 1:6.4.3-0ubuntu0.20.04.1 Version table: *** 1:6.4.3-0ubuntu0.20.04.1 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:6.4.2-0ubuntu3 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages Just FYI in case it is necessary: I am using Lubuntu 20.04 LTS with LXQt. Best regards, Owen Charles ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libreoffice-writer 1:6.4.3-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: LXQt Date: Wed Jun 17 12:47:56 2020 InstallationDate: Installed on 2020-06-05 (11 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1883886/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1883886]
(In reply to Alex Thurgood from comment #110) > (In reply to Heiko Tietze from comment #106) > > (In reply to Alex Thurgood from comment #105) > > > Version : 6.4.3.2 > > > > Please test with a nightly build (or RC1) of 7.0. > > Still not fixed with > > Version: 7.1.0.0.alpha0+ > Build ID: > CPU threads: 4; OS: Mac OS X 10.15.6; UI render: default; VCL: osx > Locale: fr-FR (fr_FR.UTF-8); UI: en-US > Calc: threaded > > and also reported separately in bug 136609 > > Reopening. Note that LibreOffice Vanilla appears to diplay the dialog correctly, whereas LO7001rc and my test on 7100alpha, do not display the dialog correctly. -- 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/1883886 Title: Print dialogue's height in Libreoffice Writer is too high to see and click buttons. Status in LibreOffice: Confirmed Status in libreoffice package in Ubuntu: Fix Released Bug description: Hello, I have the bug that is denoted here https://ask.libreoffice.org/en/question/240651/print-dialogue-too- large-to-select-ok-to-print/ and here https://bugs.documentfoundation.org/show_bug.cgi?id=127782#c67. Essentially, the libreoffice writer print's dialog box is too high for me to view and press the buttons with the mouse. A workaround is to just press ENTER to print. Please see the following screenshot for an example: https://snipboard.io/vc1X0f.jpg My information is as follows: Results of lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 Results of apt-cache policy libreoffice-writer libreoffice-writer: Installed: 1:6.4.3-0ubuntu0.20.04.1 Candidate: 1:6.4.3-0ubuntu0.20.04.1 Version table: *** 1:6.4.3-0ubuntu0.20.04.1 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:6.4.2-0ubuntu3 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages Just FYI in case it is necessary: I am using Lubuntu 20.04 LTS with LXQt. Best regards, Owen Charles ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libreoffice-writer 1:6.4.3-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: LXQt Date: Wed Jun 17 12:47:56 2020 InstallationDate: Installed on 2020-06-05 (11 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1883886/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1883886]
*** Bug 136609 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/1883886 Title: Print dialogue's height in Libreoffice Writer is too high to see and click buttons. Status in LibreOffice: Confirmed Status in libreoffice package in Ubuntu: Fix Released Bug description: Hello, I have the bug that is denoted here https://ask.libreoffice.org/en/question/240651/print-dialogue-too- large-to-select-ok-to-print/ and here https://bugs.documentfoundation.org/show_bug.cgi?id=127782#c67. Essentially, the libreoffice writer print's dialog box is too high for me to view and press the buttons with the mouse. A workaround is to just press ENTER to print. Please see the following screenshot for an example: https://snipboard.io/vc1X0f.jpg My information is as follows: Results of lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 Results of apt-cache policy libreoffice-writer libreoffice-writer: Installed: 1:6.4.3-0ubuntu0.20.04.1 Candidate: 1:6.4.3-0ubuntu0.20.04.1 Version table: *** 1:6.4.3-0ubuntu0.20.04.1 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:6.4.2-0ubuntu3 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages Just FYI in case it is necessary: I am using Lubuntu 20.04 LTS with LXQt. Best regards, Owen Charles ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libreoffice-writer 1:6.4.3-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: LXQt Date: Wed Jun 17 12:47:56 2020 InstallationDate: Installed on 2020-06-05 (11 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1883886/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1883886]
Reproduced also with Version: 7.0.1.2 Build ID: 7cbcfc562f6eb6708b5ff7d7397325de9e764452 CPU threads: 4; OS: Mac OS X 10.15.6; UI render: default; VCL: osx Locale: fr-FR (fr_FR.UTF-8); UI: en-US Calc: threaded -- 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/1883886 Title: Print dialogue's height in Libreoffice Writer is too high to see and click buttons. Status in LibreOffice: Confirmed Status in libreoffice package in Ubuntu: Fix Released Bug description: Hello, I have the bug that is denoted here https://ask.libreoffice.org/en/question/240651/print-dialogue-too- large-to-select-ok-to-print/ and here https://bugs.documentfoundation.org/show_bug.cgi?id=127782#c67. Essentially, the libreoffice writer print's dialog box is too high for me to view and press the buttons with the mouse. A workaround is to just press ENTER to print. Please see the following screenshot for an example: https://snipboard.io/vc1X0f.jpg My information is as follows: Results of lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 Results of apt-cache policy libreoffice-writer libreoffice-writer: Installed: 1:6.4.3-0ubuntu0.20.04.1 Candidate: 1:6.4.3-0ubuntu0.20.04.1 Version table: *** 1:6.4.3-0ubuntu0.20.04.1 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:6.4.2-0ubuntu3 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages Just FYI in case it is necessary: I am using Lubuntu 20.04 LTS with LXQt. Best regards, Owen Charles ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libreoffice-writer 1:6.4.3-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: LXQt Date: Wed Jun 17 12:47:56 2020 InstallationDate: Installed on 2020-06-05 (11 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1883886/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1883886]
Created attachment 165471 Screenshot of LO 7.0.1.2 Print Dialog macOS 10.15.6 -- 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/1883886 Title: Print dialogue's height in Libreoffice Writer is too high to see and click buttons. Status in LibreOffice: Confirmed Status in libreoffice package in Ubuntu: Fix Released Bug description: Hello, I have the bug that is denoted here https://ask.libreoffice.org/en/question/240651/print-dialogue-too- large-to-select-ok-to-print/ and here https://bugs.documentfoundation.org/show_bug.cgi?id=127782#c67. Essentially, the libreoffice writer print's dialog box is too high for me to view and press the buttons with the mouse. A workaround is to just press ENTER to print. Please see the following screenshot for an example: https://snipboard.io/vc1X0f.jpg My information is as follows: Results of lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 Results of apt-cache policy libreoffice-writer libreoffice-writer: Installed: 1:6.4.3-0ubuntu0.20.04.1 Candidate: 1:6.4.3-0ubuntu0.20.04.1 Version table: *** 1:6.4.3-0ubuntu0.20.04.1 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:6.4.2-0ubuntu3 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages Just FYI in case it is necessary: I am using Lubuntu 20.04 LTS with LXQt. Best regards, Owen Charles ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libreoffice-writer 1:6.4.3-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: LXQt Date: Wed Jun 17 12:47:56 2020 InstallationDate: Installed on 2020-06-05 (11 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1883886/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1883886]
(In reply to Heiko Tietze from comment #106) > (In reply to Alex Thurgood from comment #105) > > Version : 6.4.3.2 > > Please test with a nightly build (or RC1) of 7.0. Still not fixed with Version: 7.1.0.0.alpha0+ Build ID: CPU threads: 4; OS: Mac OS X 10.15.6; UI render: default; VCL: osx Locale: fr-FR (fr_FR.UTF-8); UI: en-US Calc: threaded and also reported separately in bug 136609 Reopening. -- 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/1883886 Title: Print dialogue's height in Libreoffice Writer is too high to see and click buttons. Status in LibreOffice: Confirmed Status in libreoffice package in Ubuntu: Fix Released Bug description: Hello, I have the bug that is denoted here https://ask.libreoffice.org/en/question/240651/print-dialogue-too- large-to-select-ok-to-print/ and here https://bugs.documentfoundation.org/show_bug.cgi?id=127782#c67. Essentially, the libreoffice writer print's dialog box is too high for me to view and press the buttons with the mouse. A workaround is to just press ENTER to print. Please see the following screenshot for an example: https://snipboard.io/vc1X0f.jpg My information is as follows: Results of lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 Results of apt-cache policy libreoffice-writer libreoffice-writer: Installed: 1:6.4.3-0ubuntu0.20.04.1 Candidate: 1:6.4.3-0ubuntu0.20.04.1 Version table: *** 1:6.4.3-0ubuntu0.20.04.1 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:6.4.2-0ubuntu3 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages Just FYI in case it is necessary: I am using Lubuntu 20.04 LTS with LXQt. Best regards, Owen Charles ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libreoffice-writer 1:6.4.3-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: LXQt Date: Wed Jun 17 12:47:56 2020 InstallationDate: Installed on 2020-06-05 (11 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1883886/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1707831] Re: [enhancement] Replace/extend the "Activities" label with the Ubuntu icon/logo/glyph
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1894909 -- 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/1707831 Title: [enhancement] Replace/extend the "Activities" label with the Ubuntu icon/logo/glyph Status in Yaru Theme: Fix Released Status in gnome-shell package in Ubuntu: Triaged Status in yaru-theme package in Ubuntu: Triaged Bug description: I suggest replacing the "Activities" label with the Ubuntu icon/logo. "Activities" sounds awkward and misleading. It would be more suitably vague, and more consistent with the existing Unity7 experience if the Gnome Shell "Activities" label was replaced by just the Ubuntu logo. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.24.3-0ubuntu1 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 ApportVersion: 2.20.6-0ubuntu4 Architecture: amd64 Date: Tue Aug 1 11:28:08 2017 DisplayManager: gdm3 InstallationDate: Installed on 2017-05-03 (89 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/yaru/+bug/1707831/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1894909] [NEW] Feature Request: Ability to change "Applications Overview" button style.
Public bug reported: 1) Ubuntu 20.04 2) Gnome 3.36 3) There could be an option to change the "Applications Overview" button style. Currently, the "Applications Overview" button style is a 3x3 grid. There could be a 3x3 grid option, Ubuntu logo option, (any other suggested icons) and a custom icon option. 4) There is not an option to change the "Applications Overview" button style. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1894909 Title: Feature Request: Ability to change "Applications Overview" button style. Status in gnome-shell package in Ubuntu: New Bug description: 1) Ubuntu 20.04 2) Gnome 3.36 3) There could be an option to change the "Applications Overview" button style. Currently, the "Applications Overview" button style is a 3x3 grid. There could be a 3x3 grid option, Ubuntu logo option, (any other suggested icons) and a custom icon option. 4) There is not an option to change the "Applications Overview" button style. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1894909/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1707831] Re: [enhancement] Replace/extend the "Activities" label with the Ubuntu icon/logo/glyph
"I disagree, but regardless that should be a different bug." What are your reasons? -- 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/1707831 Title: [enhancement] Replace/extend the "Activities" label with the Ubuntu icon/logo/glyph Status in Yaru Theme: Fix Released Status in gnome-shell package in Ubuntu: Triaged Status in yaru-theme package in Ubuntu: Triaged Bug description: I suggest replacing the "Activities" label with the Ubuntu icon/logo. "Activities" sounds awkward and misleading. It would be more suitably vague, and more consistent with the existing Unity7 experience if the Gnome Shell "Activities" label was replaced by just the Ubuntu logo. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.24.3-0ubuntu1 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 ApportVersion: 2.20.6-0ubuntu4 Architecture: amd64 Date: Tue Aug 1 11:28:08 2017 DisplayManager: gdm3 InstallationDate: Installed on 2017-05-03 (89 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/yaru/+bug/1707831/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1894888] [NEW] Feature Request: Add an "Energy" or "Power" tab.
Public bug reported: 1) Ubuntu 20.04 2) 3.26.0 3) There could be an energy tab screen, that would display power consumption. PowerTop(https://en.wikipedia.org/wiki/PowerTOP) could be integrated. 4) There is no "Energy" tab screen. ** Affects: gnome-system-monitor (Ubuntu) Importance: Undecided Status: New ** Bug watch added: gitlab.gnome.org/GNOME/gnome-system-monitor/-/issues #16 https://gitlab.gnome.org/GNOME/gnome-system-monitor/-/issues/16 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-system-monitor in Ubuntu. https://bugs.launchpad.net/bugs/1894888 Title: Feature Request: Add an "Energy" or "Power" tab. Status in gnome-system-monitor package in Ubuntu: New Bug description: 1) Ubuntu 20.04 2) 3.26.0 3) There could be an energy tab screen, that would display power consumption. PowerTop(https://en.wikipedia.org/wiki/PowerTOP) could be integrated. 4) There is no "Energy" tab screen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1894888/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1894888] Re: Feature Request: Add an "Energy" or "Power" tab.
https://gitlab.gnome.org/GNOME/gnome-system-monitor/-/issues/16 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-system-monitor in Ubuntu. https://bugs.launchpad.net/bugs/1894888 Title: Feature Request: Add an "Energy" or "Power" tab. Status in gnome-system-monitor package in Ubuntu: New Bug description: 1) Ubuntu 20.04 2) 3.26.0 3) There could be an energy tab screen, that would display power consumption. PowerTop(https://en.wikipedia.org/wiki/PowerTOP) could be integrated. 4) There is no "Energy" tab screen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1894888/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1894770] Re: Feature Request: Add a "GPU History" in the "Resources" tab screen.
** Summary changed: - Feature Request: Add a "GPU" usage in the "Resources" tab screen. + Feature Request: Add a "GPU History" in the "Resources" tab screen. ** Description changed: 1) Ubuntu 20.04 2) 3.26.0 - 3) Add a "GPU" usage in the "Resources" tab screen. - 4) There is no GPU usage in the "Resources" tab sreen. + 3) Add a "GPU History" on the "Resources" tab screen. + 4) There is no "GPU History" on the "Resources" tab screen. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-system-monitor in Ubuntu. https://bugs.launchpad.net/bugs/1894770 Title: Feature Request: Add a "GPU History" in the "Resources" tab screen. Status in gnome-system-monitor package in Ubuntu: New Bug description: 1) Ubuntu 20.04 2) 3.26.0 3) Add a "GPU History" on the "Resources" tab screen. 4) There is no "GPU History" on the "Resources" tab screen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1894770/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1894770] [NEW] Feature Request: Add a "GPU" usage in the "Resources" tab screen.
Public bug reported: 1) Ubuntu 20.04 2) 3.26.0 3) Add a "GPU" usage in the "Resources" tab screen. 4) There is no GPU usage in the "Resources" tab sreen. ** Affects: gnome-system-monitor (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-system-monitor in Ubuntu. https://bugs.launchpad.net/bugs/1894770 Title: Feature Request: Add a "GPU" usage in the "Resources" tab screen. Status in gnome-system-monitor package in Ubuntu: New Bug description: 1) Ubuntu 20.04 2) 3.26.0 3) Add a "GPU" usage in the "Resources" tab screen. 4) There is no GPU usage in the "Resources" tab sreen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1894770/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1894768] [NEW] Feature Request: Add a "Hardware" tab.
Public bug reported: 1) Ubuntu 20.04 2) 3.26.0 3) There should be a "Hardware" tab. It could show hardware info. IRQ info/conflicts. It could allow a user to enable/disable hardware. It could display hardware error codes. 4) There is not a "Hardware" tab. ** Affects: gnome-system-monitor (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-system-monitor in Ubuntu. https://bugs.launchpad.net/bugs/1894768 Title: Feature Request: Add a "Hardware" tab. Status in gnome-system-monitor package in Ubuntu: New Bug description: 1) Ubuntu 20.04 2) 3.26.0 3) There should be a "Hardware" tab. It could show hardware info. IRQ info/conflicts. It could allow a user to enable/disable hardware. It could display hardware error codes. 4) There is not a "Hardware" tab. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1894768/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1894767] [NEW] Feature Request: Add a "Sensors" tab that would display CPU/GPU/HDD temperature info and selectable auto/manual fan control.
Public bug reported: 1) Ubuntu 20.04 2) 3.26.0 3) There should be a "Sensors" tab. It would display sensor values. It would allow a user to adjust fan speeds. You could integrate psensor into System Monitor. http://wpitchoune.net/psensor 4) There is not a "Sensors" tab. ** Affects: gnome-system-monitor (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-system-monitor in Ubuntu. https://bugs.launchpad.net/bugs/1894767 Title: Feature Request: Add a "Sensors" tab that would display CPU/GPU/HDD temperature info and selectable auto/manual fan control. Status in gnome-system-monitor package in Ubuntu: New Bug description: 1) Ubuntu 20.04 2) 3.26.0 3) There should be a "Sensors" tab. It would display sensor values. It would allow a user to adjust fan speeds. You could integrate psensor into System Monitor. http://wpitchoune.net/psensor 4) There is not a "Sensors" tab. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1894767/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1894766] Re: Feature Request: Add a "Data Usage" tab.
Reported to: https://gitlab.gnome.org/GNOME/gnome-system- monitor/-/issues/130 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-system-monitor in Ubuntu. https://bugs.launchpad.net/bugs/1894766 Title: Feature Request: Add a "Data Usage" tab. Status in gnome-system-monitor package in Ubuntu: New Bug description: 1) Ubuntu 20.04 2) 3.26.0 3) There should be a "Data Usage" tab. Historical daily/monthly data usage could be displayed on the "Data Usage" tab screen. 4) There is not a "Data Usage" tab. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1894766/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1894766] [NEW] Feature Request: Add a "Data Usage" tab.
Public bug reported: 1) Ubuntu 20.04 2) 3.26.0 3) There should be a "Data Usage" tab. Historical daily/monthly data usage could be displayed on the "Data Usage" tab screen. 4) There is not a "Data Usage" tab. ** Affects: gnome-system-monitor (Ubuntu) Importance: Undecided Status: New ** Bug watch added: gitlab.gnome.org/GNOME/gnome-system-monitor/-/issues #130 https://gitlab.gnome.org/GNOME/gnome-system-monitor/-/issues/130 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-system-monitor in Ubuntu. https://bugs.launchpad.net/bugs/1894766 Title: Feature Request: Add a "Data Usage" tab. Status in gnome-system-monitor package in Ubuntu: New Bug description: 1) Ubuntu 20.04 2) 3.26.0 3) There should be a "Data Usage" tab. Historical daily/monthly data usage could be displayed on the "Data Usage" tab screen. 4) There is not a "Data Usage" tab. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1894766/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1707831] Re: [enhancement] Replace/extend the "Activities" label with the Ubuntu icon/logo/glyph
Maybe it would be better to change the app grid icon to a Ubuntu icon? -- 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/1707831 Title: [enhancement] Replace/extend the "Activities" label with the Ubuntu icon/logo/glyph Status in Yaru Theme: Fix Released Status in gnome-shell package in Ubuntu: Triaged Status in yaru-theme package in Ubuntu: Triaged Bug description: I suggest replacing the "Activities" label with the Ubuntu icon/logo. "Activities" sounds awkward and misleading. It would be more suitably vague, and more consistent with the existing Unity7 experience if the Gnome Shell "Activities" label was replaced by just the Ubuntu logo. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.24.3-0ubuntu1 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 ApportVersion: 2.20.6-0ubuntu4 Architecture: amd64 Date: Tue Aug 1 11:28:08 2017 DisplayManager: gdm3 InstallationDate: Installed on 2017-05-03 (89 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/yaru/+bug/1707831/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1854664] Re: Allow a user to select among a full screen app menu, bottom of the screen horizontal app menu with left/right arrows, or a vertical app menu with up/down arrows lo
Gnome developer said it should be done via an extension. Reported it here: https://github.com/home-sweet-gnome/dash-to-panel/issues/1164 ** Bug watch added: github.com/home-sweet-gnome/dash-to-panel/issues #1164 https://github.com/home-sweet-gnome/dash-to-panel/issues/1164 -- 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/1854664 Title: Allow a user to select among a full screen app menu, bottom of the screen horizontal app menu with left/right arrows, or a vertical app menu with up/down arrows located next to the dash. Status in GNOME Shell: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell-extension-dash-to-panel package in Ubuntu: New Bug description: Ubuntu 19.10 1. In the Settings app, Dock(Dash) screen, there should be an "Application Menu Style" option. The user could select: Full screen, Horizontal, or Vertical. 2. The ability to choose the application menu style. I would prefer a horizontal applications menu. 3. A full screen application menu is the only option. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1854664/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1854664] Re: Allow a user to select among a full screen app menu, bottom of the screen horizontal app menu with left/right arrows, or a vertical app menu with up/down arrows lo
** Also affects: gnome-shell-extension-dash-to-panel (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1854664 Title: Allow a user to select among a full screen app menu, bottom of the screen horizontal app menu with left/right arrows, or a vertical app menu with up/down arrows located next to the dash. Status in GNOME Shell: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell-extension-dash-to-panel package in Ubuntu: New Bug description: Ubuntu 19.10 1. In the Settings app, Dock(Dash) screen, there should be an "Application Menu Style" option. The user could select: Full screen, Horizontal, or Vertical. 2. The ability to choose the application menu style. I would prefer a horizontal applications menu. 3. A full screen application menu is the only option. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1854664/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1855699] Re: Click pen icon on right side of path bar to enter custom path.
** Summary changed: - Double click on path bar to enter custom path. + Click pen icon on right side of path bar to enter custom path. ** Description changed: 1) Ubuntu 19.10 2) 1:3.34.1-1ubuntu1 - 3) Double clicking on the path bar should allow a user to enter a custom path. - 4) Unable to enter a custom path when double clicking on the path bar. + 3) Add a pen icon to the right side of the path bar. If a user clicks the pen icon, the path bar would become editable. + 4) Unable to enter a custom path. -- 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/1855699 Title: Click pen icon on right side of path bar to enter custom path. Status in Nautilus: New Status in nautilus package in Ubuntu: Triaged Bug description: 1) Ubuntu 19.10 2) 1:3.34.1-1ubuntu1 3) Add a pen icon to the right side of the path bar. If a user clicks the pen icon, the path bar would become editable. 4) Unable to enter a custom path. To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1855699/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1879742]
Saeed from Meet here. We think we have a fix for this issue. Can those of you who were having this issue, take a look and see if they're still running into the issue still? -- 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/1879742 Title: When using Google Meet on Firefox, delay sending sound from microphone Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: New Bug description: When using Google Meet in Firefox (Ubuntu 20.04, 76.0.1 (64-bit)), for the first 5-10 seconds of the meeting, nobody can hear anything that I am saying. After that, I have no issues. I also have no issues joining with Chromium. The sound indicator on my end (the little green bars that flash when you are talking) start immediately, but nobody on the call hears anything from me. The only info I could find from Googling was somebody else talking about a similar problem: https://www.reddit.com/r/firefox/comments/9aoae0/google_meet_sound_delayed_on_linux_at_least/ ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 76.0.1+build1-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: aaron-work 1813 F pulseaudio BuildID: 20200507114007 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Wed May 20 17:05:20 2020 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2020-05-03 (16 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.0.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.0.0/24 dev wlp2s0 proto kernel scope link src 192.168.0.14 metric 600 Locales: extensions.sqlite corrupt or missing PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:738 PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=76.0.1/20200507114007 (In use) RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/11/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.1 dmi.board.name: 0F6P3V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.1:bd12/11/2019:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1879742/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1879742]
Just to update, we are working on a fix for this. I'll ping again once it's available. -- 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/1879742 Title: When using Google Meet on Firefox, delay sending sound from microphone Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: New Bug description: When using Google Meet in Firefox (Ubuntu 20.04, 76.0.1 (64-bit)), for the first 5-10 seconds of the meeting, nobody can hear anything that I am saying. After that, I have no issues. I also have no issues joining with Chromium. The sound indicator on my end (the little green bars that flash when you are talking) start immediately, but nobody on the call hears anything from me. The only info I could find from Googling was somebody else talking about a similar problem: https://www.reddit.com/r/firefox/comments/9aoae0/google_meet_sound_delayed_on_linux_at_least/ ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 76.0.1+build1-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: aaron-work 1813 F pulseaudio BuildID: 20200507114007 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Wed May 20 17:05:20 2020 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2020-05-03 (16 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.0.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.0.0/24 dev wlp2s0 proto kernel scope link src 192.168.0.14 metric 600 Locales: extensions.sqlite corrupt or missing PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:738 PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=76.0.1/20200507114007 (In use) RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/11/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.1 dmi.board.name: 0F6P3V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.1:bd12/11/2019:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1879742/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1826639] Re: wpasupplicant: unknown keys in no-mac-addr-change.conf
Working for me too. Many thanks. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1826639 Title: wpasupplicant: unknown keys in no-mac-addr-change.conf Status in wpa package in Ubuntu: Fix Released Status in wpa source package in Focal: Fix Committed Status in wpa package in Debian: New Bug description: * Impact wpa ships an invalid network-manager configuration that triggers warnings * Test case $ journalctl | grep no-mac-addr-change should not have errors listed * Regression potential the change removes configurations which are not needed (since they set the value to the same one as the default) and in the wrong section, it shouldn't have any visible impact Hi, NetworkManager warns that no-mac-addr-change.conf contains unknown configuration directives: # journalctl | grep no-mac-addr-change Apr 25 09:24:50 vougeot NetworkManager[573]: [1556177090.0596] Read config: /etc/NetworkManager/NetworkManager.conf (lib: 10-dns-resolved.conf, 20-connectivity-ubuntu.conf, no-mac-addr-change.conf) (etc: 10-globally-managed-devices.conf, default-wifi-powersave-on.conf) Apr 25 09:24:50 vougeot NetworkManager[573]: [1556177090.0596] config: unknown key 'wifi.cloned-mac-address' in section [device-mac-addr-change-wifi] of file '/usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf' Apr 25 09:24:50 vougeot NetworkManager[573]: [1556177090.0596] config: unknown key 'ethernet.cloned-mac-address' in section [device-mac-addr-change-wifi] of file '/usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf' ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: wpasupplicant 2:2.6-21ubuntu3 Uname: Linux 5.0.9-050009-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: KDE Date: Sat Apr 27 13:15:27 2019 SourcePackage: wpa UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1826639/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1879742]
Finally! Someone in our team was able to repro this as well. So we'll do some debugging and see if we can identify the root cause. -- 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/1879742 Title: When using Google Meet on Firefox, delay sending sound from microphone Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: New Bug description: When using Google Meet in Firefox (Ubuntu 20.04, 76.0.1 (64-bit)), for the first 5-10 seconds of the meeting, nobody can hear anything that I am saying. After that, I have no issues. I also have no issues joining with Chromium. The sound indicator on my end (the little green bars that flash when you are talking) start immediately, but nobody on the call hears anything from me. The only info I could find from Googling was somebody else talking about a similar problem: https://www.reddit.com/r/firefox/comments/9aoae0/google_meet_sound_delayed_on_linux_at_least/ ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 76.0.1+build1-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: aaron-work 1813 F pulseaudio BuildID: 20200507114007 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Wed May 20 17:05:20 2020 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2020-05-03 (16 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.0.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.0.0/24 dev wlp2s0 proto kernel scope link src 192.168.0.14 metric 600 Locales: extensions.sqlite corrupt or missing PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:738 PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=76.0.1/20200507114007 (In use) RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/11/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.1 dmi.board.name: 0F6P3V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.1:bd12/11/2019:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1879742/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1877194] Re: switch-on-connect mistakes startup for USB hotplug
Yes, I thought so too. I even linked it in the description. Since the issue persists after the supposed fix however, it is still an issue. Matthew M. Dean (fireculex), for example, also still has issues (see the other ticket, second to last comment). As mentioned by Daniel van Vugt (vanvugt), on the last comment, if there still are issues -> create a new ticket, which I did. I guess the major difference is that in my case it is a USB-device and not an HDMI. -- 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/1877194 Title: switch-on-connect mistakes startup for USB hotplug Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: Triaged Bug description: Similar to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1847570 Only difference is that it does not reset to HDMI output, but to one of my USB-outputs. It does not respect the change I made after reboot. In short: 1. Boot system 2. "Analogue Output - RODE NT-USB" is selected by default. I want to use "Line Out - Built-in Audio", which I choose. 3. Reboot. 4 Output device is now back to "Analogue Output - RODE NT-USB". ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: marcus 1604 F pulseaudio /dev/snd/controlC0: marcus 1604 F pulseaudio /dev/snd/controlC1: marcus 1604 F pulseaudio /dev/snd/pcmC1D0c: marcus 1604 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed May 6 23:40:08 2020 InstallationDate: Installed on 2020-05-06 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/27/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3703 dmi.board.asset.tag: Default string dmi.board.name: MAXIMUS VIII HERO 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.:bvr3703:bd12/27/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIIIHERO:rvrRev1.xx: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 To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1877194/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873403] Re: [nvidia] Screen turns off when trying to set some fractional scaling values
I have a possible related problem with Ubuntu-mate 20.04. I adjusted my mouse pointer size (Dell Inspiron 7995 with Nvidia GTX 960M graphics) the screen went black mouse pointer frozen, 10 seconds later the login screen appears. If I log back in again the screen is black and I'm stuck in an endless loop. -- 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/1873403 Title: [nvidia] Screen turns off when trying to set some fractional scaling values Status in mutter package in Ubuntu: Confirmed Status in nvidia-graphics-drivers package in Ubuntu: Confirmed Bug description: When the nvidia driver is installed, the screen turns off when trying to set some fractional scaling values like 150%. And it stays off even after rebooting and logging in again. And from ssh I can see there's no current mode set anymore (just like in bug 1869750): $ xrandr Screen 0: minimum 8 x 8, current 960 x 600, maximum 16384 x 16384 DVI-I-0 disconnected (normal left inverted right x axis y axis) DVI-I-1 disconnected (normal left inverted right x axis y axis) DP-0 disconnected (normal left inverted right x axis y axis) DP-1 connected primary (normal left inverted right x axis y axis) 1920x1200 59.95 + 59.88 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.36.1-3ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 17 15:51:15 2020 InstallationDate: Installed on 2020-02-03 (73 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1873403/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1877440] Re: /lib/NetworkManager/conf.d values in wrong section
*** This bug is a duplicate of bug 1826639 *** https://bugs.launchpad.net/bugs/1826639 > Thank you for your bug report, the configuration comes > from wpa and has been fixed in > https://salsa.debian.org/debian/wpa/-/commit/00ec8743 Many thanks. And apologies for not running "dpkg -S ..." and mis- classifying the bug. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1877440 Title: /lib/NetworkManager/conf.d values in wrong section Status in wpa package in Ubuntu: Fix Committed Bug description: $ g ^VER /etc/os-release VERSION="20.10 (Groovy Gorilla)" VERSION_ID="20.10" VERSION_CODENAME=groovy $ apt-cache policy network-manager network-manager: Installed: 1.22.10-1ubuntu3 Candidate: 1.22.10-1ubuntu3 Version table: *** 1.22.10-1ubuntu3 500 500 http://ch.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 100 /var/lib/dpkg/status $ cat /lib/NetworkManager/conf.d/no-mac-addr-change.conf # Certain drivers are known not to support changing the MAC address. # Disable touching the MAC address on such devices. # # See man NetworkManager.conf # # https://bugzilla.gnome.org/show_bug.cgi?id=777523 [device-mac-addr-change-wifi] match-device=driver:rtl8723bs,driver:rtl8189es,driver:r8188eu,driver:8188eu,driver:eagle_sdio,driver:wl wifi.scan-rand-mac-address=no wifi.cloned-mac-address=preserve ethernet.cloned-mac-address=preserve "wifi.cloned-mac-address" and "ethernet.cloned-mac-address=preserve" should be in a "[connection]" section. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1877440/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1856032] Re: Removable media icon stays on the dock after eject.
** Summary changed: - DVD icon did not disappear from dash. + Removable media icon stays on the dock after eject. -- 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/1856032 Title: Removable media icon stays on the dock after eject. Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Bug description: 1) Ubuntu 19.10 2) Dock 3) I placed a DVD in the optical drive. An optical disc with a DVD tag appeared on the dock. I pressed the button on the optical drive to open it. I removed the disc and pressed in the tray. The icon should have disappeared from the dock. 4) The icon did NOT disappear from the dock. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1856032/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1863376] Re: Seg Fault during version check
** Changed in: nautilus (Ubuntu) Status: Invalid => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1863376 Title: Seg Fault during version check Status in nautilus package in Ubuntu: Confirmed Bug description: 1) Ubuntu 19.10 2) 3.34.1 3) No seg fault. 4) Seg fault occurred when checking nautilus version. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1863376/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
