[Desktop-packages] [Bug 1779552] Re: [regression] package gnome-shell ... failed to install/upgrade: dependency problems - leave unconfigured. [... depends on python3 however: Package python3 is not c
I'm not sure this many people would manually install hplip things, or would they? ** Summary changed: - [regression] package gnome-shell ... failed to install/upgrade: dependency problems - leave unconfigured. [... depends on python3 however: Package python3 is not configured yet.] + [regression] package gnome-shell ... failed to install/upgrade: dependency problems - leave unconfigured. [... depends on python3 however: Package python3 is not configured yet.] preceded by [E: py3compile:183: cannot create directory /usr/share/hplip/ui5/__pycache__: FileNotFoundError(2, 'No such file or directory')] ** Also affects: hplip (Ubuntu) Importance: Undecided Status: New ** Changed in: hplip (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1779552 Title: [regression] package gnome-shell ... failed to install/upgrade: dependency problems - leave unconfigured. [... depends on python3 however: Package python3 is not configured yet.] preceded by [E: py3compile:183: cannot create directory /usr/share/hplip/ui5/__pycache__: FileNotFoundError(2, 'No such file or directory')] Status in gnome-shell package in Ubuntu: Invalid Status in hplip package in Ubuntu: Invalid Bug description: i think main problem is python3. i have found bug here. but i didnt resolve it yet. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.2-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 Uname: Linux 4.15.0-24-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Sun Jul 1 15:56:18 2018 DisplayManager: gdm3 ErrorMessage: проблемы зависимостей — оставляем не настроенным GsettingsChanges: InstallationDate: Installed on 2018-06-02 (28 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.2 SourcePackage: gnome-shell Title: package gnome-shell 3.28.2-0ubuntu0.18.04.1 failed to install/upgrade: проблемы зависимостей — оставляем не настроенным UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1779552/+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 1807330] Re: package gnome-shell 3.28.3-0ubuntu0.18.04.3 failed to install/upgrade: problèmes de dépendances - laissé non configuré
*** This bug is a duplicate of bug 1779552 *** https://bugs.launchpad.net/bugs/1779552 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1779552, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1779552 [regression] package gnome-shell ... failed to install/upgrade: dependency problems - leave unconfigured. [... depends on python3 however: Package python3 is not configured yet.] -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1807330 Title: package gnome-shell 3.28.3-0ubuntu0.18.04.3 failed to install/upgrade: problèmes de dépendances - laissé non configuré Status in gnome-shell package in Ubuntu: New Bug description: God Morning everyone, I think I have got some problem with the update on Ubuntu. Since I begin to use Ubuntu, there is an error on each update. Description: Ubuntu 18.04.1 LTS Release: 18.04 kala@KaLaPC:~$ apt-cache policy pkgname N: Impossible de trouver le paquet pkgname I apologies for the way I use the report (it may cause you loss of time) but I'm just a beginner with Ubuntu. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.3-0ubuntu0.18.04.3 ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18 Uname: Linux 4.15.0-39-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 AptOrdering: libraw16:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Fri Dec 7 06:24:08 2018 DisplayManager: gdm3 DpkgHistoryLog: Start-Date: 2018-12-07 06:23:41 Commandline: /usr/bin/unattended-upgrade Upgrade: libraw16:amd64 (0.18.8-1ubuntu0.1, 0.18.8-1ubuntu0.2) ErrorMessage: problèmes de dépendances - laissé non configuré GsettingsChanges: InstallationDate: Installed on 2018-09-23 (74 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.6 SourcePackage: gnome-shell Title: package gnome-shell 3.28.3-0ubuntu0.18.04.3 failed to install/upgrade: problèmes de dépendances - laissé non configuré UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1807330/+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 1733002] Re: Google Online Account Two Factor with hardware key fails immediately
** Changed in: gnome-online-accounts Status: Confirmed => Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1733002 Title: Google Online Account Two Factor with hardware key fails immediately Status in gnome-online-accounts: Unknown Status in gnome-online-accounts package in Ubuntu: New Bug description: The hardware key authentication two factor fails immediately with a web based retry dialogue when connecting a Google account to the online accounts in settings using a hardware key second factor. Steps to reproduce: 1. Set Google Account to default to a hardware security key like a Yubikey or other FIDO standard key after having two factor authentication enabled on your Google Account. 2. Open Online accounts 3. Add a Google Account 4. Enter google email address 5. Enter google password 6. (this is the login flow of two factor, if default is the hardware key the error should appear). Work around: Choose use another method to authenticate: enter the authentication code and you will proceed. Expectations were: The ability to use the hardware key to authenticate as the second factor. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-control-center 1:3.26.1-0ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-16.19-lowlatency 4.13.4 Uname: Linux 4.13.0-16-lowlatency x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Nov 17 16:01:11 2017 EcryptfsInUse: Yes ExecutablePath: /usr/bin/gnome-control-center ProcEnviron: XDG_RUNTIME_DIR= SHELL=/bin/bash PATH=(custom, user) LANG=en_US.UTF-8 SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-online-accounts/+bug/1733002/+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 1807330] [NEW] package gnome-shell 3.28.3-0ubuntu0.18.04.3 failed to install/upgrade: problèmes de dépendances - laissé non configuré
Public bug reported: God Morning everyone, I think I have got some problem with the update on Ubuntu. Since I begin to use Ubuntu, there is an error on each update. Description:Ubuntu 18.04.1 LTS Release:18.04 kala@KaLaPC:~$ apt-cache policy pkgname N: Impossible de trouver le paquet pkgname I apologies for the way I use the report (it may cause you loss of time) but I'm just a beginner with Ubuntu. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.3-0ubuntu0.18.04.3 ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18 Uname: Linux 4.15.0-39-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 AptOrdering: libraw16:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Fri Dec 7 06:24:08 2018 DisplayManager: gdm3 DpkgHistoryLog: Start-Date: 2018-12-07 06:23:41 Commandline: /usr/bin/unattended-upgrade Upgrade: libraw16:amd64 (0.18.8-1ubuntu0.1, 0.18.8-1ubuntu0.2) ErrorMessage: problèmes de dépendances - laissé non configuré GsettingsChanges: InstallationDate: Installed on 2018-09-23 (74 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.6 SourcePackage: gnome-shell Title: package gnome-shell 3.28.3-0ubuntu0.18.04.3 failed to install/upgrade: problèmes de dépendances - laissé non configuré UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1807330 Title: package gnome-shell 3.28.3-0ubuntu0.18.04.3 failed to install/upgrade: problèmes de dépendances - laissé non configuré Status in gnome-shell package in Ubuntu: New Bug description: God Morning everyone, I think I have got some problem with the update on Ubuntu. Since I begin to use Ubuntu, there is an error on each update. Description: Ubuntu 18.04.1 LTS Release: 18.04 kala@KaLaPC:~$ apt-cache policy pkgname N: Impossible de trouver le paquet pkgname I apologies for the way I use the report (it may cause you loss of time) but I'm just a beginner with Ubuntu. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.3-0ubuntu0.18.04.3 ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18 Uname: Linux 4.15.0-39-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 AptOrdering: libraw16:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Fri Dec 7 06:24:08 2018 DisplayManager: gdm3 DpkgHistoryLog: Start-Date: 2018-12-07 06:23:41 Commandline: /usr/bin/unattended-upgrade Upgrade: libraw16:amd64 (0.18.8-1ubuntu0.1, 0.18.8-1ubuntu0.2) ErrorMessage: problèmes de dépendances - laissé non configuré GsettingsChanges: InstallationDate: Installed on 2018-09-23 (74 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.6 SourcePackage: gnome-shell Title: package gnome-shell 3.28.3-0ubuntu0.18.04.3 failed to install/upgrade: problèmes de dépendances - laissé non configuré UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1807330/+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 1767096] Re: Random Xorg crashes
[Expired for xorg-server (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg-server (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1767096 Title: Random Xorg crashes Status in xorg-server package in Ubuntu: Expired Bug description: Xorg crashes randomly: environment just freezes for a second and I'm getting login screen. ProblemType: Bug DistroRelease: elementary 0.4.1 Package: xorg 1:7.7+13ubuntu3 [origin: Ubuntu] ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-39-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 CurrentDesktop: Pantheon Date: Thu Apr 26 12:57:22 2018 InstallationDate: Installed on 2018-03-01 (55 days ago) InstallationMedia: elementary OS 0.4.1 "Loki" - Stable amd64 (20180214) SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1767096/+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 1698693] Re: cups-pdf blocked by apparmor
[Expired for cups (Ubuntu) because there has been no activity for 60
days.]
** Changed in: cups (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1698693
Title:
cups-pdf blocked by apparmor
Status in cups package in Ubuntu:
Expired
Bug description:
cups-pdf cannot create the ~/PDF directory if it does not exist and
fails with no indication to the user.
It should however be pointed out that cups-pdf allows the system
administrator to change it's output directory by changing the Out key
in /etc/cups/cups-pdf.conf. As such apparmor will get in the way again
if the admin changes the Out key to some other location outside of the
${HOME}/PDF directory. (It's default setting.)
cups-pdf also does not have an #include for using local overrides in
it's apparmor config. As such any fixes that the local admin makes
will be overwritten by the next update to the cups package, breaking
it again.
Description: Ubuntu 16.04.2 LTS
Release: 16.04
printer-driver-cups-pdf:
Installed: 2.6.1-21
Candidate: 2.6.1-21
Version table:
*** 2.6.1-21 500
500 http://us.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
100 /var/lib/dpkg/status
cups:
Installed: 2.1.3-4
Candidate: 2.1.3-4
Version table:
*** 2.1.3-4 500
500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
100 /var/lib/dpkg/status
What happened:
cups-pdf when installed for the first time fails with the following apparmor
denials:
[ 6117.686934] audit: type=1400 audit(1497816878.998:1079): apparmor="DENIED"
operation="file_inherit" profile="/usr/lib/cups/backend/cups-pdf" pid=6015
comm="cups-pdf" family="unix" sock_type="stream" protocol=0
requested_mask="send receive" denied_mask="send receive" addr=none
peer_addr=none peer="/usr/sbin/cupsd"
[ 6117.686948] audit: type=1400 audit(1497816878.998:1080): apparmor="DENIED"
operation="file_inherit" profile="/usr/sbin/cupsd" pid=6015 comm="cups-pdf"
family="unix" sock_type="stream" protocol=0 requested_mask="send receive"
denied_mask="send receive" addr=none peer_addr=none
peer="/usr/lib/cups/backend/cups-pdf"
[ 6117.688671] audit: type=1400 audit(1497816879.002:1081): apparmor="DENIED"
operation="open" profile="/usr/lib/cups/backend/cups-pdf"
name="/var/lib/sss/mc/initgroups" pid=6015 comm="cups-pdf" requested_mask="r"
denied_mask="r" fsuid=0 ouid=0
[ 6117.688688] audit: type=1400 audit(1497816879.002:1082): apparmor="DENIED"
operation="open" profile="/usr/lib/cups/backend/cups-pdf"
name="/var/lib/sss/mc/initgroups" pid=6015 comm="cups-pdf" requested_mask="r"
denied_mask="r" fsuid=0 ouid=0
[ 6117.689719] audit: type=1400 audit(1497816879.002:1083): apparmor="DENIED"
operation="mkdir" profile="/usr/lib/cups/backend/cups-pdf"
name="/home/CODENET.LOCAL/codebase/PDF/" pid=6015 comm="cups-pdf"
requested_mask="c" denied_mask="c" fsuid=0 ouid=0
What I expected to happen:
cups-pdf creates the pdf file it was supposed to.
As a workaround, I set cups-pdf to use the third-party settings from the cups
profile, then it worked as expected.
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
CupsErrorLog: Error: [Errno 13] Permission denied: '/var/log/cups/error_log'
CurrentDesktop: MATE
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2017-11-24 (281 days ago)
InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Release amd64
(20171018)
Lpstat:
device for EPSONET-4550:
ipp://call.codenet.local:631/printers/EPSON_ET-4550_Series
device for PDF: cups-pdf:/
MachineType: Gigabyte Technology Co., Ltd. A320M-S2H
NonfreeKernelModules: nvidia_modeset nvidia
Package: cups 2.2.7-1ubuntu2.1
PackageArchitecture: amd64
Papersize: letter
PpdFiles: Error: command ['fgrep', '-H', '*NickName',
'/etc/cups/ppd/PDF.ppd'] failed with exit code 2: grep: /etc/cups/ppd/PDF.ppd:
Permission denied
ProcCmdline: BOOT_IMAGE=/vmlinuz-4.15.0-33-generic
root=UUID=b719b98c-6702-467b-bad1-38f7ecaed813 ro video=vesafb:off vga=normal
quiet splash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-33-generic
root=UUID=b719b98c-6702-467b-bad1-38f7ecaed813 ro video=vesafb:off vga=normal
quiet splash
ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
Tags: bionic apparmor apparmor apparmor apparmor
Uname: Linux 4.15.0-33-generic x86_64
UpgradeStatus: Upgraded to bionic on 2018-05-20 (104 days ago)
UserGroups:
_MarkForUpload: True
dmi.bios.date: 02/08/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F21
dmi.board.asset.tag: Default string
dmi.board.name: A320M-S2H-CF
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendo
[Desktop-packages] [Bug 1178043] Re: Print subsystem unusable on large network
Still a problem, although not quite as bad as before (I think someone may have reconfigured our switches to pass rather less zeroconf etc. traffic). Still ridiculous to auto-add autodetected devices. Have confirmed that if I manually remove them the damn things reappear. ** Changed in: system-config-printer (Ubuntu) Status: Expired => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to system-config-printer in Ubuntu. https://bugs.launchpad.net/bugs/1178043 Title: Print subsystem unusable on large network Status in system-config-printer package in Ubuntu: New Bug description: Automagically gathering all available zeroconf/avahi/whatever-its- called-this-week printers and presenting them as configured printers renders the print subsystem almost entirely unusable on a large network (>30k hosts on a LAN in this case). Offering them when I want to add a printer is passable, but presenting them as configured printers by default is ridiculous. It appears I have to remove them one-by-one (ain't gonna happen), and it's not even clear that that will be in any way permanent. We're not all on nice cosy little home networks. At least make it optional, please. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: system-config-printer-gnome 1.3.12+20130308-0ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 CupsErrorLog: W [09/May/2013:08:03:00 +1200] Please move "SystemGroup lpadmin" on line 16 of /etc/cups/cupsd.conf to the /etc/cups/cups-files.conf file; this will become an error in a future release. W [09/May/2013:08:03:00 +1200] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id 'facmed-laser-it-Gray..' already exists W [09/May/2013:08:03:00 +1200] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id 'facmed-laser-it-RGB..' already exists W [09/May/2013:08:03:00 +1200] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id 'facmed-laser-it-ps-Gray..' already exists E [09/May/2013:12:54:50 +1200] [cups-driverd] Bad driver information file "/usr/share/cups/drv/cupsfilters.drv"! Date: Thu May 9 13:01:08 2013 InstallationDate: Installed on 2013-03-15 (54 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MachineType: Apple Inc. Macmini6,2 MarkForUpload: True PackageArchitecture: all Papersize: a4 PpdFiles: facmed-laser-it: HP LaserJet 4250 pcl3, hpcups 3.13.3 facmed-laser-it-ps: HP LaserJet 4250 Postscript (recommended) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic root=UUID=77e44b8f-c46d-44ba-a999-d6962993dda8 ro quiet splash vt.handoff=7 SourcePackage: system-config-printer UpgradeStatus: Upgraded to raring on 2013-05-03 (5 days ago) dmi.bios.date: 11/16/2012 dmi.bios.vendor: Apple Inc. dmi.bios.version: MM61.88Z.0106.B03.1211161202 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-F65AE981FFA204ED dmi.board.vendor: Apple Inc. dmi.board.version: Macmini6,2 dmi.chassis.type: 16 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F65AE981FFA204ED dmi.modalias: dmi:bvnAppleInc.:bvrMM61.88Z.0106.B03.1211161202:bd11/16/2012:svnAppleInc.:pnMacmini6,2:pvr1.0:rvnAppleInc.:rnMac-F65AE981FFA204ED:rvrMacmini6,2:cvnAppleInc.:ct16:cvrMac-F65AE981FFA204ED: dmi.product.name: Macmini6,2 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CupsErrorLog: E [07/Dec/2018:13:42:38 +1300] [cups-deviced] PID 15115 (gutenprint52+usb) stopped with status 1! CurrentDesktop: GNOME DistroRelease: Ubuntu 18.04 EcryptfsInUse: Yes InstallationDate: Installed on 2017-01-09 (696 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) Lpstat: device for ljps: ipp://facmed-laser-it/ipp MachineType: Apple Inc. Macmini6,2 NonfreeKernelModules: wl Package: system-config-printer 1.5.11-1ubuntu2 PackageArchitecture: all Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/ljps.ppd'] failed with exit code 2: grep: /etc/cups/ppd/ljps.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=305f7448-19cc-4832-9e07-b21d2b7e5e39 ro 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: Upgraded to bionic on 2018-05-06 (214 days ago) UserGroups: adm cdrom dip docker libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/20/2016 dmi.bios.vendor: Apple Inc. dmi.bios.version: MM61.88Z.0106.B0B.1610201654 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-F65AE981FFA204ED dmi
[Desktop-packages] [Bug 1805247] Re: Onscreen Keyboard in Xorg cannot be summoned by swiping up on the screen
*** This bug is a duplicate of bug 1807276 *** https://bugs.launchpad.net/bugs/1807276 Moved to bug 1807276. ** This bug has been marked a duplicate of bug 1807276 Cannot swipe up from bottom of screen to get Onscreen Keyboard in Xorg -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1805247 Title: Onscreen Keyboard in Xorg cannot be summoned by swiping up on the screen Status in gnome-shell package in Ubuntu: Invalid Bug description: -- Ubuntu 18.04 LTS -- gnome-shell 3.28.1-0ubuntu2 When user is logged in using Wayland, swipe-up gesture cannot be used to summon the OSK. Problem is non-existent on Xorg. This has been reproduced on multiple devices, leaving the user unable to use the OSK in many situations. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1805247/+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 1807276] Re: Cannot swipe up from bottom of screen to get Onscreen Keyboard in Xorg
** Tags added: bionic cosmic osk -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1807276 Title: Cannot swipe up from bottom of screen to get Onscreen Keyboard in Xorg Status in gnome-shell package in Ubuntu: New Bug description: Ubuntu 18.10 / GNOME Shell 3.30.1 ALSO Ubuntu 18.04 LTS / GNOME Shell 3.28.1 Steps to reproduce on our end: - Login (Xorg as default) - Attempt to swipe up with finger from below screen RESULT: It draws a thin vertical (desktop) selection box, but no OSK - Logout - Log back in, after first hitting 'gear' button to select 'Ubuntu on Wayland' - ps -e | grep Xwayland #shows 'Xwayland' process is running - Repeat swipe up with finger from below screen RESULT: OSK shows up as expected This has been verified both in 1920x1080 as well as 3840x2160 resolutions (also with various scaling options selected) Issue is also logged upstream: https://gitlab.gnome.org/GNOME/gnome- shell/issues/839 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1807276/+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 1807056] Re: Occasional Keyboard freeze
Oh, actually this sounds like it might be related to USB or other kernel problems. Next time the problem happens, reboot to recover the machine and then run this command to collect the log of the previous (frozen) boot: journalctl -b-1 > prevboot.txt and attach the file 'prevboot.txt' here. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1807056 Title: Occasional Keyboard freeze Status in gnome-shell package in Ubuntu: Incomplete Bug description: I am using 18.04 and sometimes, whatever I type does not work. It is as if there is no keyboard connected while I have my laptop keyboard and an external keyboard connected to the machine. I even enabled On Screen Keyboard and tried to type through it. Same result. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.3-0ubuntu0.18.04.3 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: communitheme:ubuntu:GNOME Date: Thu Dec 6 05:41:04 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-11-29 (6 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1807056/+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 1807056] Re: Occasional Keyboard freeze
Yes if you're using Xorg (the default "Ubuntu" session) then mouse cursor movement is done by the Xorg process so it will keep moving even if gnome-shell was frozen. I meant that you should run 'top' before the problem happens and leave it running so you can watch that window. When the problem happens is it only keyboard input that freezes or window contents too? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1807056 Title: Occasional Keyboard freeze Status in gnome-shell package in Ubuntu: Incomplete Bug description: I am using 18.04 and sometimes, whatever I type does not work. It is as if there is no keyboard connected while I have my laptop keyboard and an external keyboard connected to the machine. I even enabled On Screen Keyboard and tried to type through it. Same result. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.3-0ubuntu0.18.04.3 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: communitheme:ubuntu:GNOME Date: Thu Dec 6 05:41:04 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-11-29 (6 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1807056/+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 1806165] Re: [nvidia] Ubuntu 18.10 I get logged off on resume from suspend - Unregistered Authentication Agent for unix-session
Thanks Scott. This still sounds like an Nvidia-specific crash. Please try following all the steps detailed in comment #2. ** Changed in: gdm3 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1806165 Title: [nvidia] Ubuntu 18.10 I get logged off on resume from suspend - Unregistered Authentication Agent for unix-session Status in gdm3 package in Ubuntu: Incomplete Status in gnome-shell package in Ubuntu: Incomplete Bug description: This is not a problem using only built in laptop screen however when I attach an external monitor and choose Setting->Display->Single Display then choose the external monitor to be the only active screen -> then when I suspend upon resume the external monitor lights up showing the password prompt which is good however after entering password all my launched applications are no longer running ... according to /var/log/auth.log I get logged out during this suspend/resume - this issue is repeatable This is only a problem when using nvidia drivers installed using Software & Updates -> Additional Drivers -> nvidia 390 , with nouveau its OK ... its a fresh 18.10 install not an upgrade Here is a clip from /var/log/auth.log look closely at messages just after `Lid opened` - Nov 30 21:17:01 nuem CRON[17437]: pam_unix(cron:session): session opened for user root by (uid=0) Nov 30 21:17:01 nuem CRON[17437]: pam_unix(cron:session): session closed for user root Nov 30 21:20:18 nuem gnome-keyring-daemon[3057]: asked to register item /org/freedesktop/secrets/collection/login/863, but it's already registered Nov 30 21:20:19 nuem gnome-keyring-daemon[3057]: asked to register item /org/freedesktop/secrets/collection/login/862, but it's already registered Nov 30 21:40:36 nuem gnome-keyring-daemon[3057]: asked to register item /org/freedesktop/secrets/collection/login/1, but it's already registered Nov 30 21:40:39 nuem gnome-keyring-daemon[3057]: message repeated 2 times: [ asked to register item /org/freedesktop/secrets/collection/login/1, but it's already registered] Nov 30 21:49:25 nuem systemd-logind[523]: Lid closed. Nov 30 21:49:29 nuem systemd-logind[523]: Lid opened. Nov 30 21:49:51 nuem systemd-logind[523]: Operation 'sleep' finished. Nov 30 21:49:52 nuem polkitd(authority=local): Unregistered Authentication Agent for unix-session:2 (system bus name :1.376, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) (disconnected from bus) Nov 30 21:49:52 nuem gdm-password]: pam_unix(gdm-password:session): session closed for user upha Nov 30 21:49:52 nuem dbus-daemon[507]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.2100" (uid=1000 pid=31115 comm="/usr/bin/pulseaudio --daemonize=no " label="unconfined") interface="org.freedesktop.DBus.ObjectManager" member="GetManagedObjects" error name="(unset)" requested_reply="0" destination="org.bluez" (bus) Nov 30 21:49:52 nuem systemd-logind[523]: Session 2 logged out. Waiting for processes to exit. Nov 30 21:49:53 nuem gdm-launch-environment]: pam_unix(gdm-launch-environment:session): session opened for user gdm by (uid=0) Nov 30 21:49:53 nuem systemd-logind[523]: New session c2 of user gdm. Nov 30 21:49:53 nuem systemd: pam_unix(systemd-user:session): session opened for user gdm by (uid=0) Nov 30 21:49:55 nuem systemd-logind[523]: Removed session 2. Nov 30 21:49:56 nuem systemd: pam_unix(systemd-user:session): session closed for user upha Nov 30 21:49:57 nuem polkitd(authority=local): Registered Authentication Agent for unix-session:c2 (system bus name :1.2108 [/usr/bin/gnome-shell], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) Nov 30 21:50:07 nuem gdm-password]: pam_unix(gdm-password:session): session opened for user upha by (uid=0) Nov 30 21:50:07 nuem systemd-logind[523]: New session 37 of user upha. Nov 30 21:50:07 nuem systemd: pam_unix(systemd-user:session): session opened for user upha by (uid=0) Nov 30 21:50:17 nuem polkitd(authority=local): Registered Authentication Agent for unix-session:37 (system bus name :1.2405 [/usr/bin/gnome-shell], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) Nov 30 21:50:19 nuem systemd-logind[523]: Session c2 logged out. Waiting for processes to exit. Nov 30 21:50:19 nuem polkitd(authority=local): Unregistered Authentication Agent for unix-session:c2 (system bus name :1.2108, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) (disconnected from bus) Nov 30 21:50:19 nuem systemd-logind[523]: Removed session c2. Nov 30 21:52:50 nuem systemd-logind[523]: Operation 'sleep' finished. Nov 30 21:52:59 nuem gdm-password]: gkr-pam: unlocked login keyring No
[Desktop-packages] [Bug 1805715] Re: password exposed in application windows
Oh, it is gdm3. But being Ubuntu 16.04 an older version than what we support in 18.04 onward. So I would expect extra bugs in 16.04 that we haven't seen before. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1805715 Title: password exposed in application windows Status in gnome-screensaver package in Ubuntu: Incomplete Bug description: Plain text Linux user id password exposed in calculator input box. The first character of the password is dropped. This is reproducible as follows: 0. the calculator window has the desktop focus and the input box is empty. 1. allow screen saver to kick in or invoke it manually with ctrl+alt+l 2. type in password 3. hit enter 4. view password in input box of calculator (less first character) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-calculator 1:3.18.3-0ubuntu1.16.04.1 ProcVersionSignature: Ubuntu 4.15.0-39.42~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-39-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Nov 28 16:37:44 2018 ExecutablePath: /usr/bin/gnome-calculator InstallationDate: Installed on 2018-11-14 (13 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) ProcEnviron: PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-calculator UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1805715/+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 1805715] Re: password exposed in calculator input box
No I haven't. Is this really about an animated gnome-screensaver or just the screen lock? If the latter it might be better to assign this to 'lightdm'. ** Description changed: Plain text Linux user id password exposed in calculator input box. The first character of the password is dropped. This is reproducible as follows: + 0. the calculator window has the desktop focus and the input box is empty. 1. allow screen saver to kick in or invoke it manually with ctrl+alt+l 2. type in password 3. hit enter 4. view password in input box of calculator (less first character) - - Note the calculator window has the desktop focus and the input box is - empty. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-calculator 1:3.18.3-0ubuntu1.16.04.1 ProcVersionSignature: Ubuntu 4.15.0-39.42~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-39-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Nov 28 16:37:44 2018 ExecutablePath: /usr/bin/gnome-calculator InstallationDate: Installed on 2018-11-14 (13 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) ProcEnviron: - PATH=(custom, user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + PATH=(custom, user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash SourcePackage: gnome-calculator UpgradeStatus: No upgrade log present (probably fresh install) ** Summary changed: - password exposed in calculator input box + password exposed in application windows -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1805715 Title: password exposed in application windows Status in gnome-screensaver package in Ubuntu: Incomplete Bug description: Plain text Linux user id password exposed in calculator input box. The first character of the password is dropped. This is reproducible as follows: 0. the calculator window has the desktop focus and the input box is empty. 1. allow screen saver to kick in or invoke it manually with ctrl+alt+l 2. type in password 3. hit enter 4. view password in input box of calculator (less first character) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-calculator 1:3.18.3-0ubuntu1.16.04.1 ProcVersionSignature: Ubuntu 4.15.0-39.42~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-39-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Nov 28 16:37:44 2018 ExecutablePath: /usr/bin/gnome-calculator InstallationDate: Installed on 2018-11-14 (13 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) ProcEnviron: PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-calculator UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1805715/+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 1805247] Re: Onscreen Keyboard in Xorg cannot be summoned by swiping up on the screen
I thought this bug report was fine aside from the above incorrect wording. Feel free to reopen it (change the Status value) if it's still a problem for you. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1805247 Title: Onscreen Keyboard in Xorg cannot be summoned by swiping up on the screen Status in gnome-shell package in Ubuntu: Invalid Bug description: -- Ubuntu 18.04 LTS -- gnome-shell 3.28.1-0ubuntu2 When user is logged in using Wayland, swipe-up gesture cannot be used to summon the OSK. Problem is non-existent on Xorg. This has been reproduced on multiple devices, leaving the user unable to use the OSK in many situations. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1805247/+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 1178043] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1178043/+attachment/5219843/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to system-config-printer in Ubuntu. https://bugs.launchpad.net/bugs/1178043 Title: Print subsystem unusable on large network Status in system-config-printer package in Ubuntu: Expired Bug description: Automagically gathering all available zeroconf/avahi/whatever-its- called-this-week printers and presenting them as configured printers renders the print subsystem almost entirely unusable on a large network (>30k hosts on a LAN in this case). Offering them when I want to add a printer is passable, but presenting them as configured printers by default is ridiculous. It appears I have to remove them one-by-one (ain't gonna happen), and it's not even clear that that will be in any way permanent. We're not all on nice cosy little home networks. At least make it optional, please. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: system-config-printer-gnome 1.3.12+20130308-0ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 CupsErrorLog: W [09/May/2013:08:03:00 +1200] Please move "SystemGroup lpadmin" on line 16 of /etc/cups/cupsd.conf to the /etc/cups/cups-files.conf file; this will become an error in a future release. W [09/May/2013:08:03:00 +1200] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id 'facmed-laser-it-Gray..' already exists W [09/May/2013:08:03:00 +1200] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id 'facmed-laser-it-RGB..' already exists W [09/May/2013:08:03:00 +1200] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id 'facmed-laser-it-ps-Gray..' already exists E [09/May/2013:12:54:50 +1200] [cups-driverd] Bad driver information file "/usr/share/cups/drv/cupsfilters.drv"! Date: Thu May 9 13:01:08 2013 InstallationDate: Installed on 2013-03-15 (54 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MachineType: Apple Inc. Macmini6,2 MarkForUpload: True PackageArchitecture: all Papersize: a4 PpdFiles: facmed-laser-it: HP LaserJet 4250 pcl3, hpcups 3.13.3 facmed-laser-it-ps: HP LaserJet 4250 Postscript (recommended) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic root=UUID=77e44b8f-c46d-44ba-a999-d6962993dda8 ro quiet splash vt.handoff=7 SourcePackage: system-config-printer UpgradeStatus: Upgraded to raring on 2013-05-03 (5 days ago) dmi.bios.date: 11/16/2012 dmi.bios.vendor: Apple Inc. dmi.bios.version: MM61.88Z.0106.B03.1211161202 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-F65AE981FFA204ED dmi.board.vendor: Apple Inc. dmi.board.version: Macmini6,2 dmi.chassis.type: 16 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F65AE981FFA204ED dmi.modalias: dmi:bvnAppleInc.:bvrMM61.88Z.0106.B03.1211161202:bd11/16/2012:svnAppleInc.:pnMacmini6,2:pvr1.0:rvnAppleInc.:rnMac-F65AE981FFA204ED:rvrMacmini6,2:cvnAppleInc.:ct16:cvrMac-F65AE981FFA204ED: dmi.product.name: Macmini6,2 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CupsErrorLog: E [07/Dec/2018:13:42:38 +1300] [cups-deviced] PID 15115 (gutenprint52+usb) stopped with status 1! CurrentDesktop: GNOME DistroRelease: Ubuntu 18.04 EcryptfsInUse: Yes InstallationDate: Installed on 2017-01-09 (696 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) Lpstat: device for ljps: ipp://facmed-laser-it/ipp MachineType: Apple Inc. Macmini6,2 NonfreeKernelModules: wl Package: system-config-printer 1.5.11-1ubuntu2 PackageArchitecture: all Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/ljps.ppd'] failed with exit code 2: grep: /etc/cups/ppd/ljps.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=305f7448-19cc-4832-9e07-b21d2b7e5e39 ro 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: Upgraded to bionic on 2018-05-06 (214 days ago) UserGroups: adm cdrom dip docker libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/20/2016 dmi.bios.vendor: Apple Inc. dmi.bios.version: MM61.88Z.0106.B0B.1610201654 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-F65AE981FFA204ED dmi.board.vendor: Apple Inc. dmi.board.version: Macmini6,2 dmi.chassis.type: 16 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F65AE981FFA204ED dmi.modalias: dmi:bvnAppleInc.:bvrMM61.
[Desktop-packages] [Bug 1178043] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1178043/+attachment/5219848/+files/UdevDb.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to system-config-printer in Ubuntu. https://bugs.launchpad.net/bugs/1178043 Title: Print subsystem unusable on large network Status in system-config-printer package in Ubuntu: Expired Bug description: Automagically gathering all available zeroconf/avahi/whatever-its- called-this-week printers and presenting them as configured printers renders the print subsystem almost entirely unusable on a large network (>30k hosts on a LAN in this case). Offering them when I want to add a printer is passable, but presenting them as configured printers by default is ridiculous. It appears I have to remove them one-by-one (ain't gonna happen), and it's not even clear that that will be in any way permanent. We're not all on nice cosy little home networks. At least make it optional, please. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: system-config-printer-gnome 1.3.12+20130308-0ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 CupsErrorLog: W [09/May/2013:08:03:00 +1200] Please move "SystemGroup lpadmin" on line 16 of /etc/cups/cupsd.conf to the /etc/cups/cups-files.conf file; this will become an error in a future release. W [09/May/2013:08:03:00 +1200] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id 'facmed-laser-it-Gray..' already exists W [09/May/2013:08:03:00 +1200] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id 'facmed-laser-it-RGB..' already exists W [09/May/2013:08:03:00 +1200] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id 'facmed-laser-it-ps-Gray..' already exists E [09/May/2013:12:54:50 +1200] [cups-driverd] Bad driver information file "/usr/share/cups/drv/cupsfilters.drv"! Date: Thu May 9 13:01:08 2013 InstallationDate: Installed on 2013-03-15 (54 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MachineType: Apple Inc. Macmini6,2 MarkForUpload: True PackageArchitecture: all Papersize: a4 PpdFiles: facmed-laser-it: HP LaserJet 4250 pcl3, hpcups 3.13.3 facmed-laser-it-ps: HP LaserJet 4250 Postscript (recommended) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic root=UUID=77e44b8f-c46d-44ba-a999-d6962993dda8 ro quiet splash vt.handoff=7 SourcePackage: system-config-printer UpgradeStatus: Upgraded to raring on 2013-05-03 (5 days ago) dmi.bios.date: 11/16/2012 dmi.bios.vendor: Apple Inc. dmi.bios.version: MM61.88Z.0106.B03.1211161202 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-F65AE981FFA204ED dmi.board.vendor: Apple Inc. dmi.board.version: Macmini6,2 dmi.chassis.type: 16 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F65AE981FFA204ED dmi.modalias: dmi:bvnAppleInc.:bvrMM61.88Z.0106.B03.1211161202:bd11/16/2012:svnAppleInc.:pnMacmini6,2:pvr1.0:rvnAppleInc.:rnMac-F65AE981FFA204ED:rvrMacmini6,2:cvnAppleInc.:ct16:cvrMac-F65AE981FFA204ED: dmi.product.name: Macmini6,2 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CupsErrorLog: E [07/Dec/2018:13:42:38 +1300] [cups-deviced] PID 15115 (gutenprint52+usb) stopped with status 1! CurrentDesktop: GNOME DistroRelease: Ubuntu 18.04 EcryptfsInUse: Yes InstallationDate: Installed on 2017-01-09 (696 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) Lpstat: device for ljps: ipp://facmed-laser-it/ipp MachineType: Apple Inc. Macmini6,2 NonfreeKernelModules: wl Package: system-config-printer 1.5.11-1ubuntu2 PackageArchitecture: all Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/ljps.ppd'] failed with exit code 2: grep: /etc/cups/ppd/ljps.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=305f7448-19cc-4832-9e07-b21d2b7e5e39 ro 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: Upgraded to bionic on 2018-05-06 (214 days ago) UserGroups: adm cdrom dip docker libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/20/2016 dmi.bios.vendor: Apple Inc. dmi.bios.version: MM61.88Z.0106.B0B.1610201654 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-F65AE981FFA204ED dmi.board.vendor: Apple Inc. dmi.board.version: Macmini6,2 dmi.chassis.type: 16 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F65AE981FFA204ED dmi.modalias: dmi:bvnAppleInc.:bvrMM61.88Z.0106.B0
[Desktop-packages] [Bug 1178043] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1178043/+attachment/5219847/+files/ProcModules.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to system-config-printer in Ubuntu. https://bugs.launchpad.net/bugs/1178043 Title: Print subsystem unusable on large network Status in system-config-printer package in Ubuntu: Expired Bug description: Automagically gathering all available zeroconf/avahi/whatever-its- called-this-week printers and presenting them as configured printers renders the print subsystem almost entirely unusable on a large network (>30k hosts on a LAN in this case). Offering them when I want to add a printer is passable, but presenting them as configured printers by default is ridiculous. It appears I have to remove them one-by-one (ain't gonna happen), and it's not even clear that that will be in any way permanent. We're not all on nice cosy little home networks. At least make it optional, please. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: system-config-printer-gnome 1.3.12+20130308-0ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 CupsErrorLog: W [09/May/2013:08:03:00 +1200] Please move "SystemGroup lpadmin" on line 16 of /etc/cups/cupsd.conf to the /etc/cups/cups-files.conf file; this will become an error in a future release. W [09/May/2013:08:03:00 +1200] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id 'facmed-laser-it-Gray..' already exists W [09/May/2013:08:03:00 +1200] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id 'facmed-laser-it-RGB..' already exists W [09/May/2013:08:03:00 +1200] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id 'facmed-laser-it-ps-Gray..' already exists E [09/May/2013:12:54:50 +1200] [cups-driverd] Bad driver information file "/usr/share/cups/drv/cupsfilters.drv"! Date: Thu May 9 13:01:08 2013 InstallationDate: Installed on 2013-03-15 (54 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MachineType: Apple Inc. Macmini6,2 MarkForUpload: True PackageArchitecture: all Papersize: a4 PpdFiles: facmed-laser-it: HP LaserJet 4250 pcl3, hpcups 3.13.3 facmed-laser-it-ps: HP LaserJet 4250 Postscript (recommended) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic root=UUID=77e44b8f-c46d-44ba-a999-d6962993dda8 ro quiet splash vt.handoff=7 SourcePackage: system-config-printer UpgradeStatus: Upgraded to raring on 2013-05-03 (5 days ago) dmi.bios.date: 11/16/2012 dmi.bios.vendor: Apple Inc. dmi.bios.version: MM61.88Z.0106.B03.1211161202 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-F65AE981FFA204ED dmi.board.vendor: Apple Inc. dmi.board.version: Macmini6,2 dmi.chassis.type: 16 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F65AE981FFA204ED dmi.modalias: dmi:bvnAppleInc.:bvrMM61.88Z.0106.B03.1211161202:bd11/16/2012:svnAppleInc.:pnMacmini6,2:pvr1.0:rvnAppleInc.:rnMac-F65AE981FFA204ED:rvrMacmini6,2:cvnAppleInc.:ct16:cvrMac-F65AE981FFA204ED: dmi.product.name: Macmini6,2 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CupsErrorLog: E [07/Dec/2018:13:42:38 +1300] [cups-deviced] PID 15115 (gutenprint52+usb) stopped with status 1! CurrentDesktop: GNOME DistroRelease: Ubuntu 18.04 EcryptfsInUse: Yes InstallationDate: Installed on 2017-01-09 (696 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) Lpstat: device for ljps: ipp://facmed-laser-it/ipp MachineType: Apple Inc. Macmini6,2 NonfreeKernelModules: wl Package: system-config-printer 1.5.11-1ubuntu2 PackageArchitecture: all Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/ljps.ppd'] failed with exit code 2: grep: /etc/cups/ppd/ljps.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=305f7448-19cc-4832-9e07-b21d2b7e5e39 ro 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: Upgraded to bionic on 2018-05-06 (214 days ago) UserGroups: adm cdrom dip docker libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/20/2016 dmi.bios.vendor: Apple Inc. dmi.bios.version: MM61.88Z.0106.B0B.1610201654 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-F65AE981FFA204ED dmi.board.vendor: Apple Inc. dmi.board.version: Macmini6,2 dmi.chassis.type: 16 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F65AE981FFA204ED dmi.modalias: dmi:bvnAppleInc.:bvrMM61.
[Desktop-packages] [Bug 1178043] Locale.txt
apport information ** Attachment added: "Locale.txt" https://bugs.launchpad.net/bugs/1178043/+attachment/5219839/+files/Locale.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to system-config-printer in Ubuntu. https://bugs.launchpad.net/bugs/1178043 Title: Print subsystem unusable on large network Status in system-config-printer package in Ubuntu: Expired Bug description: Automagically gathering all available zeroconf/avahi/whatever-its- called-this-week printers and presenting them as configured printers renders the print subsystem almost entirely unusable on a large network (>30k hosts on a LAN in this case). Offering them when I want to add a printer is passable, but presenting them as configured printers by default is ridiculous. It appears I have to remove them one-by-one (ain't gonna happen), and it's not even clear that that will be in any way permanent. We're not all on nice cosy little home networks. At least make it optional, please. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: system-config-printer-gnome 1.3.12+20130308-0ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 CupsErrorLog: W [09/May/2013:08:03:00 +1200] Please move "SystemGroup lpadmin" on line 16 of /etc/cups/cupsd.conf to the /etc/cups/cups-files.conf file; this will become an error in a future release. W [09/May/2013:08:03:00 +1200] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id 'facmed-laser-it-Gray..' already exists W [09/May/2013:08:03:00 +1200] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id 'facmed-laser-it-RGB..' already exists W [09/May/2013:08:03:00 +1200] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id 'facmed-laser-it-ps-Gray..' already exists E [09/May/2013:12:54:50 +1200] [cups-driverd] Bad driver information file "/usr/share/cups/drv/cupsfilters.drv"! Date: Thu May 9 13:01:08 2013 InstallationDate: Installed on 2013-03-15 (54 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MachineType: Apple Inc. Macmini6,2 MarkForUpload: True PackageArchitecture: all Papersize: a4 PpdFiles: facmed-laser-it: HP LaserJet 4250 pcl3, hpcups 3.13.3 facmed-laser-it-ps: HP LaserJet 4250 Postscript (recommended) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic root=UUID=77e44b8f-c46d-44ba-a999-d6962993dda8 ro quiet splash vt.handoff=7 SourcePackage: system-config-printer UpgradeStatus: Upgraded to raring on 2013-05-03 (5 days ago) dmi.bios.date: 11/16/2012 dmi.bios.vendor: Apple Inc. dmi.bios.version: MM61.88Z.0106.B03.1211161202 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-F65AE981FFA204ED dmi.board.vendor: Apple Inc. dmi.board.version: Macmini6,2 dmi.chassis.type: 16 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F65AE981FFA204ED dmi.modalias: dmi:bvnAppleInc.:bvrMM61.88Z.0106.B03.1211161202:bd11/16/2012:svnAppleInc.:pnMacmini6,2:pvr1.0:rvnAppleInc.:rnMac-F65AE981FFA204ED:rvrMacmini6,2:cvnAppleInc.:ct16:cvrMac-F65AE981FFA204ED: dmi.product.name: Macmini6,2 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CupsErrorLog: E [07/Dec/2018:13:42:38 +1300] [cups-deviced] PID 15115 (gutenprint52+usb) stopped with status 1! CurrentDesktop: GNOME DistroRelease: Ubuntu 18.04 EcryptfsInUse: Yes InstallationDate: Installed on 2017-01-09 (696 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) Lpstat: device for ljps: ipp://facmed-laser-it/ipp MachineType: Apple Inc. Macmini6,2 NonfreeKernelModules: wl Package: system-config-printer 1.5.11-1ubuntu2 PackageArchitecture: all Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/ljps.ppd'] failed with exit code 2: grep: /etc/cups/ppd/ljps.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=305f7448-19cc-4832-9e07-b21d2b7e5e39 ro 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: Upgraded to bionic on 2018-05-06 (214 days ago) UserGroups: adm cdrom dip docker libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/20/2016 dmi.bios.vendor: Apple Inc. dmi.bios.version: MM61.88Z.0106.B0B.1610201654 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-F65AE981FFA204ED dmi.board.vendor: Apple Inc. dmi.board.version: Macmini6,2 dmi.chassis.type: 16 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F65AE981FFA204ED dmi.modalias: dmi:bvnAppleInc.:bvrMM61.88Z.0106.B0
[Desktop-packages] [Bug 1178043] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1178043/+attachment/5219846/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to system-config-printer in Ubuntu. https://bugs.launchpad.net/bugs/1178043 Title: Print subsystem unusable on large network Status in system-config-printer package in Ubuntu: Expired Bug description: Automagically gathering all available zeroconf/avahi/whatever-its- called-this-week printers and presenting them as configured printers renders the print subsystem almost entirely unusable on a large network (>30k hosts on a LAN in this case). Offering them when I want to add a printer is passable, but presenting them as configured printers by default is ridiculous. It appears I have to remove them one-by-one (ain't gonna happen), and it's not even clear that that will be in any way permanent. We're not all on nice cosy little home networks. At least make it optional, please. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: system-config-printer-gnome 1.3.12+20130308-0ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 CupsErrorLog: W [09/May/2013:08:03:00 +1200] Please move "SystemGroup lpadmin" on line 16 of /etc/cups/cupsd.conf to the /etc/cups/cups-files.conf file; this will become an error in a future release. W [09/May/2013:08:03:00 +1200] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id 'facmed-laser-it-Gray..' already exists W [09/May/2013:08:03:00 +1200] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id 'facmed-laser-it-RGB..' already exists W [09/May/2013:08:03:00 +1200] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id 'facmed-laser-it-ps-Gray..' already exists E [09/May/2013:12:54:50 +1200] [cups-driverd] Bad driver information file "/usr/share/cups/drv/cupsfilters.drv"! Date: Thu May 9 13:01:08 2013 InstallationDate: Installed on 2013-03-15 (54 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MachineType: Apple Inc. Macmini6,2 MarkForUpload: True PackageArchitecture: all Papersize: a4 PpdFiles: facmed-laser-it: HP LaserJet 4250 pcl3, hpcups 3.13.3 facmed-laser-it-ps: HP LaserJet 4250 Postscript (recommended) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic root=UUID=77e44b8f-c46d-44ba-a999-d6962993dda8 ro quiet splash vt.handoff=7 SourcePackage: system-config-printer UpgradeStatus: Upgraded to raring on 2013-05-03 (5 days ago) dmi.bios.date: 11/16/2012 dmi.bios.vendor: Apple Inc. dmi.bios.version: MM61.88Z.0106.B03.1211161202 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-F65AE981FFA204ED dmi.board.vendor: Apple Inc. dmi.board.version: Macmini6,2 dmi.chassis.type: 16 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F65AE981FFA204ED dmi.modalias: dmi:bvnAppleInc.:bvrMM61.88Z.0106.B03.1211161202:bd11/16/2012:svnAppleInc.:pnMacmini6,2:pvr1.0:rvnAppleInc.:rnMac-F65AE981FFA204ED:rvrMacmini6,2:cvnAppleInc.:ct16:cvrMac-F65AE981FFA204ED: dmi.product.name: Macmini6,2 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CupsErrorLog: E [07/Dec/2018:13:42:38 +1300] [cups-deviced] PID 15115 (gutenprint52+usb) stopped with status 1! CurrentDesktop: GNOME DistroRelease: Ubuntu 18.04 EcryptfsInUse: Yes InstallationDate: Installed on 2017-01-09 (696 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) Lpstat: device for ljps: ipp://facmed-laser-it/ipp MachineType: Apple Inc. Macmini6,2 NonfreeKernelModules: wl Package: system-config-printer 1.5.11-1ubuntu2 PackageArchitecture: all Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/ljps.ppd'] failed with exit code 2: grep: /etc/cups/ppd/ljps.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=305f7448-19cc-4832-9e07-b21d2b7e5e39 ro 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: Upgraded to bionic on 2018-05-06 (214 days ago) UserGroups: adm cdrom dip docker libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/20/2016 dmi.bios.vendor: Apple Inc. dmi.bios.version: MM61.88Z.0106.B0B.1610201654 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-F65AE981FFA204ED dmi.board.vendor: Apple Inc. dmi.board.version: Macmini6,2 dmi.chassis.type: 16 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F65AE981FFA204ED dmi.modalias: dmi:bvnAppleInc.:bv
[Desktop-packages] [Bug 1178043] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1178043/+attachment/5219838/+files/Dependencies.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to system-config-printer in Ubuntu. https://bugs.launchpad.net/bugs/1178043 Title: Print subsystem unusable on large network Status in system-config-printer package in Ubuntu: Expired Bug description: Automagically gathering all available zeroconf/avahi/whatever-its- called-this-week printers and presenting them as configured printers renders the print subsystem almost entirely unusable on a large network (>30k hosts on a LAN in this case). Offering them when I want to add a printer is passable, but presenting them as configured printers by default is ridiculous. It appears I have to remove them one-by-one (ain't gonna happen), and it's not even clear that that will be in any way permanent. We're not all on nice cosy little home networks. At least make it optional, please. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: system-config-printer-gnome 1.3.12+20130308-0ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 CupsErrorLog: W [09/May/2013:08:03:00 +1200] Please move "SystemGroup lpadmin" on line 16 of /etc/cups/cupsd.conf to the /etc/cups/cups-files.conf file; this will become an error in a future release. W [09/May/2013:08:03:00 +1200] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id 'facmed-laser-it-Gray..' already exists W [09/May/2013:08:03:00 +1200] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id 'facmed-laser-it-RGB..' already exists W [09/May/2013:08:03:00 +1200] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id 'facmed-laser-it-ps-Gray..' already exists E [09/May/2013:12:54:50 +1200] [cups-driverd] Bad driver information file "/usr/share/cups/drv/cupsfilters.drv"! Date: Thu May 9 13:01:08 2013 InstallationDate: Installed on 2013-03-15 (54 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MachineType: Apple Inc. Macmini6,2 MarkForUpload: True PackageArchitecture: all Papersize: a4 PpdFiles: facmed-laser-it: HP LaserJet 4250 pcl3, hpcups 3.13.3 facmed-laser-it-ps: HP LaserJet 4250 Postscript (recommended) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic root=UUID=77e44b8f-c46d-44ba-a999-d6962993dda8 ro quiet splash vt.handoff=7 SourcePackage: system-config-printer UpgradeStatus: Upgraded to raring on 2013-05-03 (5 days ago) dmi.bios.date: 11/16/2012 dmi.bios.vendor: Apple Inc. dmi.bios.version: MM61.88Z.0106.B03.1211161202 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-F65AE981FFA204ED dmi.board.vendor: Apple Inc. dmi.board.version: Macmini6,2 dmi.chassis.type: 16 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F65AE981FFA204ED dmi.modalias: dmi:bvnAppleInc.:bvrMM61.88Z.0106.B03.1211161202:bd11/16/2012:svnAppleInc.:pnMacmini6,2:pvr1.0:rvnAppleInc.:rnMac-F65AE981FFA204ED:rvrMacmini6,2:cvnAppleInc.:ct16:cvrMac-F65AE981FFA204ED: dmi.product.name: Macmini6,2 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CupsErrorLog: E [07/Dec/2018:13:42:38 +1300] [cups-deviced] PID 15115 (gutenprint52+usb) stopped with status 1! CurrentDesktop: GNOME DistroRelease: Ubuntu 18.04 EcryptfsInUse: Yes InstallationDate: Installed on 2017-01-09 (696 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) Lpstat: device for ljps: ipp://facmed-laser-it/ipp MachineType: Apple Inc. Macmini6,2 NonfreeKernelModules: wl Package: system-config-printer 1.5.11-1ubuntu2 PackageArchitecture: all Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/ljps.ppd'] failed with exit code 2: grep: /etc/cups/ppd/ljps.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=305f7448-19cc-4832-9e07-b21d2b7e5e39 ro 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: Upgraded to bionic on 2018-05-06 (214 days ago) UserGroups: adm cdrom dip docker libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/20/2016 dmi.bios.vendor: Apple Inc. dmi.bios.version: MM61.88Z.0106.B0B.1610201654 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-F65AE981FFA204ED dmi.board.vendor: Apple Inc. dmi.board.version: Macmini6,2 dmi.chassis.type: 16 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F65AE981FFA204ED dmi.modalias: dmi:bvnAppleInc.:bvrMM6
[Desktop-packages] [Bug 1178043] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1178043/+attachment/5219845/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to system-config-printer in Ubuntu. https://bugs.launchpad.net/bugs/1178043 Title: Print subsystem unusable on large network Status in system-config-printer package in Ubuntu: Expired Bug description: Automagically gathering all available zeroconf/avahi/whatever-its- called-this-week printers and presenting them as configured printers renders the print subsystem almost entirely unusable on a large network (>30k hosts on a LAN in this case). Offering them when I want to add a printer is passable, but presenting them as configured printers by default is ridiculous. It appears I have to remove them one-by-one (ain't gonna happen), and it's not even clear that that will be in any way permanent. We're not all on nice cosy little home networks. At least make it optional, please. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: system-config-printer-gnome 1.3.12+20130308-0ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 CupsErrorLog: W [09/May/2013:08:03:00 +1200] Please move "SystemGroup lpadmin" on line 16 of /etc/cups/cupsd.conf to the /etc/cups/cups-files.conf file; this will become an error in a future release. W [09/May/2013:08:03:00 +1200] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id 'facmed-laser-it-Gray..' already exists W [09/May/2013:08:03:00 +1200] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id 'facmed-laser-it-RGB..' already exists W [09/May/2013:08:03:00 +1200] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id 'facmed-laser-it-ps-Gray..' already exists E [09/May/2013:12:54:50 +1200] [cups-driverd] Bad driver information file "/usr/share/cups/drv/cupsfilters.drv"! Date: Thu May 9 13:01:08 2013 InstallationDate: Installed on 2013-03-15 (54 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MachineType: Apple Inc. Macmini6,2 MarkForUpload: True PackageArchitecture: all Papersize: a4 PpdFiles: facmed-laser-it: HP LaserJet 4250 pcl3, hpcups 3.13.3 facmed-laser-it-ps: HP LaserJet 4250 Postscript (recommended) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic root=UUID=77e44b8f-c46d-44ba-a999-d6962993dda8 ro quiet splash vt.handoff=7 SourcePackage: system-config-printer UpgradeStatus: Upgraded to raring on 2013-05-03 (5 days ago) dmi.bios.date: 11/16/2012 dmi.bios.vendor: Apple Inc. dmi.bios.version: MM61.88Z.0106.B03.1211161202 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-F65AE981FFA204ED dmi.board.vendor: Apple Inc. dmi.board.version: Macmini6,2 dmi.chassis.type: 16 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F65AE981FFA204ED dmi.modalias: dmi:bvnAppleInc.:bvrMM61.88Z.0106.B03.1211161202:bd11/16/2012:svnAppleInc.:pnMacmini6,2:pvr1.0:rvnAppleInc.:rnMac-F65AE981FFA204ED:rvrMacmini6,2:cvnAppleInc.:ct16:cvrMac-F65AE981FFA204ED: dmi.product.name: Macmini6,2 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CupsErrorLog: E [07/Dec/2018:13:42:38 +1300] [cups-deviced] PID 15115 (gutenprint52+usb) stopped with status 1! CurrentDesktop: GNOME DistroRelease: Ubuntu 18.04 EcryptfsInUse: Yes InstallationDate: Installed on 2017-01-09 (696 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) Lpstat: device for ljps: ipp://facmed-laser-it/ipp MachineType: Apple Inc. Macmini6,2 NonfreeKernelModules: wl Package: system-config-printer 1.5.11-1ubuntu2 PackageArchitecture: all Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/ljps.ppd'] failed with exit code 2: grep: /etc/cups/ppd/ljps.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=305f7448-19cc-4832-9e07-b21d2b7e5e39 ro 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: Upgraded to bionic on 2018-05-06 (214 days ago) UserGroups: adm cdrom dip docker libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/20/2016 dmi.bios.vendor: Apple Inc. dmi.bios.version: MM61.88Z.0106.B0B.1610201654 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-F65AE981FFA204ED dmi.board.vendor: Apple Inc. dmi.board.version: Macmini6,2 dmi.chassis.type: 16 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F65AE981FFA204ED dmi.modalias: dmi:bvnAppleInc.:bvrMM61.
[Desktop-packages] [Bug 1178043] PrintingPackages.txt
apport information ** Attachment added: "PrintingPackages.txt" https://bugs.launchpad.net/bugs/1178043/+attachment/5219842/+files/PrintingPackages.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to system-config-printer in Ubuntu. https://bugs.launchpad.net/bugs/1178043 Title: Print subsystem unusable on large network Status in system-config-printer package in Ubuntu: Expired Bug description: Automagically gathering all available zeroconf/avahi/whatever-its- called-this-week printers and presenting them as configured printers renders the print subsystem almost entirely unusable on a large network (>30k hosts on a LAN in this case). Offering them when I want to add a printer is passable, but presenting them as configured printers by default is ridiculous. It appears I have to remove them one-by-one (ain't gonna happen), and it's not even clear that that will be in any way permanent. We're not all on nice cosy little home networks. At least make it optional, please. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: system-config-printer-gnome 1.3.12+20130308-0ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 CupsErrorLog: W [09/May/2013:08:03:00 +1200] Please move "SystemGroup lpadmin" on line 16 of /etc/cups/cupsd.conf to the /etc/cups/cups-files.conf file; this will become an error in a future release. W [09/May/2013:08:03:00 +1200] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id 'facmed-laser-it-Gray..' already exists W [09/May/2013:08:03:00 +1200] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id 'facmed-laser-it-RGB..' already exists W [09/May/2013:08:03:00 +1200] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id 'facmed-laser-it-ps-Gray..' already exists E [09/May/2013:12:54:50 +1200] [cups-driverd] Bad driver information file "/usr/share/cups/drv/cupsfilters.drv"! Date: Thu May 9 13:01:08 2013 InstallationDate: Installed on 2013-03-15 (54 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MachineType: Apple Inc. Macmini6,2 MarkForUpload: True PackageArchitecture: all Papersize: a4 PpdFiles: facmed-laser-it: HP LaserJet 4250 pcl3, hpcups 3.13.3 facmed-laser-it-ps: HP LaserJet 4250 Postscript (recommended) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic root=UUID=77e44b8f-c46d-44ba-a999-d6962993dda8 ro quiet splash vt.handoff=7 SourcePackage: system-config-printer UpgradeStatus: Upgraded to raring on 2013-05-03 (5 days ago) dmi.bios.date: 11/16/2012 dmi.bios.vendor: Apple Inc. dmi.bios.version: MM61.88Z.0106.B03.1211161202 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-F65AE981FFA204ED dmi.board.vendor: Apple Inc. dmi.board.version: Macmini6,2 dmi.chassis.type: 16 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F65AE981FFA204ED dmi.modalias: dmi:bvnAppleInc.:bvrMM61.88Z.0106.B03.1211161202:bd11/16/2012:svnAppleInc.:pnMacmini6,2:pvr1.0:rvnAppleInc.:rnMac-F65AE981FFA204ED:rvrMacmini6,2:cvnAppleInc.:ct16:cvrMac-F65AE981FFA204ED: dmi.product.name: Macmini6,2 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CupsErrorLog: E [07/Dec/2018:13:42:38 +1300] [cups-deviced] PID 15115 (gutenprint52+usb) stopped with status 1! CurrentDesktop: GNOME DistroRelease: Ubuntu 18.04 EcryptfsInUse: Yes InstallationDate: Installed on 2017-01-09 (696 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) Lpstat: device for ljps: ipp://facmed-laser-it/ipp MachineType: Apple Inc. Macmini6,2 NonfreeKernelModules: wl Package: system-config-printer 1.5.11-1ubuntu2 PackageArchitecture: all Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/ljps.ppd'] failed with exit code 2: grep: /etc/cups/ppd/ljps.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=305f7448-19cc-4832-9e07-b21d2b7e5e39 ro 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: Upgraded to bionic on 2018-05-06 (214 days ago) UserGroups: adm cdrom dip docker libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/20/2016 dmi.bios.vendor: Apple Inc. dmi.bios.version: MM61.88Z.0106.B0B.1610201654 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-F65AE981FFA204ED dmi.board.vendor: Apple Inc. dmi.board.version: Macmini6,2 dmi.chassis.type: 16 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F65AE981FFA204ED dmi.modalias: dmi:bvnAppleInc
[Desktop-packages] [Bug 1178043] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1178043/+attachment/5219841/+files/Lsusb.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to system-config-printer in Ubuntu. https://bugs.launchpad.net/bugs/1178043 Title: Print subsystem unusable on large network Status in system-config-printer package in Ubuntu: Expired Bug description: Automagically gathering all available zeroconf/avahi/whatever-its- called-this-week printers and presenting them as configured printers renders the print subsystem almost entirely unusable on a large network (>30k hosts on a LAN in this case). Offering them when I want to add a printer is passable, but presenting them as configured printers by default is ridiculous. It appears I have to remove them one-by-one (ain't gonna happen), and it's not even clear that that will be in any way permanent. We're not all on nice cosy little home networks. At least make it optional, please. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: system-config-printer-gnome 1.3.12+20130308-0ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 CupsErrorLog: W [09/May/2013:08:03:00 +1200] Please move "SystemGroup lpadmin" on line 16 of /etc/cups/cupsd.conf to the /etc/cups/cups-files.conf file; this will become an error in a future release. W [09/May/2013:08:03:00 +1200] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id 'facmed-laser-it-Gray..' already exists W [09/May/2013:08:03:00 +1200] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id 'facmed-laser-it-RGB..' already exists W [09/May/2013:08:03:00 +1200] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id 'facmed-laser-it-ps-Gray..' already exists E [09/May/2013:12:54:50 +1200] [cups-driverd] Bad driver information file "/usr/share/cups/drv/cupsfilters.drv"! Date: Thu May 9 13:01:08 2013 InstallationDate: Installed on 2013-03-15 (54 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MachineType: Apple Inc. Macmini6,2 MarkForUpload: True PackageArchitecture: all Papersize: a4 PpdFiles: facmed-laser-it: HP LaserJet 4250 pcl3, hpcups 3.13.3 facmed-laser-it-ps: HP LaserJet 4250 Postscript (recommended) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic root=UUID=77e44b8f-c46d-44ba-a999-d6962993dda8 ro quiet splash vt.handoff=7 SourcePackage: system-config-printer UpgradeStatus: Upgraded to raring on 2013-05-03 (5 days ago) dmi.bios.date: 11/16/2012 dmi.bios.vendor: Apple Inc. dmi.bios.version: MM61.88Z.0106.B03.1211161202 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-F65AE981FFA204ED dmi.board.vendor: Apple Inc. dmi.board.version: Macmini6,2 dmi.chassis.type: 16 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F65AE981FFA204ED dmi.modalias: dmi:bvnAppleInc.:bvrMM61.88Z.0106.B03.1211161202:bd11/16/2012:svnAppleInc.:pnMacmini6,2:pvr1.0:rvnAppleInc.:rnMac-F65AE981FFA204ED:rvrMacmini6,2:cvnAppleInc.:ct16:cvrMac-F65AE981FFA204ED: dmi.product.name: Macmini6,2 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CupsErrorLog: E [07/Dec/2018:13:42:38 +1300] [cups-deviced] PID 15115 (gutenprint52+usb) stopped with status 1! CurrentDesktop: GNOME DistroRelease: Ubuntu 18.04 EcryptfsInUse: Yes InstallationDate: Installed on 2017-01-09 (696 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) Lpstat: device for ljps: ipp://facmed-laser-it/ipp MachineType: Apple Inc. Macmini6,2 NonfreeKernelModules: wl Package: system-config-printer 1.5.11-1ubuntu2 PackageArchitecture: all Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/ljps.ppd'] failed with exit code 2: grep: /etc/cups/ppd/ljps.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=305f7448-19cc-4832-9e07-b21d2b7e5e39 ro 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: Upgraded to bionic on 2018-05-06 (214 days ago) UserGroups: adm cdrom dip docker libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/20/2016 dmi.bios.vendor: Apple Inc. dmi.bios.version: MM61.88Z.0106.B0B.1610201654 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-F65AE981FFA204ED dmi.board.vendor: Apple Inc. dmi.board.version: Macmini6,2 dmi.chassis.type: 16 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F65AE981FFA204ED dmi.modalias: dmi:bvnAppleInc.:bvrMM61.88Z.0106.B0B.
[Desktop-packages] [Bug 1178043] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1178043/+attachment/5219844/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to system-config-printer in Ubuntu. https://bugs.launchpad.net/bugs/1178043 Title: Print subsystem unusable on large network Status in system-config-printer package in Ubuntu: Expired Bug description: Automagically gathering all available zeroconf/avahi/whatever-its- called-this-week printers and presenting them as configured printers renders the print subsystem almost entirely unusable on a large network (>30k hosts on a LAN in this case). Offering them when I want to add a printer is passable, but presenting them as configured printers by default is ridiculous. It appears I have to remove them one-by-one (ain't gonna happen), and it's not even clear that that will be in any way permanent. We're not all on nice cosy little home networks. At least make it optional, please. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: system-config-printer-gnome 1.3.12+20130308-0ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 CupsErrorLog: W [09/May/2013:08:03:00 +1200] Please move "SystemGroup lpadmin" on line 16 of /etc/cups/cupsd.conf to the /etc/cups/cups-files.conf file; this will become an error in a future release. W [09/May/2013:08:03:00 +1200] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id 'facmed-laser-it-Gray..' already exists W [09/May/2013:08:03:00 +1200] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id 'facmed-laser-it-RGB..' already exists W [09/May/2013:08:03:00 +1200] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id 'facmed-laser-it-ps-Gray..' already exists E [09/May/2013:12:54:50 +1200] [cups-driverd] Bad driver information file "/usr/share/cups/drv/cupsfilters.drv"! Date: Thu May 9 13:01:08 2013 InstallationDate: Installed on 2013-03-15 (54 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MachineType: Apple Inc. Macmini6,2 MarkForUpload: True PackageArchitecture: all Papersize: a4 PpdFiles: facmed-laser-it: HP LaserJet 4250 pcl3, hpcups 3.13.3 facmed-laser-it-ps: HP LaserJet 4250 Postscript (recommended) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic root=UUID=77e44b8f-c46d-44ba-a999-d6962993dda8 ro quiet splash vt.handoff=7 SourcePackage: system-config-printer UpgradeStatus: Upgraded to raring on 2013-05-03 (5 days ago) dmi.bios.date: 11/16/2012 dmi.bios.vendor: Apple Inc. dmi.bios.version: MM61.88Z.0106.B03.1211161202 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-F65AE981FFA204ED dmi.board.vendor: Apple Inc. dmi.board.version: Macmini6,2 dmi.chassis.type: 16 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F65AE981FFA204ED dmi.modalias: dmi:bvnAppleInc.:bvrMM61.88Z.0106.B03.1211161202:bd11/16/2012:svnAppleInc.:pnMacmini6,2:pvr1.0:rvnAppleInc.:rnMac-F65AE981FFA204ED:rvrMacmini6,2:cvnAppleInc.:ct16:cvrMac-F65AE981FFA204ED: dmi.product.name: Macmini6,2 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CupsErrorLog: E [07/Dec/2018:13:42:38 +1300] [cups-deviced] PID 15115 (gutenprint52+usb) stopped with status 1! CurrentDesktop: GNOME DistroRelease: Ubuntu 18.04 EcryptfsInUse: Yes InstallationDate: Installed on 2017-01-09 (696 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) Lpstat: device for ljps: ipp://facmed-laser-it/ipp MachineType: Apple Inc. Macmini6,2 NonfreeKernelModules: wl Package: system-config-printer 1.5.11-1ubuntu2 PackageArchitecture: all Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/ljps.ppd'] failed with exit code 2: grep: /etc/cups/ppd/ljps.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=305f7448-19cc-4832-9e07-b21d2b7e5e39 ro 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: Upgraded to bionic on 2018-05-06 (214 days ago) UserGroups: adm cdrom dip docker libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/20/2016 dmi.bios.vendor: Apple Inc. dmi.bios.version: MM61.88Z.0106.B0B.1610201654 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-F65AE981FFA204ED dmi.board.vendor: Apple Inc. dmi.board.version: Macmini6,2 dmi.chassis.type: 16 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F65AE981FFA204ED dmi.modalias: dmi:bvnAppl
[Desktop-packages] [Bug 1178043] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1178043/+attachment/5219840/+files/Lspci.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to system-config-printer in Ubuntu. https://bugs.launchpad.net/bugs/1178043 Title: Print subsystem unusable on large network Status in system-config-printer package in Ubuntu: Expired Bug description: Automagically gathering all available zeroconf/avahi/whatever-its- called-this-week printers and presenting them as configured printers renders the print subsystem almost entirely unusable on a large network (>30k hosts on a LAN in this case). Offering them when I want to add a printer is passable, but presenting them as configured printers by default is ridiculous. It appears I have to remove them one-by-one (ain't gonna happen), and it's not even clear that that will be in any way permanent. We're not all on nice cosy little home networks. At least make it optional, please. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: system-config-printer-gnome 1.3.12+20130308-0ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 CupsErrorLog: W [09/May/2013:08:03:00 +1200] Please move "SystemGroup lpadmin" on line 16 of /etc/cups/cupsd.conf to the /etc/cups/cups-files.conf file; this will become an error in a future release. W [09/May/2013:08:03:00 +1200] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id 'facmed-laser-it-Gray..' already exists W [09/May/2013:08:03:00 +1200] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id 'facmed-laser-it-RGB..' already exists W [09/May/2013:08:03:00 +1200] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id 'facmed-laser-it-ps-Gray..' already exists E [09/May/2013:12:54:50 +1200] [cups-driverd] Bad driver information file "/usr/share/cups/drv/cupsfilters.drv"! Date: Thu May 9 13:01:08 2013 InstallationDate: Installed on 2013-03-15 (54 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MachineType: Apple Inc. Macmini6,2 MarkForUpload: True PackageArchitecture: all Papersize: a4 PpdFiles: facmed-laser-it: HP LaserJet 4250 pcl3, hpcups 3.13.3 facmed-laser-it-ps: HP LaserJet 4250 Postscript (recommended) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic root=UUID=77e44b8f-c46d-44ba-a999-d6962993dda8 ro quiet splash vt.handoff=7 SourcePackage: system-config-printer UpgradeStatus: Upgraded to raring on 2013-05-03 (5 days ago) dmi.bios.date: 11/16/2012 dmi.bios.vendor: Apple Inc. dmi.bios.version: MM61.88Z.0106.B03.1211161202 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-F65AE981FFA204ED dmi.board.vendor: Apple Inc. dmi.board.version: Macmini6,2 dmi.chassis.type: 16 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F65AE981FFA204ED dmi.modalias: dmi:bvnAppleInc.:bvrMM61.88Z.0106.B03.1211161202:bd11/16/2012:svnAppleInc.:pnMacmini6,2:pvr1.0:rvnAppleInc.:rnMac-F65AE981FFA204ED:rvrMacmini6,2:cvnAppleInc.:ct16:cvrMac-F65AE981FFA204ED: dmi.product.name: Macmini6,2 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CupsErrorLog: E [07/Dec/2018:13:42:38 +1300] [cups-deviced] PID 15115 (gutenprint52+usb) stopped with status 1! CurrentDesktop: GNOME DistroRelease: Ubuntu 18.04 EcryptfsInUse: Yes InstallationDate: Installed on 2017-01-09 (696 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) Lpstat: device for ljps: ipp://facmed-laser-it/ipp MachineType: Apple Inc. Macmini6,2 NonfreeKernelModules: wl Package: system-config-printer 1.5.11-1ubuntu2 PackageArchitecture: all Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/ljps.ppd'] failed with exit code 2: grep: /etc/cups/ppd/ljps.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=305f7448-19cc-4832-9e07-b21d2b7e5e39 ro 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: Upgraded to bionic on 2018-05-06 (214 days ago) UserGroups: adm cdrom dip docker libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/20/2016 dmi.bios.vendor: Apple Inc. dmi.bios.version: MM61.88Z.0106.B0B.1610201654 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-F65AE981FFA204ED dmi.board.vendor: Apple Inc. dmi.board.version: Macmini6,2 dmi.chassis.type: 16 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F65AE981FFA204ED dmi.modalias: dmi:bvnAppleInc.:bvrMM61.88Z.0106.B0B.
[Desktop-packages] [Bug 1178043] Re: Print subsystem unusable on large network
apport information ** Tags added: apport-collected bionic ** Description changed: Automagically gathering all available zeroconf/avahi/whatever-its- called-this-week printers and presenting them as configured printers renders the print subsystem almost entirely unusable on a large network (>30k hosts on a LAN in this case). Offering them when I want to add a printer is passable, but presenting them as configured printers by default is ridiculous. It appears I have to remove them one-by-one (ain't gonna happen), and it's not even clear that that will be in any way permanent. We're not all on nice cosy little home networks. At least make it optional, please. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: system-config-printer-gnome 1.3.12+20130308-0ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 CupsErrorLog: W [09/May/2013:08:03:00 +1200] Please move "SystemGroup lpadmin" on line 16 of /etc/cups/cupsd.conf to the /etc/cups/cups-files.conf file; this will become an error in a future release. W [09/May/2013:08:03:00 +1200] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id 'facmed-laser-it-Gray..' already exists W [09/May/2013:08:03:00 +1200] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id 'facmed-laser-it-RGB..' already exists W [09/May/2013:08:03:00 +1200] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id 'facmed-laser-it-ps-Gray..' already exists E [09/May/2013:12:54:50 +1200] [cups-driverd] Bad driver information file "/usr/share/cups/drv/cupsfilters.drv"! Date: Thu May 9 13:01:08 2013 InstallationDate: Installed on 2013-03-15 (54 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MachineType: Apple Inc. Macmini6,2 MarkForUpload: True PackageArchitecture: all Papersize: a4 PpdFiles: facmed-laser-it: HP LaserJet 4250 pcl3, hpcups 3.13.3 facmed-laser-it-ps: HP LaserJet 4250 Postscript (recommended) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic root=UUID=77e44b8f-c46d-44ba-a999-d6962993dda8 ro quiet splash vt.handoff=7 SourcePackage: system-config-printer UpgradeStatus: Upgraded to raring on 2013-05-03 (5 days ago) dmi.bios.date: 11/16/2012 dmi.bios.vendor: Apple Inc. dmi.bios.version: MM61.88Z.0106.B03.1211161202 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-F65AE981FFA204ED dmi.board.vendor: Apple Inc. dmi.board.version: Macmini6,2 dmi.chassis.type: 16 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F65AE981FFA204ED dmi.modalias: dmi:bvnAppleInc.:bvrMM61.88Z.0106.B03.1211161202:bd11/16/2012:svnAppleInc.:pnMacmini6,2:pvr1.0:rvnAppleInc.:rnMac-F65AE981FFA204ED:rvrMacmini6,2:cvnAppleInc.:ct16:cvrMac-F65AE981FFA204ED: dmi.product.name: Macmini6,2 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.5 + Architecture: amd64 + CupsErrorLog: E [07/Dec/2018:13:42:38 +1300] [cups-deviced] PID 15115 (gutenprint52+usb) stopped with status 1! + CurrentDesktop: GNOME + DistroRelease: Ubuntu 18.04 + EcryptfsInUse: Yes + InstallationDate: Installed on 2017-01-09 (696 days ago) + InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) + Lpstat: device for ljps: ipp://facmed-laser-it/ipp + MachineType: Apple Inc. Macmini6,2 + NonfreeKernelModules: wl + Package: system-config-printer 1.5.11-1ubuntu2 + PackageArchitecture: all + Papersize: a4 + PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/ljps.ppd'] failed with exit code 2: grep: /etc/cups/ppd/ljps.ppd: Permission denied + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=305f7448-19cc-4832-9e07-b21d2b7e5e39 ro 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: Upgraded to bionic on 2018-05-06 (214 days ago) + UserGroups: adm cdrom dip docker libvirt lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 10/20/2016 + dmi.bios.vendor: Apple Inc. + dmi.bios.version: MM61.88Z.0106.B0B.1610201654 + dmi.board.asset.tag: Base Board Asset Tag# + dmi.board.name: Mac-F65AE981FFA204ED + dmi.board.vendor: Apple Inc. + dmi.board.version: Macmini6,2 + dmi.chassis.type: 16 + dmi.chassis.vendor: Apple Inc. + dmi.chassis.version: Mac-F65AE981FFA204ED + dmi.modalias: dmi:bvnAppleInc.:bvrMM61.88Z.0106.B0B.1610201654:bd10/20/2016:svnAppleInc.:pnMacmini6,2:pvr1.0:rvnAppleInc.:rnMac-F65AE981FFA204ED:rvrMacmini6,2:cvnAppleInc.:ct16:cvrMac-F65AE981FFA204ED: + dmi.product.family: Macmini + dmi.product.name: Macmini6,2 + dmi.product.version: 1.0 + dmi.sys.vendor: Apple Inc. ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1178043/+a
[Desktop-packages] [Bug 1807056] Re: Occasional Keyboard freeze
@Daniel I did try without any extension. It was happening even then. So I put them back for comfort sake. Also, how will I type the " top " command as I cannot type anything when the issues happen. It gets ok by itself after sometime ( without me doing anything ). The interesting part is that the mouse is working fine. It is not a total freeze. I can copy, cut and paste using the mouse. Thanks. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1807056 Title: Occasional Keyboard freeze Status in gnome-shell package in Ubuntu: Incomplete Bug description: I am using 18.04 and sometimes, whatever I type does not work. It is as if there is no keyboard connected while I have my laptop keyboard and an external keyboard connected to the machine. I even enabled On Screen Keyboard and tried to type through it. Same result. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.3-0ubuntu0.18.04.3 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: communitheme:ubuntu:GNOME Date: Thu Dec 6 05:41:04 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-11-29 (6 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1807056/+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 1807076] Re: gnome-control-center doesn't start
** Attachment added: "journalctl.log" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1807076/+attachment/5219836/+files/journalctl.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1807076 Title: gnome-control-center doesn't start Status in gnome-control-center package in Ubuntu: Incomplete Bug description: gnome-control-center doesn't start. There is no crash, core dump, etc. This bit in syslog (/var/log/syslog) gives us some information: gnome-control-c[2962]: invalid unclassed pointer in cast to 'GtkWindow' gnome-control-c[2962]: gtk_window_present_with_time: assertion 'GTK_IS_WINDOW (window)' failed Actually something similar has been seen already in the past but it hasn't been resolved: https://bugs.launchpad.net/ubuntu/+source/gnome-control- center/+bug/1745846 I might not be the only person affected: https://askubuntu.com/questions/1094442/gnome-control-center- disappears-on-ubuntu-18-10-after-repostioning-ubuntu- dock/1098815#1098815 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.2 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: GNOME-Flashback:GNOME Date: Thu Dec 6 11:08:42 2018 InstallationDate: Installed on 2018-11-26 (9 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1807076/+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 1751252] Re: [regression] ubiquity crashed in debconf.py:104 with ValueError: invalid literal for int() with base 10: ''
In the Live Version on MacBook Pro 2015 (13 inches, Retina) I changed
the 'Screen Scale' from 200% to 100%, settings > Device > Display, and
solved!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cairo in Ubuntu.
https://bugs.launchpad.net/bugs/1751252
Title:
[regression] ubiquity crashed in debconf.py:104 with ValueError:
invalid literal for int() with base 10: ''
Status in cairo:
Unknown
Status in OEM Priority Project:
Fix Released
Status in cairo package in Ubuntu:
In Progress
Status in ubiquity package in Ubuntu:
Fix Released
Status in ubiquity source package in Bionic:
Fix Released
Bug description:
* Impact
The Ubuntu installer crashes on some machines (seems more often on hiDPI
machines (QHD/UHD etc)).
* Test case
Try installing Ubuntu on an hidpi machine, it should complete installation
instead of crashing.
* Regression potential
The fix in ubiquity touches the code handle uid drop/privilege, that can have
unexpected side effects so we need proper/complete testing of the installer
--
Update: Actually the crash occurs on slow-ish systems due to a race
condition. It's not strictly only hi-DPI machines - that's just the
most common place it is experienced.
---
https://errors.ubuntu.com/problem/82f7f7e7923663c7b2123c7f1f49af29f6ff4d77
https://errors.ubuntu.com/problem/735a2b847e0eeab6c8a7b954de5110e43889be15
https://errors.ubuntu.com/problem/dcd4c9da5ee0cc6d36324446e0e49d39705c90b7
https://errors.ubuntu.com/problem/cb82f70f9ede07369e8104da9ddf87e28b42257d
https://errors.ubuntu.com/problem/84a5563af3d2b85f098da832ece4cb8450bfd524
---
WORKAROUND:
1. Boot into the live session.
2. Settings > Devices > Displays > Scale = 100%
3. Click Apply.
4. Proceed with installation: Click "Install Ubuntu 18.04 LTS".
---
Crashed in a VM in the middle of installation. The host is Bionic up
to date.
From the journal
Feb 23 12:52:27 ubuntu kernel: traps: ubiquity[2646] trap int3
ip:7f5a76936961 sp:7ffde5090c50 error:0 in
libglib-2.0.so.0.5400.1[7f5a768e6000+111000]
Feb 23 12:52:41 ubuntu /install.py[6858]: Exception during installation:
Feb 23 12:52:41 ubuntu /install.py[6858]: Traceback (most recent call last):
Feb 23 12:52:41 ubuntu /install.py[6858]: File
"/usr/share/ubiquity/install.py", line 757, in
Feb 23 12:52:41 ubuntu /install.py[6858]: install.run()
Feb 23 12:52:41 ubuntu /install.py[6858]: File
"/usr/share/ubiquity/install.py", line 135, in run
Feb 23 12:52:41 ubuntu /install.py[6858]: self.copy_all()
Feb 23 12:52:41 ubuntu /install.py[6858]: File
"/usr/share/ubiquity/install.py", line 505, in copy_all
Feb 23 12:52:41 ubuntu /install.py[6858]: self.db.progress('SET', 10 +
copy_progress)
Feb 23 12:52:41 ubuntu /install.py[6858]: File
"/usr/lib/python3/dist-packages/debconf.py", line 83, in
Feb 23 12:52:41 ubuntu /install.py[6858]: lambda *args, **kw:
self.command(command, *args, **kw))
Feb 23 12:52:41 ubuntu /install.py[6858]: File
"/usr/lib/python3/dist-packages/debconf.py", line 104, in command
Feb 23 12:52:41 ubuntu /install.py[6858]: status = int(status)
Feb 23 12:52:41 ubuntu /install.py[6858]: ValueError: invalid literal for
int() with base 10: ''
ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: ubiquity 18.04.1
ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CasperVersion: 1.388
Date: Fri Feb 23 12:52:28 2018
ExecutablePath: /usr/lib/ubiquity/bin/ubiquity
InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper
initrd=/casper/initrd.lz quiet splash --- keyboard-configuration/layoutcode=fr
keyboard-configuration/variantcode=oss
InterpreterPath: /usr/bin/python3.6
LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222)
ProcCmdline: /usr/bin/python3 /usr/lib/ubiquity/bin/ubiquity -d
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
LANG=C.UTF-8
SHELL=/bin/bash
Python3Details: /usr/bin/python3.6, Python 3.6.4+, python3-minimal, 3.6.4-1
PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
Signal: 5
SourcePackage: ubiquity
StacktraceTop:
?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
_XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6
XPending () from /usr/lib/x86_64-linux-gnu/libX11.so.6
?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
Title: ubiquity crashed with signal 5 in _XEventsQueued()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
To manage notifications about this bug go to:
https://bugs.launchpad.net/cairo/+bug/1751252/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://
[Desktop-packages] [Bug 1745666] Re: gsd-housekeeping leaks file descriptors
I'm not sure if this is related or if this helps troubleshoot, but my system will randomly go unresponsive and needs to be hard rebooted. May or may not be related to this bug. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1745666 Title: gsd-housekeeping leaks file descriptors Status in gnome-settings-daemon package in Ubuntu: Confirmed Bug description: Apparently a process called gsd-housekeeping is periodically invoked on my Ubuntu 17.10 system. It traverses my /var/tmp for some reason. Looks like it is leaking file descriptors while doing so. My syslogs are full of error messages like the following: Jan 26 20:21:42 snail gsd-housekeepin[3178]: Failed to enumerate children of /var/tmp/chmaa-backup/usr/include/c++/5/bits/stl_raw_storage_iter.h: Error opening directory '/var/tmp/chmaa-backup/usr/include/c++/5/bits/stl_raw_storage_iter.h': Too many open files Jan 26 20:21:42 snail gsd-housekeepin[3178]: Failed to enumerate children of /var/tmp/chmaa-backup/usr/include/c++/5/bits/basic_string.h: Error opening directory '/var/tmp/chmaa-backup/usr/include/c++/5/bits/basic_string.h': Too many open files Jan 26 20:21:42 snail gsd-housekeepin[3178]: Failed to enumerate children of /var/tmp/chmaa-backup/usr/include/c++/5/bits/quoted_string.h: Error opening directory '/var/tmp/chmaa-backup/usr/include/c++/5/bits/quoted_string.h': Too many open files Jan 26 20:21:42 snail gsd-housekeepin[3178]: Failed to enumerate children of /var/tmp/chmaa-backup/usr/include/c++/5/bits/postypes.h: Error opening directory '/var/tmp/chmaa-backup/usr/include/c++/5/bits/postypes.h': Too many open files Jan 26 20:21:42 snail gsd-housekeepin[3178]: Failed to enumerate children of /var/tmp/chmaa-backup/usr/include/c++/5/bits/stl_iterator.h: Error opening directory '/var/tmp/chmaa-backup/usr/include/c++/5/bits/stl_iterator.h': Too many open files Jan 26 20:21:42 snail gsd-housekeepin[3178]: Failed to enumerate children of /var/tmp/chmaa-backup/usr/include/c++/5/bits/move.h: Error opening directory '/var/tmp/chmaa-backup/usr/include/c++/5/bits/move.h': Too many open files $ lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 $ apt policy gnome-settings-daemon gnome-settings-daemon: Installed: 3.26.2-0ubuntu0.1 Candidate: 3.26.2-0ubuntu0.1 Version table: *** 3.26.2-0ubuntu0.1 500 500 http://se.archive.ubuntu.com/ubuntu artful-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.26.1-0ubuntu5 500 500 http://se.archive.ubuntu.com/ubuntu artful/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1745666/+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 1745666] Re: gsd-housekeeping leaks file descriptors
Same issue here. Ubuntu 18.04 Kernel4.15.0-42-generic Dec 06 2018 Failed to enumerate children of /tmp/systemd-private- 42045536c330493292b9e62a860928e4-fwupd.service-GNaXSl: Error opening directory '/tmp/systemd-private-42045536c330493292b9e62a860928e4-fwupd .service-GNaXSl': Permission denied -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1745666 Title: gsd-housekeeping leaks file descriptors Status in gnome-settings-daemon package in Ubuntu: Confirmed Bug description: Apparently a process called gsd-housekeeping is periodically invoked on my Ubuntu 17.10 system. It traverses my /var/tmp for some reason. Looks like it is leaking file descriptors while doing so. My syslogs are full of error messages like the following: Jan 26 20:21:42 snail gsd-housekeepin[3178]: Failed to enumerate children of /var/tmp/chmaa-backup/usr/include/c++/5/bits/stl_raw_storage_iter.h: Error opening directory '/var/tmp/chmaa-backup/usr/include/c++/5/bits/stl_raw_storage_iter.h': Too many open files Jan 26 20:21:42 snail gsd-housekeepin[3178]: Failed to enumerate children of /var/tmp/chmaa-backup/usr/include/c++/5/bits/basic_string.h: Error opening directory '/var/tmp/chmaa-backup/usr/include/c++/5/bits/basic_string.h': Too many open files Jan 26 20:21:42 snail gsd-housekeepin[3178]: Failed to enumerate children of /var/tmp/chmaa-backup/usr/include/c++/5/bits/quoted_string.h: Error opening directory '/var/tmp/chmaa-backup/usr/include/c++/5/bits/quoted_string.h': Too many open files Jan 26 20:21:42 snail gsd-housekeepin[3178]: Failed to enumerate children of /var/tmp/chmaa-backup/usr/include/c++/5/bits/postypes.h: Error opening directory '/var/tmp/chmaa-backup/usr/include/c++/5/bits/postypes.h': Too many open files Jan 26 20:21:42 snail gsd-housekeepin[3178]: Failed to enumerate children of /var/tmp/chmaa-backup/usr/include/c++/5/bits/stl_iterator.h: Error opening directory '/var/tmp/chmaa-backup/usr/include/c++/5/bits/stl_iterator.h': Too many open files Jan 26 20:21:42 snail gsd-housekeepin[3178]: Failed to enumerate children of /var/tmp/chmaa-backup/usr/include/c++/5/bits/move.h: Error opening directory '/var/tmp/chmaa-backup/usr/include/c++/5/bits/move.h': Too many open files $ lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 $ apt policy gnome-settings-daemon gnome-settings-daemon: Installed: 3.26.2-0ubuntu0.1 Candidate: 3.26.2-0ubuntu0.1 Version table: *** 3.26.2-0ubuntu0.1 500 500 http://se.archive.ubuntu.com/ubuntu artful-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.26.1-0ubuntu5 500 500 http://se.archive.ubuntu.com/ubuntu artful/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1745666/+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 1804576] Re: MaxJobTime=0 results in jobs being cancelled immediately instead of never
I am unsubscribing the Sponsors Team since there doesn't appear to be anything left to sponsor here. Please feel to resubscribe if you have anything else that needs to be sponsored. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1804576 Title: MaxJobTime=0 results in jobs being cancelled immediately instead of never Status in CUPS: New Status in cups package in Ubuntu: In Progress Status in cups source package in Trusty: Invalid Status in cups source package in Xenial: In Progress Status in cups source package in Bionic: In Progress Status in cups source package in Cosmic: In Progress Status in cups source package in Disco: In Progress Status in cups package in Debian: New Bug description: [Impact] Setting the cupsd option MaxJobTime to 0 should make the server wait indefinitely for the job to be ready for print. Instead, after updating job-cancel-after option with MaxJobTime=0 value it results in immediate cancelling. This leads to problems with using filters that take some time to process - the user needs to set MaxJobTime to a ridiculously high value to ensure the job is not going to get cancelled instead of just disabling the cancelling timeout. [Test Case] 1. Add MaxJobTime 0 option to /etc/cups/cupsd.conf. 2. Setup a filter that takes at least several seconds to process. (please find a sample imagetopdf wrapper introducing 5s delay) 3. Submit a print job matching the filter, e.g. lp -d my-printer someimage.jpg # jpg uses the imagetopdf wrapper Expected result: The job is printed after the 5s delay. Actual result: The job is cancelled. [Regression Potential] The scope of the change is limited to fixing the MaxJobTime handling in scheduler/job.c and scheduler/printers.c. There should be no difference in behavior except for the special value of MaxJobTime=0. [Other Info] Original bug description: When using CUPS filters, these filters can take a few seconds to complete. In this case no documents are allowed to be lost on printing failures, so we used to set "MaxJobTime 0" in cupsd.conf which worked on Ubuntu 14.04. With cups on 18.04, you get the following message in /var/log/cups/error_log whenever the filter takes a little longer: I [12/Nov/2018:14:43:26 +0100] [Job 18] Canceling stuck job after 0 seconds. Then, the job is deleted and lost. "MaxJobTime 0" is documented as "indefinite wait", but apparently cups treats is as "wait almost not at all". This issue appears to have also been filed upstream: https://github.com/apple/cups/issues/5438 Temporary workaround is to set the MaxJobTime to a very large value instead (e.g. 3 years) Trusty is not affected by this bug. To manage notifications about this bug go to: https://bugs.launchpad.net/cups/+bug/1804576/+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 1807271] Re: MaxBitmap causing segmentation fault
*** This bug is a duplicate of bug 1806517 *** https://bugs.launchpad.net/bugs/1806517 This is possibly a duplicate of bug 1806517. Please check whether the fixed version also fixes your problem. ** This bug has been marked a duplicate of bug 1806517 Ghostscript segmentation fault on PDF using -dFirstPage and -dLastPage -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ghostscript in Ubuntu. https://bugs.launchpad.net/bugs/1807271 Title: MaxBitmap causing segmentation fault Status in ghostscript package in Ubuntu: New Bug description: Ghostscript 9.26 is seeing a segfault when MaxBitmap is too high combined with pngalpha and FirstPage settings. I've seen this on two very different PDFs from different sources. Running on Ubuntu 18.04 Command run: % gs -dMaxBitmap=5000 '-sDEVICE=pngalpha' -dFirstPage=1 '-sOutputFile=out.pdf' -fin.pdf Causes a segfault Changing MaxBitmap (or removing either of the pngalpha or FirstPage options!?) takes away the seg fault. For example, this will pass: % gs -dMaxBitmap=1000 '-sDEVICE=pngalpha' -dFirstPage=1 '-sOutputFile=out.pdf' -fin.pdf Backtrace on non-debug version when segfaulting: #0 0xb73a5ce9 in ?? () from /usr/lib/i386-linux-gnu/libgs.so.9 #1 0xb72351f4 in ?? () from /usr/lib/i386-linux-gnu/libgs.so.9 #2 0xb71b26c3 in ?? () from /usr/lib/i386-linux-gnu/libgs.so.9 #3 0xb71b8558 in ?? () from /usr/lib/i386-linux-gnu/libgs.so.9 #4 0xb71b9d29 in send_pdf14trans () from /usr/lib/i386-linux-gnu/libgs.so.9 #5 0xb719f1c1 in ?? () from /usr/lib/i386-linux-gnu/libgs.so.9 #6 0xb71a0357 in gs_pop_pdf14trans_device () from /usr/lib/i386-linux-gnu/libgs.so.9 #7 0xb74e5afc in ?? () from /usr/lib/i386-linux-gnu/libgs.so.9 #8 0xb748f07e in ?? () from /usr/lib/i386-linux-gnu/libgs.so.9 #9 0xb748f49f in gs_interpret () from /usr/lib/i386-linux-gnu/libgs.so.9 #10 0xb7481c30 in gs_main_run_string_end () from /usr/lib/i386-linux-gnu/libgs.so.9 #11 0xb7481cbc in gs_main_run_string_with_length () from /usr/lib/i386-linux-gnu/libgs.so.9 #12 0xb7481d03 in gs_main_run_string () from /usr/lib/i386-linux-gnu/libgs.so.9 #13 0xb7483918 in ?? () from /usr/lib/i386-linux-gnu/libgs.so.9 #14 0xb7483a8d in ?? () from /usr/lib/i386-linux-gnu/libgs.so.9 #15 0xb7483b64 in ?? () from /usr/lib/i386-linux-gnu/libgs.so.9 #16 0xb7484337 in ?? () from /usr/lib/i386-linux-gnu/libgs.so.9 #17 0xb74852d0 in gs_main_init_with_args () from /usr/lib/i386-linux-gnu/libgs.so.9 #18 0xb7486b82 in gsapi_init_with_args () from /usr/lib/i386-linux-gnu/libgs.so.9 #19 0x00400835 in ?? () #20 0xb6f0be81 in __libc_start_main (main=0x400780, argc=6, argv=0xb704, init=0x400aa0, fini=0x400b00, To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1807271/+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 1807277] [NEW] Cannot set tiling background for desktop
Public bug reported: The Ubuntu settings app used to allow choosing how the background image would fit the window (tiled, stretched, centered). It no longer offers any choices, backgrounds are always stretched. (Other approaches, like alt-clicking on an image in Firefox, still allow me to set a tiled background, so clearly the system is still capable of it, but it has vanished from the settings UI.) The settings app also seems generally sparser and less functional than before, which is off-putting. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.2 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Dec 6 13:38:25 2018 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-osp1-20150720-0 EcryptfsInUse: Yes ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2016-04-15 (965 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20150720-04:06 SourcePackage: gnome-control-center UpgradeStatus: Upgraded to bionic on 2018-11-08 (28 days ago) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1807277 Title: Cannot set tiling background for desktop Status in gnome-control-center package in Ubuntu: New Bug description: The Ubuntu settings app used to allow choosing how the background image would fit the window (tiled, stretched, centered). It no longer offers any choices, backgrounds are always stretched. (Other approaches, like alt-clicking on an image in Firefox, still allow me to set a tiled background, so clearly the system is still capable of it, but it has vanished from the settings UI.) The settings app also seems generally sparser and less functional than before, which is off-putting. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.2 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Dec 6 13:38:25 2018 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-osp1-20150720-0 EcryptfsInUse: Yes ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2016-04-15 (965 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20150720-04:06 SourcePackage: gnome-control-center UpgradeStatus: Upgraded to bionic on 2018-11-08 (28 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1807277/+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 1807276] [NEW] Cannot swipe up from bottom of screen to get Onscreen Keyboard in Xorg
Public bug reported: Ubuntu 18.10 / GNOME Shell 3.30.1 ALSO Ubuntu 18.04 LTS / GNOME Shell 3.28.1 Steps to reproduce on our end: - Login (Xorg as default) - Attempt to swipe up with finger from below screen RESULT: It draws a thin vertical (desktop) selection box, but no OSK - Logout - Log back in, after first hitting 'gear' button to select 'Ubuntu on Wayland' - ps -e | grep Xwayland #shows 'Xwayland' process is running - Repeat swipe up with finger from below screen RESULT: OSK shows up as expected This has been verified both in 1920x1080 as well as 3840x2160 resolutions (also with various scaling options selected) Issue is also logged upstream: https://gitlab.gnome.org/GNOME/gnome- shell/issues/839 ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1807276 Title: Cannot swipe up from bottom of screen to get Onscreen Keyboard in Xorg Status in gnome-shell package in Ubuntu: New Bug description: Ubuntu 18.10 / GNOME Shell 3.30.1 ALSO Ubuntu 18.04 LTS / GNOME Shell 3.28.1 Steps to reproduce on our end: - Login (Xorg as default) - Attempt to swipe up with finger from below screen RESULT: It draws a thin vertical (desktop) selection box, but no OSK - Logout - Log back in, after first hitting 'gear' button to select 'Ubuntu on Wayland' - ps -e | grep Xwayland #shows 'Xwayland' process is running - Repeat swipe up with finger from below screen RESULT: OSK shows up as expected This has been verified both in 1920x1080 as well as 3840x2160 resolutions (also with various scaling options selected) Issue is also logged upstream: https://gitlab.gnome.org/GNOME/gnome- shell/issues/839 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1807276/+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 1328934] Re: nautilus crash after bluetooth reconnect
*** This bug is a duplicate of bug 1186647 *** https://bugs.launchpad.net/bugs/1186647 ** This bug has been marked a duplicate of bug 1186647 /usr/bin/nautilus:6:g_assertion_message:g_assertion_message_expr:nautilus_bookmark_connect_file:nautilus_bookmark_connect_file:g_object_newv -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1328934 Title: nautilus crash after bluetooth reconnect Status in nautilus package in Ubuntu: New Bug description: When i click "browse files" from the bluetooth manager nautilus will open an show the device folders. then go out of reach with my BT device and come back. The folder is reset to home folder now and the BT device is no longer listed in the sidebar. When you now click "browse files" again from the bluetooth applet it will wait 1 or 2 seconds and then either crash instantly or when you choose the BT device in the sidebar. user@computer:~$ nautilus Gtk-Message: Failed to load module "overlay-scrollbar" ** ERROR:nautilus-bookmark.c:350:nautilus_bookmark_connect_file: assertion failed: (!nautilus_file_is_gone (bookmark->details->file)) Abgebrochen (Speicherabzug geschrieben) user@computer:~$ user@computer:~$ lsb_release -rd Description: Ubuntu 14.04 LTS Release: 14.04 user@computer:~$ apt-cache policy nautilus nautilus: Installiert: 1:3.10.1-0ubuntu9 Installationskandidat: 1:3.10.1-0ubuntu9.1 Versionstabelle: 1:3.10.1-0ubuntu9.1 0 500 http://archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages *** 1:3.10.1-0ubuntu9 0 100 /var/lib/dpkg/status 1:3.10.1-0ubuntu8 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1328934/+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 1702082] Re: /usr/bin/nautilus:ERROR:nautilus-bookmark.c:351:nautilus_bookmark_connect_file: assertion failed: (!nautilus_file_is_gone (bookmark->details->file))
Description from a duplicate "The application crashed when pressing the back button into a directory that had been deleted. This should be handled, and the application should not crash." -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1702082 Title: /usr/bin/nautilus:ERROR:nautilus- bookmark.c:351:nautilus_bookmark_connect_file: assertion failed: (!nautilus_file_is_gone (bookmark->details->file)) Status in Nautilus: Invalid Status in nautilus package in Ubuntu: Triaged Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding nautilus. This problem was most recently seen with package version 1:3.20.4-0ubuntu2, the problem page at https://errors.ubuntu.com/problem/bf809b6dff6ba5f9da90cc650449a4b862e1d00f contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1702082/+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 1792722] Re: Restarting unity-settings-daemon screws up Nautilus settings, needs Nautilus restart
** Changed in: nautilus (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1792722 Title: Restarting unity-settings-daemon screws up Nautilus settings, needs Nautilus restart Status in nautilus package in Ubuntu: New Bug description: UPDATE: see comment 2 From time to time, these two bugs resurface, which were fixed ages ago: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1130722 https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1731985 and also: the font type and/or size in Nautilus changes to a smaller and less readable font. The three things always reappear at once. Then everything goes back to expected; I'm not sure if that's when I get some new updates installed or when I just reboot. It seems to me that all these issues are things that got changed upstream in Nautilus, but patched in Ubuntu because Ubuntu maintainers have some more common sense than the Nautilus developers. I don't know if (a) sometimes someone forgets to apply some patches, and an unpatched version slips into Ubuntu's packages until somebody corrects it, or (b) some configuration gets randomly lost/changed and then restored/changed back on reboot. Either way, it's f***ing annoying. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-135.161-generic 4.4.140 Uname: Linux 4.4.0-135-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: Unity Date: Sat Sep 15 18:25:09 2018 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'190' b'org.gnome.nautilus.window-state' b'geometry' b"'1044x767+374+165'" b'org.gnome.nautilus.list-view' b'use-tree-view' b'true' b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where']" InstallationDate: Installed on 2013-10-11 (1799 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1792722/+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 1793152] Re: No feedback when I format a voume from Nautilus
** Changed in: nautilus (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1793152 Title: No feedback when I format a voume from Nautilus Status in nautilus package in Ubuntu: New Bug description: Ubuntu 18.04.1 - Communitheme installed If I have to format a Volume (in my case an external usb 750GB hard drive with secure erasing flag on) I have no feedback about the process, the window simply disappear. Good to have some progressing feedback since could be a long process ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.3-0ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 CurrentDesktop: communitheme:ubuntu:GNOME Date: Tue Sep 18 15:57:42 2018 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'322' b'org.gnome.nautilus.window-state' b'geometry' b"'1026x550+2367+244'" InstallationDate: Installed on 2018-05-08 (133 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: synology-cloud-station 4.2.6-4408 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1793152/+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 1806385]
Confirmed from my side for Version: 6.3.0.0.alpha0+ Build ID: e4c2d0bb57ab8ea8f5c400d103d01376b8140f22 CPU threads: 1; OS: Linux 4.14; UI render: default; VCL: kde5; TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:master, Time: 2018-11-30_21:37:10 Locale: ru-RU (ru_RU.UTF-8); UI-Language: en-US Calc: threaded -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1806385 Title: Creating a new slide by double click not working correctly Status in LibreOffice: Confirmed Status in libreoffice package in Ubuntu: Confirmed Bug description: 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. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1806385/+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 1805247] Re: Onscreen Keyboard in Xorg cannot be summoned by swiping up on the screen
Hi all, I made the regrettable mistake of logging the issue incorrectly; will open a new ticket ** Summary changed: - Onscreen Keyboard in Wayland cannot be summoned by swiping up on the screen + Onscreen Keyboard in Xorg cannot be summoned by swiping up on the screen ** Changed in: gnome-shell (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1805247 Title: Onscreen Keyboard in Xorg cannot be summoned by swiping up on the screen Status in gnome-shell package in Ubuntu: Invalid Bug description: -- Ubuntu 18.04 LTS -- gnome-shell 3.28.1-0ubuntu2 When user is logged in using Wayland, swipe-up gesture cannot be used to summon the OSK. Problem is non-existent on Xorg. This has been reproduced on multiple devices, leaving the user unable to use the OSK in many situations. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1805247/+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 1806385] Re: Creating a new slide by double click not working correctly
** Changed in: df-libreoffice Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1806385 Title: Creating a new slide by double click not working correctly Status in LibreOffice: Confirmed Status in libreoffice package in Ubuntu: Confirmed Bug description: 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. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1806385/+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 1793873] Re: document in \Templates does not show up on right click in Nautilus
Thank you for your bug report. Could you add your ~/.config/user- dirs.dirs to the bug? Do other files/templates work? ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low ** Changed in: nautilus (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1793873 Title: document in \Templates does not show up on right click in Nautilus Status in nautilus package in Ubuntu: Incomplete Bug description: A Text Document (empty one) in \Templates does not show up on right click in Nautilus, I tried many locations. michal:~$ ls -ltr ~/Templates/ total 0 -rw-r--r-- 1 michal michal 0 Sep 14 08:49 text I just see in Right click: New Folder Paste Select All Properties Open in Terminal Restore Missing Files... I have michal@Beast:~$ apt list | grep nautil clamtk-nautilus/bionic,bionic,bionic,bionic 5.25-1 all easytag-nautilus/bionic,bionic 2.4.3-4 amd64 gir1.2-nautilus-3.0/bionic,now 1:3.26.3-0ubuntu4 amd64 [installed,automatic] libnautilus-extension-dev/bionic 1:3.26.3-0ubuntu4 amd64 libnautilus-extension1a/bionic,now 1:3.26.3-0ubuntu4 amd64 [installed] nautilus/bionic,now 1:3.26.3-0ubuntu4 amd64 [installed] nautilus-admin/bionic,bionic,bionic,bionic 1.1.3-1 all nautilus-compare/bionic,bionic,bionic,bionic,now 0.0.4+po1-1 all [installed] nautilus-data/bionic,bionic,now 1:3.26.3-0ubuntu4 all [installed] nautilus-dropbox/bionic 2015.10.28-1ubuntu2 amd64 nautilus-emblems/bionic,bionic,bionic,bionic 0.3.1-3 all nautilus-extension-brasero/bionic,bionic 3.12.1-4ubuntu2 amd64 nautilus-extension-burner/bionic,bionic 3.0.4-0ubuntu1 amd64 nautilus-extension-gnome-terminal/bionic-updates,now 3.28.2-1ubuntu1~18.04.1 amd64 [installed,automatic] nautilus-filename-repairer/bionic,bionic 0.2.0-1 amd64 nautilus-gtkhash/bionic,bionic 1.1.1-2 amd64 nautilus-hide/bionic,bionic,bionic,bionic 0.2.3-2 all nautilus-ideviceinfo/bionic,bionic 0.1.0-0ubuntu14 amd64 nautilus-image-converter/bionic,bionic 0.3.1~git20110416-2 amd64 nautilus-owncloud/bionic,bionic,bionic,bionic 2.4.1+dfsg-1 all nautilus-script-audio-convert/bionic,bionic,bionic,bionic 0.3.1.1-0ubuntu6 all nautilus-script-collection-svn/bionic,bionic,bionic,bionic 0.9.2-0ubuntu3 all nautilus-script-debug/bionic,bionic,bionic,bionic 0.9.2-0ubuntu3 all nautilus-script-manager/bionic,bionic,bionic,bionic 0.0.5-0ubuntu5 all nautilus-scripts-manager/bionic,bionic,bionic,bionic 2.0-1 all nautilus-sendto/bionic,now 3.8.6-2 amd64 [installed] nautilus-share/bionic,now 0.7.3-2ubuntu3 amd64 [installed] nautilus-wipe/bionic,bionic 0.3-1 amd64 nitroshare-nautilus/bionic,bionic,bionic,bionic 0.3.3-1 all python-nautilus/bionic,bionic,now 1.1-6 amd64 [installed,automatic] rabbitvcs-nautilus/bionic,bionic,bionic,bionic 0.16-1.1 all seahorse-nautilus/bionic,bionic 3.11.92-2 amd64 subliminal-nautilus/bionic,bionic,bionic,bionic 1.1.1-2 all tortoisehg-nautilus/bionic,bionic,bionic,bionic 4.5.2-0ubuntu1 all ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.3-0ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Sep 22 06:45:44 2018 ExecutablePath: /usr/bin/nautilus InstallationDate: Installed on 2017-10-27 (329 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: Upgraded to bionic on 2018-09-03 (18 days ago) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1793873/+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 1794896] Re: nautilus does not show Ghex in "Open With">"Other Application" list
On what sort of file did you try to open it? Does it work now? ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low ** Changed in: nautilus (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1794896 Title: nautilus does not show Ghex in "Open With">"Other Application" list Status in nautilus package in Ubuntu: Incomplete Bug description: Ghex is installed (and the system was rebooted), but Nautilus does not show Ghex under "Open With>Other Application". ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu6 ProcVersionSignature: Ubuntu 4.15.0-34.37~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: Unity Date: Fri Sep 28 10:26:02 2018 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.preferences' b'always-use-location-entry' b'true' b'org.gnome.nautilus.preferences' b'enable-delete' b'true' b'org.gnome.nautilus.window-state' b'geometry' b"'1235x472+45+24'" b'org.gnome.nautilus.icon-view' b'captions' b"['date_modified', 'where', 'size']" b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where']" InstallationDate: Installed on 2017-12-13 (288 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: nautilus UpgradeStatus: Upgraded to xenial on 2018-08-28 (30 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1794896/+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 1793435] Re: nautilus crashed with SIGABRT
*** This bug is a duplicate of bug 1321851 *** https://bugs.launchpad.net/bugs/1321851 ** This bug has been marked a duplicate of private bug 1725942 ** This bug is no longer a duplicate of private bug 1725942 ** This bug has been marked a duplicate of bug 1321851 /usr/bin/nautilus:6:g_assertion_message:g_assertion_message_expr:nautilus_bookmark_connect_file:nautilus_bookmark_constructed:g_object_new_internal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1793435 Title: nautilus crashed with SIGABRT Status in nautilus package in Ubuntu: New Bug description: Hi It occurred while reach to network drive via created bookmark. Thanks ProblemType: Crash DistroRelease: Ubuntu 18.10 Package: nautilus 1:3.26.4-0ubuntu3 ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5 Uname: Linux 4.18.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Sep 20 07:44:41 2018 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.window-state' b'geometry' b"'960x1016+960+23'" b'org.gnome.nautilus.desktop' b'volumes-visible' b'false' b'org.gnome.nautilus.list-view' b'default-zoom-level' b"'small'" InstallationDate: Installed on 2018-09-12 (7 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180911) ProcCmdline: /usr/bin/nautilus --gapplication-service Signal: 6 SourcePackage: nautilus StacktraceTop: () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 () () () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: nautilus crashed with SIGABRT UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip fax floppy lpadmin plugdev sambashare scanner sudo tape video usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1793435/+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 1765396] Re: nautilus crashed with SIGABRT in g_assertion_message()
*** This bug is a duplicate of bug 1321851 *** https://bugs.launchpad.net/bugs/1321851 ** This bug is no longer a duplicate of private bug 1725942 ** This bug has been marked a duplicate of bug 1321851 /usr/bin/nautilus:6:g_assertion_message:g_assertion_message_expr:nautilus_bookmark_connect_file:nautilus_bookmark_constructed:g_object_new_internal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1765396 Title: nautilus crashed with SIGABRT in g_assertion_message() Status in nautilus package in Ubuntu: New Bug description: Nautilus crashes when trying to connect to an sftp server. After crashing a second retry usually works. The ssh server is on an osx machine running el capitan in case it makes any difference ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.3-0ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 19 14:35:43 2018 ExecutablePath: /usr/bin/nautilus InstallationDate: Installed on 2016-07-25 (633 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcCmdline: /usr/bin/nautilus --gapplication-service Signal: 6 SourcePackage: nautilus StacktraceTop: g_assertion_message () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 () () () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: nautilus crashed with SIGABRT in g_assertion_message() UpgradeStatus: Upgraded to bionic on 2018-04-14 (5 days ago) UserGroups: adm cdrom dialout dip docker lpadmin plugdev sambashare sudo usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1765396/+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 1794081] Re: Nautilus Freezes with High CPU and RAM
Thank you for your bug report. Does it happen every time? Is it specific to a directory? It could be a file that is causing problems in there (there has been case of svg creating issues) ** Changed in: nautilus (Ubuntu) Importance: Undecided => High ** Changed in: nautilus (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1794081 Title: Nautilus Freezes with High CPU and RAM Status in nautilus package in Ubuntu: Incomplete Bug description: When opening Nautilus with Icon View, it freezes and causing 100% CPU load and accumulates RAM until the system is out of RAM. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.3-0ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Sep 24 14:44:58 2018 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'226' b'org.gnome.nautilus.window-state' b'geometry' b"'1213x1094+62+186'" b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'larger'" b'org.gnome.nautilus.list-view' b'use-tree-view' b'true' b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'mime_type', 'where', 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency']" InstallationDate: Installed on 2017-12-15 (283 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: nautilus UpgradeStatus: Upgraded to bionic on 2018-08-22 (33 days ago) usr_lib_nautilus: dropbox 2015.10.28 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1794081/+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 1747662] Re: nautilus crashed with SIGABRT in g_assertion_message()
*** This bug is a duplicate of bug 1321851 *** https://bugs.launchpad.net/bugs/1321851 ** This bug is no longer a duplicate of private bug 1725942 ** This bug has been marked a duplicate of bug 1321851 /usr/bin/nautilus:6:g_assertion_message:g_assertion_message_expr:nautilus_bookmark_connect_file:nautilus_bookmark_constructed:g_object_new_internal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1747662 Title: nautilus crashed with SIGABRT in g_assertion_message() Status in nautilus package in Ubuntu: New Bug description: opening archiv file ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.14.0-16.19-generic 4.14.12 Uname: Linux 4.14.0-16-generic x86_64 ApportVersion: 2.20.8-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Feb 6 13:11:01 2018 ExecutablePath: /usr/bin/nautilus InstallationDate: Installed on 2017-10-26 (102 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcCmdline: /usr/bin/nautilus --gapplication-service ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=de_DE.UTF-8 Signal: 6 SourcePackage: nautilus StacktraceTop: g_assertion_message () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 () () () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: nautilus crashed with SIGABRT in g_assertion_message() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip libvirt lpadmin plugdev sambashare sudo usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1747662/+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 1795199] Re: Can't launch right click menu using touchscreen
Thank you for your bug report. Is the issue specific to the file manager? Does it work in other applications? ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low ** Changed in: nautilus (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1795199 Title: Can't launch right click menu using touchscreen Status in nautilus package in Ubuntu: Incomplete Bug description: I am using a Dell Inspiron 7373 (2-in-1) laptop running Ubuntu 18.04, and I am not able to launch the right click menu using the touchscreen, this also affects the new 18.10 beta. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1795199/+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 1795200] Re: nautilus hangs when copying mp3 audio file
** Changed in: nautilus (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1795200 Title: nautilus hangs when copying mp3 audio file Status in nautilus package in Ubuntu: New Bug description: having two windows of nautilus open copy file with from one window past file with to other window progress bar appears, runs, but stops (see attached) file appears to have been copied correctly, because it plays correctly. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu6 ProcVersionSignature: Ubuntu 4.15.0-34.37~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: Unity Date: Sun Sep 30 14:13:56 2018 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.preferences' b'always-use-location-entry' b'true' b'org.gnome.nautilus.preferences' b'enable-delete' b'true' b'org.gnome.nautilus.window-state' b'geometry' b"'1235x472+45+24'" b'org.gnome.nautilus.icon-view' b'captions' b"['date_modified', 'where', 'size']" b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where']" InstallationDate: Installed on 2017-12-13 (290 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: nautilus UpgradeStatus: Upgraded to xenial on 2018-08-28 (33 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1795200/+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 1800037] Re: Ups! Etwas ist schiefgegangen.
According to https://github.com/GNOME/nautilus/blob/8442b4e7dd45fe15ebafa4457e781e9e9c89d166/po/de.po#L4500 the original message is "Unable to find the requested file. Please check the spelling and try again." I don't remember how I triggered the error message - maybe I copied lots of files to or from a network drive, or I was copying lots of files and deleted one of them before Nautilus could get to it. I don't "complain" that the error happened, it's only that the error message is not helpful. It should have a window title, so that users can know which program is talking to them. And it would also be nice if the message includes the path and filename. Nautilus just tried to copy/move/delete the file, it surely knows which file it is talking about, and that's also an information that is useful for the users. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1800037 Title: Ups! Etwas ist schiefgegangen. Status in nautilus package in Ubuntu: Incomplete Bug description: I got an error popup with no title and the message: Ups! Etwas ist schiefgegangen. Die angeforderte Datei kann nicht gefunden werden. Bitte prüfen Sie die Schreibweise und versuchen Sie es noch einmal. OK 1) Could we please get a title for this dialog that tells users which program threw up that popup? Normal users surely don't know how to use xprop and they shouldn't need to know. 2) "The requested file could not be found". Could you please also mention the name of the requested file? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1800037/+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 1218507] Re: After user switch it's impossible to login, must reboot PC
Thank for your bug report but that issue was not a file manager one. It's also old and without duplicate so closing, feel free to open a new report if you still have problems in current versions though ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low ** Changed in: nautilus (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1218507 Title: After user switch it's impossible to login, must reboot PC Status in nautilus package in Ubuntu: Invalid Bug description: I am running Ubuntu 13.04 x64. I recently added a 2nd monitor to my PC. I also have 3 accounts on my PC, and I regularly switch between them. What happens: Once I added the 2nd monitor, I started having this problem: I am in one account, I go to the account switch options (on the top right, "Lock/Switch account") and select a new account. What happens next is that the screen flashes and shows me the desktop for the new account, but it does not prompt me to log in, the "Enter your password" window is nowhere to be seen, all I see is the desktop for the new account. I can move the mouse around, but nothing I click responds, and the keyboard is non responsive either. It happens on a daily basis, and the only option I have is to force reboot the machine, there is no way out once I get into this state. What I expect to happen: When I switch accounts: * I should be prompted the password for the new account I want to log in * the desktop for the new account should not flash (this is a privacy issue) - even when things work and I get the prompt for the new account, I also get a flash of the desktop before the "Enter your password" window appears I have an i7-3770K with the integrated graphics card, no dedicated video card. And, as mentioned, this only started happening once I added the 2nd monitor. lsb_release -rd Description: Ubuntu 13.04 Release: 13.04 ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: nautilus 1:3.6.3-0ubuntu16 ProcVersionSignature: Ubuntu 3.8.0-29.42-generic 3.8.13.5 Uname: Linux 3.8.0-29-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 Date: Thu Aug 29 09:49:06 2013 ExecutablePath: /usr/bin/nautilus InstallationDate: Installed on 2013-04-26 (125 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1218507/+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 1807271] [NEW] MaxBitmap causing segmentation fault
Public bug reported: Ghostscript 9.26 is seeing a segfault when MaxBitmap is too high combined with pngalpha and FirstPage settings. I've seen this on two very different PDFs from different sources. Running on Ubuntu 18.04 Command run: % gs -dMaxBitmap=5000 '-sDEVICE=pngalpha' -dFirstPage=1 '-sOutputFile=out.pdf' -fin.pdf Causes a segfault Changing MaxBitmap (or removing either of the pngalpha or FirstPage options!?) takes away the seg fault. For example, this will pass: % gs -dMaxBitmap=1000 '-sDEVICE=pngalpha' -dFirstPage=1 '-sOutputFile=out.pdf' -fin.pdf Backtrace on non-debug version when segfaulting: #0 0xb73a5ce9 in ?? () from /usr/lib/i386-linux-gnu/libgs.so.9 #1 0xb72351f4 in ?? () from /usr/lib/i386-linux-gnu/libgs.so.9 #2 0xb71b26c3 in ?? () from /usr/lib/i386-linux-gnu/libgs.so.9 #3 0xb71b8558 in ?? () from /usr/lib/i386-linux-gnu/libgs.so.9 #4 0xb71b9d29 in send_pdf14trans () from /usr/lib/i386-linux-gnu/libgs.so.9 #5 0xb719f1c1 in ?? () from /usr/lib/i386-linux-gnu/libgs.so.9 #6 0xb71a0357 in gs_pop_pdf14trans_device () from /usr/lib/i386-linux-gnu/libgs.so.9 #7 0xb74e5afc in ?? () from /usr/lib/i386-linux-gnu/libgs.so.9 #8 0xb748f07e in ?? () from /usr/lib/i386-linux-gnu/libgs.so.9 #9 0xb748f49f in gs_interpret () from /usr/lib/i386-linux-gnu/libgs.so.9 #10 0xb7481c30 in gs_main_run_string_end () from /usr/lib/i386-linux-gnu/libgs.so.9 #11 0xb7481cbc in gs_main_run_string_with_length () from /usr/lib/i386-linux-gnu/libgs.so.9 #12 0xb7481d03 in gs_main_run_string () from /usr/lib/i386-linux-gnu/libgs.so.9 #13 0xb7483918 in ?? () from /usr/lib/i386-linux-gnu/libgs.so.9 #14 0xb7483a8d in ?? () from /usr/lib/i386-linux-gnu/libgs.so.9 #15 0xb7483b64 in ?? () from /usr/lib/i386-linux-gnu/libgs.so.9 #16 0xb7484337 in ?? () from /usr/lib/i386-linux-gnu/libgs.so.9 #17 0xb74852d0 in gs_main_init_with_args () from /usr/lib/i386-linux-gnu/libgs.so.9 #18 0xb7486b82 in gsapi_init_with_args () from /usr/lib/i386-linux-gnu/libgs.so.9 #19 0x00400835 in ?? () #20 0xb6f0be81 in __libc_start_main (main=0x400780, argc=6, argv=0xb704, init=0x400aa0, fini=0x400b00, ** Affects: ghostscript (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ghostscript in Ubuntu. https://bugs.launchpad.net/bugs/1807271 Title: MaxBitmap causing segmentation fault Status in ghostscript package in Ubuntu: New Bug description: Ghostscript 9.26 is seeing a segfault when MaxBitmap is too high combined with pngalpha and FirstPage settings. I've seen this on two very different PDFs from different sources. Running on Ubuntu 18.04 Command run: % gs -dMaxBitmap=5000 '-sDEVICE=pngalpha' -dFirstPage=1 '-sOutputFile=out.pdf' -fin.pdf Causes a segfault Changing MaxBitmap (or removing either of the pngalpha or FirstPage options!?) takes away the seg fault. For example, this will pass: % gs -dMaxBitmap=1000 '-sDEVICE=pngalpha' -dFirstPage=1 '-sOutputFile=out.pdf' -fin.pdf Backtrace on non-debug version when segfaulting: #0 0xb73a5ce9 in ?? () from /usr/lib/i386-linux-gnu/libgs.so.9 #1 0xb72351f4 in ?? () from /usr/lib/i386-linux-gnu/libgs.so.9 #2 0xb71b26c3 in ?? () from /usr/lib/i386-linux-gnu/libgs.so.9 #3 0xb71b8558 in ?? () from /usr/lib/i386-linux-gnu/libgs.so.9 #4 0xb71b9d29 in send_pdf14trans () from /usr/lib/i386-linux-gnu/libgs.so.9 #5 0xb719f1c1 in ?? () from /usr/lib/i386-linux-gnu/libgs.so.9 #6 0xb71a0357 in gs_pop_pdf14trans_device () from /usr/lib/i386-linux-gnu/libgs.so.9 #7 0xb74e5afc in ?? () from /usr/lib/i386-linux-gnu/libgs.so.9 #8 0xb748f07e in ?? () from /usr/lib/i386-linux-gnu/libgs.so.9 #9 0xb748f49f in gs_interpret () from /usr/lib/i386-linux-gnu/libgs.so.9 #10 0xb7481c30 in gs_main_run_string_end () from /usr/lib/i386-linux-gnu/libgs.so.9 #11 0xb7481cbc in gs_main_run_string_with_length () from /usr/lib/i386-linux-gnu/libgs.so.9 #12 0xb7481d03 in gs_main_run_string () from /usr/lib/i386-linux-gnu/libgs.so.9 #13 0xb7483918 in ?? () from /usr/lib/i386-linux-gnu/libgs.so.9 #14 0xb7483a8d in ?? () from /usr/lib/i386-linux-gnu/libgs.so.9 #15 0xb7483b64 in ?? () from /usr/lib/i386-linux-gnu/libgs.so.9 #16 0xb7484337 in ?? () from /usr/lib/i386-linux-gnu/libgs.so.9 #17 0xb74852d0 in gs_main_init_with_args () from /usr/lib/i386-linux-gnu/libgs.so.9 #18 0xb7486b82 in gsapi_init_with_args () from /usr/lib/i386-linux-gnu/libgs.so.9 #19 0x00400835 in ?? () #20 0xb6f0be81 in __libc_start_main (main=0x400780, argc=6, argv=0xb704, init=0x400aa0, fini=0x400b00, To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1807271/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://he
[Desktop-packages] [Bug 1807272] Re: package libpolkit-backend-1-0:amd64 0.105-14.1 failed to install/upgrade: package libpolkit-backend-1-0:amd64 is not ready for configuration cannot configure (curr
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1807272 Title: package libpolkit-backend-1-0:amd64 0.105-14.1 failed to install/upgrade: package libpolkit-backend-1-0:amd64 is not ready for configuration cannot configure (current status 'half-installed') Status in policykit-1 package in Ubuntu: New Bug description: I install Ubuntu 16.04 two days ago and install package only with synaptic. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libpolkit-backend-1-0:amd64 0.105-14.1 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Fri Dec 7 00:30:14 2018 DuplicateSignature: package:libpolkit-backend-1-0:amd64:0.105-14.1 Processing triggers for libglib2.0-0:amd64 (2.48.2-0ubuntu4.1) ... dpkg: error processing package libpolkit-backend-1-0:amd64 (--configure): package libpolkit-backend-1-0:amd64 is not ready for configuration ErrorMessage: package libpolkit-backend-1-0:amd64 is not ready for configuration cannot configure (current status 'half-installed') RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.15ubuntu0.2 SourcePackage: policykit-1 Title: package libpolkit-backend-1-0:amd64 0.105-14.1 failed to install/upgrade: package libpolkit-backend-1-0:amd64 is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1807272/+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 1795721] Re: Newly mounted drive icons jumbled with Desktop icons.
** Changed in: nautilus (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1795721 Title: Newly mounted drive icons jumbled with Desktop icons. Status in nautilus package in Ubuntu: New Bug description: The icons for newly mounted [flash] drives automatically appear directly on top of existing desktop icons even if the the "Keep aligned" context menu has previously been selected. It can easily be corrected by selecting "Organize Desktop by Name" from the context menu, but past versions of Ubuntu have usually accomplished this automatically upon flash drive mounting without the need for doing it manually. I will attach a screenshot where you can see the icons mixed together. It appears to affect only flash drives and only the first one that is inserted, as additional drives that are added appear automatically organized on the Desktop. I'm not sure if it has anything to do with the size of the flash drive or not because my 2GB drive would not appear on the Desktop (or anywhere else for that matter) at all... ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Oct 2 12:30:21 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.10, 4.15.0-34-generic, x86_64: installed DpkgLog: ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0156] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company 3rd Gen Core processor Graphics Controller [103c:1854] InstallationDate: Installed on 2018-09-02 (30 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Hewlett-Packard HP 2000 Notebook PC ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-34-generic root=UUID=11b3a365-ed63-4add-b6d2-0d7fe34d05bb ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/16/2014 dmi.bios.vendor: Insyde dmi.bios.version: F.46 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 1854 dmi.board.vendor: Hewlett-Packard dmi.board.version: 64.2A dmi.chassis.asset.tag: 5CG3103SQ4 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.46:bd06/16/2014:svnHewlett-Packard:pnHP2000NotebookPC:pvr088A1230591620100:rvnHewlett-Packard:rn1854:rvr64.2A:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PRE X=MIN dmi.product.name: HP 2000 Notebook PC dmi.product.version: 088A1230591620100 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1795721/+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 1807272] [NEW] package libpolkit-backend-1-0:amd64 0.105-14.1 failed to install/upgrade: package libpolkit-backend-1-0:amd64 is not ready for configuration cannot configure (cu
Public bug reported: I install Ubuntu 16.04 two days ago and install package only with synaptic. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libpolkit-backend-1-0:amd64 0.105-14.1 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Fri Dec 7 00:30:14 2018 DuplicateSignature: package:libpolkit-backend-1-0:amd64:0.105-14.1 Processing triggers for libglib2.0-0:amd64 (2.48.2-0ubuntu4.1) ... dpkg: error processing package libpolkit-backend-1-0:amd64 (--configure): package libpolkit-backend-1-0:amd64 is not ready for configuration ErrorMessage: package libpolkit-backend-1-0:amd64 is not ready for configuration cannot configure (current status 'half-installed') RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.15ubuntu0.2 SourcePackage: policykit-1 Title: package libpolkit-backend-1-0:amd64 0.105-14.1 failed to install/upgrade: package libpolkit-backend-1-0:amd64 is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: policykit-1 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1807272 Title: package libpolkit-backend-1-0:amd64 0.105-14.1 failed to install/upgrade: package libpolkit-backend-1-0:amd64 is not ready for configuration cannot configure (current status 'half-installed') Status in policykit-1 package in Ubuntu: New Bug description: I install Ubuntu 16.04 two days ago and install package only with synaptic. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libpolkit-backend-1-0:amd64 0.105-14.1 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Fri Dec 7 00:30:14 2018 DuplicateSignature: package:libpolkit-backend-1-0:amd64:0.105-14.1 Processing triggers for libglib2.0-0:amd64 (2.48.2-0ubuntu4.1) ... dpkg: error processing package libpolkit-backend-1-0:amd64 (--configure): package libpolkit-backend-1-0:amd64 is not ready for configuration ErrorMessage: package libpolkit-backend-1-0:amd64 is not ready for configuration cannot configure (current status 'half-installed') RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.15ubuntu0.2 SourcePackage: policykit-1 Title: package libpolkit-backend-1-0:amd64 0.105-14.1 failed to install/upgrade: package libpolkit-backend-1-0:amd64 is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1807272/+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 1806448] Re: Dragging a window to the edge of the screen does not tile/semi-maximize it (for some apps)
Right, well those can be used, you just can't snap a window that has minimal size of 700 to half a screen in this case... it's easy to check, resize one of those application down as much as you can and see if it's smaller than half your screen? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1806448 Title: Dragging a window to the edge of the screen does not tile/semi- maximize it (for some apps) Status in gnome-shell package in Ubuntu: Incomplete Bug description: Have a relatively fresh installation of Ubuntu 18.10. Unfortunately, I just had to realize that dragging windows to the left or right edge unfortunately does not have the desired effect in a number of cases that they fill half the screen. This applies to the following apps, among others: - LibreOffice - Nautilus - Gnome Calendar - Gnome Tasks - Settings Seems to be the same in a wayland and X Session. Especially the problem with LibreOffice makes working almost impossible for me. Should not necessarily be part of a bug report, but I'm thinking about switching back to Unity or another desktop environment, as the Gnome desktop doesn't seem to be mature for a long time (I've already reported well over 10 bugs now). ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-shell 3.30.1-2ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Dec 3 18:09:43 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-11-30 (3 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1806448/+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 1783000] Re: package gnome-control-center-faces 1:3.28.2-0ubuntu0.18.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it befor
it's a package/disk corruption, not a gnome-control-center bug ** Changed in: gnome-control-center (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-control-center (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1783000 Title: package gnome-control-center-faces 1:3.28.2-0ubuntu0.18.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in gnome-control-center package in Ubuntu: Invalid Bug description: Updated failed ProblemType: Package DistroRelease: Ubuntu 18.04 Package: gnome-control-center-faces 1:3.28.2-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 Uname: Linux 4.15.0-24-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 AptOrdering: grub-common:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Sun Jul 22 21:39:04 2018 Dependencies: ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2018-06-08 (43 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.2 SourcePackage: gnome-control-center Title: package gnome-control-center-faces 1:3.28.2-0ubuntu0.18.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1783000/+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 1783000] Re: package gnome-control-center-faces 1:3.28.2-0ubuntu0.18.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it befor
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-control-center (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1783000 Title: package gnome-control-center-faces 1:3.28.2-0ubuntu0.18.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in gnome-control-center package in Ubuntu: Confirmed Bug description: Updated failed ProblemType: Package DistroRelease: Ubuntu 18.04 Package: gnome-control-center-faces 1:3.28.2-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 Uname: Linux 4.15.0-24-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 AptOrdering: grub-common:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Sun Jul 22 21:39:04 2018 Dependencies: ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2018-06-08 (43 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.2 SourcePackage: gnome-control-center Title: package gnome-control-center-faces 1:3.28.2-0ubuntu0.18.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1783000/+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 1807265] [NEW] Screen locking issue
Public bug reported: Upgraded to Cosmic Cuttlefish a little over a week ago, Now every time that the computer locks the screen, the screen is mostly blank and shows only the launchpad with favorites at the left, and the status icons at the top right. Clicking on the apps shows the app for a moment before being hidden again. The system drop down menu shows the usual information except the system tools / lock / power icons with a pause button displayed in their place but all is disabled except the pause button which suspends the computer. Upon waking again the computer is still locked. Have not discovered a key sequence that does anything when in this state. Cannot even switch virtual terminals or desktops. My only solution has been to power off the machine and do a hard reboot. I expected the lock screen to blank out the screen as it did in the previous release and show a login My computer is a Lenovo Thinkpad T-410 with 6Gb RAM. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-screensaver (not installed) ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Dec 7 03:01:50 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2017-03-22 (624 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: gnome-screensaver Symptom: security Title: Screen locking issue UpgradeStatus: Upgraded to cosmic on 2018-11-26 (10 days ago) ** Affects: gnome-screensaver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1807265 Title: Screen locking issue Status in gnome-screensaver package in Ubuntu: New Bug description: Upgraded to Cosmic Cuttlefish a little over a week ago, Now every time that the computer locks the screen, the screen is mostly blank and shows only the launchpad with favorites at the left, and the status icons at the top right. Clicking on the apps shows the app for a moment before being hidden again. The system drop down menu shows the usual information except the system tools / lock / power icons with a pause button displayed in their place but all is disabled except the pause button which suspends the computer. Upon waking again the computer is still locked. Have not discovered a key sequence that does anything when in this state. Cannot even switch virtual terminals or desktops. My only solution has been to power off the machine and do a hard reboot. I expected the lock screen to blank out the screen as it did in the previous release and show a login My computer is a Lenovo Thinkpad T-410 with 6Gb RAM. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-screensaver (not installed) ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Dec 7 03:01:50 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2017-03-22 (624 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: gnome-screensaver Symptom: security Title: Screen locking issue UpgradeStatus: Upgraded to cosmic on 2018-11-26 (10 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1807265/+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 1698270] Re: Totem pauses and stutters during video playback even when CPU usage is low
** Changed in: gstreamer Status: Confirmed => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to clutter-gst-3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1698270 Title: Totem pauses and stutters during video playback even when CPU usage is low Status in GStreamer: Expired Status in GTK+: Fix Released Status in totem-pl-parser: Expired Status in clutter-1.0 package in Ubuntu: Confirmed Status in clutter-gst-3.0 package in Ubuntu: Incomplete Status in clutter-gtk package in Ubuntu: Fix Released Status in gstreamer-vaapi package in Ubuntu: Incomplete Status in gtk+3.0 package in Ubuntu: Fix Released Status in totem-pl-parser package in Ubuntu: Fix Released Bug description: Totem pauses and stutters during video playback even when CPU usage is low. After figuring out how to play videos with full hardware accelerated decoding (e.g. <= 10% CPU), I was surprised to find Totem still pauses and stutters during playback. Other apps like Mplayer, VLC and even gst-play-1.0 never have this problem. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: totem 3.24.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 ApportVersion: 2.20.5-0ubuntu4 Architecture: amd64 Date: Fri Jun 16 12:03:18 2017 InstallationDate: Installed on 2017-05-03 (44 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502) SourcePackage: totem UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gstreamer/+bug/1698270/+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 1806517] Re: Ghostscript segmentation fault on PDF using -dFirstPage and -dLastPage
This bug was fixed in the package ghostscript - 9.26~dfsg+0-0ubuntu0.18.04.3 --- ghostscript (9.26~dfsg+0-0ubuntu0.18.04.3) bionic-security; urgency=medium * SECURITY REGRESSION: multiple regressions (LP: #1806517) - debian/patches/020181126-96c381c*.patch: fix duplex issue. - debian/patches/020181205-fae21f16*.patch: fix -dFirstPage and -dLastPage issue. -- Marc Deslauriers Thu, 06 Dec 2018 07:17:16 -0500 ** Changed in: ghostscript (Ubuntu Bionic) Status: Confirmed => Fix Released ** Changed in: ghostscript (Ubuntu Trusty) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ghostscript in Ubuntu. https://bugs.launchpad.net/bugs/1806517 Title: Ghostscript segmentation fault on PDF using -dFirstPage and -dLastPage Status in GS-GPL: Fix Released Status in ghostscript package in Ubuntu: Fix Released Status in ghostscript source package in Trusty: Fix Released Status in ghostscript source package in Xenial: Fix Released Status in ghostscript source package in Bionic: Fix Released Status in ghostscript source package in Cosmic: Fix Released Status in ghostscript source package in Disco: Fix Released Bug description: In order to convert a PDF file in PNG I use the command: » convert "myfile.pdf[0]" test.png Which gives this error: convert-im6.q16: FailedToExecuteCommand `'gs' -sstdout=%stderr -dQUIET -dSAFER -dBATCH -dNOPAUSE -dNOPROMPT -dMaxBitmap=5 -dAlignToPixels=0 -dGridFitTT=2 '-sDEVICE=pngalpha' -dTextAlphaBits=4 -dGraphicsAlphaBits=4 '-r72x72' -dFirstPage=1 -dLastPage=1 '-sOutputFile=/tmp/magick-11774WIkYdVETEs9I%d' '-f/tmp/magick-11774JZhknqCDhkN0' '-f/tmp/magick-11774twGtf-JFihri'' (-1) @ error/delegate.c/ExternalDelegateCommand/462. convert-im6.q16: no images defined `test.png' @ error/convert.c/ConvertImageCommand/3258. So I tried using ghostscript directly: » ghostscript -dSAFER -dBATCH -dNOPAUSE -dNOPROMPT -dMaxBitmap=5 -dAlignToPixels=0 -dGridFitTT=2 -sDEVICE=pngalpha -dTextAlphaBits=4 -dGraphicsAlphaBits=4 -r72x72 -dFirstPage=1 -dLastPage=1 '-sOutputFile=test.png' '-fmyfile.pdf' Which gives an error: GPL Ghostscript 9.26 (2018-11-20) Copyright (C) 2018 Artifex Software, Inc. All rights reserved. This software comes with NO WARRANTY: see the file PUBLIC for details. Processing pages 1 through 1. Page 1 [1]10954 segmentation fault (core dumped) ghostscript -dSAFER -dBATCH -dNOPAUSE -dNOPROMPT -dMaxBitmap=5 If I omit -dFirstPage=1 -dLastPage=1 it works properly: » ghostscript -dSAFER -dBATCH -dNOPAUSE -dNOPROMPT -dMaxBitmap=5 -dAlignToPixels=0 -dGridFitTT=2 -sDEVICE=pngalpha -dTextAlphaBits=4 -dGraphicsAlphaBits=4 -r72x72 '-sOutputFile=test.png' '-fmyfile.pdf' GPL Ghostscript 9.26 (2018-11-20) Copyright (C) 2018 Artifex Software, Inc. All rights reserved. This software comes with NO WARRANTY: see the file PUBLIC for details. Processing pages 1 through 2. Page 1 Page 2 Please note that it also affects imagemagick convert command and PHP readimage command. I have confirmed the bug on Ubuntu 16.04 too. The recent ghostscript 9.26 version is definitely guilty. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: ghostscript 9.26~dfsg+0-0ubuntu0.18.10.1 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Dec 4 12:59:59 2018 InstallationDate: Installed on 2018-06-28 (158 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: ghostscript UpgradeStatus: Upgraded to cosmic on 2018-10-20 (44 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gs-gpl/+bug/1806517/+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 1806517] Re: Ghostscript segmentation fault on PDF using -dFirstPage and -dLastPage
This bug was fixed in the package ghostscript - 9.26~dfsg+0-0ubuntu0.14.04.3 --- ghostscript (9.26~dfsg+0-0ubuntu0.14.04.3) trusty-security; urgency=medium * SECURITY REGRESSION: multiple regressions (LP: #1806517) - debian/patches/020181126-96c381c*.patch: fix duplex issue. - debian/patches/020181205-fae21f16*.patch: fix -dFirstPage and -dLastPage issue. -- Marc Deslauriers Thu, 06 Dec 2018 07:18:19 -0500 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ghostscript in Ubuntu. https://bugs.launchpad.net/bugs/1806517 Title: Ghostscript segmentation fault on PDF using -dFirstPage and -dLastPage Status in GS-GPL: Fix Released Status in ghostscript package in Ubuntu: Fix Released Status in ghostscript source package in Trusty: Fix Released Status in ghostscript source package in Xenial: Fix Released Status in ghostscript source package in Bionic: Fix Released Status in ghostscript source package in Cosmic: Fix Released Status in ghostscript source package in Disco: Fix Released Bug description: In order to convert a PDF file in PNG I use the command: » convert "myfile.pdf[0]" test.png Which gives this error: convert-im6.q16: FailedToExecuteCommand `'gs' -sstdout=%stderr -dQUIET -dSAFER -dBATCH -dNOPAUSE -dNOPROMPT -dMaxBitmap=5 -dAlignToPixels=0 -dGridFitTT=2 '-sDEVICE=pngalpha' -dTextAlphaBits=4 -dGraphicsAlphaBits=4 '-r72x72' -dFirstPage=1 -dLastPage=1 '-sOutputFile=/tmp/magick-11774WIkYdVETEs9I%d' '-f/tmp/magick-11774JZhknqCDhkN0' '-f/tmp/magick-11774twGtf-JFihri'' (-1) @ error/delegate.c/ExternalDelegateCommand/462. convert-im6.q16: no images defined `test.png' @ error/convert.c/ConvertImageCommand/3258. So I tried using ghostscript directly: » ghostscript -dSAFER -dBATCH -dNOPAUSE -dNOPROMPT -dMaxBitmap=5 -dAlignToPixels=0 -dGridFitTT=2 -sDEVICE=pngalpha -dTextAlphaBits=4 -dGraphicsAlphaBits=4 -r72x72 -dFirstPage=1 -dLastPage=1 '-sOutputFile=test.png' '-fmyfile.pdf' Which gives an error: GPL Ghostscript 9.26 (2018-11-20) Copyright (C) 2018 Artifex Software, Inc. All rights reserved. This software comes with NO WARRANTY: see the file PUBLIC for details. Processing pages 1 through 1. Page 1 [1]10954 segmentation fault (core dumped) ghostscript -dSAFER -dBATCH -dNOPAUSE -dNOPROMPT -dMaxBitmap=5 If I omit -dFirstPage=1 -dLastPage=1 it works properly: » ghostscript -dSAFER -dBATCH -dNOPAUSE -dNOPROMPT -dMaxBitmap=5 -dAlignToPixels=0 -dGridFitTT=2 -sDEVICE=pngalpha -dTextAlphaBits=4 -dGraphicsAlphaBits=4 -r72x72 '-sOutputFile=test.png' '-fmyfile.pdf' GPL Ghostscript 9.26 (2018-11-20) Copyright (C) 2018 Artifex Software, Inc. All rights reserved. This software comes with NO WARRANTY: see the file PUBLIC for details. Processing pages 1 through 2. Page 1 Page 2 Please note that it also affects imagemagick convert command and PHP readimage command. I have confirmed the bug on Ubuntu 16.04 too. The recent ghostscript 9.26 version is definitely guilty. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: ghostscript 9.26~dfsg+0-0ubuntu0.18.10.1 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Dec 4 12:59:59 2018 InstallationDate: Installed on 2018-06-28 (158 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: ghostscript UpgradeStatus: Upgraded to cosmic on 2018-10-20 (44 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gs-gpl/+bug/1806517/+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 1806517] Re: Ghostscript segmentation fault on PDF using -dFirstPage and -dLastPage
This bug was fixed in the package ghostscript - 9.26~dfsg+0-0ubuntu0.16.04.3 --- ghostscript (9.26~dfsg+0-0ubuntu0.16.04.3) xenial-security; urgency=medium * SECURITY REGRESSION: multiple regressions (LP: #1806517) - debian/patches/020181126-96c381c*.patch: fix duplex issue. - debian/patches/020181205-fae21f16*.patch: fix -dFirstPage and -dLastPage issue. -- Marc Deslauriers Thu, 06 Dec 2018 07:17:51 -0500 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ghostscript in Ubuntu. https://bugs.launchpad.net/bugs/1806517 Title: Ghostscript segmentation fault on PDF using -dFirstPage and -dLastPage Status in GS-GPL: Fix Released Status in ghostscript package in Ubuntu: Fix Released Status in ghostscript source package in Trusty: Fix Released Status in ghostscript source package in Xenial: Fix Released Status in ghostscript source package in Bionic: Fix Released Status in ghostscript source package in Cosmic: Fix Released Status in ghostscript source package in Disco: Fix Released Bug description: In order to convert a PDF file in PNG I use the command: » convert "myfile.pdf[0]" test.png Which gives this error: convert-im6.q16: FailedToExecuteCommand `'gs' -sstdout=%stderr -dQUIET -dSAFER -dBATCH -dNOPAUSE -dNOPROMPT -dMaxBitmap=5 -dAlignToPixels=0 -dGridFitTT=2 '-sDEVICE=pngalpha' -dTextAlphaBits=4 -dGraphicsAlphaBits=4 '-r72x72' -dFirstPage=1 -dLastPage=1 '-sOutputFile=/tmp/magick-11774WIkYdVETEs9I%d' '-f/tmp/magick-11774JZhknqCDhkN0' '-f/tmp/magick-11774twGtf-JFihri'' (-1) @ error/delegate.c/ExternalDelegateCommand/462. convert-im6.q16: no images defined `test.png' @ error/convert.c/ConvertImageCommand/3258. So I tried using ghostscript directly: » ghostscript -dSAFER -dBATCH -dNOPAUSE -dNOPROMPT -dMaxBitmap=5 -dAlignToPixels=0 -dGridFitTT=2 -sDEVICE=pngalpha -dTextAlphaBits=4 -dGraphicsAlphaBits=4 -r72x72 -dFirstPage=1 -dLastPage=1 '-sOutputFile=test.png' '-fmyfile.pdf' Which gives an error: GPL Ghostscript 9.26 (2018-11-20) Copyright (C) 2018 Artifex Software, Inc. All rights reserved. This software comes with NO WARRANTY: see the file PUBLIC for details. Processing pages 1 through 1. Page 1 [1]10954 segmentation fault (core dumped) ghostscript -dSAFER -dBATCH -dNOPAUSE -dNOPROMPT -dMaxBitmap=5 If I omit -dFirstPage=1 -dLastPage=1 it works properly: » ghostscript -dSAFER -dBATCH -dNOPAUSE -dNOPROMPT -dMaxBitmap=5 -dAlignToPixels=0 -dGridFitTT=2 -sDEVICE=pngalpha -dTextAlphaBits=4 -dGraphicsAlphaBits=4 -r72x72 '-sOutputFile=test.png' '-fmyfile.pdf' GPL Ghostscript 9.26 (2018-11-20) Copyright (C) 2018 Artifex Software, Inc. All rights reserved. This software comes with NO WARRANTY: see the file PUBLIC for details. Processing pages 1 through 2. Page 1 Page 2 Please note that it also affects imagemagick convert command and PHP readimage command. I have confirmed the bug on Ubuntu 16.04 too. The recent ghostscript 9.26 version is definitely guilty. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: ghostscript 9.26~dfsg+0-0ubuntu0.18.10.1 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Dec 4 12:59:59 2018 InstallationDate: Installed on 2018-06-28 (158 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: ghostscript UpgradeStatus: Upgraded to cosmic on 2018-10-20 (44 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gs-gpl/+bug/1806517/+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 1806517] Re: Ghostscript segmentation fault on PDF using -dFirstPage and -dLastPage
This bug was fixed in the package ghostscript - 9.26~dfsg+0-0ubuntu0.18.10.3 --- ghostscript (9.26~dfsg+0-0ubuntu0.18.10.3) cosmic-security; urgency=medium * SECURITY REGRESSION: multiple regressions (LP: #1806517) - debian/patches/020181126-96c381c*.patch: fix duplex issue. - debian/patches/020181205-fae21f16*.patch: fix -dFirstPage and -dLastPage issue. -- Marc Deslauriers Thu, 06 Dec 2018 07:14:48 -0500 ** Changed in: ghostscript (Ubuntu Cosmic) Status: Confirmed => Fix Released ** Changed in: ghostscript (Ubuntu Xenial) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ghostscript in Ubuntu. https://bugs.launchpad.net/bugs/1806517 Title: Ghostscript segmentation fault on PDF using -dFirstPage and -dLastPage Status in GS-GPL: Fix Released Status in ghostscript package in Ubuntu: Fix Released Status in ghostscript source package in Trusty: Fix Released Status in ghostscript source package in Xenial: Fix Released Status in ghostscript source package in Bionic: Fix Released Status in ghostscript source package in Cosmic: Fix Released Status in ghostscript source package in Disco: Fix Released Bug description: In order to convert a PDF file in PNG I use the command: » convert "myfile.pdf[0]" test.png Which gives this error: convert-im6.q16: FailedToExecuteCommand `'gs' -sstdout=%stderr -dQUIET -dSAFER -dBATCH -dNOPAUSE -dNOPROMPT -dMaxBitmap=5 -dAlignToPixels=0 -dGridFitTT=2 '-sDEVICE=pngalpha' -dTextAlphaBits=4 -dGraphicsAlphaBits=4 '-r72x72' -dFirstPage=1 -dLastPage=1 '-sOutputFile=/tmp/magick-11774WIkYdVETEs9I%d' '-f/tmp/magick-11774JZhknqCDhkN0' '-f/tmp/magick-11774twGtf-JFihri'' (-1) @ error/delegate.c/ExternalDelegateCommand/462. convert-im6.q16: no images defined `test.png' @ error/convert.c/ConvertImageCommand/3258. So I tried using ghostscript directly: » ghostscript -dSAFER -dBATCH -dNOPAUSE -dNOPROMPT -dMaxBitmap=5 -dAlignToPixels=0 -dGridFitTT=2 -sDEVICE=pngalpha -dTextAlphaBits=4 -dGraphicsAlphaBits=4 -r72x72 -dFirstPage=1 -dLastPage=1 '-sOutputFile=test.png' '-fmyfile.pdf' Which gives an error: GPL Ghostscript 9.26 (2018-11-20) Copyright (C) 2018 Artifex Software, Inc. All rights reserved. This software comes with NO WARRANTY: see the file PUBLIC for details. Processing pages 1 through 1. Page 1 [1]10954 segmentation fault (core dumped) ghostscript -dSAFER -dBATCH -dNOPAUSE -dNOPROMPT -dMaxBitmap=5 If I omit -dFirstPage=1 -dLastPage=1 it works properly: » ghostscript -dSAFER -dBATCH -dNOPAUSE -dNOPROMPT -dMaxBitmap=5 -dAlignToPixels=0 -dGridFitTT=2 -sDEVICE=pngalpha -dTextAlphaBits=4 -dGraphicsAlphaBits=4 -r72x72 '-sOutputFile=test.png' '-fmyfile.pdf' GPL Ghostscript 9.26 (2018-11-20) Copyright (C) 2018 Artifex Software, Inc. All rights reserved. This software comes with NO WARRANTY: see the file PUBLIC for details. Processing pages 1 through 2. Page 1 Page 2 Please note that it also affects imagemagick convert command and PHP readimage command. I have confirmed the bug on Ubuntu 16.04 too. The recent ghostscript 9.26 version is definitely guilty. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: ghostscript 9.26~dfsg+0-0ubuntu0.18.10.1 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Dec 4 12:59:59 2018 InstallationDate: Installed on 2018-06-28 (158 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: ghostscript UpgradeStatus: Upgraded to cosmic on 2018-10-20 (44 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gs-gpl/+bug/1806517/+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 1806448] Re: Dragging a window to the edge of the screen does not tile/semi-maximize it (for some apps)
Setting the scaling to 150% solved the issue for me. But I don't know if it is because of the minimum width. If I understand it correctly, due to the scaling I have 1225 pixels available instead of 2550, half of which would be 637 pixels. Doesn't sound that bad either. There are also monitors and beamers that have a lower resolution than 1225 pixel in width, right? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1806448 Title: Dragging a window to the edge of the screen does not tile/semi- maximize it (for some apps) Status in gnome-shell package in Ubuntu: Incomplete Bug description: Have a relatively fresh installation of Ubuntu 18.10. Unfortunately, I just had to realize that dragging windows to the left or right edge unfortunately does not have the desired effect in a number of cases that they fill half the screen. This applies to the following apps, among others: - LibreOffice - Nautilus - Gnome Calendar - Gnome Tasks - Settings Seems to be the same in a wayland and X Session. Especially the problem with LibreOffice makes working almost impossible for me. Should not necessarily be part of a bug report, but I'm thinking about switching back to Unity or another desktop environment, as the Gnome desktop doesn't seem to be mature for a long time (I've already reported well over 10 bugs now). ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-shell 3.30.1-2ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Dec 3 18:09:43 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-11-30 (3 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1806448/+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 1802569] Re: RM openssl1.0 from Ubuntu
** Changed in: netty-tcnative-1.1 (Debian) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to freerdp in Ubuntu. https://bugs.launchpad.net/bugs/1802569 Title: RM openssl1.0 from Ubuntu Status in cfengine2 package in Ubuntu: Confirmed Status in ckermit package in Ubuntu: Confirmed Status in conserver package in Ubuntu: Confirmed Status in cqrlog package in Ubuntu: Confirmed Status in freerdp package in Ubuntu: New Status in libpam-ssh package in Ubuntu: New Status in mailavenger package in Ubuntu: Confirmed Status in moonshot-trust-router package in Ubuntu: Confirmed Status in netkit-ftp-ssl package in Ubuntu: Confirmed Status in netty-tcnative-1.1 package in Ubuntu: New Status in openssl1.0 package in Ubuntu: Incomplete Status in osslsigncode package in Ubuntu: New Status in pam-ssh-agent-auth package in Ubuntu: New Status in pidentd package in Ubuntu: New Status in qpid-proton package in Ubuntu: New Status in radsecproxy package in Ubuntu: New Status in reconserver package in Ubuntu: Confirmed Status in resiprocate package in Ubuntu: New Status in ruby-eventmachine package in Ubuntu: New Status in stunserver package in Ubuntu: New Status in validns package in Ubuntu: New Status in cfengine2 package in Debian: New Status in ckermit package in Debian: New Status in conserver package in Debian: New Status in cqrlog package in Debian: New Status in freerdp package in Debian: Fix Released Status in libpam-ssh package in Debian: New Status in mailavenger package in Debian: Fix Released Status in moonshot-trust-router package in Debian: New Status in netkit-ftp-ssl package in Debian: New Status in netty-tcnative-1.1 package in Debian: Fix Released Status in openssl1.0 package in Debian: New Status in osslsigncode package in Debian: New Status in pam-ssh-agent-auth package in Debian: New Status in pidentd package in Debian: New Status in qpid-proton package in Debian: New Status in radsecproxy package in Debian: Confirmed Status in reconserver package in Debian: New Status in resiprocate package in Debian: Confirmed Status in ruby-eventmachine package in Debian: Fix Released Status in stunserver package in Debian: Confirmed Status in validns package in Debian: Confirmed Bug description: RM openssl1.0 from Ubuntu reconserver has multiple ftbfs issues / bugs. freerdp is superseeded by freerdp2. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cfengine2/+bug/1802569/+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 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
Hello, sorry for my poor english, I am french. A had exactly the same issue with a ASUS Zenbook UX433, and I fund a solution. The issue comes from the Kernel part of the Alsa drivers. Daniel Drake and Jian-Hong Pan provided a patch in the alsa mailing list to fix this issue for UX533/UX433 laptop (and maybe other Asus models) : http://mailman.alsa-project.org/pipermail/alsa-devel/2018-December/142572.html This patch is not in the current kernel, nor in 4.20rc tree as far I can see. Fortunatly, you can find a patched version of the files in : https://github.com/endlessm/linux/tree/master/sound (A nice, easy to use linux distro) What I did : - clone official Kernel source repo (4.19-7 in my case) - clone endless Os repo - Copy the "sound" folder from endless tree to official kernel tree. - Compile the "no more official" Kernel. (I followed this tuto : https://wiki.archlinux.org/index.php/Kernel/Traditional_compilation because I use Manjaro, based on Arch) You have to find an appropriate tuto for Ubuntu. It was the firt time I compile a kernel.) - Use this kernel : the sound work perfectly. Note : I'm absolutly not a linux expert, it maybe exists a better way to use the patch than recompile the kernel. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1784485 Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Bug description: Internal speaker - not sound at all Cable Headphonse - realy quiet disorted sound Bluetooth headphones - sound works fine On Windows 10 everything works fine. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pmichalski 7964 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Jul 30 22:32:10 2018 InstallationDate: Installed on 2018-07-17 (12 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Wbudowany dźwięk - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm2988 F pulseaudio pmichalski 7964 F pulseaudio Symptom_Jack: Mic, Internal Symptom_Type: No sound at all Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX391UA.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX391UA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook S dmi.product.name: ZenBook S UX391UA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485/+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 1804424] Re: Segmentation fault when region panel is closed during init
This bug was fixed in the package gnome-control-center - 1:3.30.2-1ubuntu0.18.10.1 --- gnome-control-center (1:3.30.2-1ubuntu0.18.10.1) cosmic; urgency=medium * New upstream release (LP: #1805441) - Fix crash in power panel (LP: #1797205) * debian/patches: - Debian-s-adduser-doesn-t-allow-uppercase-letters-by-defau.patch: + Drop because we already have 08_lowercase_user_names.patch in cosmic. - region-Autodisconnect-IBusBus-connected-handler.patch: + Do not segfault when region panel is closed during init (LP: #1804424) - region-Fix-double-free-when-closing-the-input-chooser-dia.patch: + Drop, applied upstream. -- Andrea Azzarone Wed, 21 Nov 2018 10:29:36 + ** Changed in: gnome-control-center (Ubuntu Cosmic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1804424 Title: Segmentation fault when region panel is closed during init Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-control-center source package in Cosmic: Fix Released Bug description: [Impact] gnome-control-center crashes during opening. [Test case] -$ gnome-control-center region - close gnome-control-center -$ gnome-control-center notifications Make sure gnome-control-center does not crash and no critical warning is displayed. [Possible regressions] It's a safe signal disconnection patch so there should be no possible regression. Original bug: https://gitlab.gnome.org/GNOME/gnome-control- center/issues/223 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1804424/+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 1797205] Update Released
The verification of the Stable Release Update for gnome-control-center has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1797205 Title: /usr/bin/gnome-control- center:11:g_type_check_instance:g_signal_handlers_block_matched:als_enabled_state_changed:ffi_call_unix64:ffi_call Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-control-center source package in Cosmic: Fix Released Bug description: * Impact g-c-c segfaults in the region panel sometimes * Test case Use the power panel and switch to other panels, also check that the e.u.c reports stop * Regression potential The change is in the power panel, check those settings still work correctly -- The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-control-center. This problem was most recently seen with package version 1:3.30.1-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/2ddf38bad57fd999c49468a7407614123cac3e11 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1797205/+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 1804448] Update Released
The verification of the Stable Release Update for mutter has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1804448 Title: SRU Mutter 3.30.2-1 to cosmic Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Cosmic: Fix Released Bug description: [Impact] As per https://gitlab.gnome.org/GNOME/mutter/commit/bcd6103c44ff74ebffd1737b8e0f3a952b83bd54 the new stable version fixes two crashes (one when `gnome-shell --replace` is used and the other one is likely LP: #1801110), a memory leak and a couple of issue with input methods. In particular the fix for the crash on `gnome-shell --replace` will make gnome-shell development fun again. [Test case] Covered by https://wiki.ubuntu.com/StableReleaseUpdates/GNOME [Potential Regressions] Please make sure that monitor hot-plug properly works in an X session. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1804448/+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 1797205] Re: /usr/bin/gnome-control-center:11:g_type_check_instance:g_signal_handlers_block_matched:als_enabled_state_changed:ffi_call_unix64:ffi_call
This bug was fixed in the package gnome-control-center - 1:3.30.2-1ubuntu0.18.10.1 --- gnome-control-center (1:3.30.2-1ubuntu0.18.10.1) cosmic; urgency=medium * New upstream release (LP: #1805441) - Fix crash in power panel (LP: #1797205) * debian/patches: - Debian-s-adduser-doesn-t-allow-uppercase-letters-by-defau.patch: + Drop because we already have 08_lowercase_user_names.patch in cosmic. - region-Autodisconnect-IBusBus-connected-handler.patch: + Do not segfault when region panel is closed during init (LP: #1804424) - region-Fix-double-free-when-closing-the-input-chooser-dia.patch: + Drop, applied upstream. -- Andrea Azzarone Wed, 21 Nov 2018 10:29:36 + ** Changed in: gnome-control-center (Ubuntu Cosmic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1797205 Title: /usr/bin/gnome-control- center:11:g_type_check_instance:g_signal_handlers_block_matched:als_enabled_state_changed:ffi_call_unix64:ffi_call Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-control-center source package in Cosmic: Fix Released Bug description: * Impact g-c-c segfaults in the region panel sometimes * Test case Use the power panel and switch to other panels, also check that the e.u.c reports stop * Regression potential The change is in the power panel, check those settings still work correctly -- The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-control-center. This problem was most recently seen with package version 1:3.30.1-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/2ddf38bad57fd999c49468a7407614123cac3e11 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1797205/+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 1804448] Re: SRU Mutter 3.30.2-1 to cosmic
This bug was fixed in the package mutter - 3.30.2-1~ubuntu18.10.1 --- mutter (3.30.2-1~ubuntu18.10.1) cosmic; urgency=medium * SRU backport from unstable / disco to cosmic. (LP: #1804448) * Drop change from 3.30.1-4 for the SRU - we are not ready to SRU this yet (reinstates the patch): + Drop clutter-Smooth-out-master-clock-to-smooth-visuals.patch: It was abandoned upstream, but also seems to be limiting refresh rates in Xorg sessions to 60Hz when previously they were unlimited. + Also modify the changelog entry for 3.30.1-4 to drop the bug ref so it doesn't confuse the SRU process. mutter (3.30.2-1) unstable; urgency=medium * Team upload * New upstream release - Drop cherry-picked patches mutter (3.30.1-4) unstable; urgency=medium [ Andrea Azzarone ] * d/p/x11-close-display-in-an-idle-function.patch: - close the x11 display in an idle function. This fixes a crash when running 'gnome-shell --replace'. [ Daniel van Vugt] * Drop clutter-Smooth-out-master-clock-to-smooth-visuals.patch: It was abandoned upstream, but also seems to be limiting refresh rates in Xorg sessions to 60Hz when previously they were unlimited (see LP #1763892). mutter (3.30.1-3) unstable; urgency=medium * Team upload [ Jeremy Bicha ] * Only depend on libegl1-mesa-dev on Linux * debian/libmutter-3-0.symbols: Mark many symbols as Linux-only [ Simon McVittie ] * debian/patches: Update to upstream gnome-3-30 branch at commit 3.30.1-8-g1abab3fe2 - In particular this fixes two memory leaks introduced in 3.30.1 (Closes: #913028) mutter (3.30.1-2) unstable; urgency=medium * Only Build-Depend on libdrm-dev and libgbm-dev on Linux -- Iain Lane Thu, 22 Nov 2018 13:53:20 + ** Changed in: mutter (Ubuntu Cosmic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1804448 Title: SRU Mutter 3.30.2-1 to cosmic Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Cosmic: Fix Released Bug description: [Impact] As per https://gitlab.gnome.org/GNOME/mutter/commit/bcd6103c44ff74ebffd1737b8e0f3a952b83bd54 the new stable version fixes two crashes (one when `gnome-shell --replace` is used and the other one is likely LP: #1801110), a memory leak and a couple of issue with input methods. In particular the fix for the crash on `gnome-shell --replace` will make gnome-shell development fun again. [Test case] Covered by https://wiki.ubuntu.com/StableReleaseUpdates/GNOME [Potential Regressions] Please make sure that monitor hot-plug properly works in an X session. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1804448/+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 1805441] Update Released
The verification of the Stable Release Update for gnome-control-center has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1805441 Title: SRU 3.30.2 to Cosmic Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-control-center source package in Cosmic: Fix Released Bug description: [Description] Update cosmic from 3.30.1 to 3.30.2. We cannot just backport 3.30.2 from Disco because we need to drop Debian-s-adduser-doesn-t-allow-uppercase-letters-by-defau.patch as we already got a diffrent patch in cosmic. We should also include debian/patches/region-Autodisconnect-IBusBus- connected-handler.patch. This patch has been cherry picked from the gnome-3-30 upstream patch and contains a fix for a segmentation fault (LP: #1804424). NEWS. The upstream changes are covered by https://wiki.ubuntu.com/StableReleaseUpdates/GNOME: === Version 3.30.2 === - Translation updates Display: - Hide unsupported resolutions again - Improve snapping - Stop night light dialog being destroyed twice Online Accounts: - Track the lifecycle of CcGoaPanel across async calls Region: - Fix double-free when closing the input chooser dialog Wi-Fi: - Disable periodic scan only when Wi-Fi is disabled [Test Case] Open gnome-control-center and make sure that the panels in the above list are working properly. Testing all possible scenarios would be problematic but I suggest focusing on: 1. Open the wifi panel and make sure that you can enable/disable the wifi properly 2. On a multi-head setup open the display panel and make sure that you can re-arrange the layout of your displays. Please follow also the test case for LP: #1804424 that should cover the fixes included in debian/patches/region-Autodisconnect-IBusBus- connected-handler.patch [Regression Potential] The changes to the Online Accounts panel, Regions panels and Night Light dialog are pretty safe and there should be no possible regression. Possible regressions: - wifi panel: you could not be able to enable/disable the wifi - display panel: you could not be able to re-arrange the monitor layouts on a multi-monitor setup. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1805441/+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 1805247] Re: Onscreen Keyboard in Wayland cannot be summoned by swiping up on the screen
Logged upstream: https://gitlab.gnome.org/GNOME/gnome-shell/issues/831 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1805247 Title: Onscreen Keyboard in Wayland cannot be summoned by swiping up on the screen Status in gnome-shell package in Ubuntu: New Bug description: -- Ubuntu 18.04 LTS -- gnome-shell 3.28.1-0ubuntu2 When user is logged in using Wayland, swipe-up gesture cannot be used to summon the OSK. Problem is non-existent on Xorg. This has been reproduced on multiple devices, leaving the user unable to use the OSK in many situations. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1805247/+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 1804424] Update Released
The verification of the Stable Release Update for gnome-control-center has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1804424 Title: Segmentation fault when region panel is closed during init Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-control-center source package in Cosmic: Fix Released Bug description: [Impact] gnome-control-center crashes during opening. [Test case] -$ gnome-control-center region - close gnome-control-center -$ gnome-control-center notifications Make sure gnome-control-center does not crash and no critical warning is displayed. [Possible regressions] It's a safe signal disconnection patch so there should be no possible regression. Original bug: https://gitlab.gnome.org/GNOME/gnome-control- center/issues/223 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1804424/+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 1805441] Re: SRU 3.30.2 to Cosmic
This bug was fixed in the package gnome-control-center - 1:3.30.2-1ubuntu0.18.10.1 --- gnome-control-center (1:3.30.2-1ubuntu0.18.10.1) cosmic; urgency=medium * New upstream release (LP: #1805441) - Fix crash in power panel (LP: #1797205) * debian/patches: - Debian-s-adduser-doesn-t-allow-uppercase-letters-by-defau.patch: + Drop because we already have 08_lowercase_user_names.patch in cosmic. - region-Autodisconnect-IBusBus-connected-handler.patch: + Do not segfault when region panel is closed during init (LP: #1804424) - region-Fix-double-free-when-closing-the-input-chooser-dia.patch: + Drop, applied upstream. -- Andrea Azzarone Wed, 21 Nov 2018 10:29:36 + ** Changed in: gnome-control-center (Ubuntu Cosmic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1805441 Title: SRU 3.30.2 to Cosmic Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-control-center source package in Cosmic: Fix Released Bug description: [Description] Update cosmic from 3.30.1 to 3.30.2. We cannot just backport 3.30.2 from Disco because we need to drop Debian-s-adduser-doesn-t-allow-uppercase-letters-by-defau.patch as we already got a diffrent patch in cosmic. We should also include debian/patches/region-Autodisconnect-IBusBus- connected-handler.patch. This patch has been cherry picked from the gnome-3-30 upstream patch and contains a fix for a segmentation fault (LP: #1804424). NEWS. The upstream changes are covered by https://wiki.ubuntu.com/StableReleaseUpdates/GNOME: === Version 3.30.2 === - Translation updates Display: - Hide unsupported resolutions again - Improve snapping - Stop night light dialog being destroyed twice Online Accounts: - Track the lifecycle of CcGoaPanel across async calls Region: - Fix double-free when closing the input chooser dialog Wi-Fi: - Disable periodic scan only when Wi-Fi is disabled [Test Case] Open gnome-control-center and make sure that the panels in the above list are working properly. Testing all possible scenarios would be problematic but I suggest focusing on: 1. Open the wifi panel and make sure that you can enable/disable the wifi properly 2. On a multi-head setup open the display panel and make sure that you can re-arrange the layout of your displays. Please follow also the test case for LP: #1804424 that should cover the fixes included in debian/patches/region-Autodisconnect-IBusBus- connected-handler.patch [Regression Potential] The changes to the Online Accounts panel, Regions panels and Night Light dialog are pretty safe and there should be no possible regression. Possible regressions: - wifi panel: you could not be able to enable/disable the wifi - display panel: you could not be able to re-arrange the monitor layouts on a multi-monitor setup. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1805441/+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 1755490] Re: Incorrect information about display shown in gnome/unity-control-center
This bug was fixed in the package hwdata - 0.267-1ubuntu2 --- hwdata (0.267-1ubuntu2) xenial; urgency=medium * Change PNP vendor name for GSM to LG Electronics (LP: #1755490) Update pnp.ids file, which was missing from last change. -- Dariusz Gadomski Tue, 27 Nov 2018 09:13:39 +0100 ** Changed in: hwdata (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-desktop3 in Ubuntu. https://bugs.launchpad.net/bugs/1755490 Title: Incorrect information about display shown in gnome/unity-control- center Status in gnome-desktop3 package in Ubuntu: Fix Released Status in hwdata package in Ubuntu: Fix Released Status in unity-settings-daemon package in Ubuntu: Fix Released Status in gnome-desktop3 source package in Trusty: Fix Committed Status in hwdata source package in Trusty: Fix Committed Status in unity-settings-daemon source package in Trusty: Invalid Status in hwdata source package in Xenial: Fix Released Status in unity-settings-daemon source package in Xenial: Fix Released Status in hwdata source package in Bionic: Fix Committed Status in unity-settings-daemon source package in Bionic: Fix Released Status in hwdata source package in Cosmic: Fix Committed Status in unity-settings-daemon source package in Cosmic: Fix Released Bug description: [Impact] * There is a number of display devices that misuse the width & height field in EDID. Instead of real size in centimeters it contains encoded aspect ratio (e.g. 1600x900, 16x10, 160x90). This leads to incorrect calculation of diagonal for the purpose of e.g. Unity settings app. [Test Case] 1. Connect a display device that provides incorrect EDID data (e.g. LG 49UB850T-DA TV). 2. Open the Displays section of Unity settings. 3. Look for the name of the newly connected display in the settings window. Expected result: Display name should contain its real diagonal or model name (if dimensions are not availabe). Actual result: Display name contains a ridiculous diagonal (e.g. 72" in case of a 49" display). [Regression Potential] * This affects the way the display name will be formatted for any software using unity-settings-daemon. If anything is testing/comparing display names - it may fail. [Other Info] * Original bug description: After connecting a LG 49UB850T-DA TV the following information is displayed in the unity-control-center: Goldstar Company Ltd 72" It's misleading since neither the company name nor the diagonal matches. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-desktop3/+bug/1755490/+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 1802675] Re: Nautilus progress bar don't appear when you Copy-Paste files to Desktop, and small files don't show that has been copied/moved succesfully in the circle indicator
Hello Sebastian, Although I move back to Windows (*it was needed for my job). I remember that I when was copying between local directories or from a directory to the my ext. HDD was behaving ok the problem appears when copying straight to the desktop (*not the folder). If you see the video I attached I demonstrate well the problem. Also the hdd was formatted as NTFS. Thank you. Ellinas Marios -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1802675 Title: Nautilus progress bar don't appear when you Copy-Paste files to Desktop, and small files don't show that has been copied/moved succesfully in the circle indicator Status in nautilus package in Ubuntu: New Bug description: Hello, When i Copy/Move Files from my Ext. Hdd to the Desktop the progress bar (circle indicator) dont appear at all i know its finished by the LED light on my Ext. Hdd. In the other hand when i use the Copy To/Move To from the right click context menu the indicator with progress appear and shows the progress of the Move/Copy. Also when i Move/Copy small files the method doesn't matter in this case the circle indicator don't appear at all neither i get a message "Copied "File name" to "Destination"succesfully. I attach a video s that shows both problems. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.4-0~ubuntu18.04.2 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 NonfreeKernelModules: wl nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME Date: Sat Nov 10 21:46:15 2018 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'170' b'org.gnome.nautilus.window-state' b'geometry' b"'649x280+717+348'" InstallationDate: Installed on 2018-10-26 (15 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1802675/+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 1804576] Re: MaxJobTime=0 results in jobs being cancelled immediately instead of never
> Sponsored all the CUPS package uploads: disco, cosmic, bionic, xenial, > and subscribed SRU team. hmm, cups is still in disco-proposed currently, so hopefully that proceeds to -updates without problems. Thanks. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1804576 Title: MaxJobTime=0 results in jobs being cancelled immediately instead of never Status in CUPS: New Status in cups package in Ubuntu: In Progress Status in cups source package in Trusty: Invalid Status in cups source package in Xenial: In Progress Status in cups source package in Bionic: In Progress Status in cups source package in Cosmic: In Progress Status in cups source package in Disco: In Progress Status in cups package in Debian: New Bug description: [Impact] Setting the cupsd option MaxJobTime to 0 should make the server wait indefinitely for the job to be ready for print. Instead, after updating job-cancel-after option with MaxJobTime=0 value it results in immediate cancelling. This leads to problems with using filters that take some time to process - the user needs to set MaxJobTime to a ridiculously high value to ensure the job is not going to get cancelled instead of just disabling the cancelling timeout. [Test Case] 1. Add MaxJobTime 0 option to /etc/cups/cupsd.conf. 2. Setup a filter that takes at least several seconds to process. (please find a sample imagetopdf wrapper introducing 5s delay) 3. Submit a print job matching the filter, e.g. lp -d my-printer someimage.jpg # jpg uses the imagetopdf wrapper Expected result: The job is printed after the 5s delay. Actual result: The job is cancelled. [Regression Potential] The scope of the change is limited to fixing the MaxJobTime handling in scheduler/job.c and scheduler/printers.c. There should be no difference in behavior except for the special value of MaxJobTime=0. [Other Info] Original bug description: When using CUPS filters, these filters can take a few seconds to complete. In this case no documents are allowed to be lost on printing failures, so we used to set "MaxJobTime 0" in cupsd.conf which worked on Ubuntu 14.04. With cups on 18.04, you get the following message in /var/log/cups/error_log whenever the filter takes a little longer: I [12/Nov/2018:14:43:26 +0100] [Job 18] Canceling stuck job after 0 seconds. Then, the job is deleted and lost. "MaxJobTime 0" is documented as "indefinite wait", but apparently cups treats is as "wait almost not at all". This issue appears to have also been filed upstream: https://github.com/apple/cups/issues/5438 Temporary workaround is to set the MaxJobTime to a very large value instead (e.g. 3 years) Trusty is not affected by this bug. To manage notifications about this bug go to: https://bugs.launchpad.net/cups/+bug/1804576/+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 1799740] Re: Moving desktop icons places them with some offset
** Tags added: hidpi -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1799740 Title: Moving desktop icons places them with some offset Status in nautilus package in Ubuntu: New Bug description: Desktop Environment: Budgie Note: I have HighDPI scaling enabled (200%). Moving icons on desktop doesn't place them at the position where you drag them to, but about 100px top-left from the target position. This "error offset" is constant, though. It does NOT get bigger on different (more bottom right) positions. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.4-0~ubuntu18.04.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Wed Oct 24 17:33:51 2018 InstallationDate: Installed on 2018-10-20 (3 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1799740/+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 1796475] Re: Nautilus lists files in a directory without proper permissions
Thank you for your bug report, what happens if you try to ls the directory from a command line? ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low ** Changed in: nautilus (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1796475 Title: Nautilus lists files in a directory without proper permissions Status in nautilus package in Ubuntu: Incomplete Bug description: I have a directory inside '/tmp' which is owned by root:root (user root and group root). Directory's permissions are 0700 (means that only the user, root, has full permissions). The directory '/tmp' has permissions 'drwxrwxrwt' and is owned by root:root. I created a directory '/tmp/OO' with permissions 'drwx--' which is owned by root:root. Inside the directory '/tmp/OO' there are two files: $ sudo ls -la /tmp/OO total 16 drwx-- 2 root root 80 Oct 6 13:39 . drwxrwxrwt 17 root root 400 Oct 6 13:54 .. -rw-rw-r-- 1 root root 8503 Oct 6 13:16 FILE.ods -rwxrw-r-- 1 root root 64 Oct 6 13:20 run.sh I open Nautilus in '/tmp' and click on the arrow (of Tree View) for '/tmp/OO' and successfully manages to see the file 'run.sh' inside (but cannot see the file 'FILE.ods'). I expected that I won't be able to see *any* file, since that the eXecute permission of the directory '/tmp/OO' is absent for Other. Ubuntu release 16.04. Nautilus package version 1:3.18.4.is.3.14.3-0ubuntu6. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1796475/+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 1798769] Re: Unable to mount
Thanks, closing the report then since it was not a problem due to nautilus ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low ** Changed in: nautilus (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1798769 Title: Unable to mount Status in nautilus package in Ubuntu: Invalid Bug description: I just upgraded Ubuntu from 18.04.1 to 18.10. Now the graphics are great. But as my OS is on a partition for itself I need to mount several partitions to do some regular work on my system. I usually do this through Nautilus. But as I attempt to mount my drives in Nautilus I receive the error: unable to access location error mounting /dev/sdc1 at /media/User/Maxtor:mount(2) system call failed: bad address and if I try to mount through the terminal I receive the same error. So I went into Gparted to check up on my partitions. Every partition and harddrives are visible in here. Now I'm stuck ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: nautilus 1:3.26.4-0ubuntu7 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 NonfreeKernelModules: talpa_vfshook talpa_pedconnector talpa_pedevice talpa_vcdevice talpa_core talpa_linux talpa_syscallhook nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 19 10:32:31 2018 InstallationDate: Installed on 2018-09-07 (41 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: nautilus UpgradeStatus: Upgraded to cosmic on 2018-10-19 (0 days ago) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1798769/+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 1796711] Re: Nautilus not generating image thumbnails
*** This bug is a duplicate of bug 1796369 *** https://bugs.launchpad.net/bugs/1796369 ** This bug has been marked a duplicate of bug 1796369 Nautilus not generating image thumbnails -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1796711 Title: Nautilus not generating image thumbnails Status in nautilus package in Ubuntu: New Bug description: Ubuntu 18.04.1 nautilus-1:3.26.4-0 When going to a directory with images those images that were there before I updated to 18.04 still display thumbnails. Any new images placed in to the directory don't display thumbnails. Any images, new or old, that are edited and saved back don't display thumbnails. Edit any existing image which does have a thumbnail and the thumbnail will disappear. The same happens on the Desktop which I believe also uses Nautilus to render. I'll attach a screenshot ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: nautilus 1:3.26.4-0ubuntu5 Uname: Linux 4.18.0-041800-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: KDE Date: Mon Oct 8 17:05:14 2018 GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b"'967x803+900+104'" b'org.gnome.nautilus.desktop' b'home-icon-visible' b'false' b'org.gnome.nautilus.desktop' b'volumes-visible' b'false' b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'mime_type', 'where', 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency']" InstallationDate: Installed on 2017-12-06 (306 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: nautilus UpgradeStatus: Upgraded to cosmic on 2018-07-10 (90 days ago) usr_lib_nautilus: dropbox 2015.10.28 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1796711/+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 1795854] Re: recently glitchy, no response to keyboard or mouse
Thank you for your bug report. Is that only with the file manager? Did you try rebooting, does that make any difference? ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low ** Changed in: nautilus (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1795854 Title: recently glitchy, no response to keyboard or mouse Status in nautilus package in Ubuntu: Incomplete Bug description: Since update 2 days ago UI has been glitchy, keyboard and mouse stop responding click to open file... nothing happens mouse does not respond...then cursor starts moving again. This is UNWANTED behavior! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.4-0~ubuntu18.04.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Oct 3 13:37:56 2018 InstallationDate: Installed on 2015-08-23 (1136 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) SourcePackage: nautilus UpgradeStatus: Upgraded to bionic on 2018-08-21 (43 days ago) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1795854/+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 1796369] Re: Nautilus not generating image thumbnails
Could you include your journalctl log after triggering the issue? ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low ** Changed in: nautilus (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1796369 Title: Nautilus not generating image thumbnails Status in nautilus package in Ubuntu: Incomplete Bug description: Ubuntu 18.04.1 nautilus-1:3.26.4-0 When going to a directory with images those images that were there before I updated to 18.04 still display thumbnails. Any new images placed in to the directory don't display thumbnails. Any images, new or old, that are edited and saved back don't display thumbnails. Edit any existing image which does have a thumbnail and the thumbnail will disappear. The same happens on the Desktop which I believe also uses Nautilus to render. I'll attach a screenshot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1796369/+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 1797163] Re: crashed with no warning no error message
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low ** Changed in: nautilus (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1797163 Title: crashed with no warning no error message Status in nautilus package in Ubuntu: Invalid Bug description: normal activity searching for a file screen locked nautilus crashed Nautilus has been hurky jerky glitchy for weeks now :( ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.4-0~ubuntu18.04.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Oct 10 18:38:20 2018 InstallationDate: Installed on 2015-08-23 (1144 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) SourcePackage: nautilus UpgradeStatus: Upgraded to bionic on 2018-08-21 (50 days ago) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1797163/+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 1797158] Re: Nautilus fails to show file transfer status when copying from NAS
thank you for your bug report, the issue looks similar to bug #1802675 ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1797158 Title: Nautilus fails to show file transfer status when copying from NAS Status in nautilus package in Ubuntu: New Bug description: When copying a file from a NAS using the AFP protocol the "pie chart" graphic in Nautilus fails to display status of the transfer. Eventually the file is copied to the Ubuntu system correctly. This does not occur when copying from Ubuntu system to the NAS, in that case the progress graph displays the file transfer progress. Description:Ubuntu 18.04.1 LTS nautilus: Installed: 1:3.26.3-0ubuntu4 Candidate: 1:3.26.4-0~ubuntu18.04.1 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.3-0ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Oct 10 11:17:49 2018 InstallationDate: Installed on 2018-05-08 (154 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1797158/+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 1807127] Re: Fixing bug #1795668 breaks thumbnail creation on 32-bit Ubuntu
I submitted a fix to upstream: https://gitlab.gnome.org/GNOME/gnome- desktop/merge_requests/20, let's see what they say. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-desktop3 in Ubuntu. https://bugs.launchpad.net/bugs/1807127 Title: Fixing bug #1795668 breaks thumbnail creation on 32-bit Ubuntu Status in gnome-desktop3 package in Ubuntu: New Bug description: Fixing bug #1795668 breaks thumbnail creation on 32-bit Ubuntu. Looks like same issue in upstream - https://bugzilla.redhat.com/show_bug.cgi?id=1651952 Cause - bubblewrap runs with --ro-bind /lib64 option, then fails. Workaround - create empty /lib64 directory at root. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libgnome-desktop-3-17 3.28.2-0ubuntu1.1 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic i686 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: i386 CurrentDesktop: ubuntu:GNOME Date: Thu Dec 6 12:07:28 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-desktop3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-desktop3/+bug/1807127/+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 1800037] Re: Ups! Etwas ist schiefgegangen.
Thank you for your bug report, that doesn't seem a nautilus issue though. Could you include a screenshot of the dialog? How did you trigger it? ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low ** Changed in: nautilus (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1800037 Title: Ups! Etwas ist schiefgegangen. Status in nautilus package in Ubuntu: Incomplete Bug description: I got an error popup with no title and the message: Ups! Etwas ist schiefgegangen. Die angeforderte Datei kann nicht gefunden werden. Bitte prüfen Sie die Schreibweise und versuchen Sie es noch einmal. OK 1) Could we please get a title for this dialog that tells users which program threw up that popup? Normal users surely don't know how to use xprop and they shouldn't need to know. 2) "The requested file could not be found". Could you please also mention the name of the requested file? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1800037/+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 1801415] Re: Enlarging icon view within a folder changes desktop icon size also
*** This bug is a duplicate of bug 1537606 *** https://bugs.launchpad.net/bugs/1537606 ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low ** This bug has been marked a duplicate of bug 1537606 Changing icon sizes causes desktop icon sizes to change too -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1801415 Title: Enlarging icon view within a folder changes desktop icon size also Status in nautilus package in Ubuntu: New Bug description: If you open a folder and change the view from list to icons and then hold CTRL and zoom in, the size of the icons on the desktop change as well. Zooming in while using the list view does not affect the desktop icon sizes. To me this is a bug and not desirable behavior but if it's just a matter of preference and not a bug please let me know. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.4-0~ubuntu18.04.2 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Nov 2 16:03:51 2018 GsettingsChanges: b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.preferences' b'search-filter-time-type' b"'last_used'" b'org.gnome.nautilus.window-state' b'sidebar-width' b'196' b'org.gnome.nautilus.window-state' b'geometry' b"'935x685+898+236'" InstallationDate: Installed on 2018-10-31 (2 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1801415/+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 1800149] Re: nautilus text overflow selection
That's indeed suboptimal, ideally it should be reported upstream on https://gitlab.gnome.org/GNOME/nautilus/issues/ ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low ** Changed in: nautilus (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1800149 Title: nautilus text overflow selection Status in nautilus package in Ubuntu: Confirmed Bug description: Sorry but my english is not well Conditions: 1.- Multiple large filenames 2.- Select various files Result: The result is that texts and icons are stacked, making it illegible It shows the names of the files in the same way as when you select only one, making it look bad enough. showing the names of the files about icons To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1800149/+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 1801317] Re: Can't move/snap Nautilus window to occupy left or right half of the 1366x768 screen
not a nautilus bug but a gnome-shell limitation ** Changed in: nautilus (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1801317 Title: Can't move/snap Nautilus window to occupy left or right half of the 1366x768 screen Status in nautilus package in Ubuntu: Invalid Bug description: I'm running Ubuntu 18.04 LTS with GNOME Shell. Nautilus does not want to occupy 50% (left or right) of the screen sized at 1366x768. See screencast - https://i.stack.imgur.com/ainWP.gif . Other applications (such as GNOME Terminal, Eye of GNOME, Gedit) are normally snapping to the left/right half of the screen. But Nautilus can be resized to the width lower than half of screen (I can get 650 px, which is smaller than 1366/2 = 683 px). The first usable screen resolution seems to be 1400x1050, then goes 1440x900. But large amount of [current devices](http://gs.statcounter.com/screen-resolution- stats/desktop/worldwide/#monthly-201709-201809-bar) are still using 1366x768. Notes: 1. first seen on AskUbuntu ( https://askubuntu.com/q/1088630/66509 ) 2. disabling SideBar helps (by or `gsettings set org.gnome.nautilus.window-state start-with-sidebar false` ), but it is hack and loss of usubility. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.3-0ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Nov 2 12:21:05 2018 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'196' b'org.gnome.nautilus.window-state' b'geometry' b"'890x549+268+38'" InstallationDate: Installed on 2018-04-28 (187 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1801317/+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 1800043] Re: nautilus cannot write on nfs file share
Thank you for your bug report. Can you write into that directory using the gio command line utility? Do you get any error in the journalctl log or in the nautilus UI when trying to copy to the base directory? ** Changed in: nautilus (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1800043 Title: nautilus cannot write on nfs file share Status in nautilus package in Ubuntu: New Bug description: I installed Ubuntu 18.04LTS comming from 16.04LTS where I did not have this weird problem: If I mount a NFS share from a file server (i.e. Synology DS 418) Nautilus is not able to perform any write access to it (write, delete, make new directory,...). I can do all of this operations by using shell commands (touch, cp, mkdir...) in a terminal window. Also, nautilus can perform these actions if I start it with root privileges. Even stranger is the following: even though nautilus cannot write into the mounted shares it is able to write into its subfolders. This bug seems to affect others as well: https://askubuntu.com/questions/1000973/nautilus-cannot-write-into-1st-directory-of-a-nfs-share Ubuntu version: 18.04.1 LTS - amd64 Nautilus version: 1:3.26.4-0~ubuntu18.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1800043/+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 1802610] Re: FIle View Windows Don't Snap To Screen Sides On Second Monitor
Upstream doesn't consider it as a bug, at least not in nautilus. Could perhaps be handled in a nicer way in gnome-shell though... ** Changed in: nautilus (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1802610 Title: FIle View Windows Don't Snap To Screen Sides On Second Monitor Status in nautilus package in Ubuntu: Invalid Bug description: When I have a folder open and try to snap the window to the sides of my second monitor nothing happens. Bringing the window to the top of the screen will make it go full screen as expected. Snapping works perfectly on my primary monitor (left, top, right). Other applications like terminal, gedit, and Firefox snap correctly on my second monitor. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1802610/+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 1804576] Re: MaxJobTime=0 results in jobs being cancelled immediately instead of never
Sponsored all the CUPS package uploads: disco, cosmic, bionic, xenial, and subscribed SRU team. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1804576 Title: MaxJobTime=0 results in jobs being cancelled immediately instead of never Status in CUPS: New Status in cups package in Ubuntu: In Progress Status in cups source package in Trusty: Invalid Status in cups source package in Xenial: In Progress Status in cups source package in Bionic: In Progress Status in cups source package in Cosmic: In Progress Status in cups source package in Disco: In Progress Status in cups package in Debian: New Bug description: [Impact] Setting the cupsd option MaxJobTime to 0 should make the server wait indefinitely for the job to be ready for print. Instead, after updating job-cancel-after option with MaxJobTime=0 value it results in immediate cancelling. This leads to problems with using filters that take some time to process - the user needs to set MaxJobTime to a ridiculously high value to ensure the job is not going to get cancelled instead of just disabling the cancelling timeout. [Test Case] 1. Add MaxJobTime 0 option to /etc/cups/cupsd.conf. 2. Setup a filter that takes at least several seconds to process. (please find a sample imagetopdf wrapper introducing 5s delay) 3. Submit a print job matching the filter, e.g. lp -d my-printer someimage.jpg # jpg uses the imagetopdf wrapper Expected result: The job is printed after the 5s delay. Actual result: The job is cancelled. [Regression Potential] The scope of the change is limited to fixing the MaxJobTime handling in scheduler/job.c and scheduler/printers.c. There should be no difference in behavior except for the special value of MaxJobTime=0. [Other Info] Original bug description: When using CUPS filters, these filters can take a few seconds to complete. In this case no documents are allowed to be lost on printing failures, so we used to set "MaxJobTime 0" in cupsd.conf which worked on Ubuntu 14.04. With cups on 18.04, you get the following message in /var/log/cups/error_log whenever the filter takes a little longer: I [12/Nov/2018:14:43:26 +0100] [Job 18] Canceling stuck job after 0 seconds. Then, the job is deleted and lost. "MaxJobTime 0" is documented as "indefinite wait", but apparently cups treats is as "wait almost not at all". This issue appears to have also been filed upstream: https://github.com/apple/cups/issues/5438 Temporary workaround is to set the MaxJobTime to a very large value instead (e.g. 3 years) Trusty is not affected by this bug. To manage notifications about this bug go to: https://bugs.launchpad.net/cups/+bug/1804576/+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 1802675] Re: Nautilus progress bar don't appear when you Copy-Paste files to Desktop, and small files don't show that has been copied/moved succesfully in the circle indicator
Thank you for your bug report. Is that specific to some devices? Do you get it when copying between local directories or from other drives? What sort of disk/filesystem is it? ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1802675 Title: Nautilus progress bar don't appear when you Copy-Paste files to Desktop, and small files don't show that has been copied/moved succesfully in the circle indicator Status in nautilus package in Ubuntu: New Bug description: Hello, When i Copy/Move Files from my Ext. Hdd to the Desktop the progress bar (circle indicator) dont appear at all i know its finished by the LED light on my Ext. Hdd. In the other hand when i use the Copy To/Move To from the right click context menu the indicator with progress appear and shows the progress of the Move/Copy. Also when i Move/Copy small files the method doesn't matter in this case the circle indicator don't appear at all neither i get a message "Copied "File name" to "Destination"succesfully. I attach a video s that shows both problems. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.4-0~ubuntu18.04.2 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 NonfreeKernelModules: wl nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME Date: Sat Nov 10 21:46:15 2018 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'170' b'org.gnome.nautilus.window-state' b'geometry' b"'649x280+717+348'" InstallationDate: Installed on 2018-10-26 (15 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1802675/+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 1807197] [NEW] gdm3 doesn't remember last session
Public bug reported: gdm3 under Ubuntu 18.04 amd64 doesn't save/restore the last session you logged into, instead it always reverts to GNOME (that's the case if you have GNOME installed at least). If you want to use any other desktop it has to be manually chosen from the session menu every time you login. It should be noted that I use pbis-open (PowerBroker Identity Service) for AD authentication, because its a work machine, hence the first two lines of my /etc/nsswitch.conf look like: passwd: compat systemd lsass group: compat systemd lsass and my login/username looks like: domain\user ie With a backslash in the middle. If this is not a bug and gdm3 isn't supposed to default to using your last used session/desktop, how do I force gdm3 to default to MATE instead of GNOME? Thanks ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Description changed: gdm3 under Ubuntu 18.04 amd64 doesn't save/restore the last session you logged into, instead it always reverts to GNOME (that's the case if you - have GNOME installed at least). If you want to user any other desktop it + have GNOME installed at least). If you want to use any other desktop it has to be manually chosen from the session menu every time you login. It should be noted that I use pbis-open (PowerBroker Identity Service) for AD authentication, because its a work machine, hence the first two lines of my /etc/nsswitch.conf look like: - passwd: compat systemd lsass group: compat systemd lsass and my login/username looks like: domain\user ie With a backslash in the middle. - - If this is not a bug and gdm3 isn't supposed to default to using your last used session/desktop, how do I force gdm3 to default to MATE instead of GNOME? + If this is not a bug and gdm3 isn't supposed to default to using your + last used session/desktop, how do I force gdm3 to default to MATE + instead of GNOME? Thanks -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1807197 Title: gdm3 doesn't remember last session Status in gdm3 package in Ubuntu: New Bug description: gdm3 under Ubuntu 18.04 amd64 doesn't save/restore the last session you logged into, instead it always reverts to GNOME (that's the case if you have GNOME installed at least). If you want to use any other desktop it has to be manually chosen from the session menu every time you login. It should be noted that I use pbis-open (PowerBroker Identity Service) for AD authentication, because its a work machine, hence the first two lines of my /etc/nsswitch.conf look like: passwd: compat systemd lsass group: compat systemd lsass and my login/username looks like: domain\user ie With a backslash in the middle. If this is not a bug and gdm3 isn't supposed to default to using your last used session/desktop, how do I force gdm3 to default to MATE instead of GNOME? Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1807197/+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 1805715]
Daniel, since you are dealing with many reports on screensavers/screenlockers, have you seen this before? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1805715 Title: password exposed in calculator input box Status in gnome-screensaver package in Ubuntu: Incomplete Bug description: Plain text Linux user id password exposed in calculator input box. The first character of the password is dropped. This is reproducible as follows: 1. allow screen saver to kick in or invoke it manually with ctrl+alt+l 2. type in password 3. hit enter 4. view password in input box of calculator (less first character) Note the calculator window has the desktop focus and the input box is empty. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-calculator 1:3.18.3-0ubuntu1.16.04.1 ProcVersionSignature: Ubuntu 4.15.0-39.42~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-39-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Nov 28 16:37:44 2018 ExecutablePath: /usr/bin/gnome-calculator InstallationDate: Installed on 2018-11-14 (13 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) ProcEnviron: PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-calculator UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1805715/+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
