[Bug 1971559] Re: After Ugrade, Jammy requires me to create a new user, although users are present
Ah, that's what I was looking for, thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971559 Title: After Ugrade, Jammy requires me to create a new user, although users are present To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-initial-setup/+bug/1971559/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971559] Re: After Ugrade, Jammy requires me to create a new user, although users are present
> Non system accounts flagged as systemuser should perhaps could as an existing user in that logic even if they aren't explicitly displayed? I'd expect that to depend very much on the installation at hand (in our case it would), but that can't be decided programmatically. I'd opt for a way of skipping the initial-install wizard for advanced users. Possibly hidden below an "advanced setup” option and with a warning about being left without any usable account. But there should be a way of skipping it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971559 Title: After Ugrade, Jammy requires me to create a new user, although users are present To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-initial-setup/+bug/1971559/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971559] Re: After Ugrade, Jammy requires me to create a new user, although users are present
Sebastien, thanks for your reply. First of all, considering that this is a somewhat special (though not unlikely) setup on our side, you may demote this bug from importance high to lower. This is to remove strain on you developers, this bug will only concern special institutional setups like ours and never will concern private users. Take a break ;-). The problem did not appear upon update to 20.04. Was there a comparable "initial-setup" dialog in 20.04? This is a multi-user installation at a school. I flagged the linadmin user (and other local users we utilize for managing our services) as being system users manually. I did that to not have them displayed in gdm's user list at tje login page. There may be more appropriate ways of doing this, if you know of them (lest disabling the user list altogether), let me know, please. At the tome being, I can workaround the issue by creating some local dummy user nit tagged as system. My suggestion is to have included into the initial-install wizard an option to skip the dialog if root is sure about it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971559 Title: After Ugrade, Jammy requires me to create a new user, although users are present To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-initial-setup/+bug/1971559/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971559] Re: After Ugrade, Jammy requires me to create a new user, although users are present
Behaviour in 20.04 was like it is in 22.04: Once I went through the dialog and created one no-system user, the login screen shows all accounts not listed as "system". I.e. all of our LDAP users (which are the only ones relevant to our users). I manually marked those accounts as system, to have them excluded from the login list. The link you posted is about disabling the user list altogether, which is not what we we want. We want to have the user list but have it show only standard, no-special users. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971559 Title: After Ugrade, Jammy requires me to create a new user, although users are present To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-initial-setup/+bug/1971559/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971559] Re: After Ugrade, Jammy requires me to create a new user, although users are present
Indeed, all local accounts are marked as system accounts, because they all serve administrative uses in one way or the other, and shall not be seen by normal users. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971559 Title: After Ugrade, Jammy requires me to create a new user, although users are present To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-initial-setup/+bug/1971559/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971559] Re: After Ugrade, Jammy requires me to create a new user, although users are present
root@rechner2-3-12:~# /usr/libexec/accounts-daemon --debug (accounts-daemon:9005): DEBUG: entering main loop (accounts-daemon:9005): DEBUG: Changing permission of /var/lib/AccountsService/users/vorlage to 0600 (accounts-daemon:9005): DEBUG: Changing permission of /var/lib/AccountsService/users/windows to 0600 (accounts-daemon:9005): DEBUG: Changing permission of /var/lib/AccountsService/users/linadmin to 0600 (accounts-daemon:9005): DEBUG: Changing permission of /var/lib/AccountsService/users/gnome-initial-setup to 0600 (accounts-daemon:9005): DEBUG: Changing permission of /var/lib/AccountsService/users/gdm to 0600 (accounts-daemon:9005): DEBUG: skipping user: root (accounts-daemon:9005): DEBUG: skipping user: daemon (accounts-daemon:9005): DEBUG: skipping user: bin (accounts-daemon:9005): DEBUG: skipping user: sys (accounts-daemon:9005): DEBUG: skipping user: sync (accounts-daemon:9005): DEBUG: skipping user: games (accounts-daemon:9005): DEBUG: skipping user: man (accounts-daemon:9005): DEBUG: skipping user: lp (accounts-daemon:9005): DEBUG: skipping user: mail (accounts-daemon:9005): DEBUG: skipping user: news (accounts-daemon:9005): DEBUG: skipping user: uucp (accounts-daemon:9005): DEBUG: skipping user: proxy (accounts-daemon:9005): DEBUG: skipping user: www-data (accounts-daemon:9005): DEBUG: skipping user: backup (accounts-daemon:9005): DEBUG: skipping user: list (accounts-daemon:9005): DEBUG: skipping user: irc (accounts-daemon:9005): DEBUG: skipping user: gnats (accounts-daemon:9005): DEBUG: skipping user: nobody (accounts-daemon:9005): DEBUG: skipping user: systemd-timesync (accounts-daemon:9005): DEBUG: skipping user: systemd-network (accounts-daemon:9005): DEBUG: skipping user: systemd-resolve (accounts-daemon:9005): DEBUG: skipping user: syslog (accounts-daemon:9005): DEBUG: skipping user: _apt (accounts-daemon:9005): DEBUG: skipping user: messagebus (accounts-daemon:9005): DEBUG: skipping user: uuidd (accounts-daemon:9005): DEBUG: skipping user: lightdm (accounts-daemon:9005): DEBUG: skipping user: whoopsie (accounts-daemon:9005): DEBUG: skipping user: avahi-autoipd (accounts-daemon:9005): DEBUG: skipping user: colord (accounts-daemon:9005): DEBUG: skipping user: speech-dispatcher (accounts-daemon:9005): DEBUG: skipping user: hplip (accounts-daemon:9005): DEBUG: skipping user: kernoops (accounts-daemon:9005): DEBUG: skipping user: pulse (accounts-daemon:9005): DEBUG: skipping user: rtkit (accounts-daemon:9005): DEBUG: skipping user: saned (accounts-daemon:9005): DEBUG: skipping user: usbmux (accounts-daemon:9005): DEBUG: loaded user: linadmin (accounts-daemon:9005): DEBUG: skipping user: sshd (accounts-daemon:9005): DEBUG: skipping user: ntp (accounts-daemon:9005): DEBUG: skipping user: geoclue (accounts-daemon:9005): DEBUG: skipping user: nm-openvpn (accounts-daemon:9005): DEBUG: skipping user: postfix (accounts-daemon:9005): DEBUG: skipping user: guest-3qs2su (accounts-daemon:9005): DEBUG: loaded user: windows (accounts-daemon:9005): DEBUG: loaded user: vorlage (accounts-daemon:9005): DEBUG: skipping user: statd (accounts-daemon:9005): DEBUG: skipping user: cups-pk-helper (accounts-daemon:9005): DEBUG: skipping user: gdm (accounts-daemon:9005): DEBUG: skipping user: gnome-initial-setup (accounts-daemon:9005): DEBUG: skipping user: tss (accounts-daemon:9005): DEBUG: skipping user: tcpdump (accounts-daemon:9005): DEBUG: skipping user: _rpc (accounts-daemon:9005): DEBUG: skipping user: avahi (accounts-daemon:9005): DEBUG: skipping user: systemd-coredump (accounts-daemon:9005): DEBUG: skipping user: motion (accounts-daemon:9005): DEBUG: loaded user: gnome-initial-setup (accounts-daemon:9005): DEBUG: loaded user: gdm (accounts-daemon:9005): DEBUG: failed to load gdms custom.conf: Die Schlüsselwertedatei hat keinen Schlüssel »AutomaticLoginEnable« in der Gruppe »daemon« (accounts-daemon:9005): DEBUG: got NameLost, exiting (accounts-daemon:9005): DEBUG: exiting Key "AutomaticLoginEnable" is commented out in /etc/gdm3/custom.conf. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971559 Title: After Ugrade, Jammy requires me to create a new user, although users are present To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-initial-setup/+bug/1971559/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971559] Re: After Ugrade, Jammy requires me to create a new user, although users are present
root@rechner2-3-12:~# cat /var/lib/AccountsService/users/linadmin # do not show user in greeter [User] SystemAccount=true Ah! This could be it! lindamin is marked as SystemAccount, because our users shall not see it in the list of accounts on the login screen … -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971559 Title: After Ugrade, Jammy requires me to create a new user, although users are present To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-initial-setup/+bug/1971559/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971559] Re: After Ugrade, Jammy requires me to create a new user, although users are present
Don't know if this helps: root@rechner2-3-12:~# ps -ef|grep initial gnome-i+20441829 0 08:20 tty1 00:00:00 /usr/libexec/gdm-x-session dbus-run-session -- gnome-session --autostart /usr/share/gdm/greeter/autostart --session gnome-initial-setup gnome-i+20812044 0 08:20 tty1 00:00:00 dbus-run-session -- gnome-session --autostart /usr/share/gdm/greeter/autostart --session gnome-initial-setup gnome-i+20832081 0 08:20 tty1 00:00:00 /usr/libexec/gnome-session-binary --autostart /usr/share/gdm/greeter/autostart --session gnome-initial-setup gnome-i+23662083 0 08:20 tty1 00:00:14 /usr/libexec/gnome-initial-setup root85898365 0 15:31 pts/000:00:00 grep initial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971559 Title: After Ugrade, Jammy requires me to create a new user, although users are present To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-initial-setup/+bug/1971559/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971559] Re: After Ugrade, Jammy requires me to create a new user, although users are present
linadmin is definitely a user with ultimate sudo rights: root@rechner2-3-12:~# sudo -U linadmin --list Passende Defaults-Einträge für linadmin auf rechner2-3-12: env_reset, mail_badpass, secure_path=/usr/local/sbin\:/usr/local/bin\:/usr/sbin\:/usr/bin\:/sbin\:/bin\:/snap/bin Der Benutzer linadmin darf die folgenden Befehle auf rechner2-3-12 ausführen: (ALL : ALL) ALL -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971559 Title: After Ugrade, Jammy requires me to create a new user, although users are present To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-initial-setup/+bug/1971559/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971559] Re: After Ugrade, Jammy requires me to create a new user, although users are present
Yes, system is still in this state. I went through the dialog once and created a user. After that the machine booted into th login screen and worked. Then I removed the new user with "deluser" and at next boot I was back at the dialog. So, yes, it appears the code does not detect that there are other users. dbus-send --system --type=method_call --print-reply --dest=org.freedesktop.Accounts /org/freedesktop/Accounts org.freedesktop.Accounts.ListCachedUsers method return time=1651757139.332087 sender=:1.8 -> destination=:1.153 serial=94 reply_serial=2 array [ ] I'm logged in remotely via ssh. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971559 Title: After Ugrade, Jammy requires me to create a new user, although users are present To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-initial-setup/+bug/1971559/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971559] Re: After Ugrade, Jammy requires me to create a new user, although users are present
/bin/bash is availble, I can su to linadmin and even connect as linadmin by ssh. Journal is attached. ** Attachment added: "journal" https://bugs.launchpad.net/ubuntu/+source/gnome-initial-setup/+bug/1971559/+attachment/5587019/+files/journal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971559 Title: After Ugrade, Jammy requires me to create a new user, although users are present To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-initial-setup/+bug/1971559/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971559] Re: After Ugrade, Jammy requires me to create a new user, although users are present
root@rechner2-3-12:~# grep linadmin /etc/passwd linadmin:x:1000:1000:Linux-Administrator,,,:/home/linadmin:/bin/bash /home/linadmin is a local directory and linadmin is a locally configured user, no LDAP account. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971559 Title: After Ugrade, Jammy requires me to create a new user, although users are present To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-initial-setup/+bug/1971559/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971559] Re: After Ugrade, Jammy requires me to create a new user, although users are present
The local user with sudo rights has uid 1000: root@rechner2-3-12:~# id linadmin uid=1000(linadmin) gid=1000(linadmin) Gruppen=4(adm),24(cdrom),27(sudo),30(dip),46(plugdev),113(lpadmin),128(sambashare),1000(linadmin) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971559 Title: After Ugrade, Jammy requires me to create a new user, although users are present To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-initial-setup/+bug/1971559/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971559] Re: After Ugrade, Jammy requires me to create a new user, although users are present
** Attachment added: "image20220505_082109516.jpg" https://bugs.launchpad.net/ubuntu/+source/gnome-initial-setup/+bug/1971559/+attachment/5586888/+files/image20220505_082109516.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971559 Title: After Ugrade, Jammy requires me to create a new user, although users are present To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-initial-setup/+bug/1971559/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971559] Re: After Ugrade, Jammy requires me to create a new user, although users are present
That's the dialog. ** Attachment added: "image20220505_082026251.jpg" https://bugs.launchpad.net/ubuntu/+source/gnome-initial-setup/+bug/1971559/+attachment/5586887/+files/image20220505_082026251.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971559 Title: After Ugrade, Jammy requires me to create a new user, although users are present To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-initial-setup/+bug/1971559/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971559] Re: After Ugrade, Jammy requires me to create a new user, although users are present
Sorry, I'm far from that machine at the moment, but I'll try describing: - Desktop environment: GNOME (standard Ubuntu Desktop) - I don't see the login screen, Ubuntu boots through to the desktop and shows the dialog. - dialog fills almost the whole desktop and nothing can be done except finishing that dialog. - it says (from my mind): only a few steps are required to finish setip, this wizard will help you create an account. Then ist prompts for a new user name, login id, locale, time zone, etc. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971559 Title: After Ugrade, Jammy requires me to create a new user, although users are present To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1971559/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971559] Re: After Ugrade, Jammy requires me to create a new user, although users are present
Not sure if ubiquoty package is the right place, please change if necessary. ** Package changed: ubuntu => ubiquity (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971559 Title: After Ugrade, Jammy requires me to create a new user, although users are present To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1971559/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971559] [NEW] After Ugrade, Jammy requires me to create a new user, although users are present
Public bug reported: I upgraded from 20.04 to 22.04 using "do-release-upgrade". At reboot, I see a kind of "first-run wizard" requiring me to create a new user and her profile. The dialog cannot be canncelled or skipped. There is no need creating a new user: there are already local users with sudo rights (obviously, I could not have run 20.04 otherwise!) and approx. 900 LDAP users, too. But somehow, Ubuntu seems to believe this was a fresh install with no users present. How can I skip this dialog? I already tried going through the dialog and creating a dummy user and removing it later – just to be greeted with the same dialog again on next boot! ** Affects: ubuntu Importance: Undecided Status: New ** Description changed: I upgraded from 20.04 to 22.04 using "do-release-upgrade". At reboot, I see a kind of "first-run wizard" requiring me to create a new user and her profile. The dialog cannot be canncelled or skipped. There is no need creating a new user: there are already local users with - sudo rights (obviously, I could not have run 22.04 otherwise!) and + sudo rights (obviously, I could not have run 20.04 otherwise!) and approx. 900 LDAP users, too. But somehow, Ubuntu seems to believe this was a fresh install with no users present. How can I skip this dialog? I already tried going through the dialog and creating a dummy user and removing it later – just to be greeted with the same dialog again on next boot! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971559 Title: After Ugrade, Jammy requires me to create a new user, although users are present To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1971559/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1697957] Re: Impress crashes when using smooth fade transition on Gnome based desktop environment
I ran into this problem today with LO Version: 6.4.7.2. (Both the crashes and the jagged, flickering transitions.) Is it possible that this was never fixed? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1697957 Title: Impress crashes when using smooth fade transition on Gnome based desktop environment To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1697957/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1458336] Re: Allow users to decide which apps can display anything in the circle
Addition to #5: Fluffychat seems to have solved how to do that: once in a while it slips in reminders as a circle message and this message always appears first after boot. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1458336 Title: Allow users to decide which apps can display anything in the circle To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1458336/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1458336] Re: Allow users to decide which apps can display anything in the circle
See also https://github.com/ubports/ubuntu-touch/issues/1391#issuecomment-600214923. It suggestes using the "circle message" app in order to display emergency data on the lock screen. However, it is not very useful if the message is not shown directly after boot. ** Bug watch added: github.com/ubports/ubuntu-touch/issues #1391 https://github.com/ubports/ubuntu-touch/issues/1391 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1458336 Title: Allow users to decide which apps can display anything in the circle To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1458336/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1458336] Re: Allow users to decide which apps can display anything in the circle
I'd like to add that it would be useful if one could customize the order of messages displayed. Especially which message is displayed right after bootup. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1458336 Title: Allow users to decide which apps can display anything in the circle To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1458336/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1458336] Re: Allow users to decide which apps can display anything in the circle
Still a very good idea. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1458336 Title: Allow users to decide which apps can display anything in the circle To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1458336/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856738] Re: access always denied when using @{HOME} tunable in peer_addr for abstract socket
Is this issue related to Bug #1890905?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1856738
Title:
access always denied when using @{HOME} tunable in peer_addr for
abstract socket
To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1856738/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1923053] Re: [SRU] nextcloud crashed with SIGSEGV.
(Sorry for the double posting.) Yes, I now see how this is to be meant, but it's not a direct popup but what you see when you select "Main Window" *from* the popup menu. – Anyway, unrelated to this issue, you are right, thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1923053 Title: [SRU] nextcloud crashed with SIGSEGV. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nextcloud-desktop/+bug/1923053/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1923053] Re: [SRU] nextcloud crashed with SIGSEGV.
Interesting. Here's how it looks on my desktop. The netcloud window disappears as soon as I click anywhere on the desktop. ** Attachment added: "Bildschirmfoto von 2021-04-26 20-35-20.png" https://bugs.launchpad.net/ubuntu/+source/nextcloud-desktop/+bug/1923053/+attachment/5492533/+files/Bildschirmfoto%20von%202021-04-26%2020-35-20.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1923053 Title: [SRU] nextcloud crashed with SIGSEGV. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nextcloud-desktop/+bug/1923053/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1923053] Re: [SRU] nextcloud crashed with SIGSEGV.
Interesting. Here's how it looks on my desktop. The netcloud window disappears as soon as I click anywhere on the desktop. ** Attachment added: "Bildschirmfoto von 2021-04-26 20-35-20.png" https://bugs.launchpad.net/ubuntu/+source/nextcloud-desktop/+bug/1923053/+attachment/5492532/+files/Bildschirmfoto%20von%202021-04-26%2020-35-20.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1923053 Title: [SRU] nextcloud crashed with SIGSEGV. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nextcloud-desktop/+bug/1923053/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1923053] Re: [SRU] nextcloud crashed with SIGSEGV.
nextcloud-desktop is back in hirsute-proposed, testing. Here's what I see: The client starts up and sync seems to work, but the main window ist next to unusable. Window shows, but has no title bar. Erratically, it switches to some text output and back again. The window cannot be moved, unless you hold the super-key. Soon, it disappears unexpectedly. There's definitively something wrong with the graphics toolkit, but sync seems to work. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1923053 Title: [SRU] nextcloud crashed with SIGSEGV. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nextcloud-desktop/+bug/1923053/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1923053] Re: [SRU] nextcloud crashed with SIGSEGV.
All right, thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1923053 Title: [SRU] nextcloud crashed with SIGSEGV. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nextcloud-desktop/+bug/1923053/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1923053] Re: [SRU] nextcloud crashed with SIGSEGV.
I can't find the package in proposed, what happened? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1923053 Title: [SRU] nextcloud crashed with SIGSEGV. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nextcloud-desktop/+bug/1923053/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916640] Re: Nvidia 340.108 fails to install with kernels 5.11.x - new patches needeed
Package from Butterfly (kelebek333) works with Hirsute. Thanks for the work, guys!! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1916640 Title: Nvidia 340.108 fails to install with kernels 5.11.x - new patches needeed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1916640/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908825] Re: Nvidia 340.108: Garbled graphics after resume
Your are right that Chromium seems often affected, but this is by no means limited to Chromium. See next screen shot, where Document Viewer (evince) is affected. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908825 Title: Nvidia 340.108: Garbled graphics after resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1908825/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908825] Re: Nvidia 340.108: Garbled graphics after resume
** Attachment added: "Evince showing distorted graphics" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1908825/+attachment/5446243/+files/Bildschirmfoto%20von%202020-12-23%2012-06-11.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908825 Title: Nvidia 340.108: Garbled graphics after resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1908825/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908825] Re: Nvidia 340.108: Garbled graphics after resume
** Attachment added: "Bildschirmfoto von 2020-11-24 12-21-43.png" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1908825/+attachment/5445242/+files/Bildschirmfoto%20von%202020-11-24%2012-21-43.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908825 Title: Nvidia 340.108: Garbled graphics after resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1908825/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908825] Re: Nvidia 340.108: Garbled graphics after resume
** Attachment added: "Bildschirmfoto von 2020-11-25 19-15-41.png" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1908825/+attachment/5445241/+files/Bildschirmfoto%20von%202020-11-25%2019-15-41.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908825 Title: Nvidia 340.108: Garbled graphics after resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1908825/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908825] Re: Nvidia 340.108: Garbled graphics after resume
** Attachment added: "Bildschirmfoto von 2020-11-25 19-16-06.png" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1908825/+attachment/5445240/+files/Bildschirmfoto%20von%202020-11-25%2019-16-06.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908825 Title: Nvidia 340.108: Garbled graphics after resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1908825/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908825] Re: Nvidia 340.108: Garbled graphics after resume
** Attachment added: "Bildschirmfoto von 2020-12-02 20-30-48.png" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1908825/+attachment/5445239/+files/Bildschirmfoto%20von%202020-12-02%2020-30-48.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908825 Title: Nvidia 340.108: Garbled graphics after resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1908825/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908825] Re: Nvidia 340.108: Garbled graphics after resume
** Attachment added: "Bildschirmfoto von 2020-12-03 15-17-09.png" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1908825/+attachment/5445238/+files/Bildschirmfoto%20von%202020-12-03%2015-17-09.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908825 Title: Nvidia 340.108: Garbled graphics after resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1908825/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908825] Re: Nvidia 340.108: Garbled graphics after resume
** Attachment added: "Bildschirmfoto von 2020-12-03 15-17-46.png" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1908825/+attachment/5445237/+files/Bildschirmfoto%20von%202020-12-03%2015-17-46.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908825 Title: Nvidia 340.108: Garbled graphics after resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1908825/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908825] [NEW] Nvidia 340.108: Garbled graphics after resume
Public bug reported: On my Thinkpad T61 using Nvidia 340.108 driver, I regularly see graphics distortions returning from suspend. (Not completely sure if it also appears after screen lock.) See attached screen shots. ** Affects: nvidia-graphics-drivers-340 (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Bildschirmfoto von 2020-12-15 13-53-22.png" https://bugs.launchpad.net/bugs/1908825/+attachment/5445236/+files/Bildschirmfoto%20von%202020-12-15%2013-53-22.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908825 Title: Nvidia 340.108: Garbled graphics after resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1908825/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776873] Re: Whitelisted allowedURLschemes breaks some desktop apps
I'm sorry to say we were forced to move from Chromium to Google Chrome (unconfined deb package). I am not at all happy with that, as our software is now less secure than it was before (with the unconfined Chromium). But I never managed to get the snap running for my users, snaps are just not designed to work in networks. Missing URL handlers was the least of our problems. Not being able to access network shares and snaps caching into the users's homes was what made it unusable. Very sad that a decision that supposedly was meant to make Chromium more secure has caused right the opposite for us. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776873 Title: Whitelisted allowedURLschemes breaks some desktop apps To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1776873/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872950] Re: Nvidia 340.108 fails to install with kernels 5.5 onward
On my Thinkpad T61 I still see garbled screen content resuming from sleep. Is this to e expected, or are will still missing some patch? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872950 Title: Nvidia 340.108 fails to install with kernels 5.5 onward To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1872950/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872950] Re: Nvidia 340.108 fails to install with kernels 5.5 onward
Thanks, that worked. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872950 Title: Nvidia 340.108 fails to install with kernels 5.5 onward To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1872950/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903729] Re: Fails to start in xenial
Missing depedencies? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903729 Title: Fails to start in xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pylang/+bug/1903729/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903729] [NEW] Fails to start in xenial
Public bug reported: CDalling pylang in a recent xenial install yields: ``` Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/pylang/pylang.py", line 20, in from view.pylang import Practice File "/usr/lib/python2.7/dist-packages/pylang/view/pylang.py", line 20, in from gi.repository import Gtk, Gdk, GObject ImportError: No module named gi.repository ``` ** Affects: pylang (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/1903729 Title: Fails to start in xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pylang/+bug/1903729/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872950] Re: Nvidia 340.108 fails to install with kernels 5.5 onward
Confirming: 340.108-0ubuntu5.20.10.1 installs, compiles and runs.
It does however compain:
> /var/lib/dkms/nvidia-340/340.108/source/dkms.conf: Zeile 16:
> PATCH{7]=do-not-call-pci_save_state.patch: Befehl nicht gefunden
(/var/lib/dkms/nvidia-340/340.108/source/dkms.conf: line 16: PATCH{7
]=do-not-call-pci_save_state.patch: command not found)
It seems, patch "o-not-call-pci_save_state.patch" ist missing in the
package.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1872950
Title:
Nvidia 340.108 fails to install with kernels 5.5 onward
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1872950/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896878] Re: Doesn't compile for groovy
This patch needa the /kernel/ path prefixes removed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896878 Title: Doesn't compile for groovy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1896878/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896878] Re: Doesn't compile for groovy
Here's how to resolve the issue: - put the two patches above into /usr/src/nvidia-340-340.108/patches/ - modify /usr/src/nvidia-340-340.108/dkms.conf: - remove any PATCH[] lines - add PATCH[0]="kernel-5.7.patch" PATCH[1]="0002-kernel-5.8.patch" - dpkg --configure nvidia-340 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896878 Title: Doesn't compile for groovy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1896878/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896878] Re: Doesn't compile for groovy
Here's how to resolve the issue: - put the two patches above into /usr/src/nvidia-340-340.108/patches/ - modify /usr/src/nvidia-340-340.108/dkms.conf: - remove any PATCH[] lines - add ```PATCH[0]="kernel-5.7.patch" PATCH[1]="buildfix_kernel_5.8.patch"``` - dpkg --configure nvidia-340 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896878 Title: Doesn't compile for groovy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1896878/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896878] Re: Doesn't compile for groovy
** Patch added: "patch for kernel-5.8" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1896878/+attachment/5427736/+files/0002-kernel-5.8.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896878 Title: Doesn't compile for groovy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1896878/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896878] Re: Doesn't compile for groovy
Answering my own question: No, this was the wrong file. I extracted the right one from the gut repository here: https://aur.archlinux.org/pkgbase/nvidia-340xx/ Needed to adjust the paths in the .patch file, but now it works. Attaching the adjusted patch. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896878 Title: Doesn't compile for groovy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1896878/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896878] Re: Doesn't compile for groovy
@satmandu: buildfix_kernel_5.8.patch is no longer accessible via the link you mention. Is this the same patch as mentioned here? (002-kernel-5.8.patch) https://aur.archlinux.org/packages/nvidia-340xx -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896878 Title: Doesn't compile for groovy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1896878/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896878] Re: Doesn't compile for groovy
Please, can this be fixed in time? Users on hardware that requires this driver have no other option: either this works or they are left with an anusable system (like myself right now). This is a »leave-Ubuntu«-impulse for everyone affected. Please!! Fix this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896878 Title: Doesn't compile for groovy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1896878/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901493] Re: fails to build on groovy [ERROR: Kernel configuration is invalid.]
*** This bug is a duplicate of bug 1896878 *** https://bugs.launchpad.net/bugs/1896878 Thanks for redirecting! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901493 Title: fails to build on groovy [ERROR: Kernel configuration is invalid.] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1901493/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901493] [NEW] fails to build on groovy [ERROR: Kernel configuration is invalid.]
Public bug reported: nvidia-340 fails to build after update to 20.10. Attaching crash log. Note: This is fatal on the Thinkpad T61. Desktop does not start. apt-cache policy nvidia-340 nvidia-340: Installiert: (keine) Installationskandidat: 340.108-0ubuntu5 Versionstabelle: 340.108-0ubuntu5 500 500 http://de.archive.ubuntu.com/ubuntu groovy/restricted amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: nvidia-340 (not installed) ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Oct 26 09:38:20 2020 InstallationDate: Installed on 2020-07-12 (105 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: nvidia-graphics-drivers-340 UpgradeStatus: Upgraded to groovy on 2020-10-25 (0 days ago) ** Affects: nvidia-graphics-drivers-340 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy ** Attachment added: "crash log when building nvidia-340 on groovy" https://bugs.launchpad.net/bugs/1901493/+attachment/5427169/+files/nvidia-340.0.crash -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901493 Title: fails to build on groovy [ERROR: Kernel configuration is invalid.] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1901493/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890905] Re: Snaps cannot access IBus when $XDG_CACHE_HOME is set
Sorry, I mixed up `.cache` and `.config` in the bug description (corrected). I originally found this problem referring to the users CACHE directory. But as ibus needs both, .cache and .config, it is to be expected that the same problem appears when users' CONFIG is relocated (wich is as easily possible as CACHE). The relevant environment variables from the freedesktop specification are (see https://specifications.freedesktop.org/basedir- spec/latest/ar01s03.html): - $XDG_CACHE_HOME (defaults to ~/.cache) - $XDG_CONFIG_HOME (defaults to ~/.config) Both must be taken care of, as there are valid reasons for setting them to non-standard locations, esp. in networking environments. ** Description changed: This is a follow-up to #1580463. (Note: I am not an expert in snap or apparmor related things, please correct me in anything I say below, thank you ;-).) Bug #1580463 dealt with a problem in snaps achieving a correct path for accessing IBus and has since been closed as fixed. Here, I describe a problem which is most probably related and appears when user caches are stored in non-standard locations (i.e., not in ~/.cache). Background: - IBus is an input method for graphical Desktops like GNOME, allowing easy keyboard input for some languages (like Asian languages). - It is the standard input method on GNOME, which is the standard desktop environment in Ubuntu. - - When the user logs into the desktop session, the IBus interface is created and sockets stored in the user's config directory, the default being ~/.config/ibus/bus/ . - - Applications need access to this data to consume keyboard input. + - When the user logs into the desktop session, the IBus interface is created and sockets stored in the user's cache directory, the default being ~/.cache/ibus/ and ~/.config/ibus/. + - Applications need access to these data to consume keyboard input. Regarding snaps: - Snaps are confined, meaning they have access to only the smallest possible subset of file paths – including strictly defined paths in the users's home directory. - - In the process of resolving #1580463, it has been ensured that snaps can safely access ~/.config/ibus/bus/, so they can consume keyboard input. + - In the process of resolving #1580463, it has been ensured that snaps can safely access ~/.cache/ibus/, so they can consume keyboard input. Issue at hand: - - There is a well-documented and perfectly valid way of moving a user's config directory away from the default location: + - There is a well-documented and perfectly valid way of moving a user's cache directory away from the default location: - It is defined by the freedesktop.org specification (see https://specifications.freedesktop.org/basedir-spec/latest/ar01s03.html) which GNOME adheres to. - - That specifies that all applications shall expect user specific configuration data to be located below $XDG_CONFIG_HOME, where this environment variable shall default to ~/.config if unset or empty. - - I here report that snaps currently do not follow this specification, causing them to *refuse any keyboard input when IBus is selected as input method and $XDG_CONFIG_HOME is set*. + - That specifies that all applications shall expect user specific cache data to be located below $XDG_CACHE_HOME, where this environment variable shall default to ~/.cache if unset or empty. + - I here report that snaps currently do not follow this specification, causing them to *refuse any keyboard input when IBus is selected as input method and $XDG_CACHE_HOME is set*. Typical use case: - - $XDG_CONFIG_HOME is typically set to a local file path when the users' home directories are located on a network share. + - $XDG_CACHE_HOME is typically set to a local file path when the users' home directories are located on a network share. - This is a typical setup for mid- to larger scale applications of Ubuntu, such as schools or universities. - Meaning this will affect *a lot of users* at institutions using Ubuntu (but not the average home user). Test case: - Chromium snap in Ubuntu 20.04[.1] - Upon upgrade from 18.04 LTS to 20.04 LTS, the chromium-browser deb package (unconfined) will forcefully be replaced by the (confined) chromium snap, which manifests above described problem. Impact: - - Chromium (and presumably other snaps) stop accepting keyboard input after LTS upgrade to Ubuntu 20.04 when $XDG_CONFIG_HOME is set. + - Chromium (and presumably other snaps) stop accepting keyboard input after LTS upgrade to Ubuntu 20.04 when $XDG_CACHE_HOME is set. This is a severe problem. Steps to reproduce: - - Set $XDG_CONFIG_HOME to a location different from ~/.config, such as /tmp/ or /var/. (Both are paths very likely be used by installs with network located homes. Note this must be done before the graphical session starts, like in the user's ~/.profile.) + - Set $XDG_CACHE_HOME to a location different from ~/.cache,
[Bug 1065126] Re: "Always do this from now on" does not work
I gave up on Firefox. Switched to Chromium instead. I'm sorry, but you need to take action at some time (and time means: 7 years and 10 months since I reported this). I hope the Firefox community can work this out, I am not longer part of it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1065126 Title: "Always do this from now on" does not work To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1065126/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890905] Re: Snaps cannot access IBus when $XDG_CACHE_HOME is set
Attaching relevant portions from journalctl: Once with and without XDG_CACHE_HOME set. Each time I launched the chrome snap, typed some keys, and quit. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890905 Title: Snaps cannot access IBus when $XDG_CACHE_HOME is set To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1890905/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890905] Re: Snaps cannot access IBus when $XDG_CACHE_HOME is set
** Attachment added: "Log with XDG:CACHE_HOME unset (working)" https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1890905/+attachment/5400722/+files/log-working -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890905 Title: Snaps cannot access IBus when $XDG_CACHE_HOME is set To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1890905/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890905] Re: Snaps cannot access IBus when $XDG_CACHE_HOME is set
** Attachment added: "Log with XDG:CACHE_HOME set (not working)" https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1890905/+attachment/5400723/+files/log-notworking2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890905 Title: Snaps cannot access IBus when $XDG_CACHE_HOME is set To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1890905/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890905] Re: Snaps cannot access IBus when $XDG_CACHE_HOME is set
** Description changed: This is a follow-up to #1580463. (Note: I am not an expert in snap or apparmor related things, please correct me in anything I say below, thank you ;-).) Bug #1580463 dealt with a problem in snaps achieving a correct path for accessing IBus and has since been closed as fixed. Here, I describe a problem which is most probably related and appears when user caches are stored in non-standard locations (i.e., not in ~/.cache). Background: - IBus is an input method for graphical Desktops like GNOME, allowing easy keyboard input for some languages (like Asian languages). - It is the standard input method on GNOME, which is the standard desktop environment in Ubuntu. - When the user logs into the desktop session, the IBus interface is created and sockets stored in the user's config directory, the default being ~/.config/ibus/bus/ . - Applications need access to this data to consume keyboard input. Regarding snaps: - Snaps are confined, meaning they have access to only the smallest possible subset of file paths – including strictly defined paths in the users's home directory. - In the process of resolving #1580463, it has been ensured that snaps can safely access ~/.config/ibus/bus/, so they can consume keyboard input. Issue at hand: - There is a well-documented and perfectly valid way of moving a user's config directory away from the default location: - It is defined by the freedesktop.org specification (see https://specifications.freedesktop.org/basedir-spec/latest/ar01s03.html) which GNOME adheres to. - That specifies that all applications shall expect user specific configuration data to be located below $XDG_CONFIG_HOME, where this environment variable shall default to ~/.config if unset or empty. - I here report that snaps currently do not follow this specification, causing them to *refuse any keyboard input when IBus is selected as input method and $XDG_CONFIG_HOME is set*. Typical use case: - $XDG_CONFIG_HOME is typically set to a local file path when the users' home directories are located on a network share. - This is a typical setup for mid- to larger scale applications of Ubuntu, such as schools or universities. - Meaning this will affect *a lot of users* at institutions using Ubuntu (but not the average home user). Test case: - Chromium snap in Ubuntu 20.04[.1] - Upon upgrade from 18.04 LTS to 20.04 LTS, the chromium-browser deb package (unconfined) will forcefully be replaced by the (confined) chromium snap, which manifests above described problem. Impact: - Chromium (and presumably other snaps) stop accepting keyboard input after LTS upgrade to Ubuntu 20.04 when $XDG_CONFIG_HOME is set. This is a severe problem. Steps to reproduce: - - Set $XDG_CONFIG_HOME to a location different from ~/.config. (This must be done before the graphical session starts, like in the user's ~/.profile.) + - Set $XDG_CONFIG_HOME to a location different from ~/.config, such as /tmp/ or /var/. (Both are paths very likely be used by installs with network located homes. Note this must be done before the graphical session starts, like in the user's ~/.profile.) - Log the user out from and in again to the graphical session. - Confirm (from a terminal) that IBus data is now located below $XDG_CONFIG_HOME/ibus/bus. - (rm -r ~/snap/chromium/current/.config/ if you had formerly started the chromium snap) - Start the chromium snap. - Observe that *it refuses to read any keyboard input*. ** Description changed: This is a follow-up to #1580463. (Note: I am not an expert in snap or apparmor related things, please correct me in anything I say below, thank you ;-).) Bug #1580463 dealt with a problem in snaps achieving a correct path for accessing IBus and has since been closed as fixed. Here, I describe a problem which is most probably related and appears when user caches are stored in non-standard locations (i.e., not in ~/.cache). Background: - IBus is an input method for graphical Desktops like GNOME, allowing easy keyboard input for some languages (like Asian languages). - It is the standard input method on GNOME, which is the standard desktop environment in Ubuntu. - When the user logs into the desktop session, the IBus interface is created and sockets stored in the user's config directory, the default being ~/.config/ibus/bus/ . - Applications need access to this data to consume keyboard input. Regarding snaps: - Snaps are confined, meaning they have access to only the smallest possible subset of file paths – including strictly defined paths in the users's home directory. - In the process of resolving #1580463, it has been ensured that snaps can safely access ~/.config/ibus/bus/, so they can consume keyboard input. Issue at hand: - There is a well-documented and perfectly valid way of moving a user's config directory away from
[Bug 1580463] Re: Snap blocks access to system input methods (ibus, fcitx, ...)
For your reference: Bug #1890905 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1580463 Title: Snap blocks access to system input methods (ibus, fcitx, ...) To manage notifications about this bug go to: https://bugs.launchpad.net/ibus/+bug/1580463/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890905] Re: Snaps cannot access IBus when $XDG_CACHE_HOME is set
** Description changed: This is a follow-up to #1580463. (Note: I am not an expert in snap or apparmor related things, please correct me in anything I say below, thank you ;-).) Bug #1580463 dealt with a problem in snaps achieving a correct path for accessing IBus and has since been closed as fixed. Here, I describe a problem which is most probably related and appears when user caches are stored in non-standard locations (i.e., not in ~/.cache). Background: - IBus is an input method for graphical Desktops like GNOME, allowing easy keyboard input for some languages (like Asian languages). - It is the standard input method on GNOME, which is the standard desktop environment in Ubuntu. - When the user logs into the desktop session, the IBus interface is created and sockets stored in the user's config directory, the default being ~/.config/ibus/bus/ . - Applications need access to this data to consume keyboard input. Regarding snaps: - Snaps are confined, meaning they have access to only the smallest possible subset of file paths – including strictly defined paths in the users's home directory. - In the process of resolving #1580463, it has been ensured that snaps can safely access ~/.config/ibus/bus/, so they can consume keyboard input. Issue at hand: - There is a well-documented and perfectly valid way of moving a user's config directory away from the default location: - It is defined by the freedesktop.org specification (see https://specifications.freedesktop.org/basedir-spec/latest/ar01s03.html) which GNOME adheres to. - That specifies that all applications shall expect user specific configuration data to be located below $XDG_CONFIG_HOME, where this environment variable shall default to ~/.config if unset or empty. - I here report that snaps currently do not follow this specification, causing them to *refuse any keyboard input when IBus is selected as input method and $XDG_CONFIG_HOME is set*. + - $XDG_CONFIG_HOME is typically set to a local file path when the users' home directories are located on a network share. + - This is a typical setup for mid- to larger scale applications of Ubuntu, such as schools or universities. + - Meaning this will affect *a lot of users* at institutions using Ubuntu (but not the average home user). + + + Test case: + - Chromium snap in Ubuntu 20.04[.1] + - Upon upgrade from 18.04 LTS to 20.04 LTS, the chromium-browser deb package (unconfined) will forcefully be replaced by the (confined) chromium snap, which manifests above described problem. + + Impact: + - Chromium (and presumably other snaps) stop accepting keyboard input after LTS upgrade to Ubuntu 20.04 when $XDG_CONFIG_HOME is set. + + This is a severe problem. + + + Steps to reproduce: + - Set $XDG_CONFIG_HOME to a location different from ~/.config. (This must be done before the graphical session starts, like in the user's ~/.profile.) + - Log the user out from and out again to the graphical session. + - Confirm (from a terminal) that IBus data is now located below $XDG_CONFIG_HOME/ibus/bus. + - (rm -r ~/.config/snap/chromium if you had formerly started the chromium snap) + - Start the chromium snap. + - Observe that *it refuses to read any keyboard input*. ** Description changed: This is a follow-up to #1580463. (Note: I am not an expert in snap or apparmor related things, please correct me in anything I say below, thank you ;-).) Bug #1580463 dealt with a problem in snaps achieving a correct path for accessing IBus and has since been closed as fixed. Here, I describe a problem which is most probably related and appears when user caches are stored in non-standard locations (i.e., not in ~/.cache). Background: - IBus is an input method for graphical Desktops like GNOME, allowing easy keyboard input for some languages (like Asian languages). - It is the standard input method on GNOME, which is the standard desktop environment in Ubuntu. - When the user logs into the desktop session, the IBus interface is created and sockets stored in the user's config directory, the default being ~/.config/ibus/bus/ . - Applications need access to this data to consume keyboard input. Regarding snaps: - Snaps are confined, meaning they have access to only the smallest possible subset of file paths – including strictly defined paths in the users's home directory. - In the process of resolving #1580463, it has been ensured that snaps can safely access ~/.config/ibus/bus/, so they can consume keyboard input. Issue at hand: - There is a well-documented and perfectly valid way of moving a user's config directory away from the default location: - It is defined by the freedesktop.org specification (see https://specifications.freedesktop.org/basedir-spec/latest/ar01s03.html) which GNOME adheres to. - That specifies that all applications shall expect user specific configuration data to be located
[Bug 1890905] Re: Snaps cannot access IBus when $XDG_CACHE_HOME is set
Cross references: - https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1580463/comments/39 indicating that /home/* may be hard coded for snap access (breaking the freedesktop.org specs) - https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1580463/comments/40 stating that this *should* have been changed to $XDG_CACHE_HOME/ibus – but apparently this did not work. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890905 Title: Snaps cannot access IBus when $XDG_CACHE_HOME is set To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1890905/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890905] [NEW] Snaps cannot access IBus when $XDG_CACHE_HOME is set
Public bug reported: This is a follow-up to #1580463. (Note: I am not an expert in snap or apparmor related things, please correct me in anything I say below, thank you ;-).) Bug #1580463 dealt with a problem in snaps achieving a correct path for accessing IBus and has since been closed as fixed. Here, I describe a problem which is most probably related and appears when user caches are stored in non-standard locations (i.e., not in ~/.cache). Background: - IBus is an input method for graphical Desktops like GNOME, allowing easy keyboard input for some languages (like Asian languages). - It is the standard input method on GNOME, which is the standard desktop environment in Ubuntu. - When the user logs into the desktop session, the IBus interface is created and sockets stored in the user's config directory, the default being ~/.config/ibus/bus/ . - Applications need access to this data to consume keyboard input. Regarding snaps: - Snaps are confined, meaning they have access to only the smallest possible subset of file paths – including strictly defined paths in the users's home directory. - In the process of resolving #1580463, it has been ensured that snaps can safely access ~/.config/ibus/bus/, so they can consume keyboard input. Issue at hand: - There is a well-documented and perfectly valid way of moving a user's config directory away from the default location: - It is defined by the freedesktop.org specification (see https://specifications.freedesktop.org/basedir-spec/latest/ar01s03.html) which GNOME adheres to. - That specifies that all applications shall expect user specific configuration data to be located below $XDG_CONFIG_HOME, where this environment variable shall default to ~/.config if unset or empty. - I here report that snaps currently do not follow this specification, causing them to *refuse any keyboard input when IBus is selected as input method and $XDG_CONFIG_HOME is set*. ** Affects: snapd (Ubuntu) Importance: Undecided Status: New ** Description changed: This is a follow-up to #1580463. (Note: I am not an expert in snap or apparmor related things, please correct my in anything I say below, thank you ;-).) Bug #1580463 dealt with a problem in snaps achieving a correct path for - accessing IBus and has since closed as fixed. Here, I describe a problem - which is most probably related and appears when user caches are stored - in non-standard locations (i.e., not in ~/.cache). + accessing IBus and has since been closed as fixed. Here, I describe a + problem which is most probably related and appears when user caches are + stored in non-standard locations (i.e., not in ~/.cache). Background: - IBus is an input method for graphical Desktops like GNOME, allowing easy keyboard input for some languages (like Asian languages). - It is the standard input method on GNOME, which is the standard desktop environment in Ubuntu. - When the user logs into the desktop session, the IBus interface is created and sockets stored in the user's config directory, the default being ~/.config/ibus/bus/ . - Applications need access to this data to consume keyboard input. Regarding snaps: - Snaps are confined, meaning they have access to only the smallest possible subset of file paths – including strictly defined paths in the users's home directory. - In the process of resolving #1580463, it has been ensured that snaps can safely access ~/.config/ibus/bus/, so they can consume keyboard input. Issue at hand: - There is a well-documented and perfectly valid way of moving a user's config directory away from the default location: - It is defined by the freedesktop.org specification (see https://specifications.freedesktop.org/basedir-spec/latest/ar01s03.html) which GNOME adheres to. - That specifies that all applications shall expect user specific configuration data to be located below $XDG_CONFIG_HOME, where this environment variable shall default to ~/.config if unset or empty. - I here report that snaps currently do not follow this specification, causing them to *refuse any keyboard input when IBus is selected as input method*. ** Description changed: This is a follow-up to #1580463. (Note: I am not an expert in snap or - apparmor related things, please correct my in anything I say below, + apparmor related things, please correct me in anything I say below, thank you ;-).) Bug #1580463 dealt with a problem in snaps achieving a correct path for accessing IBus and has since been closed as fixed. Here, I describe a problem which is most probably related and appears when user caches are stored in non-standard locations (i.e., not in ~/.cache). Background: - IBus is an input method for graphical Desktops like GNOME, allowing easy keyboard input for some languages (like Asian languages). - It is the standard input method on GNOME, which is the standard desktop environment in Ubuntu. - When the user
[Bug 1580463] Re: Snap blocks access to system input methods (ibus, fcitx, ...)
Agreed. I'll be referencing this issue there. And I'll have a look into the journal, thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1580463 Title: Snap blocks access to system input methods (ibus, fcitx, ...) To manage notifications about this bug go to: https://bugs.launchpad.net/ibus/+bug/1580463/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1580463] Re: Snap blocks access to system input methods (ibus, fcitx, ...)
We are talking about recent Ubuntu focal, thst is: Ubuntu 20.04.1. This is deemed safe for LTS upgrade! It is not! It will make petfectly working installs of 18.04 LTS unusable without any warning. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1580463 Title: Snap blocks access to system input methods (ibus, fcitx, ...) To manage notifications about this bug go to: https://bugs.launchpad.net/ibus/+bug/1580463/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1580463] Re: Snap blocks access to system input methods (ibus, fcitx, ...)
This will affect many installs, notably in professional multi user environments. It is absurd assuming that $XDG_CACHE_HOME is unset (any installation with a few hundred users will have homes on a network share and consequently caches moved elsewhere). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1580463 Title: Snap blocks access to system input methods (ibus, fcitx, ...) To manage notifications about this bug go to: https://bugs.launchpad.net/ibus/+bug/1580463/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1580463] Re: Snap blocks access to system input methods (ibus, fcitx, ...)
Test case: chromium snap with $XDG_CACHE_HOME set. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1580463 Title: Snap blocks access to system input methods (ibus, fcitx, ...) To manage notifications about this bug go to: https://bugs.launchpad.net/ibus/+bug/1580463/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1580463] Re: Snap blocks access to system input methods (ibus, fcitx, ...)
Our $XDG_CACHE_HOME points to /var/cache/usercache//
I tried adding /var/cache/usercache/ to @{HOMEDIRS} in apparmor, but it did not
work. How do I tell my snaps that user caches are in /var/cache/usercache/ ??
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1580463
Title:
Snap blocks access to system input methods (ibus, fcitx, ...)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ibus/+bug/1580463/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1580463] Re: Snap blocks access to system input methods (ibus, fcitx, ...)
This is *not* fixed. I still see this issue in a recent install of Ubuntu 20.04, where $XDG_CACHE_HOME is set. We have home dirs mounted via network, so user caches were moved to local storage to sanitize network load. The right and perfectly valid way of doing so is setting $XDG_CACHE_HOME. Snapd honors this variable, from what I get from related bug reports. However, it appears that snaps are still not allowed access to the direcrory configured in this environment variable. This is a production environment for 800+ users who rely on chromium and Ubuntu. I *really, honestly* need this fixed ASOP. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1580463 Title: Snap blocks access to system input methods (ibus, fcitx, ...) To manage notifications about this bug go to: https://bugs.launchpad.net/ibus/+bug/1580463/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776873] Re: Whitelisted allowedURLschemes breaks some desktop apps
@akkzilla is right, this is more like a problem of general intercommunication of snaps. It probably needs a decent framework for snaps as a whole, not only the chromium snap. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776873 Title: Whitelisted allowedURLschemes breaks some desktop apps To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1776873/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776873] Re: Whitelisted allowedURLschemes breaks some desktop apps
Snaps do have that concept of plugs and sockets. Shouldn't that be the way of solving this? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776873 Title: Whitelisted allowedURLschemes breaks some desktop apps To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1776873/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776873] Re: Whitelisted allowedURLschemes breaks some desktop apps
Jusr wanted to comment on Samuele Pedroni referring to "rudeness" – then I saw that Balazs Gyurak already did: Yes, I saw the comment that has subsequently been removed from this forum post, and Samuele was completely right to object. Please remove this part of your article. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776873 Title: Whitelisted allowedURLschemes breaks some desktop apps To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1776873/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871844] Re: [Snap] xdg-open not working
*** This bug is a duplicate of bug 1776873 *** https://bugs.launchpad.net/bugs/1776873 Thanks for referring! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871844 Title: [Snap] xdg-open not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1871844/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871844] [NEW] [Snap] xdg-open not working
Public bug reported: Several services register handlers for opening links in their external applications (examples: zoom.us, Microsoft Teams). Following a link to the respective content makes chromium display a box asking if xdg-open should be called. When I choose yes, nothing happens at all. Example content: https://t1p.de/WebinarZSL (That's a webinar for schools using MS Teams. The Teams app can be downloaded from their page.) ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: chromium-browser (not installed) ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18 Uname: Linux 5.3.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 9 14:54:39 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2015-12-13 (1579 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: chromium-browser UpgradeStatus: Upgraded to eoan on 2019-10-19 (173 days ago) ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871844 Title: [Snap] xdg-open not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1871844/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1598665] Re: Option "use this connection only for resources on its network" not respected
Still true on 19.10. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1598665 Title: Option "use this connection only for resources on its network" not respected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1598665/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856289] Re: TimedLogin feature not working when user list is disabled
Sorry, my reply got lost in conversation. Yes, I did set disable-user-list=true. Thanks for pointing me to the red hat bug report, that's obviously the same bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856289 Title: TimedLogin feature not working when user list is disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1856289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856289] Re: TimedLogin feature not working when user list is disabled
** Summary changed: - TimedLogin feature not working in Ubuntu 18.04 + TimedLogin feature not working when user list is disabled -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856289 Title: TimedLogin feature not working when user list is disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1856289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856289] [NEW] TimedLogin feature not working in Ubuntu 18.04
Public bug reported: In Ubuntu 18.04.3, gdm3's TimedLogin feature is not working. Steps to reproduce: In /etc/gdm3/custom.conf, uncomment these lines TimedLoginEnable = true TimedLogin = user1 TimedLoginDelay = 10 and change "user1" to an exiting user name. Reboot. Observe that nothing happens at all. Syslog has the following errors: Dec 12 15:45:23 rechner-lz-06 gnome-shell[1887]: JS ERROR: TypeError: this._timedLoginItem is null#012_resetTimedLogin@resource:///org/gnome/shell/gdm/loginDialog.js:1068:13#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012_onTimedLoginRequested/<@resource:///org/gnome/shell/gdm/loginDialog.js:1089:16 In contrast, AutomaticLogin feature works as expected. ** Affects: gdm3 (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/1856289 Title: TimedLogin feature not working in Ubuntu 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1856289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 839019] Re: bringing up 10ec:8185 wifi module freezes the system
I do not use the respective hardware any longer, but it still exists. Going to test it if I find the time. Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/839019 Title: bringing up 10ec:8185 wifi module freezes the system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/839019/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1178272] Re: Lubuntu: banshee, rhythmbox, etc cannot play audio without pulseaudio or gstreamer1.0-alsa
Hello Chris Guiver, I am not currently using Lubuntu on any device, so I cannot easily test if the problem still exists. User deutrino could have more information. @deutrino: Has the bug reached attention upstream? Is it still present in recent Lubuntu installs? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1178272 Title: Lubuntu: banshee, rhythmbox, etc cannot play audio without pulseaudio or gstreamer1.0-alsa To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/banshee/+bug/1178272/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1036236] Re: hpcups and hpijs driver use different rasterization
Well, at least Suma Byrappa is the person that has this bug assigned, and Amarnath Chitumalla is listes as "may be notified" on this page. The two should probably know the answer. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1036236 Title: hpcups and hpijs driver use different rasterization To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/1036236/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1036236] Re: hpcups and hpijs driver use different rasterization
Is the hpcups driver actually being maintained by HP? Or is this a community driver? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1036236 Title: hpcups and hpijs driver use different rasterization To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/1036236/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1036236] Re: hpcups and hpijs driver use different rasterization
For the record: Upstream bug is at https://bugs.launchpad.net/hplip/+bug/1036236. But projects are linked. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1036236 Title: hpcups and hpijs driver use different rasterization To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/1036236/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1036236] Re: hpcups and hpijs driver use different rasterization
Hello J T, thanks for reporting that this is still a problem. I had originally filed this report in 2012, but since it never moved forward I just resigned and kept using the HPIJS driver, which produces much better (in terms of visually accurate) output. However, Till Kamppeter says that Ubuntu is actively phasing out the HPIJS driver. This means that the HPCUPS driver needs to be improved/fixed. This bug is (upstream) assigned to Suma Byrappa, so he/she should be the person to contact. @Suma Byrappa: Can you confirm that hpcups uses different halftoning algorithms (amplitude vs. frequency modulation). Why is this? Why does it mainly concern greyscale prints, not color? How about adding an option of selecting the algorithm in the officially maintained driver (which is hpcups, as I understand)? Thanks for your support! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1036236 Title: hpcups and hpijs driver use different rasterization To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/1036236/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767564] Re: Ubuntu 18.04 Workspaces only change on primary monitor
@torzsmokus > the Activities (and the hot corner) on the secondary display shows windows on > all workspaces I had noticed that too, but it appears this bug was fixed. I cannot reproduce it in a current Ubuntu Cosmic install. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767564 Title: Ubuntu 18.04 Workspaces only change on primary monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1767564/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1502644] Re: nm-applet frequentyl fails with broadband activated
This bugh is no longer present in recent Ubuntu. Thanks for caring, Paul. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1502644 Title: nm-applet frequentyl fails with broadband activated To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1502644/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1806385] Re: Creating a new slide by double click not working correctly
Na problem, here it is: https://bugs.documentfoundation.org/show_bug.cgi?id=121927 ** Bug watch added: Document Foundation Bugzilla #121927 https://bugs.documentfoundation.org/show_bug.cgi?id=121927 ** Also affects: df-libreoffice via https://bugs.documentfoundation.org/show_bug.cgi?id=121927 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/1806385 Title: Creating a new slide by double click not working correctly To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1806385/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1806385] Re: [snap] Creating new slide by double click not working correctly
I don't know if the bug is related to the snap. Probably not. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1806385 Title: [snap] Creating new slide by double click not working correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1806385/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1806385] [NEW] [snap] Creating new slide by double click not working correctly
Public bug reported: Version: 6.1.3.2 Build-ID: libreoffice-6.1.3.2-snap1 You can create new slides in impress by double clicking on the empty part of the slides pane (below the existing slide). However, this works only as expected while the slides pane actually has empty space at the bottom. As soon as I have created a few slides, the slides pane is completely filled, and two things happen: (1) Improvement: It is very hard to double click on the thin white space at the bottom of the filled slides pane. This could be improved by always letting a few pixels at the bottom to click on. (2) Bug: You can actually manage to double click there and this creates a new slide. However, this new slide is not filed at the end of slides (as it should) but appears at a strange location somewhere in the middle of slides. This is definitely wrong. ** Affects: libreoffice (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/1806385 Title: [snap] Creating new slide by double click not working correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1806385/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1393688] Re: open *.ppt file in libreoffice Impress is abnormal
For me, the file opens in impress. I see only one (incomplete) slide, as shijing described. Version: 6.1.3.2 Build-ID: libreoffice-6.1.3.2-snap1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1393688 Title: open *.ppt file in libreoffice Impress is abnormal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1393688/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1805015] Re: [snap] Documents opened with libreoffice snap do not appear in "recent files" list of nautilus
Thanks Olivier, I see the potential leak. However, it makes LO somewhat less useful for me, because I very frequently access files form the recently used list. All in all, it seems that the question is, how snaps can be integrated into a desktop shell so as to give the user a flawless experience of the desktop as a whole. For years, desktop shells like GNOME or KDE strive to give an integrated "touch and feel" to the user. The (intended) separation of snaps from each other seem to contradict this design goal. In the end, the desktop might just feel like a loose assembly of separate applications running side by side without much interaction. I'm not sure how this can be resolved. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1805015 Title: [snap] Documents opened with libreoffice snap do not appear in "recent files" list of nautilus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1805015/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1805015] Re: [Snap] Documents opened with libreoffice snap do not appear in "recent files" list of nautilus
For me, this disrupts the daily workflow with LO to an extent where I consider changing back from the snap to deb. ** Summary changed: - [Snap] Documents opened with linbreoffice snap do not appear in "recent files" list of nautilus + [Snap] Documents opened with libreoffice snap do not appear in "recent files" list of nautilus ** Description changed: - I'm not sure of it's nautilus or Gnome shell keeping the list of recent files. I#m talking about this file: - ~/.local/share/recently-used.xbel + I'm not sure of it's nautilus or Gnome shell keeping the list of recent files. I'm talking about this file: + ~/.local/share/recently-used.xbel It usually contains all recently used files. However, if you open some file with the libreoffice snap, it won't get added to this list. Consequently, it will not later appear in the "recently used" section of nautilus, nor will the Gnome shell "recent files" plugin list it. It is, however, in Linbreoffice'w own recent files list (Files->Recently used documents) ** Description changed: I'm not sure of it's nautilus or Gnome shell keeping the list of recent files. I'm talking about this file: ~/.local/share/recently-used.xbel It usually contains all recently used files. However, if you open some file with the libreoffice snap, it won't get added to this list. Consequently, it will not later appear in the "recently used" section of nautilus, nor will the Gnome shell "recent files" plugin list it. - It is, however, in Linbreoffice'w own recent files list (Files->Recently + It is, however, in Linbreoffice's own recent files list (Files->Recently used documents) ** Description changed: - I'm not sure of it's nautilus or Gnome shell keeping the list of recent files. I'm talking about this file: + I'm not sure if it's nautilus or Gnome shell keeping the list of recent files. I'm talking about this file: ~/.local/share/recently-used.xbel It usually contains all recently used files. However, if you open some file with the libreoffice snap, it won't get added to this list. Consequently, it will not later appear in the "recently used" section of nautilus, nor will the Gnome shell "recent files" plugin list it. It is, however, in Linbreoffice's own recent files list (Files->Recently used documents) ** Description changed: I'm not sure if it's nautilus or Gnome shell keeping the list of recent files. I'm talking about this file: ~/.local/share/recently-used.xbel It usually contains all recently used files. However, if you open some file with the libreoffice snap, it won't get added to this list. Consequently, it will not later appear in the "recently used" section of nautilus, nor will the Gnome shell "recent files" plugin list it. - It is, however, in Linbreoffice's own recent files list (Files->Recently + It is, however, in Libreoffice's own recent files list (Files->Recently used documents) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1805015 Title: [Snap] Documents opened with libreoffice snap do not appear in "recent files" list of nautilus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1805015/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1805015] [NEW] [Snap] Documents opened with linbreoffice snap do not appear in "recent files" list of nautilus
Public bug reported: I'm not sure of it's nautilus or Gnome shell keeping the list of recent files. I#m talking about this file: ~/.local/share/recently-used.xbel It usually contains all recently used files. However, if you open some file with the libreoffice snap, it won't get added to this list. Consequently, it will not later appear in the "recently used" section of nautilus, nor will the Gnome shell "recent files" plugin list it. It is, however, in Linbreoffice'w own recent files list (Files->Recently used documents) ** Affects: libreoffice (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/1805015 Title: [Snap] Documents opened with linbreoffice snap do not appear in "recent files" list of nautilus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1805015/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1036168] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1036168/+attachment/5201257/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1036168 Title: Superfluous option "print-color-mode" cannot be removed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1036168/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1036168] Locale.txt
apport information ** Attachment added: "Locale.txt" https://bugs.launchpad.net/bugs/1036168/+attachment/5201258/+files/Locale.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1036168 Title: Superfluous option "print-color-mode" cannot be removed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1036168/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1036168] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1036168/+attachment/5201256/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1036168 Title: Superfluous option "print-color-mode" cannot be removed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1036168/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1036168] Re: Superfluous option "print-color-mode" cannot be removed
Hello, interestingly, the problem still exists in bionic. There are two "advanced options", "print-color-ode" and "job-cancel-after" that cannot be removed or changed (as meilan pointed out above). ** Tags added: apport-collected bionic ** Description changed: Drivers: hp-color_laserjet_cp1515n-pcl3.ppd hp-color_laserjet_cp1515n-hpijs-pcl3.ppd Both drivers display an advanced option called "print-color-mode" in the "Job Options" panel, which is superfluous, since color mode is selected on the "Printer Options" panel. Moreover, trying to remove this option pressing the "remove" button does not work. The option seems to disappear, but reappears when the dialog is displayed next time. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: hplip 3.12.2-1ubuntu3.1 ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24 Uname: Linux 3.2.0-29-generic i686 ApportVersion: 2.0.1-0ubuntu12 Architecture: i386 CurrentDmesg: [ 63.368304] init: plymouth-stop pre-start process (1700) terminated with status 1 Date: Mon Aug 13 14:47:01 2012 Lpstat: device for Farblaser: hp:/net/HP_Color_LaserJet_CP1515n?zc=NPIE56824 MachineType: exone D156200 Papersize: letter PpdFiles: Farblaser: HP Color LaserJet cp1515n pcl3, hpcups 3.12.2 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-29-generic root=/dev/mapper/lvmvg-Root ro quiet splash vt.handoff=7 SourcePackage: hplip UpgradeStatus: Upgraded to precise on 2012-04-26 (108 days ago) dmi.bios.date: 04/23/2004 dmi.bios.vendor: FUJITSU SIEMENS // Phoenix Technologies Ltd. dmi.bios.version: 4.06 Rev. 1.09.1562 dmi.board.name: D1562 dmi.board.vendor: FUJITSU SIEMENS dmi.board.version: S26361-D1562 dmi.chassis.type: 6 dmi.chassis.vendor: exone dmi.modalias: dmi:bvnFUJITSUSIEMENS//PhoenixTechnologiesLtd.:bvr4.06Rev.1.09.1562:bd04/23/2004:svnexone:pnD156200:pvr:rvnFUJITSUSIEMENS:rnD1562:rvrS26361-D1562:cvnexone:ct6:cvr: dmi.product.name: D156200 dmi.sys.vendor: exone + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.4 + Architecture: amd64 + CupsErrorLog: + W [15/Oct/2018:17:43:09 +0200] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'Farblaser-Gray..\' already exists + W [15/Oct/2018:17:43:09 +0200] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'Farblaser-CMYK..\' already exists + W [15/Oct/2018:17:43:16 +0200] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'Farblaser-Gray..\' already exists + W [15/Oct/2018:17:43:16 +0200] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'Farblaser-CMYK..\' already exists + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 18.04 + EcryptfsInUse: Yes + InstallationDate: Installed on 2015-12-13 (1037 days ago) + InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) + Lpstat: device for Farblaser: socket://192.168.1.8 + MachineType: LENOVO 34382AG + Package: hplip 3.17.10+repack0-5 + PackageArchitecture: amd64 + Papersize: a4 + PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/Farblaser.ppd'] failed with exit code 2: grep: /etc/cups/ppd/Farblaser.ppd: Permission denied + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=/dev/mapper/vg-lv--root ro noprompt quiet splash vt.handoff=1 + ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 + Tags: bionic + Uname: Linux 4.15.0-36-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 06/19/2018 + dmi.bios.vendor: LENOVO + dmi.bios.version: GCETB1WW (2.71 ) + dmi.board.asset.tag: Not Available + dmi.board.name: 34382AG + dmi.board.vendor: LENOVO + dmi.board.version: Not Defined + dmi.chassis.asset.tag: No Asset Information + dmi.chassis.type: 10 + dmi.chassis.vendor: LENOVO + dmi.chassis.version: Not Available + dmi.modalias: dmi:bvnLENOVO:bvrGCETB1WW(2.71):bd06/19/2018:svnLENOVO:pn34382AG:pvrThinkPadX230Tablet:rvnLENOVO:rn34382AG:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: + dmi.product.family: ThinkPad X230 Tablet + dmi.product.name: 34382AG + dmi.product.version: ThinkPad X230 Tablet + dmi.sys.vendor: LENOVO -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1036168 Title: Superfluous option "print-color-mode" cannot be removed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1036168/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1036168] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1036168/+attachment/5201266/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1036168 Title: Superfluous option "print-color-mode" cannot be removed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1036168/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
