[Desktop-packages] [Bug 1308250] Re: chromium window creeps upward under unity bar
[Expired for chromium-browser (Ubuntu) because there has been no activity for 60 days.] ** Changed in: chromium-browser (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1308250 Title: chromium window creeps upward under unity bar Status in chromium-browser package in Ubuntu: Expired Bug description: In chromium 34, the window can be initially placed so the window bar is obscured by the top unity bar. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1308250/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1195338] Re: cr build ugliness: shlibdeps
[Expired for chromium-browser (Ubuntu) because there has been no activity for 60 days.] ** Changed in: chromium-browser (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1195338 Title: cr build ugliness: shlibdeps Status in chromium-browser package in Ubuntu: Expired Bug description: dh_shlibdeps -pchromium-browser dpkg-shlibdeps: warning: couldn't find library libbase.so needed by debian/chromium-browser/usr/lib/chromium-browser/libs/libffmpeg.so (ELF format: 'elf32-i386'; RPATH: '/usr/lib/chromium-browser/libs/libs') dpkg-shlibdeps: warning: couldn't find library libwebkit.so needed by debian/chromium-browser/usr/lib/chromium-browser/libs/libTestRunner.so (ELF format: 'elf32-i386'; RPATH: '/usr/lib/chromium-browser/libs/libs') dpkg-shlibdeps: warning: couldn't find library libskia.so needed by debian/chromium-browser/usr/lib/chromium-browser/libs/libsurface.so (ELF format: 'elf32-i386'; RPATH: '/usr/lib/chromium-browser/libs/libs') dpkg-shlibdeps: warning: couldn't find library libui.so needed by debian/chromium-browser/usr/lib/chromium-browser/libs/libsurface.so (ELF format: 'elf32-i386'; RPATH: '/usr/lib/chromium-browser/libs/libs') dpkg-shlibdeps: warning: couldn't find library libbase.so needed by debian/chromium-browser/usr/lib/chromium-browser/libs/libdbus.so (ELF format: 'elf32-i386'; RPATH: '/usr/lib/chromium-browser/libs/libs') dpkg-shlibdeps: warning: couldn't find library libprotobuf_lite.so needed by debian/chromium-browser/usr/lib/chromium-browser/libs/libdbus.so (ELF format: 'elf32-i386'; RPATH: '/usr/lib/chromium-browser/libs/libs') dpkg-shlibdeps: warning: couldn't find library libbase.so needed by debian/chromium-browser/usr/lib/chromium-browser/libs/libsync.so (ELF format: 'elf32-i386'; RPATH: '/usr/lib/chromium-browser/libs/libs') dpkg-shlibdeps: warning: couldn't find library libbase_i18n.so needed by debian/chromium-browser/usr/lib/chromium-browser/libs/libsync.so (ELF format: 'elf32-i386'; RPATH: '/usr/lib/chromium-browser/libs/libs') dpkg-shlibdeps: warning: couldn't find library libgoogleurl.so needed by debian/chromium-browser/usr/lib/chromium-browser/libs/libsync.so (ELF format: 'elf32-i386'; RPATH: '/usr/lib/chromium-browser/libs/libs') dpkg-shlibdeps: warning: couldn't find library libcrcrypto.so needed by debian/chromium-browser/usr/lib/chromium-browser/libs/libsync.so (ELF format: 'elf32-i386'; RPATH: '/usr/lib/chromium-browser/libs/libs') dpkg-shlibdeps: warning: couldn't find library libnet.so needed by debian/chromium-browser/usr/lib/chromium-browser/libs/libsync.so (ELF format: 'elf32-i386'; RPATH: '/usr/lib/chromium-browser/libs/libs') dpkg-shlibdeps: warning: couldn't find library libsql.so needed by debian/chromium-browser/usr/lib/chromium-browser/libs/libsync.so (ELF format: 'elf32-i386'; RPATH: '/usr/lib/chromium-browser/libs/libs') dpkg-shlibdeps: warning: couldn't find library libprotobuf_lite.so needed by debian/chromium-browser/usr/lib/chromium-browser/libs/libsync.so (ELF format: 'elf32-i386'; RPATH: '/usr/lib/chromium-browser/libs/libs') dpkg-shlibdeps: warning: couldn't find library libcrssl.so needed by debian/chromium-browser/usr/lib/chromium-browser/libs/libsync.so (ELF format: 'elf32-i386'; RPATH: '/usr/lib/chromium-browser/libs/libs') dpkg-shlibdeps: warning: couldn't find library libbase.so needed by debian/chromium-browser/usr/lib/chromium-browser/libs/libwebkit_base.so (ELF format: 'elf32-i386'; RPATH: '/usr/lib/chromium-browser/libs/libs') dpkg-shlibdeps: warning: couldn't find library libgoogleurl.so needed by debian/chromium-browser/usr/lib/chromium-browser/libs/libwebkit_base.so (ELF format: 'elf32-i386'; RPATH: '/usr/lib/chromium-browser/libs/libs') dpkg-shlibdeps: warning: couldn't find library libwebkit.so needed by debian/chromium-browser/usr/lib/chromium-browser/libs/libwebkit_base.so (ELF format: 'elf32-i386'; RPATH: '/usr/lib/chromium-browser/libs/libs') dpkg-shlibdeps: warning: couldn't find library libbase_i18n.so needed by debian/chromium-browser/usr/lib/chromium-browser/libs/libglue.so (ELF format: 'elf32-i386'; RPATH: '/usr/lib/chromium-browser/libs/libs') dpkg-shlibdeps: warning: couldn't find library libgoogleurl.so needed by debian/chromium-browser/usr/lib/chromium-browser/libs/libglue.so (ELF format: 'elf32-i386'; RPATH: '/usr/lib/chromium-browser/libs/libs') dpkg-shlibdeps: warning: couldn't find library libmedia.so needed by debian/chromium-browser/usr/lib/chromium-browser/libs/libglue.so (ELF format: 'elf32-i386'; RPATH: '/usr/lib/chromium-browser/libs/libs') dpkg-shlibdeps: warning: couldn't find library libgoogleurl.so needed by debian/chromium-browser/usr/lib/chromium-browser/libs/libnet.so (ELF format: 'elf32-i386'; RPATH: '/usr/lib/chromium-browser/libs/libs')
[Desktop-packages] [Bug 1309781] Re: Chromium browser does not respect defined input method
[Expired for chromium-browser (Ubuntu) because there has been no activity for 60 days.] ** Changed in: chromium-browser (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1309781 Title: Chromium browser does not respect defined input method Status in chromium-browser package in Ubuntu: Expired Bug description: = Steps to reproduce 1. Use “im-config” to select “xim” as input method. It will change your “~/.xinputrc” file to define “xim” as selected method. = Expected behavior === 1. You should be able to use your “~/.XCompose” sequences in any program inside Ubuntu. = Current behavior == 1. Your “XCompose” sequences won't work anywhere inside the Chromium window, and any input in Chromium will behave sometimes as the standard input (“ibus”, if I recall correctly), other times it will ignore dead keys completely (apostrophe, quotes and grave have no effect). 1.1. I say “sometimes” because I couldn't figure out what makes/when it behave in any of the two ways. But both are wrong anyway, so it does not really matter. Other programs I've tried so far (gedit, firefox and others) work correctly all the time, i.e., I can normally use my XCompose escape sequencies as expected. = Rationale === As of now, I need “XCompose” sequences in order to type special characters and diacritics easily and correctly, for portuguese. As it happens, the standard input does not provide an easy way to type c-cedilla (ç), as the input sequence (apostrophe-c) ends with a c-acute (ć) instead. Therefore, I'd like Chromium to behave as the other programs do, i.e., using “xim” as the input method. = lsb_release -rd = Description: Ubuntu 14.04 LTS Release: 14.04 = apt-cache policy pkgname == chromium-browser: Installed: 34.0.1847.116-0ubuntu2 Candidate: 34.0.1847.116-0ubuntu2 Version table: *** 34.0.1847.116-0ubuntu2 0 500 http://br.archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: chromium-browser 34.0.1847.116-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Fri Apr 18 18:54:32 2014 Desktop-Session: DESKTOP_SESSION = ubuntu XDG_CONFIG_DIRS = /etc/xdg/xdg-ubuntu:/usr/share/upstart/xdg:/etc/xdg XDG_DATA_DIRS = /usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/ DetectedPlugins: Env: MOZ_PLUGIN_PATH = None LD_LIBRARY_PATH = None InstallationDate: Installed on 2014-04-18 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) chromium-default: CHROMIUM_FLAGS="" gconf-keys: /desktop/gnome/applications/browser/exec = b'/usr/bin/chromium-browser\n'/desktop/gnome/url-handlers/https/command = b'/usr/bin/chromium-browser %s\n'/desktop/gnome/url-handlers/https/enabled = b'true\n'/desktop/gnome/url-handlers/http/command = b'/usr/bin/chromium-browser %s\n'/desktop/gnome/url-handlers/http/enabled = b'true\n'/desktop/gnome/session/required_components/windowmanager = b''/apps/metacity/general/compositing_manager = b''/desktop/gnome/interface/icon_theme = b'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n' modified.conffile..etc.default.chromium.browser: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1309781/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1933027] Re: Gdm3 with smartcard asks for login/smartcard pin even if there is no smartcard authentication enabled
Update: a workaround to recover the "gdm user chooser" is to avoid the smartcard support from launching, which can be done editing this file /etc/xdg/autostart/org.gnome.SettingsDaemon.Smartcard.desktop comment out the existing "Exec" line, and add a new one pointing to this harmless do-nothing binary, /usr/bin/true The chooser now works. Still wondering how is it that 22.04 was working with no problem with my yubikey always plugged since June till November -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1933027 Title: Gdm3 with smartcard asks for login/smartcard pin even if there is no smartcard authentication enabled Status in gdm3 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Fix Released Bug description: I use my Ubuntu PC with Yubikey almost always plugged in. It provides several security token interfaces, such as U2F, GPG smartcard, proprieritary Yubico interfaces (of which I mostly use TOTP codes), and also PIV smartcard. However, I haven't configured a PIV smartcard on it. Whenever I login into the system having Yubikey plugged in, I'm prompted for login name, and then for PIN for some smartcard while also being asked to plug in one. This is very misleading on several layers: 1. I have the device providing smartcard plugged id, 2. But it's not the smartcard GDM would think it is as it's not configured properly, 3. There are no local smartcard-authenticating users right now in the system, 3. There are no remote authentication systems configured on the system (so no ActiveDirectory-smartcard logins or such). If I unplug the token UX goes back on old good track. Given the circumstances above, I'd consider that GDM (and, on my bet, any PAM configuration it uses) shouldn't offer to login using smartcard if there is no way to actually do so. I feel something is off here, so I'm reporting a bug. It could be an upstream problem though; it also could be an upstream SSSD problem, or all combined. I believe there is a more clear user experience: 1. GDM should display users that can login into the system, as it always does (if configured). It may also provide entering other login name (also if configured). This is GDM usually does without smartcards altogether. 2. When user is chosen (from the list or manually typed in), check can this user even authenticate with smartcards (i.e. if any of available smartcards is actually recognised for this user). If so, then ask for PIN. Else, don't show anything about smartcards at all (this includes when SSSD is not configured for any AD or related and this user has no local smartcard configuration). This can switch there & back based on device events. I've seen other OS doing this. Ubuntu/Gnome session doesn't ask me for PIN for a smartcard on a lock screen, so I guess it doesn't support it at all or correctly finds out it can't be used. Even more, I couldn't find a way to actually add my smartcard as a local login method. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gdm3 3.38.2.1-2ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Jun 20 14:02:02 2021 InstallationDate: Installed on 2017-03-05 (1567 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcEnviron: TERM=tmux-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: Upgraded to hirsute on 2021-05-13 (37 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1933027/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1933027] Re: Gdm3 with smartcard asks for login/smartcard pin even if there is no smartcard authentication enabled
-- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1933027 Title: Gdm3 with smartcard asks for login/smartcard pin even if there is no smartcard authentication enabled Status in gdm3 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Fix Released Bug description: I use my Ubuntu PC with Yubikey almost always plugged in. It provides several security token interfaces, such as U2F, GPG smartcard, proprieritary Yubico interfaces (of which I mostly use TOTP codes), and also PIV smartcard. However, I haven't configured a PIV smartcard on it. Whenever I login into the system having Yubikey plugged in, I'm prompted for login name, and then for PIN for some smartcard while also being asked to plug in one. This is very misleading on several layers: 1. I have the device providing smartcard plugged id, 2. But it's not the smartcard GDM would think it is as it's not configured properly, 3. There are no local smartcard-authenticating users right now in the system, 3. There are no remote authentication systems configured on the system (so no ActiveDirectory-smartcard logins or such). If I unplug the token UX goes back on old good track. Given the circumstances above, I'd consider that GDM (and, on my bet, any PAM configuration it uses) shouldn't offer to login using smartcard if there is no way to actually do so. I feel something is off here, so I'm reporting a bug. It could be an upstream problem though; it also could be an upstream SSSD problem, or all combined. I believe there is a more clear user experience: 1. GDM should display users that can login into the system, as it always does (if configured). It may also provide entering other login name (also if configured). This is GDM usually does without smartcards altogether. 2. When user is chosen (from the list or manually typed in), check can this user even authenticate with smartcards (i.e. if any of available smartcards is actually recognised for this user). If so, then ask for PIN. Else, don't show anything about smartcards at all (this includes when SSSD is not configured for any AD or related and this user has no local smartcard configuration). This can switch there & back based on device events. I've seen other OS doing this. Ubuntu/Gnome session doesn't ask me for PIN for a smartcard on a lock screen, so I guess it doesn't support it at all or correctly finds out it can't be used. Even more, I couldn't find a way to actually add my smartcard as a local login method. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gdm3 3.38.2.1-2ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Jun 20 14:02:02 2021 InstallationDate: Installed on 2017-03-05 (1567 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcEnviron: TERM=tmux-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: Upgraded to hirsute on 2021-05-13 (37 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1933027/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1933027] Re: Gdm3 with smartcard asks for login/smartcard pin even if there is no smartcard authentication enabled
I've been using 22.04 (fresh install) since June and today after a routine update this "bug" popped up. This is in a system that has a yubikey 4 permanently plugged in. It's weird that the bug just popped out of nowhere. The last workaround from wastrel worked great for me. Now in addition to this bug, GDM's "face chooser" disappeared, no longer shows up, on boot I get prompted for a username. 22.04 was supposed to be a stable long-term release :/ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1933027 Title: Gdm3 with smartcard asks for login/smartcard pin even if there is no smartcard authentication enabled Status in gdm3 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Fix Released Bug description: I use my Ubuntu PC with Yubikey almost always plugged in. It provides several security token interfaces, such as U2F, GPG smartcard, proprieritary Yubico interfaces (of which I mostly use TOTP codes), and also PIV smartcard. However, I haven't configured a PIV smartcard on it. Whenever I login into the system having Yubikey plugged in, I'm prompted for login name, and then for PIN for some smartcard while also being asked to plug in one. This is very misleading on several layers: 1. I have the device providing smartcard plugged id, 2. But it's not the smartcard GDM would think it is as it's not configured properly, 3. There are no local smartcard-authenticating users right now in the system, 3. There are no remote authentication systems configured on the system (so no ActiveDirectory-smartcard logins or such). If I unplug the token UX goes back on old good track. Given the circumstances above, I'd consider that GDM (and, on my bet, any PAM configuration it uses) shouldn't offer to login using smartcard if there is no way to actually do so. I feel something is off here, so I'm reporting a bug. It could be an upstream problem though; it also could be an upstream SSSD problem, or all combined. I believe there is a more clear user experience: 1. GDM should display users that can login into the system, as it always does (if configured). It may also provide entering other login name (also if configured). This is GDM usually does without smartcards altogether. 2. When user is chosen (from the list or manually typed in), check can this user even authenticate with smartcards (i.e. if any of available smartcards is actually recognised for this user). If so, then ask for PIN. Else, don't show anything about smartcards at all (this includes when SSSD is not configured for any AD or related and this user has no local smartcard configuration). This can switch there & back based on device events. I've seen other OS doing this. Ubuntu/Gnome session doesn't ask me for PIN for a smartcard on a lock screen, so I guess it doesn't support it at all or correctly finds out it can't be used. Even more, I couldn't find a way to actually add my smartcard as a local login method. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gdm3 3.38.2.1-2ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Jun 20 14:02:02 2021 InstallationDate: Installed on 2017-03-05 (1567 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcEnviron: TERM=tmux-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: Upgraded to hirsute on 2021-05-13 (37 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1933027/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1986979] Re: Ubuntu 22.04 English input language duplicates twice when switching input language
*** This bug is a duplicate of bug 1956916 *** https://bugs.launchpad.net/bugs/1956916 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-control-center (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1986979 Title: Ubuntu 22.04 English input language duplicates twice when switching input language Status in gnome-control-center package in Ubuntu: Confirmed Bug description: I have only two input languages and I used Gnome Tweak tools to make alt+shift switching input languages. But when I cycle through them - I get English language selected twice. I did many tests and it can not be a coincidence or misclick. Pattern repeats many times. `asdas dasdas фвівфі adsasd dsasda Фівфів adsdas Adsasdas Фівфівф sdasad dasdas вфівфі asdasd Adsasdas вфівфі' See? I typed it just one time, it is impossible that I failed to switch to English 5 times in a row. There is got to be some bug or what? Did anybody encounter this? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1986979/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1995416] Re: lmdb is out of date - please update to 0.9.29
hmm ... looking at that site lmdb 0.9.24 seems to be in stable . I guest that is as good as it gets. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lmdb in Ubuntu. https://bugs.launchpad.net/bugs/1995416 Title: lmdb is out of date - please update to 0.9.29 Status in lmdb package in Ubuntu: New Status in lmdb package in Debian: Unknown Bug description: Subject says it all. Is it possible to report out-of-date packages in another way that a bugreport ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lmdb/+bug/1995416/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1993127] Re: /usr/bin/nautilus:11:g_list_store_find_with_equal_func_full:g_list_store_find_with_equal_func:g_list_store_find:nautilus_view_model_get_index:scroll_to_file_on_idl
Has new version with the released fix applied already been published? My nautilus version is current on Ubuntu 22.10, it is on 1:43.0-1ubuntu1. This bug still affects me and it can be reproduced easily in at least two ways: - Have a Nautilus window open, then right-click the launcher and click a bookmarked folder there -> nautilus crashes immediately (see also https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1934579) - In a Nautilus window, type some letters to start a search, then open one of the result folders and then go back either using the button in the title bar or using the "back" button of the mouse -> the previous location is displayed briefly and then nautilus crashes. None of the workarounds found on the web helps (removing `~/.cache/tracker3` or using an Xorg session instead of Wayland). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1993127 Title: /usr/bin/nautilus:11:g_list_store_find_with_equal_func_full:g_list_store_find_with_equal_func:g_list_store_find:nautilus_view_model_get_index:scroll_to_file_on_idle Status in Nautilus: Fix Released Status in nautilus package in Ubuntu: Triaged Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding nautilus. This problem was most recently seen with package version 1:43.0-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/32454f0bde038596049406d7ad99e47263fb8bf7 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1993127/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1993874] Re: Settings and Quick Menu apply Dark style differently
Does canonical have any plan to fix this? A lot of reports about this anoing bug and no answer from canonical. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1993874 Title: Settings and Quick Menu apply Dark style differently Status in gnome-control-center package in Ubuntu: Confirmed Bug description: I just upgraded to Ubuntu 22.10 and noticed that some of my apps were no longer in Dark mode including gedit/chrome. When setting the style through the quick menu however, these apps go to Dark mode (presumably due to gtk theme being applied). Likewise for the quick menu itself, setting the style to Dark in gnome-control-settings doesn't change it to dark, it remains light. see screenshot attached, you will see that when setting the style to Dark in Settings, gedit and the quick menu remain light. I tried to logout in case it was an issue with how the settings are applied but it didn't help. it's also clear that the toggle in the quick menu works as intended so there seems to be an issue with the way gnome- control-center applies the Dark style. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-control-center 1:43.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Oct 22 10:21:40 2022 InstallationDate: Installed on 2022-04-06 (198 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to kinetic on 2022-10-21 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1993874/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1741074] Re: [snap] chrome-gnome-shell extension fails to detect native host connector
Plasma Browser integration now kind of works with: firefox 106.0.5-1 2067 latest/stable/… mozilla✓ xdg-desktop-portal 1.14.4-1ubuntu2~22.04.1 but I had to manually set permission - following directions for KeePassXC integration. Steps: sudo apt-get install flatpak flatpak permission-set webextensions org.kde.plasma.browser_integration snap.firefox yes restart firefox @lucas+- The onus is now on the user/sysadmin as well, because of the annoying update notifications of the firefox snap and the blocking of "snap refresh firefox" by a running firefox (why do I have to do this manually). If this would be fixed, the firefox snap will finally be worthy of inclusion into a LTS version! IMHO, this process is what interim releases are for and I just don't get, why Canonical and Mozilla decided that they want to torture LTS users with this UX. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1741074 Title: [snap] chrome-gnome-shell extension fails to detect native host connector Status in Mozilla Firefox: In Progress Status in KeePassXC Snap Builds: Unknown Status in chromium-browser package in Ubuntu: Triaged Status in firefox package in Ubuntu: In Progress Status in goopg package in Ubuntu: Confirmed Status in kdeconnect package in Ubuntu: Confirmed Status in plasma-browser-integration package in Ubuntu: Confirmed Bug description: (initially reported at https://forum.snapcraft.io/t/chrome-gnome- shell-does-not-work-with-chromium-snap/3377) See attached screenshot. [Workaround] If you're using Ubuntu 22.04 LTS, you can install GNOME Shell extensions with this app. sudo apt install gnome-shell-extension-manager To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1741074/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1884299] Re: Snaps don't run with NFS home on AutoFS
I ran into a similar issue when trying to use sshfs-mounted profile for firefox. My setup: $ mkdir .remote $ sshfs .remote -o idmap=user $ ln -s .remote/snap So now /home/ubuntu/snap is a symlink to a directory /home/ubuntu/.remote/snap. When trying to run firefox, it fails with: $ firefox cannot create user data directory: /home/ubuntu/snap/firefox/1232: Not a directory Which is confusing, as /home/ubuntu/snap/firefox/1232 is a directory. Trying to strace what's going on (details in https://pastebin.com/gbeHV8L1) I found out that firefox (or snap) is confused that snap is a symlink to directory, not a directory by itself (and this limitation doesn't makes sense to me, looks like just implementation flaw of creating user directory). Not sure if this is related to the above, but experience is similar. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1884299 Title: Snaps don't run with NFS home on AutoFS Status in firefox package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Confirmed Bug description: My physical computer lab uses AutoFS home drives (per https://help.ubuntu.com/community/Autofs#Wildcard_characters). If any user tries to run chromium browser, it fails. I assume it is related to these: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1662552 But that says a fix was released, but seems toi only work for NFS home drives https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1782873 That ones is reported as a dupe but it's not, AutoFS home drives still don't work. $ chromium -v cannot create user data directory: /home/test.student2/snap/chromium/1193: Stale file handle $ tail -f /var/log/syslog Jun 19 11:21:09 tbl-h10-4 kernel: [18949.188657] nfs: RPC call returned error 13 Jun 19 11:21:09 tbl-h10-4 kernel: [18949.188666] nfs: RPC call returned error 13 Jun 19 11:21:09 tbl-h10-4 kernel: [18949.188695] audit: type=1400 audit(1592590869.460:59): apparmor="DENIED" operation="sendmsg" profile="/snap/snapd/8140/usr/lib/snapd/snap-confine" pid=12884 comm="snap-confine" laddr=192.168.43.216 lport=766 faddr=192.168.43.4 fport=2049 family="inet" sock_type="stream" protocol=6 requested_mask="send" denied_mask="send" Jun 19 11:21:09 tbl-h10-4 kernel: [18949.188697] audit: type=1400 audit(1592590869.460:60): apparmor="DENIED" operation="sendmsg" profile="/snap/snapd/8140/usr/lib/snapd/snap-confine" pid=12884 comm="snap-confine" laddr=192.168.43.216 lport=766 faddr=192.168.43.4 fport=2049 family="inet" sock_type="stream" protocol=6 requested_mask="send" denied_mask="send" $ lsb_release -rd Description: Ubuntu 20.04 LTS $ apt policy chromium-browser chromium-browser: Installed: 81.0.4044.129-0ubuntu0.20.04.1 Candidate: 81.0.4044.129-0ubuntu0.20.04.1 Version table: *** 81.0.4044.129-0ubuntu0.20.04.1 500 500 http://ca.archive.ubuntu.com/ubuntu focal-updates/universe amd64 Packages 100 /var/lib/dpkg/status 80.0.3987.163-0ubuntu1 500 500 http://ca.archive.ubuntu.com/ubuntu focal/universe amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1884299/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1985066] Re: cannot refresh snap "firefox": snap "firefox" has running apps (firefox)
This is a very bad user experience and besides the very annoying notifications that firefox need to be closed because of an update and if I follow this, then nothing happens and I get the same message after starting it again, I'm finished with giving this distribution method (snap) a fair try. ** Changed in: firefox (Ubuntu) Status: Invalid => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1985066 Title: cannot refresh snap "firefox": snap "firefox" has running apps (firefox) Status in firefox package in Ubuntu: Confirmed Bug description: Firefox installed via 22.04 snap does not seem to update properly. There is a log line (or error printout on manual execution), but it does not really point me to the actual bug. I already know firefox is running for some other user - that machine is never up and not running firefox - but I do not see how that matters. # snap list firefox Name VersionRev Tracking Publisher Notes firefox 103.0.1-1 1635 latest/stable mozilla✓ - # snap info firefox | grep latest/stable tracking: latest/stable latest/stable:103.0.2-12022-08-09 (1670) 171MB - # sudo snap refresh firefox error: cannot refresh "firefox": snap "firefox" has running apps (firefox), pids: 19113,19246,19268,19361,19524,19529,19588,19874,20047,20075,20105,20127 # firefox --version Mozilla Firefox 103.0.1 (expected: 103.0.2) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1985066/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1995416] Re: lmdb is out of date - please update to 0.9.29
> Is it possible to report out-of-date packages in another way that a bugreport ? Not that I know of. You can try to contact the Debian maintainer (or file a bug report there) https://tracker.debian.org/pkg/lmdb for packages which are synced unchanged. I did find there's a corresponding Debian bug report, and seems like there's been some work on packaging the newer version, see the attached bug watch for details. ** Bug watch added: Debian Bug tracker #952904 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952904 ** Also affects: lmdb (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952904 Importance: Unknown Status: Unknown ** Tags added: upgrade-software-version -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lmdb in Ubuntu. https://bugs.launchpad.net/bugs/1995416 Title: lmdb is out of date - please update to 0.9.29 Status in lmdb package in Ubuntu: New Status in lmdb package in Debian: Unknown Bug description: Subject says it all. Is it possible to report out-of-date packages in another way that a bugreport ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lmdb/+bug/1995416/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
