[Desktop-packages] [Bug 1958267] Re: wpa can't connect to servers using TLS 1.1 or older
Thank Kuradakis (p-alexandrosz) #51, I can connect to Hotspot in ubuntu 2204 LTS from my android 11 phone, originally my phone connect error message: connect time exceed - try later, now its ok at all. p.s: I had to edit minor correction at #51: original deb http://archive.ubuntu.com/ubuntu/ impish . to deb http://old-releases.ubuntu.com/ubuntu impish .) and downgrade work perfectly. -- 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 Released 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 1990709] [NEW] package firefox 104.0+build3-0ubuntu0.20.04.1 failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 1
Public bug reported: Snap fails to install during do-release-upgrade from 20.04 to 22.04. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: firefox 104.0+build3-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-126.142-generic 5.4.203 Uname: Linux 5.4.0-126-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kristv 802 F pulseaudio /dev/snd/controlC1: kristv 802 F pulseaudio BuildID: 20220818191623 CasperMD5CheckResult: unknown Channel: Unavailable Date: Fri Sep 23 22:01:11 2022 ErrorMessage: new firefox package pre-installation script subprocess returned error exit status 1 ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-07-28 (1518 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IpRoute: default via 192.168.1.1 dev enp2s0 proto dhcp metric 100 169.254.0.0/16 dev enp2s0 scope link metric 1000 192.168.1.0/24 dev enp2s0 proto kernel scope link src 192.168.1.10 metric 100 NoProfiles: True 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.6, 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.1 apt 2.4.7 RunningIncompatibleAddons: False SourcePackage: firefox Title: package firefox 104.0+build3-0ubuntu0.20.04.1 failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to jammy on 2022-09-24 (0 days ago) dmi.bios.date: 02/21/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080015 dmi.board.name: NC99D3 dmi.board.vendor: Jetway Information Co., Ltd dmi.board.version: 1.0 dmi.chassis.type: 10 dmi.chassis.vendor: Jetway Information Co., Ltd dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080015:bd02/21/2012:svnJetwayInformationCo.,Ltd:pnNC99D3:pvr1.0:rvnJetwayInformationCo.,Ltd:rnNC99D3:rvr1.0:cvnJetwayInformationCo.,Ltd:ct10:cvr1.0: dmi.product.name: NC99D3 dmi.product.version: 1.0 dmi.sys.vendor: Jetway Information Co., Ltd ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy need-duplicate-check -- 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/1990709 Title: package firefox 104.0+build3-0ubuntu0.20.04.1 failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 1 Status in firefox package in Ubuntu: New Bug description: Snap fails to install during do-release-upgrade from 20.04 to 22.04. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: firefox 104.0+build3-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-126.142-generic 5.4.203 Uname: Linux 5.4.0-126-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kristv 802 F pulseaudio /dev/snd/controlC1: kristv 802 F pulseaudio BuildID: 20220818191623 CasperMD5CheckResult: unknown Channel: Unavailable Date: Fri Sep 23 22:01:11 2022 ErrorMessage: new firefox package pre-installation script subprocess returned error exit status 1 ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-07-28 (1518 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IpRoute: default via 192.168.1.1 dev enp2s0 proto dhcp metric 100 169.254.0.0/16 dev enp2s0 scope link metric 1000 192.168.1.0/24 dev enp2s0 proto kernel scope link src 192.168.1.10 metric 100 NoProfiles: True 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.6, 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.1 apt 2.4.7 RunningIncompatibleAddons: False SourcePackage: firefox Title: package firefox 104.0+build3-0ubuntu0.20.04.1 failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to jammy on 2022-09-24 (0 days ago) dmi.bios.date: 02/21/2012
[Desktop-packages] [Bug 1288655] Re: Terminal height shrinks - repeatedly restored shorter than the previous height
Another surprising observation: Wayland seems to work just fine for me, it's only X11 that has the maximization shrinking bug. 'headerbar' can be true or false on Wayland with 22.04. I tried it on two different installs with the same behavior. Okay then. I guess I'll use Wayland. I liked to have the restart feature which Wayland doens't have, but I think I'd rather not have this gnome-terminal bug more than 'r'. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1288655 Title: Terminal height shrinks - repeatedly restored shorter than the previous height Status in GNOME Terminal: New Status in gnome-terminal package in Ubuntu: Triaged Bug description: 1. Open a gnome-terminal window (from the launcher or by pressing Ctrl + Alt + T) 2. "stty -a | grep rows" reports "rows 24; columns 80;" 3. Maximize the window (by clicking on the maximize button, or double clicking the title bar, or dragging the window up to the panel) 4. Do the same again to un-maximize the window 5. Now "stty -a | grep rows" reports "rows 23; columns 79;" Each time I do this, the window keeps getting one character shorter and one character narrower! ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-terminal 3.6.1-0ubuntu6 ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3 Uname: Linux 3.11.0-17-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Thu Mar 6 10:22:46 2014 InstallationDate: Installed on 2010-04-15 (1421 days ago) InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100406.1) MarkForUpload: True SourcePackage: gnome-terminal UpgradeStatus: Upgraded to saucy on 2013-10-29 (128 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-terminal/+bug/1288655/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1975487] Re: zsys not installed during Kinetic ISO install with ZFS option
The package zsys is no longer installed by default in Ubuntu and the test case needs updating. This is something I'm currently working on and will get sorted. ** Also affects: ubuntu-manual-tests Importance: Undecided Status: New ** Changed in: ubuntu-manual-tests Status: New => In Progress ** Changed in: ubuntu-manual-tests Importance: Undecided => High ** Changed in: ubuntu-manual-tests Assignee: (unassigned) => Brian Murray (brian-murray) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to zsys in Ubuntu. https://bugs.launchpad.net/bugs/1975487 Title: zsys not installed during Kinetic ISO install with ZFS option Status in Ubuntu Manual Tests: In Progress Status in zsys package in Ubuntu: New Bug description: After following the instructions at: http://iso.qa.ubuntu.com/qatracker/milestones/433/builds/248685/testcases/1716/results on the 20220523 daily build of Kinetic, I used the command zsysctl show and was met with the message: ~$ zsysctl show Command 'zsysctl' not found, but can be installed with: sudo apt install zsys ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: zsys (not installed) ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon May 23 12:33:24 2022 InstallationDate: Installed on 2022-05-23 (0 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220522) SourcePackage: zsys UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-manual-tests/+bug/1975487/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990705] [NEW] Doesn't autoconnect to wifi using iwd
Public bug reported: If you create your wireless connection with wpa_supplicant, then the /etc/NetworkManager/system-connections/.network lists the "interface-name". But then when you install iwd, it becomes the handler of wireless networks and changes the network interface name without updating the name (or removing it) from the .network file. The upstream bug is https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/1091 Filed the launchpad bug in iwd because an iwd post-install script will be the proposed solution. ** Affects: iwd (Ubuntu) Importance: Undecided Status: New ** Description changed: If you create your wireless connection with wpa_supplicant, then the /etc/NetworkManager/system-connections/.network lists the "interface-name". But then when you install iwd, it becomes the handler of wireless networks and changes the network interface name without updating the name (or removing it) from the .network file. + + The upstream bug is + https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/1091 + + Filed the launchpad bug in iwd because an iwd post-install script will + be the proposed solution. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to iwd in Ubuntu. https://bugs.launchpad.net/bugs/1990705 Title: Doesn't autoconnect to wifi using iwd Status in iwd package in Ubuntu: New Bug description: If you create your wireless connection with wpa_supplicant, then the /etc/NetworkManager/system-connections/.network lists the "interface-name". But then when you install iwd, it becomes the handler of wireless networks and changes the network interface name without updating the name (or removing it) from the .network file. The upstream bug is https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/1091 Filed the launchpad bug in iwd because an iwd post-install script will be the proposed solution. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iwd/+bug/1990705/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1288655] Re: Terminal height shrinks - repeatedly restored shorter than the previous height
@peterx14 I did a few more experiments. One needs a new gnome session altogether for the 'headerbar' false change to work. I tried this a few times to confirm. Just killing all the terminals is not enough. However, when I login/out or kill gnome-session to restart the session manager, the problem is fixed. The side effect is that one loses all the nice gnome-terminal decoration (hamburger menu, find button, etc.). Oh well. Take your choice. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1288655 Title: Terminal height shrinks - repeatedly restored shorter than the previous height Status in GNOME Terminal: New Status in gnome-terminal package in Ubuntu: Triaged Bug description: 1. Open a gnome-terminal window (from the launcher or by pressing Ctrl + Alt + T) 2. "stty -a | grep rows" reports "rows 24; columns 80;" 3. Maximize the window (by clicking on the maximize button, or double clicking the title bar, or dragging the window up to the panel) 4. Do the same again to un-maximize the window 5. Now "stty -a | grep rows" reports "rows 23; columns 79;" Each time I do this, the window keeps getting one character shorter and one character narrower! ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-terminal 3.6.1-0ubuntu6 ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3 Uname: Linux 3.11.0-17-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Thu Mar 6 10:22:46 2014 InstallationDate: Installed on 2010-04-15 (1421 days ago) InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100406.1) MarkForUpload: True SourcePackage: gnome-terminal UpgradeStatus: Upgraded to saucy on 2013-10-29 (128 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-terminal/+bug/1288655/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 462564] Re: [Upstream] Deleting a column in Writer deletes whole table
** Changed in: df-libreoffice Status: Confirmed => Fix Released -- 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/462564 Title: [Upstream] Deleting a column in Writer deletes whole table Status in LibreOffice: Fix Released Status in OpenOffice: Invalid Status in libreoffice package in Ubuntu: Triaged Status in openoffice.org package in Ubuntu: Won't Fix Bug description: Binary package hint: openoffice.org 1) lsb_release -rd Description: Ubuntu 11.04 Release: 11.04 2) apt-cache policy libreoffice-writer libreoffice-writer: Installed: 1:3.3.3-1ubuntu2 Candidate: 1:3.3.3-1ubuntu2 Version table: *** 1:3.3.3-1ubuntu2 0 500 http://us.archive.ubuntu.com/ubuntu/ natty-updates/main i386 Packages 100 /var/lib/dpkg/status 1:3.3.2-1ubuntu4 0 500 http://us.archive.ubuntu.com/ubuntu/ natty/main i386 Packages 3) What is expected to happen in LibreOffice Writer via the Terminal: cd ~/Desktop && wget https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/462564/+attachment/894856/+files/test.odt && lowriter -nologo test.odt is when one highlights the second column of the table -> secondary clicks -> Column -> Delete is only that column is deleted. Please see movie for more details: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/462564/+attachment/894864/+files/out.ogv 4) What happens instead is the whole table is deleted. Reproducible in: lsb_release -rd Description: Ubuntu precise (development branch) Release: 12.04 apt-cache policy libreoffice-writer libreoffice-writer: Installed: 1:3.5.2-2ubuntu1 Candidate: 1:3.5.2-2ubuntu1 Version table: *** 1:3.5.2-2ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ precise/main i386 Packages 100 /var/lib/dpkg/status WORKAROUND: Split the table then delete the column. WORKAROUND: Use Word via WINE. Microsoft Office Word 2003 (11.5604.6505) apt-cache policy wine1.3 wine1.3: Installed: 1.3.28-0ubuntu1~ppa1~natty1 Candidate: 1.3.28-0ubuntu1~ppa1~natty1 Version table: *** 1.3.28-0ubuntu1~ppa1~natty1 0 500 http://ppa.launchpad.net/ubuntu-wine/ppa/ubuntu/ natty/main i386 Packages 100 /var/lib/dpkg/status 1.3.15-0ubuntu5 0 500 http://us.archive.ubuntu.com/ubuntu/ natty/universe i386 Packages ProblemType: Bug Architecture: amd64 Date: Wed Oct 28 09:43:20 2009 DistroRelease: Ubuntu 9.10 NonfreeKernelModules: fglrx Package: openoffice.org-core 1:3.1.1-5ubuntu1 ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-14.48-generic SourcePackage: openoffice.org Uname: Linux 2.6.31-14-generic x86_64 To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/462564/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 399765]
Dear Matthew Paul Thomas, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/399765 Title: [Upstream] Ctrl Q doesn't quit when a combo box is focused Status in LibreOffice: Confirmed Status in OpenOffice: Invalid Status in libreoffice package in Ubuntu: Confirmed Bug description: OpenOffice.org 3.0.1, Ubuntu 9.04 LibreOffice 3.4.3, Ubuntu 11.10 beta 1. Focus any combo box, e.g. the style combo box in Writer, or the font or size combo boxes in Writer or Calc. 2. Type Ctrl Q to quit the program. What should happen: The application quits. What actually happens: Nothing. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/399765/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 462564]
Proposed basic fix at http://gerrit.libreoffice.org/c/core/+/140455 -- 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/462564 Title: [Upstream] Deleting a column in Writer deletes whole table Status in LibreOffice: Fix Released Status in OpenOffice: Invalid Status in libreoffice package in Ubuntu: Triaged Status in openoffice.org package in Ubuntu: Won't Fix Bug description: Binary package hint: openoffice.org 1) lsb_release -rd Description: Ubuntu 11.04 Release: 11.04 2) apt-cache policy libreoffice-writer libreoffice-writer: Installed: 1:3.3.3-1ubuntu2 Candidate: 1:3.3.3-1ubuntu2 Version table: *** 1:3.3.3-1ubuntu2 0 500 http://us.archive.ubuntu.com/ubuntu/ natty-updates/main i386 Packages 100 /var/lib/dpkg/status 1:3.3.2-1ubuntu4 0 500 http://us.archive.ubuntu.com/ubuntu/ natty/main i386 Packages 3) What is expected to happen in LibreOffice Writer via the Terminal: cd ~/Desktop && wget https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/462564/+attachment/894856/+files/test.odt && lowriter -nologo test.odt is when one highlights the second column of the table -> secondary clicks -> Column -> Delete is only that column is deleted. Please see movie for more details: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/462564/+attachment/894864/+files/out.ogv 4) What happens instead is the whole table is deleted. Reproducible in: lsb_release -rd Description: Ubuntu precise (development branch) Release: 12.04 apt-cache policy libreoffice-writer libreoffice-writer: Installed: 1:3.5.2-2ubuntu1 Candidate: 1:3.5.2-2ubuntu1 Version table: *** 1:3.5.2-2ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ precise/main i386 Packages 100 /var/lib/dpkg/status WORKAROUND: Split the table then delete the column. WORKAROUND: Use Word via WINE. Microsoft Office Word 2003 (11.5604.6505) apt-cache policy wine1.3 wine1.3: Installed: 1.3.28-0ubuntu1~ppa1~natty1 Candidate: 1.3.28-0ubuntu1~ppa1~natty1 Version table: *** 1.3.28-0ubuntu1~ppa1~natty1 0 500 http://ppa.launchpad.net/ubuntu-wine/ppa/ubuntu/ natty/main i386 Packages 100 /var/lib/dpkg/status 1.3.15-0ubuntu5 0 500 http://us.archive.ubuntu.com/ubuntu/ natty/universe i386 Packages ProblemType: Bug Architecture: amd64 Date: Wed Oct 28 09:43:20 2009 DistroRelease: Ubuntu 9.10 NonfreeKernelModules: fglrx Package: openoffice.org-core 1:3.1.1-5ubuntu1 ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-14.48-generic SourcePackage: openoffice.org Uname: Linux 2.6.31-14-generic x86_64 To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/462564/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 462564]
Justin Luth committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/bb47ffbc9d36e83695aa0d01767d3f83533c04e0 tdf#46733 sw: don't double-select column during deleteCol It will be available in 7.5.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback. -- 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/462564 Title: [Upstream] Deleting a column in Writer deletes whole table Status in LibreOffice: Fix Released Status in OpenOffice: Invalid Status in libreoffice package in Ubuntu: Triaged Status in openoffice.org package in Ubuntu: Won't Fix Bug description: Binary package hint: openoffice.org 1) lsb_release -rd Description: Ubuntu 11.04 Release: 11.04 2) apt-cache policy libreoffice-writer libreoffice-writer: Installed: 1:3.3.3-1ubuntu2 Candidate: 1:3.3.3-1ubuntu2 Version table: *** 1:3.3.3-1ubuntu2 0 500 http://us.archive.ubuntu.com/ubuntu/ natty-updates/main i386 Packages 100 /var/lib/dpkg/status 1:3.3.2-1ubuntu4 0 500 http://us.archive.ubuntu.com/ubuntu/ natty/main i386 Packages 3) What is expected to happen in LibreOffice Writer via the Terminal: cd ~/Desktop && wget https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/462564/+attachment/894856/+files/test.odt && lowriter -nologo test.odt is when one highlights the second column of the table -> secondary clicks -> Column -> Delete is only that column is deleted. Please see movie for more details: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/462564/+attachment/894864/+files/out.ogv 4) What happens instead is the whole table is deleted. Reproducible in: lsb_release -rd Description: Ubuntu precise (development branch) Release: 12.04 apt-cache policy libreoffice-writer libreoffice-writer: Installed: 1:3.5.2-2ubuntu1 Candidate: 1:3.5.2-2ubuntu1 Version table: *** 1:3.5.2-2ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ precise/main i386 Packages 100 /var/lib/dpkg/status WORKAROUND: Split the table then delete the column. WORKAROUND: Use Word via WINE. Microsoft Office Word 2003 (11.5604.6505) apt-cache policy wine1.3 wine1.3: Installed: 1.3.28-0ubuntu1~ppa1~natty1 Candidate: 1.3.28-0ubuntu1~ppa1~natty1 Version table: *** 1.3.28-0ubuntu1~ppa1~natty1 0 500 http://ppa.launchpad.net/ubuntu-wine/ppa/ubuntu/ natty/main i386 Packages 100 /var/lib/dpkg/status 1.3.15-0ubuntu5 0 500 http://us.archive.ubuntu.com/ubuntu/ natty/universe i386 Packages ProblemType: Bug Architecture: amd64 Date: Wed Oct 28 09:43:20 2009 DistroRelease: Ubuntu 9.10 NonfreeKernelModules: fglrx Package: openoffice.org-core 1:3.1.1-5ubuntu1 ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-14.48-generic SourcePackage: openoffice.org Uname: Linux 2.6.31-14-generic x86_64 To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/462564/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1900454]
Calc - AutoCalculate malfunction, always F9 (ReCalculate) necessary Product: https://amongus2.io LibreOffice Version: 7.1.0.0.alpha0+ Master Hardware -- 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/1900454 Title: Calc doesn't recalculate formulas on cell content changes Status in LibreOffice: Fix Released Status in libreoffice package in Ubuntu: Fix Committed Bug description: libreoffice-calc 1:7.0.2-0ubuntu1 (Groovy) The problem is better explained via steps to reproduce: 1. Start calc; you'll get a new spreadsheet. 2. Fill in the following in cells A1-A3: A1: 1 A2: =A1+1 A3: =A1-1 As expected: A2 is calculated as 2, A3 is calculated as 0. 3. Change A1 to 2 and press enter. A2 is autocalculated to 3, but A3 remains at 0 (wrong!). Now for the fun part: switch to a different application so LibreOffice window loses focus, the put it back in focus. A3 is now recalculated to 1. (Partially taken from: https://ask.libreoffice.org/en/question/271324/calc-v7022-cell- autocalculate-not-working-while-window-has-focus/) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1900454/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1971001] Re: Multiple vulnerabilities in Trusty, Xenial, Bionic, Focal and Jammy
typo in my comment, recommendation is to build tiff with libjbig disabled... sorry.. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tiff in Ubuntu. https://bugs.launchpad.net/bugs/1971001 Title: Multiple vulnerabilities in Trusty, Xenial, Bionic, Focal and Jammy Status in tiff package in Ubuntu: In Progress Bug description: The versions in Trusty, Xenial, Bionic, Focal and Jammy may be vulnerable to all CVEs below. Debian released an advisory on March 24. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tiff/+bug/1971001/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1971001] Re: Multiple vulnerabilities in Trusty, Xenial, Bionic, Focal and Jammy
Can Ubuntu address CVE-2022-1210 similar to other Linux Distros (RHEL, SUSE, YOCTO,...) with not building tiff with JBIG disabled since the bug is really in libjbig (build with --disable-jbig) . See Fedora Bug Tracker https://bugzilla.redhat.com/show_bug.cgi?id=2072615 ** Bug watch added: Red Hat Bugzilla #2072615 https://bugzilla.redhat.com/show_bug.cgi?id=2072615 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tiff in Ubuntu. https://bugs.launchpad.net/bugs/1971001 Title: Multiple vulnerabilities in Trusty, Xenial, Bionic, Focal and Jammy Status in tiff package in Ubuntu: In Progress Bug description: The versions in Trusty, Xenial, Bionic, Focal and Jammy may be vulnerable to all CVEs below. Debian released an advisory on March 24. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tiff/+bug/1971001/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1288655] Re: Terminal height shrinks - repeatedly restored shorter than the previous height
22.04 fresh install, even worse, the window shrunk by 3 lines each time :-O And now even shrinks by 3 rows ... I use toggle full screen back and forth, since this is what I really use a lot, not the maximize. But maximize has the same effect, just checked. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1288655 Title: Terminal height shrinks - repeatedly restored shorter than the previous height Status in GNOME Terminal: New Status in gnome-terminal package in Ubuntu: Triaged Bug description: 1. Open a gnome-terminal window (from the launcher or by pressing Ctrl + Alt + T) 2. "stty -a | grep rows" reports "rows 24; columns 80;" 3. Maximize the window (by clicking on the maximize button, or double clicking the title bar, or dragging the window up to the panel) 4. Do the same again to un-maximize the window 5. Now "stty -a | grep rows" reports "rows 23; columns 79;" Each time I do this, the window keeps getting one character shorter and one character narrower! ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-terminal 3.6.1-0ubuntu6 ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3 Uname: Linux 3.11.0-17-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Thu Mar 6 10:22:46 2014 InstallationDate: Installed on 2010-04-15 (1421 days ago) InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100406.1) MarkForUpload: True SourcePackage: gnome-terminal UpgradeStatus: Upgraded to saucy on 2013-10-29 (128 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-terminal/+bug/1288655/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990669] Re: Sync libwnck3 43.0-2 (main) from Debian unstable (main)
** Changed in: libwnck3 (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libwnck3 in Ubuntu. https://bugs.launchpad.net/bugs/1990669 Title: Sync libwnck3 43.0-2 (main) from Debian unstable (main) Status in libwnck3 package in Ubuntu: Fix Released Bug description: Please sync libwnck3 43.0-2 (main) from Debian unstable (main) Changelog entries since current kinetic version 43.0-1: libwnck3 (43.0-2) unstable; urgency=medium * Add a patch to fix segfault in invalidate_icons. (Closes: #1020262) (LP: #1990263) -- Dmitry Shachnev Fri, 23 Sep 2022 00:16:49 +0300 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libwnck3/+bug/1990669/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1964036] Re: Firefox icon missing from panel following Kubuntu upgrade 20.04->22.04
I just rebuilt ubuntu-release-upgrader to omit the firefox entry in deb2snap.json, i.e. so that the upgrade would not manually install the firefox snap or remove the firefox deb. I used this version to test an upgrade from focal to jammy in a regular Ubuntu VM, and it did not resolve the issue. I still did not have a firefox icon on my dock after the upgrade. I have attached the main.log from that upgrade. I do agree that ideally ubuntu-release-upgrader should let the firefox deb handle the snap transition, but this deb2snap behavior does not appear to be the cause of this issue. ** Attachment added: "main.log" https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1964036/+attachment/5618455/+files/main.log -- 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/1964036 Title: Firefox icon missing from panel following Kubuntu upgrade 20.04->22.04 Status in firefox package in Ubuntu: Confirmed Status in ubuntu-release-upgrader package in Ubuntu: Confirmed Bug description: 1) lsb_release -rd Description:Ubuntu Jammy Jellyfish (development branch) Release:22.04 (Kubuntu Jammy live session in QEMU VM) 2) apt-cache policy ubuntu-release-upgrader-core ubuntu-release-upgrader-core: Installed: 1:22.04.6 3) expected (upgrade from Kubuntu 20.04.3 -> 22.04. Reboot.) * Firefox icon on panel to be intact. * Clicked icon launches browser. * Icon tooltip/mouse hover to describe application. 4) happened instead * Icon is missing/replaced with a generic icon * Icon click produces error notification "Plasma Workspace - preferred://browser" * Icon tooltip/mouse hover appears, though is blank. Additional info: * firefox is still installed, works as expected. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-03-07 (2 days ago) InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819.1) Package: ubuntu-release-upgrader (not installed) ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Tags: jammy dist-upgrade Uname: Linux 5.15.0-18-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-03-07 (2 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1964036/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990689] Re: Cannot connect to Google account after upgrading to 22.04 LTS
** Package changed: ubiquity (Ubuntu) => gnome-online-accounts (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1990689 Title: Cannot connect to Google account after upgrading to 22.04 LTS Status in gnome-online-accounts package in Ubuntu: New Bug description: After upgrading from 20.04 LTS to 22.04 LTS, my Google accounts were disconnected. In the "Parameters/Online accounts" window, a double-click on each Google account opens a window indicating "authentication data expired. Please login to use this account". A click on the "Login" button opens a blank window, the only thing I can do is closing the window. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 NonfreeKernelModules: vboxnetadp vboxnetflt vboxdrv ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Sep 23 21:00:36 2022 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd quiet splash --- maybe-ubiquity InstallationDate: Installed on 2021-12-29 (268 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity Symptom: installation UpgradeStatus: Upgraded to jammy on 2022-09-11 (12 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1990689/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1961910] Re: Ubuntu 22 crash when updating, broken network manager and cannot report bug
crash during full-upgrade: (that removed bunch of packages, see below...)
Start-Date: 2022-09-23 00:16:10
Commandline: apt full-upgrade
black screen, no network.
reboot.
configuring network: (from history)
1093 ip a add 192.168.178.100/24 dev enp37s0
1094 ip link set dev enp37s0 up
1095 ip route add default via 192.168.178.1
/etc/hosts: 129.143.116.10 ftp-stud.hs-esslingen.de (for my
sources.list)
apt update
apt --fix-broken install
(problem remains: no gui no net)
apt install ubuntu-desktop .. gui is back.
found Removed packages from faulty full-upgrade. a bunch of. -> file
atached: Removed
cat Removed | tr , \\n| awk -F: '{print $1}'|grep -v Remove|xargs apt install
-y
did the job. online+working OK
End-Date: 2022-09-23 01:23:51
** Attachment added: "The Removed packages from faulty full-upgrade"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1961910/+attachment/5618454/+files/Removed
--
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/1961910
Title:
Ubuntu 22 crash when updating, broken network manager and cannot
report bug
Status in gnome-shell package in Ubuntu:
Invalid
Bug description:
A new day, a new struggle with Ubuntu 22.04.
So, I decided to get my daily updates and in the middle of the process the
system just crashed, leaving me at the login page. When I got back, the wifi
was no longer there and the network configuration was reporting an error about
the network manager having problems.
I shut down and restarted, the wifi came back.
Went to the var/crash folder to report the bug with
$:/var/crash$ ubuntu-bug _usr_bin_gnome-shell.1000.crash
and it started complaining about older packages that need to be
upgraded. I run `apt upgrade`, one of the packages is `dbus`, I tried
`apt install dbus` and another even uglier crash that left me with a
black screen from which I could only come back with a forced shutdown
and restart.
Now, how do I get out of this mess and report the bug?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1961910/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990689] [NEW] Cannot connect to Google account after upgrading to 22.04 LTS
You have been subscribed to a public bug: After upgrading from 20.04 LTS to 22.04 LTS, my Google accounts were disconnected. In the "Parameters/Online accounts" window, a double-click on each Google account opens a window indicating "authentication data expired. Please login to use this account". A click on the "Login" button opens a blank window, the only thing I can do is closing the window. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 NonfreeKernelModules: vboxnetadp vboxnetflt vboxdrv ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Sep 23 21:00:36 2022 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd quiet splash --- maybe-ubiquity InstallationDate: Installed on 2021-12-29 (268 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity Symptom: installation UpgradeStatus: Upgraded to jammy on 2022-09-11 (12 days ago) ** Affects: gnome-online-accounts (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ubiquity-18.04.14.14 wayland-session -- Cannot connect to Google account after upgrading to 22.04 LTS https://bugs.launchpad.net/bugs/1990689 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-online-accounts in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990293] Re: Cannot move file to trash, do you want to delete immediately?" on EXT4 partitions on ubuntu 22.04 et Linux Mint 21 ( trash work perfectly on ubuntu 20.04 )
Thanks for the report. > do you think this bug will be corrected soon ? or i change parent directory name of mountpoints ? Probably better off changing the parent directory name, I'm afraid. ** Changed in: glib2.0 (Ubuntu) Status: New => Triaged ** Changed in: glib2.0 (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1990293 Title: Cannot move file to trash, do you want to delete immediately?" on EXT4 partitions on ubuntu 22.04 et Linux Mint 21 ( trash work perfectly on ubuntu 20.04 ) Status in glib2.0 package in Ubuntu: Triaged Status in glib2.0 source package in Jammy: New Bug description: Hi , when i delete a file where is in another partition than " / " or mounted in /media/ , i obtain the message in title. how can i use trash again please ? iznobe@iznobe-PC:~$ cat /etc/fstab # /etc/fstab: static file system information. # # Use 'blkid' to print the universally unique identifier for a # device; this may be used with UUID= as a more robust way to name devices # that works even if disks are added and removed. See fstab(5). # # # / was on /dev/nvme0n1p2 during installation UUID=eb18366b-2ac9-4a7e-8f93-ba2caa30e90e / ext4 noatime,errors=remount-ro 0 1 # /boot/efi was on /dev/nvme0n1p1 during installation UUID=C071-9050/boot/efi vfatdefaults0 0 # swap was on /dev/sdc3 during installation UUID=61218fe2-0bd1-4ada-9dd3-5ec996a02456 noneswap sw,pri=10 0 # partition de données separée comune aux OS linux UUID=01c9b796-0869-4ff9-a2a1-6c0f56ed5257 /datas ext4 defaults0 0 LABEL=WD8 /Vidéos/WD8 ext4 defaults0 0 #/dev/disk/by-label/WD8PRO2 /media/WD8PRO2 ext4 defaults0 0 LABEL=WD8PRO2 /Vidéos/WD8PRO2 ext4defaults 0 0 LABEL=WD8PRO1 /media/WD8PRO1 ext4 defaults0 0 LABEL=Seagate_4T /media/Seagate_4T ext4 defaults,noauto 0 0 trash is working for filesysteme mounted on /media/WD8PRO1 but not in FS mounted on /Vidéos/WD8PRO2 and /Vidéos/WD8 using ubuntu 22.04.1 LTS . Exactly same file systeme mounted on same directory , with same trash directory is working fine on ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1990293/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990263] Re: bamfdaemon crashes with libwnck3 43.0-1
This bug was fixed in the package libwnck3 - 43.0-2 --- libwnck3 (43.0-2) unstable; urgency=medium * Add a patch to fix segfault in invalidate_icons. (Closes: #1020262) (LP: #1990263) -- Dmitry Shachnev Fri, 23 Sep 2022 00:16:49 +0300 ** Changed in: libwnck3 (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libwnck3 in Ubuntu. https://bugs.launchpad.net/bugs/1990263 Title: bamfdaemon crashes with libwnck3 43.0-1 Status in libwnck3 package in Ubuntu: Fix Released Status in libwnck3 package in Debian: Fix Released Bug description: bamfdaemon crashes with libwnck3 43.0-1 Thread 1 "bamfdaemon" received signal SIGSEGV, Segmentation fault. 0x77e10616 in invalidate_icons (self=0x5581da30) at ../libwnck/wnck-handle.c:81 81../libwnck/wnck-handle.c: Datei oder Verzeichnis nicht gefunden. (gdb) bt #0 0x77e10616 in invalidate_icons (self=0x5581da30) at ../libwnck/wnck-handle.c:81 #1 0x555713ca in bamf_legacy_screen_get_default () at ./src/bamf-legacy-screen.c:591 #2 0x5557b695 in bamf_legacy_screen_get_default () at ./src/bamf-matcher.c:3192 #3 bamf_matcher_init (self=0x55868140) at ./src/bamf-matcher.c:3137 #4 0x77204791 in g_type_create_instance () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #5 0x771eb8cf in () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #6 0x771ed118 in g_object_new_with_properties () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #7 0x771edec1 in g_object_new () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #8 0x5557b758 in bamf_matcher_get_default () at ./src/bamf-matcher.c:3290 #9 0x55574861 in bamf_on_bus_acquired (connection=0x55628000, name=, self=0x55697320) at ./src/bamf-daemon.c:59 #10 0x7733b905 in () at /lib/x86_64-linux-gnu/libgio-2.0.so.0 #11 0x772da559 in () at /lib/x86_64-linux-gnu/libgio-2.0.so.0 #12 0x772da783 in () at /lib/x86_64-linux-gnu/libgio-2.0.so.0 #13 0x77337e22 in () at /lib/x86_64-linux-gnu/libgio-2.0.so.0 #14 0x772da559 in () at /lib/x86_64-linux-gnu/libgio-2.0.so.0 #15 0x772da59d in () at /lib/x86_64-linux-gnu/libgio-2.0.so.0 #16 0x770e33bf in g_main_context_dispatch () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #17 0x77138098 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #18 0x770e2a6f in g_main_loop_run () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #19 0x5556c43b in main (argc=, argv=) at ./src/main.c:65 Happens when running gnome-xorg/x11 session under gnome-shell 43.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libwnck3/+bug/1990263/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1987976] Re: firefox black window
This affects me too. Memory: 4.0 GiB Processor: Intel® Celeron(R) N4000 CPU @ 1.10GHz × 2 Graphics: Mesa Intel® UHD Graphics 600 (GLK 2) Disk Capacity: 128.0 GB OS Name: Ubuntu 22.04.1 LTS OS Type: 64-bit GNOME Version: 42.4 Windowing System: Wayland -- 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/1987976 Title: firefox black window Status in Mozilla Firefox: New Status in firefox package in Ubuntu: Confirmed Bug description: nicolas@nicolas-fixe:~$ lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 nicolas@nicolas-fixe:~$ apt-cache policy firefox firefox: Installé : 1:1snap1-0ubuntu2 Candidat : 1:1snap1-0ubuntu2 Table de version : *** 1:1snap1-0ubuntu2 500 500 http://fr.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status When I boot Ubuntu and start Firefox, the Firefox's window is totally black. See attachment. I am at your disposal to answer any question you have. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox 1:1snap1-0ubuntu2 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 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Aug 28 12:42:29 2022 InstallationDate: Installed on 2022-08-25 (2 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash Snap.Changes: aucun changement trouvé SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1987976/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1989359] Re: [UIFe] Kinetic wallpapers updates
This bug was fixed in the package ubuntustudio-look - 22.10.2 --- ubuntustudio-look (22.10.2) kinetic; urgency=medium * Fix typo in .install file ubuntustudio-look (22.10.1) kinetic; urgency=medium * New Kinetic Kudu Wallpapers (LP: #1989359) -- Erich Eickmeyer Thu, 22 Sep 2022 20:59:00 -0700 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-wallpapers in Ubuntu. https://bugs.launchpad.net/bugs/1989359 Title: [UIFe] Kinetic wallpapers updates Status in ubuntu-mate-artwork package in Ubuntu: Fix Released Status in ubuntu-unity-backgrounds package in Ubuntu: Fix Released Status in ubuntu-wallpapers package in Ubuntu: In Progress Status in ubuntustudio-default-settings package in Ubuntu: Fix Released Status in ubuntustudio-look package in Ubuntu: Fix Released Bug description: The Canonical design team isn't going to have the new default wallpapers ready by UIF but target end of September so we are requesting an exception to upload those once they are available. The community wallpapers are also going to be available after UIF since the competition was not organized early enough https://discourse.ubuntu.com/t/kinetic-kudu-22-10-wallpaper-competition The results will be published on Sep 23th so we ask for permission to refresh our package with the new content by the next monday (26th) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-mate-artwork/+bug/1989359/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1989359] Re: [UIFe] Kinetic wallpapers updates
This bug was fixed in the package ubuntustudio-default-settings - 22.10.5 --- ubuntustudio-default-settings (22.10.5) kinetic; urgency=medium * Point to new default wallpaper for kinetic (LP: #1989359) -- Erich Eickmeyer Fri, 23 Sep 2022 09:20:51 -0700 ** Changed in: ubuntustudio-default-settings (Ubuntu) Status: Fix Committed => Fix Released ** Changed in: ubuntustudio-look (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-wallpapers in Ubuntu. https://bugs.launchpad.net/bugs/1989359 Title: [UIFe] Kinetic wallpapers updates Status in ubuntu-mate-artwork package in Ubuntu: Fix Released Status in ubuntu-unity-backgrounds package in Ubuntu: Fix Released Status in ubuntu-wallpapers package in Ubuntu: In Progress Status in ubuntustudio-default-settings package in Ubuntu: Fix Released Status in ubuntustudio-look package in Ubuntu: Fix Released Bug description: The Canonical design team isn't going to have the new default wallpapers ready by UIF but target end of September so we are requesting an exception to upload those once they are available. The community wallpapers are also going to be available after UIF since the competition was not organized early enough https://discourse.ubuntu.com/t/kinetic-kudu-22-10-wallpaper-competition The results will be published on Sep 23th so we ask for permission to refresh our package with the new content by the next monday (26th) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-mate-artwork/+bug/1989359/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1964036] Re: Firefox icon missing from panel following Kubuntu upgrade 20.04->22.04
** Changed in: ubuntu-release-upgrader (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1964036 Title: Firefox icon missing from panel following Kubuntu upgrade 20.04->22.04 Status in firefox package in Ubuntu: Confirmed Status in ubuntu-release-upgrader package in Ubuntu: Confirmed Bug description: 1) lsb_release -rd Description:Ubuntu Jammy Jellyfish (development branch) Release:22.04 (Kubuntu Jammy live session in QEMU VM) 2) apt-cache policy ubuntu-release-upgrader-core ubuntu-release-upgrader-core: Installed: 1:22.04.6 3) expected (upgrade from Kubuntu 20.04.3 -> 22.04. Reboot.) * Firefox icon on panel to be intact. * Clicked icon launches browser. * Icon tooltip/mouse hover to describe application. 4) happened instead * Icon is missing/replaced with a generic icon * Icon click produces error notification "Plasma Workspace - preferred://browser" * Icon tooltip/mouse hover appears, though is blank. Additional info: * firefox is still installed, works as expected. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-03-07 (2 days ago) InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819.1) Package: ubuntu-release-upgrader (not installed) ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Tags: jammy dist-upgrade Uname: Linux 5.15.0-18-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-03-07 (2 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1964036/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1989359] Re: [UIFe] Kinetic wallpapers updates
We have already uploaded the new Ubuntu Unity wallpapers to proposed (ubuntu-unity-backgrounds), and they should be present in today's ISO build if there aren't any issues with transition of packages in proposed to universe today. ** Also affects: ubuntu-unity-backgrounds (Ubuntu) Importance: Undecided Status: New ** Changed in: ubuntu-unity-backgrounds (Ubuntu) Status: New => Fix Released ** Changed in: ubuntu-unity-backgrounds (Ubuntu) Assignee: (unassigned) => Rudra Saraswat (rs2009) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-wallpapers in Ubuntu. https://bugs.launchpad.net/bugs/1989359 Title: [UIFe] Kinetic wallpapers updates Status in ubuntu-mate-artwork package in Ubuntu: Fix Released Status in ubuntu-unity-backgrounds package in Ubuntu: Fix Released Status in ubuntu-wallpapers package in Ubuntu: In Progress Status in ubuntustudio-default-settings package in Ubuntu: Fix Committed Status in ubuntustudio-look package in Ubuntu: Fix Committed Bug description: The Canonical design team isn't going to have the new default wallpapers ready by UIF but target end of September so we are requesting an exception to upload those once they are available. The community wallpapers are also going to be available after UIF since the competition was not organized early enough https://discourse.ubuntu.com/t/kinetic-kudu-22-10-wallpaper-competition The results will be published on Sep 23th so we ask for permission to refresh our package with the new content by the next monday (26th) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-mate-artwork/+bug/1989359/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990263] Re: bamfdaemon crashes with libwnck3 43.0-1
Removing block-proposed tag since the fix is in -proposed now. ** Tags removed: block-proposed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libwnck3 in Ubuntu. https://bugs.launchpad.net/bugs/1990263 Title: bamfdaemon crashes with libwnck3 43.0-1 Status in libwnck3 package in Ubuntu: Triaged Status in libwnck3 package in Debian: Fix Released Bug description: bamfdaemon crashes with libwnck3 43.0-1 Thread 1 "bamfdaemon" received signal SIGSEGV, Segmentation fault. 0x77e10616 in invalidate_icons (self=0x5581da30) at ../libwnck/wnck-handle.c:81 81../libwnck/wnck-handle.c: Datei oder Verzeichnis nicht gefunden. (gdb) bt #0 0x77e10616 in invalidate_icons (self=0x5581da30) at ../libwnck/wnck-handle.c:81 #1 0x555713ca in bamf_legacy_screen_get_default () at ./src/bamf-legacy-screen.c:591 #2 0x5557b695 in bamf_legacy_screen_get_default () at ./src/bamf-matcher.c:3192 #3 bamf_matcher_init (self=0x55868140) at ./src/bamf-matcher.c:3137 #4 0x77204791 in g_type_create_instance () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #5 0x771eb8cf in () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #6 0x771ed118 in g_object_new_with_properties () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #7 0x771edec1 in g_object_new () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #8 0x5557b758 in bamf_matcher_get_default () at ./src/bamf-matcher.c:3290 #9 0x55574861 in bamf_on_bus_acquired (connection=0x55628000, name=, self=0x55697320) at ./src/bamf-daemon.c:59 #10 0x7733b905 in () at /lib/x86_64-linux-gnu/libgio-2.0.so.0 #11 0x772da559 in () at /lib/x86_64-linux-gnu/libgio-2.0.so.0 #12 0x772da783 in () at /lib/x86_64-linux-gnu/libgio-2.0.so.0 #13 0x77337e22 in () at /lib/x86_64-linux-gnu/libgio-2.0.so.0 #14 0x772da559 in () at /lib/x86_64-linux-gnu/libgio-2.0.so.0 #15 0x772da59d in () at /lib/x86_64-linux-gnu/libgio-2.0.so.0 #16 0x770e33bf in g_main_context_dispatch () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #17 0x77138098 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #18 0x770e2a6f in g_main_loop_run () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #19 0x5556c43b in main (argc=, argv=) at ./src/main.c:65 Happens when running gnome-xorg/x11 session under gnome-shell 43.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libwnck3/+bug/1990263/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990677] Re: Update fonts-noto-color-emoji for Unicode 15
** Tags added: jammy ** Tags added: upgrade-software-version -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fonts-noto-color-emoji in Ubuntu. https://bugs.launchpad.net/bugs/1990677 Title: Update fonts-noto-color-emoji for Unicode 15 Status in fonts-noto-color-emoji package in Ubuntu: Fix Released Status in fonts-noto-color-emoji source package in Jammy: Triaged Bug description: [Impact] Ubuntu has included Google's color emoji font by default for years. Annually, the Unicode Consortium releases a new Unicode standard with new emoji. Internet communication platforms quickly adopt the new emoji and it's important that those emoji also work on the latest Ubuntu release. Emojipedia provides a list of the emoji provided by this font. Click the Show new link to see the new emoji. Click the changed link to see other changes that were made in this release. https://emojipedia.org/google/15.0/ [Test Plan] The test plan is outlined on this wiki: https://wiki.ubuntu.com/DesktopTeam/TestPlans/EmojiFont [Where problems could occur] Sometimes there is an issue with the display of a particular font after the font has been updated. See Debian #788791 for instance. Perhaps this is a bug with font caching. To avoid this bug, it's recommended to restart your computer after applying the update. We are adding a postinst to tell Ubuntu's update-notifier to prompt the user to restart. This could technically be a User Interface Freeze change, but the new and changed emoji don't show in the Ubuntu docs or official screenshots. So there doesn't seem to be a need to notify the Docs team. There are no translations here so no need to notify the Translations team. [Other] This bug is fixed in the current development release. Fix is released: https://bugs.launchpad.net/ubuntu/+source/fonts-noto- color-emoji/+bug/1989626 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-noto-color-emoji/+bug/1990677/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1989359] Re: [UIFe] Kinetic wallpapers updates
@Seb FYI This [1] upload is in the NEW queue right now. But it refers to the old UIFe, not this one here - so I'm not accepting it right now in csae you want to fix this up. [1]: https://launchpadlibrarian.net/625301973/ubuntu- wallpapers_22.10.1-0ubuntu1_amd64.changes -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-wallpapers in Ubuntu. https://bugs.launchpad.net/bugs/1989359 Title: [UIFe] Kinetic wallpapers updates Status in ubuntu-mate-artwork package in Ubuntu: Fix Released Status in ubuntu-wallpapers package in Ubuntu: In Progress Status in ubuntustudio-default-settings package in Ubuntu: Fix Committed Status in ubuntustudio-look package in Ubuntu: Fix Committed Bug description: The Canonical design team isn't going to have the new default wallpapers ready by UIF but target end of September so we are requesting an exception to upload those once they are available. The community wallpapers are also going to be available after UIF since the competition was not organized early enough https://discourse.ubuntu.com/t/kinetic-kudu-22-10-wallpaper-competition The results will be published on Sep 23th so we ask for permission to refresh our package with the new content by the next monday (26th) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-mate-artwork/+bug/1989359/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1989359] Re: [UIFe] Kinetic wallpapers updates
** Changed in: ubuntustudio-default-settings (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-wallpapers in Ubuntu. https://bugs.launchpad.net/bugs/1989359 Title: [UIFe] Kinetic wallpapers updates Status in ubuntu-mate-artwork package in Ubuntu: Fix Released Status in ubuntu-wallpapers package in Ubuntu: In Progress Status in ubuntustudio-default-settings package in Ubuntu: Fix Committed Status in ubuntustudio-look package in Ubuntu: Fix Committed Bug description: The Canonical design team isn't going to have the new default wallpapers ready by UIF but target end of September so we are requesting an exception to upload those once they are available. The community wallpapers are also going to be available after UIF since the competition was not organized early enough https://discourse.ubuntu.com/t/kinetic-kudu-22-10-wallpaper-competition The results will be published on Sep 23th so we ask for permission to refresh our package with the new content by the next monday (26th) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-mate-artwork/+bug/1989359/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990677] Re: Update fonts-noto-color-emoji for Unicode 15
** Description changed: - Ubuntu LTS should be capable of display all current color emojis. + [Impact] - For instance, these new emojis in unicode 15.0 + Ubuntu has included Google's color emoji font by default for years. + Annually, the Unicode Consortium releases a new Unicode standard with + new emoji. Internet communication platforms quickly adopt the new emoji + and it's important that those emoji also work on the latest Ubuntu + release. + Emojipedia provides a list of the emoji provided by this font. + + Click the Show new link to see the new emoji. Click the changed link to + see other changes that were made in this release. https://emojipedia.org/google/15.0/ + + [Test Plan] + + The test plan is outlined on this wiki: + https://wiki.ubuntu.com/DesktopTeam/TestPlans/EmojiFont + + [Where problems could occur] + + Sometimes there is an issue with the display of a particular font after + the font has been updated. See Debian #788791 for instance. Perhaps this + is a bug with font caching. To avoid this bug, it's recommended to + restart your computer after applying the update. + + We are adding a postinst to tell Ubuntu's update-notifier to prompt the + user to restart. + + This could technically be a User Interface Freeze change, but the new + and changed emoji don't show in the Ubuntu docs or official screenshots. + So there doesn't seem to be a need to notify the Docs team. There are no + translations here so no need to notify the Translations team. + + [Other] + + This bug is fixed in the current development release. + + Fix is released: https://bugs.launchpad.net/ubuntu/+source/fonts-noto- + color-emoji/+bug/1989626 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fonts-noto-color-emoji in Ubuntu. https://bugs.launchpad.net/bugs/1990677 Title: Update fonts-noto-color-emoji for Unicode 15 Status in fonts-noto-color-emoji package in Ubuntu: Fix Released Status in fonts-noto-color-emoji source package in Jammy: Triaged Bug description: [Impact] Ubuntu has included Google's color emoji font by default for years. Annually, the Unicode Consortium releases a new Unicode standard with new emoji. Internet communication platforms quickly adopt the new emoji and it's important that those emoji also work on the latest Ubuntu release. Emojipedia provides a list of the emoji provided by this font. Click the Show new link to see the new emoji. Click the changed link to see other changes that were made in this release. https://emojipedia.org/google/15.0/ [Test Plan] The test plan is outlined on this wiki: https://wiki.ubuntu.com/DesktopTeam/TestPlans/EmojiFont [Where problems could occur] Sometimes there is an issue with the display of a particular font after the font has been updated. See Debian #788791 for instance. Perhaps this is a bug with font caching. To avoid this bug, it's recommended to restart your computer after applying the update. We are adding a postinst to tell Ubuntu's update-notifier to prompt the user to restart. This could technically be a User Interface Freeze change, but the new and changed emoji don't show in the Ubuntu docs or official screenshots. So there doesn't seem to be a need to notify the Docs team. There are no translations here so no need to notify the Translations team. [Other] This bug is fixed in the current development release. Fix is released: https://bugs.launchpad.net/ubuntu/+source/fonts-noto- color-emoji/+bug/1989626 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-noto-color-emoji/+bug/1990677/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990677] Re: Update fonts-noto-color-emoji for Unicode 15
** Changed in: fonts-noto-color-emoji (Ubuntu) Status: New => Fix Released ** Also affects: fonts-noto-color-emoji (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: fonts-noto-color-emoji (Ubuntu Jammy) Status: New => Triaged ** Changed in: fonts-noto-color-emoji (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: fonts-noto-color-emoji (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fonts-noto-color-emoji in Ubuntu. https://bugs.launchpad.net/bugs/1990677 Title: Update fonts-noto-color-emoji for Unicode 15 Status in fonts-noto-color-emoji package in Ubuntu: Fix Released Status in fonts-noto-color-emoji source package in Jammy: Triaged Bug description: [Impact] Ubuntu has included Google's color emoji font by default for years. Annually, the Unicode Consortium releases a new Unicode standard with new emoji. Internet communication platforms quickly adopt the new emoji and it's important that those emoji also work on the latest Ubuntu release. Emojipedia provides a list of the emoji provided by this font. Click the Show new link to see the new emoji. Click the changed link to see other changes that were made in this release. https://emojipedia.org/google/15.0/ [Test Plan] The test plan is outlined on this wiki: https://wiki.ubuntu.com/DesktopTeam/TestPlans/EmojiFont [Where problems could occur] Sometimes there is an issue with the display of a particular font after the font has been updated. See Debian #788791 for instance. Perhaps this is a bug with font caching. To avoid this bug, it's recommended to restart your computer after applying the update. We are adding a postinst to tell Ubuntu's update-notifier to prompt the user to restart. This could technically be a User Interface Freeze change, but the new and changed emoji don't show in the Ubuntu docs or official screenshots. So there doesn't seem to be a need to notify the Docs team. There are no translations here so no need to notify the Translations team. [Other] This bug is fixed in the current development release. Fix is released: https://bugs.launchpad.net/ubuntu/+source/fonts-noto- color-emoji/+bug/1989626 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-noto-color-emoji/+bug/1990677/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990677] [NEW] Update fonts-noto-color-emoji for Unicode 15
Public bug reported: Ubuntu LTS should be capable of display all current color emojis. For instance, these new emojis in unicode 15.0 https://emojipedia.org/google/15.0/ ** Affects: fonts-noto-color-emoji (Ubuntu) Importance: Medium Status: Fix Released ** Affects: fonts-noto-color-emoji (Ubuntu Jammy) Importance: Medium Status: Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fonts-noto-color-emoji in Ubuntu. https://bugs.launchpad.net/bugs/1990677 Title: Update fonts-noto-color-emoji for Unicode 15 Status in fonts-noto-color-emoji package in Ubuntu: Fix Released Status in fonts-noto-color-emoji source package in Jammy: Triaged Bug description: Ubuntu LTS should be capable of display all current color emojis. For instance, these new emojis in unicode 15.0 https://emojipedia.org/google/15.0/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-noto-color-emoji/+bug/1990677/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990673] Re: Default paragraph style should be "Text body"
Launchpad has imported 41 comments from the remote bug at https://bugs.documentfoundation.org/show_bug.cgi?id=47295. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2012-03-13T16:46:28+00:00 Rūdolfs Mazurs wrote: The "Default" paragraph style is not a good idea for a default paragraph style. A "Text body" would be more suitable. Reason 1: If "Default" is used as base style for all other paragraph styles. If a user includes this style somewhere in the document and then changes it through "Edit paragraph style" context menu command, like adding first line indent, it indents all other styles. This happens quite often, almost silently, and usually breaks appearance. Reason 2: When composing text, the normal paragraphs will have style "Default", however, after the first heading, the style will change to "Text body" and stay such. It could be argued that text before any heading is not typical "Text body", but not all writers set heading styles the moment they are written, especially, if text is copied and pasted. The first problem can be solved by linking all other styled to something different than "Default" or making the default style of a new document something other than "Default" (this sounds a bit confusing). Reply at: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1990673/comments/0 On 2012-06-05T03:44:03+00:00 Sasha-libreoffice wrote: Thanks for new idea 1. Problem may be in default template, not in program itself 2. Paragraph Style dialog, tag "Organizer", field "Next style" so again, it is in template So, this all may reformulated as this: "Use different template as default" Reply at: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1990673/comments/1 On 2012-07-02T21:18:42+00:00 Jmadero-dev wrote: Can you provide a document that shows this behavior and what you mean by "breaks appearance". I'm going to mark this as NEEDINFO, once you provide the document please mark it as UNCONFIRMED and we'll take a look at it again. Thanks for your input on LO, we appreciate it :) Reply at: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1990673/comments/2 On 2013-05-26T22:32:28+00:00 Qa-admin-q wrote: Dear Bug Submitter, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INVALID due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/FDO/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team Reply at: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1990673/comments/3 On 2013-07-08T21:23:04+00:00 Qa-admin-q wrote: Dear Bug Submitter, Please read this message in its entirety before proceeding. Your bug report is being closed as INVALID due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of FDO Reply at: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1990673/comments/4 On 2017-05-29T09:53:08+00:00 Thomas-lendo wrote: I reopen this bug because I think it's worth discussing
[Desktop-packages] [Bug 1940543] Re: Show Hidden Files does not persist and even resets during the same session
I can confirm that this happens when I use File Chooser from Electron apps. The bug is described here: https://github.com/electron/electron/issues/34706 ** Bug watch added: github.com/electron/electron/issues #34706 https://github.com/electron/electron/issues/34706 -- 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/1940543 Title: Show Hidden Files does not persist and even resets during the same session Status in nautilus package in Ubuntu: Confirmed Bug description: Since 20.04 has been released, the option "Show Hidden Files" has never lasted long. It never persists over a reboot and even during the same session, it will just hide the files after some random (it seems random) interval. This happens for me on 3 different computers, all different builds. This happens on a vanilla install too. I have never been able to make "Show Hidden Files" last longer than an hourish, and never over a reboot. I work a lot in hidden files, this is mostly just frustrating to me since it happens randomly and when I am moving around a project, I have to keep toggling "Show Hidden Files" to get work done. I did have to reinstall `gnome-control-center` after a fresh install and updating Ubuntu 20.04 the latest version, I am not sure if that could help identify the issue but I have always had this issue on 20.04 so I am doubtful. I did this running: ``` sudo apt install --reinstall gnome-control-center ``` I had to reinstall this since Settings was no longer available after the system was updated (fresh install with `sudo apt update && sudo apt upgrade` is what broken it for me to have to reinstall it. I even tried using: ``` gsettings set org.gtk.Settings.FileChooser show-hidden true ``` but the issue still happens. Also, not sure why nautilus is installed, I thought 20.04 was gnome? Again, this is a fresh install (15 days old) ``` $ lsb_release -rd Description: Ubuntu 20.04.2 LTS Release: 20.04 ``` ``` $ apt-cache policy nautilus nautilus: Installed: 1:3.36.3-0ubuntu1 Candidate: 1:3.36.3-0ubuntu1 Version table: *** 1:3.36.3-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:3.36.1.1-1ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages ``` ``` apt-cache policy gnome gnome: Installed: (none) Candidate: 1:3.30+2 Version table: 1:3.30+2 500 500 http://us.archive.ubuntu.com/ubuntu focal/universe amd64 Packages ``` ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.3-0ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Aug 19 09:46:31 2021 GsettingsChanges: b'org.gnome.nautilus.window-state' b'initial-size' b'(1280, 1393)' b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'where', 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency', 'starred', 'detailed_type']" InstallationDate: Installed on 2021-08-03 (15 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1940543/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1288655] Re: Terminal height shrinks - repeatedly restored shorter than the previous height
Hm, perhaps I misremembered the tweak. I do recall that 22.04 did not work initially. I applied the dconf menu setting and it started to work. I reset the dconf legacy menu setting just now and it still works (i.e. no shrinking after maximization). So I'm mystified . . . -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1288655 Title: Terminal height shrinks - repeatedly restored shorter than the previous height Status in GNOME Terminal: New Status in gnome-terminal package in Ubuntu: Triaged Bug description: 1. Open a gnome-terminal window (from the launcher or by pressing Ctrl + Alt + T) 2. "stty -a | grep rows" reports "rows 24; columns 80;" 3. Maximize the window (by clicking on the maximize button, or double clicking the title bar, or dragging the window up to the panel) 4. Do the same again to un-maximize the window 5. Now "stty -a | grep rows" reports "rows 23; columns 79;" Each time I do this, the window keeps getting one character shorter and one character narrower! ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-terminal 3.6.1-0ubuntu6 ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3 Uname: Linux 3.11.0-17-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Thu Mar 6 10:22:46 2014 InstallationDate: Installed on 2010-04-15 (1421 days ago) InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100406.1) MarkForUpload: True SourcePackage: gnome-terminal UpgradeStatus: Upgraded to saucy on 2013-10-29 (128 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-terminal/+bug/1288655/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1940543] Re: Show Hidden Files does not persist and even resets during the same session
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nautilus (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1940543 Title: Show Hidden Files does not persist and even resets during the same session Status in nautilus package in Ubuntu: Confirmed Bug description: Since 20.04 has been released, the option "Show Hidden Files" has never lasted long. It never persists over a reboot and even during the same session, it will just hide the files after some random (it seems random) interval. This happens for me on 3 different computers, all different builds. This happens on a vanilla install too. I have never been able to make "Show Hidden Files" last longer than an hourish, and never over a reboot. I work a lot in hidden files, this is mostly just frustrating to me since it happens randomly and when I am moving around a project, I have to keep toggling "Show Hidden Files" to get work done. I did have to reinstall `gnome-control-center` after a fresh install and updating Ubuntu 20.04 the latest version, I am not sure if that could help identify the issue but I have always had this issue on 20.04 so I am doubtful. I did this running: ``` sudo apt install --reinstall gnome-control-center ``` I had to reinstall this since Settings was no longer available after the system was updated (fresh install with `sudo apt update && sudo apt upgrade` is what broken it for me to have to reinstall it. I even tried using: ``` gsettings set org.gtk.Settings.FileChooser show-hidden true ``` but the issue still happens. Also, not sure why nautilus is installed, I thought 20.04 was gnome? Again, this is a fresh install (15 days old) ``` $ lsb_release -rd Description: Ubuntu 20.04.2 LTS Release: 20.04 ``` ``` $ apt-cache policy nautilus nautilus: Installed: 1:3.36.3-0ubuntu1 Candidate: 1:3.36.3-0ubuntu1 Version table: *** 1:3.36.3-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:3.36.1.1-1ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages ``` ``` apt-cache policy gnome gnome: Installed: (none) Candidate: 1:3.30+2 Version table: 1:3.30+2 500 500 http://us.archive.ubuntu.com/ubuntu focal/universe amd64 Packages ``` ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.3-0ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Aug 19 09:46:31 2021 GsettingsChanges: b'org.gnome.nautilus.window-state' b'initial-size' b'(1280, 1393)' b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'where', 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency', 'starred', 'detailed_type']" InstallationDate: Installed on 2021-08-03 (15 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1940543/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990673] Re: Default paragraph style should be "Text body"
** Bug watch added: Document Foundation Bugzilla #47295 https://bugs.documentfoundation.org/show_bug.cgi?id=47295 ** Also affects: df-libreoffice via https://bugs.documentfoundation.org/show_bug.cgi?id=47295 Importance: Unknown Status: Unknown -- 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/1990673 Title: Default paragraph style should be "Text body" Status in LibreOffice: Unknown Status in libreoffice package in Ubuntu: New Bug description: Summary: when creating a new Writer document, the first paragraph has the style "Default Paragraph Style", which leads to surprising behaviour. This bug has been reported in upstream [1], but at least some devs seem to believe that this is a packaging issue [2] so it might make sense to be fixed in downstream. Ideally fixed in upstream as well. [1] https://bugs.documentfoundation.org/show_bug.cgi?id=47295 [2] even though this issue is seemingly present on all platforms To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1990673/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990673] [NEW] Default paragraph style should be "Text body"
Public bug reported: Summary: when creating a new Writer document, the first paragraph has the style "Default Paragraph Style", which leads to surprising behaviour. This bug has been reported in upstream [1], but at least some devs seem to believe that this is a packaging issue [2] so it might make sense to be fixed in downstream. Ideally fixed in upstream as well. [1] https://bugs.documentfoundation.org/show_bug.cgi?id=47295 [2] even though this issue is seemingly present on all platforms ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New -- 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/1990673 Title: Default paragraph style should be "Text body" Status in libreoffice package in Ubuntu: New Bug description: Summary: when creating a new Writer document, the first paragraph has the style "Default Paragraph Style", which leads to surprising behaviour. This bug has been reported in upstream [1], but at least some devs seem to believe that this is a packaging issue [2] so it might make sense to be fixed in downstream. Ideally fixed in upstream as well. [1] https://bugs.documentfoundation.org/show_bug.cgi?id=47295 [2] even though this issue is seemingly present on all platforms To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1990673/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1886653] Re: cups-pki-expired
I tried adding the option 'AllowExpiredCerts' and setting it 'true'. It did not change anything for me: The printer state is set to 'Stopped' with status message 'cups-pki-expired' as soon as I send a job. -- 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/1886653 Title: cups-pki-expired Status in cups package in Ubuntu: Confirmed Bug description: The printer always goes to stopped state in Ubuntu 20.04. Print properties window has status message saying: "cups-pki-expired". I have HP color laserjet m552, which Ubuntu discovers directly from the local network and configures automatically. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cups 2.3.1-9ubuntu1.1 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Jul 7 14:40:00 2020 InstallationDate: Installed on 2019-11-03 (247 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lpstat: device for HP_Color_LaserJet_M552_5F80BF_: implicitclass://HP_Color_LaserJet_M552_5F80BF_/ MachineType: LENOVO 81H1 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP_Color_LaserJet_M552_5F80BF_.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP_Color_LaserJet_M552_5F80BF_.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=UUID=7f92666a-65f8-485e-b998-046c2c596aa5 ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: Upgraded to focal on 2020-03-28 (100 days ago) dmi.bios.date: 08/17/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 8PCN45WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 530S-14ARR dmi.modalias: dmi:bvnLENOVO:bvr8PCN45WW:bd08/17/2018:svnLENOVO:pn81H1:pvrLenovoideapad530S-14ARR:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoideapad530S-14ARR: dmi.product.family: ideapad 530S-14ARR dmi.product.name: 81H1 dmi.product.sku: LENOVO_MT_81H1_BU_idea_FM_ideapad 530S-14ARR dmi.product.version: Lenovo ideapad 530S-14ARR dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1886653/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990669] [NEW] Sync libwnck3 43.0-2 (main) from Debian unstable (main)
Public bug reported: Please sync libwnck3 43.0-2 (main) from Debian unstable (main) Changelog entries since current kinetic version 43.0-1: libwnck3 (43.0-2) unstable; urgency=medium * Add a patch to fix segfault in invalidate_icons. (Closes: #1020262) (LP: #1990263) -- Dmitry Shachnev Fri, 23 Sep 2022 00:16:49 +0300 ** Affects: libwnck3 (Ubuntu) Importance: Wishlist Status: New ** Changed in: libwnck3 (Ubuntu) Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libwnck3 in Ubuntu. https://bugs.launchpad.net/bugs/1990669 Title: Sync libwnck3 43.0-2 (main) from Debian unstable (main) Status in libwnck3 package in Ubuntu: New Bug description: Please sync libwnck3 43.0-2 (main) from Debian unstable (main) Changelog entries since current kinetic version 43.0-1: libwnck3 (43.0-2) unstable; urgency=medium * Add a patch to fix segfault in invalidate_icons. (Closes: #1020262) (LP: #1990263) -- Dmitry Shachnev Fri, 23 Sep 2022 00:16:49 +0300 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libwnck3/+bug/1990669/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1969303] Re: "No package to remove" error when attempting to uninstall
I have the "Handbrake" (ghb) version 1.2.1 installed. The version information is from the about menu of the application. "Ubuntu Software" application shows "Handbrake" installed and reports its version as 1.5.1+ds1 which is incorrect. This is happening possibly because my Ubuntu installation is an upgrade from previous version(s). I am unable to remove "Handbrake" via the "Ubuntu Software" application. It shows "Unable to remove Handbrake: no packages to remove" when the red thrash bin icon (remove) is clicked on. The output of "apt list ghb" is empty and "sudo apt remove ghb" returns "E: Unable to locate package ghb" -- 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/1969303 Title: "No package to remove" error when attempting to uninstall Status in GNOME Software: Fix Released Status in snap-store-desktop: Fix Released Status in gnome-software package in Ubuntu: Fix Released Status in gnome-software source package in Jammy: Fix Released Bug description: [Impact] * The Ubuntu repository version of gnome-software in 22.04 does not allow a user to uninstall an application. For new users this could be be construed as disconcerting allowing only installing apps without the ability to remove those apps later if required. This SRU is applicable only to the gnome-software application installed from the repository and not the branded ubuntu-store snap that is the default in Ubuntu (but not in flavours such as Ubuntu Budgie) This fix for gnome-software has been backported from the v41 version of ubuntu's snap-store. The fixed software now checks for the status of a deb package installed - either manually installed or automatically as part of a distro install. Previously this check was not done and gnome-software defaulted to not allowing the package to be uninstalled. The new status check allows gnome-software to evaluate that the package can be uninstalled. [Test Plan] * Choose a package from the installed list in gnome-software. Click the trash icon. Note the error message that the package cannot be removed. * install gnome-software from the proposed repository. Logout and login. Repeat the trash icon click step above. This time the package can be removed. Confirm via either your distro menu or searching in GNOME Overview (if you are using gnome-software from the repository) that the application has been successfully removed. * Perform additional testing such as installing applications from the repository (change the source to "Ubuntu (deb)") and then deleting the application. * Perform additional testing such as installing applications from the snap repository (change the source to "Snap") and then deleting the application. [Where problems could occur] * The code changed is specific to 'packagekit' repos i.e. debian based repos. Thus it is sensitive to possible regressions when installing & removing apps. * The patch itself is well tested since it was backported to the ubuntu snap-store several weeks ago and has been rolled out. No adverse issues has been reported. * The risk would be that there could be additional changes to the snap-store that was not incorporated in gnome-software possibly producing different results. * The additional regression tests in the Test Plan will reveal this. [Other Info] * There is no need to backport this to Kinetic since a revised version of the patch has been upstreamed (GNOME Team) and is in the kinetic version. On a fresh install of Ubuntu 22.04, ubuntu-store won't uninstall any application If you want to uninstall a software, there is an error message : "no package to remove" No problem to uninstall this same software with synaptic for example To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1969303/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1989744] Re: KB/Mouse use causing short system freezes. Happens after resume
I can provide a Gnome System Profiler capture if that would help. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1989744 Title: KB/Mouse use causing short system freezes. Happens after resume Status in xorg-server package in Ubuntu: Incomplete Bug description: Summary: My laptop gets into a an odd state after resuming from sleep where, depending on user activity, the entire system freezes every 20 seconds for about 1/2 second. This does not happen after every resume. After upgrading to 22.04 was much less frequent than it was with 21.10. It seems that after some recent update it is happening more frequently again. Maybe one every 4 suspend/resume cycles. Normal operation can be restored by rebooting or sometimes suspending and waking. The triggering event is complex: * The pointer or pointer and keyboard must be actively used * Just typing with no mouse use will not cause it to happen. * Just moving the mouse pointer around but keeping it inside the same GUI element(a textarea for example) will not cause it * Typing for more than 20 seconds and then moving the mouse one pixel will cause it. * Moving the mouse around constantly for over 20 seconds will cause it to happen only if: a key on the keyboard was hit OR the pointer moved over a new GUI element(window border, button, even frames in a web page) * It is not application specific. The following is usually logged(not always though) when the freeze happens: ==> ~/.local/share/xorg/Xorg.1.log <== [1214998.964] (II) event5 - TPPS/2 Elan TrackPoint: SYN_DROPPED event - some input events have been lost. ==> /var/log/syslog <== Sep 15 08:23:51 krug /usr/libexec/gdm-x-session[3264]: (II) event5 - TPPS/2 Elan TrackPoint: SYN_DROPPED event - some input events have been lost. Sep 15 08:50:34 krug /usr/libexec/gdm-x-session[3264]: (II) event5 - TPPS/2 Elan TrackPoint: SYN_DROPPED event - some input events have been lost. Sep 15 08:50:07 krug /usr/libexec/gdm-x-session[3264]: (EE) client bug: timer event4 trackpoint: scheduled expiry is in the past (-317ms), your system is too slow Sep 15 08:50:07 krug /usr/libexec/gdm-x-session[3264]: (EE) client bug: timer event4 trackpoint: scheduled expiry is in the past (-301ms), your system is too slow Sep 15 08:50:07 krug /usr/libexec/gdm-x-session[3264]: (EE) client bug: timer event4 trackpoint: scheduled expiry is in the past (-288ms), your system is too slow Sep 15 08:50:07 krug /usr/libexec/gdm-x-session[3264]: (EE) client bug: timer event4 trackpoint: scheduled expiry is in the past (-278ms), your system is too slow Sep 15 08:50:07 krug /usr/libexec/gdm-x-session[3264]: (EE) WARNING: log rate limit exceeded (5 msgs per 360ms). Discarding future messages. System Information: Lenovo Thinkpad P15 Model: 20YQ-003WUS OS: Ubuntu 22.04.1 LTS Kernel: 5.15.0-46-generic ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xserver-xorg-core 2:21.1.3-2ubuntu2.1 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-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 515.65.01 Wed Jul 20 14:00:58 UTC 2022 GCC version: ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Sep 15 10:13:26 2022 DistUpgraded: 2022-06-30 16:37:37,968 DEBUG icon theme changed, re-reading DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.34, 5.15.0-43-generic, x86_64: installed virtualbox/6.1.34, 5.15.0-46-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation TigerLake-H GT1 [UHD Graphics] [8086:9a60] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo TigerLake-H GT1 [UHD Graphics] [17aa:22d8] NVIDIA Corporation GA107GLM [RTX A2000 Mobile] [10de:25b8] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo GA107GLM [RTX A2000 Mobile] [17aa:22d8] InstallationDate: Installed on 2022-03-03 (195 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) MachineType: LENOVO 20YQ003WUS ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash
[Desktop-packages] [Bug 1990526] Re: [FFe] UDI snap no longer strictly needed for WSL OOBE
Same as the other one - a bit late, but let's go with it. Approved (since it's just a seed change). ** Changed in: ubuntu-meta (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1990526 Title: [FFe] UDI snap no longer strictly needed for WSL OOBE Status in ubuntu-meta package in Ubuntu: Triaged Bug description: Ubuntu Desktop Installer (UDI, for short) package implementing the WSL OOBE has been ported to Windows and the WSL application is able to launch the OOBE running as a native Win32 application, instead of relying on WSLg to display the OOBE. That implies in the possibility of replacing UDI by Subiquity snap, which results in a smaller rootfs image (besides an enhanced experience due native rendering on graphics - instead of depending on RDP as it is currently with the OOBE running inside Ubuntu). Fixing this would require: - replace UDI by Subiquity snaps in the WSL seed; - updating the wsl-setup package to the latest upstream (which is able to mount and launch Subiquity from its snap) LP: #1990426 . Following the approach above won't have effects outside of WSL. Kinetic being not an LTS is a good release to receive the fix for this first, as it affects a small audience of Ubuntu WSL community, giving us time to learn from them before backporting this to Jammy early next cycle. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1990526/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990423] Re: gnome-shell >> 43
I'm having the same problem. I checked and the extension itself has support for GNOME 43, that's just a problem with package relationship (depends on). -- 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/1990423 Title: gnome-shell >> 43 Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Bug description: Wondering if will it be still supported for gnome-shell version 43 and above? especially in kinetic kudu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1990423/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990423] Re: gnome-shell >> 43
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1990423 Title: gnome-shell >> 43 Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Bug description: Wondering if will it be still supported for gnome-shell version 43 and above? especially in kinetic kudu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1990423/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1988484]
I can't find it anymore, sorry. :/ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1988484 Title: Holding down volume keys sometimes crashes xorg Status in X.Org X server: Won't Fix Status in xorg-server package in Ubuntu: New Bug description: Running KDE 5.24.4 on Ubuntu Jammy. On a few occasions, I've been able to trigger a complete desktop crash by pressing and holding the volume keys on my laptop. Steps to reproduce: 1) Have something play audio - typically youtube in a browser 2) Hold down Fn+F3 or Fn+F2 to increase/decrease volume. Crash. More information: You may find more detail in crashes from this machine at https://errors.ubuntu.com/user/39741994cfebc02a360b6373cda1e148b8bca640b31a1aec7727d4862d5bbdf25251b0221ae0686ac25e1f415fd9a5a73a8a95d904dac3ba9a31985bb2ec824d The last time this happened was a week or so back - here's the crash report https://errors.ubuntu.com/oops/8bd96e8c-2540-11ed-97b9-fa163e993415 Todays crash hasn't finished being processed yet so I can't link to it. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xserver-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: unknown CompositorRunning: None CurrentDesktop: KDE Date: Thu Sep 1 23:16:03 2022 DistUpgraded: 2022-03-29 22:59:20,069 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: akvcam/1.2.2, 5.13.0-30-generic, x86_64: installed akvcam/1.2.2, 5.13.0-37-generic, x86_64: installed akvcam/1.2.2, 5.15.0-43-generic, x86_64: installed akvcam/1.2.2, 5.15.0-46-generic, x86_64: installed akvcam/1.2.2, 5.15.0-47-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 5500 [17aa:5034] InstallationDate: Installed on 2020-06-11 (812 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20BV001BUK ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-46-generic root=/dev/mapper/vgubuntu-root ro quiet splash intel_idle.max_cstate=4 vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: xorg UpgradeStatus: Upgraded to jammy on 2022-03-29 (156 days ago) dmi.bios.date: 08/14/2019 dmi.bios.release: 1.37 dmi.bios.vendor: LENOVO dmi.bios.version: JBET73WW (1.37 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BV001BUK dmi.board.vendor: LENOVO dmi.board.version: 0B98417 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.4 dmi.modalias: dmi:bvnLENOVO:bvrJBET73WW(1.37):bd08/14/2019:br1.37:efr1.4:svnLENOVO:pn20BV001BUK:pvrThinkPadT450:rvnLENOVO:rn20BV001BUK:rvr0B98417WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20BV_BU_Think_FM_ThinkPadT450: dmi.product.family: ThinkPad T450 dmi.product.name: 20BV001BUK dmi.product.sku: LENOVO_MT_20BV_BU_Think_FM_ThinkPad T450 dmi.product.version: ThinkPad T450 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.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.5-0ubuntu0.1 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-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1988484/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990382] Re: [BPO] libreoffice 7.3.6 for bionic
** Changed in: libreoffice (Ubuntu Bionic) Status: In Progress => Fix Committed -- 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/1990382 Title: [BPO] libreoffice 7.3.6 for bionic Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Bionic: Fix Committed Bug description: [Impact] * LibreOffice 7.3.6 is in its sixth bugfix release of the 7.3 line: https://wiki.documentfoundation.org/ReleasePlan/7.3#7.3.6_release * This source packages matches the processed SRU for jammy handled at https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1988744 and a test build is currently available at https://launchpad.net/~libreoffice/+archive/ubuntu/experimental/+packages * Similar backport of 7.3.6 for focal handled at https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1989418 * LibreOffice 6.0.7 (EOL since November 26, 2018) is currently released in bionic. [Scope] * Backport of https://launchpad.net/ubuntu/+source/libreoffice/1:7.3.6-0ubuntu0.22.04.1 * Backport target is Bionci/18.04 LTS only to provide an official build of a more recent upstream version of LibreOffice [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_73/1900/ * More information about the upstream QA testing can be found here: * Automated tests https://wiki.documentfoundation.org/QA/Testing/Automated_Tests * Automated UI tests https://wiki.documentfoundation.org/Development/UITests * Regression tests https://wiki.documentfoundation.org/QA/Testing/Regression_Tests * Feature tests https://wiki.documentfoundation.org/QA/Testing/Feature_Tests * Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing. * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-bionic-libreoffice-experimental/bionic/amd64/libr/libreoffice/20220921_023821_f6636@/log.gz * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-bionic-libreoffice-experimental/bionic/arm64/libr/libreoffice/20220921_015824_12ef6@/log.gz * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-bionic-libreoffice-experimental/bionic/armhf/libr/libreoffice/20220922_104328_3c444@/log.gz * [i386] https://autopkgtest.ubuntu.com/results/autopkgtest-bionic-libreoffice-experimental/bionic/i386/libr/libreoffice/20220921_150152_8877b@/log.gz * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-bionic-libreoffice-experimental/bionic/ppc64el/libr/libreoffice/20220921_140441_6e26b@/log.gz * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-bionic-libreoffice-experimental/bionic/s390x/libr/libreoffice/20220921_134627_506c7@/log.gz * General smoke testing of all the applications in the office suite were carried out by going through the manual testplan as documented by: https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice [Regression Potential] * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1990382/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1852911] Re: CriticalPowerAction=Suspend should be supported
I have found a (dirty?) workaround for this. The idea is simple: use a
udev rule to suspend the laptop before UPower shuts it down. This can be
done by creating a file /etc/udev/rules.d/99-lowbat.rules with the
following content:
# Suspend the system when battery level drops to 5% or lower
SUBSYSTEM=="power_supply", ATTR{status}=="Discharging",
ATTR{capacity}=="[0-5]", RUN+="/usr/bin/systemctl suspend"
You can of course tune the threshold.
This method seems to work well for me. If you want to use a threshold
that's lower than the UPower one, *I think* you could set the
PercentageAction parameter to 0% or 1% in /etc/UPower/UPower.conf,
although I'm not 100% sure this is a good idea (the disclaimer at the
beginning of the file seems to discourage users from directly modifying
the file).
Reference:
https://wiki.archlinux.org/title/laptop#Hibernate_on_low_battery_level
On a side note, I definitely wish this bug could be addressed. It's not normal
that a computer just shuts down and makes you lose your work when there's still
battery. Also note that afaik there's currently no way to enable hibernation
with full disk encryption, so this limitation of UPower will become
increasingly serious as more and more users will make the (right) choice to use
FDE.
--
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/1852911
Title:
CriticalPowerAction=Suspend should be supported
Status in Upower:
New
Status in upower package in Ubuntu:
Triaged
Bug description:
The action to take when the battery is critical can only be one of the
following:
# Possible values are:
# PowerOff
# Hibernate
# HybridSleep
Adding Suspend to that list makes perfect sense. My laptop is
currently powering off on low power which is useless as I'll be losing
my work anyway. Might as well suspend and allow me to notice that and
connect a charger. If the thinking is that suspend uses power I can
set a high enough threshold to give me some margin.
The failovers are:
# If HybridSleep isn't available, Hibernate will be used
# If Hibernate isn't available, PowerOff will be used
I'd argue Suspend should actually come before PowerOff in that list.
For most laptop users having their computer suspend because they
didn't notice the battery was running out is very easy to fix and
takes no time. They'll just connect the charger. If however the
computer needs to be completely rebooted, not only does that take a
lot more time it will very likely cause lost work.
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: upower 0.99.10-1
ProcVersionSignature: Ubuntu 5.0.0-32.34-generic 5.0.21
Uname: Linux 5.0.0-32-generic x86_64
ApportVersion: 2.20.10-0ubuntu27.3
Architecture: amd64
CurrentDesktop: Unity
Date: Sun Nov 17 14:32:13 2019
InstallationDate: Installed on 2019-05-09 (191 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
SourcePackage: upower
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/upower/+bug/1852911/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990207] Re: "Night Light unavailable" in Settings (but the quick settings toggle for it works)
** Changed in: gnome-control-center Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1990207 Title: "Night Light unavailable" in Settings (but the quick settings toggle for it works) Status in gnome-control-center: Fix Released Status in Mutter: Fix Released Status in gnome-control-center package in Ubuntu: Invalid Status in mutter package in Ubuntu: Fix Committed Bug description: "Night Light unavailable" in Settings (but the quick settings toggle for it works). To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1990207/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1288655] Re: Terminal height shrinks - repeatedly restored shorter than the previous height
@martin-weinberg-5 I tried the dconf write as you suggested, and I did alt-F2 and "r" to restart Gnome, but it doesn't seem to have changed anything. ***As I wrote the above, I remembered that I'd left some terminal windows open during the process. I've re-tested but closed all windows before restarting Gnome and it *does* resolve the problem. However, I now have a menu bar on all my terminal windows. (screen grab attached for the benefit of others). For the moment, I'll reset that entry: dconf reset /org/gnome/terminal/legacy/headerbar ..but hopefully that will help a little in figuring out where the underlying bug is. ** Attachment added: "Screenshot of gnome terminal with headerbar set to @mb false via dconf" https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1288655/+attachment/5618395/+files/Screenshot%20from%202022-09-23%2012-21-45.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1288655 Title: Terminal height shrinks - repeatedly restored shorter than the previous height Status in GNOME Terminal: New Status in gnome-terminal package in Ubuntu: Triaged Bug description: 1. Open a gnome-terminal window (from the launcher or by pressing Ctrl + Alt + T) 2. "stty -a | grep rows" reports "rows 24; columns 80;" 3. Maximize the window (by clicking on the maximize button, or double clicking the title bar, or dragging the window up to the panel) 4. Do the same again to un-maximize the window 5. Now "stty -a | grep rows" reports "rows 23; columns 79;" Each time I do this, the window keeps getting one character shorter and one character narrower! ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-terminal 3.6.1-0ubuntu6 ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3 Uname: Linux 3.11.0-17-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Thu Mar 6 10:22:46 2014 InstallationDate: Installed on 2010-04-15 (1421 days ago) InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100406.1) MarkForUpload: True SourcePackage: gnome-terminal UpgradeStatus: Upgraded to saucy on 2013-10-29 (128 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-terminal/+bug/1288655/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1983778] Re: Major security issue in Ubuntu Desktop default config - Removable Media
I personally don't think the reasons you've listed above are good enough to change the default setting, but please file a bug with the upstream project and you can convince them to change them: https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues Once you've filed a bug with the GNOME project, please paste the bug number here. Thanks! ** Changed in: gnome-control-center (Ubuntu) Status: Incomplete => Confirmed ** Changed in: gnome-control-center (Ubuntu) Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1983778 Title: Major security issue in Ubuntu Desktop default config - Removable Media Status in gnome-control-center package in Ubuntu: Confirmed Bug description: There is a MAJOR SECURITY VULNERABILITY in Ubuntu Desktop since release 18.04 ! Recently I used Ubuntu 22.04 LTS and noticed that the issue still exist! I don’t know the reason for it, but default values for “Removable Media” are VERY Risky! It will automatically run the software which is attached to the removable media. Why? Why has Ubuntu still didn’t disable that option? The following is the default configuration (the “bad” configuration): https://imgur.com/XXXQlV2 The following is the configuration which Ubuntu should be having (it is the fix to the problem): https://imgur.com/a/0JeM6ve Please change the default configurations for Ubuntu! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1983778/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1776800] Re: Unable to start snap applications if user's home directory is not /home/$USER
Small update: we have now merged a change that allows snaps to work on system where the users' home directories are not /home// but /home///https://bugs.launchpad.net/snapd/+bug/1620771 instead. -- 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/1776800 Title: Unable to start snap applications if user's home directory is not /home/$USER Status in snapd: In Progress Status in chromium-browser package in Ubuntu: Confirmed Status in firefox package in Ubuntu: Confirmed Status in lxd package in Ubuntu: Confirmed Bug description: Users with home directories in /home/$USER can run snap application, but users in /home/users/$USER can't. nate@WorkstationC:~$ snap --version snap2.32.8+18.04 snapd 2.32.8+18.04 series 16 ubuntu 18.04 kernel 4.15.0-22-generic nate@WorkstationC:~$ echo $HOME /home/users/nate nate@WorkstationC:~$ which hello-world /snap/bin/hello-world nate@WorkstationC:~$ hello-world cannot create nate data directory: /home/users/nate/snap/hello-world/27: Permission denied To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1776800/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990384] Re: Super + L doesn't work
I can confirm what you said. However, I didn't have this problem after installing my Ubuntu. It started randomly (probably after an update). Is there a solution to it, other than reinstalling my Ubuntu? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1990384 Title: Super + L doesn't work Status in gnome-screensaver package in Ubuntu: Confirmed Bug description: Neither does changing the shortkey to the lockscreen. In the journalctl I get this: Couldn't lock screen: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: GDBus.Error:org.freedesktop.DBuscreen: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.Shell.ScreenShield was not provided by any .service fError.ServiceUnknown: The name org.gnome.Shell.ScreenShield was not provided by any .service files ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-screensaver 3.6.1-13ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 21 12:04:17 2022 GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None GsettingsGnomeSession: org.gnome.desktop.session idle-delay uint32 300 org.gnome.desktop.session session-name 'ubuntu' InstallationDate: Installed on 2022-08-16 (35 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: gnome-screensaver UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1990384/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990444] Re: firefox snap took 20 minutes to update
That's fair enough, the problem appeared as being with firefox itself, even though the underlying cause was the outage of the snap store services. I'm not really sure how the user experience could be improved in case of an outage. I'm opening a snapd task for this bug though, let's see what the snapd team thinks about this kind of situation (which I agree is very puzzling and a bad experience from a user perspective). ** Also affects: snapd 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/1990444 Title: firefox snap took 20 minutes to update Status in snapd: New Status in firefox package in Ubuntu: Invalid Bug description: I logged and firefox was unavailable, no indication of update, nothing. When I tried to launch firefox I was invited to install it BUT I klnow it's installed, so I tried to install it but it said to me I needed to 'snap refresh', I tried to snap refresh but it indicated that everything was up to date. I tried to uninstall/reinstall the firefox snap and at this moment, I got the indication that the update was in progress since 15 MINUTES ! Then I tried to remove the snap because I was sure it's bugged : in 20.04 firefox never took more than 2 mins to update and my machine BUT after 20 minutes firefox launched... wtf ? I'm an ubuntu user since circa 2005 and I believe firefox was already the default browser then, this is the worse user experience I've ever had. 1/ I never selected auto-update, let me update when I want : being blocked 15 MINUTES by the OS is not a good user experience, I know this is accepted by Windows users but I prefer to use Ubuntu 2/ If you want to update tell me you're updating not that the application is not installed : really not a good idea if you want your users to trust you I've waited 6 months after 22.04 release to migrate from 20.04 because I don't want to have this kind of bugs, I hope you do something really quick because this is not at the level of quality expected by your users. To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1990444/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990263] Re: bamfdaemon crashes with libwnck3 43.0-1
** Changed in: libwnck3 (Debian) Status: Unknown => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libwnck3 in Ubuntu. https://bugs.launchpad.net/bugs/1990263 Title: bamfdaemon crashes with libwnck3 43.0-1 Status in libwnck3 package in Ubuntu: Triaged Status in libwnck3 package in Debian: Fix Released Bug description: bamfdaemon crashes with libwnck3 43.0-1 Thread 1 "bamfdaemon" received signal SIGSEGV, Segmentation fault. 0x77e10616 in invalidate_icons (self=0x5581da30) at ../libwnck/wnck-handle.c:81 81../libwnck/wnck-handle.c: Datei oder Verzeichnis nicht gefunden. (gdb) bt #0 0x77e10616 in invalidate_icons (self=0x5581da30) at ../libwnck/wnck-handle.c:81 #1 0x555713ca in bamf_legacy_screen_get_default () at ./src/bamf-legacy-screen.c:591 #2 0x5557b695 in bamf_legacy_screen_get_default () at ./src/bamf-matcher.c:3192 #3 bamf_matcher_init (self=0x55868140) at ./src/bamf-matcher.c:3137 #4 0x77204791 in g_type_create_instance () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #5 0x771eb8cf in () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #6 0x771ed118 in g_object_new_with_properties () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #7 0x771edec1 in g_object_new () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #8 0x5557b758 in bamf_matcher_get_default () at ./src/bamf-matcher.c:3290 #9 0x55574861 in bamf_on_bus_acquired (connection=0x55628000, name=, self=0x55697320) at ./src/bamf-daemon.c:59 #10 0x7733b905 in () at /lib/x86_64-linux-gnu/libgio-2.0.so.0 #11 0x772da559 in () at /lib/x86_64-linux-gnu/libgio-2.0.so.0 #12 0x772da783 in () at /lib/x86_64-linux-gnu/libgio-2.0.so.0 #13 0x77337e22 in () at /lib/x86_64-linux-gnu/libgio-2.0.so.0 #14 0x772da559 in () at /lib/x86_64-linux-gnu/libgio-2.0.so.0 #15 0x772da59d in () at /lib/x86_64-linux-gnu/libgio-2.0.so.0 #16 0x770e33bf in g_main_context_dispatch () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #17 0x77138098 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #18 0x770e2a6f in g_main_loop_run () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #19 0x5556c43b in main (argc=, argv=) at ./src/main.c:65 Happens when running gnome-xorg/x11 session under gnome-shell 43.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libwnck3/+bug/1990263/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990646] [NEW] Report a bug
Public bug reported: Report a bug ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-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 Sep 23 12:17:07 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company UHD Graphics 620 [103c:8544] InstallationDate: Installed on 2022-09-23 (0 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:b00a Realtek Semiconductor Corp. Realtek Bluetooth 4.2 Adapter Bus 001 Device 003: ID 04ca:7092 Lite-On Technology Corp. HP TrueVision HD Camera Bus 001 Device 002: ID 3044:eac6 MIIIW MIIIW USB Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Laptop 14-df0xxx ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=f923f152-9747-4348-b5c2-f8d1f6320e44 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/23/2021 dmi.bios.release: 15.64 dmi.bios.vendor: Insyde dmi.bios.version: F.64 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8544 dmi.board.vendor: HP dmi.board.version: KBC Version 74.37 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 74.37 dmi.modalias: dmi:bvnInsyde:bvrF.64:bd07/23/2021:br15.64:efr74.37:svnHP:pnHPLaptop14-df0xxx:pvrType1ProductConfigId:rvnHP:rn8544:rvrKBCVersion74.37:cvnHP:ct10:cvrChassisVersion:sku4XN68UA#ABA: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 14-df0xxx dmi.product.sku: 4XN68UA#ABA dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.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-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ubuntu 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/1990646 Title: Report a bug Status in xorg package in Ubuntu: New Bug description: Report a bug ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-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 Sep 23 12:17:07 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company UHD Graphics 620 [103c:8544] InstallationDate: Installed on 2022-09-23 (0 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:b00a Realtek Semiconductor Corp. Realtek Bluetooth 4.2 Adapter Bus 001 Device 003: ID 04ca:7092 Lite-On Technology Corp. HP TrueVision HD Camera Bus 001 Device 002: ID 3044:eac6 MIIIW MIIIW USB Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Laptop 14-df0xxx ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=f923f152-9747-4348-b5c2-f8d1f6320e44 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/23/2021 dmi.bios.release: 15.64 dmi.bios.vendor: Insyde dmi.bios.version: F.64 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8544 dmi.board.vendor: HP dmi.board.version: KBC Version 74.37 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 74.37 dmi.modalias:
[Desktop-packages] [Bug 1990647] [NEW] Report a bug
Public bug reported: Report a bug ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-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 Sep 23 12:17:07 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company UHD Graphics 620 [103c:8544] InstallationDate: Installed on 2022-09-23 (0 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:b00a Realtek Semiconductor Corp. Realtek Bluetooth 4.2 Adapter Bus 001 Device 003: ID 04ca:7092 Lite-On Technology Corp. HP TrueVision HD Camera Bus 001 Device 002: ID 3044:eac6 MIIIW MIIIW USB Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Laptop 14-df0xxx ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=f923f152-9747-4348-b5c2-f8d1f6320e44 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/23/2021 dmi.bios.release: 15.64 dmi.bios.vendor: Insyde dmi.bios.version: F.64 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8544 dmi.board.vendor: HP dmi.board.version: KBC Version 74.37 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 74.37 dmi.modalias: dmi:bvnInsyde:bvrF.64:bd07/23/2021:br15.64:efr74.37:svnHP:pnHPLaptop14-df0xxx:pvrType1ProductConfigId:rvnHP:rn8544:rvrKBCVersion74.37:cvnHP:ct10:cvrChassisVersion:sku4XN68UA#ABA: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 14-df0xxx dmi.product.sku: 4XN68UA#ABA dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.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-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ubuntu 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/1990647 Title: Report a bug Status in xorg package in Ubuntu: New Bug description: Report a bug ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-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 Sep 23 12:17:07 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company UHD Graphics 620 [103c:8544] InstallationDate: Installed on 2022-09-23 (0 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:b00a Realtek Semiconductor Corp. Realtek Bluetooth 4.2 Adapter Bus 001 Device 003: ID 04ca:7092 Lite-On Technology Corp. HP TrueVision HD Camera Bus 001 Device 002: ID 3044:eac6 MIIIW MIIIW USB Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Laptop 14-df0xxx ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=f923f152-9747-4348-b5c2-f8d1f6320e44 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/23/2021 dmi.bios.release: 15.64 dmi.bios.vendor: Insyde dmi.bios.version: F.64 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8544 dmi.board.vendor: HP dmi.board.version: KBC Version 74.37 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 74.37 dmi.modalias:
[Desktop-packages] [Bug 1990384] Re: Super + L doesn't work
This bug affects not only the Super-L key. Lock screen doesn't work at all: - resuming from hibernating will come back with unlocked session - resuming from suspend to RAM will come back with unlocked session It happens after the upgrade from focal to jammy and aswell after a complete new installation of jammy. syslog has this ERROR message: Sep 21 14:48:37 ultrabook budgie-panel[2492]: UserIndicatorWindow.vala:379: Cannot lock screen: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.Shell.ScreenShield was not provided by any .service files -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1990384 Title: Super + L doesn't work Status in gnome-screensaver package in Ubuntu: Confirmed Bug description: Neither does changing the shortkey to the lockscreen. In the journalctl I get this: Couldn't lock screen: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: GDBus.Error:org.freedesktop.DBuscreen: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.Shell.ScreenShield was not provided by any .service fError.ServiceUnknown: The name org.gnome.Shell.ScreenShield was not provided by any .service files ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-screensaver 3.6.1-13ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 21 12:04:17 2022 GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None GsettingsGnomeSession: org.gnome.desktop.session idle-delay uint32 300 org.gnome.desktop.session session-name 'ubuntu' InstallationDate: Installed on 2022-08-16 (35 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: gnome-screensaver UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1990384/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990384] Re: Super + L doesn't work
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-screensaver (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1990384 Title: Super + L doesn't work Status in gnome-screensaver package in Ubuntu: Confirmed Bug description: Neither does changing the shortkey to the lockscreen. In the journalctl I get this: Couldn't lock screen: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: GDBus.Error:org.freedesktop.DBuscreen: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.Shell.ScreenShield was not provided by any .service fError.ServiceUnknown: The name org.gnome.Shell.ScreenShield was not provided by any .service files ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-screensaver 3.6.1-13ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 21 12:04:17 2022 GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None GsettingsGnomeSession: org.gnome.desktop.session idle-delay uint32 300 org.gnome.desktop.session session-name 'ubuntu' InstallationDate: Installed on 2022-08-16 (35 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: gnome-screensaver UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1990384/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1593407] Re: Guest session cannot run snaps
Hi Alberto, the audit log output when starting firefox is the following: Sep 23 06:49:13 ub22mate audit[5486]: AVC apparmor="DENIED" operation="mkdir" profile="/snap/snapd/16778/usr/lib/snapd/snap-confine" name="/tmp/guest-tikhhx/" pid=5486 comm="snap-confine" requested_mask="c" denied_mask="c" fsuid=997 ouid=997 The permissions of the created directory are: guest-tikhhx@ub22mate:~$ ls -la /tmp/guest-tikhhx/snap/firefox/ insgesamt 0 drwxr-xr-x 4 guest-tikhhx guest-tikhhx 100 Sep 23 06:49 . drwx-- 3 guest-tikhhx guest-tikhhx 60 Sep 23 06:49 .. drwxr-xr-x 2 guest-tikhhx guest-tikhhx 40 Sep 23 06:49 1860 drwxr-xr-x 2 guest-tikhhx guest-tikhhx 40 Sep 23 06:49 common lrwxrwxrwx 1 guest-tikhhx guest-tikhhx 4 Sep 23 06:49 current -> 1860 And just to be clear: this seems to be a Snap problem, not a Firefox problem, as the Snaps of Chromium, Opera and Skype show same behaviour. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1593407 Title: Guest session cannot run snaps Status in Light Display Manager: Confirmed Status in Snappy: Confirmed Status in Ubuntu MATE: Confirmed Status in Desktop: New Status in firefox package in Ubuntu: Confirmed Status in lightdm package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Confirmed Status in firefox source package in Xenial: Confirmed Status in lightdm source package in Xenial: Confirmed Status in snapd source package in Xenial: Confirmed Bug description: I'm using Ubuntu 16.04. The guest session cannot execute snaps, because of a permission error. The LightDM's guest session AppArmor profile is not allowing access to /snap and other needed files and folders. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1593407/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1969291] Re: apport-collect & ubuntu-bug failing to switch to firefox
First install today using current Lubuntu daily.. (20220919) Post install (not logged on QA-tracker though as not part of install test) and I was trying to open xscreensaver to confirm Leok's bug report... but it won't open. I explore /var/crash and crash report was there, so used `ubuntu-bug` hoping for it to simply finding the bug report (intending to click 'affects me too'), but instead of opening firefox though, I get /usr/bin/xdg-open: 882: firefox: not found /usr/bin/xdg-open: 882: firefox: not found xdg-open: no method available for opening 'https://bugs.launchpad.net/ubuntu/+source/xscreensaver/+filebug/1e63d072-3b07-11ed-b7a8-d485646cd9a4?' FULL PASTE of terminal follows --- guiverc@svp11216cgb:~$ ubuntu-bug /var/crash/_usr_bin_xscreensaver-settings.1000.crash *** Send problem report to the developers? After the problem report has been sent, please fill out the form in the automatically opened web browser. What would you like to do? Your options are: S: Send report (1.1 MB) V: View report K: Keep report file for sending later or copying to somewhere else I: Cancel and ignore future crashes of this program version C: Cancel Please choose (S/V/K/I/C): s *** Collecting problem information The collected information can be sent to the developers to improve the application. This might take a few minutes. *** Uploading problem information The collected information is being sent to the bug tracking system. This might take a few minutes. 99% *** To continue, you must visit the following URL: https://bugs.launchpad.net/ubuntu/+source/xscreensaver/+filebug/1e63d072-3b07-11ed-b7a8-d485646cd9a4? You can launch a browser now, or copy this URL into a browser on another computer. Choices: 1: Launch a browser now C: Cancel Please choose (1/C): 1 /usr/bin/xdg-open: 882: firefox: not found /usr/bin/xdg-open: 882: firefox: not found xdg-open: no method available for opening 'https://bugs.launchpad.net/ubuntu/+source/xscreensaver/+filebug/1e63d072-3b07-11ed-b7a8-d485646cd9a4?' guiverc@svp11216cgb:~$ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-utils in Ubuntu. https://bugs.launchpad.net/bugs/1969291 Title: apport-collect & ubuntu-bug failing to switch to firefox Status in xdg-utils package in Ubuntu: New Bug description: In attempting to file a bug report on Lubuntu jammy ISO (QA-test installed yesterday using ISO 2020-04-15) -- guiverc@dc7700-2re:~$ apport-collect 1969290 The authorization page: (https://launchpad.net/+authorize-token?oauth_token=6K7rwSbKHlbLWmkK65sj_permission=DESKTOP_INTEGRATION) should be opening in your browser. Use your browser to authorize this program to access Launchpad on your behalf. Waiting to hear from Launchpad about your decision... /usr/bin/xdg-open: 882: firefox: not found /usr/bin/xdg-open: 882: firefox: not found xdg-open: no method available for opening 'https://launchpad.net/+authorize-token?oauth_token=6K7rwSbKHlbLWmkK65sj_permission=DESKTOP_INTEGRATION' --- On attempting to file using `ubuntu-bug apport` --- guiverc@dc7700-2re:~$ ubuntu-bug apport *** Collecting problem information The collected information can be sent to the developers to improve the application. This might take a few minutes. . *** Send problem report to the developers? After the problem report has been sent, please fill out the form in the automatically opened web browser. What would you like to do? Your options are: S: Send report (5.0 KB)
[Desktop-packages] [Bug 1963264] Re: Gnome screen recorder doesn't work on dist-upgraded jammy systems
Removing ~/.cache/gstreamer-1.0/ worked for me, too. I upgraded from ‘focal’ to ‘jammy’. Following Bojan's suggestion, ‘pipewiresrc’ appeared in the output of ‘gst-inspect-1.0’ after the purge. -- 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/1963264 Title: Gnome screen recorder doesn't work on dist-upgraded jammy systems Status in GNOME Shell: Fix Released Status in gnome-shell package in Ubuntu: Confirmed Bug description: When I press Ctrl+Shift+Alt+R, screencast indicator appears in the indicator menu but disappears in about 2 seconds. No file is even created under the Videos folder. journalctl shows: Mar 02 09:10:29 Development dbus-daemon[2962]: [session uid=1000 pid=2962] Activating service name='org.gnome.Shell.Screencast' requested by ':1.62' (uid=1000 pid=3311 comm="/usr/libexec/gsd-media-> Mar 02 09:10:29 Development dbus-daemon[2962]: [session uid=1000 pid=2962] Successfully activated service 'org.gnome.Shell.Screencast' Mar 02 09:10:31 Development dbus-daemon[2962]: [session uid=1000 pid=2962] Activating service name='org.gnome.Shell.Screencast' requested by ':1.62' (uid=1000 pid=3311 comm="/usr/libexec/gsd-media-> Mar 02 09:10:31 Development dbus-daemon[2962]: [session uid=1000 pid=2962] Successfully activated service 'org.gnome.Shell.Screencast' Mar 02 09:10:32 Development gjs[5825]: JS LOG: Failed to create pipeline: Gst.ParseError: no element "pipewiresrc" The issue is the Gst.ParseError. Before upgrading to jammy (22.04), it used to work fine. Also, when testing under qemu/KVM it works properly. It just doesn't work when running directly on the PC. What other logs can I provide? ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 41.3-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Mar 3 15:41:44 2022 DisplayManager: gdm3 InstallationDate: Installed on 2020-05-12 (660 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) RelatedPackageVersions: mutter-common 41.3-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-02-27 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1963264/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990626] Re: gjs-console crashed with SIGABRT in pthread_kill()
*** This bug is a duplicate of bug 1986455 *** https://bugs.launchpad.net/bugs/1986455 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1986455, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1990626/+attachment/5618260/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1990626/+attachment/5618262/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1990626/+attachment/5618265/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1990626/+attachment/5618266/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1990626/+attachment/5618267/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1990626/+attachment/5618268/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1990626/+attachment/5618269/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1986455 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/1990626 Title: gjs-console crashed with SIGABRT in pthread_kill() Status in gjs package in Ubuntu: New Bug description: Apport popped up saying gjs-console had crashed ProblemType: Crash DistroRelease: Ubuntu 22.10 Package: gjs 1.74.0-1 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Sep 23 14:30:24 2022 ExecutablePath: /usr/bin/gjs-console InstallationDate: Installed on 2021-08-03 (415 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210802) ProcCmdline: /usr/bin/gjs /usr/bin/gnome-characters --gapplication-service ProcEnviron: XDG_RUNTIME_DIR= SHELL=/bin/bash LANGUAGE=en_AU:en PATH=(custom, user) LANG=en_AU.UTF-8 Signal: 6 SourcePackage: gjs StacktraceTop: pthread_kill () at /lib/x86_64-linux-gnu/libc.so.6 raise () at /lib/x86_64-linux-gnu/libc.so.6 abort () at /lib/x86_64-linux-gnu/libc.so.6 () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gjs-console crashed with SIGABRT in pthread_kill() UpgradeStatus: Upgraded to kinetic on 2022-08-27 (27 days ago) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sbuild sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1990626/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
