[Bug 1967632] Re: [snap] apparmor denied when trying to load pkcs11 module for smart card authentication
I missed the obvious fact that the module will only work if sourced from a 22.04, as Firefox is based on core22. There is a priori no guarantee it would work for other series, as it indeed doesn't. If sourced from 24.10, ldd says stuff like opensc-pkcs11.so: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.38' not found (required by /snap/firefox/x7/usr/lib/x86_64-linux-gnu/libopensc.so.11) I'll amend the description and later update it with something that works accross all series, at least for supported cards supported by that module. ** Description changed: - We believe the best solution/work-around at the moment is: + For 22.04 we believe the best solution/work-around at the moment is: - sudo apt install opensc-pkcs11 + sudo apt install opensc-pkcs11 sudo snap refresh --edge firefox sudo snap connect firefox:pcscd cp /usr/lib/*/opensc-pkcs11.so $HOME/snap/firefox/common Then load the module from that path, i.e. $HOME/snap/firefox/common/opensc-pkcs11.so. If you get "unable to load module" make sure you are the owner of the file: chown "$(id -u)" $HOME/snap/firefox/common/opensc-pkcs11.so Please report whether this solves the issue. The part of copying the module to a snap-readable location is clumsy and - we will work on a more proper solution to that. + we will work on a more proper solution to that. And of course, to make + this series-independent. I use a smart card to access government sites. I have that working in firefox and chrome on ubuntu impish, and gave jammy a try, but there firefox won't load the library, giving me a generic error. dmesg, however, shows this apparmor denied message: [sáb abr 2 17:32:27 2022] audit: type=1400 audit(1648931547.646:115): apparmor="DENIED" operation="file_mmap" profile="snap.firefox.firefox" name="/run/user/1000/doc/e0bac853/libaetpkss.so.3.5.4112" pid=3680 comm="firefox" requested_mask="m" denied_mask="m" fsuid=1000 ouid=0 Note also the path, that's not what I typed into the firefox dialog box. I have the .so copied to /usr/lib/x86_64-linux- gnu/libaetpkss.so.3.5.4112, and that's what I typed in when prompted for its path by firefox. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox 1:1snap1-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Apr 2 17:34:09 2022 InstallationDate: Installed on 2022-03-20 (13 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220319) Snap.Changes: no changes found SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967632 Title: [snap] apparmor denied when trying to load pkcs11 module for smart card authentication To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1967632/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967632] Re: [snap] apparmor denied when trying to load pkcs11 module for smart card authentication
Andreas, thank you for your response. As in my previous message, we cannot expect such a hack to work outside of 22.04, I updated the description, sorry for wasting your time with that. Then, it doesn't matter if /usr/lib/x86_64-linux-gnu/libcrypto.so.1.0.0 is in the host, the snap is on core22 and only sees /snap/core22/current/lib/x86_64-linux-gnu/libcrypto.so.3. In any case your comment is very valuable as it gives us a list of libraries required by a module outside the our open-source archive that we should keep in mind when ironing this out. ** Description changed: - For 22.04 we believe the best solution/work-around at the moment is: + For 22.04, if your smart card is supported by OpenSC + (https://github.com/OpenSC/OpenSC/wiki/Supported-hardware-%28smart- + cards-and-USB-tokens%29), we believe the best solution/work-around at + the moment is: sudo apt install opensc-pkcs11 sudo snap refresh --edge firefox sudo snap connect firefox:pcscd cp /usr/lib/*/opensc-pkcs11.so $HOME/snap/firefox/common Then load the module from that path, i.e. $HOME/snap/firefox/common/opensc-pkcs11.so. If you get "unable to load module" make sure you are the owner of the file: chown "$(id -u)" $HOME/snap/firefox/common/opensc-pkcs11.so Please report whether this solves the issue. The part of copying the module to a snap-readable location is clumsy and we will work on a more proper solution to that. And of course, to make this series-independent. I use a smart card to access government sites. I have that working in firefox and chrome on ubuntu impish, and gave jammy a try, but there firefox won't load the library, giving me a generic error. dmesg, however, shows this apparmor denied message: [sáb abr 2 17:32:27 2022] audit: type=1400 audit(1648931547.646:115): apparmor="DENIED" operation="file_mmap" profile="snap.firefox.firefox" name="/run/user/1000/doc/e0bac853/libaetpkss.so.3.5.4112" pid=3680 comm="firefox" requested_mask="m" denied_mask="m" fsuid=1000 ouid=0 Note also the path, that's not what I typed into the firefox dialog box. I have the .so copied to /usr/lib/x86_64-linux- gnu/libaetpkss.so.3.5.4112, and that's what I typed in when prompted for its path by firefox. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox 1:1snap1-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Apr 2 17:34:09 2022 InstallationDate: Installed on 2022-03-20 (13 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220319) Snap.Changes: no changes found SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967632 Title: [snap] apparmor denied when trying to load pkcs11 module for smart card authentication To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1967632/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2041831] Re: Update-manager crashes when packages are de-selected with the mouse
** Merge proposal linked: https://code.launchpad.net/~nteodosio/update-manager/+git/update-manager/+merge/473514 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2041831 Title: Update-manager crashes when packages are de-selected with the mouse To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pygobject/+bug/2041831/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2041831] Re: /usr/bin/update-manager:11:g_type_check_instance_is_fundamentally_a:g_object_ref:gdk_event_copy:pygi_boxed_copy_in_place:arg_boxed_to_py_cleanup
nager. This problem was most recently seen with package version 1:23.10.1, the problem page at https://errors.ubuntu.com/problem/dff72cd5c27c916b2d887a56311ba08ef15b0dff 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/. ** Changed in: update-manager (Ubuntu) Importance: Undecided => High ** Summary changed: - /usr/bin/update-manager:11:g_type_check_instance_is_fundamentally_a:g_object_ref:gdk_event_copy:pygi_boxed_copy_in_place:arg_boxed_to_py_cleanup + Update-manager crashes when packages are de-selected with the mouse ** Changed in: update-manager (Ubuntu) Assignee: (unassigned) => Nathan Teodosio (nteodosio) ** Changed in: update-manager (Ubuntu) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2041831 Title: Update-manager crashes when packages are de-selected with the mouse To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pygobject/+bug/2041831/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2041831] Re: Update-manager crashes when packages are de-selected with the mouse
After some whack-a-moling, removing the setBusy calls from toggle_from_items makes the issue go away, as does removing while Gtk.events_pending(): Gtk.main_iteration() from setBusy(). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2041831 Title: Update-manager crashes when packages are de-selected with the mouse To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pygobject/+bug/2041831/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967632] Re: [snap] apparmor denied when trying to load pkcs11 module for smart card authentication
** Description changed: + We believe the best solution/work-around at the moment is: + + sudo snap refresh --edge firefox + sudo snap connect firefox:pcscd + cp /usr/lib/*/opensc-pkcs11.so $HOME/snap/firefox/common + + Then load the module from that path, i.e. + $HOME/snap/firefox/common/opensc-pkcs11.so. + + If you get "unable to load module" make sure you are the owner of the + file: + + chown "$(id -u)" $HOME/snap/firefox/common/opensc-pkcs11.so + + Please report whether this solves the issue. + + + I use a smart card to access government sites. I have that working in firefox and chrome on ubuntu impish, and gave jammy a try, but there firefox won't load the library, giving me a generic error. dmesg, however, shows this apparmor denied message: [sáb abr 2 17:32:27 2022] audit: type=1400 audit(1648931547.646:115): apparmor="DENIED" operation="file_mmap" profile="snap.firefox.firefox" name="/run/user/1000/doc/e0bac853/libaetpkss.so.3.5.4112" pid=3680 comm="firefox" requested_mask="m" denied_mask="m" fsuid=1000 ouid=0 - - Note also the path, that's not what I typed into the firefox dialog box. I have the .so copied to /usr/lib/x86_64-linux-gnu/libaetpkss.so.3.5.4112, and that's what I typed in when prompted for its path by firefox. + Note also the path, that's not what I typed into the firefox dialog box. + I have the .so copied to /usr/lib/x86_64-linux- + gnu/libaetpkss.so.3.5.4112, and that's what I typed in when prompted for + its path by firefox. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox 1:1snap1-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Apr 2 17:34:09 2022 InstallationDate: Installed on 2022-03-20 (13 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220319) Snap.Changes: no changes found SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) ** Changed in: firefox (Ubuntu) Assignee: (unassigned) => Nathan Teodosio (nteodosio) ** Description changed: We believe the best solution/work-around at the moment is: - sudo snap refresh --edge firefox - sudo snap connect firefox:pcscd - cp /usr/lib/*/opensc-pkcs11.so $HOME/snap/firefox/common + sudo apt install opensc-pkcs11 + sudo snap refresh --edge firefox + sudo snap connect firefox:pcscd + cp /usr/lib/*/opensc-pkcs11.so $HOME/snap/firefox/common Then load the module from that path, i.e. $HOME/snap/firefox/common/opensc-pkcs11.so. If you get "unable to load module" make sure you are the owner of the file: - chown "$(id -u)" $HOME/snap/firefox/common/opensc-pkcs11.so + chown "$(id -u)" $HOME/snap/firefox/common/opensc-pkcs11.so Please report whether this solves the issue. + + The part of copying the module to a snap-readable location is clumsy and + we will work on a more proper solution to that. I use a smart card to access government sites. I have that working in firefox and chrome on ubuntu impish, and gave jammy a try, but there firefox won't load the library, giving me a generic error. dmesg, however, shows this apparmor denied message: [sáb abr 2 17:32:27 2022] audit: type=1400 audit(1648931547.646:115): apparmor="DENIED" operation="file_mmap" profile="snap.firefox.firefox" name="/run/user/1000/doc/e0bac853/libaetpkss.so.3.5.4112" pid=3680 comm="firefox" requested_mask="m" denied_mask="m" fsuid=1000 ouid=0 Note also the path, that's not what I typed into the firefox dialog box. I have the .so copied to /usr/lib/x86_64-linux- gnu/libaetpkss.so.3.5.4112, and that's what I typed in when prompted for its path by firefox. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox 1:1snap1-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Apr 2 17:34:09 2022 InstallationDate: Installed on 2022-03-20 (13 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220319) Snap.Changes: no changes found SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpa
[Bug 2041831] Re: Update-manager crashes when packages are de-selected with the mouse
Sometimes this also appears: /usr/lib/python3/dist-packages/gi/overrides/Gtk.py:1694: Warning: g_object_ref: assertion 'G_IS_OBJECT (object)' failed return _Gtk_main(*args, **kwargs) (update-manager:188833): Gdk-CRITICAL **: 11:19:39.154: gdk_window_get_display: assertion 'GDK_IS_WINDOW (window)' failed /usr/lib/python3/dist-packages/gi/overrides/Gtk.py:1694: Warning: g_object_unref: assertion 'G_IS_OBJECT (object)' failed return _Gtk_main(*args, **kwargs) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2041831 Title: Update-manager crashes when packages are de-selected with the mouse To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pygobject/+bug/2041831/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2081072] Re: The updater crashes when selecting which updates to install
*** This bug is a duplicate of bug 2041831 *** https://bugs.launchpad.net/bugs/2041831 This looks like a duplicate of LP:2041831. For lack of information, I'll mark it so. You can always run apport-collect 2041831 to submit the crash report. ** This bug has been marked a duplicate of bug 2041831 /usr/bin/update-manager:11:g_type_check_instance_is_fundamentally_a:g_object_ref:gdk_event_copy:pygi_boxed_copy_in_place:arg_boxed_to_py_cleanup -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2081072 Title: The updater crashes when selecting which updates to install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/2081072/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064211] Re: /usr/bin/update-manager:AttributeError::available:start_available:refresh_cache:_get_ua_security_status
In a 18.04 virtual machine, I installed update-manager/1:18.04.13.1 and ran UA_CONFIG_FILE=/ update-manager --no-update It started normally. ** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064211 Title: /usr/bin/update- manager:AttributeError::available:start_available:refresh_cache:_get_ua_security_status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/2064211/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2007652] Re: [SRU] PWA don't launch as applications, just another chromium window
Debdiff for 20.04: https://salsa.debian.org/gnome-team/gnome- shell/-/merge_requests/81.diff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2007652 Title: [SRU] PWA don't launch as applications, just another chromium window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2007652/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080953] Re: Chromium WebGL Errors Leading to Video Input Crashing and Eventual Crash
> i'm also confused about that commandline being unsupported -- that's what clicking on the dock item shows in ps, Ah, I didn't know it was from ps, looks like a legit issue then. However when invoking in the command-line you shouldn't use that full qualified path, but just 'chromium' or 'snap run chromium' or '/snap/bin/chromium'. Sorry, it is indeed confusing. Are you using Xorg or Wayland? You can run "echo $XDG_SESSION_TYPE" to determine that, and then please check if the issue is reproducible in the other one (by selecting Ubuntu (on Wayland) vs Ubuntu on Xorg in the log-in screen cog). Alternatively, Chromium from the beta channel could help, as they are use a newer base (core24). You can change the channel you are tracking with snap refresh --beta chromium > trying to make it a base launch command not one of the tools Probably doesn't change things, though I don't really understand what you mean there. > it's in the notes about "raising a bug" with helpful commands and all that. guess a maintainer really like Monty Python :) Yup, the 'w' was meant to reproduce the old keeper being launched. :P -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2080953 Title: Chromium WebGL Errors Leading to Video Input Crashing and Eventual Crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2080953/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080953] Re: Chromium WebGL Errors Leading to Video Input Crashing and Eventual Crash
> /snap/chromium/2943/usr/lib/chromium-browser/chrome Can you please verify whether the issue still happens if you substitute that by /snap/bin/chromium? The reason is: That command line in unsupported as launches Chromium as a unsandboxed application, and thus it tries the hosts' shared libraries instead of the ones provided by core22/gnome-42-2204. In most cases that is the problem. > airspeed velocity: African or European? Wa.. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2080953 Title: Chromium WebGL Errors Leading to Video Input Crashing and Eventual Crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2080953/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2007652] Re: [SRU] PWA don't launch as applications, just another chromium window
Debdiff for 22.04: https://salsa.debian.org/gnome-team/gnome- shell/-/merge_requests/80.diff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2007652 Title: [SRU] PWA don't launch as applications, just another chromium window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2007652/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2007652] Re: [SRU] PWA don't launch as applications, just another chromium window
Debdiff for 24.04: https://salsa.debian.org/gnome-team/gnome- shell/-/merge_requests/79.diff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2007652 Title: [SRU] PWA don't launch as applications, just another chromium window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2007652/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2007652] Re: [SRU] PWA don't launch as applications, just another chromium window
** Description changed: - I have recently converted from deb to snap package of chromium and - progressive web applications (PWAs) launch just as another window of - chromium and are not recognized as separate application by the window - manager (for example when switching using Super+Tab) or dock (grouped - under chromium windows). + Impact + -- - This is either a regression of the snap package vs deb or ubuntu 20.04 - vs ubuntu 18.04 (I am not able to differentiate between these two since - both happened together). + When converting from deb to snap package of chromium, progressive web + applications (PWAs) launch just as another window of chromium and are + not recognized as separate application by the window manager (for + example when switching using Super+Tab) or dock (grouped under chromium + windows). + + This strikes users as a regression (as it is). + + Test case + - + + *Install the package. + *Log in to Ubuntu desktop. + *Start Chromium. + *Go to a site that offers PWA to install, e.g. earth.google.com. + *In the right end of the address bar, click the icon to install the PWA. + *The PWA opens in a separate window. + In this first launch it may be that the PWA is not yet recognized as a different application by the Gnome Shell, if this is the case, close the PWA and open it again. + *Verify that the PWA behaves as a stand-alone program, namely insofar as it: + ++can be found by pressing Super and then typing its name (e.g. 'earth' if you installed Google Earth). + ++launches when thereby clicking that launcher. + ++does not share Chromium's tab group in the alt-tab switcher. + ++does not share Chromium's launcher icon in the dock (i.e. the launcher bar that by default is flush to the left edge of the screen). + + Regression potential + + + Regressions may arise as incorrect window grouping in the alt-tab + switcher or in the dock for desktop applications. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2007652 Title: [SRU] PWA don't launch as applications, just another chromium window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2007652/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2007652] Re: [SRU] PWA don't launch as applications, just another chromium window
** Summary changed: - [snap] PWA don't launch as applications, just another chromium window + [SRU] PWA don't launch as applications, just another chromium window ** Changed in: gnome-shell (Ubuntu Focal) Assignee: (unassigned) => Nathan Teodosio (nteodosio) ** Changed in: gnome-shell (Ubuntu Jammy) Assignee: (unassigned) => Nathan Teodosio (nteodosio) ** Changed in: gnome-shell (Ubuntu Noble) Assignee: (unassigned) => Nathan Teodosio (nteodosio) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2007652 Title: [SRU] PWA don't launch as applications, just another chromium window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2007652/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080923] Re: Unreadable hyperlink colors in dark theme
I'm adding Yaru to the bug task because I don't see how this is something for each GTK program to implement, rather it should be the resolved by the theme. ** Tags added: a11y ui -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2080923 Title: Unreadable hyperlink colors in dark theme To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/2080923/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080923] Re: Unreadable hyperlink colors in dark theme
** Also affects: yaru-theme (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2080923 Title: Unreadable hyperlink colors in dark theme To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/2080923/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061918] Re: package thunderbird 2:1snap1-0ubuntu1 failed to install/upgrade: new thunderbird package pre-installation script subprocess returned error exit status 1
In this debdiff I'm adding libglib2.0t64 to Chromium's dependencies as proposed by Julian. ** Patch added: "chromium-2to3.diff" https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/2061918/+attachment/5818460/+files/chromium-2to3.diff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061918 Title: package thunderbird 2:1snap1-0ubuntu1 failed to install/upgrade: new thunderbird package pre-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2061918/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2007652] Re: [snap] PWA don't launch as applications, just another chromium window
** Changed in: gnome-shell (Ubuntu) Status: Opinion => Fix Committed ** Also affects: chromium-browser (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: gnome-shell (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: chromium-browser (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: gnome-shell (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: chromium-browser (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: gnome-shell (Ubuntu Jammy) Importance: Undecided Status: New ** No longer affects: chromium-browser (Ubuntu Focal) ** No longer affects: chromium-browser (Ubuntu Jammy) ** No longer affects: chromium-browser (Ubuntu Noble) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2007652 Title: [snap] PWA don't launch as applications, just another chromium window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2007652/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064211] Re: /usr/bin/update-manager:AttributeError::available:start_available:refresh_cache:_get_ua_security_status
In a 24.04 virtual machine, I installed update-manager/1:24.04.8 and ran 'UA_CONFIG_FILE=/ update-manager --no-update'. Update-manager started normally. ** Tags removed: verification-needed-noble ** Tags added: verification-done-noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064211 Title: /usr/bin/update- manager:AttributeError::available:start_available:refresh_cache:_get_ua_security_status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/2064211/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2068809] Re: changelogs not listed for PPA packages
In a 24.04 virtual machine I installed update-manager/1:24.04.8. I did apt-add-repository ppa:nteodosio/rebuilds and started update-manager. It correctly showed the "Software Updater" in the list with the change log saying ---> Technical description [--snip--] Changes for update-manager versions: Installed version: 1:24.04.8 Available version: 5:74.04.2 Version 5:74.04.2: * foobar <--- which is correct. ** Tags removed: verification-needed verification-needed-noble ** Tags added: verification-done verification-done-noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2068809 Title: changelogs not listed for PPA packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/2068809/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064211] Re: /usr/bin/update-manager:AttributeError::available:start_available:refresh_cache:_get_ua_security_status
In a 20.04 virtual machine, I installed update-manager/1:20.04.10.23 and ran 'UA_CONFIG_FILE=/ update-manager --no-update'. Update-manager started normally. ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064211 Title: /usr/bin/update- manager:AttributeError::available:start_available:refresh_cache:_get_ua_security_status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/2064211/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080611] Re: [SRU] Backport gnome-control-center 46.4 to Noble
** Changed in: gnome-control-center (Ubuntu) Status: New => Fix Released ** Also affects: gnome-control-center (Ubuntu Noble) Importance: Undecided Status: New ** Changed in: gnome-control-center (Ubuntu) Assignee: Nathan Teodosio (nteodosio) => (unassigned) ** Changed in: gnome-control-center (Ubuntu Noble) Assignee: (unassigned) => Nathan Teodosio (nteodosio) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2080611 Title: [SRU] Backport gnome-control-center 46.4 to Noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2080611/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080611] [NEW] [SRU] Backport gnome-control-center 46.4 to Noble
Public bug reported: Impact -- This is a minor point release update for Gnome Control Center, which has a minor release exception: https://wiki.ubuntu.com/StableReleaseUpdates/GNOME. Test plan - https://wiki.ubuntu.com/DesktopTeam/TestPlans/GnomeControlCenter Regression potential Attention to the apps, network, privacy and users panels, as those had the most substantial changes. ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: gnome-control-center (Ubuntu Noble) Importance: Undecided Assignee: Nathan Teodosio (nteodosio) Status: New ** Tags: noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2080611 Title: [SRU] Backport gnome-control-center 46.4 to Noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2080611/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080611] Re: [SRU] Backport gnome-control-center 46.4 to Noble
Patch: https://salsa.debian.org/gnome-team/gnome-control- center/-/merge_requests/43.diff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2080611 Title: [SRU] Backport gnome-control-center 46.4 to Noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2080611/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061918] Re: package thunderbird 2:1snap1-0ubuntu1 failed to install/upgrade: new thunderbird package pre-installation script subprocess returned error exit status 1
Duplicate LP:2080578: Upgrading from 22.04 to 24.04 (judging by the line "Unpacking libibus-1.0-5:amd64 (1.5.29-2) over (1.5.26-4) ..." in the log) caused the same abortion. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061918 Title: package thunderbird 2:1snap1-0ubuntu1 failed to install/upgrade: new thunderbird package pre-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2061918/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061918] Re: package thunderbird 2:1snap1-0ubuntu1 failed to install/upgrade: new thunderbird package pre-installation script subprocess returned error exit status 1
** Also affects: chromium-browser (Ubuntu) Importance: Undecided Status: New ** Changed in: thunderbird (Ubuntu) Status: Fix Released => Confirmed ** Changed in: chromium-browser (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061918 Title: package thunderbird 2:1snap1-0ubuntu1 failed to install/upgrade: new thunderbird package pre-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2061918/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080578] Re: package chromium-browser 1:111.0.5563.8-0ubuntu1~ppa1~22.04.1 failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 1
*** This bug is a duplicate of bug 2061918 *** https://bugs.launchpad.net/bugs/2061918 ** This bug has been marked a duplicate of bug 2061918 package thunderbird 2:1snap1-0ubuntu1 failed to install/upgrade: new thunderbird package pre-installation script subprocess returned error exit status 1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2080578 Title: package chromium-browser 1:111.0.5563.8-0ubuntu1~ppa1~22.04.1 failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2080578/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080222] Re: get_keyring/get_password trying kdewallet even though it is not installed
Hi Dmitry, > I think the right solution here would be to specify explicitly the desired backend (most likely keyring.backends.SecretService.Keyring) in the configuration file as described in the README: I did as you suggested and I confirm it works now, thank you! I also confirmed that removing kwallet6 solved it. However, I do not think that that default state is acceptable: I'm sure I'm not the only one who has Qt and GTK programs installed and we cannot expect users to create a cryptic file. This must be a bug somewhere. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2080222 Title: get_keyring/get_password trying kdewallet even though it is not installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-keyring/+bug/2080222/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064211] Re: /usr/bin/update-manager:AttributeError::available:start_available:refresh_cache:_get_ua_security_status
** Tags removed: verification-failed-bionic verification-failed-focal verification-failed-xenial verification-needed ** Tags added: verification-done verification-done-bionic verification-done-focal verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064211 Title: /usr/bin/update- manager:AttributeError::available:start_available:refresh_cache:_get_ua_security_status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/2064211/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 2007652] Re: [snap] PWA don't launch as applications, just another chromium window
If it is accepted in 24.10 — and I'm reasonably confident it will —, I'll afterwards file a backport for 24.04. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2007652 Title: [snap] PWA don't launch as applications, just another chromium window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2007652/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080222] [NEW] get_keyring/get_password trying kdewallet even though it is not installed
Public bug reported:
I got this error dialog attached when trying 'ppa wait ...' (from ppa-
dev-tools). Sorry but LC_ALL=C LANG=en did not help to get it in
English.
I do have kwallet installed as it is pulled in as a dependency by
Quassel, but rather is normally gnome-keyring in use (that's whence I
get a password prompt on log in).
--->
dpkg -l|grep -E 'keyring|wallet'
ii debian-ports-archive-keyring 2024.02.02
all GnuPG archive keys of the debian-ports archive
ii gnome-keyring 46.2-1
amd64GNOME keyring services (daemon and tools)
ii gnome-keyring-pkcs11:amd6446.2-1
amd64GNOME keyring module for the PKCS#11 module loading
library
ii kwallet6 6.5.0-0ubuntu2
amd64safe desktop-wide storage for passwords - kwalletd
daemon
ii libkf5wallet-bin 5.116.0-0ubuntu2
all transitional dummy package
ii libkf5wallet-data 5.116.0-0ubuntu2
all Secure and unified container for user passwords.
ii libkf5wallet5:amd64 5.116.0-0ubuntu2
amd64Secure and unified container for user passwords.
ii libkf6wallet-data 6.5.0-0ubuntu2
all safe desktop-wide storage for passwords - data files
ii libkf6wallet6:amd64 6.5.0-0ubuntu2
amd64safe desktop-wide storage for passwords - shared library
ii libkf6walletbackend6:amd646.5.0-0ubuntu2
amd64safe desktop-wide storage for passwords - backend
library
ii libpam-gnome-keyring:amd6446.2-1
amd64PAM module to unlock the GNOME keyring upon login
ii python3-keyring 25.3.0-1
all store and access your passwords safely
ii ubuntu-keyring2023.11.28.1
all GnuPG keys of the Ubuntu archive
<---
--->
% LC_ALL=C LANG=en ./scripts/ppa wait nteodosio:rebuilds
Traceback (most recent call last):
File "/home/nteodosio/canonical/ppa-dev-tools/./scripts/ppa", line 1148, in
retval = main(args)
^^
File "/home/nteodosio/canonical/ppa-dev-tools/./scripts/ppa", line 1118, in
main
config = create_config(lp, args)
^^^
File "/home/nteodosio/canonical/ppa-dev-tools/./scripts/ppa", line 517, in
create_config
elif lp.me:
^
File "/home/nteodosio/canonical/ppa-dev-tools/ppa/lp.py", line 134, in
__getattr__
instance = super(Lp, self).__getattribute__('_instance')
^
File "/home/nteodosio/canonical/ppa-dev-tools/ppa/lp.py", line 121, in
_instance
self._get_instance_from_login()
File "/home/nteodosio/canonical/ppa-dev-tools/ppa/lp.py", line 108, in
_get_instance_from_login
return self._service.login_with(
^
File "/usr/lib/python3/dist-packages/launchpadlib/launchpad.py", line 693, in
login_with
return cls._authorize_token_and_login(
^^^
File "/usr/lib/python3/dist-packages/launchpadlib/launchpad.py", line 438, in
_authorize_token_and_login
cached_credentials = credential_store.load(
^^
File "/usr/lib/python3/dist-packages/launchpadlib/credentials.py", line 322,
in load
return self.do_load(unique_key)
File "/usr/lib/python3/dist-packages/launchpadlib/credentials.py", line 402,
in do_load
credential_string = keyring.get_password(
^
File "/usr/lib/python3/dist-packages/keyring/core.py", line 63, in
get_password
return get_keyring().get_password(service_name, username)
^^
File "/usr/lib/python3/dist-packages/keyring/backends/chainer.py", line 49,
in get_password
password = keyring.get_password(service, username)
^^^
File "/usr/lib/python3/dist-packages/keyring/backends/kwallet.py", line 110,
in get_password
raise KeyringLocked("Failed to unlock the keyring!")
keyring.errors.KeyringLocked: Failed to unlock the keyring!
<---
ProblemType: Bug
DistroRelease: Ubuntu 24.10
Package: python3-keyring 25.3.0-1
ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
Uname: Linux 6.8.0-31-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.30.0-0ubuntu1
Architecture: amd64
CasperMD5Check
[Bug 2080220] [NEW] The specified keyring may be incorrect or out of date
Public bug reported: ---> % mk-sbuild --arch=amd64 --distro=ubuntu bionic I: Retrieving InRelease I: Checking Release signature E: Release signed by unknown key (key id 3B4FE6ACC0B21F32) The specified keyring /usr/share/keyrings/ubuntu-archive-removed-keys.gpg may be incorrect or out of date. You can find the latest Debian release key at https://ftp-master.debian.org/keys.html <--- Resolved by deleting said key-ring and retrying the command. Also note the failed command nonetheless creates a mostly empty /var/lib/schroot/chroots/bionic-amd64/ so trying mk-sbuild again fails without removing the directory first. % sbuild --version sbuild (Debian sbuild) 0.85.10 (30 May 2024) % lsb_release -r Release:24.10 ** Affects: sbuild (Ubuntu) Importance: Undecided Status: New ** Description changed: ---> % mk-sbuild --arch=amd64 --distro=ubuntu bionic I: Retrieving InRelease I: Checking Release signature E: Release signed by unknown key (key id 3B4FE6ACC0B21F32) -The specified keyring /usr/share/keyrings/ubuntu-archive-removed-keys.gpg may be incorrect or out of date. -You can find the latest Debian release key at https://ftp-master.debian.org/keys.html + The specified keyring /usr/share/keyrings/ubuntu-archive-removed-keys.gpg may be incorrect or out of date. + You can find the latest Debian release key at https://ftp-master.debian.org/keys.html <--- Resolved by deleting said key-ring and retrying the command. Also note the failed command nonetheless creates a mostly empty /var/lib/schroot/chroots/bionic-amd64/ so trying mk-sbuild again fails without removing the directory first. + + % sbuild --version + sbuild (Debian sbuild) 0.85.10 (30 May 2024) + % lsb_release -r + Release:24.10 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2080220 Title: The specified keyring may be incorrect or out of date To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sbuild/+bug/2080220/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2080024] Re: Can't load some pages with chromium (steam, ebay, snyk.io)
Alright, let us know if the issue appears again. ** Changed in: chromium-browser (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2080024 Title: Can't load some pages with chromium (steam, ebay, snyk.io) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2080024/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2019249] Re: wishlist: how about changing update-manager description layout to horizontal ?
** Merge proposal linked: https://code.launchpad.net/~yurenchen/ubuntu/+source/update-manager/+git/update-manager/+merge/472837 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2019249 Title: wishlist: how about changing update-manager description layout to horizontal ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/2019249/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 2007652] Re: [snap] PWA don't launch as applications, just another chromium window
Glad to hear that, thank you for testing! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2007652 Title: [snap] PWA don't launch as applications, just another chromium window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2007652/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 2007652] Re: [snap] PWA don't launch as applications, just another chromium window
I submitted a build for 24.04 in that PPA, will be there by the end of the day if nothing goes wrong. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2007652 Title: [snap] PWA don't launch as applications, just another chromium window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2007652/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2077117] Re: settings - mouse&touchpad - scroll direction images empty
> Try tweaking .illustrated-row in shell/style.css ? That is only in force for picture-disabled, so nothing to do there. > Alternatively, sadly, try querying the validity of self->media_stream in panels/common/cc-illustrated-row.c and hide the widget when the media stream isn't working. I tried with gtk_media_stream_get_error() but it relays no error. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2077117 Title: settings - mouse&touchpad - scroll direction images empty To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/2077117/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2077117] Re: settings - mouse&touchpad - scroll direction images empty
I confirm they play in Oracular. In the Control Center however they are still just orange squares. Infuriating. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2077117 Title: settings - mouse&touchpad - scroll direction images empty To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/2077117/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2077117] Re: settings - mouse&touchpad - scroll direction images empty
Thanks for your help on this. Those videos do play if gstreamer*bad is not installed, but if it is installed, then they do not play: ---> % LC_ALL=C gst-play-1.0 edge-scroll.webm Press 'k' to see a list of keyboard shortcuts. Now playing /tmp/edge-scroll.webm ERROR Internal data stream error. for file:///tmp/edge-scroll.webm ERROR debug information: ../gst/matroska/matroska-demux.c(6115): gst_matroska_demux_loop (): /GstPlayBin3:playbin/GstURIDecodeBin3:uridecodebin3/GstURISourceBin:urisourcebin0/GstParseBin:parsebin0/GstMatroskaDemux:matroskademux0: streaming stopped, reason not-negotiated (-4) Reached end of play list. % sudo apt remove gstreamer*bad ... % LC_ALL=C gst-play-1.0 edge-scroll.webm #Plays fine despite the error message Press 'k' to see a list of keyboard shortcuts. Now playing /tmp/edge-scroll.webm Redistribute latency... ERROR Output window was closed for file:///tmp/edge-scroll.webm ERROR debug information: ../sys/xvimage/xvimagesink.c(586): gst_xv_image_sink_handle_xevents (): /GstPlayBin3:playbin/GstPlaySink:playsink/GstBin:vbin/GstAutoVideoSink:videosink/GstXvImageSink:videosink-actual-sink-xvimage Reached end of play list. <--- -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2077117 Title: settings - mouse&touchpad - scroll direction images empty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2077117/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2079043] Re: Please merge Orca 47 RC from Debian experimental
** Patch added: "deb-ubu.diff" https://bugs.launchpad.net/ubuntu/+source/orca/+bug/2079043/+attachment/5813680/+files/deb-ubu.diff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2079043 Title: Please merge Orca 47 RC from Debian experimental To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/orca/+bug/2079043/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2079043] [NEW] Please merge Orca 47 RC from Debian experimental
Public bug reported: Built fine in 24.10. ** Affects: orca (Ubuntu) Importance: Undecided Assignee: Nathan Teodosio (nteodosio) Status: Triaged ** Patch added: "ubu-ubu.diff" https://bugs.launchpad.net/bugs/2079043/+attachment/5813679/+files/ubu-ubu.diff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2079043 Title: Please merge Orca 47 RC from Debian experimental To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/orca/+bug/2079043/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2076084] Re: Additional drivers tab cause uncancellable operation that prevents the program from closing
** Description changed: Start software-properties-gtk, switch to additional drivers tab. The program will start consuming 100% CPU for quite some time (many seconds or minutes depending on the machine). There is however no way to cancel the operation other than killing software-properties. Trying to close the window or clicking Close button hangs. Test plans -- 1. Start software-properties-gtk 1.1. Go to additional drivers tab. 1.2. Click close at the south-east corner or close the window via your window manager. Expected. Window closes immediately. 4. Start software-properties-gtk 4.1. Go to additional drivers tab and wait. - Expected: The viewport will at the end say that either no drivers are available or show a list of drivers such as in the drivers-list.png attachment. The cancel and retry buttons are gone in the latter case. + Expected: The viewport will at the end say that either no drivers are available or show a list of drivers such as in the drivers-list.png attachment. The cancel/retry buttons are gone in the latter case. 2. Start software-properties-gtk and 'top' in a terminal 2.1. Go to additional drivers tab. Expected: The 'python3' command starts consuming 100% CPU. 2.2. Click cancel. - Expected: The aforementioned process is no longer hogging the CPU, indicating that the driver scan really stopped. The retry button is clickable but cancel is not. + Expected: The aforementioned process is no longer hogging the CPU, indicating that the driver scan really stopped. The button is now retry, clickable. 2.3. Click retry. - Expected: The 'python3' command starts consuming 100% CPU. The retry button is not clickable but cancel ist. + Expected: The 'python3' command starts consuming 100% CPU. The button is now cancel. 3. Start software-properties-gtk and 'top' in a terminal 3.1. Go to additional drivers tab. 3.2. Get the PID of the 'python3' process consuming 100% CPU and kill it with kill -29 PID - Expected: The viewport says "An error blabla. Exit status: -29." Retry is clickable but cancel is not. + Expected: The viewport reports the error. Retry is clickable. 5. Start software-properties-gtk 5.1. Introduce a unconditional exception in /usr/lib/python3/dist-packages/UbuntuDrivers/detect.py:system_device_drivers, e.g.: ---> --- /usr/lib/python3/dist-packages/UbuntuDrivers/detect.py +++ /usr/lib/python3/dist-packages/UbuntuDrivers/detect.py @@ -866,4 +866,5 @@ def system_device_drivers(apt_cache=None, sys_path=None, freeonly=False): +print(fooo) '''Get by-device driver packages that are available for the system. <--- 5.2. Go to additional drivers tab. Expected: "An error occurred while searching for drivers."; In the terminal, the backtrace is shown: ---> Traceback (most recent call last): - File "/home/nteodosio/canonical/ubuntu-pro/software-properties/softwareproperties/gtk/SoftwarePropertiesGtk.py", line 1456, in detect_drivers - raise(self.p.exception) + File "/home/nteodosio/canonical/ubuntu-pro/software-properties/softwareproperties/gtk/SoftwarePropertiesGtk.py", line 1456, in detect_drivers + raise(self.p.exception) Exception: Traceback (most recent call last): - File "/home/nteodosio/canonical/ubuntu-pro/software-properties/softwareproperties/gtk/SoftwarePropertiesGtk.py", line 121, in run - multiprocessing.Process.run(self) - File "/usr/lib/python3.12/multiprocessing/process.py", line 108, in run - self._target(*self._args, **self._kwargs) - File "/home/nteodosio/canonical/ubuntu-pro/software-properties/softwareproperties/gtk/SoftwarePropertiesGtk.py", line 1437, in wrapper_system_device_drivers - devices = detect.system_device_drivers(cache) - ^^^ - File "/usr/lib/python3/dist-packages/UbuntuDrivers/detect.py", line 919, in system_device_drivers - print(fo) - ^^ + File "/home/nteodosio/canonical/ubuntu-pro/software-properties/softwareproperties/gtk/SoftwarePropertiesGtk.py", line 121, in run + multiprocessing.Process.run(self) + File "/usr/lib/python3.12/multiprocessing/process.py", line 108, in run + self._target(*self._args, **self._kwargs) + File "/home/nteodosio/canonical/ubuntu-pro/software-properties/softwareproperties/gtk/SoftwarePropertiesGtk.py", line 1437, in wrapper_system_device_drivers + devices = detect.system_device_drivers(cache) + ^^^ + File "/usr/lib/python3/dist-packages/UbuntuDrivers/detect.py", line 919, in system_device_drivers + print(fo) + ^^ NameError: name 'fo' is not defined <--- -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2076084 Title: Additional drivers tab cause uncancellable operation that prevents the program from closi
[Bug 2072772] Re: The package is build without malcontent
Merge request: https://salsa.debian.org/gnome-team/gnome-control- center/-/merge_requests/41.diff ** Changed in: gnome-control-center (Ubuntu) Status: Incomplete => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072772 Title: The package is build without malcontent To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2072772/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2072772] Re: The package is build without malcontent
** Changed in: gnome-control-center (Ubuntu) Status: Fix Released => Incomplete ** Changed in: gnome-control-center (Ubuntu Noble) Status: Triaged => Incomplete ** Changed in: gnome-control-center (Ubuntu) Assignee: (unassigned) => Nathan Teodosio (nteodosio) ** Changed in: gnome-control-center (Ubuntu Noble) Assignee: (unassigned) => Nathan Teodosio (nteodosio) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072772 Title: The package is build without malcontent To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2072772/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2078827] Re: [MIR] luit
** Description changed: - #Stub# + [Availability] + - The package luit is already in Ubuntu universe. + - The package luit build for the architectures it is designed to work on + - It currently builds and works for architectures: amd64 arm64 armhf ppc64el + riscv64 s390x + - Link to package https://launchpad.net/ubuntu/+source/luit + + [Rationale] + - The package luit is required in Ubuntu main for support to + transcoding some encodings to the terminal's. E.g. + https://xtermjs.org/docs/guides/encoding/. + + - The package luit will not generally be useful for a large part of + our user base, but is important/helpful still for legacy setups + that already rely on luit. + + - The package luit is a recommends of x11-utils (main) we already support + and also xterm (universe). + Note: luit was in x11-utils (main) but was broken off to its own package + after 7.7+6 as per https://launchpad.net/ubuntu/+source/x11-utils/7.7+6. + That is 22.04 LTS was had it in main + (https://launchpadlibrarian.net/592958282/buildlog_ubuntu-jammy-amd64.x11-utils_7.7+5build2_BUILDING.txt.gz), + so it is OK to take the standalone luit package to main too. + + - There is no other/better way to solve this that is already in main or + should go universe->main instead of this. + Note: There is iconv but it has at least one limitation, namely it cannot + deal with continuous input, rather it needs the whole text, see for instance + https://unix.stackexchange.com/q/35662. + + - The binary package luit needs to be in main to continue the support of + set ups with legacy encodings. + + - It would be great and useful to community/processes to have the + package luit in Ubuntu main, but there is no definitive deadline. + + + ---> + #Old stub, to be deleted after confirmation that the above is enough# This is broken out of x11-utils and thereby should be ok to go to main, but it actually isn't part of the same in Jammy: https://launchpadlibrarian.net/592958282/buildlog_ubuntu-jammy- amd64.x11-utils_7.7+5build2_BUILDING.txt.gz recommends in Noble and later: https://launchpadlibrarian.net/746621535/buildlog_ubuntu-oracular-amd64.x11-utils_7.7+7_BUILDING.txt.gz The changelog says https://launchpad.net/ubuntu/+source/x11-utils/7.7+6 * Removed luit, which is now packaged separately with a different upstream (closes: #1006193, #1003021, #1003130, #816289). Added recommends for that package. - Same problem in Noble, but there luit didn't exist and hence was - ignored. + Same problem in Noble, but there luit didn't exist and hence was ignored. + <--- ** Changed in: luit (Ubuntu) Assignee: Jeremy Bícha (jbicha) => Nathan Teodosio (nteodosio) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2078827 Title: [MIR] luit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/luit/+bug/2078827/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2077117] Re: settings - mouse&touchpad - scroll direction images empty
It's pretty mysterious how those are chosen. I found no control on the GTK side for it. As a stop-gap we could just un-map those rectangles in case codecalpha is missing, if we think that the current behavior warrants it, but for all I know in a new release of it could well start loading a different plug-in in gstreamer*good with which the animations would work. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2077117 Title: settings - mouse&touchpad - scroll direction images empty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk4/+bug/2077117/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 2011281] Re: chromium snap upgrade "lost" my passwords
Do you remember from which version of Ubuntu you upgraded and how exactly you carried it out (i.e. manually by editing /etc/apt/sources.list, do-release-upgrade, ...)? This gives me a way to try to reproduce it myself. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2011281 Title: chromium snap upgrade "lost" my passwords To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2011281/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2077117] Re: settings - mouse&touchpad - scroll direction images empty
How does GTK choose the plug-in? Are we able to change it? VPX is in good and supports VP9 decoding too: % gst-inspect-1.0 vpx vp8dec: On2 VP8 Decoder vp8enc: On2 VP8 Encoder vp9dec: On2 VP9 Decoder vp9enc: On2 VP9 Encoder % gst-inspect-1.0 codecalpha alphacombine: Alpha Combiner codecalphademux: CODEC Alpha Demuxer vp8alphadecodebin: VP8 Alpha Decoder vp9alphadecodebin: VP9 Alpha Decoder -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2077117 Title: settings - mouse&touchpad - scroll direction images empty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk4/+bug/2077117/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2077117] Re: settings - mouse&touchpad - scroll direction images empty
Feel free to take over the bug, you seem to have a better idea of what is going on. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2077117 Title: settings - mouse&touchpad - scroll direction images empty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk4/+bug/2077117/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2077117] Re: settings - mouse&touchpad - scroll direction images empty
** Changed in: gnome-control-center (Ubuntu) Status: Triaged => In Progress ** Changed in: gnome-control-center (Ubuntu) Assignee: (unassigned) => Nathan Teodosio (nteodosio) ** Changed in: gnome-control-center (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2077117 Title: settings - mouse&touchpad - scroll direction images empty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2077117/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2072772] Re: The package is build without malcontent
24.10: Sorry there was a small error in the Oracular patch, fixed now. ** Patch removed: "oracular+parentcontrol-malcontent+apps.patch" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2072772/+attachment/5812810/+files/oracular+parentcontrol-malcontent+apps.patch ** Patch added: "oracular+parentcontrol-malcontent+apps.patch" https://bugs.launchpad.net/bugs/2072772/+attachment/5812811/+files/oracular+parentcontrol-malcontent+apps.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072772 Title: The package is build without malcontent To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2072772/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2072772] Oracular patch
** Patch added: "oracular+parentcontrol-malcontent+apps.patch" https://bugs.launchpad.net/bugs/2072772/+attachment/5812810/+files/oracular+parentcontrol-malcontent+apps.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072772 Title: The package is build without malcontent To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2072772/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2072772] Re: The package is build without malcontent
24.04: Salsa has been unbearably slow so I'm not opening a merge request there. I attach the patch. Alternatively, merge the malcontent branch of https://salsa.debian.org/nteodosio/gnome-control-center. Tested that: - Without malcontent installed, apps show up normally, parent control is not available. - With malcontent installed, apps show up normally, parent control is available. ** Changed in: gnome-control-center (Ubuntu Noble) Status: Fix Committed => Triaged ** Patch added: "+parentcontrol-malcontent+apps.patch" https://bugs.launchpad.net/bugs/2072772/+attachment/5812777/+files/+parentcontrol-malcontent+apps.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072772 Title: The package is build without malcontent To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2072772/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2072772] Re: The package is build without malcontent
Sebastien clarified that this would be any user in the sudo group, so a normal Ubuntu user such as the one created during installation will have those rights. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072772 Title: The package is build without malcontent To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2072772/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2072772] Re: The package is build without malcontent
Can you please clarify what 'admin' user means in this context? Is it a user named 'admin' or is it a user with certain administration rights? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072772 Title: The package is build without malcontent To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2072772/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069564] Re: gnome-shell crashed with SIGTRAP in meta_wayland_compositor_new() from meta_context_start() from main() ["Failed to start X Wayland: Directory \"/tmp/.X11-unix\" is not writable"]
** Description changed: + If you are hitting this bug, please write your case in + https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3984. + + > it'd be good to know when this actually happens to evaluate why it + happens, and then evaluate if there is anything we should change. + + --- + The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 46.0-0ubuntu5.1, the problem page at https://errors.ubuntu.com/problem/a7dbd55723a8ea326d1ccf32e31fe307151786c2 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/. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2069564 Title: gnome-shell crashed with SIGTRAP in meta_wayland_compositor_new() from meta_context_start() from main() ["Failed to start X Wayland: Directory \"/tmp/.X11-unix\" is not writable"] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2069564/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069564] Re: gnome-shell crashed with SIGTRAP in meta_wayland_compositor_new() from meta_context_start() from main() ["Failed to start X Wayland: Directory \"/tmp/.X11-unix\" is not writable"]
Proposed https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3984. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2069564 Title: gnome-shell crashed with SIGTRAP in meta_wayland_compositor_new() from meta_context_start() from main() ["Failed to start X Wayland: Directory \"/tmp/.X11-unix\" is not writable"] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2069564/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069564] Re: gnome-shell crashed with SIGTRAP in meta_wayland_compositor_new() from meta_context_start() from main() ["Failed to start X Wayland: Directory \"/tmp/.X11-unix\" is not writable"]
Thanks, Pedro, but without the hard facts it is difficult to ascertain whether this is a bug. Namely, whoami; stat /tmp /tmp/.X11-unix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2069564 Title: gnome-shell crashed with SIGTRAP in meta_wayland_compositor_new() from meta_context_start() from main() ["Failed to start X Wayland: Directory \"/tmp/.X11-unix\" is not writable"] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2069564/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2077880] Re: The programm "Aktualisierugsverwaltung" does not start in Ubuntu 22.04
> ii ubuntu-advantage-tools 99+p22.04+vrelease+git20240821.1516 This version number is highly weird, you are using non-official repositories. You could paste the output of grep -r '^[^#]' /etc/apt/sources.list* to confirm that. Please follow up with Tuxedo's support. We only support machines that use the official Ubuntu archives. ** Changed in: update-manager (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2077880 Title: The programm "Aktualisierugsverwaltung" does not start in Ubuntu 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/2077880/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069564] Re: gnome-shell crashed with SIGTRAP in meta_wayland_compositor_new() from meta_context_start() from main() ["Failed to start X Wayland: Directory \"/tmp/.X11-unix\" is not writable"]
In the case that /tmp is owned by ourselves and it matches 0200 but not
0022, it is still writable but it would fail with the present error.
I do not know if this is actually an intended blockage and thus the
description is just not clear enough or if this is an edge case to
consider.
Nor do we know whether all the reports here would be solved by allowing
this scenario, namely {we are not root, /tmp is ours, /tmp/.X11-unix is
at least 0200}.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2069564
Title:
gnome-shell crashed with SIGTRAP in meta_wayland_compositor_new() from
meta_context_start() from main() ["Failed to start X Wayland:
Directory \"/tmp/.X11-unix\" is not writable"]
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2069564/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2077880] Re: The programm "Aktualisierugsverwaltung" does not start in Ubuntu 22.04
Can you please also respond to comment #6 above? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2077880 Title: The programm "Aktualisierugsverwaltung" does not start in Ubuntu 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/2077880/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069564] Re: gnome-shell crashed with SIGTRAP in meta_wayland_compositor_new() from meta_context_start() from main() ["Failed to start X Wayland: Directory \"/tmp/.X11-unix\" is not writable"]
This comes from ensure_x11_unix_perms, which is determining that the
/tmp/.X11-unix does not have at least permission bits 022:
--->
static gboolean
ensure_x11_unix_perms (GError **error)
{
/* Try to detect systems on which /tmp/.X11-unix is owned by neither root nor
* ourselves because in that case the owner can take over the socket we create
* (symlink races are fixed in linux 800179c9b8a1). This should not be
* possible in the first place and systems should come with some way to ensure
* that's the case (systemd-tmpfiles, polyinstantiation …).
*
* That check however only works if we see the root user namespace which might
* not be the case when running in e.g. toolbx (root and other user are all
* mapped to overflowuid). */
struct stat x11_tmp, tmp;
if (lstat (X11_TMP_UNIX_DIR, &x11_tmp) != 0)
{
g_set_error (error, G_IO_ERROR, g_io_error_from_errno (errno),
"Failed to check permissions on directory \"%s\": %s",
X11_TMP_UNIX_DIR, g_strerror (errno));
return FALSE;
}
if (lstat (TMP_UNIX_DIR, &tmp) != 0)
{
g_set_error (error, G_IO_ERROR, g_io_error_from_errno (errno),
"Failed to check permissions on directory \"%s\": %s",
TMP_UNIX_DIR, g_strerror (errno));
return FALSE;
}
/* If the directory already exists, it should belong to the same
* user as /tmp or belong to ourselves ...
* (if /tmp is not owned by root or ourselves we're in deep trouble) */
if (x11_tmp.st_uid != tmp.st_uid && x11_tmp.st_uid != getuid ())
{
g_set_error (error, G_IO_ERROR, G_IO_ERROR_PERMISSION_DENIED,
"Wrong ownership for directory \"%s\"",
X11_TMP_UNIX_DIR);
return FALSE;
}
/* ... be writable ... */
if ((x11_tmp.st_mode & 0022) != 0022)
{
g_set_error (error, G_IO_ERROR, G_IO_ERROR_PERMISSION_DENIED,
"Directory \"%s\" is not writable",
X11_TMP_UNIX_DIR);
return FALSE;
}
<---
So the bug is not in Mutter.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2069564
Title:
gnome-shell crashed with SIGTRAP in meta_wayland_compositor_new() from
meta_context_start() from main() ["Failed to start X Wayland:
Directory \"/tmp/.X11-unix\" is not writable"]
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2069564/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2077880] Re: The programm "Aktualisierugsverwaltung" does not start in Ubuntu 24.02
Please also edit the title of the bug report to include the right Ubuntu version as 24.02 does not exist, did you mean 24.04? You can use the settings application to find the exact release version or run 'lsb_release -a' in a terminal. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2077880 Title: The programm "Aktualisierugsverwaltung" does not start in Ubuntu 24.02 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/2077880/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2077880] Re: The programm "Aktualisierugsverwaltung" does not start in Ubuntu 24.02
Hi, nothing to apologize, I'm the one who sent a dense message. Can you open a terminal and enter dpkg -l|grep -e ubuntu-adva -e ubuntu-pro and paste the output here? > What shall I do to make it work? I think you are missing the ubuntu-pro-client package. So you could open a terminal and enter sudo apt install ubuntu-pro-client (answer "yes" to the prompt). Am 28/08/2024 um 13:28 schrieb 2077...@bugs.launchpad.net: > Am 28.08.24 um 12:45 schrieb Nathan Teodosio: > > What is > > > >dpkg -l|grep -e ubuntu-adva -e ubuntu-pro > > > > Do you have https://github.com/FreeOpcUa/opcua-client-gui installed? > > Check https://github.com/canonical/ubuntu-pro-client/issues/2434. > > > > ** Bug watch added: github.com/canonical/ubuntu-pro-client/issues #2434 > > https://github.com/canonical/ubuntu-pro-client/issues/2434 > > > sorry, I am only a simple user, and do not understand, what you mean. > What shall I do to make it work? > ** Description changed: - I tried to start it several times, also after reboot. Bit there is no + I tried to start it several times, also after reboot. But there is no reaction and no way to re-install it... + + Traceback (most recent call last): +File "/usr/bin/update-manager", line 40, in + from UpdateManager.UpdateManager import UpdateManager +File "/usr/lib/python3/dist-packages/UpdateManager/UpdateManager.py", + line 30, in + import uaclient.api.u.pro.packages.updates.v1 as ua + ModuleNotFoundError: No module named 'uaclient' -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2077880 Title: The programm "Aktualisierugsverwaltung" does not start in Ubuntu 24.02 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/2077880/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2077880] Re: The programm "Aktualisierugsverwaltung" does not start in Ubuntu 24.02
What is dpkg -l|grep -e ubuntu-adva -e ubuntu-pro Do you have https://github.com/FreeOpcUa/opcua-client-gui installed? Check https://github.com/canonical/ubuntu-pro-client/issues/2434. ** Bug watch added: github.com/canonical/ubuntu-pro-client/issues #2434 https://github.com/canonical/ubuntu-pro-client/issues/2434 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2077880 Title: The programm "Aktualisierugsverwaltung" does not start in Ubuntu 24.02 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/2077880/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2077968] Re: repeated 'Problem in chrome' pop-up messages every 3m
Glad to hear that! Anyway a single crash dump there obviously shouldn't spam error windows so I'll leave this open to Whoopsie. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2077968 Title: repeated 'Problem in chrome' pop-up messages every 3m To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/2077968/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2077290] Re: GLArea transparency broken
I confirmed the fix in 24.04 and created https://salsa.debian.org/gnome- team/gtk3/-/merge_requests/24 for it. ** Description changed: + [Impact] + In Noble a GtkGlArea widget with transparency doesn't show the GTK widgets beneath it correctly. This was a regression fixed in https://gitlab.gnome.org/GNOME/gtk/-/commit/6754765a5a849ecbdd5c5fa60b5a6f80a968133e (released in 3.24.42). - Test Case: + [Test Case] Run gdkgears: $ apt source gtk+3.0 $ cd src/gtk+3.0-3.24.41 $ meson _build $ ninja -C _build $ ./_build/tests/gdkgears Click "Alpha" checkbox. Expected results: Gears are shown with Gtk window background behind them. Observed results: Uninitialized buffer is shown behind gears (commonly looks like repeated contents of old window frames). + + [Regression potential] + + Issues can be expected in GTK3 widgets with a transparent background. ** Summary changed: - GLArea transparency broken + [SRU] GLArea transparency broken -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2077290 Title: [SRU] GLArea transparency broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/2077290/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2077968] Re: repeated 'Problem in chrome' pop-up messages every 3m
Hi Sandy, thanks for the very clear and thorough bug report. I can see no issues on Chromium's side. I'm afraid that is indeed a Whoopsie problem. The > Your computer does not have enough free memory to automatically analyze the problem and send a report to the developers. looks very out of place in a machine with 32 GB, although last time Whoopsie had a new release was in April... No Chromium crashes in /var/crash/, I assume? For now you can work-around the issue by removing Whoopsie: 'apt remove whoopsie'. ** Also affects: whoopsie (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2077968 Title: repeated 'Problem in chrome' pop-up messages every 3m To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2077968/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2077290] Re: GLArea transparency broken
** Changed in: gtk+3.0 (Ubuntu Noble) Assignee: (unassigned) => Nathan Teodosio (nteodosio) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2077290 Title: GLArea transparency broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/2077290/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2077880] Re: The programm "Aktualisierugsverwaltung" does not start in Ubuntu 24.02
Any update-manager file in /var/crash/? Please open a terminal and enter 'update-manager'. Attach the output here. ** Changed in: update-manager (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2077880 Title: The programm "Aktualisierugsverwaltung" does not start in Ubuntu 24.02 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/2077880/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2077272] Re: Gnome's large text accessibility setting not reflect in Chromium in Wayland
So you mean 'in Chrome', right? I can indeed no longer reproduce #12.0... Either I screwed up during testing or something changed in between, which is highly unlikely in such a short time frame. Anyway, added debug statements confirm that Chromium is running with GTK3. Additionally, it DOES receive the resolution signal, but in Ozone Wayland, it thinks the display configuration did nonetheless not change and does not goes further. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2077272 Title: Gnome's large text accessibility setting not reflect in Chromium in Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2077272/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2077272] Re: Gnome's large text accessibility setting not reflect in Chromium in Wayland
8. Chromium is using GTK 3. And the unsandboxed one is too, so the
difference in behavior does not lay on the different GTK versions. Might
be the signal not being caught in the sandbox... I'm building it with a
patch with debugging statements to verify that.
--->
# For snapped Chromium
% for p in $(ps ax | awk '/chrom/{print $1}'); do lsof -p $p | grep gtk; done
chrome 193331 nteodosio mem REG 7,28 10754
/snap/chromium/2934/gnome-platform/usr/lib/x86_64-linux-gnu/libgtk-3.so.0.2406.32
(stat: No such file or directory)
chrome 193331 nteodosio mem REG 7,28 10043
/snap/chromium/2934/gnome-platform/usr/lib/x86_64-linux-gnu/gtk-3.0/3.0.0/immodules/im-cedilla.so
(stat: No such file or directory)
chrome 193331 nteodosio mem REG 7,28 16313
/snap/chromium/2934/gnome-platform/usr/share/locale/de/LC_MESSAGES/gtk30-properties.mo
(stat: No such file or directory)
chrome 193331 nteodosio mem REG 7,28 16314
/snap/chromium/2934/gnome-platform/usr/share/locale/de/LC_MESSAGES/gtk30.mo
(stat: No such file or directory)
# For unsandboxed Chromium
% for p in $(ps ax | awk '/chrom/{print $1}'); do lsof -p $p | grep gtk; done
chrome 196401 nteodosio mem REG 252,1 8128032 17310742
/usr/lib/x86_64-linux-gnu/libgtk-3.so.0.2411.32
chrome 196401 nteodosio mem REG 252,1 14752 17958459
/usr/lib/x86_64-linux-gnu/gtk-3.0/3.0.0/immodules/im-cedilla.so
<---
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2077272
Title:
Gnome's large text accessibility setting not reflect in Chromium in
Wayland
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2077272/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2077272] Re: Gnome's large text accessibility setting not reflect in Chromium in Wayland
...Chromium builds against GTK 3 but a different version may be loaded at runtime. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2077272 Title: Gnome's large text accessibility setting not reflect in Chromium in Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2077272/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2077272] Re: Gnome's large text accessibility setting not reflect in Chromium in Wayland
3.1. In GTK4 Chromium listens to the gtk-xft-dpi signal in //ui/gtk/gtk_ui.cc, thereat calling UpdateDeviceScaleFactor. In GTK3 it listens to screen resolution's notify::resolution only. Todo: Confirm the GTK version and whether the respective signal is actually caught and if so why it cannot do what they want. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2077272 Title: Gnome's large text accessibility setting not reflect in Chromium in Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2077272/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2077272] Re: Gnome's large text accessibility setting not reflect in Chromium in Wayland
0. Unsandboxed Chromium in Wayland ((unsupported and just for testing purposes!) /snap/chromium_edge/current/usr/lib/chromium-browser/chrome --ozone-platform-hint=wayland) has no issues responding to 'large text' setting. This must be a downstream problem. 1. Chromium in the sandbox can see changes to text-scaling-factor via gsettings: nteodosio@canonical:/home/nteodosio$ gsettings get org.gnome.desktop.interface text-scaling-factor 1.0 #After changing to 1.5 in the host...: nteodosio@canonical:/home/nteodosio$ gsettings get org.gnome.desktop.interface text-scaling-factor 1.5 2. It moreover acknowledges the change in that setting with: (chrome:33484): Gdk-DEBUG: 10:20:33.195: Using changed portal setting org.gnome.desktop.interface text-scaling-factor: 1.5 3. Judging by //gdk/wayland/gdkdisplay-wayland.c, GTK gets it from the settings portal when a Gsetting changes. All Gnome applications (but the here discussed snapped Chromium on Ozone) respond. However, in the stderr one does see 4. Why does Chromium bundle the GTK tree (in //third_party/wayland- protocols), though? At any rate it does not seem to use it: The debug statements I injected there are never triggered. 5. There is a --enable-wayland-server option but judging by the variable name (kAshEnableWaylandServer) it probably does nothing in Linux. Indeed, if the Wayland interface is disconnected from Chromium, it fails to launch regardless. 6. Xorg's side of it does not have any mention to text-scaling-factor and indeed no application responds to that Gsetting in Icewm or Dwm. But they do on Gnome-Shell (in Xorg). Gnome-Shell has //js/ui/status:_buildFontItem which responds to that setting, but I do not understand how it is able to propagate it to its windows (as these are other programs, other processes, right?). 7. --force-device-scale-factor is experimental and indeed Chromium goes wild with it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2077272 Title: Gnome's large text accessibility setting not reflect in Chromium in Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2077272/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2077272] Re: Gnome's large text accessibility setting not reflect in Chromium in Wayland
** Changed in: chromium-browser (Ubuntu) Status: Fix Released => Triaged ** Changed in: chromium-browser (Ubuntu) Assignee: (unassigned) => Nathan Teodosio (nteodosio) ** Description changed: Chromium - 127.0.6533.119 wayland - Chromium app ignores large text setting + Chromium app ignores large text setting if started with --ozone- + platform-hint=wayland. ProblemType: Bug DistroRelease: Ubuntu 24.04 ProcVersionSignature: Ubuntu 6.8.0-40.40-generic 6.8.12 Uname: Linux 6.8.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Aug 18 20:25:21 2024 InstallationDate: Installed on 2024-08-17 (1 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= Snap: chromium 127.0.6533.119 (latest/candidate) SnapSource: ubuntu/+source/chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2077272 Title: Gnome's large text accessibility setting not reflect in Chromium in Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2077272/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2077451] Software-properties-gtk times
** Attachment added: "softpp" https://bugs.launchpad.net/bugs/2077451/+attachment/5807630/+files/softpp -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2077451 Title: GNOME 47: GNOME apps don't launch for around the first 20 seconds after login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/2077451/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2077451] Re: GNOME 47: GNOME apps don't launch for around the first 20 seconds after login
I also get a very similar backtraces if I kill Nautilus but mine looks more useful (see at the end), as it even has the timeout=25000. Looks like I have been for two years stumbling in this very bug but just shrugging it off as it happens only in specific circumstances. To reproduce the bug consistently: (1-2 is unnecessary if you already log in to Ubuntu Gnome) 1. systemctl start sddm (any login manager should work I reckon). 2. login to Ubuntu. 3. logout from Ubuntu. 4. systemctl stop sddm. 5. startx /bin/dwm (or mwm, or icewm, ..., I reckon it will work with any unpretentious window manager). 6. start the Gnome application Looks like something dbus is left off running as a result of 3/4 and ---> #0 0x7d846e31b4cd in __GI___poll (fds=0x56462c63bbb0, nfds=1, timeout=25000) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7d846fabb66e in ??? () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7d846fa5cf77 in g_main_loop_run () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7d846ec0d392 in ??? () at /lib/x86_64-linux-gnu/libgio-2.0.so.0 #4 0x7d846eb6c8bc in g_initable_new_valist () at /lib/x86_64-linux-gnu/libgio-2.0.so.0 #5 0x7d846eb6c9ab in g_initable_new () at /lib/x86_64-linux-gnu/libgio-2.0.so.0 #6 0x7d846ec0f3db in g_dbus_proxy_new_for_bus_sync () at /lib/x86_64-linux-gnu/libgio-2.0.so.0 #7 0x7d846e8ac64a in ??? () at /lib/x86_64-linux-gnu/libadwaita-1.so.0 #8 0x7d846eab1bba in ??? () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #9 0x7d846eab3016 in g_object_new_with_properties () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #10 0x7d846eab3f71 in g_object_new () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #11 0x7d846e8ab50d in adw_settings_get_default () at /lib/x86_64-linux-gnu/libadwaita-1.so.0 #12 0x7d846e887116 in ??? () at /lib/x86_64-linux-gnu/libadwaita-1.so.0 #13 0x7d846eab1bba in ??? () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #14 0x7d846eab3016 in g_object_new_with_properties () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #15 0x7d846eab3f71 in g_object_new () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #16 0x7d846e883184 in ??? () at /lib/x86_64-linux-gnu/libadwaita-1.so.0 #17 0x7d846e86f3e8 in adw_init () at /lib/x86_64-linux-gnu/libadwaita-1.so.0 #18 0x7d846e841dd4 in ??? () at /lib/x86_64-linux-gnu/libadwaita-1.so.0 #19 0x56462ad5da14 in ??? () #20 0x7d846eac06bd in ??? () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #21 0x7d846eac07c1 in g_signal_emit_valist () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #22 0x7d846eac0883 in g_signal_emit () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #23 0x7d846ebd4f2e in g_application_register () at /lib/x86_64-linux-gnu/libgio-2.0.so.0 #24 0x7d846ebd54d0 in ??? () at /lib/x86_64-linux-gnu/libgio-2.0.so.0 #25 0x7d846ebd5823 in g_application_run () at /lib/x86_64-linux-gnu/libgio-2.0.so.0 #26 0x56462ad5633d in ??? () #27 0x7d846e22a1ca in __libc_start_call_main (main=main@entry=0x56462ad56260, argc=argc@entry=1, argv=argv@entry=0x7ffe1c7a0f18) at ../sysdeps/nptl/libc_start_call_main.h:58 #28 0x7d846e22a28b in __libc_start_main_impl (main=0x56462ad56260, argc=1, argv=0x7ffe1c7a0f18, init=, fini=, rtld_fini=, stack_end=0x7ffe1c7a0f08) at ../csu/libc-start.c:360 #29 0x56462ad563b5 in ??? () <--- ---> #0 0x79134011b4cd in __GI___poll (fds=0x5a732fa6f270, nfds=1, timeout=25000) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x79134170266e in ??? () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7913416a3f77 in g_main_loop_run () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x79134080d392 in ??? () at /lib/x86_64-linux-gnu/libgio-2.0.so.0 #4 0x79134076c8bc in g_initable_new_valist () at /lib/x86_64-linux-gnu/libgio-2.0.so.0 #5 0x79134076c9ab in g_initable_new () at /lib/x86_64-linux-gnu/libgio-2.0.so.0 #6 0x79134080d5c2 in g_dbus_proxy_new_sync () at /lib/x86_64-linux-gnu/libgio-2.0.so.0 #7 0x791340d47a97 in ??? () at /lib/x86_64-linux-gnu/libgtk-4.so.1 #8 0x791340d49926 in ??? () at /lib/x86_64-linux-gnu/libgtk-4.so.1 #9 0x791340ad4ead in ??? () at /lib/x86_64-linux-gnu/libgtk-4.so.1 #10 0x791340441dcf in ??? () at /lib/x86_64-linux-gnu/libadwaita-1.so.0 #11 0x5a732f3e0a14 in ??? () #12 0x7913406c06bd in ??? () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #13 0x7913406c07c1 in g_signal_emit_valist () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #14 0x7913406c0883 in g_signal_emit () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #15 0x7913407d4f2e in g_application_register () at /lib/x86_64-linux-gnu/libgio-2.0.so.0 #16 0x7913407d54d0 in ??? () at /lib/x86_64-linux-gnu/libgio-2.0.so.0 #17 0x7913407d5823 in g_application_run () at /lib/x86_64-linux-gnu/libgio-2.0.so.0 #18 0x5a732f3d933d in ??? () #19 0x79134002a1ca in __libc_start_call_main (main=main@entry=0x5a732f3d9260, argc=argc@entry=
[Bug 2077451] Re: GNOME 47: GNOME apps don't launch for around the first 20 seconds after login
You got a backtrace for Nautilus? Is it crashing too or are you interrupting it during this warm-up period of 20 s? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2077451 Title: GNOME 47: GNOME apps don't launch for around the first 20 seconds after login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/2077451/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2077313] Re: GTK 4.15.5: memorytexture, dmabufformats and scaling tests fail
Thank you Marco, and as you also pointed out, that is ---> GLogLevelFlags fatal_mask = (GLogLevelFlags) g_log_set_always_fatal ((GLogLevelFlags) G_LOG_FATAL_MASK); fatal_mask = (GLogLevelFlags) (fatal_mask | G_LOG_LEVEL_WARNING | G_LOG_LEVEL_CRITICAL); g_log_set_always_fatal (fatal_mask); <--- in https://gitlab.gnome.org/GNOME/glib/-/raw/main/glib/gtestutils.c. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2077313 Title: GTK 4.15.5: memorytexture, dmabufformats and scaling tests fail To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/2077313/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2077313] Re: GTK 4.15.5: memorytexture, dmabufformats and scaling tests fail
** Bug watch added: gitlab.gnome.org/GNOME/gtk/-/issues #6947 https://gitlab.gnome.org/GNOME/gtk/-/issues/6947 ** Also affects: gtk via https://gitlab.gnome.org/GNOME/gtk/-/issues/6947 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2077313 Title: GTK 4.15.5: memorytexture, dmabufformats and scaling tests fail To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/2077313/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2077403] Re: Difficult to identify open windows in high contrast mode
Yup, problem still there. ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2077403 Title: Difficult to identify open windows in high contrast mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/2077403/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2077403] [NEW] Difficult to identify open windows in high contrast mode
Public bug reported: Enable gnome-control-center > accessibility > seeing > large text and open a couple of windows. Observed: It is difficult to identify open windows in the dock. They are represented by a small dot to the left of their respective icons. Expected: It is easy to identify open windows in the dock. E.g., they are represented similarly to the active window, probably with a different color to distinguish them from it. The problem is more pronounced the smaller the dock size. Surprisingly, changing the accent color (as a more vivid color would help distinguishing it from the dunkel background) does not reflect the dots size for me, they are always blue. ProblemType: Bug DistroRelease: Ubuntu 24.10 Package: gnome-shell-extension-ubuntu-dock 90ubuntu1 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu4 Architecture: amd64 CasperMD5CheckResult: pass Date: Tue Aug 20 10:28:53 2024 InstallationDate: Installed on 2022-05-16 (827 days ago) InstallationMedia: Xubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) 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: a11y amd64 apport-bug oracular third-party-packages ** Attachment added: "Screenshot from 2024-08-20 10-02-42.png" https://bugs.launchpad.net/bugs/2077403/+attachment/5807298/+files/Screenshot%20from%202024-08-20%2010-02-42.png ** Tags added: a11y ** Summary changed: - Very difficult to see open windows in high contrast mode + Difficult to identify open windows in high contrast mode -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2077403 Title: Difficult to identify open windows in high contrast mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/2077403/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2077313] Re: GTK 4.15.5: memorytexture, dmabufformats and scaling tests fail
** Description changed:
MERGE REQUEST https://salsa.debian.org/gnome-
team/gtk4/-/merge_requests/25
+
+ UPSTREAM BUG: https://gitlab.gnome.org/GNOME/gtk/-/issues/6947
These GTK 4.15.5 tests fail:
--->
gtk:gdk / memorytexture
ERROR0.33s killed by signal 5 SIGTRAP
gtk:gdk / dmabufformats
ERROR0.21s killed by signal 5 SIGTRAP
gtk:gsk / scaling
ERROR0.25s killed by signal 5 SIGTRAP
<---
as per
https://launchpad.net/~jbicha/+archive/ubuntu/arch/+sourcepub/16394764/+listing-
archive-extra.
The full log of memorytexture is [1]. Its backtrace is
--->
#0 0x77ecf5fa in g_log_writer_default () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1 0x77ec6d64 in g_log_structured_array () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2 0x77ec6fb8 in g_log_structured_standard () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3 0x778c0db7 in gdk_vulkan_handle_result
(res=, called_function=0x77a10955 "vkCreateInstance")
at ../../../gdk/gdkvulkancontextprivate.h:68
#4 gdk_vulkan_handle_result
(res=, called_function=0x77a10955 "vkCreateInstance")
at ../../../gdk/gdkvulkancontextprivate.h:63
#5 gdk_display_create_vulkan_instance (display=0x555a14f0,
error=)
at ../../../gdk/gdkvulkancontext.c:1675
#6 0x77961ef3 in gdk_display_init_vulkan (display=0x555a14f0,
error=0x0)
at ../../../gdk/gdkvulkancontext.c:1771
#7 gsk_vulkan_device_get_for_display (display=0x555a14f0, error=0x0)
at ../../../gsk/gpu/gskvulkandevice.c:421
#8 0x7794c717 in gsk_gpu_renderer_realize
(renderer=0x60defa00, display=0x555a14f0, surface=0x0, error=0x0)
at ../../../gsk/gpu/gskgpurenderer.c:213
#9 0x778d863b in gsk_renderer_do_realize
(renderer=0x60defa00, display=display@entry=0x555a14f0,
surface=surface@entry=0x0, error=error@entry=0x0) at
../../../gsk/gskrenderer.c:271
#10 0x778df4c5 in gsk_renderer_realize_for_display
(renderer=, display=display@entry=0x555a14f0,
error=error@entry=0x0)
at ../../../gsk/gskrenderer.c:357
#11 0x6a41 in main (argc=, argv=)
at ../../../testsuite/gdk/memorytexture.c:1587
<---
gdkvulkancontextprivate.h:68 at #3 is nothing but the warning:
g_warning ("%s(): %s (%d)", called_function, gdk_vulkan_strerror
(res), res);
So I must conclude the test is failing because the warning is being
called, as if G_DEBUG=fatal-warnings had been passed, which it is
however not. Open questions are:
1. Why is this causing a SIGTRAP if no fatal-warnings is enabled?
2. Why do other tests (e.g. 511 gtk:reftest / reftest actionbar.ui) that
raise the same warning not fail?
Anyway, those three tests pass with vulkan-disable (number of skipped
remains unaltered) as a matter of fact. I'm proposing that as a merge
request[2] in Debian's bug tracking system.
[1] https://l.termbin.com/a0e2
[2] https://salsa.debian.org/gnome-team/gtk4/-/merge_requests/25
** Changed in: gtk4 (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2077313
Title:
GTK 4.15.5: memorytexture, dmabufformats and scaling tests fail
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk4/+bug/2077313/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2070889] Re: Chromium opens, but cursor remains in "loading" state within 15 seconds after opening.
Note that Chromium stable is now back to Xwayland until the real solution for LP:2077272 is found. You can however always enable it in about://flags or by invoking with chromium --ozone-platform-hint=auto. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2070889 Title: Chromium opens, but cursor remains in "loading" state within 15 seconds after opening. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2070889/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2077272] Re: Gnome's large text accessibility setting not reflect in Chromium in Wayland
Glad to hear everything fell into place. > I think it's best to hide this by default to avoid confusing users like me. I do not agree there. ** Changed in: chromium-browser (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2077272 Title: Gnome's large text accessibility setting not reflect in Chromium in Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2077272/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2077272] Re: Gnome's large text accessibility setting not reflect in Chromium in Wayland
Reversion committed: https://git.launchpad.net/~chromium-team/chromium- browser/+git/snap-from- source/commit/?id=66a95be63c03ae2b8c0c5a5d5ee612ded8b51dbd ** Changed in: chromium-browser (Ubuntu) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2077272 Title: Gnome's large text accessibility setting not reflect in Chromium in Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2077272/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2077272] Re: Gnome's large text accessibility setting not reflect in Chromium in Wayland
Answering my own question: > Is anything in your report a regression, i.e., a new issue that was not there a few days ago? This is a regression of Chromium in native Wayland, it does not occur in older releases. Chromium on Xwayland is fine as tested with --ozone-platform-hint=x11. ** Tags added: regression -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2077272 Title: Gnome's large text accessibility setting not reflect in Chromium in Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2077272/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2077313] Re: GTK 4.15.5: memorytexture, dmabufformats and scaling tests fail
Adding mesa-vulkan-drivers to build-depends makes the memorytexture and
scaling tests fail with segmentation fault, although it solves
dmabufformats test failure.
https://launchpad.net/~nteodosio/+archive/ubuntu/rebuilds/+build/28880496/+files/buildlog_ubuntu-
oracular-armhf.gtk4_4.15.5+ds-2_BUILDING.txt.gz
** Description changed:
+ MERGE REQUEST https://salsa.debian.org/gnome-
+ team/gtk4/-/merge_requests/25
+
These GTK 4.15.5 tests fail:
--->
gtk:gdk / memorytexture
ERROR0.33s killed by signal 5 SIGTRAP
gtk:gdk / dmabufformats
ERROR0.21s killed by signal 5 SIGTRAP
gtk:gsk / scaling
ERROR0.25s killed by signal 5 SIGTRAP
<---
as per
https://launchpad.net/~jbicha/+archive/ubuntu/arch/+sourcepub/16394764/+listing-
archive-extra.
The full log of memorytexture is [1]. Its backtrace is
--->
#0 0x77ecf5fa in g_log_writer_default () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1 0x77ec6d64 in g_log_structured_array () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2 0x77ec6fb8 in g_log_structured_standard () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3 0x778c0db7 in gdk_vulkan_handle_result
(res=, called_function=0x77a10955 "vkCreateInstance")
at ../../../gdk/gdkvulkancontextprivate.h:68
#4 gdk_vulkan_handle_result
(res=, called_function=0x77a10955 "vkCreateInstance")
at ../../../gdk/gdkvulkancontextprivate.h:63
#5 gdk_display_create_vulkan_instance (display=0x555a14f0,
error=)
at ../../../gdk/gdkvulkancontext.c:1675
#6 0x77961ef3 in gdk_display_init_vulkan (display=0x555a14f0,
error=0x0)
at ../../../gdk/gdkvulkancontext.c:1771
#7 gsk_vulkan_device_get_for_display (display=0x555a14f0, error=0x0)
at ../../../gsk/gpu/gskvulkandevice.c:421
#8 0x7794c717 in gsk_gpu_renderer_realize
(renderer=0x60defa00, display=0x555a14f0, surface=0x0, error=0x0)
at ../../../gsk/gpu/gskgpurenderer.c:213
#9 0x778d863b in gsk_renderer_do_realize
(renderer=0x60defa00, display=display@entry=0x555a14f0,
surface=surface@entry=0x0, error=error@entry=0x0) at
../../../gsk/gskrenderer.c:271
#10 0x778df4c5 in gsk_renderer_realize_for_display
(renderer=, display=display@entry=0x555a14f0,
error=error@entry=0x0)
at ../../../gsk/gskrenderer.c:357
#11 0x6a41 in main (argc=, argv=)
at ../../../testsuite/gdk/memorytexture.c:1587
<---
gdkvulkancontextprivate.h:68 at #3 is nothing but the warning:
g_warning ("%s(): %s (%d)", called_function, gdk_vulkan_strerror
(res), res);
So I must conclude the test is failing because the warning is being
called, as if G_DEBUG=fatal-warnings had been passed, which it is
however not. Open questions are:
1. Why is this causing a SIGTRAP if no fatal-warnings is enabled?
2. Why do other tests (e.g. 511 gtk:reftest / reftest actionbar.ui) that
raise the same warning not fail?
Anyway, those three tests pass with vulkan-disable (number of skipped
remains unaltered) as a matter of fact. I'm proposing that as a merge
request[2] in Debian's bug tracking system.
[1] https://l.termbin.com/a0e2
[2] https://salsa.debian.org/gnome-team/gtk4/-/merge_requests/25
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2077313
Title:
GTK 4.15.5: memorytexture, dmabufformats and scaling tests fail
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk4/+bug/2077313/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2077272] Re: Gnome's large text accessibility setting not reflect in Chromium in Wayland
** Summary changed: - Difference in behavior in wayland and xorg sessions + Gnome's large text accessibility setting not reflect in Chromium in Wayland ** Changed in: chromium-browser (Ubuntu) Status: New => Triaged ** Changed in: chromium-browser (Ubuntu) Importance: Undecided => Medium ** Description changed: Chromium - 127.0.6533.119 wayland - Chromium app ignores large text setting - There is no top bar named New Tab - chromuim - - - - - xorg - There is top bar named New Tab - chromuim - There is a bug "Chromium opens, but still loads within 15 seconds after opening" - - - - - What needs to be done: - 1)Remove top bar in xorg session. - The flatpak or aur version does not have this top bar. It should not be in any session. Moreover, Google Chrome deb version comes without a top bar. - - 2)Chromium app should not ignore large text setting in ubuntu in wayland - session - - 3)Chromium opens, but still loads within 15 seconds after opening - https://issues.chromium.org/issues/349835592 - https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2070889 - - It seems someone has created a custom patch for the Wayland session within the Snap format. Chromium now launches directly into the Wayland session without any delay. - As seen in the upstream bug, no one seems to know why this is happening or is willing to address it. In other words, Google doesn't seem to prioritize Linux development. - We need to figure out what this patch does, how to integrate it into the xorg session, and who can merge it into the upstream repository. This is a serious issue affecting all GNOME-based and chromium-based browser distributions and their forks, and it's being ignored. + Chromium app ignores large text setting ProblemType: Bug DistroRelease: Ubuntu 24.04 ProcVersionSignature: Ubuntu 6.8.0-40.40-generic 6.8.12 Uname: Linux 6.8.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Aug 18 20:25:21 2024 InstallationDate: Installed on 2024-08-17 (1 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= Snap: chromium 127.0.6533.119 (latest/candidate) SnapSource: ubuntu/+source/chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) ** Tags added: gnome wayland -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2077272 Title: Gnome's large text accessibility setting not reflect in Chromium in Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2077272/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2077272] Re: Difference in behavior in wayland and xorg sessions
For the top bar, there is a 'use system title bar and borders'. That works if you turn it off, doesn't it? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2077272 Title: Difference in behavior in wayland and xorg sessions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2077272/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2070889] Re: Chromium opens, but cursor remains in "loading" state within 15 seconds after opening.
> open normally on wayland session What exactly do you mean with open normally? As far as I know, it opened normally before too. The only abnormal thing was the spinning cursor. Do you mean the spinning cursor went away in 127.0.6533.119? The substantial difference in that version is that Chromium now runs natively in Wayland via Ozone. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2070889 Title: Chromium opens, but cursor remains in "loading" state within 15 seconds after opening. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2070889/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2077313] Re: GTK 4.15.5: memorytexture, dmabufformats and scaling tests fail
No. I'll try too. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2077313 Title: GTK 4.15.5: memorytexture, dmabufformats and scaling tests fail To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk4/+bug/2077313/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2077313] Re: GTK 4.15.5: memorytexture, dmabufformats and scaling tests fail
** Description changed:
These GTK 4.15.5 tests fail:
--->
gtk:gdk / memorytexture
ERROR0.33s killed by signal 5 SIGTRAP
gtk:gdk / dmabufformats
ERROR0.21s killed by signal 5 SIGTRAP
- gtk:gsk / scaling
ERROR0.25s killed by signal 5 SIGTRAP
+ gtk:gsk / scaling
ERROR0.25s killed by signal 5 SIGTRAP
<---
as per
https://launchpad.net/~jbicha/+archive/ubuntu/arch/+sourcepub/16394764/+listing-
archive-extra.
The full log of memorytexture is [1]. Its backtrace is
--->
#0 0x77ecf5fa in g_log_writer_default () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1 0x77ec6d64 in g_log_structured_array () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2 0x77ec6fb8 in g_log_structured_standard () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3 0x778c0db7 in gdk_vulkan_handle_result
- (res=, called_function=0x77a10955 "vkCreateInstance")
- at ../../../gdk/gdkvulkancontextprivate.h:68
+ (res=, called_function=0x77a10955 "vkCreateInstance")
+ at ../../../gdk/gdkvulkancontextprivate.h:68
#4 gdk_vulkan_handle_result
- (res=, called_function=0x77a10955 "vkCreateInstance")
- at ../../../gdk/gdkvulkancontextprivate.h:63
+ (res=, called_function=0x77a10955 "vkCreateInstance")
+ at ../../../gdk/gdkvulkancontextprivate.h:63
#5 gdk_display_create_vulkan_instance (display=0x555a14f0,
error=)
- at ../../../gdk/gdkvulkancontext.c:1675
+ at ../../../gdk/gdkvulkancontext.c:1675
#6 0x77961ef3 in gdk_display_init_vulkan (display=0x555a14f0,
error=0x0)
- at ../../../gdk/gdkvulkancontext.c:1771
+ at ../../../gdk/gdkvulkancontext.c:1771
#7 gsk_vulkan_device_get_for_display (display=0x555a14f0, error=0x0)
- at ../../../gsk/gpu/gskvulkandevice.c:421
+ at ../../../gsk/gpu/gskvulkandevice.c:421
#8 0x7794c717 in gsk_gpu_renderer_realize
- (renderer=0x60defa00, display=0x555a14f0, surface=0x0, error=0x0)
- at ../../../gsk/gpu/gskgpurenderer.c:213
+ (renderer=0x60defa00, display=0x555a14f0, surface=0x0, error=0x0)
+ at ../../../gsk/gpu/gskgpurenderer.c:213
#9 0x778d863b in gsk_renderer_do_realize
- (renderer=0x60defa00, display=display@entry=0x555a14f0,
surface=surface@entry=0x0, error=error@entry=0x0) at
../../../gsk/gskrenderer.c:271
+ (renderer=0x60defa00, display=display@entry=0x555a14f0,
surface=surface@entry=0x0, error=error@entry=0x0) at
../../../gsk/gskrenderer.c:271
#10 0x778df4c5 in gsk_renderer_realize_for_display
- (renderer=, display=display@entry=0x555a14f0,
error=error@entry=0x0)
- at ../../../gsk/gskrenderer.c:357
+ (renderer=, display=display@entry=0x555a14f0,
error=error@entry=0x0)
+ at ../../../gsk/gskrenderer.c:357
#11 0x6a41 in main (argc=, argv=)
- at ../../../testsuite/gdk/memorytexture.c:1587
+ at ../../../testsuite/gdk/memorytexture.c:1587
<---
gdkvulkancontextprivate.h:68 at #3 is nothing but the warning:
- g_warning ("%s(): %s (%d)", called_function, gdk_vulkan_strerror
+ g_warning ("%s(): %s (%d)", called_function, gdk_vulkan_strerror
(res), res);
So I must conclude the test is failing because the warning is being
called, as if G_DEBUG=fatal-warnings had been passed, which it is
however not. Open questions are:
1. Why is this causing a SIGTRAP if no fatal-warnings is enabled?
2. Why do other tests (e.g. 511 gtk:reftest / reftest actionbar.ui) that
raise the same warning not fail?
Anyway, those three tests pass with vulkan-disable (number of skipped
remains unaltered) as a matter of fact. I'm proposing that as a merge
request[2] in Debian's bug tracking system.
[1] https://l.termbin.com/a0e2
- [2]
+ [2] https://salsa.debian.org/gnome-team/gtk4/-/merge_requests/25
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2077313
Title:
GTK 4.15.5: memorytexture, dmabufformats and scaling tests fail
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk4/+bug/2077313/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2077313] [NEW] GTK 4.15.5: memorytexture, dmabufformats and scaling tests fail
Public bug reported:
These GTK 4.15.5 tests fail:
--->
gtk:gdk / memorytexture
ERROR0.33s killed by signal 5 SIGTRAP
gtk:gdk / dmabufformats
ERROR0.21s killed by signal 5 SIGTRAP
gtk:gsk / scaling
ERROR0.25s killed by signal 5 SIGTRAP
<---
as per
https://launchpad.net/~jbicha/+archive/ubuntu/arch/+sourcepub/16394764/+listing-
archive-extra.
The full log of memorytexture is [1]. Its backtrace is
--->
#0 0x77ecf5fa in g_log_writer_default () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1 0x77ec6d64 in g_log_structured_array () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2 0x77ec6fb8 in g_log_structured_standard () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3 0x778c0db7 in gdk_vulkan_handle_result
(res=, called_function=0x77a10955 "vkCreateInstance")
at ../../../gdk/gdkvulkancontextprivate.h:68
#4 gdk_vulkan_handle_result
(res=, called_function=0x77a10955 "vkCreateInstance")
at ../../../gdk/gdkvulkancontextprivate.h:63
#5 gdk_display_create_vulkan_instance (display=0x555a14f0,
error=)
at ../../../gdk/gdkvulkancontext.c:1675
#6 0x77961ef3 in gdk_display_init_vulkan (display=0x555a14f0,
error=0x0)
at ../../../gdk/gdkvulkancontext.c:1771
#7 gsk_vulkan_device_get_for_display (display=0x555a14f0, error=0x0)
at ../../../gsk/gpu/gskvulkandevice.c:421
#8 0x7794c717 in gsk_gpu_renderer_realize
(renderer=0x60defa00, display=0x555a14f0, surface=0x0, error=0x0)
at ../../../gsk/gpu/gskgpurenderer.c:213
#9 0x778d863b in gsk_renderer_do_realize
(renderer=0x60defa00, display=display@entry=0x555a14f0,
surface=surface@entry=0x0, error=error@entry=0x0) at
../../../gsk/gskrenderer.c:271
#10 0x778df4c5 in gsk_renderer_realize_for_display
(renderer=, display=display@entry=0x555a14f0,
error=error@entry=0x0)
at ../../../gsk/gskrenderer.c:357
#11 0x6a41 in main (argc=, argv=)
at ../../../testsuite/gdk/memorytexture.c:1587
<---
gdkvulkancontextprivate.h:68 at #3 is nothing but the warning:
g_warning ("%s(): %s (%d)", called_function, gdk_vulkan_strerror
(res), res);
So I must conclude the test is failing because the warning is being
called, as if G_DEBUG=fatal-warnings had been passed, which it is
however not. Open questions are:
1. Why is this causing a SIGTRAP if no fatal-warnings is enabled?
2. Why do other tests (e.g. 511 gtk:reftest / reftest actionbar.ui) that
raise the same warning not fail?
Anyway, those three tests pass with vulkan-disable (number of skipped
remains unaltered) as a matter of fact. I'm proposing that as a merge
request[2] in Debian's bug tracking system.
[1] https://l.termbin.com/a0e2
[2]
** Affects: gtk4 (Ubuntu)
Importance: Undecided
Assignee: Nathan Teodosio (nteodosio)
Status: In Progress
** Tags: ftbfs
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2077313
Title:
GTK 4.15.5: memorytexture, dmabufformats and scaling tests fail
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk4/+bug/2077313/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2070889] Re: Chromium opens, but still loads within 15 seconds after opening.
** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Chromium opens, but still loads within 15 seconds after opening. + Chromium opens, but cursor remains in "loading" state within 15 seconds after opening. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2070889 Title: Chromium opens, but cursor remains in "loading" state within 15 seconds after opening. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2070889/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2077272] Re: Difference in behavior in wayland and xorg sessions
Is anything in your report a regression, i.e., a new issue that was not there a few days ago? What is this large text setting and where is it used? In the web pages themselves or in Chromium's interface elements such as tab bar, configurations menu etc.? What is this 'top bar named New Tab - chromuim'? Can you send a picture? You list the 15 s bug first under Xorg but then say 'Chromium now launches directly into the Wayland session without any delay', can you clarify what is the session affected? What is the patch you talk about? Finally, please let us have one bug report for each separate issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2077272 Title: Difference in behavior in wayland and xorg sessions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2077272/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2077089] [NEW] apr-util fails to build due to bad m4 script
Public bug reported: Apr-util fails to build: https://launchpadlibrarian.net/743610341/buildlog_ubuntu-oracular- amd64.apr-util_1.6.3-2ubuntu1_BUILDING.txt.gz Attached a patch to fix it. Build with patch in PPA: https://launchpad.net/~nteodosio/+archive/ubuntu/rebuilds/+sourcepub/16399892/+listing- archive-extra ** Affects: apr-util (Ubuntu) Importance: Undecided Assignee: Nathan Teodosio (nteodosio) Status: Triaged ** Tags: ftbfs patch ** Patch added: "apr-util.diff" https://bugs.launchpad.net/bugs/2077089/+attachment/5806095/+files/apr-util.diff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2077089 Title: apr-util fails to build due to bad m4 script To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apr-util/+bug/2077089/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
