[Desktop-packages] [Bug 1894715] Re: sane-utils update-inetd: warning: cannot add service, /etc/inetd.conf does not exist
this is 3 years ago. are we really only 4 people using scanners anymore? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1894715 Title: sane-utils update-inetd: warning: cannot add service, /etc/inetd.conf does not exist Status in sane-backends package in Ubuntu: Confirmed Bug description: Following warning displayed during install Setting up sane-utils (1.0.29-0ubuntu5.1) ... update-inetd: warning: cannot add service, /etc/inetd.conf does not exist ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: sane-utils 1.0.29-0ubuntu5.1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Sep 7 09:31:24 2020 InstallationDate: Installed on 2019-03-30 (526 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190318) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/zsh SourcePackage: sane-backends UpgradeStatus: Upgraded to focal on 2020-05-15 (115 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1894715/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1851250] Re: [snap] chromium-browser snap cannot upload files outside ~
This affects me too after upgrading from 18.04 LTS to 20.04 and I fint it COMPLETELY UNACCEPTABLE. The use of symlinks from /home to data on larger drives (which are shared between windows and linux systems, and not unix FS) is industry standard since over 30 years and this regression is atrocious. I will remove the snap and install the .DEB until it is resolved. My root disk is too small for the files i need to upload so a symlink to the storage drive which is permanently mounted in fstab under /datasjoe is necessary. The implication you have also broken access to removable media by default is likewise idiocy, any user is right in assuming he/she can acess theyir usb drves anywhere in their desktop system. Think again. please? I dont want to have to give up ubuntu after 11 years of daily driving it. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1851250 Title: [snap] chromium-browser snap cannot upload files outside ~ Status in chromium-browser package in Ubuntu: Invalid Bug description: After upgrading from 19.04 to 19.10, my Chromium package was converted to a snap. After figuring out how to manually reconnect the password manager, and figuring out how to apply CHROMIUM_FLAGS that used to live in /etc/chromium-browser/default, and noticing that GMail is no longer able to play a sound when a call comes in, now I see that I am unable to upload files from anywhere except my home directory! Connecting chromium:removable-media as in https://bugs.launchpad.net/ubuntu/+source/chromium- browser/+bug/1832711 does not help with anything else. Is there some way to let the file upload dialog work on any file my user account has access to? Or run this snap in --classic mode? If not, this seems like a critical limitation, as I need this multiple times a day. Switching to Chrome or Firefox cannot be the only workaround for this, surely? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1851250/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1282294] Re: "Cannot open pixbuf loader module file"
Same here when upgrading 16.04 LTS to 18.04 The bug is six years old ? We should send it to preschool =) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdk-pixbuf in Ubuntu. https://bugs.launchpad.net/bugs/1282294 Title: "Cannot open pixbuf loader module file" Status in gdk-pixbuf package in Ubuntu: Triaged Status in gdk-pixbuf package in Debian: New Bug description: While doing testing on trusty, I keep finding errors like the following in my apt-get -u dist-upgrade output: Preparing to unpack .../indicator-printers_0.1.7+14.04.20140213-0ubuntu1_amd64.deb ... Unpacking indicator-printers (0.1.7+14.04.20140213-0ubuntu1) over (0.1.7daily13.03.01-0ubuntu1) ... (gtk-update-icon-cache-3.0:29671): GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/usr/lib/x86_64-linux-gnu/gdk- pixbuf-2.0/2.10.0/loaders.cache': No such file or directory This likely means that your installation is broken. Try running the command gdk-pixbuf-query-loaders > /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache to make things work again for the time being. (gtk-update-icon-cache-3.0:29672): GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/usr/lib/x86_64-linux-gnu/gdk- pixbuf-2.0/2.10.0/loaders.cache': No such file or directory This likely means that your installation is broken. Try running the command gdk-pixbuf-query-loaders > /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache to make things work again for the time being. ... Processing triggers for hicolor-icon-theme (0.13-1) ... (gtk-update-icon-cache-3.0:32198): GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/usr/lib/x86_64-linux-gnu/gdk- pixbuf-2.0/2.10.0/loaders.cache': No such file or directory This likely means that your installation is broken. Try running the command gdk-pixbuf-query-loaders > /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache to make things work again for the time being. These errors make it difficult to look for errors that I might have introduced in my own packages and if they persist in our final product will make users wonder what is broken and why it is broken. sarnold@sec-trusty-amd64:~$ lsb_release -rd Description: Ubuntu Trusty Tahr (development branch) Release: 14.04 sarnold@sec-trusty-amd64:~$ dpkg -S gdk-pixbuf-query-loaders libgdk-pixbuf2.0-0:amd64: /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/gdk-pixbuf-query-loaders sarnold@sec-trusty-amd64:~$ apt-cache policy libgdk-pixbuf2.0-0 libgdk-pixbuf2.0-0: Installed: 2.30.5-0ubuntu1 Candidate: 2.30.5-0ubuntu1 Version table: *** 2.30.5-0ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status sarnold@sec-trusty-amd64:~$ dpkg -S /usr/bin/gtk-update-icon-cache-3.0 libgtk-3-bin: /usr/bin/gtk-update-icon-cache-3.0 sarnold@sec-trusty-amd64:~$ apt-cache policy libgtk-3-bin libgtk-3-bin: Installed: 3.10.7-0ubuntu2 Candidate: 3.10.7-0ubuntu2 Version table: *** 3.10.7-0ubuntu2 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status sarnold@sec-trusty-amd64:~$ Thanks ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libgtk-3-bin 3.10.7-0ubuntu2 ProcVersionSignature: User Name 3.13.0-5.20-generic 3.13.0 Uname: Linux 3.13.0-5-generic x86_64 ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 Date: Wed Feb 19 14:38:47 2014 InstallationDate: Installed on 2014-01-09 (41 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140108) ProcEnviron: TERM=rxvt-unicode PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gtk+3.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1282294/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
