[Desktop-packages] [Bug 2000551] Re: [System Fonts] Replace default sinhala font from LKLUG to Noto
@Aurora: fonts-noto-core needs to be installed also. Please see the test plan. They should open Language Support. If a user already has the Sinhala language installed, they will be prompted to install fonts-noto-core. Otherwise they should install Sinhala, in which case fonts-noto-core will be one of the installed packages. Or they can simply do: sudo apt install fonts-noto-core Once ISOs with the 22.04.2 point release is out, a new install of Ubuntu, where the user picks Sinhala as the language in the installer, will use the Noto fonts out of the box. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/2000551 Title: [System Fonts] Replace default sinhala font from LKLUG to Noto Status in language-selector package in Ubuntu: Fix Released Status in ubuntu-meta package in Ubuntu: Won't Fix Status in language-selector source package in Jammy: Fix Committed Status in language-selector source package in Kinetic: Fix Committed Bug description: [ Impact ] The current default font for Sinhala (LKLUG) is unmaintained and comes with issues. Noto offers Sinhala fonts with significantly higher quality. fonts-lklug-sinhala is pulled by quite a few meta packages. Instead of changing that, the proposed change makes fontconfig give Noto Sans Sinhala respective Noto Serif Sinhala higher precedence than LKLUG, and that — together with installation of fonts-noto-core — seems to be sufficient to achieve the desired result. [ Test Plan ] * Install language-selector-[common,gnome] from [jammy,kinetic]-proposed. * Open Language Support and install the Sinhala language. * Open a terminal window and run this command: fc-match -a | grep -E 'LKLUG|Sinhala' * Confirm that Noto Sans Sinhala is listed before LKLUG. * Close Firefox and re-open it. * Visit e.g. https://si.wikipedia.org and confirm the improvement. (Also I (Gunnar), who don't speak Sinhala, notice a remarkable difference.) [ Where problems could occur ] No real problem in sight. Some Sinhala speaking users with fonts-noto- core installed will indeed see a surprise change when it starts to render Sinhala via Noto fonts instead of LKLUG. But that surprise ought to make them happy. :) Please note Robie Basak's warning about the changed font metrics in comment #7, though. [ Original description ] **What's the problem?** Currently ubuntu comes with LKLUG font for sinhala (si). it's not clear. e.g. we cannot recognize vowel signs and read websites using that font. We can change it manually but such changes do not apply to some applications or application types e.g. snap apps etc. LKLUG (last active: 2012) no one maintain it now. https://web.archive.org/web/202200*/http://www.lug.lk/ http://www.lug.lk/fonts/lklug **What expected to happen?** We would like to see Noto serif sinhala as the default font for sinhala language https://fonts.google.com/noto/specimen/Noto+Serif+Sinhala [Highlighs: clear (readable), thin, takes less space than sans sinhala] If noto sans is more suitable for ubuntuOS, you can add noto sans sinhala https://fonts.google.com/noto/specimen/Noto+Sans+Sinhala [Highlighs: clear (readable), thick, takes more space than serif sinhala] **Additional details** Screenshots (see the difference: LKLUG/Noto) LKLUG https://i.ibb.co/nbHM5Mw/lklug.jpg Noto Sinhala https://i.ibb.co/k9dbtYb/noto.jpg If you need more examples or clarifications, please add a comment Random posts 1. https://groups.google.com/g/Sinhala-Unicode/c/LYxuJ44dY3g 2. https://twitter.com/thilinag/status/1598707165920825344#m (LKLUG bug with some apps) 3. https://www.reddit.com/r/srilanka/comments/nzpl9p/change_sinhala_font_in_ubuntu/ Also, some developers already have designed tools, scripts for that problem however many people do not try to find these scripts and switch to other OS 1. https://github.com/IMS94/UbuntuSinhalaFont (developer: PMC chair @apache) 2. https://gist.github.com/thilinag/66577033fafd00c3dfdaa898c2478c79 3. https://github.com/hankyoTutorials/linux-system-sinhala-font-changer Please review details, screenshots and posts. This is not a personal opinion and atleast, i expect to see this change in the next interim or LTS release. Furthermore, please let me know if i can help to speed-up this replacement process To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/2000551/+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 1959103] Re: polkitd crashes with segfault with specific config file
I had similar issue with the following config:
[steam-network-perm]
Identity unix-user:gry
Action org.freedesktop.NetworkManager.settings.modify.system
ResultActive no
ResultInactive no
ResultAny no
This is due to some programming bug when handling config files. Attached patch
fixes the issue for me.
** Patch added: "fix-config-error-handling.patch"
https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1959103/+attachment/5641584/+files/fix-config-error-handling.patch
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to policykit-1 in Ubuntu.
https://bugs.launchpad.net/bugs/1959103
Title:
polkitd crashes with segfault with specific config file
Status in policykit-1 package in Ubuntu:
Confirmed
Bug description:
The following config file in
`/etc/polkit-1/localauthority.conf.d/02-allow-colord.conf` can cause a
segfault in `polkitd`.
```
polkit.addRule(function(action, subject) {
if ((action.id == "org.freedesktop.color-manager.create-device" ||
action.id == "org.freedesktop.color-manager.create-profile" ||
action.id == "org.freedesktop.color-manager.delete-device" ||
action.id == "org.freedesktop.color-manager.delete-profile" ||
action.id == "org.freedesktop.color-manager.modify-device" ||
action.id == "org.freedesktop.color-manager.modify-profile") &&
subject.isInGroup("{group}")) {
return polkit.Result.YES;
}
});
```
1. As normal user: `systemctl restart cron.service`
2. Error message `Failed to restart cron.service: Message recipient
disconnected from message bus without replying`
3. `dmesg` reports:
```
58.003893] polkitd[963]: segfault at 8 ip 558a96789856 sp
7ffda31e45f0 error 4 in polkitd[558a96784000+f000]
[ 58.003899] Code: 50 c7 ff ff 4d 89 e5 48 89 44 24 08 eb 53 66 0f 1f 44 00
00 48 8b 44 24 10 48 89 e9 be 10 00 00 00 31 ff 48 8d 15 0b af 00 00 <4c> 8b 40
08 31 c0 e8 af cb ff ff 48 8b 7c 24 10 e8 65 c9 ff ff 4c
``
If you remove the 02-allow-colord.conf the segfault goes away and you
are normally prompted for a password. You can also find a couple of
references in the internet, e.g http://c-nergy.be/blog/?p=12043.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1959103/+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 2000551] Re: [System Fonts] Replace default sinhala font from LKLUG to Noto
Hi @gunnarhj >I have played with the language-selector package and made a test version >available here: Can you please install language-selector-gnome and language-selector-common from the PPA I mentioned, https://launchpad.net/~gunnarhj/+archive/ubuntu/language-selector I said that it helped to change the font properly (kinetic:22.10 device) ^_^ but users who received the 0.219.1 update (jammy-proposed) to 22.04 said nothing changed on their devices. what's the reason? they've also restarted their devices -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/2000551 Title: [System Fonts] Replace default sinhala font from LKLUG to Noto Status in language-selector package in Ubuntu: Fix Released Status in ubuntu-meta package in Ubuntu: Won't Fix Status in language-selector source package in Jammy: Fix Committed Status in language-selector source package in Kinetic: Fix Committed Bug description: [ Impact ] The current default font for Sinhala (LKLUG) is unmaintained and comes with issues. Noto offers Sinhala fonts with significantly higher quality. fonts-lklug-sinhala is pulled by quite a few meta packages. Instead of changing that, the proposed change makes fontconfig give Noto Sans Sinhala respective Noto Serif Sinhala higher precedence than LKLUG, and that — together with installation of fonts-noto-core — seems to be sufficient to achieve the desired result. [ Test Plan ] * Install language-selector-[common,gnome] from [jammy,kinetic]-proposed. * Open Language Support and install the Sinhala language. * Open a terminal window and run this command: fc-match -a | grep -E 'LKLUG|Sinhala' * Confirm that Noto Sans Sinhala is listed before LKLUG. * Close Firefox and re-open it. * Visit e.g. https://si.wikipedia.org and confirm the improvement. (Also I (Gunnar), who don't speak Sinhala, notice a remarkable difference.) [ Where problems could occur ] No real problem in sight. Some Sinhala speaking users with fonts-noto- core installed will indeed see a surprise change when it starts to render Sinhala via Noto fonts instead of LKLUG. But that surprise ought to make them happy. :) Please note Robie Basak's warning about the changed font metrics in comment #7, though. [ Original description ] **What's the problem?** Currently ubuntu comes with LKLUG font for sinhala (si). it's not clear. e.g. we cannot recognize vowel signs and read websites using that font. We can change it manually but such changes do not apply to some applications or application types e.g. snap apps etc. LKLUG (last active: 2012) no one maintain it now. https://web.archive.org/web/202200*/http://www.lug.lk/ http://www.lug.lk/fonts/lklug **What expected to happen?** We would like to see Noto serif sinhala as the default font for sinhala language https://fonts.google.com/noto/specimen/Noto+Serif+Sinhala [Highlighs: clear (readable), thin, takes less space than sans sinhala] If noto sans is more suitable for ubuntuOS, you can add noto sans sinhala https://fonts.google.com/noto/specimen/Noto+Sans+Sinhala [Highlighs: clear (readable), thick, takes more space than serif sinhala] **Additional details** Screenshots (see the difference: LKLUG/Noto) LKLUG https://i.ibb.co/nbHM5Mw/lklug.jpg Noto Sinhala https://i.ibb.co/k9dbtYb/noto.jpg If you need more examples or clarifications, please add a comment Random posts 1. https://groups.google.com/g/Sinhala-Unicode/c/LYxuJ44dY3g 2. https://twitter.com/thilinag/status/1598707165920825344#m (LKLUG bug with some apps) 3. https://www.reddit.com/r/srilanka/comments/nzpl9p/change_sinhala_font_in_ubuntu/ Also, some developers already have designed tools, scripts for that problem however many people do not try to find these scripts and switch to other OS 1. https://github.com/IMS94/UbuntuSinhalaFont (developer: PMC chair @apache) 2. https://gist.github.com/thilinag/66577033fafd00c3dfdaa898c2478c79 3. https://github.com/hankyoTutorials/linux-system-sinhala-font-changer Please review details, screenshots and posts. This is not a personal opinion and atleast, i expect to see this change in the next interim or LTS release. Furthermore, please let me know if i can help to speed-up this replacement process To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/2000551/+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 2002941] Re: [BPO] libreoffice 7.4.4 for jammy
** Patch added: "libreoffice_7.4.4-0ubuntu0.22.10.1_bpo22.04.1.patch" https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2002941/+attachment/5641557/+files/libreoffice_7.4.4-0ubuntu0.22.10.1_bpo22.04.1.patch -- 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/2002941 Title: [BPO] libreoffice 7.4.4 for jammy Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Jammy: New Bug description: [Impact] * LibreOffice 7.4.4 is in its forth bugfix release of the 7.4 line: https://wiki.documentfoundation.org/ReleasePlan/7.4#7.4.4_release * This source packages matches the proposed SRU for kinetic handled at https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2001911 and its backport is currently provided by the LibreOffice Fresh PPA at https://launchpad.net/~libreoffice/+archive/ubuntu/ppa/+packages * LibreOffice 7.3.7 (EOL since November 30, 2022) is currently released in jammy. * 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. [Scope] * Backport of https://launchpad.net/ubuntu/+source/libreoffice/1:7.4.4-0ubuntu0.22.10.1 * Backport target is Jammy/22.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_74/1542/ * 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] ... * [arm64] ... * [armhf] ... * [ppc64el] ... * [s390x] ... * 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 114 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/2002941/+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 1682542] Re: Add support for top bars on all monitors to allow for multi-monitor support in primary extensions - apps-menu, places-menu, topbar, etc
Yes, this is a very required feature. When working with (or presenting to) external displays, it is necessary to: - see time - have access to calendar - Some apps are missing top bars. Very appreciated. -- 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/1682542 Title: Add support for top bars on all monitors to allow for multi-monitor support in primary extensions - apps-menu, places-menu, topbar, etc Status in GNOME Shell: New Status in gnome-shell package in Ubuntu: Triaged Bug description: This issue will effectively be a regression in desktop usage once Ubuntu switches from Unity to Gnome Shell. Gnome Shell does not work well with multiple monitors unlike every other desktop environment except Budgie, which is switching away from GTK/Gnome to Qt with Budgie 11 due out in the next month or two. I reported it upstream last month but it does not appear to have much traction at the moment. https://bugzilla.gnome.org/show_bug.cgi?id=780078 " It would be nice if the primary included gnome-shell extensions, eg apps-menu and places-menu (and by extension the topbar) supported multi-monitor similar to how the bottom bar 'window-list' currently does. This was easy to achieve on Gnome 2 and now via MATE (out of the box) but there does not appear to be any way to do this with Gnome 3. This also leads to there not being a way to do this via 'Gnome Classic'. Even Windows finally (in W10) does this better out of the box than Gnome 3. BTW - Intel has supported IGP triple head since Ivy Bridge (2012) so it is very cheap to deploy a triple head system (~ $200 for 3 1080p monitors). AMD supports up to quad head in their IGPs. This has been blocking me from moving to Gnome 3 since its release and I finally decided to write a bug report about it. I have had all multi-monitor systems since prior to 2004. " And see comments #11 and #14 from Florian. " No, you don't want that in the extensions. Each extension is separate, so what you are asking for here is that apps-menu and places-menu *both* add top bars to non-primary monitors. We are definitely not going to add two or more stacked panels at the top. What you probably want instead is an option in gnome-shell to put top bars on non-primary monitors, and the aforementioned extensions to handle that case. " " Well, we've established what you want, but that doesn't necessarily mean that we'll implement it. So far the reasoning seems to be: - you really want the feature - GNOME 2 / Windows has it Unlike the case of the window list, nothing in the top bar (except for the app menu to some extent) is tied to a particular monitor, so there's a much weaker case here IMHO. (I'll also note that this wouldn't be a "cheap" option, but require work on lots of details throughout the stack - we'd need to figure out the overview (only include the activities button on the primary monitor? or allow an overview on any monitor?), get API to control the brightness of a particular monitor (rather than the built-in one), don't use "the monitor with the top bar" as indicator for the primary monitor in Settings, ...) " To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1682542/+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 1988364] Re: Missing the A2DP profile and defaults to low quality
** Tags added: jammy ** Also affects: bluez (Ubuntu Lunar) Importance: High Status: Fix Released ** Also affects: bluez (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: bluez (Ubuntu Kinetic) Importance: Undecided Status: New ** Changed in: bluez (Ubuntu Kinetic) Status: New => Fix Released ** Changed in: bluez (Ubuntu Kinetic) Importance: Undecided => High ** Changed in: bluez (Ubuntu Jammy) Status: New => In Progress ** Changed in: bluez (Ubuntu Jammy) Assignee: (unassigned) => Daniel van Vugt (vanvugt) ** Changed in: bluez (Ubuntu Kinetic) Importance: High => Medium ** Changed in: bluez (Ubuntu Lunar) Importance: High => Medium ** Changed in: bluez (Ubuntu Jammy) Importance: Undecided => Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1988364 Title: Missing the A2DP profile and defaults to low quality Status in Bluez Utilities: Fix Released Status in bluez package in Ubuntu: Fix Released Status in bluez source package in Jammy: In Progress Status in bluez source package in Kinetic: Fix Released Status in bluez source package in Lunar: Fix Released Bug description: [ Impact ] Sony WH-1000XM4 missing the A2DP profile and defaults to low quality. Probably other headphone types would be affected too. https://github.com/bluez/bluez/issues/313 [ Test Plan ] ANYONE AFFECTED BY THE BUG PLEASE FILL THIS IN [ Where problems could occur ] The fix touches Bluetooth audio logic (only). So anything relating to Bluetooth audio (A2DP) is the main risk. A secondary risk is the rest of bluetoothd which could suffer side effects. [ Other Info ] None provided. To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1988364/+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 2002966] Re: gnome-calendar crashed with SIGSEGV in g_source_get_ready_time()
*** This bug is a duplicate of bug 1869068 *** https://bugs.launchpad.net/bugs/1869068 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 #1869068, 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/2002966/+attachment/5641648/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/2002966/+attachment/5641650/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/2002966/+attachment/5641653/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/2002966/+attachment/5641654/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/2002966/+attachment/5641655/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/2002966/+attachment/5641656/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/2002966/+attachment/5641657/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1869068 ** 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 gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/2002966 Title: gnome-calendar crashed with SIGSEGV in g_source_get_ready_time() Status in gnome-calendar package in Ubuntu: New Bug description: The calendar app was not open. The error bug just appeared on the desktop. I have put this down as new bug as the fix filed in 2019 hasn't worked on Lunar Lobster ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: gnome-calendar 43.1-1 ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 ApportVersion: 2.24.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jan 16 08:36:21 2023 ExecutablePath: /usr/bin/gnome-calendar InstallationDate: Installed on 2023-01-05 (11 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221209) ProcCmdline: /usr/bin/gnome-calendar --gapplication-service ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANGUAGE=en_GB:en LANG=en_GB.UTF-8 SegvAnalysis: Segfault happened at: 0x7f08c174d82d : mov 0x18(%rdi),%eax PC (0x7f08c174d82d) ok source "0x18(%rdi)" (0x0329) not located in a known VMA region (needed readable region)! destination "%eax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-calendar StacktraceTop: g_source_get_ready_time () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-calendar crashed with SIGSEGV in g_source_get_ready_time() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/2002966/+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 1997907] Re: [snap] Message 0 rejected by interface blink.mojom.WidgetHost
Yes, wireless function is nominal. -- 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/1997907 Title: [snap] Message 0 rejected by interface blink.mojom.WidgetHost Status in chromium-browser package in Ubuntu: New Bug description: Chromium shuts down and when restarted, says it didn't shut down properly. ProblemType: Bug DistroRelease: Ubuntu 20.04 ProcVersionSignature: Ubuntu 5.15.0-53.59~20.04.1-generic 5.15.64 Uname: Linux 5.15.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Nov 24 16:34:50 2022 InstallationDate: Installed on 2022-03-19 (250 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 Snap: chromium 107.0.5304.110 (latest/stable) SnapSource: ubuntu/+source/chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1997907/+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 1993318] Re: ZFS + Encryption installations of Ubuntu Desktop do not come up correctly on first boot, systemd unmounts many of the zfs volumes
** Changed in: snapd (Ubuntu) Status: Incomplete => Invalid -- 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/1993318 Title: ZFS + Encryption installations of Ubuntu Desktop do not come up correctly on first boot, systemd unmounts many of the zfs volumes Status in Ubuntu Manual Tests: New Status in Release Notes for Ubuntu: Fix Released Status in snapd package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Status in ubiquity package in Ubuntu: Fix Released Status in zfs-linux package in Ubuntu: Confirmed Status in zsys package in Ubuntu: Invalid Bug description: This is *probably* the wrong package, but it's the best I can figure for this, so here goes. Hardware: Kubuntu Focus XE, 32 GB RAM, 1 TB SSD, 11th Gen Intel Core i5, UEFI, no secure boot. Testing done in GNOME Boxes, BIOS, 4 GB RAM, 50 GB disk space . OS is Ubuntu Desktop, Kinetic Final ISO. Steps to reproduce: 1. Boot the Ubuntu desktop ISO. 2. Select "Install Ubuntu" and proceed with the installation process. 3. When you get to the "Installation type" screen, select "Advanced Options", and enable ZFS + Encryption. 4. Proceed with the rest of the installation as normal. 5. Reboot into the newly installed system. 6. Log in. 7. Run "sudo apt update" in a terminal. Expected result: The package database should be updated normally. Actual result: You are presented with the following errors at the end of the apt output: Reading package lists... Error! E: flAbsPath on /var/lib/dpkg/status failed - realpath (2: No such file or directory) E: Could not open file - open (2: No such file or directory) E: Problem opening E: The package lists or status file could not be parsed or opened. Notes: Switching to a TTY will print a crash error message related to the same missing /var/lib/dpkg/status file. Running "sudo touch /var/lib/dpkg/status" will allow "sudo apt update" to function and fix the crashed process in the TTY. Once you log in, you'll notice that Firefox is missing (bug #1993279), and you will likely be presented with a ton of error messages and other scary junk. At least one of those error messages was related to update-manager in my experience, and another one was from "check-new- release-gtk". ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: zsys (not installed) ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Oct 18 09:55:27 2022 InstallationDate: Installed on 2022-10-18 (0 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221018) ProcEnviron: TERM=xterm-256color PATH=(custom, no username) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash 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/1993318/+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 1999924] Re: Unsupported buffer format 842094158
** Changed in: chromium-browser (Ubuntu) Status: Fix Committed => Confirmed -- 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/124 Title: Unsupported buffer format 842094158 Status in chromium-browser package in Ubuntu: Confirmed Bug description: This is with 107.0.5304.121-hwacc from latest/candidate/hwacc on Ubuntu 22.10 Wayland. When playing a h264 video, or a youtube video, I get: ``` $ snap info chromium | grep installed installed: 107.0.5304.121-hwacc(2224) 171MB - $ chromium ~/sample.mp4 Gtk-Message: 09:25:06.701: Not loading module "atk-bridge": The functionality is provided by GTK natively. Please try to not load it. [15876:15876:1216/092506.880657:ERROR:gpu_init.cc(537)] Passthrough is not supported, GL is egl, ANGLE is [15747:15837:1216/092506.908136:ERROR:top_sites_backend.cc(79)] Failed to initialize database. [15747:15747:1216/092507.059802:ERROR:wayland_event_watcher.cc(36)] libwayland: [destroyed object]: error 7: failed to import supplied dmabufs: Unsupported buffer format 842094158 Trace/breakpoint trap (core dumped) ``` Test video: https://test- videos.co.uk/vids/bigbuckbunny/mp4/h264/1080/Big_Buck_Bunny_1080_10s_30MB.mp4 I will try other hwacc versions and a non-hwacc version to see if they behave differently. OS: Ubuntu 22.10 Desktop: Wayland GPU: Intel AlderLake-S GT1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/124/+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 2002978] Re: sh[1111]: /bin/sh: 1: initctl: not found
The issue was fixed in https://launchpad.net/ubuntu/+source/gnome- keyring/42.1-1 indeed. It might still be worth fixing in the LTS ** Changed in: gnome-keyring (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-keyring (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/2002978 Title: sh[]: /bin/sh: 1: initctl: not found Status in gnome-keyring package in Ubuntu: Fix Released Bug description: Just an unexpected error logged, no further issues from this. /usr/lib/systemd/user/gnome-keyring-ssh.service from gnome-keyring=40.0-3ubuntu3 (22.04.1) calls initctl from a systemd user service. Looks like 42.1-1 sets SSH_AUTH_SOCK without such user unit, so the problem may be resolved in current versions (though not in LTS). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/2002978/+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 1969637] Re: IBus lookup table appears bottom left of application (x11)
It seems there is still an edge case issue.
ctrl+; wouldn't work (eg: in gedit) on my freshly rebooted host, with up to
date softwares proprietary nvidia drivers, Xorg and gnome on a 22.04
release-upgraded from a 21.10 initial installation)
ctrl+; was working with `GTK_IM_MODULE=ibus gedit` (with an underlined
'e' where I could type an emoji name to select it, a different interface
than what follows)
I then installed (for the first time) both xsettingsd and
unity-settings-daemon-schemas and ctrl+; was working in gedit (showing black or
at least theme colored background box with emoji pictures) but not in
gnome-terminal (even with `GTK_IM_MODULE=ibus gnome-terminal`)
The following env var hadn't changed:
XMODIFIERS=@im=ibus
GTK_MODULES=gail:atk-bridge
QT_IM_MODULE=ibus
(GTK_IM_MODULE was still unset)
I then uninstalled xsettingsd and unity-settings-daemon-schemas (also
tried with --purge) and ctrl+; still works with gedit and still doesn't
with gnome-terminal, even with a fresh reboot.
note : I have a "French Alt." keyboard layout
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to im-config in Ubuntu.
https://bugs.launchpad.net/bugs/1969637
Title:
IBus lookup table appears bottom left of application (x11)
Status in GNOME Settings Daemon:
Fix Released
Status in ibus:
Fix Released
Status in gnome-settings-daemon package in Ubuntu:
Fix Released
Status in im-config package in Ubuntu:
Fix Released
Status in gnome-settings-daemon source package in Jammy:
Fix Released
Status in im-config package in Debian:
Fix Released
Status in openSUSE:
Fix Released
Bug description:
[Impact]
Changes in gnome-settings-daemon v. 42 resulted in IM issues in GNOME
on Xorg. On Ubuntu the effect is that the candidate window is
misplaced, and appears at the bottom of the application window instead
of close to the cursor. It's an annoying enough issue to justify an
SRU.
[Test Plan]
On an updated Ubuntu 22.04:
1. Install ibus-libpinyin
2. Run these commands:
sudo locale-gen zh_CN.UTF-8
sudo update-locale LC_CTYPE=zh_CN.UTF-8
3. Reboot and log in to an Ubuntu on Xorg session
4. Add "Intelligent Pinyin" to the input sources
5. Open gedit, switch to "Intelligent Pinyin", and input something.
=> Find that the candidate window is misplaced.
6. Install gnome-settings-daemon{,-common} from jammy-proposed and
reboot
7. Repeat step 5.
=> Find that the candidate window is shown close to the cursor as
expected.
[Where problems could occur]
The change is an upstream MR and a one-liner. It shouldn't reasonably
affect anything but ibus configuration, and I have successfully tested
it back and forth in both x11 and wayland sessions.
[Other Info]
This change has not yet reached kinetic, but will do so later when
g-s-d is upgraded. The issue has temporarily been addressed in Debian
(and soon in kinetic via sync) through an im-config workaround, which
will be dropped later when g-s-d is updated. But for an SRU I think
it's better to make the more proper g-s-d change directly.
[Original description]
I know it is not im-config issue. I don't know what is root cause.
how to reproduce:
1. Install Ubuntu 22.04 LTS or apply newest update
2. boot
3. select a user
4. select Ubuntu on Xorg
5. input password
6. login
7. run gedit
8. push Hankaku/Zenkaku key
9. input any keys
10. lookup table appears bottom left of application
proposed fix:
edit DESKTOP_SETUP_IBUS="GNOME" to DESKTOP_SETUP_IBUS="" on
/etc/default/im-config
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: im-config 0.50-2
ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
Uname: Linux 5.15.0-25-generic x86_64
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu Apr 21 00:13:10 2022
InstallationDate: Installed on 2022-04-20 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220415)
PackageArchitecture: all
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=ja_JP.UTF-8
SHELL=/bin/bash
SourcePackage: im-config
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-settings-daemon/+bug/1969637/+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 1232872]
I've just re-tested with Libre Office 7.3.7.2 from my Ubuntu 22.04 machine, and it seems to me that the problem is no longer present: opening a file via NFS does not stall anymore. -- 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/1232872 Title: [upstream] NFS / lock problem with LibreOffice wth 13.04 Status in LibreOffice: Confirmed Status in libreoffice package in Ubuntu: Confirmed Bug description: Hi all, I have a problem very similar to what is exposed in question #234375. Since I upgraded to Ubuntu 13.04 (host x86_64), I have trouble accessing documents via NFS with LibreOffice. The slash screen display for about 30s, then there is a popup warning saying that another user has opened the file, and offering to open a copy, open as readonly or cancel. The point is, no other user has opened that file (being the only user on my personal PC, but storing my documents on NAS). So I tried the suggestion about adding "noauto" in /etc/fstab and changing /etc/rc.local, with no luck. But the modification of /usr/lib/libreoffice/program/soffice: ## # STAR_PROFILE_LOCKING_DISABLED=1 export STAR_PROFILE_LOCKING_DISABLED # # file locking now enabled by default #SAL_ENABLE_FILE_LOCKING=1 # <<- if set to 0 ; same trouble ... #export SAL_ENABLE_FILE_LOCKING ### (That is, uncomment the first 2 lines, and commenting the other 2) This works OK. If this is the official way of fixing things, then I guess LibreOffice deserves an update on Ubuntu at least. Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1232872/+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 2002978] [NEW] sh[1111]: /bin/sh: 1: initctl: not found
Public bug reported: Just an unexpected error logged, no further issues from this. /usr/lib/systemd/user/gnome-keyring-ssh.service from gnome-keyring=40.0-3ubuntu3 (22.04.1) calls initctl from a systemd user service. Looks like 42.1-1 sets SSH_AUTH_SOCK without such user unit, so the problem may be resolved in current versions (though not in LTS). ** Affects: gnome-keyring (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/2002978 Title: sh[]: /bin/sh: 1: initctl: not found Status in gnome-keyring package in Ubuntu: New Bug description: Just an unexpected error logged, no further issues from this. /usr/lib/systemd/user/gnome-keyring-ssh.service from gnome-keyring=40.0-3ubuntu3 (22.04.1) calls initctl from a systemd user service. Looks like 42.1-1 sets SSH_AUTH_SOCK without such user unit, so the problem may be resolved in current versions (though not in LTS). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/2002978/+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 1991761] Re: Backport packages for 22.04.2 HWE stack
** Changed in: spirv-llvm-translator-14 (Ubuntu Jammy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1991761 Title: Backport packages for 22.04.2 HWE stack Status in directx-headers package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-15 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in spirv-headers package in Ubuntu: Invalid Status in spirv-llvm-translator-14 package in Ubuntu: Invalid Status in spirv-llvm-translator-15 package in Ubuntu: Invalid Status in directx-headers source package in Jammy: Fix Committed Status in libdrm source package in Jammy: Fix Committed Status in llvm-toolchain-15 source package in Jammy: Fix Committed Status in mesa source package in Jammy: Fix Committed Status in spirv-headers source package in Jammy: Fix Committed Status in spirv-llvm-translator-14 source package in Jammy: Fix Committed Status in spirv-llvm-translator-15 source package in Jammy: Fix Committed Bug description: [Impact The graphics HWE stack from kinetic needs to be backported for 22.04.2 directx-headers - build-dep of the new Mesa libdrm - build-dep of the new Mesa llvm-15 - new package in jammy - build-dep of the new Mesa mesa - new major release (22.2.x) - new HW support, like AMD RDNA3, Intel DG2 spirv-headers - needed by s-l-t-15 spirv-llvm-translator-14 - needed to bootstrap libclc from llvm spirv-llvm-translator-15 - needed for the actual libclc-15 after initial bootstrap Bootstrapping plan: - s-l-t-14 built from NEW - llvm-15 built with s-l-t-14 - s-l-t-15 built against llvm-15 - llvm-15 built again with s-l-t-15 -> mesa ready for building [Test case] Install the new mesa on various hw, see that everything still works like before or better. spirv-headers: - test reverse-build-deps that they still build Reverse-Build-Depends * glslang * intel-graphics-compiler * spirv-llvm-translator-14 * spirv-llvm-translator-15 * spirv-tools * vkbasalt * vkd3d * vulkan-validationlayers [Where things could go wrong] This is a major update of Mesa, there could be regressions but we'll backport the final stable release of 22.2.x in order to minimize the chance for those. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/directx-headers/+bug/1991761/+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 1971712] Re: Add support for Intel DG2
and is there now -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1971712 Title: Add support for Intel DG2 Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Fix Released Status in linux-firmware source package in Jammy: Fix Released Status in linux-oem-5.17 source package in Jammy: Won't Fix Status in linux-oem-6.1 source package in Jammy: Fix Released Status in mesa source package in Jammy: Fix Released Status in linux-firmware source package in Kinetic: Fix Released Bug description: [Impact] Ubuntu 22.04 does not support Intel DG2-based hw which is released later this year. [Fix] Mesa: needs a bunch of patches backported to 22.0.x, will be upstream in 22.1 or 22.2 kernel: oem-6.0 plus a bunch of backports from 6.1/drm-tip firmare: updates to i915 DMC, GuC [Test case] Boot a system with a DG2-based GPU, check that native graphics drivers are used. Test mesa also on gen9-gen12 GPU's to verify that there are no regressions even though the backports are for DG2. [What could go wrong] The Mesa patches are only for DG2 support, should not affect other hardware at all. The kernel driver is in a separate package which isn't installed by default except preinstall machines with this hardware. So other users are not affected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1971712/+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 1959103] Re: polkitd crashes with segfault with specific config file
The attachment "fix-config-error-handling.patch" seems to be a patch.
If it isn't, please remove the "patch" flag from the attachment, remove
the "patch" tag, and if you are a member of the ~ubuntu-reviewers,
unsubscribe the team.
[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]
** Tags added: patch
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to policykit-1 in Ubuntu.
https://bugs.launchpad.net/bugs/1959103
Title:
polkitd crashes with segfault with specific config file
Status in policykit-1 package in Ubuntu:
Confirmed
Bug description:
The following config file in
`/etc/polkit-1/localauthority.conf.d/02-allow-colord.conf` can cause a
segfault in `polkitd`.
```
polkit.addRule(function(action, subject) {
if ((action.id == "org.freedesktop.color-manager.create-device" ||
action.id == "org.freedesktop.color-manager.create-profile" ||
action.id == "org.freedesktop.color-manager.delete-device" ||
action.id == "org.freedesktop.color-manager.delete-profile" ||
action.id == "org.freedesktop.color-manager.modify-device" ||
action.id == "org.freedesktop.color-manager.modify-profile") &&
subject.isInGroup("{group}")) {
return polkit.Result.YES;
}
});
```
1. As normal user: `systemctl restart cron.service`
2. Error message `Failed to restart cron.service: Message recipient
disconnected from message bus without replying`
3. `dmesg` reports:
```
58.003893] polkitd[963]: segfault at 8 ip 558a96789856 sp
7ffda31e45f0 error 4 in polkitd[558a96784000+f000]
[ 58.003899] Code: 50 c7 ff ff 4d 89 e5 48 89 44 24 08 eb 53 66 0f 1f 44 00
00 48 8b 44 24 10 48 89 e9 be 10 00 00 00 31 ff 48 8d 15 0b af 00 00 <4c> 8b 40
08 31 c0 e8 af cb ff ff 48 8b 7c 24 10 e8 65 c9 ff ff 4c
``
If you remove the 02-allow-colord.conf the segfault goes away and you
are normally prompted for a password. You can also find a couple of
references in the internet, e.g http://c-nergy.be/blog/?p=12043.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1959103/+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 1969637] Re: IBus lookup table appears bottom left of application (x11)
running
`echo GTK_IM_MODULE=ibus | sudo tee /etc/environment.d/99inputemoji.conf`
I have it working on both gedit and gnome-terminal (with the underlined 'e'
interface) after a reboot
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to im-config in Ubuntu.
https://bugs.launchpad.net/bugs/1969637
Title:
IBus lookup table appears bottom left of application (x11)
Status in GNOME Settings Daemon:
Fix Released
Status in ibus:
Fix Released
Status in gnome-settings-daemon package in Ubuntu:
Fix Released
Status in im-config package in Ubuntu:
Fix Released
Status in gnome-settings-daemon source package in Jammy:
Fix Released
Status in im-config package in Debian:
Fix Released
Status in openSUSE:
Fix Released
Bug description:
[Impact]
Changes in gnome-settings-daemon v. 42 resulted in IM issues in GNOME
on Xorg. On Ubuntu the effect is that the candidate window is
misplaced, and appears at the bottom of the application window instead
of close to the cursor. It's an annoying enough issue to justify an
SRU.
[Test Plan]
On an updated Ubuntu 22.04:
1. Install ibus-libpinyin
2. Run these commands:
sudo locale-gen zh_CN.UTF-8
sudo update-locale LC_CTYPE=zh_CN.UTF-8
3. Reboot and log in to an Ubuntu on Xorg session
4. Add "Intelligent Pinyin" to the input sources
5. Open gedit, switch to "Intelligent Pinyin", and input something.
=> Find that the candidate window is misplaced.
6. Install gnome-settings-daemon{,-common} from jammy-proposed and
reboot
7. Repeat step 5.
=> Find that the candidate window is shown close to the cursor as
expected.
[Where problems could occur]
The change is an upstream MR and a one-liner. It shouldn't reasonably
affect anything but ibus configuration, and I have successfully tested
it back and forth in both x11 and wayland sessions.
[Other Info]
This change has not yet reached kinetic, but will do so later when
g-s-d is upgraded. The issue has temporarily been addressed in Debian
(and soon in kinetic via sync) through an im-config workaround, which
will be dropped later when g-s-d is updated. But for an SRU I think
it's better to make the more proper g-s-d change directly.
[Original description]
I know it is not im-config issue. I don't know what is root cause.
how to reproduce:
1. Install Ubuntu 22.04 LTS or apply newest update
2. boot
3. select a user
4. select Ubuntu on Xorg
5. input password
6. login
7. run gedit
8. push Hankaku/Zenkaku key
9. input any keys
10. lookup table appears bottom left of application
proposed fix:
edit DESKTOP_SETUP_IBUS="GNOME" to DESKTOP_SETUP_IBUS="" on
/etc/default/im-config
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: im-config 0.50-2
ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
Uname: Linux 5.15.0-25-generic x86_64
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu Apr 21 00:13:10 2022
InstallationDate: Installed on 2022-04-20 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220415)
PackageArchitecture: all
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=ja_JP.UTF-8
SHELL=/bin/bash
SourcePackage: im-config
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-settings-daemon/+bug/1969637/+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 1998950] Re: GPU hang on Alder Lake laptop
I don't see this happening anymore as of the release of linux- image-5.19.0-28-generic. Neither the -28 nor the -29 kernel seem to cause this to happen anymore, so I suspect this can probably be closed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1998950 Title: GPU hang on Alder Lake laptop Status in Linux: New Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Bug description: I see frequent (multiple times per day) hangs on my Lenovo ThinkPad X1 Carbon Gen 10. When this occurs, part of the image tears away and X becomes unusable. Sometimes the cursor continues to move for a short time after the fact. In order to recover, I must SSH into the machine and run `sudo killall -9 Xorg`, which drops me back to the lightdm login screen and then things work again. I've also seen this on Debian sid on a nearly identical machine, and there when upgrading to kernel 6.0 and Mesa 22.3, the problem disappears. However, those are not available in Kinetic. I've tried both `i915.enable_psr=0` and `i915.enable_dc=0` as boot parameters and this does not affect anything. The problem has been occurring since I installed Ubuntu on this machine when I got it on November 17. I believe the upstream bug report is this: https://gitlab.freedesktop.org/drm/intel/-/issues/6757. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-26.27-generic 5.19.7 Uname: Linux 5.19.0-26-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: MATE Date: Tue Dec 6 16:42:04 2022 DistUpgraded: Fresh install DistroCodename: kinetic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation Alder Lake-P Integrated Graphics Controller [8086:46a6] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Lenovo Alder Lake-P Integrated Graphics Controller [17aa:22e7] InstallationDate: Installed on 2022-11-17 (18 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: LENOVO 21CBCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-26-generic root=/dev/mapper/vgubuntu-root ro i915.enable_dc=0 quiet splash i915.enable_dc=0 vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/02/2022 dmi.bios.release: 1.30 dmi.bios.vendor: LENOVO dmi.bios.version: N3AET65W (1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 21CBCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0T76461 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.14 dmi.modalias: dmi:bvnLENOVO:bvrN3AET65W(1.30):bd08/02/2022:br1.30:efr1.14:svnLENOVO:pn21CBCTO1WW:pvrThinkPadX1CarbonGen10:rvnLENOVO:rn21CBCTO1WW:rvrSDK0T76461WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21CB_BU_Think_FM_ThinkPadX1CarbonGen10: dmi.product.family: ThinkPad X1 Carbon Gen 10 dmi.product.name: 21CBCTO1WW dmi.product.sku: LENOVO_MT_21CB_BU_Think_FM_ThinkPad X1 Carbon Gen 10 dmi.product.version: ThinkPad X1 Carbon Gen 10 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.1-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-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 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1998950/+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 1986451] Re: Can't click context menu items when they cover the dock (in a Xorg session)
I found more reports: https://youtrack.jetbrains.com/issue/IDEA-145727/Context-menu-item- cannot-be-clicked-when-overlaps-the-top-Gnome-bar https://youtrack.jetbrains.com/issue/IDEA-286370/Cant-click-menu-items- over-Ubuntu-task-bar. This error has been around for 5 years. -- 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/1986451 Title: Can't click context menu items when they cover the dock (in a Xorg session) Status in Dash to dock: Unknown Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: ubuntu dock in bottom position won't let me click on button (convert java file to Kotlin file) in android studio, but in the left position everything works correctly. That is, if the menu android studio overlaps the ubuntu dock, then the menu buttons will not be pressed. https://youtu.be/KsOVG7Uucow ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 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 CasperMD5CheckResult: pass CompositorRunning: None Date: Sun Aug 14 10:52:56 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: openrazer-driver/3.4.0, 5.15.0-43-generic, x86_64: installed openrazer-driver/3.4.0, 5.15.0-46-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Xiaomi UHD Graphics 620 [1d72:1701] Subsystem: Xiaomi Mi Notebook Pro [GeForce MX150] [1d72:1701] InstallationDate: Installed on 2022-07-13 (31 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Timi TM1701 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=7c5eaac1-9b38-4169-8a20-0fef5e97c644 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/02/2018 dmi.bios.release: 106.121 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: XMAKB5R0P0603 dmi.board.asset.tag: Any dmi.board.name: TM1701 dmi.board.vendor: Timi dmi.board.version: MP dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Timi dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 0.3 dmi.modalias: dmi:bvnINSYDECorp.:bvrXMAKB5R0P0603:bd02/02/2018:br106.121:efr0.3:svnTimi:pnTM1701:pvr:rvnTimi:rnTM1701:rvrMP:cvnTimi:ct10:cvrChassisVersion:sku: dmi.product.family: Timibook dmi.product.name: TM1701 dmi.sys.vendor: Timi 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.nvidia-graphics-drivers: nvidia-graphics-drivers-* 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 To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1986451/+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 1990563] Re: Some maximized/fullscreen windows appear on both monitors
This bug was fixed in the package mutter - 43.2-4ubuntu1 --- mutter (43.2-4ubuntu1) lunar; urgency=medium * Merge with Debian. Remaining change: - Add x11-Add-support-for-fractional-scaling-using-Randr.patch mutter (43.2-4) unstable; urgency=medium * Team upload * Mark xwayland test-case as known to be flaky on 32-bit ARM. Mitigates: #1026445 mutter (43.2-3) unstable; urgency=medium * Team upload * Rebuild source package with non-expired signing key mutter (43.2-2) unstable; urgency=medium * Team upload * d/p/workspace-Don-t-crash-on-invalid-argument-to-meta_workspa.patch: Add proposed patch to avoid crashing on an invalid argument * d/p/tests-Break-up-stacking-installed-tests-into-more-smaller.patch: Add proposed patch to have more, smaller installed-tests. As well as doing what it was intended to do, this also avoids a crash during autopkgtest. (Mitigates: #1024438) mutter (43.2-1) unstable; urgency=medium * New upstream release * Update symbols files mutter (43.1-2) unstable; urgency=medium * Team upload * Disable restore-size test. This avoids intermittent FTBFS, especially on armel and armhf. * Build-/test-depend on dbus-daemon instead of dbus * d/upstream/metadata: Add Repository field mutter (43.1-1) unstable; urgency=medium * Team upload * New upstream release - Among other fixes, this avoids a fullscreen window on one display being replicated on another display (Closes: #1023256, LP: #1990563) * Refresh patch series - Drop patches that were included upstream - Update triple-buffering patch from GNOME/mutter!1441 * Set field Upstream-Name in debian/copyright. * d/upstream/metadata: Add * Update symbols file for new upstream release * Reduce entropy of .symbols file. The SONAME changed in version 43~beta, so there's no point in keeping track of whether symbols are older than that version. Similarly, if a symbol was introduced in a prerelease, we want dependent packages to depend on the final release, so there's little point in finer-grained tracking of which specific prerelease each symbol came from. mutter (43.0-3) unstable; urgency=medium * Cherry-pick patch to fix Night Light availability in GNOME Settings (Closes: #1020941) (LP: #1990207) * Cherry-pick patches to avoid crash when ICC color profile is invalid (Closes: #1021680) (LP: #1993114) mutter (43.0-2) unstable; urgency=medium * Release to unstable (Closes: #1009990, #1019266, #1020515) -- Jeremy Bicha Tue, 27 Dec 2022 15:00:07 -0900 ** Changed in: mutter (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1990563 Title: Some maximized/fullscreen windows appear on both monitors Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Released Bug description: I have a dual monitor setup, with external monitor configured as primary. When I maximize certain windows on the secondary monitor, a copy of the same window appears on the primary monitor (see first attached video). It happens with some apps, not with all of them. For example, it happens with IntelliJ IDEA (Java app) and Spotify (presumably Electron app), not with Gnome Text Editor, Gnome Terminal, Chrome or Firefox, for instance. A very similar situation occurs when taking a screenshot with Flameshot, though in the opposite way: a copy of the primary monitor appears on the secondary (see second attached video). ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: mutter 43.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Thu Sep 22 14:37:37 2022 InstallationDate: Installed on 2018-12-14 (1378 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: mutter UpgradeStatus: Upgraded to kinetic on 2022-09-02 (20 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1990563/+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 1969637] Re: IBus lookup table appears bottom left of application (x11)
@Romain: This bug is closed. Please submit a new bug about that issue:
ubuntu-bug ibus
(I appreciate if you do, because I think that problem area is worth a
separate discussion.)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to im-config in Ubuntu.
https://bugs.launchpad.net/bugs/1969637
Title:
IBus lookup table appears bottom left of application (x11)
Status in GNOME Settings Daemon:
Fix Released
Status in ibus:
Fix Released
Status in gnome-settings-daemon package in Ubuntu:
Fix Released
Status in im-config package in Ubuntu:
Fix Released
Status in gnome-settings-daemon source package in Jammy:
Fix Released
Status in im-config package in Debian:
Fix Released
Status in openSUSE:
Fix Released
Bug description:
[Impact]
Changes in gnome-settings-daemon v. 42 resulted in IM issues in GNOME
on Xorg. On Ubuntu the effect is that the candidate window is
misplaced, and appears at the bottom of the application window instead
of close to the cursor. It's an annoying enough issue to justify an
SRU.
[Test Plan]
On an updated Ubuntu 22.04:
1. Install ibus-libpinyin
2. Run these commands:
sudo locale-gen zh_CN.UTF-8
sudo update-locale LC_CTYPE=zh_CN.UTF-8
3. Reboot and log in to an Ubuntu on Xorg session
4. Add "Intelligent Pinyin" to the input sources
5. Open gedit, switch to "Intelligent Pinyin", and input something.
=> Find that the candidate window is misplaced.
6. Install gnome-settings-daemon{,-common} from jammy-proposed and
reboot
7. Repeat step 5.
=> Find that the candidate window is shown close to the cursor as
expected.
[Where problems could occur]
The change is an upstream MR and a one-liner. It shouldn't reasonably
affect anything but ibus configuration, and I have successfully tested
it back and forth in both x11 and wayland sessions.
[Other Info]
This change has not yet reached kinetic, but will do so later when
g-s-d is upgraded. The issue has temporarily been addressed in Debian
(and soon in kinetic via sync) through an im-config workaround, which
will be dropped later when g-s-d is updated. But for an SRU I think
it's better to make the more proper g-s-d change directly.
[Original description]
I know it is not im-config issue. I don't know what is root cause.
how to reproduce:
1. Install Ubuntu 22.04 LTS or apply newest update
2. boot
3. select a user
4. select Ubuntu on Xorg
5. input password
6. login
7. run gedit
8. push Hankaku/Zenkaku key
9. input any keys
10. lookup table appears bottom left of application
proposed fix:
edit DESKTOP_SETUP_IBUS="GNOME" to DESKTOP_SETUP_IBUS="" on
/etc/default/im-config
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: im-config 0.50-2
ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
Uname: Linux 5.15.0-25-generic x86_64
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu Apr 21 00:13:10 2022
InstallationDate: Installed on 2022-04-20 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220415)
PackageArchitecture: all
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=ja_JP.UTF-8
SHELL=/bin/bash
SourcePackage: im-config
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-settings-daemon/+bug/1969637/+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 1943752] Re: cheese does not work with laptop webcam in Ubuntu 21.10+
Ubuntu 20.04 was the last version of Ubuntu desktop that Cheese worked as expected. AlmaLinux 9.1 Cheese works as expected. Fedora 36 Cheese works as expected. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cheese in Ubuntu. https://bugs.launchpad.net/bugs/1943752 Title: cheese does not work with laptop webcam in Ubuntu 21.10+ Status in cheese package in Ubuntu: Confirmed Bug description: Ubuntu 21.10 from live usb on a HP 840 G3 laptop 1.Ubuntu Impish Indri (development branch) 2.cheese version installed: 3.38.0-4, candidate: 3.38.0-4 version table:***3.38.0-4 500 3.cheese should display an image from laptop camera after being opened. 4.The error has reproduced by me on this hardware at least 4 times. When opening the cheese app no image is displayed until closing and reopening the app at least 3 times. The cheese app works as expected in both Ubuntu 18.04 and Ubuntu 20.04. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: cheese 3.38.0-4 ProcVersionSignature: Ubuntu 5.13.0-14.14-generic 5.13.1 Uname: Linux 5.13.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu68 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.465 CurrentDesktop: ubuntu:GNOME Date: Wed Sep 15 17:10:23 2021 LiveMediaBuild: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210915) MachineType: HP HP EliteBook 840 G3 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: cheese3.38.0-4 cheese-common 3.38.0-4 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/20/2021 dmi.bios.release: 1.52 dmi.bios.vendor: HP dmi.bios.version: N75 Ver. 01.52 dmi.board.name: 8079 dmi.board.vendor: HP dmi.board.version: KBC Version 85.79 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 133.121 dmi.modalias: dmi:bvnHP:bvrN75Ver.01.52:bd04/20/2021:br1.52:efr133.121:svnHP:pnHPEliteBook840G3:pvr:sku2FZ00UP#ABA:rvnHP:rn8079:rvrKBCVersion85.79:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP EliteBook dmi.product.name: HP EliteBook 840 G3 dmi.product.sku: 2FZ00UP#ABA dmi.sys.vendor: HP lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04f2:b51c Chicony Electronics Co., Ltd HP HD Camera Bus 001 Device 003: ID 138a:003f Validity Sensors, Inc. VFS495 Fingerprint Reader Bus 001 Device 002: ID 154b:0054 PNY USB 2.0 FD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu68 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 5074 F pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.465 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.10 LiveMediaBuild: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210915) Lsusb: Bus 002 Device 002: ID 0781:5581 SanDisk Corp. Ultra Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b51c Chicony Electronics Co., Ltd HP HD Camera Bus 001 Device 002: ID 138a:003f Validity Sensors, Inc. VFS495 Fingerprint Reader Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP EliteBook 840 G3 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- ProcVersionSignature: Ubuntu 5.13.0-14.14-generic 5.13.1 RelatedPackageVersions: linux-restricted-modules-5.13.0-14-generic N/A linux-backports-modules-5.13.0-14-generic N/A linux-firmware 1.199 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: impish Uname: Linux 5.13.0-14-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/20/2021 dmi.bios.release: 1.52 dmi.bios.vendor: HP dmi.bios.version: N75 Ver. 01.52 dmi.board.name: 8079 dmi.board.vendor: HP dmi.board.version: KBC Version 85.79 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 133.121 dmi.modalias: dmi:bvnHP:bvrN75Ver.01.52:bd04/20/2021:br1.52:efr133.121:svnHP:pnHPEliteBook840G3:pvr:sku2FZ00UP#ABA:rvnHP:rn8079:rvrKBCVersion85.79:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP EliteBook dmi.product.name: HP EliteBook 840 G3 dmi.product.sku: 2FZ00UP#ABA dmi.sys.vendor: HP To manage notifications about this
[Desktop-packages] [Bug 1917887] Re: Network Manager OpenVPN nested connections fail to setup routes correctly
The following changes were applied upstream to fix this issue in network-manager: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/1491/diffs -- 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/1917887 Title: Network Manager OpenVPN nested connections fail to setup routes correctly Status in OpenVPN: Fix Released Status in network-manager package in Ubuntu: Triaged Status in openvpn package in Ubuntu: Invalid Bug description: Setup: Host lan: 192.168.0.238/24 Host Default gw: 192.168.0.1 ip route: default via 192.168.0.1 dev eno1 proto dhcp metric 100 169.254.0.0/16 dev eno1 scope link metric 1000 192.168.0.0/24 dev eno1 proto kernel scope link src 192.168.0.238 metric 100 Primary OpenVPN (check "Use this connection only for resources on its network"): server ip: public a.b.c.d OpenVPN Tunnel: 192.168.1.0/24 routes pushed: 192.168.100.0/24 First VPN works OK: default via 192.168.0.1 dev eno1 proto dhcp metric 100 169.254.0.0/16 dev eno1 scope link metric 1000 192.168.0.0/24 dev eno1 proto kernel scope link src 192.168.0.238 metric 100 192.168.0.1 dev eno1 proto static scope link metric 100 192.168.100.0/24 via 192.168.10.1 dev tun0 proto static metric 50 a.b.c.d via 192.168.0.1 dev eno1 proto static metric 100 Secondary OpenVPN (check "Use this connection only for resources on its network"): server ip: private 192.168.100.10 OpenVPN Tunnel: 192.168.20.0/24 routes pushed: 192.168.200.0/24 Second VPN Connect OK, routing table is wrong: default via 192.168.0.1 dev eno1 proto dhcp metric 100 192.168.200.0/24 via 192.168.20.1 dev tun1 192.168.20.0/24 dev tun1 proto kernel scope link src 192.168.20.59 169.254.0.0/16 dev eno1 scope link metric 1000 192.168.0.0/24 dev eno1 proto kernel scope link src 192.168.0.238 metric 100 192.168.0.1 dev eno1 proto static scope link metric 100 192.168.100.0/24 via 192.168.10.1 dev tun0 proto static metric 50 a.b.c.d via 192.168.0.1 dev eno1 proto static metric 100 192.168.100.10 via 192.168.0.1 dev eno1 proto static metric 100 <- this is wrong, the openVPN#2 Gateway is not on the local lan Correct routing table using "sudo /usr/sbin/openvpn /path/to/config.openvpn" (same a Network Manager) default via 192.168.0.1 dev eno1 proto dhcp metric 100 192.168.200.0/24 via 192.168.20.1 dev tun1 192.168.20.0/24 dev tun1 proto kernel scope link src 192.168.20.59 169.254.0.0/16 dev eno1 scope link metric 1000 192.168.0.0/24 dev eno1 proto kernel scope link src 192.168.0.238 metric 100 192.168.0.1 dev eno1 proto static scope link metric 100 192.168.100.0/24 via 192.168.10.1 dev tun0 proto static metric 50 a.b.c.d via 192.168.0.1 dev eno1 proto static metric 100 It seems that Network Manager add a wrong additional route not added by the openvpn bin: 192.168.100.10 via 192.168.0.1 dev eno1 proto static metric 100 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: openvpn 2.4.7-1ubuntu2 ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Mar 5 12:44:39 2021 InstallationDate: Installed on 2021-02-19 (13 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: openvpn UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/openvpn/+bug/1917887/+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 2002926] Re: GNOME Console doesn't copy last line
This bug was fixed in the package vte2.91 - 0.70.2-2 --- vte2.91 (0.70.2-2) unstable; urgency=high * Cherry-pick fix for GNOME Console 43 copying last line (Closes: #1017015) (LP: #2002926) -- Jeremy Bicha Sun, 15 Jan 2023 19:27:32 -0500 ** Changed in: vte2.91 (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vte2.91 in Ubuntu. https://bugs.launchpad.net/bugs/2002926 Title: GNOME Console doesn't copy last line Status in vte2.91 package in Ubuntu: Fix Released Status in vte2.91 source package in Kinetic: In Progress Bug description: Impact -- GNOME Console 43 has switched to GTK4 and the final line of text isn't being copied. If there is only one line you are trying to copy, the clipboard is apparently empty. Test Case - Install the updated vte packages and gnome-console. Run the Console app. Run this command: cat /etc/os-release Copy a selection that includes the end of the line. One easy way to do this is to triple-click the line. Then right-click and choose Copy. Then right-click and choose Paste. All the lines should be pasted including the final line. What Could Go Wrong --- This is a one line fix that modifies a function (vte_terminal_get_text_selected) that is only used by GNOME Builder and GNOME Console. (GNOME Builder is affected by the same bug). Neither GNOME Builder nor GNOME Console are included by default in any Ubuntu flavor. GNOME Console may replace GNOME Terminal as the default terminal app for Ubuntu Desktop in a future Ubuntu release. This bug was a blocker for that happening. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vte2.91/+bug/2002926/+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 1997099] Re: Alt + Tab gives focus to the always-on-top window
mutter (43.2-4ubuntu1) lunar; urgency=medium ** Changed in: mutter (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1997099 Title: Alt + Tab gives focus to the always-on-top window Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Released Bug description: With an always-on-top window opened, Alt + Tab will, instead of giving (keyboard) focus to the chosen window, focus will go to the always-on- top window. Reproducing steps: 1. Make sure your Ubuntu session is a Wayland session. 2. Open Firefox. Make sure it uses Wayland, launch with `env MOZ_ENABLE_WAYLAND=1 firefox`. 3. Play a YouTube video, and then clicks the Picture-in-Picture buttton. 4. Due to Wayland limitation, right-click on the PiP window and choose "Always on top". 5. Open another window of anything e.g. a terminal. 6. Press Alt + Tab to switch to the browser. Expected result: focus goes to the browser. If on YouTube, you should be able to press '/' and cursor should go to the search box. Actual result: focus goes to the PiP window. This also happens if e.g. you use Alt + Shift to change keyboard languages. The system is Ubuntu 22.04 running Gnome-shell-based, Wayland, Ubuntu session. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.5-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-53.59-generic 5.15.64 Uname: Linux 5.15.0-53-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Nov 18 23:16:42 2022 DisplayManager: gdm3 InstallationDate: Installed on 2021-03-15 (612 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=th_TH.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.5-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-10-22 (26 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1997099/+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 1988256] Re: gnome-shell crashed with SIGSEGV in meta_get_first_subsurface_node() from pointer_can_grab_surface() from meta_wayland_pointer_can_grab_surface() from meta_wayland
mutter (43.2-4ubuntu1) lunar; urgency=medium ** Changed in: mutter (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1988256 Title: gnome-shell crashed with SIGSEGV in meta_get_first_subsurface_node() from pointer_can_grab_surface() from meta_wayland_pointer_can_grab_surface() from meta_wayland_seat_get_grab_info() from token_can_activate() Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 43~beta-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/6582f375d7b1e6bec0fdee2e9d2ec574844a8457 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. Also https://errors.ubuntu.com/problem/f3d88d48bae2b5c8c883c91ee37f390d0887819d To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1988256/+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 1994519] Re: DisplayLink display is black on plug-in and mutter crash after moving cursor on DisplayLink display.
mutter (43.2-4ubuntu1) lunar; urgency=medium
** Changed in: mutter (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1994519
Title:
DisplayLink display is black on plug-in and mutter crash after moving
cursor on DisplayLink display.
Status in Mutter:
Fix Released
Status in mutter package in Ubuntu:
Fix Released
Bug description:
This is recent regression with reproduction rate 100%.
This is regression mutter-43, Ubuntu 22.04 works fine.
Bug is raised on Gnome/mutter:
https://gitlab.gnome.org/GNOME/mutter/-/issues/2481
Fix is under review:
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2676
### Steps to reproduce
1. Login
2. Attach DisplayLink device with display connected
3. Notice that display is visible in Display Preferences but display stays
blank.
4. Move cursor over DisplayLink display.
5. Mutter crashes.
### What happened
Mutter crashes, user is asked to log-in again.
### What did you expect to happen
Mutter does not crash.
### Relevant logs, screenshots, screencasts etc.
Crash in line:
https://gitlab.gnome.org/GNOME/mutter/-/blob/main/src/backends/native/meta-renderer-native.c#L226
Crash backtrace:
```
Thread 1 "gnome-shell" received signal SIGSEGV, Segmentation fault.
0x7f9209c35329 in meta_gbm_device_from_gpu (gpu_kms=0x55eb13bc9e00) at
../src/backends/native/meta-renderer-native.c:204
204 render_device = renderer_gpu_data->render_device;
(gdb) bt
#0 0x7f9209c35329 in meta_gbm_device_from_gpu (gpu_kms=0x55eb13bc9e00)
at ../src/backends/native/meta-renderer-native.c:204
#1 0x7f9209c06674 in create_cursor_drm_buffer (gpu_kms=0x55eb13bc9e00,
device_file=0x55eb15eaa860, pixels=0x7f91b4bb9700 "", width=24, height=24,
stride=96, cursor_width=64, cursor_height=64, format=875713089,
error=0x7ffda9443108) at
../src/backends/native/meta-cursor-renderer-native.c:1329
#2 0x7f9209c068b9 in load_cursor_sprite_gbm_buffer_for_gpu
(native=0x55eb1617f580, gpu_kms=0x55eb13bc9e00, cursor_sprite=0x55eb1918fb00,
pixels=0x7f91b4bb9700 "", width=24, height=24, rowstride=96,
gbm_format=875713089) at
../src/backends/native/meta-cursor-renderer-native.c:1399
#3 0x7f9209c06f98 in load_scaled_and_transformed_cursor_sprite
(native=0x55eb1617f580, gpu_kms=0x55eb13bc9e00, cursor_sprite=0x55eb1918fb00,
relative_scale=1, relative_transform=META_MONITOR_TRANSFORM_NORMAL,
data=0x7f91b4bb9700 "", width=24, height=24, rowstride=96, gbm_format=875713089)
at ../src/backends/native/meta-cursor-renderer-native.c:1574
#4 0x7f9209c07293 in realize_cursor_sprite_from_wl_buffer_for_gpu
(renderer=0x55eb1617f580, gpu_kms=0x55eb13bc9e00,
sprite_wayland=0x55eb1918fb00) at
../src/backends/native/meta-cursor-renderer-native.c:1670
#5 0x7f9209c07788 in realize_cursor_sprite_for_gpu
(renderer=0x55eb1617f580, gpu_kms=0x55eb13bc9e00, cursor_sprite=0x55eb1918fb00)
at ../src/backends/native/meta-cursor-renderer-native.c:1836
#6 0x7f9209c077cf in realize_cursor_sprite (renderer=0x55eb1617f580,
cursor_sprite=0x55eb1918fb00, gpus=0x55eb16345a20 = {...}) at
../src/backends/native/meta-cursor-renderer-native.c:1854
#7 0x7f9209c05dd4 in meta_cursor_renderer_native_update_cursor
(renderer=0x55eb1617f580, cursor_sprite=0x55eb1918fb00) at
../src/backends/native/meta-cursor-renderer-native.c:1087
#8 0x7f9209aac8fa in meta_cursor_renderer_update_cursor
(renderer=0x55eb1617f580, cursor_sprite=0x55eb1918fb00) at
../src/backends/meta-cursor-renderer.c:413
#9 0x7f9209aaca07 in meta_cursor_renderer_force_update
(renderer=0x55eb1617f580) at ../src/backends/meta-cursor-renderer.c:448
#10 0x7f9209bc4dc6 in update_cursor_sprite_texture
(cursor_surface=0x55eb1924d880) at
../src/wayland/meta-wayland-cursor-surface.c:79
#11 0x7f9209bc512a in meta_wayland_cursor_surface_apply_state
(surface_role=0x55eb1924d880, pending=0x55eb1918d410) at
../src/wayland/meta-wayland-cursor-surface.c:179
#12 0x7f9209be3774 in meta_wayland_surface_role_apply_state
(surface_role=0x55eb1924d880, pending=0x55eb1918d410) at
../src/wayland/meta-wayland-surface.c:1938
#13 0x7f9209be14b6 in meta_wayland_surface_apply_state
(surface=0x55eb16305e60, state=0x55eb1918d410) at
../src/wayland/meta-wayland-surface.c:882
#14 0x7f9209be19c7 in meta_wayland_surface_commit
(surface=0x55eb16305e60) at ../src/wayland/meta-wayland-surface.c:1038
#15 0x7f9209be1e9f in wl_surface_commit (client=0x55eb191d7150,
resource=0x55eb191f1eb0) at ../src/wayland/meta-wayland-surface.c:1191
#16 0x7f9209d1ae2e in () at /lib/x86_64-linux-gnu/libffi.so.8
#17 0x7f9209d17493 in () at /lib/x86_64-linux-gnu/libffi.so.8
#18 0x7f920aea42a0 in () at /lib/x86_64-linux-gnu/libwayland-server.so.0
#19
[Desktop-packages] [Bug 1997597] Re: [amdgpu] Higher input latency for fullscreen games in Wayland sessions compared to Xorg
mutter (43.2-4ubuntu1) lunar; urgency=medium ** Changed in: mutter (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1997597 Title: [amdgpu] Higher input latency for fullscreen games in Wayland sessions compared to Xorg Status in mutter package in Ubuntu: Fix Released Bug description: This is a regression that came with the change from Xorg to Wayland. It's particularly bad for playing fast-paced games, such as first- person shooters. The pointer tracking has a small but significant delay, which cannot be reproduced on the Xorg session. Similar reports: - https://bugs.launchpad.net/ubuntu/+bug/1982560 - https://bugzilla.gnome.org/show_bug.cgi?id=745032 ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Nov 23 17:42:07 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-11-23 (0 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 43.0-1ubuntu4 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1997597/+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 2003019] [NEW] package software-properties-gtk 0.99.22.4 failed to install/upgrade: podproces nowy pakiet software-properties-gtk skrypt pre-removal zwrócił kod błędu 1
Public bug reported: try to install driver for tp-link ac600 and broke ProblemType: Package DistroRelease: Ubuntu 22.04 Package: software-properties-gtk 0.99.22.4 ProcVersionSignature: Ubuntu 5.15.0-37.39-generic 5.15.35 Uname: Linux 5.15.0-37-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass Date: Mon Jan 16 21:01:32 2023 ErrorMessage: podproces nowy pakiet software-properties-gtk skrypt pre-removal zwrócił kod błędu 1 InstallationDate: Installed on 2022-06-14 (216 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.8 SourcePackage: software-properties Title: package software-properties-gtk 0.99.22.4 failed to install/upgrade: podproces nowy pakiet software-properties-gtk skrypt pre-removal zwrócił kod błędu 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2003019 Title: package software-properties-gtk 0.99.22.4 failed to install/upgrade: podproces nowy pakiet software-properties-gtk skrypt pre-removal zwrócił kod błędu 1 Status in software-properties package in Ubuntu: New Bug description: try to install driver for tp-link ac600 and broke ProblemType: Package DistroRelease: Ubuntu 22.04 Package: software-properties-gtk 0.99.22.4 ProcVersionSignature: Ubuntu 5.15.0-37.39-generic 5.15.35 Uname: Linux 5.15.0-37-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass Date: Mon Jan 16 21:01:32 2023 ErrorMessage: podproces nowy pakiet software-properties-gtk skrypt pre-removal zwrócił kod błędu 1 InstallationDate: Installed on 2022-06-14 (216 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.8 SourcePackage: software-properties Title: package software-properties-gtk 0.99.22.4 failed to install/upgrade: podproces nowy pakiet software-properties-gtk skrypt pre-removal zwrócił kod błędu 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2003019/+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 2000551] Re: [System Fonts] Replace default sinhala font from LKLUG to Noto
Ah! got it. thank you ^_^ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/2000551 Title: [System Fonts] Replace default sinhala font from LKLUG to Noto Status in language-selector package in Ubuntu: Fix Released Status in ubuntu-meta package in Ubuntu: Won't Fix Status in language-selector source package in Jammy: Fix Committed Status in language-selector source package in Kinetic: Fix Committed Bug description: [ Impact ] The current default font for Sinhala (LKLUG) is unmaintained and comes with issues. Noto offers Sinhala fonts with significantly higher quality. fonts-lklug-sinhala is pulled by quite a few meta packages. Instead of changing that, the proposed change makes fontconfig give Noto Sans Sinhala respective Noto Serif Sinhala higher precedence than LKLUG, and that — together with installation of fonts-noto-core — seems to be sufficient to achieve the desired result. [ Test Plan ] * Install language-selector-[common,gnome] from [jammy,kinetic]-proposed. * Open Language Support and install the Sinhala language. * Open a terminal window and run this command: fc-match -a | grep -E 'LKLUG|Sinhala' * Confirm that Noto Sans Sinhala is listed before LKLUG. * Close Firefox and re-open it. * Visit e.g. https://si.wikipedia.org and confirm the improvement. (Also I (Gunnar), who don't speak Sinhala, notice a remarkable difference.) [ Where problems could occur ] No real problem in sight. Some Sinhala speaking users with fonts-noto- core installed will indeed see a surprise change when it starts to render Sinhala via Noto fonts instead of LKLUG. But that surprise ought to make them happy. :) Please note Robie Basak's warning about the changed font metrics in comment #7, though. [ Original description ] **What's the problem?** Currently ubuntu comes with LKLUG font for sinhala (si). it's not clear. e.g. we cannot recognize vowel signs and read websites using that font. We can change it manually but such changes do not apply to some applications or application types e.g. snap apps etc. LKLUG (last active: 2012) no one maintain it now. https://web.archive.org/web/202200*/http://www.lug.lk/ http://www.lug.lk/fonts/lklug **What expected to happen?** We would like to see Noto serif sinhala as the default font for sinhala language https://fonts.google.com/noto/specimen/Noto+Serif+Sinhala [Highlighs: clear (readable), thin, takes less space than sans sinhala] If noto sans is more suitable for ubuntuOS, you can add noto sans sinhala https://fonts.google.com/noto/specimen/Noto+Sans+Sinhala [Highlighs: clear (readable), thick, takes more space than serif sinhala] **Additional details** Screenshots (see the difference: LKLUG/Noto) LKLUG https://i.ibb.co/nbHM5Mw/lklug.jpg Noto Sinhala https://i.ibb.co/k9dbtYb/noto.jpg If you need more examples or clarifications, please add a comment Random posts 1. https://groups.google.com/g/Sinhala-Unicode/c/LYxuJ44dY3g 2. https://twitter.com/thilinag/status/1598707165920825344#m (LKLUG bug with some apps) 3. https://www.reddit.com/r/srilanka/comments/nzpl9p/change_sinhala_font_in_ubuntu/ Also, some developers already have designed tools, scripts for that problem however many people do not try to find these scripts and switch to other OS 1. https://github.com/IMS94/UbuntuSinhalaFont (developer: PMC chair @apache) 2. https://gist.github.com/thilinag/66577033fafd00c3dfdaa898c2478c79 3. https://github.com/hankyoTutorials/linux-system-sinhala-font-changer Please review details, screenshots and posts. This is not a personal opinion and atleast, i expect to see this change in the next interim or LTS release. Furthermore, please let me know if i can help to speed-up this replacement process To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/2000551/+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 1988836] [ubuntu-drivers-common/focal] verification still needed
The fix for this bug has been awaiting testing feedback in the -proposed repository for focal for more than 90 days. Please test this fix and update the bug appropriately with the results. In the event that the fix for this bug is still not verified 15 days from now, the package will be removed from the -proposed repository. ** Tags added: removal-candidate -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1988836 Title: LRMv7: Enable the open NVIDIA kernel modules Status in linux-restricted-modules package in Ubuntu: In Progress Status in nvidia-graphics-drivers-515 package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in linux-restricted-modules source package in Focal: In Progress Status in nvidia-graphics-drivers-515 source package in Focal: Fix Released Status in ubuntu-drivers-common source package in Focal: Fix Committed Status in linux-restricted-modules source package in Jammy: In Progress Status in nvidia-graphics-drivers-515 source package in Jammy: Fix Released Status in ubuntu-drivers-common source package in Jammy: Fix Committed Bug description: [ Impact ] * The 515 series introduced open kernel modules for the NVIDIA driver. They come with an open source licence, and should be provided as an option for datacenter GPUs: https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/ Currently, this is only production-ready (and enabled) on datacenter GPUs. * We should enable signed modules for the 515-open drivers, giving users the option to try the drivers. * The ubuntu-drivers tool should set a lower priority for the -open flavour, so that we do not end up recommending it over the plain 515 flavour. [ Test Plan ] * [ubuntu-drivers-common]: "sudo ubuntu-drivers install (to make sure the driver is not installed by default)" * [nvidia driver] "sudo ubuntu-drivers install nvidia:515-open" to make sure that the driver can be installed manually. Please make sure that this installs the correct linux-restricted- modules. Note: support for GeForce and Workstation GPUs is alpha-quality, and is disabled by default. This means that desktop testing is not needed at the moment. [ Where problems could occur ] * This adds a new driver combination, which is not meant to be default, and is only enabled for a limited amount of devices (datacenter GPUs). * We need to be sure that the driver is not recommended over the other drivers. [ Other Info ] - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1988836/+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 1990563] Re: Some maximized/fullscreen windows appear on both monitors
I confirm this new version of Mutter fixes the issue on 23.04, thanks! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1990563 Title: Some maximized/fullscreen windows appear on both monitors Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Released Bug description: I have a dual monitor setup, with external monitor configured as primary. When I maximize certain windows on the secondary monitor, a copy of the same window appears on the primary monitor (see first attached video). It happens with some apps, not with all of them. For example, it happens with IntelliJ IDEA (Java app) and Spotify (presumably Electron app), not with Gnome Text Editor, Gnome Terminal, Chrome or Firefox, for instance. A very similar situation occurs when taking a screenshot with Flameshot, though in the opposite way: a copy of the primary monitor appears on the secondary (see second attached video). ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: mutter 43.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Thu Sep 22 14:37:37 2022 InstallationDate: Installed on 2018-12-14 (1378 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: mutter UpgradeStatus: Upgraded to kinetic on 2022-09-02 (20 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1990563/+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 2003024] [NEW] Dock prevents Search switching to some apps in different workspaces
Public bug reported: While the Ubuntu Dock extension is active, searching for certain applications on the overview screen and pressing Enter does not switch to them if an instance exists on other workspaces. Notably a few GNOME Apps such as Nautilus and gedit. From the programs I've tested: - Pressing Enter on Nautilus, gedit and Firefox does nothing, not even close the overview nor switch to an open instance. - Pressing Enter on Thunderbird switches to it properly. - Pressing Enter on KeepassXC gets you a notification and clicking it will switch to it. - Pressing Enter on Terminal opens a new instance on the current workspace instead of switching to an existing one if one exists on another workspace. If the dock extension is disabled, searching for a program and pressing Enter behaves as expected, that is, the program becomes focused and is switched to. I apologize in case that wasn't well explained, if there are any doubts, I'll attempt to record a video of it. Ubuntu: 22.04.01 LTS Ubuntu Dock: 72~ubuntu5.22.04.1 gnome-shell: 42.5-0ubuntu1 Running on Xorg. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell-extension-ubuntu-dock 72~ubuntu5.22.04.1 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jan 16 20:04:47 2023 InstallationDate: Installed on 2022-09-12 (126 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ** Description changed: While the Ubuntu Dock extension is active, searching for certain applications on the overview screen and pressing Enter does not switch to them if an instance exists on other workspaces. Notably a few GNOME Apps such as Nautilus and gedit. From the programs I've tested: - Pressing Enter on Nautilus, gedit and Firefox does nothing, not even close the overview nor switch to an open instance. - Pressing Enter on Thunderbird switches to it properly. - Pressing Enter on KeepassXC gets you a notification and clicking it will switch to it. - Pressing Enter on Terminal opens a new instance on the current workspace instead of switching to an existing one if one exists on another workspace. If the dock extension is disabled, searching for a program and pressing Enter behaves as expected, that is, the program becomes focused and is switched to. I apologize in case that wasn't well explained, if there are any doubts, I'll attempt to record a video of it. Ubuntu: 22.04.01 LTS Ubuntu Dock: 72~ubuntu5.22.04.1 gnome-shell: 42.5-0ubuntu1 + Running on Xorg. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell-extension-ubuntu-dock 72~ubuntu5.22.04.1 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jan 16 20:04:47 2023 InstallationDate: Installed on 2022-09-12 (126 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) -- 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/2003024 Title: Dock prevents Search switching to some apps in different workspaces Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: While the Ubuntu Dock extension is active, searching for certain applications on the overview screen and pressing Enter does not switch to them if an instance exists on other workspaces. Notably a few GNOME Apps such as Nautilus and gedit. From the programs I've tested: - Pressing Enter on Nautilus, gedit and Firefox does nothing, not even close the overview nor switch to an open instance. - Pressing Enter on Thunderbird switches to it properly. - Pressing Enter on KeepassXC gets you a notification and clicking it will switch to it. - Pressing Enter on Terminal opens a new instance on the current workspace instead of switching to an existing one if one exists on another workspace. If the dock extension is disabled, searching for a program and pressing Enter behaves as expected, that is, the program becomes focused and is switched to. I apologize in case that wasn't well explained, if there are any doubts, I'll attempt to record a video of it. Ubuntu: 22.04.01 LTS
[Desktop-packages] [Bug 2003024] Re: Dock prevents Search switching to some apps in different workspaces
** Description changed: While the Ubuntu Dock extension is active, searching for certain applications on the overview screen and pressing Enter does not switch to them if an instance exists on other workspaces. Notably a few GNOME Apps such as Nautilus and gedit. From the programs I've tested: - Pressing Enter on Nautilus, gedit and Firefox does nothing, not even close the overview nor switch to an open instance. - Pressing Enter on Thunderbird switches to it properly. - Pressing Enter on KeepassXC gets you a notification and clicking it will switch to it. - Pressing Enter on Terminal opens a new instance on the current workspace instead of switching to an existing one if one exists on another workspace. If the dock extension is disabled, searching for a program and pressing Enter behaves as expected, that is, the program becomes focused and is switched to. + + Edit: After some more testing, it only happens if either "Include + applications from the current workspace only" or "Include applications + from each monitor only" options are activated in Control Center > + Multitasking > Application Switching I apologize in case that wasn't well explained, if there are any doubts, I'll attempt to record a video of it. Ubuntu: 22.04.01 LTS Ubuntu Dock: 72~ubuntu5.22.04.1 gnome-shell: 42.5-0ubuntu1 Running on Xorg. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell-extension-ubuntu-dock 72~ubuntu5.22.04.1 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jan 16 20:04:47 2023 InstallationDate: Installed on 2022-09-12 (126 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) -- 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/2003024 Title: Dock prevents Search switching to some apps in different workspaces Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: While the Ubuntu Dock extension is active, searching for certain applications on the overview screen and pressing Enter does not switch to them if an instance exists on other workspaces. Notably a few GNOME Apps such as Nautilus and gedit. From the programs I've tested: - Pressing Enter on Nautilus, gedit and Firefox does nothing, not even close the overview nor switch to an open instance. - Pressing Enter on Thunderbird switches to it properly. - Pressing Enter on KeepassXC gets you a notification and clicking it will switch to it. - Pressing Enter on Terminal opens a new instance on the current workspace instead of switching to an existing one if one exists on another workspace. If the dock extension is disabled, searching for a program and pressing Enter behaves as expected, that is, the program becomes focused and is switched to. Edit: After some more testing, it only happens if either "Include applications from the current workspace only" or "Include applications from each monitor only" options are activated in Control Center > Multitasking > Application Switching I apologize in case that wasn't well explained, if there are any doubts, I'll attempt to record a video of it. Ubuntu: 22.04.01 LTS Ubuntu Dock: 72~ubuntu5.22.04.1 gnome-shell: 42.5-0ubuntu1 Running on Xorg. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell-extension-ubuntu-dock 72~ubuntu5.22.04.1 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jan 16 20:04:47 2023 InstallationDate: Installed on 2022-09-12 (126 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/2003024/+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 1958084] Re: Please apply the upstream commit to drop Bitstream Vera fonts
** Changed in: fontconfig (Debian) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/1958084 Title: Please apply the upstream commit to drop Bitstream Vera fonts Status in fontconfig package in Ubuntu: New Status in fontconfig package in Debian: Fix Released Bug description: Upstream dropped Bitstream Vera fonts, please apply that fix in the Ubuntu package. https://gitlab.freedesktop.org/fontconfig/fontconfig/-/commit/fcb042028126d79ea5a5fa015b2b034b98656e73 Rationale: DejaVu font extends the Bitstream Vera font, and is already installed by default. Besides, the Bitstream Vera font is very obsolete, looks worse than DejaVu and sometimes as a negative side effect it takes over as a default font when installed (without DejaVu). After applying the upstream fix, this Ubuntu patch becomes obsolete (03_prefer_dejavu.patch): https://git.launchpad.net/ubuntu/+source/fontconfig/tree/debian/patches/03_prefer_dejavu.patch You may also think about updating the whole package to an up-to-date snapshot, since the last Debian/Ubuntu version update was in 2018. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1958084/+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 2003031] [NEW] gjs crash crashes gnome session
Public bug reported: GJS crashes - here's the crashdump. I saw the crash occur after a screensaver had been running, and the screens had gone blank. I assume this means they were turned off by the sleep timer. When I worke the machine, I was presented with a prompt, I *quickly* entered my login credentials and momentarily saw the desktop and all open programs on it. Then, the screens (3) flickered and I saw the login prompt again. I logged in (again), and all applications had been shut down. I checked /var/log/syslog and saw the following details -- see (log). Uploaded file, and the crashdump. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Uname: Linux 5.19.0-29-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jan 16 20:52:55 2023 DistUpgraded: 2023-01-14 21:42:30,924 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: kinetic DistroVariant: ubuntu DkmsStatus: 8812au/5.6.4.2_35491.20191025, 5.15.0-58-generic, x86_64: installed 8812au/5.6.4.2_35491.20191025, 5.19.0-29-generic, x86_64: installed nvidia/470.161.03, 5.19.0-29-generic, x86_64: installed virtualbox/6.1.38, 5.15.0-58-generic, x86_64: installed virtualbox/6.1.38, 5.19.0-29-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo TigerLake-LP GT2 [Iris Xe Graphics] [17aa:22d4] InstallationDate: Installed on 2023-01-09 (7 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: LENOVO 20XY0027US ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-29-generic root=UUID=1cae8af8-977f-4853-9106-9169f34c4bc2 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to kinetic on 2023-01-15 (1 days ago) dmi.bios.date: 07/27/2022 dmi.bios.release: 1.55 dmi.bios.vendor: LENOVO dmi.bios.version: N32ET79W (1.55 ) dmi.board.asset.tag: Not Available dmi.board.name: 20XY0027US dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.33 dmi.modalias: dmi:bvnLENOVO:bvrN32ET79W(1.55):bd07/27/2022:br1.55:efr1.33:svnLENOVO:pn20XY0027US:pvrThinkPadX1YogaGen6:rvnLENOVO:rn20XY0027US:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:skuLENOVO_MT_20XY_BU_Think_FM_ThinkPadX1YogaGen6: dmi.product.family: ThinkPad X1 Yoga Gen 6 dmi.product.name: 20XY0027US dmi.product.sku: LENOVO_MT_20XY_BU_Think_FM_ThinkPad X1 Yoga Gen 6 dmi.product.version: ThinkPad X1 Yoga Gen 6 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.1-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.3 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 crash kinetic third-party-packages ubuntu wayland-session ** Attachment added: "this is the crashdump for this bug report, 'log' is the syslog details at the same time." https://bugs.launchpad.net/bugs/2003031/+attachment/5641786/+files/gjs-crash-report.tar.gz -- 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/2003031 Title: gjs crash crashes gnome session Status in xorg package in Ubuntu: New Bug description: GJS crashes - here's the crashdump. I saw the crash occur after a screensaver had been running, and the screens had gone blank. I assume this means they were turned off by the sleep timer. When I worke the machine, I was presented with a prompt, I *quickly* entered my login credentials and momentarily saw the desktop and all open programs on it. Then, the screens (3) flickered and I saw the login prompt again. I logged in (again), and all applications had been shut down. I checked /var/log/syslog and saw the following details -- see (log). Uploaded file, and the crashdump. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17
[Desktop-packages] [Bug 2003030] [NEW] unable to scan using simple-scan
Public bug reported: start simple scan, does see my scan-printer over the wireless. when try to scan get the error unable to start scanners. This is what i get when checking for scanner: scanimage -L device `escl:https://fe80::e6e7:49ff:fe8f:7612:443' is a HP ENVY 5000 series [8F7612] (1259) SSL platen scanner device `airscan:e0:HP ENVY 5000 series [8F7612] (1259)' is a eSCL HP ENVY 5000 series [8F7612] (1259) ip=fe80::e6e7:49ff:fe8f:7612%2 used to work fine, seem to have broken down on the last version of ubuntu. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: simple-scan 42.0-1 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Jan 17 12:46:33 2023 InstallationDate: Installed on 2022-05-07 (255 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Dell Inc. XPS 13 9360 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic root=UUID=5ee1619e-9b01-4a30-be0c-da0346bee175 ro quiet splash vt.handoff=7 SourcePackage: simple-scan UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/14/2019 dmi.bios.release: 2.13 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.13.0 dmi.board.name: 02PG84 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.13.0:bd11/14/2019:br2.13:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn02PG84:rvrA00:cvnDellInc.:ct9:cvr:sku082A: dmi.product.family: XPS dmi.product.name: XPS 13 9360 dmi.product.sku: 082A dmi.sys.vendor: Dell Inc. ** Affects: simple-scan (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to simple-scan in Ubuntu. https://bugs.launchpad.net/bugs/2003030 Title: unable to scan using simple-scan Status in simple-scan package in Ubuntu: New Bug description: start simple scan, does see my scan-printer over the wireless. when try to scan get the error unable to start scanners. This is what i get when checking for scanner: scanimage -L device `escl:https://fe80::e6e7:49ff:fe8f:7612:443' is a HP ENVY 5000 series [8F7612] (1259) SSL platen scanner device `airscan:e0:HP ENVY 5000 series [8F7612] (1259)' is a eSCL HP ENVY 5000 series [8F7612] (1259) ip=fe80::e6e7:49ff:fe8f:7612%2 used to work fine, seem to have broken down on the last version of ubuntu. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: simple-scan 42.0-1 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Jan 17 12:46:33 2023 InstallationDate: Installed on 2022-05-07 (255 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Dell Inc. XPS 13 9360 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic root=UUID=5ee1619e-9b01-4a30-be0c-da0346bee175 ro quiet splash vt.handoff=7 SourcePackage: simple-scan UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/14/2019 dmi.bios.release: 2.13 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.13.0 dmi.board.name: 02PG84 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.13.0:bd11/14/2019:br2.13:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn02PG84:rvrA00:cvnDellInc.:ct9:cvr:sku082A: dmi.product.family: XPS dmi.product.name: XPS 13 9360 dmi.product.sku: 082A dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/2003030/+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 1998950] Re: GPU hang on Alder Lake laptop
Hmm perhaps bug 2001914 needs revisiting though (22.04) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1998950 Title: GPU hang on Alder Lake laptop Status in Linux: New Status in linux package in Ubuntu: Incomplete Status in mesa package in Ubuntu: Incomplete Bug description: I see frequent (multiple times per day) hangs on my Lenovo ThinkPad X1 Carbon Gen 10. When this occurs, part of the image tears away and X becomes unusable. Sometimes the cursor continues to move for a short time after the fact. In order to recover, I must SSH into the machine and run `sudo killall -9 Xorg`, which drops me back to the lightdm login screen and then things work again. I've also seen this on Debian sid on a nearly identical machine, and there when upgrading to kernel 6.0 and Mesa 22.3, the problem disappears. However, those are not available in Kinetic. I've tried both `i915.enable_psr=0` and `i915.enable_dc=0` as boot parameters and this does not affect anything. The problem has been occurring since I installed Ubuntu on this machine when I got it on November 17. I believe the upstream bug report is this: https://gitlab.freedesktop.org/drm/intel/-/issues/6757. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-26.27-generic 5.19.7 Uname: Linux 5.19.0-26-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: MATE Date: Tue Dec 6 16:42:04 2022 DistUpgraded: Fresh install DistroCodename: kinetic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation Alder Lake-P Integrated Graphics Controller [8086:46a6] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Lenovo Alder Lake-P Integrated Graphics Controller [17aa:22e7] InstallationDate: Installed on 2022-11-17 (18 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: LENOVO 21CBCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-26-generic root=/dev/mapper/vgubuntu-root ro i915.enable_dc=0 quiet splash i915.enable_dc=0 vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/02/2022 dmi.bios.release: 1.30 dmi.bios.vendor: LENOVO dmi.bios.version: N3AET65W (1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 21CBCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0T76461 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.14 dmi.modalias: dmi:bvnLENOVO:bvrN3AET65W(1.30):bd08/02/2022:br1.30:efr1.14:svnLENOVO:pn21CBCTO1WW:pvrThinkPadX1CarbonGen10:rvnLENOVO:rn21CBCTO1WW:rvrSDK0T76461WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21CB_BU_Think_FM_ThinkPadX1CarbonGen10: dmi.product.family: ThinkPad X1 Carbon Gen 10 dmi.product.name: 21CBCTO1WW dmi.product.sku: LENOVO_MT_21CB_BU_Think_FM_ThinkPad X1 Carbon Gen 10 dmi.product.version: ThinkPad X1 Carbon Gen 10 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.1-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-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 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1998950/+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 2003031] Re: gnome-shell crashes in the kernel at drm_atomic_check_only and the kernel says "adding CRTC not allowed without modesets: requested 0x4, affected 0x7"
This *might* relate to bug 2003042. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2003031 Title: gnome-shell crashes in the kernel at drm_atomic_check_only and the kernel says "adding CRTC not allowed without modesets: requested 0x4, affected 0x7" Status in Linux: Unknown Status in linux package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: GJS crashes - here's the crashdump. I saw the crash occur after a screensaver had been running, and the screens had gone blank. I assume this means they were turned off by the sleep timer. When I worke the machine, I was presented with a prompt, I *quickly* entered my login credentials and momentarily saw the desktop and all open programs on it. Then, the screens (3) flickered and I saw the login prompt again. I logged in (again), and all applications had been shut down. I checked /var/log/syslog and saw the following details -- see (log). Uploaded file, and the crashdump. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Uname: Linux 5.19.0-29-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jan 16 20:52:55 2023 DistUpgraded: 2023-01-14 21:42:30,924 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: kinetic DistroVariant: ubuntu DkmsStatus: 8812au/5.6.4.2_35491.20191025, 5.15.0-58-generic, x86_64: installed 8812au/5.6.4.2_35491.20191025, 5.19.0-29-generic, x86_64: installed nvidia/470.161.03, 5.19.0-29-generic, x86_64: installed virtualbox/6.1.38, 5.15.0-58-generic, x86_64: installed virtualbox/6.1.38, 5.19.0-29-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo TigerLake-LP GT2 [Iris Xe Graphics] [17aa:22d4] InstallationDate: Installed on 2023-01-09 (7 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: LENOVO 20XY0027US ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-29-generic root=UUID=1cae8af8-977f-4853-9106-9169f34c4bc2 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to kinetic on 2023-01-15 (1 days ago) dmi.bios.date: 07/27/2022 dmi.bios.release: 1.55 dmi.bios.vendor: LENOVO dmi.bios.version: N32ET79W (1.55 ) dmi.board.asset.tag: Not Available dmi.board.name: 20XY0027US dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.33 dmi.modalias: dmi:bvnLENOVO:bvrN32ET79W(1.55):bd07/27/2022:br1.55:efr1.33:svnLENOVO:pn20XY0027US:pvrThinkPadX1YogaGen6:rvnLENOVO:rn20XY0027US:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:skuLENOVO_MT_20XY_BU_Think_FM_ThinkPadX1YogaGen6: dmi.product.family: ThinkPad X1 Yoga Gen 6 dmi.product.name: 20XY0027US dmi.product.sku: LENOVO_MT_20XY_BU_Think_FM_ThinkPad X1 Yoga Gen 6 dmi.product.version: ThinkPad X1 Yoga Gen 6 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.1-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.3 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 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2003031/+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 2000551] Re: [System Fonts] Replace default sinhala font from LKLUG to Noto
Hi, >Or they can simply do: sudo apt install fonts-noto-core but flatpak users said that flatpak apps still use LKLUG, how to solve that problem? [different use case] Also, the main problem is more complex than i thought. >The point with the change is to make fontconfig give Noto Sans Sinhala >respective Noto Serif Sinhala ?higher precedence than LKLUG. The >fonts-noto-core package needs to be installed, of course, which it currently >is not for all users. So for a Sinhala speaking user, who wants to use Noto >fonts for rendering Sinhala, they can do either of these steps: > >* Select the Sinhala language when installing Ubuntu. That way fonts-noto-core >will be installed at first login. >* Open Language Support and add the Sinhala language from there, which will >pull fonts-noto-core. According to the details, if a sinhala language speaker or foreigner keeps only english (default) or other language in the system and when they view a sinhala web page using a web browser or use a text editor to edit something, it looks like ubuntu still uses LKLUG as the default font. please correct me if i am wrong. should i propose a small font package like LKLUG? we have thousands of sinhala fonts but no one maintains them like noto team maintains their fonts :D https://sinhala-fonts.org/fonts https://sinhalafont.net/ As far as I know, proprietary operating systems come with high quality and well-maintained fonts for all languages. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/2000551 Title: [System Fonts] Replace default sinhala font from LKLUG to Noto Status in language-selector package in Ubuntu: Fix Released Status in ubuntu-meta package in Ubuntu: Won't Fix Status in language-selector source package in Jammy: Fix Committed Status in language-selector source package in Kinetic: Fix Committed Bug description: [ Impact ] The current default font for Sinhala (LKLUG) is unmaintained and comes with issues. Noto offers Sinhala fonts with significantly higher quality. fonts-lklug-sinhala is pulled by quite a few meta packages. Instead of changing that, the proposed change makes fontconfig give Noto Sans Sinhala respective Noto Serif Sinhala higher precedence than LKLUG, and that — together with installation of fonts-noto-core — seems to be sufficient to achieve the desired result. [ Test Plan ] * Install language-selector-[common,gnome] from [jammy,kinetic]-proposed. * Open Language Support and install the Sinhala language. * Open a terminal window and run this command: fc-match -a | grep -E 'LKLUG|Sinhala' * Confirm that Noto Sans Sinhala is listed before LKLUG. * Close Firefox and re-open it. * Visit e.g. https://si.wikipedia.org and confirm the improvement. (Also I (Gunnar), who don't speak Sinhala, notice a remarkable difference.) [ Where problems could occur ] No real problem in sight. Some Sinhala speaking users with fonts-noto- core installed will indeed see a surprise change when it starts to render Sinhala via Noto fonts instead of LKLUG. But that surprise ought to make them happy. :) Please note Robie Basak's warning about the changed font metrics in comment #7, though. [ Original description ] **What's the problem?** Currently ubuntu comes with LKLUG font for sinhala (si). it's not clear. e.g. we cannot recognize vowel signs and read websites using that font. We can change it manually but such changes do not apply to some applications or application types e.g. snap apps etc. LKLUG (last active: 2012) no one maintain it now. https://web.archive.org/web/202200*/http://www.lug.lk/ http://www.lug.lk/fonts/lklug **What expected to happen?** We would like to see Noto serif sinhala as the default font for sinhala language https://fonts.google.com/noto/specimen/Noto+Serif+Sinhala [Highlighs: clear (readable), thin, takes less space than sans sinhala] If noto sans is more suitable for ubuntuOS, you can add noto sans sinhala https://fonts.google.com/noto/specimen/Noto+Sans+Sinhala [Highlighs: clear (readable), thick, takes more space than serif sinhala] **Additional details** Screenshots (see the difference: LKLUG/Noto) LKLUG https://i.ibb.co/nbHM5Mw/lklug.jpg Noto Sinhala https://i.ibb.co/k9dbtYb/noto.jpg If you need more examples or clarifications, please add a comment Random posts 1. https://groups.google.com/g/Sinhala-Unicode/c/LYxuJ44dY3g 2. https://twitter.com/thilinag/status/1598707165920825344#m (LKLUG bug with some apps) 3. https://www.reddit.com/r/srilanka/comments/nzpl9p/change_sinhala_font_in_ubuntu/ Also, some developers already have designed tools, scripts for that problem however many people do not try to find these scripts and switch to other OS 1. https://github.com/IMS94/UbuntuSinhalaFont (developer:
[Desktop-packages] [Bug 2003031] Re: gjs crash crashes gnome session
Thanks for the bug report. The biggest issue here seems to be a kernel crash: Jan 16 19:40:28 semiauto kernel: [84513.834489] adding CRTC not allowed without modesets: requested 0x4, affected 0x7 Jan 16 19:40:28 semiauto kernel: [84513.834564] WARNING: CPU: 4 PID: 2041 at drivers/gpu/drm/drm_atomic.c:1403 drm_atomic_check_only+0x40c/0x450 [drm] But it sounds like the kernel is complaining that gnome-shell is to blame. To work around that, please try adding: MUTTER_DEBUG_FORCE_KMS_MODE=simple to /etc/environment and then reboot. But there are three different crashes here and we need separate bugs opened for each. The other two crashes are of 'gjs-console' and I can see 'gnome-shell' also crashed according to the log. Please open new bugs about each of those by following https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment ** Summary changed: - gjs crash crashes gnome session + gnome-shell crashes in the kernel at drm_atomic_check_only and the kernel says "adding CRTC not allowed without modesets: requested 0x4, affected 0x7" ** Package changed: xorg (Ubuntu) => mutter (Ubuntu) ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Bug watch added: gitlab.freedesktop.org/drm/intel/-/issues #6728 https://gitlab.freedesktop.org/drm/intel/-/issues/6728 -- 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/2003031 Title: gnome-shell crashes in the kernel at drm_atomic_check_only and the kernel says "adding CRTC not allowed without modesets: requested 0x4, affected 0x7" Status in Linux: Unknown Status in linux package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: GJS crashes - here's the crashdump. I saw the crash occur after a screensaver had been running, and the screens had gone blank. I assume this means they were turned off by the sleep timer. When I worke the machine, I was presented with a prompt, I *quickly* entered my login credentials and momentarily saw the desktop and all open programs on it. Then, the screens (3) flickered and I saw the login prompt again. I logged in (again), and all applications had been shut down. I checked /var/log/syslog and saw the following details -- see (log). Uploaded file, and the crashdump. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Uname: Linux 5.19.0-29-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jan 16 20:52:55 2023 DistUpgraded: 2023-01-14 21:42:30,924 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: kinetic DistroVariant: ubuntu DkmsStatus: 8812au/5.6.4.2_35491.20191025, 5.15.0-58-generic, x86_64: installed 8812au/5.6.4.2_35491.20191025, 5.19.0-29-generic, x86_64: installed nvidia/470.161.03, 5.19.0-29-generic, x86_64: installed virtualbox/6.1.38, 5.15.0-58-generic, x86_64: installed virtualbox/6.1.38, 5.19.0-29-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo TigerLake-LP GT2 [Iris Xe Graphics] [17aa:22d4] InstallationDate: Installed on 2023-01-09 (7 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: LENOVO 20XY0027US ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-29-generic root=UUID=1cae8af8-977f-4853-9106-9169f34c4bc2 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to kinetic on 2023-01-15 (1 days ago) dmi.bios.date: 07/27/2022 dmi.bios.release: 1.55 dmi.bios.vendor: LENOVO dmi.bios.version: N32ET79W (1.55 ) dmi.board.asset.tag: Not Available dmi.board.name: 20XY0027US dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.33 dmi.modalias: dmi:bvnLENOVO:bvrN32ET79W(1.55):bd07/27/2022:br1.55:efr1.33:svnLENOVO:pn20XY0027US:pvrThinkPadX1YogaGen6:rvnLENOVO:rn20XY0027US:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:skuLENOVO_MT_20XY_BU_Think_FM_ThinkPadX1YogaGen6: dmi.product.family: ThinkPad X1 Yoga Gen 6 dmi.product.name: 20XY0027US dmi.product.sku: LENOVO_MT_20XY_BU_Think_FM_ThinkPad X1 Yoga Gen 6 dmi.product.version: ThinkPad X1 Yoga Gen 6 dmi.sys.vendor: LENOVO
[Desktop-packages] [Bug 2003031] Re: gnome-shell crashes in the kernel at drm_atomic_check_only and the kernel says "adding CRTC not allowed without modesets: requested 0x4, affected 0x7"
There is an upstream kernel bug suggesting it is triggered by using a USB-C or Thunderbolt dock. That's what it sounds like to me too... https://gitlab.freedesktop.org/drm/intel/-/issues/6728 ** Also affects: linux via https://gitlab.freedesktop.org/drm/intel/-/issues/6728 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2003031 Title: gnome-shell crashes in the kernel at drm_atomic_check_only and the kernel says "adding CRTC not allowed without modesets: requested 0x4, affected 0x7" Status in Linux: Unknown Status in linux package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: GJS crashes - here's the crashdump. I saw the crash occur after a screensaver had been running, and the screens had gone blank. I assume this means they were turned off by the sleep timer. When I worke the machine, I was presented with a prompt, I *quickly* entered my login credentials and momentarily saw the desktop and all open programs on it. Then, the screens (3) flickered and I saw the login prompt again. I logged in (again), and all applications had been shut down. I checked /var/log/syslog and saw the following details -- see (log). Uploaded file, and the crashdump. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Uname: Linux 5.19.0-29-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jan 16 20:52:55 2023 DistUpgraded: 2023-01-14 21:42:30,924 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: kinetic DistroVariant: ubuntu DkmsStatus: 8812au/5.6.4.2_35491.20191025, 5.15.0-58-generic, x86_64: installed 8812au/5.6.4.2_35491.20191025, 5.19.0-29-generic, x86_64: installed nvidia/470.161.03, 5.19.0-29-generic, x86_64: installed virtualbox/6.1.38, 5.15.0-58-generic, x86_64: installed virtualbox/6.1.38, 5.19.0-29-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo TigerLake-LP GT2 [Iris Xe Graphics] [17aa:22d4] InstallationDate: Installed on 2023-01-09 (7 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: LENOVO 20XY0027US ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-29-generic root=UUID=1cae8af8-977f-4853-9106-9169f34c4bc2 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to kinetic on 2023-01-15 (1 days ago) dmi.bios.date: 07/27/2022 dmi.bios.release: 1.55 dmi.bios.vendor: LENOVO dmi.bios.version: N32ET79W (1.55 ) dmi.board.asset.tag: Not Available dmi.board.name: 20XY0027US dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.33 dmi.modalias: dmi:bvnLENOVO:bvrN32ET79W(1.55):bd07/27/2022:br1.55:efr1.33:svnLENOVO:pn20XY0027US:pvrThinkPadX1YogaGen6:rvnLENOVO:rn20XY0027US:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:skuLENOVO_MT_20XY_BU_Think_FM_ThinkPadX1YogaGen6: dmi.product.family: ThinkPad X1 Yoga Gen 6 dmi.product.name: 20XY0027US dmi.product.sku: LENOVO_MT_20XY_BU_Think_FM_ThinkPad X1 Yoga Gen 6 dmi.product.version: ThinkPad X1 Yoga Gen 6 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.1-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.3 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 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2003031/+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 2003042] [NEW] gnome-shell crashed with SIGSEGV in meta_kms_connector_read_state(drm_connector=NULL) from meta_kms_connector_update_state()
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 43.1-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/8158e20e6ac0a16fd196b1b06a27678cf87f2029 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: mutter (Ubuntu) Importance: High Status: Fix Released ** Affects: mutter (Fedora) Importance: Unknown Status: Unknown ** Tags: fixed-in-mutter-43.2 fixed-upstream kinetic -- 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/2003042 Title: gnome-shell crashed with SIGSEGV in meta_kms_connector_read_state(drm_connector=NULL) from meta_kms_connector_update_state() Status in mutter package in Ubuntu: Fix Released Status in mutter package in Fedora: Unknown Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 43.1-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/8158e20e6ac0a16fd196b1b06a27678cf87f2029 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2003042/+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 2003042] Re: gnome-shell crashed with SIGSEGV in meta_kms_connector_read_state(drm_connector=NULL) from meta_kms_connector_update_state()
** Summary changed: - /usr/bin/gnome-shell:11:meta_kms_connector_read_state:meta_kms_connector_update_state:meta_kms_impl_device_update_states:meta_kms_device_update_states_in_impl:meta_kms_update_states_in_impl + gnome-shell crashed with SIGSEGV in meta_kms_connector_read_state(drm_connector=NULL) from meta_kms_connector_update_state() -- 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/2003042 Title: gnome-shell crashed with SIGSEGV in meta_kms_connector_read_state(drm_connector=NULL) from meta_kms_connector_update_state() Status in mutter package in Ubuntu: Fix Released Status in mutter package in Fedora: Unknown Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 43.1-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/8158e20e6ac0a16fd196b1b06a27678cf87f2029 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2003042/+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 2003045] Re: package firefox 108.0.2+build1-0ubuntu0.20.04.1 failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 1
** Tags removed: 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/2003045 Title: package firefox 108.0.2+build1-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: I start upgrade my laptop but it cant upgrade because of some bugs so please verify thrt bugs. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: firefox 108.0.2+build1-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.15.0-58.64~20.04.1-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 1345 F pulseaudio BuildID: 20230104165113 CasperMD5CheckResult: unknown Channel: Unavailable Date: Tue Jan 17 12:19:13 2023 ErrorMessage: new firefox package pre-installation script subprocess returned error exit status 1 ForcedLayersAccel: False InstallationDate: Installed on 2022-03-16 (307 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) IpRoute: default via 192.168.98.186 dev wlp0s20f3 proto dhcp metric 600 169.254.0.0/16 dev wlp0s20f3 scope link metric 1000 192.168.98.0/24 dev wlp0s20f3 proto kernel scope link src 192.168.98.51 metric 600 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: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.8 RunningIncompatibleAddons: False SourcePackage: firefox Title: package firefox 108.0.2+build1-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 2023-01-17 (0 days ago) dmi.bios.date: 10/11/2022 dmi.bios.release: 1.46 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: V1.46 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Timpani_TL dmi.board.vendor: TGL dmi.board.version: V1.46 dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 1.20 dmi.modalias: dmi:bvnINSYDECorp.:bvrV1.46:bd10/11/2022:br1.46:efr1.20:svnAcer:pnTravelMateP214-53:pvrV1.46:rvnTGL:rnTimpani_TL:rvrV1.46:cvnChassisManufacturer:ct10:cvrChassisVersion:sku: dmi.product.family: TravelMate P2 dmi.product.name: TravelMate P214-53 dmi.product.sku: dmi.product.version: V1.46 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2003045/+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 2003045] [NEW] package firefox 108.0.2+build1-0ubuntu0.20.04.1 failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 1
Public bug reported: I start upgrade my laptop but it cant upgrade because of some bugs so please verify thrt bugs. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: firefox 108.0.2+build1-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.15.0-58.64~20.04.1-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 1345 F pulseaudio BuildID: 20230104165113 CasperMD5CheckResult: unknown Channel: Unavailable Date: Tue Jan 17 12:19:13 2023 ErrorMessage: new firefox package pre-installation script subprocess returned error exit status 1 ForcedLayersAccel: False InstallationDate: Installed on 2022-03-16 (307 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) IpRoute: default via 192.168.98.186 dev wlp0s20f3 proto dhcp metric 600 169.254.0.0/16 dev wlp0s20f3 scope link metric 1000 192.168.98.0/24 dev wlp0s20f3 proto kernel scope link src 192.168.98.51 metric 600 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: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.8 RunningIncompatibleAddons: False SourcePackage: firefox Title: package firefox 108.0.2+build1-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 2023-01-17 (0 days ago) dmi.bios.date: 10/11/2022 dmi.bios.release: 1.46 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: V1.46 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Timpani_TL dmi.board.vendor: TGL dmi.board.version: V1.46 dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 1.20 dmi.modalias: dmi:bvnINSYDECorp.:bvrV1.46:bd10/11/2022:br1.46:efr1.20:svnAcer:pnTravelMateP214-53:pvrV1.46:rvnTGL:rnTimpani_TL:rvrV1.46:cvnChassisManufacturer:ct10:cvrChassisVersion:sku: dmi.product.family: TravelMate P2 dmi.product.name: TravelMate P214-53 dmi.product.sku: dmi.product.version: V1.46 dmi.sys.vendor: Acer ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/2003045 Title: package firefox 108.0.2+build1-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: I start upgrade my laptop but it cant upgrade because of some bugs so please verify thrt bugs. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: firefox 108.0.2+build1-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.15.0-58.64~20.04.1-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 1345 F pulseaudio BuildID: 20230104165113 CasperMD5CheckResult: unknown Channel: Unavailable Date: Tue Jan 17 12:19:13 2023 ErrorMessage: new firefox package pre-installation script subprocess returned error exit status 1 ForcedLayersAccel: False InstallationDate: Installed on 2022-03-16 (307 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) IpRoute: default via 192.168.98.186 dev wlp0s20f3 proto dhcp metric 600 169.254.0.0/16 dev wlp0s20f3 scope link metric 1000 192.168.98.0/24 dev wlp0s20f3 proto kernel scope link src 192.168.98.51 metric 600 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: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.8 RunningIncompatibleAddons: False SourcePackage: firefox Title: package firefox 108.0.2+build1-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 2023-01-17 (0 days ago) dmi.bios.date: 10/11/2022 dmi.bios.release: 1.46 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: V1.46 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Timpani_TL dmi.board.vendor: TGL
[Desktop-packages] [Bug 1682542] Re: Add support for top bars on all monitors to allow for multi-monitor support in primary extensions - apps-menu, places-menu, topbar, etc
This is an upstream gnome-shell feature request so it should be discussed there: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/4603 -- 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/1682542 Title: Add support for top bars on all monitors to allow for multi-monitor support in primary extensions - apps-menu, places-menu, topbar, etc Status in GNOME Shell: New Status in gnome-shell package in Ubuntu: Triaged Bug description: This issue will effectively be a regression in desktop usage once Ubuntu switches from Unity to Gnome Shell. Gnome Shell does not work well with multiple monitors unlike every other desktop environment except Budgie, which is switching away from GTK/Gnome to Qt with Budgie 11 due out in the next month or two. I reported it upstream last month but it does not appear to have much traction at the moment. https://bugzilla.gnome.org/show_bug.cgi?id=780078 " It would be nice if the primary included gnome-shell extensions, eg apps-menu and places-menu (and by extension the topbar) supported multi-monitor similar to how the bottom bar 'window-list' currently does. This was easy to achieve on Gnome 2 and now via MATE (out of the box) but there does not appear to be any way to do this with Gnome 3. This also leads to there not being a way to do this via 'Gnome Classic'. Even Windows finally (in W10) does this better out of the box than Gnome 3. BTW - Intel has supported IGP triple head since Ivy Bridge (2012) so it is very cheap to deploy a triple head system (~ $200 for 3 1080p monitors). AMD supports up to quad head in their IGPs. This has been blocking me from moving to Gnome 3 since its release and I finally decided to write a bug report about it. I have had all multi-monitor systems since prior to 2004. " And see comments #11 and #14 from Florian. " No, you don't want that in the extensions. Each extension is separate, so what you are asking for here is that apps-menu and places-menu *both* add top bars to non-primary monitors. We are definitely not going to add two or more stacked panels at the top. What you probably want instead is an option in gnome-shell to put top bars on non-primary monitors, and the aforementioned extensions to handle that case. " " Well, we've established what you want, but that doesn't necessarily mean that we'll implement it. So far the reasoning seems to be: - you really want the feature - GNOME 2 / Windows has it Unlike the case of the window list, nothing in the top bar (except for the app menu to some extent) is tied to a particular monitor, so there's a much weaker case here IMHO. (I'll also note that this wouldn't be a "cheap" option, but require work on lots of details throughout the stack - we'd need to figure out the overview (only include the activities button on the primary monitor? or allow an overview on any monitor?), get API to control the brightness of a particular monitor (rather than the built-in one), don't use "the monitor with the top bar" as indicator for the primary monitor in Settings, ...) " To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1682542/+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 2003042] Re: gnome-shell crashed with SIGSEGV in meta_kms_connector_read_state(drm_connector=NULL) from meta_kms_connector_update_state()
Fixed in mutter 43.2 by commit: 07f1da261743ac49305158a501528bccbd20e7c0 ** Bug watch added: Red Hat Bugzilla #2131269 https://bugzilla.redhat.com/show_bug.cgi?id=2131269 ** Also affects: mutter (Fedora) via https://bugzilla.redhat.com/show_bug.cgi?id=2131269 Importance: Unknown Status: Unknown ** Package changed: gnome-shell (Ubuntu) => mutter (Ubuntu) ** Changed in: mutter (Ubuntu) Importance: Undecided => High ** Changed in: mutter (Ubuntu) Status: New => Fix Released ** Tags added: fixed-in-mutter-43.2 fixed-upstream ** Tags added: rls-kk-incoming -- 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/2003042 Title: gnome-shell crashed with SIGSEGV in meta_kms_connector_read_state(drm_connector=NULL) from meta_kms_connector_update_state() Status in mutter package in Ubuntu: Fix Released Status in mutter package in Fedora: Unknown Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 43.1-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/8158e20e6ac0a16fd196b1b06a27678cf87f2029 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2003042/+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 1998950] Re: GPU hang on Alder Lake laptop
Thanks. I did have a configuration in which I could reproduce this recently so myself or someone else should look at confirming it's really fixed. I wasn't too worried about this bug though because: * It never happens on 22.04 * 23.04 will get kernels 6.1 and 6.2 in the coming months ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete ** Changed in: mesa (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1998950 Title: GPU hang on Alder Lake laptop Status in Linux: New Status in linux package in Ubuntu: Incomplete Status in mesa package in Ubuntu: Incomplete Bug description: I see frequent (multiple times per day) hangs on my Lenovo ThinkPad X1 Carbon Gen 10. When this occurs, part of the image tears away and X becomes unusable. Sometimes the cursor continues to move for a short time after the fact. In order to recover, I must SSH into the machine and run `sudo killall -9 Xorg`, which drops me back to the lightdm login screen and then things work again. I've also seen this on Debian sid on a nearly identical machine, and there when upgrading to kernel 6.0 and Mesa 22.3, the problem disappears. However, those are not available in Kinetic. I've tried both `i915.enable_psr=0` and `i915.enable_dc=0` as boot parameters and this does not affect anything. The problem has been occurring since I installed Ubuntu on this machine when I got it on November 17. I believe the upstream bug report is this: https://gitlab.freedesktop.org/drm/intel/-/issues/6757. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-26.27-generic 5.19.7 Uname: Linux 5.19.0-26-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: MATE Date: Tue Dec 6 16:42:04 2022 DistUpgraded: Fresh install DistroCodename: kinetic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation Alder Lake-P Integrated Graphics Controller [8086:46a6] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Lenovo Alder Lake-P Integrated Graphics Controller [17aa:22e7] InstallationDate: Installed on 2022-11-17 (18 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: LENOVO 21CBCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-26-generic root=/dev/mapper/vgubuntu-root ro i915.enable_dc=0 quiet splash i915.enable_dc=0 vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/02/2022 dmi.bios.release: 1.30 dmi.bios.vendor: LENOVO dmi.bios.version: N3AET65W (1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 21CBCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0T76461 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.14 dmi.modalias: dmi:bvnLENOVO:bvrN3AET65W(1.30):bd08/02/2022:br1.30:efr1.14:svnLENOVO:pn21CBCTO1WW:pvrThinkPadX1CarbonGen10:rvnLENOVO:rn21CBCTO1WW:rvrSDK0T76461WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21CB_BU_Think_FM_ThinkPadX1CarbonGen10: dmi.product.family: ThinkPad X1 Carbon Gen 10 dmi.product.name: 21CBCTO1WW dmi.product.sku: LENOVO_MT_21CB_BU_Think_FM_ThinkPad X1 Carbon Gen 10 dmi.product.version: ThinkPad X1 Carbon Gen 10 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.1-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-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 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1998950/+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 2003024] Re: Dock prevents Search switching to some apps in different workspaces
Thanks for the bug report. It sounds like there might be multiple issues here. To start, please disable dock auto-hide (if enabled) so that we can rule out bug 1979096. Please then update the bug description with the main issue that remains after that. ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: New => Incomplete -- 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/2003024 Title: Dock prevents Search switching to some apps in different workspaces Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Incomplete Bug description: While the Ubuntu Dock extension is active, searching for certain applications on the overview screen and pressing Enter does not switch to them if an instance exists on other workspaces. Notably a few GNOME Apps such as Nautilus and gedit. From the programs I've tested: - Pressing Enter on Nautilus, gedit and Firefox does nothing, not even close the overview nor switch to an open instance. - Pressing Enter on Thunderbird switches to it properly. - Pressing Enter on KeepassXC gets you a notification and clicking it will switch to it. - Pressing Enter on Terminal opens a new instance on the current workspace instead of switching to an existing one if one exists on another workspace. If the dock extension is disabled, searching for a program and pressing Enter behaves as expected, that is, the program becomes focused and is switched to. Edit: After some more testing, it only happens if either "Include applications from the current workspace only" or "Include applications from each monitor only" options are activated in Control Center > Multitasking > Application Switching I apologize in case that wasn't well explained, if there are any doubts, I'll attempt to record a video of it. Ubuntu: 22.04.01 LTS Ubuntu Dock: 72~ubuntu5.22.04.1 gnome-shell: 42.5-0ubuntu1 Running on Xorg. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell-extension-ubuntu-dock 72~ubuntu5.22.04.1 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jan 16 20:04:47 2023 InstallationDate: Installed on 2022-09-12 (126 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/2003024/+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 1993284] Re: All app icons are missing after computer locked for some time (Ubuntu 22.04)
*** This bug is a duplicate of bug 1936734 *** https://bugs.launchpad.net/bugs/1936734 ** Summary changed: - Dash-to-dock shows blank black screen after computer locked for some time (Ubuntu 22.04) + All app icons are missing after computer locked for some time (Ubuntu 22.04) ** Also affects: dash-to-dock via https://github.com/micheleg/dash-to-dock/issues/1852 Importance: Unknown Status: Unknown ** This bug has been marked a duplicate of bug 1936734 All app icons are missing -- 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/1993284 Title: All app icons are missing after computer locked for some time (Ubuntu 22.04) Status in Dash to dock: Unknown Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Bug description: Happening in Ubuntu 22.04 How to reproduce: Left computer idle and locked for quite some time Unlock the computer Only Show Applications icon is shown in dash-to-dock When clicked, blank black screen with no application is shown. And can't return to desktop or do any other navigations. Log out / restart menu still works so I usually restart my computer to fix this. Affected application: micheleg-dash-to-dock ~$ lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1993284/+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 2002941] [NEW] [BPO] libreoffice 7.4.4 for jammy
Public bug reported: [Impact] * LibreOffice 7.4.4 is in its forth bugfix release of the 7.4 line: https://wiki.documentfoundation.org/ReleasePlan/7.4#7.4.4_release * This source packages matches the proposed SRU for kinetic handled at https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2001911 and its backport is currently provided by the LibreOffice Fresh PPA at https://launchpad.net/~libreoffice/+archive/ubuntu/ppa/+packages * LibreOffice 7.3.7 (EOL since November 30, 2022) is currently released in jammy. * 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. [Scope] * Backport of https://launchpad.net/ubuntu/+source/libreoffice/1:7.4.4-0ubuntu0.22.10.1 * Backport target is Jammy/22.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_74/1542/ * 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] ... * [arm64] ... * [armhf] ... * [ppc64el] ... * [s390x] ... * 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 114 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. ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: libreoffice (Ubuntu Jammy) Importance: Undecided Assignee: Rico Tzschichholz (ricotz) Status: New ** Also affects: libreoffice (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: libreoffice (Ubuntu) Status: New => Fix Released ** 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/2002941 Title: [BPO] libreoffice 7.4.4 for jammy Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Jammy: New Bug description: [Impact] * LibreOffice 7.4.4 is in its forth bugfix release of the 7.4 line: https://wiki.documentfoundation.org/ReleasePlan/7.4#7.4.4_release * This source packages matches the proposed SRU for kinetic handled at https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2001911 and its backport is currently provided by the LibreOffice Fresh PPA at https://launchpad.net/~libreoffice/+archive/ubuntu/ppa/+packages * LibreOffice 7.3.7 (EOL since November 30, 2022) is currently released in jammy. * 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. [Scope] * Backport of https://launchpad.net/ubuntu/+source/libreoffice/1:7.4.4-0ubuntu0.22.10.1 * Backport target is Jammy/22.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_74/1542/ * 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
