Indeed, I confirmed the issue and the fix by doing a
$ sudo snap refresh --edge snapd
restarting the machine and trying to print again the printer are listed
again (note that if you try that you might want to refresh back to
--stable later on otherwise you will track unstable snapd builds)
**
** Tags added: rls-jj-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1967799
Title:
firefox, chromium and other snap apps can't print
To manage notifications about this bug go to:
The log has
CUPS: Error getting default printer: Bad file descriptor
unsure if that's the issue, and maybe the snapd fix mentioned is needed?
** Changed in: snapd (Ubuntu)
Status: Incomplete => New
** Changed in: snapd (Ubuntu)
Importance: Undecided => High
--
You received this bug
Just yesterday we landed a fix in snapd to address some issues with
cups: https://github.com/snapcore/snapd/pull/11616
Unfortunately I do not know the details of the issue that this change
solves, but maybe someone with more knowledge of cups can tell if that
change could fix this bug too.
--
$ dpkg -l | grep xdg-desktop-portal
ii xdg-desktop-portal 1.14.1-2
amd64desktop integration portal for Flatpak and
Snap
ii xdg-desktop-portal-gnome 42.0.1-1
journalctl -b 0
** Attachment added: "log"
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1967799/+attachment/5577038/+files/log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1967799
Thank you for your bug report, could you add your 'journalctl -b 0 >
log' to the bug after trying to print?
Also could you share the output of
$ dpkg -l | grep xdg-desktop-portal
** Changed in: snapd (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you
