[Desktop-packages] [Bug 1991976] Re: the application uses too much CPU, and at the end of the first game, usage goes to 100%
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-mahjongg (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-mahjongg in Ubuntu. https://bugs.launchpad.net/bugs/1991976 Title: the application uses too much CPU, and at the end of the first game, usage goes to 100% Status in gnome-mahjongg package in Ubuntu: Confirmed Bug description: Environment: The OS is Xubuntu 22.04.1. The kernel is Linux 5.15.0-48-generic. The architecture is 64-bit. The machine is Lenovo ThinkPad X1 Carbon 7th generation. I'm using the snap version of the application. Command "gnome-mahjongg -v" yields "gnome-mahjongg 3.38.0". The launch command is "env BAMF_DESKTOP_FILE_HINT=/var/lib/snapd/desktop/applications/gnome- mahjongg_gnome-mahjongg.desktop /snap/bin/gnome-mahjongg". After startup, the application uses a lot of CPU; I've seen command top report over 30% usage. When the first game is finished, the usage goes to 100%. This makes application unresponsive, and I have to kill it via the command line or using command xkill. See the screenshot. The application has started to behave only recently, probably after the update to this version. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-mahjongg/+bug/1991976/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2046216] Re: error typing some Tamil characters in Ubuntu 23.10
** Description changed:
- I upgraded to Ubuntu 23.10 (Mantic) three days ago; i also installed
- updates yesterday (2023 Nov 21).
+ I upgraded to Ubuntu 23.10 (Mantic) recently and installed updates on
+ 2023 Nov 21.
I have IBus 1.5.29-rc1 installed.
Since the upgrade I've been experiencing problems typing certain
characters of the Tamil alphabet (ibus-m17n). These problems weren't
there until I upgraded to Ubuntu 23.10 (from 23.04).
I need to describe the problem in Tamil because it won't make sense
otherwise. I hope this is ok! Thank you.
---
சிக்கல் 1:
தமிழ் மெய் எழுத்துகளில் 'க்', உயிர்மெய் எழுத்துகளில் க, ங, ச, ஞ, ண, த,
ப, ர, ல, வ, ற, ன ஆகியவற்றுக்கு அடுத்ததாக வேறொரு தமிழ் எழுத்தை அல்லது
இடைவெளியைத் (space) தட்டச்சுச் செய்கையில் மேற்படி எழுத்துகளுக்கு
முன்னதாக ஓர் இடைவெளி வருகிறது!
அந்த எழுத்துகளுக்கு அடுத்ததாக (இடைவெளி அல்லாத பிற) நிறுத்தற் குறிகளைத்
தட்டச்சுச் செய்கையில் இந்தச் சிக்கல் நேர்வதில்லை.
---
- சிக்கல் 2:
+ சிக்கல் 2:
இதைச் சில எடுத்துக்காட்டுகளைக் கொண்டு தான் விளக்க முடியும்.
"பிளன" என்று தட்டச்சுச் செய்துவிட்டு 'ன'-வை நீக்க முற்பட்டால் 'ள'
அழிக்கப்படுகிறது. ஆனால் இது ஒவ்வொரு முறையும் இப்படி ஆவதில்லை!
அடுத்தடுத்து 2-3 முறை இதைச் செய்தால் முதல் தடவை மட்டும் இப்படி ஆகிறது.
பிறகு வேறு எதையேனும் (எ.கா. Enter/newline) தட்டச்சுச் செய்துவிட்டு
மீண்டும் 'பிளன'-வைத் தட்டச்சுச் செய்து backspace-ஐ அழுத்தினால் 'ள'
அழிபடுகிறது.
"பிளன"-வைப் போலவே "பிறன", "பினட" உள்ளிட்டவற்றுக்கும் ஆகிறது.
---
சிக்கல் 3:
மகுடேசுவரன் என்று தட்டச்சுச் செய்கையில் 'மகுடேச' என்பது வரை தட்டச்சுச் செய்து
backspace-ஐ அழுத்தினால் 'ச'-வுக்கு பதில் இரட்டைக் கொம்பு அழிந்துவிடுகிறது.
---
சிக்கல் 4:
தொகுத்த_ என்று எழுதினால் தொகுத்_த என்று மாறிவிடுகிறது. ('த'-வுக்குப்
பிறகு மீண்டும் ஒரு முறை '_' குறியை உள்ளிட்டு, முந்திய '_' குறியை
அழிக்கவேண்டியுள்ளது!)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ibus-m17n in Ubuntu.
https://bugs.launchpad.net/bugs/2046216
Title:
error typing some Tamil characters in Ubuntu 23.10
Status in ibus-m17n package in Ubuntu:
New
Bug description:
I upgraded to Ubuntu 23.10 (Mantic) recently and installed updates on
2023 Nov 21.
I have IBus 1.5.29-rc1 installed.
Since the upgrade I've been experiencing problems typing certain
characters of the Tamil alphabet (ibus-m17n). These problems weren't
there until I upgraded to Ubuntu 23.10 (from 23.04).
I need to describe the problem in Tamil because it won't make sense
otherwise. I hope this is ok! Thank you.
---
சிக்கல் 1:
தமிழ் மெய் எழுத்துகளில் 'க்', உயிர்மெய் எழுத்துகளில் க, ங, ச, ஞ, ண, த,
ப, ர, ல, வ, ற, ன ஆகியவற்றுக்கு அடுத்ததாக வேறொரு தமிழ் எழுத்தை அல்லது
இடைவெளியைத் (space) தட்டச்சுச் செய்கையில் மேற்படி எழுத்துகளுக்கு
முன்னதாக ஓர் இடைவெளி வருகிறது!
அந்த எழுத்துகளுக்கு அடுத்ததாக (இடைவெளி அல்லாத பிற) நிறுத்தற் குறிகளைத்
தட்டச்சுச் செய்கையில் இந்தச் சிக்கல் நேர்வதில்லை.
---
சிக்கல் 2:
இதைச் சில எடுத்துக்காட்டுகளைக் கொண்டு தான் விளக்க முடியும்.
"பிளன" என்று தட்டச்சுச் செய்துவிட்டு 'ன'-வை நீக்க முற்பட்டால் 'ள'
அழிக்கப்படுகிறது. ஆனால் இது ஒவ்வொரு முறையும் இப்படி ஆவதில்லை!
அடுத்தடுத்து 2-3 முறை இதைச் செய்தால் முதல் தடவை மட்டும் இப்படி ஆகிறது.
பிறகு வேறு எதையேனும் (எ.கா. Enter/newline) தட்டச்சுச் செய்துவிட்டு
மீண்டும் 'பிளன'-வைத் தட்டச்சுச் செய்து backspace-ஐ அழுத்தினால் 'ள'
அழிபடுகிறது.
"பிளன"-வைப் போலவே "பிறன", "பினட" உள்ளிட்டவற்றுக்கும் ஆகிறது.
---
சிக்கல் 3:
மகுடேசுவரன் என்று தட்டச்சுச் செய்கையில் 'மகுடேச' என்பது வரை தட்டச்சுச் செய்து
backspace-ஐ அழுத்தினால் 'ச'-வுக்கு பதில் இரட்டைக் கொம்பு அழிந்துவிடுகிறது.
---
சிக்கல் 4:
தொகுத்த_ என்று எழுதினால் தொகுத்_த என்று மாறிவிடுகிறது. ('த'-வுக்குப்
பிறகு மீண்டும் ஒரு முறை '_' குறியை உள்ளிட்டு, முந்திய '_' குறியை
அழிக்கவேண்டியுள்ளது!)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus-m17n/+bug/2046216/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2046216] [NEW] error typing some Tamil characters in Ubuntu 23.10
Public bug reported:
I upgraded to Ubuntu 23.10 (Mantic) recently and installed updates on
2023 Nov 21.
I have IBus 1.5.29-rc1 installed.
Since the upgrade I've been experiencing problems typing certain
characters of the Tamil alphabet (ibus-m17n). These problems weren't
there until I upgraded to Ubuntu 23.10 (from 23.04).
I need to describe the problem in Tamil because it won't make sense otherwise.
I hope this is ok! Thank you.
---
சிக்கல் 1:
தமிழ் மெய் எழுத்துகளில் 'க்', உயிர்மெய் எழுத்துகளில் க, ங, ச, ஞ, ண, த,
ப, ர, ல, வ, ற, ன ஆகியவற்றுக்கு அடுத்ததாக வேறொரு தமிழ் எழுத்தை அல்லது
இடைவெளியைத் (space) தட்டச்சுச் செய்கையில் மேற்படி எழுத்துகளுக்கு
முன்னதாக ஓர் இடைவெளி வருகிறது!
அந்த எழுத்துகளுக்கு அடுத்ததாக (இடைவெளி அல்லாத பிற) நிறுத்தற் குறிகளைத்
தட்டச்சுச் செய்கையில் இந்தச் சிக்கல் நேர்வதில்லை.
---
சிக்கல் 2:
இதைச் சில எடுத்துக்காட்டுகளைக் கொண்டு தான் விளக்க முடியும்.
"பிளன" என்று தட்டச்சுச் செய்துவிட்டு 'ன'-வை நீக்க முற்பட்டால் 'ள'
அழிக்கப்படுகிறது. ஆனால் இது ஒவ்வொரு முறையும் இப்படி ஆவதில்லை!
அடுத்தடுத்து 2-3 முறை இதைச் செய்தால் முதல் தடவை மட்டும் இப்படி ஆகிறது.
பிறகு வேறு எதையேனும் (எ.கா. Enter/newline) தட்டச்சுச் செய்துவிட்டு
மீண்டும் 'பிளன'-வைத் தட்டச்சுச் செய்து backspace-ஐ அழுத்தினால் 'ள'
அழிபடுகிறது.
"பிளன"-வைப் போலவே "பிறன", "பினட" உள்ளிட்டவற்றுக்கும் ஆகிறது.
---
சிக்கல் 3:
மகுடேசுவரன் என்று தட்டச்சுச் செய்கையில் 'மகுடேச' என்பது வரை தட்டச்சுச் செய்து
backspace-ஐ அழுத்தினால் 'ச'-வுக்கு பதில் இரட்டைக் கொம்பு அழிந்துவிடுகிறது.
---
சிக்கல் 4:
தொகுத்த_ என்று எழுதினால் தொகுத்_த என்று மாறிவிடுகிறது. ('த'-வுக்குப்
பிறகு மீண்டும் ஒரு முறை '_' குறியை உள்ளிட்டு, முந்திய '_' குறியை
அழிக்கவேண்டியுள்ளது!)
** Affects: ibus-m17n (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ibus-m17n in Ubuntu.
https://bugs.launchpad.net/bugs/2046216
Title:
error typing some Tamil characters in Ubuntu 23.10
Status in ibus-m17n package in Ubuntu:
New
Bug description:
I upgraded to Ubuntu 23.10 (Mantic) recently and installed updates on
2023 Nov 21.
I have IBus 1.5.29-rc1 installed.
Since the upgrade I've been experiencing problems typing certain
characters of the Tamil alphabet (ibus-m17n). These problems weren't
there until I upgraded to Ubuntu 23.10 (from 23.04).
I need to describe the problem in Tamil because it won't make sense
otherwise. I hope this is ok! Thank you.
---
சிக்கல் 1:
தமிழ் மெய் எழுத்துகளில் 'க்', உயிர்மெய் எழுத்துகளில் க, ங, ச, ஞ, ண, த,
ப, ர, ல, வ, ற, ன ஆகியவற்றுக்கு அடுத்ததாக வேறொரு தமிழ் எழுத்தை அல்லது
இடைவெளியைத் (space) தட்டச்சுச் செய்கையில் மேற்படி எழுத்துகளுக்கு
முன்னதாக ஓர் இடைவெளி வருகிறது!
அந்த எழுத்துகளுக்கு அடுத்ததாக (இடைவெளி அல்லாத பிற) நிறுத்தற் குறிகளைத்
தட்டச்சுச் செய்கையில் இந்தச் சிக்கல் நேர்வதில்லை.
---
சிக்கல் 2:
இதைச் சில எடுத்துக்காட்டுகளைக் கொண்டு தான் விளக்க முடியும்.
"பிளன" என்று தட்டச்சுச் செய்துவிட்டு 'ன'-வை நீக்க முற்பட்டால் 'ள'
அழிக்கப்படுகிறது. ஆனால் இது ஒவ்வொரு முறையும் இப்படி ஆவதில்லை!
அடுத்தடுத்து 2-3 முறை இதைச் செய்தால் முதல் தடவை மட்டும் இப்படி ஆகிறது.
பிறகு வேறு எதையேனும் (எ.கா. Enter/newline) தட்டச்சுச் செய்துவிட்டு
மீண்டும் 'பிளன'-வைத் தட்டச்சுச் செய்து backspace-ஐ அழுத்தினால் 'ள'
அழிபடுகிறது.
"பிளன"-வைப் போலவே "பிறன", "பினட" உள்ளிட்டவற்றுக்கும் ஆகிறது.
---
சிக்கல் 3:
மகுடேசுவரன் என்று தட்டச்சுச் செய்கையில் 'மகுடேச' என்பது வரை தட்டச்சுச் செய்து
backspace-ஐ அழுத்தினால் 'ச'-வுக்கு பதில் இரட்டைக் கொம்பு அழிந்துவிடுகிறது.
---
சிக்கல் 4:
தொகுத்த_ என்று எழுதினால் தொகுத்_த என்று மாறிவிடுகிறது. ('த'-வுக்குப்
பிறகு மீண்டும் ஒரு முறை '_' குறியை உள்ளிட்டு, முந்திய '_' குறியை
அழிக்கவேண்டியுள்ளது!)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus-m17n/+bug/2046216/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1761742] Re: Hangs for a few seconds when entering the last page when the metrics server is unavailable
This bug was fixed in the package gnome-initial-setup - 45.0-1ubuntu4 --- gnome-initial-setup (45.0-1ubuntu4) noble; urgency=medium [ Nathan Pratta Teodosio ] * Do not block on calls to Ubuntu Report (LP: #1761742). * Do not set the page as skippable. [ Marco Trevisan (Treviño) ] * debian/patches: Refresh indexes * ubuntu-report-page: Use linked style for show-report buttons * ubuntu-report-page: Fix error handling on show report * ubuntu-report-page: Avoid firing a new thread if the report is available * ubuntu-report-page: Go to next page once report is sent or on error * ubuntu-report-page: Add timeout before failing during report send * ubuntu-report-page: translate errors -- Marco Trevisan (Treviño) Mon, 11 Dec 2023 22:58:05 +0100 ** Changed in: gnome-initial-setup (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-initial-setup in Ubuntu. https://bugs.launchpad.net/bugs/1761742 Title: Hangs for a few seconds when entering the last page when the metrics server is unavailable Status in gnome-initial-setup package in Ubuntu: Fix Released Bug description: This server doesn't work at the minute. When advancing to the last page of the wizard, the following message is displayed: ** (gnome-initial-setup:803): WARNING **: 13:44:36.643: Failed to send decline: data were not delivered successfully to metrics server: couldn't send post http request: Post https://metrics.ubuntu.com/ubuntu/desktop/18.04: dial tcp 127.0.0.53:53: i/o timeout and there is a delay of a few seconds displaying the page. I suppose the calls to sysmetrics to send the report/decline should be done asynchronously. It's probably not a big problem if a few people manage to quit before the submission is finished, but if it is then there would need to be a way for the quit button to wait for all save calls to finish their async work. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-initial-setup/+bug/1761742/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2031096] Re: udisks2 daemon fails to start
If people still have an issue with the current version they should report a new issue using ubuntu-bug rather than adding content to a slightly different issue closed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to udisks2 in Ubuntu. https://bugs.launchpad.net/bugs/2031096 Title: udisks2 daemon fails to start Status in udisks: New Status in udisks2 package in Ubuntu: Fix Released Bug description: udisks2 2.10.0 fails to start in Ubuntu Mantic (23.10) Error status is: Aug 11 10:36:37 nodename systemd[1]: Starting udisks2.service - Disk Manager... Aug 11 10:36:37 nodename udisksd[232247]: udisks daemon version 2.10.0 starting Aug 11 10:36:38 nodename udisksd[232247]: Error getting 'loop28' information: Failed to open device loop28: No such file o> Aug 11 10:36:38 nodename udisksd[232247]: Error getting 'loop28' information: Failed to open device loop28: No such file o> Aug 11 10:36:38 nodename udisksd[232247]: *** stack smashing detected ***: terminated Aug 11 10:36:38 nodename systemd[1]: udisks2.service: Main process exited, code=dumped, status=6/ABRT Aug 11 10:36:38 nodename systemd[1]: udisks2.service: Failed with result 'core-dump'. Aug 11 10:36:38 nodename systemd[1]: Failed to start udisks2.service - Disk Manager. This bug seems to refer: https://github.com/storaged- project/udisks/issues/1139 To manage notifications about this bug go to: https://bugs.launchpad.net/udisks/+bug/2031096/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1908011] Re: Apport crashes during handling package-hooks and re compile
Re-assinging the bug to thunderbird which ships /usr/share/apport/package-hooks/source_thunderbird.py ** Package changed: apport (Ubuntu) => thunderbird (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1908011 Title: Apport crashes during handling package-hooks and re compile Status in thunderbird package in Ubuntu: New Bug description: Below console output should be self-explaining, don't hesitate to ask for any further info nusch@xps13:/tmp$ ubuntu-bug thunderbird ERROR: hook /usr/share/apport/package-hooks/source_thunderbird.py crashed: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/apport/report.py", line 218, in _run_hook symb['add_info'](report, ui) File "/usr/share/apport/package-hooks/source_thunderbird.py", line 1386, in add_info if (profile.current or profile.default) and profile.addon_compat_check_disabled: File "/usr/share/apport/package-hooks/source_thunderbird.py", line 1227, in addon_compat_check_disabled is_nightly = re.sub(r'^[^\.]+\.[0-9]+([a-z0-9]*).*', r'\1', self.last_version) == 'a1' File "/usr/lib/python3.6/re.py", line 191, in sub return _compile(pattern, flags).sub(repl, string, count) TypeError: expected string or bytes-like object ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: apport 2.20.9-0ubuntu7.20 Uname: Linux 5.10.0-051000rc6-generic x86_64 ApportLog: ApportVersion: 2.20.9-0ubuntu7.20 Architecture: amd64 CrashReports: 644:0:118:316:2020-12-09 17:54:46.572232715 +0100:2020-11-25 03:58:44.990978419 +0100:/var/crash/kexec_cmd CurrentDesktop: ubuntu:GNOME Date: Mon Dec 14 02:27:16 2020 InstallationDate: Installed on 2015-05-08 (2046 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: apport UpgradeStatus: Upgraded to bionic on 2018-08-26 (840 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1908011/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1908011] [NEW] Apport crashes during handling package-hooks and re compile
You have been subscribed to a public bug: Below console output should be self-explaining, don't hesitate to ask for any further info nusch@xps13:/tmp$ ubuntu-bug thunderbird ERROR: hook /usr/share/apport/package-hooks/source_thunderbird.py crashed: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/apport/report.py", line 218, in _run_hook symb['add_info'](report, ui) File "/usr/share/apport/package-hooks/source_thunderbird.py", line 1386, in add_info if (profile.current or profile.default) and profile.addon_compat_check_disabled: File "/usr/share/apport/package-hooks/source_thunderbird.py", line 1227, in addon_compat_check_disabled is_nightly = re.sub(r'^[^\.]+\.[0-9]+([a-z0-9]*).*', r'\1', self.last_version) == 'a1' File "/usr/lib/python3.6/re.py", line 191, in sub return _compile(pattern, flags).sub(repl, string, count) TypeError: expected string or bytes-like object ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: apport 2.20.9-0ubuntu7.20 Uname: Linux 5.10.0-051000rc6-generic x86_64 ApportLog: ApportVersion: 2.20.9-0ubuntu7.20 Architecture: amd64 CrashReports: 644:0:118:316:2020-12-09 17:54:46.572232715 +0100:2020-11-25 03:58:44.990978419 +0100:/var/crash/kexec_cmd CurrentDesktop: ubuntu:GNOME Date: Mon Dec 14 02:27:16 2020 InstallationDate: Installed on 2015-05-08 (2046 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: apport UpgradeStatus: Upgraded to bionic on 2018-08-26 (840 days ago) ** Affects: thunderbird (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic third-party-packages -- Apport crashes during handling package-hooks and re compile https://bugs.launchpad.net/bugs/1908011 You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird 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 2036751] Re: file-roller's show files doesn't go to file directory
** Description changed: - Clicking show files doesn't pull up the directory the files were - extracted to. It opens home. + Download any .deb package. Open from file-roller. Double-click + data.tar.zst. Click Home. Click Extract. Click Show Files. The opened + directory is /home/ not the user's home directory. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to file-roller in Ubuntu. https://bugs.launchpad.net/bugs/2036751 Title: file-roller's show files doesn't go to file directory Status in file-roller package in Ubuntu: Incomplete Bug description: Download any .deb package. Open from file-roller. Double-click data.tar.zst. Click Home. Click Extract. Click Show Files. The opened directory is /home/ not the user's home directory. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/2036751/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2046189] [NEW] Xorg freezes on external displays when in Gnome Shell on Nvidia graphics
Public bug reported:
When using external displays, they randomly freeze, but the internal
display works just fine. Windows remain interactive, but frozen, on
external displays, and the cursor disappears.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
Uname: Linux 6.5.0-14-generic x86_64
.tmp.unity_support_test.0:
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: XFCE
Date: Mon Dec 11 15:14:50 2023
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
Intel Corporation TigerLake-H GT1 [UHD Graphics] [8086:9a60] (rev 01) (prog-if
00 [VGA controller])
Subsystem: Micro-Star International Co., Ltd. [MSI] TigerLake-H GT1 [UHD
Graphics] [1462:1305]
NVIDIA Corporation GA106M [GeForce RTX 3060 Mobile / Max-Q] [10de:2520] (rev
a1) (prog-if 00 [VGA controller])
Subsystem: Micro-Star International Co., Ltd. [MSI] GA106M [GeForce RTX 3060
Mobile / Max-Q] [1462:1305]
InstallationDate: Installed on 2022-06-28 (531 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-14-generic
root=UUID=70390c05-b447-4e39-b596-a9f9eb4ac62b ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/15/2021
dmi.bios.release: 1.27
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: E17K3IMS.11B
dmi.board.asset.tag: Default string
dmi.board.name: MS-17K3
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: REV:1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: N/A
dmi.modalias:
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrE17K3IMS.11B:bd09/15/2021:br1.27:svnMicro-StarInternationalCo.,Ltd.:pnGE76Raider11UE:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-17K3:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:sku17K3.1:
dmi.product.family: GE
dmi.product.name: GE76 Raider 11UE
dmi.product.sku: 17K3.1
dmi.product.version: REV:1.0
dmi.sys.vendor: Micro-Star International Co., Ltd.
version.compiz: compiz 1:0.9.14.2+22.10.20220822-0ubuntu4
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.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-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1
** Affects: xorg (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug false-gpu-hang freeze mantic ubuntu
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/2046189
Title:
Xorg freezes on external displays when in Gnome Shell on Nvidia
graphics
Status in xorg package in Ubuntu:
New
Bug description:
When using external displays, they randomly freeze, but the internal
display works just fine. Windows remain interactive, but frozen, on
external displays, and the cursor disappears.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
Uname: Linux 6.5.0-14-generic x86_64
.tmp.unity_support_test.0:
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: XFCE
Date: Mon Dec 11 15:14:50 2023
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
Intel Corporation TigerLake-H GT1 [UHD Graphics] [8086:9a60] (rev 01)
(prog-if 00 [VGA controller])
Subsystem: Micro-Star International Co., Ltd. [MSI] TigerLake-H GT1 [UHD
Graphics] [1462:1305]
NVIDIA Corporation GA106M [GeForce RTX 3060 Mobile / Max-Q] [10de:2520] (rev
a1) (prog-if 00 [VGA controller])
Subsystem: Micro-Star International Co., Ltd. [MSI] GA106M [GeForce RTX
3060 Mobile / Max-Q] [1462:1305]
InstallationDate: Installed on 2022-06-28 (531 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64
(20220419)
MachineType: {report['dmi.sys.vendor']} {report['dmi.pro
[Desktop-packages] [Bug 2046150] Re: [BPO] libreoffice 7.5.9 for jammy
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-6185 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-6186 -- 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/2046150 Title: [BPO] libreoffice 7.5.9 for jammy Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Jammy: In Progress Bug description: [Impact] * LibreOffice 7.5.9 is in its ninth and last bugfix release of the 7.5 line: https://wiki.documentfoundation.org/ReleasePlan/7.5#7.5.9_release * This source packages matches the proposed SRU for lunar handled at https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2044369 [Scope] * Backport of https://launchpad.net/ubuntu/+source/libreoffice/1:7.5.9-0ubuntu0.23.04.1 * Backport target is Jammy/22.04 LTS releases 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_75/1776/ * 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. Jammy/22.04 build at https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-still/+sourcepub/15416837/+listing-archive-extra * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-still/jammy/amd64/libr/libreoffice/20231208_123108_1b879@/log.gz * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-still/jammy/arm64/libr/libreoffice/20231208_175608_c3b14@/log.gz * [armhf] ... (autopkgtests infra problems on this arch) * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-still/jammy/ppc64el/libr/libreoffice/20231208_135706_f6680@/log.gz * [riscv64] not available * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-still/jammy/s390x/libr/libreoffice/20231208_150850_45529@/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/2046150/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2046166] Re: mesa 23.3 zink errors
** Tags removed: block-proposed ** Tags added: block-proposed-noble update-excuse -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk4 in Ubuntu. https://bugs.launchpad.net/bugs/2046166 Title: mesa 23.3 zink errors Status in gtk4 package in Ubuntu: Triaged Status in mesa package in Ubuntu: Triaged Bug description: mesa 23.3 is emitting ZINK errors. Some initial issues were fixed which had caused autopkgtest failures for mutter and gtk4. There is still a gtk4 build test failure. My theory is that the extra ZINK stderr output is confusing the gtk:tools / validate test which is not expecting the extra errors. https://launchpad.net/ubuntu/+source/gtk4/4.12.4+ds-3ubuntu1 I am setting the block-proposed tag since I don't think we want mesa to migrate out of noble-proposed while it is causing gtk4 to fail to build. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk4/+bug/2046166/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2046166] [NEW] mesa 23.3 zink errors
Public bug reported: mesa 23.3 is emitting ZINK errors. Some initial issues were fixed which had caused autopkgtest failures for mutter and gtk4. There is still a gtk4 build test failure. My theory is that the extra ZINK stderr output is confusing the gtk:tools / validate test which is not expecting the extra errors. https://launchpad.net/ubuntu/+source/gtk4/4.12.4+ds-3ubuntu1 I am setting the block-proposed tag since I don't think we want mesa to migrate out of noble-proposed while it is causing gtk4 to fail to build. ** Affects: gtk4 (Ubuntu) Importance: High Status: Triaged ** Affects: mesa (Ubuntu) Importance: High Status: Triaged ** Tags: block-proposed ftbfs noble ** Also affects: gtk4 (Ubuntu) Importance: Undecided Status: New ** Description changed: mesa 23.3 is emitting ZINK errors. Some initial issues were fixed which had caused autopkgtest failures for mutter and gtk4. There is still a gtk4 build test failure. My theory is that the extra - ZINK stderr is confusing the gtk:tools / validate test which is not - expecting the extra errors. + ZINK stderr output is confusing the gtk:tools / validate test which is + not expecting the extra errors. https://launchpad.net/ubuntu/+source/gtk4/4.12.4+ds-3ubuntu1 I am setting the block-proposed tag since I don't think we want mesa to migrate out of noble-proposed while it is causing gtk4 to fail to build. ** Changed in: gtk4 (Ubuntu) Importance: Undecided => High ** Changed in: gtk4 (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk4 in Ubuntu. https://bugs.launchpad.net/bugs/2046166 Title: mesa 23.3 zink errors Status in gtk4 package in Ubuntu: Triaged Status in mesa package in Ubuntu: Triaged Bug description: mesa 23.3 is emitting ZINK errors. Some initial issues were fixed which had caused autopkgtest failures for mutter and gtk4. There is still a gtk4 build test failure. My theory is that the extra ZINK stderr output is confusing the gtk:tools / validate test which is not expecting the extra errors. https://launchpad.net/ubuntu/+source/gtk4/4.12.4+ds-3ubuntu1 I am setting the block-proposed tag since I don't think we want mesa to migrate out of noble-proposed while it is causing gtk4 to fail to build. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk4/+bug/2046166/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2046162] [NEW] RDP Remote Desktop automatically closes abnormally and refuses to connect.
Public bug reported: taichu@taichu-System:~$ journalctl --user-unit=gnome-remote-desktop -f 12月 11 22:39:56 taichu-System gnome-remote-de[2789012]: Unable to check file descriptor, closing connection 12月 11 22:42:01 taichu-System gnome-remote-desktop-daemon[2789012]: onnection] - Negotiated Security: NLA:1 TLS:0 RDP:0 12月 11 22:42:01 taichu-System gnome-remote-desktop-daemon[2789012]: [22:38:43:794] [2789012:2873403] [INFO][com.freerdp.core.connection] - Client Security: NLA:1 TLS:1 RDP:0 12月 11 22:42:01 taichu-System gnome-remote-desktop-daemon[2789012]: [22:38:43:794] [2789012:2873403] [INFO][com.freerdp.core.connection] - Server Security: NLA:1 TLS:0 RDP:0 12月 11 22:42:01 taichu-System gnome-remote-desktop-daemon[2789012]: [22:38:43:794] [2789012:2873403] [INFO][com.freerdp.core.connection] - Negotiated Security: NLA:1 TLS:0 RDP:0 12月 11 22:42:01 taichu-System gnome-remote-desktop-daemon[2789012]: [22:39:06:840] [2789012:2873497] [INFO][com.freerdp.core.connection] - Client Security: NLA:1 TLS:1 RDP:0 12月 11 22:42:01 taichu-System gnome-remote-desktop-daemon[2789012]: [22:39:06:840] [2789012:2873497] [INFO][com.freerdp.core.connection] - Server Security: NLA:1 TLS:0 RDP:0 12月 11 22:42:01 taichu-System gnome-remote-desktop-daemon[2789012]: [22:39:06:840] [2789012:2873497] [INFO][com.freerdp.core.connection] - Negotiated Security: NLA:1 TLS:0 RDP:0 12月 11 22:42:01 taichu-System gnome-remote-desktop-daemon[2789012]: [22:39:15:892] [2789012:2873568] [INFO][com.freerdp.core.connection] - Client Security: NLA:1 TLS:1 RDP:0 12月 11 22:42:01 taichu-System gnome-remote-desktop-daemon[2789012]: [22:39:15:892] [2789012:2873568] [INFO][com.freerdp.core.connection] - Server Security: NLA:1 TLS:0 RDP:0 12月 11 22:42:01 taichu-System gnome-remote-desktop-daemon[2789012]: [22:39:15:892] [2789012:2873568] [INFO][com.freerdp.core.connection] - Negotiated Security: NLA:1 TLS:0 RDP:0 12月 11 22:42:01 taichu-System gnome-remote-desktop-daemon[2789012]: [22:39:33:078] [2789012:2874536] [INFO][com.freerdp.core.connection] - Client Security: NLA:1 TLS:1 RDP:0 12月 11 22:42:01 taichu-System gnome-remote-desktop-daemon[2789012]: [22:39:33:078] [2789012:2874536] [INFO][com.freerdp.core.connection] - Server Security: NLA:1 TLS:0 RDP:0 12月 11 22:42:01 taichu-System gnome-remote-desktop-daemon[2789012]: [22:39:33:078] [2789012:2874536] [INFO][com.freerdp.core.connection] - Negotiated Security: NLA:1 TLS:0 RDP:0 12月 11 22:42:01 taichu-System gnome-remote-desktop-daemon[2789012]: [22:39:55:567] [2789012:2874729] [INFO][com.freerdp.core.connection] - Client Security: NLA:1 TLS:1 RDP:0 12月 11 22:42:01 taichu-System gnome-remote-desktop-daemon[2789012]: [22:39:55:567] [2789012:2874729] [INFO][com.freerdp.core.connection] - Server Security: NLA:1 TLS:0 RDP:0 12月 11 22:42:01 taichu-System gnome-remote-desktop-daemon[2789012]: [22:39:55:567] [2789012:2874729] [INFO][com.freerdp.core.connection] - Negotiated Security: NLA:1 TLS:0 RDP:0 12月 11 22:42:01 taichu-System gnome-remote-desktop-daemon[2789012]: [22:40:19:945] [2789012:2874839] [INFO][com.freerdp.core.connection] - Client Security: NLA:1 TLS:1 RDP:0 12月 11 22:42:01 taichu-System gnome-remote-desktop-daemon[2789012]: [22:40:19:945] [2789012:2874839] [INFO][com.freerdp.core.connection] - Server Security: NLA:1 TLS:0 RDP:0 12月 11 22:42:01 taichu-System gnome-remote-desktop-daemon[2789012]: [22:40:19:945] [2789012:2874839] [INFO][com.freerdp.core.connection] - Negotiated Security: NLA:1 TLS:0 RDP:0 12月 11 22:42:01 taichu-System gnome-remote-desktop-daemon[2789012]: [22:40:27:704] [2789012:2874906] [INFO][com.freerdp.core.connection] - Client Security: NLA:1 TLS:1 RDP:0 12月 11 22:42:01 taichu-System gnome-remote-desktop-daemon[2789012]: [22:40:27:704] [2789012:2874906] [INFO][com.freerdp.core.connection] - Server Security: NLA:1 TLS:0 RDP:0 12月 11 22:42:01 taichu-System gnome-remote-desktop-daemon[2789012]: [22:40:27:704] [2789012:2874906] [INFO][com.freerdp.core.connection] - Negotiated Security: NLA:1 TLS:0 RDP:0 12月 11 22:42:01 taichu-System gnome-remote-desktop-daemon[2789012]: [22:40:45:512] [2789012:2875009] [INFO][com.freerdp.core.connection] - Client Security: NLA:1 TLS:1 RDP:0 12月 11 22:42:01 taichu-System gnome-remote-desktop-daemon[2789012]: [22:40:45:512] [2789012:2875009] [INFO][com.freerdp.core.connection] - Server Security: NLA:1 TLS:0 RDP:0 12月 11 22:42:01 taichu-System gnome-remote-desktop-daemon[2789012]: [22:40:45:512] [2789012:2875009] [INFO][com.freerdp.core.connection] - Negotiated Security: NLA:1 TLS:0 RDP:0 12月 11 22:42:01 taichu-System gnome-remote-desktop-daemon[2789012]: [22:41:09:326] [2789012:2875123] [INFO][com.freerdp.core.connection] - Client Security: NLA:1 TLS:1 RDP:0 12月 11 22:42:01 taichu-System gnome-remote-desktop-daemon[2789012]: [22:41:09:326] [2789012:2875123] [INFO][com.freerdp.core.connection] - Server Security: NLA:1 TLS:0 RDP:0 12月 11 22:42:01 taichu-System gnome-remote-desktop-daemon[2789012]:
[Desktop-packages] [Bug 2009071] Re: [Blade 16 - RZ09-0483, Realtek ALC298, Speaker, Internal] No sound at all
I have a Razor Blade 16 (2023). I ran the script linked in issue #4055 (https://pastebin.com/45ksYAXX) but still do not hear any sound from the speakers. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/2009071 Title: [Blade 16 - RZ09-0483, Realtek ALC298, Speaker, Internal] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Bug description: New install of Ubuntu 22.04 has no audio. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mblack 1793 F pulseaudio /dev/snd/controlC1: mblack 1793 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME CurrentDmesg: Error: command ['pkexec', 'dmesg'] failed with exit code 126: Error executing command as another user: Request dismissed Date: Thu Mar 2 13:21:20 2023 InstallationDate: Installed on 2023-03-02 (0 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed Symptom_Card: sof-hda-dsp - sof-hda-dsp Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mblack 1793 F pulseaudio /dev/snd/controlC1: mblack 1793 F pulseaudio mblack 8091 F alsamixer Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [Blade 16 - RZ09-0483, Realtek ALC298, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/27/2023 dmi.bios.release: 1.7 dmi.bios.vendor: Razer dmi.bios.version: 1.07 dmi.board.name: SO690 dmi.board.vendor: Razer dmi.board.version: 4 dmi.chassis.type: 10 dmi.chassis.vendor: Razer dmi.ec.firmware.release: 1.3 dmi.modalias: dmi:bvnRazer:bvr1.07:bd01/27/2023:br1.7:efr1.3:svnRazer:pnBlade16-RZ09-0483:pvr9.04:rvnRazer:rnSO690:rvr4:cvnRazer:ct10:cvr:skuRZ09-0483SEJ3: dmi.product.family: 1A583006 Razer Blade dmi.product.name: Blade 16 - RZ09-0483 dmi.product.sku: RZ09-0483SEJ3 dmi.product.version: 9.04 dmi.sys.vendor: Razer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2009071/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2046158] Re: Updating wireguard-peer.allowed-ips gets wrong default netmask for IPv6 addresses
** Description changed:
In https://cockpit-project.org/ we have an integration test for
NM+wireguard integration. That test starts with an IPv4-only connection:
# cat /etc/netplan/90-NM-b5edee2d-c736-4827-bae3-c95e349cb73b.yaml
network:
- version: 2
- tunnels:
- wg0:
- renderer: NetworkManager
- addresses:
- - "10.0.0.2/24"
- mode: "wireguard"
- port: 51820
- keys:
- private: "KDI3xiJN6uthba43AMm7EBBxjPPNeamjlV3xXT5Zh0E="
- peers:
- - keys:
- public: "RsfKtJHMIAYs/i2i/TZUfRSWF1LmAEXzc3UyidXZTnI="
- allowed-ips:
- - "10.0.0.1/32"
- networkmanager:
- uuid: "b5edee2d-c736-4827-bae3-c95e349cb73b"
- name: "con-wg0"
- passthrough:
- ipv6.addr-gen-mode: "default"
- ipv6.method: "disabled"
- ipv6.ip6-privacy: "-1"
- proxy._: ""
-
+ version: 2
+ tunnels:
+ wg0:
+ renderer: NetworkManager
+ addresses:
+ - "10.0.0.2/24"
+ mode: "wireguard"
+ port: 51820
+ keys:
+ private: "KDI3xiJN6uthba43AMm7EBBxjPPNeamjlV3xXT5Zh0E="
+ peers:
+ - keys:
+ public: "RsfKtJHMIAYs/i2i/TZUfRSWF1LmAEXzc3UyidXZTnI="
+ allowed-ips:
+ - "10.0.0.1/32"
+ networkmanager:
+ uuid: "b5edee2d-c736-4827-bae3-c95e349cb73b"
+ name: "con-wg0"
+ passthrough:
+ ipv6.addr-gen-mode: "default"
+ ipv6.method: "disabled"
+ ipv6.ip6-privacy: "-1"
+ proxy._: ""
which gets rendered as
# cat /run/NetworkManager/system-connections/netplan-wg0.nmconnection
[connection]
id=con-wg0
type=wireguard
uuid=b5edee2d-c736-4827-bae3-c95e349cb73b
interface-name=wg0
[wireguard]
private-key=KDI3xiJN6uthba43AMm7EBBxjPPNeamjlV3xXT5Zh0E=
listen-port=51820
[wireguard-peer.RsfKtJHMIAYs/i2i/TZUfRSWF1LmAEXzc3UyidXZTnI=]
allowed-ips=10.0.0.1/32;
[ipv4]
method=manual
address1=10.0.0.2/24
[ipv6]
#Netplan: passthrough override
method=disabled
#Netplan: passthrough setting
addr-gen-mode=default
[proxy]
-
- Now the UI modifies the "allowed-ips" setting to ["10.0.0.1", "2001::1"].
Notably the addresses do *not* have a netmask, neither in the original config
nor that update. Unfortunately that update cannot be done on the CLI:
+ Now the UI modifies the "allowed-ips" setting to ["10.0.0.1",
+ "2001::1"]. Notably the addresses do *not* have a netmask, neither in
+ the original config nor that update. Unfortunately that update cannot be
+ done on the CLI:
# nmcli con modify con-wg0
"wireguard-peer.RsfKtJHMIAYs/i2i/TZUfRSWF1LmAEXzc3UyidXZTnI=.allowed-ips"
"2001::1"
Error: invalid or not allowed setting 'wireguard-peer': 'wireguard-peer' not
among [connection, wireguard, match, ipv4, ipv6, hostname, link, tc, proxy].
-
So it has to happen via D-Bus:
"/org/freedesktop/NetworkManager/Settings/5","org.freedesktop.NetworkManager.Settings.Connection","Update",[{"connection":{"id":{"v":"con-
wg0","t":"s"},"interface-
name":{"v":"wg0","t":"s"},"permissions":{"t":"as","v":[]},"timestamp":{"t":"t","v":1702299778},"type":{"v":"wireguard","t":"s"},"uuid":{"v":"04237010-9663-4064-aa06-bcde279b67da","t":"s"},"autoconnect":{"v":true,"t":"b"},"autoconnect-
slaves":{"v":-1,"t":"i"}},"wireguard":{"listen-
port":{"v":51820,"t":"u"},"peers":{"v":[{"public-
key":{"t":"s","v":"2CvDKtc8k94LLpabq6rZdYh1Co8fzjhoAD61ESMfjSc="},"allowed-
ips":{"t":"as","v":["10.0.0.1/32","2001::1"]}}],"t":"aa{sv}"},"private-
key":{"v":"iDM1BknhsROJt8TpJnBNNHVCAqWnfqZEkL20+sVfXlA=","t":"s"}},"ipv4":{"address-
data":{"t":"aa{sv}","v":[{"address":{"t":"s","v":"10.0.0.2"},"prefix":{"t":"u","v":24}}]},"addresses":{"v":[[33554442,24,0]],"t":"aau"},"dns-
search":{"v":[],"t":"as"},"method":{"v":"manual","t":"s"},"route-
data":{"t":"aa{sv}","v":[]},"routes":{"t":"aau","v":[]},"dns":{"v":[],"t":"au"}},"ipv6":{"address-
data":{"t":"aa{sv}","v":[]},"addresses":{"v":[],"t":"a(ayuay)"},"dns-
search":{"v":[],"t":"as"},"method":{"v":"disabled","t":"s"},"route-
data":{"t":"aa{sv}","v":[]},"routes":{"v":[],"t":"a(ayuayu)"},"ignore-
auto-dns":{"v":false,"t":"b"},"ignore-auto-
routes":{"v":false,"t":"b"},"dns":{"v":[],"t":"aay"}},"proxy":{}}]]
+ But this generates a wrong "/32" default netmask in the netplan config
+ for the IPv6 address:
- But this generates a wrong "/32" default netmask in the netplan config for
the IPv6 address:
-
- allowed-ips:
- - "10.0.0.1/32"
- - "2001::1/32"
+ allowed-ips:
+ - "10.0.0.1/32"
+ - "2001::1/32"
On Fedora, with NM's default .nmconnection files, such a netmask is not
added on this call. The netplan backend should do that (not second-
guessing NM) or at least default to /128 for an IPv6 address.
Doing this D-Bus call with `busctl` is a nuisance. If you need a
reproducer at this level, I can spend an hour o
[Desktop-packages] [Bug 2046158] [NEW] Updating wireguard-peer.allowed-ips gets wrong default netmask for IPv6 addresses
Public bug reported:
In https://cockpit-project.org/ we have an integration test for
NM+wireguard integration. That test starts with an IPv4-only connection:
# cat /etc/netplan/90-NM-b5edee2d-c736-4827-bae3-c95e349cb73b.yaml
network:
version: 2
tunnels:
wg0:
renderer: NetworkManager
addresses:
- "10.0.0.2/24"
mode: "wireguard"
port: 51820
keys:
private: "KDI3xiJN6uthba43AMm7EBBxjPPNeamjlV3xXT5Zh0E="
peers:
- keys:
public: "RsfKtJHMIAYs/i2i/TZUfRSWF1LmAEXzc3UyidXZTnI="
allowed-ips:
- "10.0.0.1/32"
networkmanager:
uuid: "b5edee2d-c736-4827-bae3-c95e349cb73b"
name: "con-wg0"
passthrough:
ipv6.addr-gen-mode: "default"
ipv6.method: "disabled"
ipv6.ip6-privacy: "-1"
proxy._: ""
which gets rendered as
# cat /run/NetworkManager/system-connections/netplan-wg0.nmconnection
[connection]
id=con-wg0
type=wireguard
uuid=b5edee2d-c736-4827-bae3-c95e349cb73b
interface-name=wg0
[wireguard]
private-key=KDI3xiJN6uthba43AMm7EBBxjPPNeamjlV3xXT5Zh0E=
listen-port=51820
[wireguard-peer.RsfKtJHMIAYs/i2i/TZUfRSWF1LmAEXzc3UyidXZTnI=]
allowed-ips=10.0.0.1/32;
[ipv4]
method=manual
address1=10.0.0.2/24
[ipv6]
#Netplan: passthrough override
method=disabled
#Netplan: passthrough setting
addr-gen-mode=default
[proxy]
Now the UI modifies the "allowed-ips" setting to ["10.0.0.1", "2001::1"].
Notably the addresses do *not* have a netmask, neither in the original config
nor that update. Unfortunately that update cannot be done on the CLI:
# nmcli con modify con-wg0
"wireguard-peer.RsfKtJHMIAYs/i2i/TZUfRSWF1LmAEXzc3UyidXZTnI=.allowed-ips"
"2001::1"
Error: invalid or not allowed setting 'wireguard-peer': 'wireguard-peer' not
among [connection, wireguard, match, ipv4, ipv6, hostname, link, tc, proxy].
So it has to happen via D-Bus:
"/org/freedesktop/NetworkManager/Settings/5","org.freedesktop.NetworkManager.Settings.Connection","Update",[{"connection":{"id":{"v":"con-
wg0","t":"s"},"interface-
name":{"v":"wg0","t":"s"},"permissions":{"t":"as","v":[]},"timestamp":{"t":"t","v":1702299778},"type":{"v":"wireguard","t":"s"},"uuid":{"v":"04237010-9663-4064-aa06-bcde279b67da","t":"s"},"autoconnect":{"v":true,"t":"b"},"autoconnect-
slaves":{"v":-1,"t":"i"}},"wireguard":{"listen-
port":{"v":51820,"t":"u"},"peers":{"v":[{"public-
key":{"t":"s","v":"2CvDKtc8k94LLpabq6rZdYh1Co8fzjhoAD61ESMfjSc="},"allowed-
ips":{"t":"as","v":["10.0.0.1/32","2001::1"]}}],"t":"aa{sv}"},"private-
key":{"v":"iDM1BknhsROJt8TpJnBNNHVCAqWnfqZEkL20+sVfXlA=","t":"s"}},"ipv4":{"address-
data":{"t":"aa{sv}","v":[{"address":{"t":"s","v":"10.0.0.2"},"prefix":{"t":"u","v":24}}]},"addresses":{"v":[[33554442,24,0]],"t":"aau"},"dns-
search":{"v":[],"t":"as"},"method":{"v":"manual","t":"s"},"route-
data":{"t":"aa{sv}","v":[]},"routes":{"t":"aau","v":[]},"dns":{"v":[],"t":"au"}},"ipv6":{"address-
data":{"t":"aa{sv}","v":[]},"addresses":{"v":[],"t":"a(ayuay)"},"dns-
search":{"v":[],"t":"as"},"method":{"v":"disabled","t":"s"},"route-
data":{"t":"aa{sv}","v":[]},"routes":{"v":[],"t":"a(ayuayu)"},"ignore-
auto-dns":{"v":false,"t":"b"},"ignore-auto-
routes":{"v":false,"t":"b"},"dns":{"v":[],"t":"aay"}},"proxy":{}}]]
But this generates a wrong "/32" default netmask in the netplan config for the
IPv6 address:
allowed-ips:
- "10.0.0.1/32"
- "2001::1/32"
On Fedora, with NM's default .nmconnection files, such a netmask is not
added on this call. The netplan backend should do that (not second-
guessing NM) or at least default to /128 for an IPv6 address.
Doing this D-Bus call with `busctl` is a nuisance. If you need a
reproducer at this level, I can spend an hour or so trying to stitch it
together, but I hope your unit tests make this easier somehow.
This was fine until 22.10, but with NM's new "netplan by default"
backend this regressed.
DistroRelease: Ubuntu 23.04
Package: network-manager 1.44.2-1ubuntu1.2
** Affects: network-manager (Ubuntu)
Importance: Undecided
Status: New
** Tags: mantic regression-release
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/2046158
Title:
Updating wireguard-peer.allowed-ips gets wrong default netmask for
IPv6 addresses
Status in network-manager package in Ubuntu:
New
Bug description:
In https://cockpit-project.org/ we have an integration test for
NM+wireguard integration. That test starts with an IPv4-only
connection:
# cat /etc/netplan/90-NM-b5edee2d-c736-4827-bae3-c95e349cb73b.yaml
network:
version: 2
tunnels:
wg0:
renderer: NetworkManager
addresses:
- "10.0.0.2/24"
mode: "wireguard"
port: 51820
keys:
private: "KDI3xiJN6uthba43AMm7EBBxjPPNeamjlV3xXT5Zh0E="
peers:
- keys:
public: "RsfKtJHMIAYs/i2i/TZUfRSWF
[Desktop-packages] [Bug 2044019] Re: [SRU] libreoffice 7.6.4 for mantic
This bug was fixed in the package libreoffice - 4:7.6.4-0ubuntu0.23.10.1 --- libreoffice (4:7.6.4-0ubuntu0.23.10.1) mantic-security; urgency=medium * New upstream release (LP: #2044019) * SECURITY UPDATE: Improper input validation enabling arbitrary Gstreamer pipeline injection - CVE-2023-6185 * SECURITY UPDATE: Link targets allow arbitrary script execution - CVE-2023-6186 [ Rico Tzschichholz ] * debian/patches/fix-arm64-tests.diff: - Dropped while it got fixed upsteam * debian/patches/fix-armhf-linker.diff: - Included upsteam now * Update replace-source-sans-in-templates.diff [ Rene Engelhard ] * debian/rules: - readd fonts-crosextra-caladea build-dep; Cambria usage is back - re-enable cmis; bump libcmis build-dep to >= 0.6.1 * debian/control.in: - duplicate Replaces: as Breaks: in -uiconfig-* * Update patches/we-dont-have-the-needed-fonts.diff and patches/adapt-for-new-carlito.diff -- Rico Tzschichholz Thu, 07 Dec 2023 22:10:12 +0100 ** Changed in: libreoffice (Ubuntu Mantic) Status: In Progress => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-6185 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-6186 -- 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/2044019 Title: [SRU] libreoffice 7.6.4 for mantic Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Mantic: Fix Released Bug description: [Impact] * LibreOffice 7.6.4 is in its forth bugfix release of the 7.6 line: https://wiki.documentfoundation.org/ReleasePlan/7.6#7.6.4_release * Version 7.6.2 is currently released in mantic. For a list of fixed bugs compared to 7.6.2 see the list of bugs fixed in the release candidates of 7.6.4 (that's a total of 157 bugs): https://wiki.documentfoundation.org/Releases/7.6.3/RC1#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/7.6.3/RC2#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/7.6.4/RC1#List_of_fixed_bugs 7.6.4 RC1 is identical to the 7.6.4 release * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [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_76/1558/ * 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. Tested build can be found at https://launchpad.net/~ricotz/+archive/ubuntu/ppa/+sourcepub/15417677/+listing-archive-extra * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-ricotz-ppa/mantic/amd64/libr/libreoffice/20231208_113305_ce7d3@/log.gz * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-ricotz-ppa/mantic/arm64/libr/libreoffice/20231208_181454_f665b@/log.gz * [armhf] ... (autopkgtests infra problems on this arch) * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-ricotz-ppa/mantic/ppc64el/libr/libreoffice/20231208_140510_db345@/log.gz * [riscv64] not available * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-ricotz-ppa/mantic/s390x/libr/libreoffice/20231208_142154_9eaf6@/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 minor release with a total of 157 bug fixes always carries the potential for introducing regressions, even though it is a bugfix-only release, meaning that no new features were added, and no existing features were removed. * 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/2044019/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packag
[Desktop-packages] [Bug 2044369] Re: [SRU] libreoffice 7.5.9 for lunar
This bug was fixed in the package libreoffice - 4:7.5.9-0ubuntu0.23.04.1 --- libreoffice (4:7.5.9-0ubuntu0.23.04.1) lunar-security; urgency=medium * New upstream release (LP: #2044369) * SECURITY UPDATE: Improper input validation enabling arbitrary Gstreamer pipeline injection - CVE-2023-6185 * SECURITY UPDATE: Link targets allow arbitrary script execution - CVE-2023-6186 [ Rico Tzschichholz ] * patches/CppunitTest_desktop_lib-adjust-asserts-so-this-works.patch: - Usage of expired certificates in CppunitTest_desktop_lib: adjust asserts so this works again [ Rene Engelhard ] * debian/rules: - Re-enable cmis; bump libcmis build-dep to >= 0.6.1 -- Rico Tzschichholz Tue, 28 Nov 2023 20:57:57 +0100 ** Changed in: libreoffice (Ubuntu Lunar) Status: In Progress => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-6185 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-6186 -- 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/2044369 Title: [SRU] libreoffice 7.5.9 for lunar Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Lunar: Fix Released Bug description: [Impact] * LibreOffice 7.5.9 is in its ninth and last bugfix release of the 7.5 line: https://wiki.documentfoundation.org/ReleasePlan/7.5#7.5.9_release * Version 7.5.8 is currently released in lunar. For a list of fixed bugs compared to 7.5.8 see the list of bugs fixed in the release candidates of 7.5.9 (that's a total of ? bugs): https://wiki.documentfoundation.org/Releases/7.5.9/RC1#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/7.5.9/RC2#List_of_fixed_bugs 7.5.9 RC2 is identical to the 7.5.9 release * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [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_75/1776/ * 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. Tested build can be found at https://launchpad.net/~ricotz/+archive/ubuntu/ppa/+sourcepub/15402714/+listing-archive-extra * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-ricotz-ppa/lunar/amd64/libr/libreoffice/20231130_032215_7d344@/log.gz * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-ricotz-ppa/lunar/arm64/libr/libreoffice/20231130_110658_1779c@/log.gz * [armhf] ... (autopkgtests infra problems on this arch) * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-ricotz-ppa/lunar/ppc64el/libr/libreoffice/20231129_180258_07169@/log.gz * [riscv64] not available * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-ricotz-ppa/lunar/s390x/libr/libreoffice/20231130_024056_ac67e@/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 minor release with a total of ? bug fixes always carries the potential for introducing regressions, even though it is a bugfix-only release, meaning that no new features were added, and no existing features were removed. * 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/2044369/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2046150] Re: [BPO] libreoffice 7.5.9 for jammy
** Patch added: "libreoffice_7.5.9-0ubuntu0.23.04.1_bpo22.04.1.diff" https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2046150/+attachment/5728235/+files/libreoffice_7.5.9-0ubuntu0.23.04.1_bpo22.04.1.diff -- 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/2046150 Title: [BPO] libreoffice 7.5.9 for jammy Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Jammy: In Progress Bug description: [Impact] * LibreOffice 7.5.9 is in its ninth and last bugfix release of the 7.5 line: https://wiki.documentfoundation.org/ReleasePlan/7.5#7.5.9_release * This source packages matches the proposed SRU for lunar handled at https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2044369 [Scope] * Backport of https://launchpad.net/ubuntu/+source/libreoffice/1:7.5.9-0ubuntu0.23.04.1 * Backport target is Jammy/22.04 LTS releases 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_75/1776/ * 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. Jammy/22.04 build at https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-still/+sourcepub/15416837/+listing-archive-extra * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-still/jammy/amd64/libr/libreoffice/20231208_123108_1b879@/log.gz * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-still/jammy/arm64/libr/libreoffice/20231208_175608_c3b14@/log.gz * [armhf] ... (autopkgtests infra problems on this arch) * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-still/jammy/ppc64el/libr/libreoffice/20231208_135706_f6680@/log.gz * [riscv64] not available * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-still/jammy/s390x/libr/libreoffice/20231208_150850_45529@/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/2046150/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2046150] [NEW] [BPO] libreoffice 7.5.9 for jammy
Public bug reported: [Impact] * LibreOffice 7.5.9 is in its ninth and last bugfix release of the 7.5 line: https://wiki.documentfoundation.org/ReleasePlan/7.5#7.5.9_release * This source packages matches the proposed SRU for lunar handled at https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2044369 [Scope] * Backport of https://launchpad.net/ubuntu/+source/libreoffice/1:7.5.9-0ubuntu0.23.04.1 * Backport target is Jammy/22.04 LTS releases 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_75/1776/ * 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. Jammy/22.04 build at https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-still/+sourcepub/15416837/+listing-archive-extra * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-still/jammy/amd64/libr/libreoffice/20231208_123108_1b879@/log.gz * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-still/jammy/arm64/libr/libreoffice/20231208_175608_c3b14@/log.gz * [armhf] ... (autopkgtests infra problems on this arch) * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-still/jammy/ppc64el/libr/libreoffice/20231208_135706_f6680@/log.gz * [riscv64] not available * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-still/jammy/s390x/libr/libreoffice/20231208_150850_45529@/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. ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: libreoffice (Ubuntu Jammy) Importance: Critical Assignee: Rico Tzschichholz (ricotz) Status: In Progress ** Also affects: libreoffice (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: libreoffice (Ubuntu) Status: New => Fix Released ** Changed in: libreoffice (Ubuntu Jammy) Importance: Undecided => Critical ** Changed in: libreoffice (Ubuntu Jammy) Status: New => In Progress ** Changed in: libreoffice (Ubuntu Jammy) Assignee: (unassigned) => Rico Tzschichholz (ricotz) -- 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/2046150 Title: [BPO] libreoffice 7.5.9 for jammy Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Jammy: In Progress Bug description: [Impact] * LibreOffice 7.5.9 is in its ninth and last bugfix release of the 7.5 line: https://wiki.documentfoundation.org/ReleasePlan/7.5#7.5.9_release * This source packages matches the proposed SRU for lunar handled at https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2044369 [Scope] * Backport of https://launchpad.net/ubuntu/+source/libreoffice/1:7.5.9-0ubuntu0.23.04.1 * Backport target is Jammy/22.04 LTS releases 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_75/1776/ * 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
[Desktop-packages] [Bug 2044382] Re: Quassel opens "another" icon under Gnome
This seems to be something to do with the version of the dash under mantic, and with the fact it's running under Wayland specifically. A similar issue came up on the Pi forums, and included an excellent minimal reproduction case (which I'll include here for simplicity). Notably, the issue does *not* occur (with either this reproduction case, or with quassel) under Xorg, only under a Wayland session: ~/.local/bin/stopwatch: #!/bin/bash echo "STOP" echo "Watch" read ~/.local/share/applications/stopwatch.desktop: [Desktop Entry] Version=1.0 Type=Application Terminal=false Icon=StopWatch Name=StopWatch Exec=gnome-terminal --class=StopWatchTerminal -- /home/ubuntu/.local/bin/stopwatch StartupWMClass=StopWatchTerminal Adjust the /home/ubuntu/ path as necessary. Pin the "StopWatch" application to the dash and launch it; under Xorg a dot appears next to the pinned application. Under Wayland, an additional "gnome-terminal- server" icon appears on the dash. -- 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/2044382 Title: Quassel opens "another" icon under Gnome Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Status in quassel package in Ubuntu: New Bug description: I'm unsure if this is a bug in quassel, or in the gnome dock itself. Under Ubuntu 23.10 (mantic), running Quassel from a pinned icon on the left bar results in the pinned icon appearing "idle" (not running), and a second icon appearing below those that are pinned which apparently represents the running quassel instance. Pressing the idle quassel icon (or pressing the Super+4 shortcut for it) runs *another* instance of quassel rather than switching to the running instance. The "extra" icon also cannot be pinned (and occasionally strange "copies" of it are left lying around if one tries to drag it to the pinned icon locations). This may be because quassel is a Qt based application, but I also run KeepassXC (another Qt application) without such issues (other than unusual window borders and icons which appear on both applications), hence why I'm unsure this is an issue in quassel or in the gnome dock. I'll attach a screenshot demonstrating the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/2044382/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2044382] Re: Quassel opens "another" icon under Gnome
Oh, and the issue on the Pi forums is here: https://forums.raspberrypi.com/viewtopic.php?p=2167317 -- 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/2044382 Title: Quassel opens "another" icon under Gnome Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Status in quassel package in Ubuntu: New Bug description: I'm unsure if this is a bug in quassel, or in the gnome dock itself. Under Ubuntu 23.10 (mantic), running Quassel from a pinned icon on the left bar results in the pinned icon appearing "idle" (not running), and a second icon appearing below those that are pinned which apparently represents the running quassel instance. Pressing the idle quassel icon (or pressing the Super+4 shortcut for it) runs *another* instance of quassel rather than switching to the running instance. The "extra" icon also cannot be pinned (and occasionally strange "copies" of it are left lying around if one tries to drag it to the pinned icon locations). This may be because quassel is a Qt based application, but I also run KeepassXC (another Qt application) without such issues (other than unusual window borders and icons which appear on both applications), hence why I'm unsure this is an issue in quassel or in the gnome dock. I'll attach a screenshot demonstrating the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/2044382/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2046146] Re: Copy/Paste or Drag/Drop fails if a source folder contains a colon in its name
Thank you for your bug report. Could you be a bit more specific on the error message you get, maybe include a screenshot showing the dialog? ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low ** Changed in: nautilus (Ubuntu) Status: New => Incomplete -- 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/2046146 Title: Copy/Paste or Drag/Drop fails if a source folder contains a colon in its name Status in nautilus package in Ubuntu: Incomplete Bug description: I was copying files to my phone connected to USB. It worked after I removed the colon from the source folder name. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: nautilus 1:45~rc-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Dec 11 05:19:36 2023 InstallationDate: Installed on 2022-02-15 (664 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: nautilus UpgradeStatus: Upgraded to mantic on 2023-11-08 (33 days ago) usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.49.92-2ubuntu1 python3-nautilus 4.0-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2046146/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2046146] [NEW] Copy/Paste or Drag/Drop fails if a source folder contains a colon in its name
Public bug reported: I was copying files to my phone connected to USB. It worked after I removed the colon from the source folder name. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: nautilus 1:45~rc-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Dec 11 05:19:36 2023 InstallationDate: Installed on 2022-02-15 (664 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: nautilus UpgradeStatus: Upgraded to mantic on 2023-11-08 (33 days ago) usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.49.92-2ubuntu1 python3-nautilus 4.0-1build1 ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug mantic wayland-session -- 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/2046146 Title: Copy/Paste or Drag/Drop fails if a source folder contains a colon in its name Status in nautilus package in Ubuntu: New Bug description: I was copying files to my phone connected to USB. It worked after I removed the colon from the source folder name. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: nautilus 1:45~rc-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Dec 11 05:19:36 2023 InstallationDate: Installed on 2022-02-15 (664 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: nautilus UpgradeStatus: Upgraded to mantic on 2023-11-08 (33 days ago) usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.49.92-2ubuntu1 python3-nautilus 4.0-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2046146/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
