[Desktop-packages] [Bug 1712268] [NEW] 2 bugs
Public bug reported: non ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-32.36~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-32-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Tue Aug 22 09:01:50 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter [80ee:beef] (prog-if 00 [VGA controller]) InstallationDate: Installed on 2017-08-21 (0 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox ProcEnviron: LANGUAGE=de_DE PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-32-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Tue Aug 22 07:21:06 2017 xserver.configfile: default xserver.errors: Failed to load module "vboxvideo" (module does not exist, 0) Failed to load module "vboxvideo" (module does not exist, 0) modeset(0): glamor initialization failed AIGLX: reverting to software rendering xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.3-1ubuntu1~16.04.2 xserver.video_driver: modeset ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1712268 Title: 2 bugs Status in xorg package in Ubuntu: New Bug description: non ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-32.36~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-32-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Tue Aug 22 09:01:50 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter [80ee:beef] (prog-if 00 [VGA controller]) InstallationDate: Installed on 2017-08-21 (0 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox ProcEnviron: LANGUAGE=de_DE PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-32-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01
[Desktop-packages] [Bug 1712267] Re: nautilus crashed with signal 5 in g_object_new_valist()
*** This bug is a duplicate of bug 1692469 *** https://bugs.launchpad.net/bugs/1692469 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1692469, so 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. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1712267/+attachment/4936782/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1712267/+attachment/4936784/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1712267/+attachment/4936788/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1712267/+attachment/4936789/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1712267/+attachment/4936790/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1712267/+attachment/4936791/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1712267/+attachment/4936792/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1692469 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- 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/1712267 Title: nautilus crashed with signal 5 in g_object_new_valist() Status in nautilus package in Ubuntu: New Bug description: Not sure how or why it crashed. Only did it in the background. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: nautilus 1:3.25.90-0ubuntu1 ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5 Uname: Linux 4.12.0-11-generic x86_64 ApportVersion: 2.20.6-0ubuntu6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Aug 22 15:55:16 2017 ExecutablePath: /usr/bin/nautilus InstallationDate: Installed on 2017-08-20 (1 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcCmdline: /usr/bin/nautilus --gapplication-service ProcEnviron: XDG_RUNTIME_DIR= SHELL=/bin/bash LANGUAGE=en_AU:en PATH=(custom, no user) LANG=en_AU.UTF-8 Signal: 5 SourcePackage: nautilus StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_object_new_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_object_new () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 tracker_tokenizer_initialize () from /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so.0 Title: nautilus crashed with signal 5 in g_object_new_valist() UpgradeStatus: Upgraded to artful on 2017-08-20 (1 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1712267/+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 1712279] [NEW] Can't add google account, shows "credentials have expired"
Public bug reported: In Artful, when I try to add my google account, it seems to log in fine. When I have gone through all steps and view the online accounts, the dialog says "credentials have expired". ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-control-center 1:3.24.3-0ubuntu4 ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5 Uname: Linux 4.12.0-11-generic x86_64 ApportVersion: 2.20.6-0ubuntu6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Aug 22 09:27:59 2017 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2017-07-24 (28 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170723) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful -- 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/1712279 Title: Can't add google account, shows "credentials have expired" Status in gnome-control-center package in Ubuntu: New Bug description: In Artful, when I try to add my google account, it seems to log in fine. When I have gone through all steps and view the online accounts, the dialog says "credentials have expired". ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-control-center 1:3.24.3-0ubuntu4 ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5 Uname: Linux 4.12.0-11-generic x86_64 ApportVersion: 2.20.6-0ubuntu6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Aug 22 09:27:59 2017 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2017-07-24 (28 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170723) 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/1712279/+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 1712279] Re: Can't add google account, shows "credentials have expired"
For some reason after doing some system updates and a reboot it started to work magically! -- 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/1712279 Title: Can't add google account, shows "credentials have expired" Status in gnome-control-center package in Ubuntu: New Bug description: In Artful, when I try to add my google account, it seems to log in fine. When I have gone through all steps and view the online accounts, the dialog says "credentials have expired". ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-control-center 1:3.24.3-0ubuntu4 ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5 Uname: Linux 4.12.0-11-generic x86_64 ApportVersion: 2.20.6-0ubuntu6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Aug 22 09:27:59 2017 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2017-07-24 (28 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170723) 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/1712279/+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
Re: [Desktop-packages] [Bug 1712019] Re: Driverless printing only prints a blank sheet 17.10
Here are the two files Good luck On 21 August 2017 at 17:01, Till Kamppeter <1712...@bugs.launchpad.net> wrote: > Can you please supply the following files: > > PPD file for your printer (in /etc/cups/ppd/) on 17.04. > > PPD file for your printer (in /etc/cups/ppd/) on 17.10. > > Output of the following commands in a terminal window: > > driverless > lpstat -v > ipptool -tv get-printer-attributes.test > > The you can find in the output of the "driverless" or "lpstat > -v" commands. It is some expression starting with "ipp://..." or > "ipps://..." (on one of my printers it is > "ipp://HP5CB901E7DDC7.local:631/ipp/print"). > > Please attach the files one by one, do not compress them and do not > package them together. Thanks. > > ** Changed in: cups (Ubuntu) >Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1712019 > > Title: > Driverless printing only prints a blank sheet 17.10 > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1712019/+subscriptions > -- Rod Jones ** Attachment added: "EPSON_WF_3620_series17-10.ppd" https://bugs.launchpad.net/bugs/1712019/+attachment/4936831/+files/EPSON_WF_3620_series17-10.ppd ** Attachment added: "EPSON-WF-3620-Series17-04.ppd" https://bugs.launchpad.net/bugs/1712019/+attachment/4936832/+files/EPSON-WF-3620-Series17-04.ppd -- 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/1712019 Title: Driverless printing only prints a blank sheet 17.10 Status in cups package in Ubuntu: Incomplete Bug description: Driverless printing works perfectly in Ubuntu 17.04 with my Epson WF 3620. Scanning is also perfect. I have 17.10 on another SSD and driverless printing was working but recent updates have broken this. I reinstalled from the Aug 14th daily build and have updated it daily but printing still does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1712019/+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 1712287] [NEW] Wayland is not the default session after installation
Public bug reported: After installation of artful desktop 20170822 with gnome-session 3.24.1-0ubuntu22, x11 is still the default and there is no way to switch between wayland and x11 sessions. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: ubuntu-session 3.24.1-0ubuntu22 ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5 Uname: Linux 4.12.0-11-generic x86_64 ApportVersion: 2.20.6-0ubuntu6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Aug 22 10:42:16 2017 InstallationDate: Installed on 2013-09-03 (1448 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-session (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1712287 Title: Wayland is not the default session after installation Status in gnome-session package in Ubuntu: New Bug description: After installation of artful desktop 20170822 with gnome-session 3.24.1-0ubuntu22, x11 is still the default and there is no way to switch between wayland and x11 sessions. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: ubuntu-session 3.24.1-0ubuntu22 ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5 Uname: Linux 4.12.0-11-generic x86_64 ApportVersion: 2.20.6-0ubuntu6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Aug 22 10:42:16 2017 InstallationDate: Installed on 2013-09-03 (1448 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1712287/+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
Re: [Desktop-packages] [Bug 1712019] Re: Driverless printing only prints a blank sheet 17.10
I think these files are the same. It took me a little while to realise that on filename uses hyphens and the other underscores. Otherwise they are the same. On 22 August 2017 at 09:24, Roderic Jones wrote: > Here are the two files > > Good luck > > On 21 August 2017 at 17:01, Till Kamppeter <1712...@bugs.launchpad.net> > wrote: > >> Can you please supply the following files: >> >> PPD file for your printer (in /etc/cups/ppd/) on 17.04. >> >> PPD file for your printer (in /etc/cups/ppd/) on 17.10. >> >> Output of the following commands in a terminal window: >> >> driverless >> lpstat -v >> ipptool -tv get-printer-attributes.test >> >> The you can find in the output of the "driverless" or "lpstat >> -v" commands. It is some expression starting with "ipp://..." or >> "ipps://..." (on one of my printers it is >> "ipp://HP5CB901E7DDC7.local:631/ipp/print"). >> >> Please attach the files one by one, do not compress them and do not >> package them together. Thanks. >> >> ** Changed in: cups (Ubuntu) >>Status: New => Incomplete >> >> -- >> You received this bug notification because you are subscribed to the bug >> report. >> https://bugs.launchpad.net/bugs/1712019 >> >> Title: >> Driverless printing only prints a blank sheet 17.10 >> >> To manage notifications about this bug go to: >> https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1712019/ >> +subscriptions >> > > > > -- > Rod Jones > > -- Rod Jones -- 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/1712019 Title: Driverless printing only prints a blank sheet 17.10 Status in cups package in Ubuntu: Incomplete Bug description: Driverless printing works perfectly in Ubuntu 17.04 with my Epson WF 3620. Scanning is also perfect. I have 17.10 on another SSD and driverless printing was working but recent updates have broken this. I reinstalled from the Aug 14th daily build and have updated it daily but printing still does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1712019/+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 1712292] Re: gvfsd-mtp crashed with SIGSEGV
*** This bug is a duplicate of bug 1706097 *** https://bugs.launchpad.net/bugs/1706097 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1706097, so 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. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1712292/+attachment/4936862/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1712292/+attachment/4936864/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1712292/+attachment/4936867/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1712292/+attachment/4936868/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1712292/+attachment/4936869/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1712292/+attachment/4936870/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1712292/+attachment/4936871/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1706097 gvfsd-mtp crashed with SIGSEGV ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1712292 Title: gvfsd-mtp crashed with SIGSEGV Status in gvfs package in Ubuntu: New Bug description: I do not know when this crashed ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gvfs-backends 1.33.90-0ubuntu1 ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5 Uname: Linux 4.12.0-11-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.6-0ubuntu6 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Tue Aug 22 09:12:37 2017 ExecutablePath: /usr/lib/gvfs/gvfsd-mtp InstallationDate: Installed on 2017-07-23 (29 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170717) ProcCmdline: /usr/lib/gvfs/gvfsd-mtp --spawner :1.7 /org/gtk/gvfs/exec_spaw/3 ProcEnviron: LANG=en_GB.UTF-8 LANGUAGE=en_GB:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SegvAnalysis: Segfault happened at: 0x7f90625a7569:mov0x18(%rax),%rax PC (0x7f90625a7569) ok source "0x18(%rax)" (0x0018) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gvfs StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/gvfs/libgvfsdaemon.so ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: gvfsd-mtp crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1712292/+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 1704847] Re: orca crashes on startup
Dear all, I'm experiencing the same bug as described in comment #3. This is a bug related to the GSettings support. Best regards. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-orca in Ubuntu. https://bugs.launchpad.net/bugs/1704847 Title: orca crashes on startup Status in gnome-orca package in Ubuntu: Confirmed Bug description: Every time I run orca, it crashes immediately with the following message. - Fatal Python error: Segmentation fault Stack (most recent call first): File "/usr/lib/python3/dist-packages/pyatspi/registry.py", line 219 in registerEventListener File "/usr/lib/python3/dist-packages/orca/event_manager.py", line 410 in _registerListener File "/usr/lib/python3/dist-packages/orca/event_manager.py", line 443 in registerScriptListeners File "/usr/lib/python3/dist-packages/orca/script.py", line 269 in registerEventListeners File "/usr/lib/python3/dist-packages/orca/scripts/default.py", line 720 in registerEventListeners File "/usr/lib/python3/dist-packages/orca/script_manager.py", line 69 in activate File "/usr/lib/python3/dist-packages/orca/orca.py", line 394 in loadUserSettings File "/usr/lib/python3/dist-packages/orca/orca.py", line 514 in init File "/usr/lib/python3/dist-packages/orca/orca.py", line 696 in main File "/usr/bin/orca", line 269 in main File "/usr/bin/orca", line 272 in Segmentation fault To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-orca/+bug/1704847/+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 1698282] Re: Totem uses dramatically higher CPU than any other video player
** Changed in: totem (Ubuntu) Importance: High => Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to clutter-1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1698282 Title: Totem uses dramatically higher CPU than any other video player Status in Totem: Confirmed Status in clutter-1.0 package in Ubuntu: Confirmed Status in clutter-gst-3.0 package in Ubuntu: Confirmed Status in totem package in Ubuntu: Fix Released Bug description: Totem uses dramatically higher CPU than any other video player. Example 1: software playback under Gnome Shell Wayland: totem: 120% (but drops to 80% in Unity7) mplayer: 40% vlc: 40% [all are using ffmpeg for decoding] Example 2: hardware-accelerated playback under Gnome Shell Xorg: totem: 11% gst-play-1.0: 3% [both are using gstreamer-vaapi for decoding] Since the decoding libraries are theoretically the same it sounds like totem's performance problems might be in its rendering path. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: libgstreamer1.0-0 1.12.0-2 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:57:11 2017 InstallationDate: Installed on 2017-05-03 (44 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502) LogAlsaMixer: Error: command ['/usr/bin/amixer'] failed with exit code 1: amixer: Mixer attach default error: No such file or directory SourcePackage: gstreamer1.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/totem/+bug/1698282/+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 1704847] Re: orca crashes on startup
Orca searches for the file /usr/lib/python3/dist- packages/orca/backends/gsettings_backend.py but it doesn't exist anyware. It looks like the Ubuntu patch "0001-Add-GSettings-backend-to- Orca.patch" is the origin of the issue. The file "src/orca/backends/gsettings_backend.py" is not shipped with the Ubuntu package. Best regards. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-orca in Ubuntu. https://bugs.launchpad.net/bugs/1704847 Title: orca crashes on startup Status in gnome-orca package in Ubuntu: Confirmed Bug description: Every time I run orca, it crashes immediately with the following message. - Fatal Python error: Segmentation fault Stack (most recent call first): File "/usr/lib/python3/dist-packages/pyatspi/registry.py", line 219 in registerEventListener File "/usr/lib/python3/dist-packages/orca/event_manager.py", line 410 in _registerListener File "/usr/lib/python3/dist-packages/orca/event_manager.py", line 443 in registerScriptListeners File "/usr/lib/python3/dist-packages/orca/script.py", line 269 in registerEventListeners File "/usr/lib/python3/dist-packages/orca/scripts/default.py", line 720 in registerEventListeners File "/usr/lib/python3/dist-packages/orca/script_manager.py", line 69 in activate File "/usr/lib/python3/dist-packages/orca/orca.py", line 394 in loadUserSettings File "/usr/lib/python3/dist-packages/orca/orca.py", line 514 in init File "/usr/lib/python3/dist-packages/orca/orca.py", line 696 in main File "/usr/bin/orca", line 269 in main File "/usr/bin/orca", line 272 in Segmentation fault To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-orca/+bug/1704847/+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 1711953] Re: deja-dup-monitor crashed with signal 5 in g_settings_get_value()
@mterry I seem to get this also. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to deja-dup in Ubuntu. https://bugs.launchpad.net/bugs/1711953 Title: deja-dup-monitor crashed with signal 5 in g_settings_get_value() Status in deja-dup package in Ubuntu: Incomplete Bug description: This error was reported soon after start-up, when executing the command apt-get upgrade. The system version is "Linux richard-desktop 4.11.0-13-generic #19-Ubuntu SMP Thu Aug 3 15:14:11 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux The error occurred on date "Sun 20 Aug 21:30:32 BST 2017" ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: deja-dup 35.4-0ubuntu3 ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12 Uname: Linux 4.11.0-13-generic x86_64 ApportVersion: 2.20.6-0ubuntu6 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Sun Aug 20 21:18:29 2017 ExecutablePath: /usr/lib/x86_64-linux-gnu/deja-dup/deja-dup-monitor InstallationDate: Installed on 2017-03-30 (143 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321) ProcCmdline: /usr/lib/x86_64-linux-gnu/deja-dup/deja-dup-monitor Signal: 5 SourcePackage: deja-dup StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 g_settings_get_value () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 g_settings_get_boolean () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 deja_dup_migrate_settings () from /usr/lib/x86_64-linux-gnu/deja-dup/libdeja.so Title: deja-dup-monitor crashed with signal 5 in g_settings_get_value() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1711953/+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 1712283] Re: Cannot resolve DNS in artful daily
** Also affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Changed in: network-manager (Ubuntu) Status: New => Triaged ** Changed in: network-manager (Ubuntu) Importance: Undecided => Critical ** Changed in: network-manager (Ubuntu) Assignee: (unassigned) => Dimitri John Ledkov (xnox) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1712283 Title: Cannot resolve DNS in artful daily Status in network-manager package in Ubuntu: Triaged Status in systemd package in Ubuntu: Confirmed Bug description: in the current daily 21 Aug 2017, I can ping 8.8.8.8 from a live session / installed session - running on virtualbox 5.1.26. However I cannot ping google.com - "Name or service not known" Kind of difficult to run ubuntu-bug here without a fully functioning network. Happy to provide more details - please can someone guide me producing a much better bug-report? my zesty VM is working just fine. As of a week ago, my artful daily was working just fine also. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1712283/+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 1712283] Re: Cannot resolve DNS in artful daily
** Changed in: livecd-rootfs (Ubuntu) Importance: Undecided => Critical -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1712283 Title: Cannot resolve DNS in artful daily Status in livecd-rootfs package in Ubuntu: New Status in network-manager package in Ubuntu: Triaged Status in systemd package in Ubuntu: Confirmed Bug description: in the current daily 21 Aug 2017, I can ping 8.8.8.8 from a live session / installed session - running on virtualbox 5.1.26. However I cannot ping google.com - "Name or service not known" Kind of difficult to run ubuntu-bug here without a fully functioning network. Happy to provide more details - please can someone guide me producing a much better bug-report? my zesty VM is working just fine. As of a week ago, my artful daily was working just fine also. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1712283/+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 1712283] Re: Cannot resolve DNS in artful daily
** Also affects: livecd-rootfs (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1712283 Title: Cannot resolve DNS in artful daily Status in livecd-rootfs package in Ubuntu: New Status in network-manager package in Ubuntu: Triaged Status in systemd package in Ubuntu: Confirmed Bug description: in the current daily 21 Aug 2017, I can ping 8.8.8.8 from a live session / installed session - running on virtualbox 5.1.26. However I cannot ping google.com - "Name or service not known" Kind of difficult to run ubuntu-bug here without a fully functioning network. Happy to provide more details - please can someone guide me producing a much better bug-report? my zesty VM is working just fine. As of a week ago, my artful daily was working just fine also. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1712283/+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 1712283] Re: Cannot resolve DNS in artful daily
** Branch linked: lp:~xnox/livecd-rootfs/force-resolved-stub-resolver -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1712283 Title: Cannot resolve DNS in artful daily Status in livecd-rootfs package in Ubuntu: New Status in network-manager package in Ubuntu: Triaged Status in systemd package in Ubuntu: Confirmed Bug description: in the current daily 21 Aug 2017, I can ping 8.8.8.8 from a live session / installed session - running on virtualbox 5.1.26. However I cannot ping google.com - "Name or service not known" Kind of difficult to run ubuntu-bug here without a fully functioning network. Happy to provide more details - please can someone guide me producing a much better bug-report? my zesty VM is working just fine. As of a week ago, my artful daily was working just fine also. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1712283/+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 1539209] Re: pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume() from source_set_volume_cb() from pa_source_process_msg()
thanks, uploaded to xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1539209 Title: pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume() from source_set_volume_cb() from pa_source_process_msg() Status in PulseAudio: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Xenial: New Status in pulseaudio source package in Zesty: New Status in pulseaudio source package in Artful: Fix Released Bug description: https://errors.ubuntu.com/problem/49276ec9f717c5268dfc99940a28fb4a56fe1b4a --- [Impact] pulseaudio daemon crashes, interrupting sound output/input. [Test Case] Theoretical test case (crash does not happen for all users): 1. Find some headphones and/or microphone. Ensure you do not wear the headphones during the test as it may be loud. 2. Set audio output/input volumes to maximum. 3. Unplug and replug the headphones/microphone. 4. Check that that pulseaudio process is still running, with a start time older than when you began this test case. [Regression Potential] Low. This SRU affects the pulseaudio daemon only so the worst case would be loss of sound output/input. The same patches have been released to 17.10 for a month already and zero regressions of the crashes have occurred worldwide since then. [Original Description] Appears randomly. ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:7.1-1ubuntu3 ProcVersionSignature: Ubuntu 4.3.0-7.18-generic 4.3.3 Uname: Linux 4.3.0-7-generic x86_64 ApportVersion: 2.19.4-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: potato12883 F...m pulseaudio /dev/snd/controlC0: potato12883 F pulseaudio /dev/snd/controlC1: potato12883 F pulseaudio CurrentDesktop: Unity Date: Thu Jan 28 22:16:03 2016 ExecutablePath: /usr/bin/pulseaudio InstallationDate: Installed on 2016-01-17 (11 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog ProcEnviron: PATH=(custom, no user) SHELL=/bin/bash LANG=ru_RU.UTF-8 LANGUAGE=ru XDG_RUNTIME_DIR= Signal: 6 SourcePackage: pulseaudio StacktraceTop: pa_alsa_path_set_volume () from /usr/lib/pulse-7.1/modules/libalsa-util.so ?? () from /usr/lib/pulse-7.1/modules/libalsa-util.so pa_source_process_msg () from /usr/lib/libpulsecore-7.1.so ?? () from /usr/lib/pulse-7.1/modules/libalsa-util.so ?? () from /usr/lib/libpulsecore-7.1.so Title: pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume() UpgradeStatus: Upgraded to xenial on 2016-01-28 (0 days ago) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 12/07/2009 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: V1.11 dmi.board.name: JV71TR dmi.board.vendor: Acer dmi.board.version: Rev dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: None dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrV1.11:bd12/07/2009:svnAcer:pnAspire7540:pvr0100:rvnAcer:rnJV71TR:rvrRev:cvnAcer:ct10:cvrNone: dmi.product.name: Aspire 7540 dmi.product.version: 0100 dmi.sys.vendor: Acer modified.conffile..etc.pulse.daemon.conf: [modified] mtime.conffile..etc.pulse.daemon.conf: 2016-01-25T21:44:07.089113 To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1539209/+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 1573408] Re: GNOME Software does not install third-party .deb packages
Hi all See my outputs: alex@alex-Latitude-7480:~$ apt-cache policy gnome-software gnome-software: Installed: 3.20.5-0ubuntu0.16.04.5 Candidate: 3.20.5-0ubuntu0.16.04.5 Version table: *** 3.20.5-0ubuntu0.16.04.5 500 500 http://se.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.20.1+git20160420.1.ca63436.ubuntu-xenial-0ubuntu2 500 500 http://se.archive.ubuntu.com/ubuntu xenial/main amd64 Packages alex@alex-Latitude-7480:~$ sudo su [sudo] password for alex: root@alex-Latitude-7480:/home/alex# cat /etc/issue Ubuntu 16.04.3 LTS \n \l root@alex-Latitude-7480:/home/alex# apt update Ign:1 http://dl.google.com/linux/chrome/deb stable InRelease Hit:2 http://se.archive.ubuntu.com/ubuntu xenial InRelease Hit:3 http://dl.google.com/linux/chrome/deb stable Release Hit:4 http://se.archive.ubuntu.com/ubuntu xenial-updates InRelease Hit:5 http://se.archive.ubuntu.com/ubuntu xenial-backports InRelease Hit:6 http://archive.canonical.com/ubuntu xenial InRelease Hit:7 http://linux-packages.resilio.com/resilio-sync/deb resilio-sync InRelease Hit:8 http://ppa.launchpad.net/jtaylor/keepass/ubuntu xenial InRelease Hit:9 https://repo.skype.com/deb stable InRelease Hit:10 http://ppa.launchpad.net/remmina-ppa-team/remmina-next/ubuntu xenial InRelease Hit:11 http://ppa.launchpad.net/webupd8team/atom/ubuntu xenial InRelease Hit:13 http://security.ubuntu.com/ubuntu xenial-security InRelease Hit:14 https://dl.ring.cx/ring-nightly/ubuntu_16.04 ring InRelease Hit:15 https://packagecloud.io/slacktechnologies/slack/debian jessie InRelease Reading package lists... Done Building dependency tree Reading state information... Done All packages are up to date. root@alex-Latitude-7480:/home/alex# apt dist-upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1573408 Title: GNOME Software does not install third-party .deb packages Status in GNOME Software: Fix Released Status in gnome-software package in Ubuntu: Fix Released Status in gnome-software source package in Xenial: Fix Released Bug description: Impact installing local debs from nautilus doesn't work Test case download a deb and double click on it nautilus Regression potential the changes are restoring a feature that was working, should regression other parts of the code - Unlike previous versions of Ubuntu Unity, I'm unable to install the google-talk-plugin in Ubuntu 16.04, where it (the deb) can be downloaded here: https://www.google.com/tools/dlpage/hangoutplugin After downloading, I open the deb file from Firefox and it launches the gnome-software package (used in Unity now). The first time I click the install button in gnome-software, I notice a strange repositioning of the layout, but nothing else happens. Clicking the install button a second time puts a question-mark-progress-launcher onto the launcher (task) bar, but it never progresses: http://neartalk.com/ss/2016-04-22_001_1262x740.png So far, no one has offered a workaround: http://askubuntu.com/questions/760305/how-to-install-google-hangouts-plugin-in-ubuntu-16-04 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-software 3.20.1+git20160420.1.ca63436.ubuntu-xenial-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Fri Apr 22 01:02:45 2016 InstallationDate: Installed on 2016-04-22 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1573408/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@li
Re: [Desktop-packages] [Bug 1712019] Re: Driverless printing only prints a blank sheet 17.10
I have reinstalled Ubuntu 17.04 from the daily build available today, updated it and only installed Fish, Gdebi, Gparted and Synaptic. The problem persists. The outputs you requested are attached as a file On 22 August 2017 at 09:41, Roderic Jones wrote: > I think these files are the same. It took me a little while to realise > that on filename uses hyphens and the other underscores. Otherwise they are > the same. > > On 22 August 2017 at 09:24, Roderic Jones wrote: > >> Here are the two files >> >> Good luck >> >> On 21 August 2017 at 17:01, Till Kamppeter <1712...@bugs.launchpad.net> >> wrote: >> >>> Can you please supply the following files: >>> >>> PPD file for your printer (in /etc/cups/ppd/) on 17.04. >>> >>> PPD file for your printer (in /etc/cups/ppd/) on 17.10. >>> >>> Output of the following commands in a terminal window: >>> >>> driverless >>> lpstat -v >>> ipptool -tv get-printer-attributes.test >>> >>> The you can find in the output of the "driverless" or "lpstat >>> -v" commands. It is some expression starting with "ipp://..." or >>> "ipps://..." (on one of my printers it is >>> "ipp://HP5CB901E7DDC7.local:631/ipp/print"). >>> >>> Please attach the files one by one, do not compress them and do not >>> package them together. Thanks. >>> >>> ** Changed in: cups (Ubuntu) >>>Status: New => Incomplete >>> >>> -- >>> You received this bug notification because you are subscribed to the bug >>> report. >>> https://bugs.launchpad.net/bugs/1712019 >>> >>> Title: >>> Driverless printing only prints a blank sheet 17.10 >>> >>> To manage notifications about this bug go to: >>> https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1712019/ >>> +subscriptions >>> >> >> >> >> -- >> Rod Jones >> >> > > > -- > Rod Jones > > -- Rod Jones ** Attachment added: "printer_diagnostic" https://bugs.launchpad.net/bugs/1712019/+attachment/4937028/+files/printer_diagnostic -- 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/1712019 Title: Driverless printing only prints a blank sheet 17.10 Status in cups package in Ubuntu: Incomplete Bug description: Driverless printing works perfectly in Ubuntu 17.04 with my Epson WF 3620. Scanning is also perfect. I have 17.10 on another SSD and driverless printing was working but recent updates have broken this. I reinstalled from the Aug 14th daily build and have updated it daily but printing still does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1712019/+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 1679535] Re: ! Cannot connect to internet in Ubuntu 17.04 (DNS Lookup fails)
*** This bug is a duplicate of bug 1654918 *** https://bugs.launchpad.net/bugs/1654918 I have a similar problem in Ubuntu Server 17.04 and I just can't find a way to work out.. I am connecting to a wired internet pppoe connection. It successfully gets connected to the internet but I cannot ping outside my network nor can get any ping from outside. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1679535 Title: ! Cannot connect to internet in Ubuntu 17.04 (DNS Lookup fails) Status in network-manager package in Ubuntu: Confirmed Bug description: Hello, I think this is a bug in the WIFI-driver or kernel. Ubuntu is connected to the WIFI (router) box, but it cannot find DNS server to get to the internet. I have periodically *serious* problems with WIFI in Ubuntu 17.04. The network icon shows "connected" to the router and internet, but browsers and other attempts to get data report DNS error / or not connected. This happens in all flavours of Ubuntu 17.04 (Ubuntu, Ubuntu GNOME etc.). Same laptop with Ubuntu 16.10 works flawlessly. The connection works fine after I reboot (power off/on) the router box. Then the bug may return (or may not return) after I turn on my laptop next time. This laptop is Toshiba Stellite P50 C. The laptop has Intel Corporation Wireless 3165 (rev 81). $ lspci -nnk | grep -iA2 net; uname -r; ls /lib/firmware/ | grep 'iwlwifi-7265d' 0d:00.0 Network controller [0280]: Intel Corporation Wireless 3165 [8086:3165] (rev 81) Subsystem: Intel Corporation Dual Band Wireless AC 3165 [8086:4010] Kernel driver in use: iwlwifi -- 0e:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 0c) Subsystem: Toshiba America Info Systems RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [1179:f840] Kernel driver in use: r8169 Kernel modules: r8169 4.11.0-041100rc4-generic Ref: https://wiki.debian.org/iwlwifi Restarting the network.manager does not help. $ sudo service network-manager restart Network manager connects (and sees) to the router, but cannot access internet. - Please see also: https://ubuntuforums.org/search.php?searchid=14761184 and https://ubuntuforums.org/showthread.php?t=2356828 ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: network-manager 1.4.4-1ubuntu3 Uname: Linux 4.11.0-041100rc4-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Apr 4 08:22:23 2017 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-03-27 (8 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321) IpRoute: default via 192.168.1.1 dev wlp13s0 proto static metric 600 169.254.0.0/16 dev wlp13s0 scope link metric 1000 192.168.1.0/24 dev wlp13s0 proto kernel scope link src 192.168.1.34 metric 600 NetworkManager.conf: [main] plugins=ifupdown,keyfile [ifupdown] managed=false NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTIONCON-UUID CON-PATH wlp13s0 wifi connected/org/freedesktop/NetworkManager/Devices/2 Ubuntu-Linux-Network dda6e4cf-5cd9-4e01-b638-418985262413 /org/freedesktop/NetworkManager/ActiveConnection/5 enp14s0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/1 ------ lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/0 ------ nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.4.4connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1679535/+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 1703110] Sticky notes
Hi everyone, Sticky Notes is such a useful tool I just can't do my work without it. But haven't been able to get the latest version work because of my poor skills in Linux. I managed to do a ton of stuff but everything is a first try. Could you help me if this new fix doesn't work on my system or it is not even installed properly. I installed the latest proposed version of gnome-applets(3.22.0-2ubuntu0.2) which has the latest Sticky Notes fixes. But I'm not sure if I really installed it because it doesn't seem to work, notes still can't be closed and text selected. Here's a picture of Synaptic showing it's installed in the attachment. I followed this and set selective upgrading for proposed packages. And I installed the latest gnome-applets from terminal. Cheers, Roland ** Attachment added: "gnome-applets.png" https://bugs.launchpad.net/bugs/1703110/+attachment/4937029/+files/gnome-applets.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-applets in Ubuntu. https://bugs.launchpad.net/bugs/1703110 Title: notes doesn't delete only if empty Status in gnome-applets package in Ubuntu: Fix Released Status in gnome-applets source package in Zesty: Fix Committed Bug description: [Impact] Unnesessary work for the user as he is forced to clear the note from text in order to delete it. It makes it more difficult that selecting text isn't possible with mouse. [Test Case] - Write anything in a note - Try to select text in a note - Try to delete it with 'x' or with 'delete notes' menu item [Proposed Fix] The fix is a backport of three upstream commits: - https://git.gnome.org/browse/gnome-applets/commit/?id=85041d6567c78b4a “sticky-notes: make sure that notes are really saved” - https://git.gnome.org/browse/gnome-applets/commit/?id=0c4e0c4fed0c61bf “sticky-notes: fix path to resource file for delete dialog” - https://git.gnome.org/browse/gnome-applets/commit/?id=e189ba213c0f8db8 “sticky-notes: fix text selection” [Regression Potential] The fix definitely improves the Sticky Notes applet because without ability to save notes that applet is mostly unusable. It does not touch other applets so no regression expected there. [Other Info] System configuration: roland@roland-Lenovo-ideapad-110-15I `:+ss+:` -+ssyy+- OS: Ubuntu 17.04 x86_64 .ossdMMMNyo. Model: 80T7 Lenovo ideapad 110-15IBR /ssshdmmNNmmyNhss/ Kernel: 4.10.0-26-generic +shmydMMMNy+ Uptime: 4 hours, 45 mins /hNMMMyhhhmNMMMNh/Packages: 2360 .dMMMNhsshNMMMd. Shell: bash 4.4.7 +hhhyNMMNyyNMMMysss+ Resolution: 1366x768 ossyNMMMNyMMhsshmmmhssso DE: GNOME-Flashback:GNOME ossyNMMMNyMMhsshmmmhssso WM: Compiz +hhhyNMMNyyNMMMysss+ WM Theme: Adwaita .dMMMNhsshNMMMd. Theme: Adwaita [GTK2/3] /hNMMMyhhhdNMMMNh/Icons: Ubuntu-mono-light [GTK2/3] +sdmydy+ Terminal: gnome-terminal /ssshdmmyNhss/ CPU: Intel Pentium N3710 (4) @ 2.5GH .ossdMMMNyo. GPU: Intel HD Graphics 405 -+syyy+- Memory: 1674MiB / 3862MiB `:+ss+:` .-/+oooo+/-. Stickynotes version: 3.22.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-applets/+bug/1703110/+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 1703110] Re: notes doesn't delete only if empty
Your screenshot shows that you have installed only gnome-applets-data form proposed. gnome-applets is still at 3.22.0-2 version, but it should be also 3.22.0-2ubuntu0.2. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-applets in Ubuntu. https://bugs.launchpad.net/bugs/1703110 Title: notes doesn't delete only if empty Status in gnome-applets package in Ubuntu: Fix Released Status in gnome-applets source package in Zesty: Fix Committed Bug description: [Impact] Unnesessary work for the user as he is forced to clear the note from text in order to delete it. It makes it more difficult that selecting text isn't possible with mouse. [Test Case] - Write anything in a note - Try to select text in a note - Try to delete it with 'x' or with 'delete notes' menu item [Proposed Fix] The fix is a backport of three upstream commits: - https://git.gnome.org/browse/gnome-applets/commit/?id=85041d6567c78b4a “sticky-notes: make sure that notes are really saved” - https://git.gnome.org/browse/gnome-applets/commit/?id=0c4e0c4fed0c61bf “sticky-notes: fix path to resource file for delete dialog” - https://git.gnome.org/browse/gnome-applets/commit/?id=e189ba213c0f8db8 “sticky-notes: fix text selection” [Regression Potential] The fix definitely improves the Sticky Notes applet because without ability to save notes that applet is mostly unusable. It does not touch other applets so no regression expected there. [Other Info] System configuration: roland@roland-Lenovo-ideapad-110-15I `:+ss+:` -+ssyy+- OS: Ubuntu 17.04 x86_64 .ossdMMMNyo. Model: 80T7 Lenovo ideapad 110-15IBR /ssshdmmNNmmyNhss/ Kernel: 4.10.0-26-generic +shmydMMMNy+ Uptime: 4 hours, 45 mins /hNMMMyhhhmNMMMNh/Packages: 2360 .dMMMNhsshNMMMd. Shell: bash 4.4.7 +hhhyNMMNyyNMMMysss+ Resolution: 1366x768 ossyNMMMNyMMhsshmmmhssso DE: GNOME-Flashback:GNOME ossyNMMMNyMMhsshmmmhssso WM: Compiz +hhhyNMMNyyNMMMysss+ WM Theme: Adwaita .dMMMNhsshNMMMd. Theme: Adwaita [GTK2/3] /hNMMMyhhhdNMMMNh/Icons: Ubuntu-mono-light [GTK2/3] +sdmydy+ Terminal: gnome-terminal /ssshdmmyNhss/ CPU: Intel Pentium N3710 (4) @ 2.5GH .ossdMMMNyo. GPU: Intel HD Graphics 405 -+syyy+- Memory: 1674MiB / 3862MiB `:+ss+:` .-/+oooo+/-. Stickynotes version: 3.22.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-applets/+bug/1703110/+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 1712339] [NEW] package emacs24 24.5+1-8ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: $ uname -a Linux kucni-FL334AA-ABD-a6664de 4.10.0-32-generic #36-Ubuntu SMP Tue Aug 8 12:10:06 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux $ lsb_release -crid Distributor ID: Ubuntu Description: Ubuntu 17.04 Release: 17.04 Codename: zesty $ dpkg -l | grep emacs iU apel 10.8+0.20120427-16 all portable library for emacsen iU emacs 46.1ubuntu1 all GNU Emacs editor (metapackage) iU emacs-nox 46.1ubuntu1 all GNU Emacs editor (metapackage, without X support) iF emacs24 24.5+1-8ubuntu2 amd64 GNU Emacs editor (with GTK+ GUI support) ii emacs24-bin-common 24.5+1-8ubuntu2 amd64 GNU Emacs editor's shared, architecture dependent files ii emacs24-common 24.5+1-8ubuntu2 all GNU Emacs editor's shared, architecture independent infrastructure ii emacs24-common-non-dfsg 24.5+1-2 all GNU Emacs common non-DFSG items, including the core documentation ii emacs24-el 24.5+1-8ubuntu2 all GNU Emacs LISP (.el) files ii emacs25-bin-common 25.1+1-3ubuntu4 amd64 GNU Emacs editor's shared, architecture dependent files ii emacs25-common 25.1+1-3ubuntu4 all GNU Emacs editor's shared, architecture independent infrastructure ii emacs25-el 25.1+1-3ubuntu4 all GNU Emacs LISP (.el) files iF emacs25-nox 25.1+1-3ubuntu4 amd64 GNU Emacs editor (without GUI support) ii emacsen-common 2.0.8 all Common facilities for all emacsen kucni@kucni-FL334AA-ABD-a6664de:~$ apt-cache policy oneliner-el emacs25-nox oneliner-el: Installed: 0.3.6-7.2 Candidate: 0.3.6-7.2 Version table: *** 0.3.6-7.2 500 500 http://rs.archive.ubuntu.com/ubuntu zesty/universe amd64 Packages 500 http://rs.archive.ubuntu.com/ubuntu zesty/universe i386 Packages 100 /var/lib/dpkg/status emacs25-nox: Installed: 25.1+1-3ubuntu4 Candidate: 25.1+1-3ubuntu4 Version table: *** 25.1+1-3ubuntu4 500 500 http://rs.archive.ubuntu.com/ubuntu zesty/main amd64 Packages 100 /var/lib/dpkg/status oneliner.el problem, how to solve? ProblemType: Package DistroRelease: Ubuntu 17.04 Package: emacs24 24.5+1-8ubuntu2 ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17 Uname: Linux 4.10.0-32-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu4.5 AptOrdering: NULL: ConfigurePending Architecture: amd64 Date: Tue Aug 22 14:42:51 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2017-08-21 (0 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: emacs24 Title: package emacs24 24.5+1-8ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: emacs24 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package zesty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to emacs24 in Ubuntu. https://bugs.launchpad.net/bugs/1712339 Title: package emacs24 24.5+1-8ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in emacs24 package in Ubuntu: New Bug description: $ uname -a Linux kucni-FL334AA-ABD-a6664de 4.10.0-32-generic #36-Ubuntu SMP Tue Aug 8 12:10:06 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux $ lsb_release -crid Distributor ID: Ubuntu Description: Ubuntu 17.04 Release: 17.04 Codename: zesty $ dpkg -l | grep emacs iU apel 10.8+0.20120427-16 all portable library for emacsen iU emacs 46.1ubuntu1 all GNU Emacs editor (metapackage) iU emacs-nox 46.1ubuntu1 all GNU Emacs editor (metapackage, without X support) iF emacs24 24.5+1-8ubuntu2 amd64 GNU Emacs editor (with GTK+ GUI support) ii emacs24-bin-common 24.5+1-8ubuntu2 amd64 GNU Emacs editor's shared, architecture dependent files ii emacs24-common 24.5+1-8ubuntu2 all GNU Emacs editor's shared, architecture independent infrastructure ii emacs24-common-non-dfsg 24.5+1-2 all GNU Emacs common non-DFSG items, including the core documentation ii emacs24-el 24.5+1-8ubuntu2 all GNU Emacs LISP (.el) files ii emacs25-bin-common 25.1+1-3ubuntu4 amd64 GNU Emacs editor's shared, architecture dependent files ii emacs25-common 25.1+1-3ubuntu4 all GNU Emacs editor's shared, architecture independent infrastructure ii emacs25-el 25.1+1-3ubuntu4 all GNU Emacs LISP (.el) files iF emacs25-nox 25.1+1-3ubuntu4 amd64 GNU Emacs editor (without GUI support) ii emacsen-common 2.0.8 all Common facilities for all emacsen kucni@kucni-FL334AA-ABD-a6664de:~$ apt-cache policy oneliner-el emacs25-nox oneliner-el: Installed: 0.3.6-7.2 Candidate: 0.3.6-7.2 Version table: *** 0.3.6-7.2 500 500 http://rs.archive.ubuntu.com/ubuntu zesty/universe amd64 Packages 500 http://rs.archive.ubuntu.com/ubuntu zesty/universe i386 Packa
[Desktop-packages] [Bug 1712339] Re: package emacs24 24.5+1-8ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to emacs24 in Ubuntu. https://bugs.launchpad.net/bugs/1712339 Title: package emacs24 24.5+1-8ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in emacs24 package in Ubuntu: New Bug description: $ uname -a Linux kucni-FL334AA-ABD-a6664de 4.10.0-32-generic #36-Ubuntu SMP Tue Aug 8 12:10:06 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux $ lsb_release -crid Distributor ID: Ubuntu Description: Ubuntu 17.04 Release: 17.04 Codename: zesty $ dpkg -l | grep emacs iU apel 10.8+0.20120427-16 all portable library for emacsen iU emacs 46.1ubuntu1 all GNU Emacs editor (metapackage) iU emacs-nox 46.1ubuntu1 all GNU Emacs editor (metapackage, without X support) iF emacs24 24.5+1-8ubuntu2 amd64 GNU Emacs editor (with GTK+ GUI support) ii emacs24-bin-common 24.5+1-8ubuntu2 amd64 GNU Emacs editor's shared, architecture dependent files ii emacs24-common 24.5+1-8ubuntu2 all GNU Emacs editor's shared, architecture independent infrastructure ii emacs24-common-non-dfsg 24.5+1-2 all GNU Emacs common non-DFSG items, including the core documentation ii emacs24-el 24.5+1-8ubuntu2 all GNU Emacs LISP (.el) files ii emacs25-bin-common 25.1+1-3ubuntu4 amd64 GNU Emacs editor's shared, architecture dependent files ii emacs25-common 25.1+1-3ubuntu4 all GNU Emacs editor's shared, architecture independent infrastructure ii emacs25-el 25.1+1-3ubuntu4 all GNU Emacs LISP (.el) files iF emacs25-nox 25.1+1-3ubuntu4 amd64 GNU Emacs editor (without GUI support) ii emacsen-common 2.0.8 all Common facilities for all emacsen kucni@kucni-FL334AA-ABD-a6664de:~$ apt-cache policy oneliner-el emacs25-nox oneliner-el: Installed: 0.3.6-7.2 Candidate: 0.3.6-7.2 Version table: *** 0.3.6-7.2 500 500 http://rs.archive.ubuntu.com/ubuntu zesty/universe amd64 Packages 500 http://rs.archive.ubuntu.com/ubuntu zesty/universe i386 Packages 100 /var/lib/dpkg/status emacs25-nox: Installed: 25.1+1-3ubuntu4 Candidate: 25.1+1-3ubuntu4 Version table: *** 25.1+1-3ubuntu4 500 500 http://rs.archive.ubuntu.com/ubuntu zesty/main amd64 Packages 100 /var/lib/dpkg/status oneliner.el problem, how to solve? ProblemType: Package DistroRelease: Ubuntu 17.04 Package: emacs24 24.5+1-8ubuntu2 ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17 Uname: Linux 4.10.0-32-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu4.5 AptOrdering: NULL: ConfigurePending Architecture: amd64 Date: Tue Aug 22 14:42:51 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2017-08-21 (0 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: emacs24 Title: package emacs24 24.5+1-8ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/emacs24/+bug/1712339/+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 1219187] Re: deja-dup cannot decrypt my backup any more, GPG reports "bad session key"
*** This bug is a duplicate of bug 918489 *** https://bugs.launchpad.net/bugs/918489 After some testing, I think I know what could cause this (now very old) bug. There was a bug in deja-dup/duplicity that allowed for an accidental change in password when making the occasional full backup checkpoint (bug 918489, fixed in deja-dup 34.3). Here's how this would be reproduced, using deja-dup <= 34.2: - Create a new backup with password 'a' - Keep backing up until deja-dup decides to make a new backup. Then either have a different password saved in gnome-keyring or enter a different password when it prompts. Say, 'b' - Now you have two backup chains with different passwords, but deja-dup will keep adding new backups. - Until either your cache gets blown away or deja-dup decides to do its every-two-months backup-validation check. (Or heaven forbid, your hard drive gets blown away and you need to restore.) - When either happens, duplicity will try to download the encrypted manifest files for all the backups and deja-dup will prompt you for the decryption password. - If you enter 'a', it will choke on your second backup and show the password prompt again. If you enter 'b' it will choke on the first. Thus you get eternal backup prompts. The only way to recover is to blow away older backups (or the whole thing) and start over. If you were trying to restore, your files can be manually recovered using duplicity though. Anyway. That's my research into what this bug was likely about. I'll mark it as a dup of bug 918489. ** This bug has been marked a duplicate of bug 918489 duplicity allows bad passphrase on full backup if archive cache exists -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to deja-dup in Ubuntu. https://bugs.launchpad.net/bugs/1219187 Title: deja-dup cannot decrypt my backup any more, GPG reports "bad session key" Status in deja-dup package in Ubuntu: New Bug description: Deja-dup cannot decrypt my backup any more. This seems to be a duplicate of https://bugzilla.novell.com/show_bug.cgi?id=821767. This is the error message: Import of duplicity.backends.sshbackend Failed: No module named paramiko Synchronizing remote metadata to local cache... GnuPG passphrase: Copying duplicity-full-signatures.20130828T120049Z.sigtar.gpg to local cache. GPGError: GPG Failed, see log below: = Begin GnuPG log = gpg: CAST5 encrypted data gpg: encrypted with 1 passphrase gpg: decryption failed: Bad session key = End GnuPG log = I am *sure* my password is correct. And I have also verified the keyboard mapping did not change. I also unset GPG_AGENT_INFO and killed gpg-agent (just in case). So what can this be? Is it in fact an incorrect password or has something else gone bad? GPG 1.4.11, duplicity 0.6.18, deja-dup 22.0 ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: deja-dup 22.0-0ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-39.60~precise1-generic 3.5.7.17 Uname: Linux 3.5.0-39-generic i686 ApportVersion: 2.0.1-0ubuntu17.4 Architecture: i386 Date: Sat Aug 31 10:35:35 2013 InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release i386 (20130214) MarkForUpload: True ProcEnviron: PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: deja-dup UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1219187/+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 918489] Re: duplicity allows bad passphrase on full backup if archive cache exists
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: duplicity (Ubuntu Xenial) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/918489 Title: duplicity allows bad passphrase on full backup if archive cache exists Status in Déjà Dup: Fix Released Status in Duplicity: New Status in deja-dup package in Ubuntu: Fix Released Status in duplicity package in Ubuntu: Confirmed Status in deja-dup source package in Trusty: Fix Released Status in duplicity source package in Trusty: Confirmed Status in deja-dup source package in Xenial: Fix Released Status in duplicity source package in Xenial: Confirmed Status in deja-dup source package in Yakkety: Fix Released Status in duplicity source package in Yakkety: Confirmed Bug description: when doing a backup for the first time, dejadup verifies your passphrase by having you enter it twice. on future incremental backups it doesn't need to do this because entering the wrong password will result in the backup failing. with the periodic 'full' backups that happen from time to time, however, any password will be accepted. this can lead to a situation where you accidentally type the wrong password once and are left in a situation where you don't know what you typed and have no way to get your files (or do another incremental backup on top of it). i think this is what happened to me recently. clearly, the fix is to explicitly verify the passphrase is correct when doing a new full backup. this may be a duplicity bug. === Ubuntu deja-dup SRU information === [impact] Users may unwittingly re-set their backup password and not be able to restore their data. [test case] - $ deja-dup-preferences # set up a dummy backup - $ deja-dup --backup # complete first encrypted full backup - $ rename 's/\.2016/\.2000/' /path/to/test/backup/* - $ rename 's/\.2016/\.2000/' ~/.cache/deja-dup/*/* - $ deja-dup --backup # second backup, enter the wrong password - $ deja-dup --restore # try to restore with original password [regression potential] Should be limited? The fix is to delete the duplicity cache files, which ought to be safe to delete. It's possible if a full backup is being resumed, we might delete the current progress. That is a better bug to have than this bug, though. A more complicated patch would need to be investigated to prevent that. To manage notifications about this bug go to: https://bugs.launchpad.net/deja-dup/+bug/918489/+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 918489] Re: duplicity allows bad passphrase on full backup if archive cache exists
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: duplicity (Ubuntu Trusty) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/918489 Title: duplicity allows bad passphrase on full backup if archive cache exists Status in Déjà Dup: Fix Released Status in Duplicity: New Status in deja-dup package in Ubuntu: Fix Released Status in duplicity package in Ubuntu: Confirmed Status in deja-dup source package in Trusty: Fix Released Status in duplicity source package in Trusty: Confirmed Status in deja-dup source package in Xenial: Fix Released Status in duplicity source package in Xenial: Confirmed Status in deja-dup source package in Yakkety: Fix Released Status in duplicity source package in Yakkety: Confirmed Bug description: when doing a backup for the first time, dejadup verifies your passphrase by having you enter it twice. on future incremental backups it doesn't need to do this because entering the wrong password will result in the backup failing. with the periodic 'full' backups that happen from time to time, however, any password will be accepted. this can lead to a situation where you accidentally type the wrong password once and are left in a situation where you don't know what you typed and have no way to get your files (or do another incremental backup on top of it). i think this is what happened to me recently. clearly, the fix is to explicitly verify the passphrase is correct when doing a new full backup. this may be a duplicity bug. === Ubuntu deja-dup SRU information === [impact] Users may unwittingly re-set their backup password and not be able to restore their data. [test case] - $ deja-dup-preferences # set up a dummy backup - $ deja-dup --backup # complete first encrypted full backup - $ rename 's/\.2016/\.2000/' /path/to/test/backup/* - $ rename 's/\.2016/\.2000/' ~/.cache/deja-dup/*/* - $ deja-dup --backup # second backup, enter the wrong password - $ deja-dup --restore # try to restore with original password [regression potential] Should be limited? The fix is to delete the duplicity cache files, which ought to be safe to delete. It's possible if a full backup is being resumed, we might delete the current progress. That is a better bug to have than this bug, though. A more complicated patch would need to be investigated to prevent that. To manage notifications about this bug go to: https://bugs.launchpad.net/deja-dup/+bug/918489/+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 918489] Re: duplicity allows bad passphrase on full backup if archive cache exists
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: duplicity (Ubuntu Yakkety) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/918489 Title: duplicity allows bad passphrase on full backup if archive cache exists Status in Déjà Dup: Fix Released Status in Duplicity: New Status in deja-dup package in Ubuntu: Fix Released Status in duplicity package in Ubuntu: Confirmed Status in deja-dup source package in Trusty: Fix Released Status in duplicity source package in Trusty: Confirmed Status in deja-dup source package in Xenial: Fix Released Status in duplicity source package in Xenial: Confirmed Status in deja-dup source package in Yakkety: Fix Released Status in duplicity source package in Yakkety: Confirmed Bug description: when doing a backup for the first time, dejadup verifies your passphrase by having you enter it twice. on future incremental backups it doesn't need to do this because entering the wrong password will result in the backup failing. with the periodic 'full' backups that happen from time to time, however, any password will be accepted. this can lead to a situation where you accidentally type the wrong password once and are left in a situation where you don't know what you typed and have no way to get your files (or do another incremental backup on top of it). i think this is what happened to me recently. clearly, the fix is to explicitly verify the passphrase is correct when doing a new full backup. this may be a duplicity bug. === Ubuntu deja-dup SRU information === [impact] Users may unwittingly re-set their backup password and not be able to restore their data. [test case] - $ deja-dup-preferences # set up a dummy backup - $ deja-dup --backup # complete first encrypted full backup - $ rename 's/\.2016/\.2000/' /path/to/test/backup/* - $ rename 's/\.2016/\.2000/' ~/.cache/deja-dup/*/* - $ deja-dup --backup # second backup, enter the wrong password - $ deja-dup --restore # try to restore with original password [regression potential] Should be limited? The fix is to delete the duplicity cache files, which ought to be safe to delete. It's possible if a full backup is being resumed, we might delete the current progress. That is a better bug to have than this bug, though. A more complicated patch would need to be investigated to prevent that. To manage notifications about this bug go to: https://bugs.launchpad.net/deja-dup/+bug/918489/+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 1118446] Re: NetworkManager[14155]: nl_recvmsgs() error: (-33) Dump inconsistency detected, interrupted
Is this issue fixed? And where will I get that fix from? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1118446 Title: NetworkManager[14155]: nl_recvmsgs() error: (-33) Dump inconsistency detected, interrupted Status in network-manager package in Ubuntu: Fix Released Bug description: I see the following messages in /var/log/syslog: NetworkManager[14155]: nl_recvmsgs() error: (-33) Dump inconsistency detected, interrupted When it goes down, I have to bounce network-manager to resolve it. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: network-manager 0.9.7.995+git201301311547.17123fc-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-4.8-generic 3.8.0-rc6 Uname: Linux 3.8.0-4-generic x86_64 ApportVersion: 2.8-0ubuntu4 Architecture: amd64 Date: Thu Feb 7 08:59:00 2013 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-01-26 (12 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) IpRoute: default via 10.0.1.1 dev wlan0 proto static 10.0.1.0/24 dev wlan0 proto kernel scope link src 10.0.1.11 metric 9 169.254.0.0/16 dev wlan0 scope link metric 1000 MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to raring on 2013-01-26 (11 days ago) nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH Ubuntuac3b296c-3250-4464-8ee0-ebd6e5d8e9ca 802-11-wireless 1360249035 Thu 07 Feb 2013 08:57:15 AM CSTyes no /org/freedesktop/NetworkManager/Settings/2 Palms 2e5ef890-c77c-466e-92ee-d9dcb777cf12 802-11-wireless 1359750784 Fri 01 Feb 2013 02:33:04 PM CSTyes no /org/freedesktop/NetworkManager/Settings/1 MIA-WiFi ea25a58d-9cb8-48a8-843a-2dc3231a1e17 802-11-wireless 1359754973 Fri 01 Feb 2013 03:42:53 PM CSTyes no /org/freedesktop/NetworkManager/Settings/0 nmcli-dev: DEVICE TYPE STATE DBUS-PATH wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.7.995 connected enabled enabled enabledenabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1118446/+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 918489] Re: duplicity allows bad passphrase on full backup if archive cache exists
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: duplicity (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/918489 Title: duplicity allows bad passphrase on full backup if archive cache exists Status in Déjà Dup: Fix Released Status in Duplicity: New Status in deja-dup package in Ubuntu: Fix Released Status in duplicity package in Ubuntu: Confirmed Status in deja-dup source package in Trusty: Fix Released Status in duplicity source package in Trusty: Confirmed Status in deja-dup source package in Xenial: Fix Released Status in duplicity source package in Xenial: Confirmed Status in deja-dup source package in Yakkety: Fix Released Status in duplicity source package in Yakkety: Confirmed Bug description: when doing a backup for the first time, dejadup verifies your passphrase by having you enter it twice. on future incremental backups it doesn't need to do this because entering the wrong password will result in the backup failing. with the periodic 'full' backups that happen from time to time, however, any password will be accepted. this can lead to a situation where you accidentally type the wrong password once and are left in a situation where you don't know what you typed and have no way to get your files (or do another incremental backup on top of it). i think this is what happened to me recently. clearly, the fix is to explicitly verify the passphrase is correct when doing a new full backup. this may be a duplicity bug. === Ubuntu deja-dup SRU information === [impact] Users may unwittingly re-set their backup password and not be able to restore their data. [test case] - $ deja-dup-preferences # set up a dummy backup - $ deja-dup --backup # complete first encrypted full backup - $ rename 's/\.2016/\.2000/' /path/to/test/backup/* - $ rename 's/\.2016/\.2000/' ~/.cache/deja-dup/*/* - $ deja-dup --backup # second backup, enter the wrong password - $ deja-dup --restore # try to restore with original password [regression potential] Should be limited? The fix is to delete the duplicity cache files, which ought to be safe to delete. It's possible if a full backup is being resumed, we might delete the current progress. That is a better bug to have than this bug, though. A more complicated patch would need to be investigated to prevent that. To manage notifications about this bug go to: https://bugs.launchpad.net/deja-dup/+bug/918489/+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 1712019] Re: Driverless printing only prints a blank sheet 17.10
Please run ipptool with the full printer URI, like this: ipptool -tv ipp://EPSON25B56D.local:631/ipp/print get-printer- attributes.test > out.txt Attach the resulting output (here the file out.txt). make sure that attachments get the MIME type text/plain, as then one can easily read them in a web browser. -- 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/1712019 Title: Driverless printing only prints a blank sheet 17.10 Status in cups package in Ubuntu: Incomplete Bug description: Driverless printing works perfectly in Ubuntu 17.04 with my Epson WF 3620. Scanning is also perfect. I have 17.10 on another SSD and driverless printing was working but recent updates have broken this. I reinstalled from the Aug 14th daily build and have updated it daily but printing still does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1712019/+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 1270592] Re: backup restore test not working
*** This bug is a duplicate of bug 918489 *** https://bugs.launchpad.net/bugs/918489 After some testing, I think I know what could cause this (now very old) bug. There was a bug in deja-dup/duplicity that allowed for an accidental change in password when making the occasional full backup checkpoint (bug 918489, fixed in deja-dup 34.3). Here's how this would be reproduced, using deja-dup <= 34.2: - Create a new backup with password 'a' - Keep backing up until deja-dup decides to make a new backup. Then either have a different password saved in gnome-keyring or enter a different password when it prompts. Say, 'b' - Now you have two backup chains with different passwords, but deja-dup will keep adding new backups. - Until either your cache gets blown away or deja-dup decides to do its every-two-months backup-validation check. (Or heaven forbid, your hard drive gets blown away and you need to restore.) - When either happens, duplicity will try to download the encrypted manifest files for all the backups and deja-dup will prompt you for the decryption password. - If you enter 'a', it will choke on your second backup and show the password prompt again. If you enter 'b' it will choke on the first. Thus you get eternal backup prompts. The only way to recover is to blow away older backups (or the whole thing) and start over. If you were trying to restore, your files can be manually recovered using duplicity though. Anyway. That's my research into what this bug was likely about. I'll mark it as a dup of bug 918489 (which has been fixed for a while). ** This bug has been marked a duplicate of bug 918489 duplicity allows bad passphrase on full backup if archive cache exists -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to deja-dup in Ubuntu. https://bugs.launchpad.net/bugs/1270592 Title: backup restore test not working Status in deja-dup package in Ubuntu: New Bug description: I'm on 13.10 with an encrypted drive - every now and then, the backup program supplies apop-up asking to test the restore function (see http://imagizer.imageshack.us/v2/800x600q90/843/ot9x.png for an image of the pop-up)... It never seems to be successful - I have entered the excryption password that I use to access the drive and it never seems happy - can anyone tell me what's wrong? Thanks, Tom To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1270592/+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 1019293] Re: "gpg: can't handle text lines longer than 19995 characters" error when backing up
** Summary changed:
- deja-jup gets into ask password loop when backing up some data
+ "gpg: can't handle text lines longer than 19995 characters" error when
backing up
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to deja-dup in Ubuntu.
https://bugs.launchpad.net/bugs/1019293
Title:
"gpg: can't handle text lines longer than 19995 characters" error when
backing up
Status in deja-dup package in Ubuntu:
New
Bug description:
When I run deja-dup, and it encounters some data* it asks for the
password to be reentered, and when you do that, it tries again, and
gets in the same loop, over and over until you cancel. Nothing ends up
being backed up.
* e.g. my gpg public keyring, but when I exclude .gnupg, it has what
may be the same problem on something else too, so I think that's
coincidence.
The last part of the log is at the bottom of this, and I'll attach the
final 1000 lines. I don't think this is a duplicate of bug #883742, as
the source of the error is quite different.
DUPLICITY: DEBUG 1
DUPLICITY: . Selecting /home/robin/.gnupg/gpg.conf
DUPLICITY: DEBUG 1
DUPLICITY: . Comparing ('home', 'robin', '.gnupg', 'gpg.conf') and None
DUPLICITY: DEBUG 1
DUPLICITY: . Getting delta of (('home', 'robin', '.gnupg', 'gpg.conf')
/home/robin/.gnupg/gpg.conf reg) and None
DUPLICITY: INFO 4 'home/robin/.gnupg/gpg.conf'
DUPLICITY: . A home/robin/.gnupg/gpg.conf
DUPLICITY: DEBUG 1
DUPLICITY: . Selecting /home/robin/.gnupg/gpg.conf~
DUPLICITY: DEBUG 1
DUPLICITY: . Comparing ('home', 'robin', '.gnupg', 'gpg.conf~') and None
DUPLICITY: DEBUG 1
DUPLICITY: . Getting delta of (('home', 'robin', '.gnupg', 'gpg.conf~')
/home/robin/.gnupg/gpg.conf~ reg) and None
DUPLICITY: INFO 4 'home/robin/.gnupg/gpg.conf~'
DUPLICITY: . A home/robin/.gnupg/gpg.conf~
DUPLICITY: DEBUG 1
DUPLICITY: . Selecting /home/robin/.gnupg/pubring.gpg
DUPLICITY: DEBUG 1
DUPLICITY: . Comparing ('home', 'robin', '.gnupg', 'pubring.gpg') and None
DUPLICITY: DEBUG 1
DUPLICITY: . Getting delta of (('home', 'robin', '.gnupg', 'pubring.gpg')
/home/robin/.gnupg/pubring.gpg reg) and None
DUPLICITY: INFO 4 'home/robin/.gnupg/pubring.gpg'
DUPLICITY: . A home/robin/.gnupg/pubring.gpg
DUPLICITY: DEBUG 1
DUPLICITY: . Removing still remembered temporary file
/tmp/duplicity-_XHa0A-tempdir/mkstemp-DS0LuL-1
DUPLICITY: DEBUG 1
DUPLICITY: . Removing still remembered temporary file
/tmp/duplicity-_XHa0A-tempdir/mktemp-w2gx_c-2
DUPLICITY: INFO 1
DUPLICITY: . GPG error detail: Traceback (most recent call last):
DUPLICITY: . File "/usr/bin/duplicity", line 1403, in
DUPLICITY: . with_tempdir(main)
DUPLICITY: . File "/usr/bin/duplicity", line 1396, in with_tempdir
DUPLICITY: . fn()
DUPLICITY: . File "/usr/bin/duplicity", line 1366, in main
DUPLICITY: . full_backup(col_stats)
DUPLICITY: . File "/usr/bin/duplicity", line 500, in full_backup
DUPLICITY: . globals.backend)
DUPLICITY: . File "/usr/bin/duplicity", line 378, in write_multivol
DUPLICITY: . globals.gpg_profile, globals.volsize)
DUPLICITY: . File "/usr/lib/python2.7/dist-packages/duplicity/gpg.py", line
332, in GPGWriteFile
DUPLICITY: . file.close()
DUPLICITY: . File "/usr/lib/python2.7/dist-packages/duplicity/gpg.py", line
221, in close
DUPLICITY: . self.gpg_failed()
DUPLICITY: . File "/usr/lib/python2.7/dist-packages/duplicity/gpg.py", line
206, in gpg_failed
DUPLICITY: . raise GPGError, msg
DUPLICITY: . GPGError: GPG Failed, see log below:
DUPLICITY: . = Begin GnuPG log =
DUPLICITY: . gpg: can't handle text lines longer than 19995 characters
DUPLICITY: . = End GnuPG log =
DUPLICITY: .
DUPLICITY: .
DUPLICITY: ERROR 31 GPGError
DUPLICITY: . GPGError: GPG Failed, see log below:
DUPLICITY: . = Begin GnuPG log =
DUPLICITY: . gpg: can't handle text lines longer than 19995 characters
DUPLICITY: . = End GnuPG log =
DUPLICITY: .
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: deja-dup 22.0-0ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-25.40-generic 3.2.18
Uname: Linux 3.2.0-25-generic x86_64
ApportVersion: 2.0.1-0ubuntu8
Architecture: amd64
Date: Fri Jun 29 14:04:01 2012
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
SourcePackage: deja-dup
UpgradeStatus: Upgraded to precise on 2012-05-08 (52 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1019293/+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 1010421] Re: Text antialiasing is green.....
It seems odd gimp doesn't override the system and user's configuration of the rgba attribute to none, e.g. by providing a /etc/gimp/2.0/fonts.conf, e.g. https://gist.github.com/csaez/5d8286b134266e51c6cb76fd218d1d5d If they think that a user might want to produce a PNG with rgba set for a particular sub-pixel layout then they could have a UI choice on the text-tool's options, just as they currently have anti-alias to override the system and user. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/1010421 Title: Text antialiasing is green. Status in fontconfig package in Ubuntu: Confirmed Bug description: g. So upgraded to Gimp 2.8 and now text antialaising is green. Use white text on a black background to check it out. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1010421/+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 1712339] Re: package emacs24 24.5+1-8ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
*** This bug is a duplicate of bug 1586145 *** https://bugs.launchpad.net/bugs/1586145 ** Package changed: emacs24 (Ubuntu) => oneliner-el (Ubuntu) ** This bug has been marked a duplicate of bug 1586145 Cannot open load file: datei oder Verzeichnis nicht gefunden, poe -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to emacs24 in Ubuntu. https://bugs.launchpad.net/bugs/1712339 Title: package emacs24 24.5+1-8ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in oneliner-el package in Ubuntu: New Bug description: $ uname -a Linux kucni-FL334AA-ABD-a6664de 4.10.0-32-generic #36-Ubuntu SMP Tue Aug 8 12:10:06 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux $ lsb_release -crid Distributor ID: Ubuntu Description: Ubuntu 17.04 Release: 17.04 Codename: zesty $ dpkg -l | grep emacs iU apel 10.8+0.20120427-16 all portable library for emacsen iU emacs 46.1ubuntu1 all GNU Emacs editor (metapackage) iU emacs-nox 46.1ubuntu1 all GNU Emacs editor (metapackage, without X support) iF emacs24 24.5+1-8ubuntu2 amd64 GNU Emacs editor (with GTK+ GUI support) ii emacs24-bin-common 24.5+1-8ubuntu2 amd64 GNU Emacs editor's shared, architecture dependent files ii emacs24-common 24.5+1-8ubuntu2 all GNU Emacs editor's shared, architecture independent infrastructure ii emacs24-common-non-dfsg 24.5+1-2 all GNU Emacs common non-DFSG items, including the core documentation ii emacs24-el 24.5+1-8ubuntu2 all GNU Emacs LISP (.el) files ii emacs25-bin-common 25.1+1-3ubuntu4 amd64 GNU Emacs editor's shared, architecture dependent files ii emacs25-common 25.1+1-3ubuntu4 all GNU Emacs editor's shared, architecture independent infrastructure ii emacs25-el 25.1+1-3ubuntu4 all GNU Emacs LISP (.el) files iF emacs25-nox 25.1+1-3ubuntu4 amd64 GNU Emacs editor (without GUI support) ii emacsen-common 2.0.8 all Common facilities for all emacsen kucni@kucni-FL334AA-ABD-a6664de:~$ apt-cache policy oneliner-el emacs25-nox oneliner-el: Installed: 0.3.6-7.2 Candidate: 0.3.6-7.2 Version table: *** 0.3.6-7.2 500 500 http://rs.archive.ubuntu.com/ubuntu zesty/universe amd64 Packages 500 http://rs.archive.ubuntu.com/ubuntu zesty/universe i386 Packages 100 /var/lib/dpkg/status emacs25-nox: Installed: 25.1+1-3ubuntu4 Candidate: 25.1+1-3ubuntu4 Version table: *** 25.1+1-3ubuntu4 500 500 http://rs.archive.ubuntu.com/ubuntu zesty/main amd64 Packages 100 /var/lib/dpkg/status oneliner.el problem, how to solve? ProblemType: Package DistroRelease: Ubuntu 17.04 Package: emacs24 24.5+1-8ubuntu2 ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17 Uname: Linux 4.10.0-32-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu4.5 AptOrdering: NULL: ConfigurePending Architecture: amd64 Date: Tue Aug 22 14:42:51 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2017-08-21 (0 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: emacs24 Title: package emacs24 24.5+1-8ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/oneliner-el/+bug/1712339/+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
Re: [Desktop-packages] [Bug 1712019] Re: Driverless printing only prints a blank sheet 17.10
Is this OK? On 22 August 2017 at 14:16, Till Kamppeter <1712...@bugs.launchpad.net> wrote: > Please run ipptool with the full printer URI, like this: > > ipptool -tv ipp://EPSON25B56D.local:631/ipp/print get-printer- > attributes.test > out.txt > > Attach the resulting output (here the file out.txt). > > make sure that attachments get the MIME type text/plain, as then one can > easily read them in a web browser. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1712019 > > Title: > Driverless printing only prints a blank sheet 17.10 > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1712019/+subscriptions > -- Rod Jones ** Attachment added: "out.txt" https://bugs.launchpad.net/bugs/1712019/+attachment/4937062/+files/out.txt -- 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/1712019 Title: Driverless printing only prints a blank sheet 17.10 Status in cups package in Ubuntu: Incomplete Bug description: Driverless printing works perfectly in Ubuntu 17.04 with my Epson WF 3620. Scanning is also perfect. I have 17.10 on another SSD and driverless printing was working but recent updates have broken this. I reinstalled from the Aug 14th daily build and have updated it daily but printing still does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1712019/+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
Re: [Desktop-packages] [Bug 1703110] Re: notes doesn't delete only if empty
It works now I figured how to set it to install in synaptic. Thank you! 2017. aug. 22., k 14.34-kor-kor, Alberts Muktupāvels <1703...@bugs.launchpad.net> írta: Your screenshot shows that you have installed only gnome-applets-data form proposed. gnome-applets is still at 3.22.0-2 version, but it should be also 3.22.0-2ubuntu0.2. -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1703110 Title: notes doesn't delete only if empty Status in gnome-applets package in Ubuntu: Fix Released Status in gnome-applets source package in Zesty: Fix Committed Bug description: [Impact] Unnesessary work for the user as he is forced to clear the note from text in order to delete it. It makes it more difficult that selecting text isn't possible with mouse. [Test Case] - Write anything in a note - Try to select text in a note - Try to delete it with 'x' or with 'delete notes' menu item [Proposed Fix] The fix is a backport of three upstream commits: - https://git.gnome.org/browse/gnome-applets/commit/?id=85041d6567c78b4a “sticky-notes: make sure that notes are really saved” - https://git.gnome.org/browse/gnome-applets/commit/?id=0c4e0c4fed0c61bf “sticky-notes: fix path to resource file for delete dialog” - https://git.gnome.org/browse/gnome-applets/commit/?id=e189ba213c0f8db8 “sticky-notes: fix text selection” [Regression Potential] The fix definitely improves the Sticky Notes applet because without ability to save notes that applet is mostly unusable. It does not touch other applets so no regression expected there. [Other Info] System configuration: roland@roland-Lenovo-ideapad-110-15I `:+ss+:` -+ssyy+- OS: Ubuntu 17.04 x86_64 .ossdMMMNyo. Model: 80T7 Lenovo ideapad 110-15IBR/ssshdmmNNmmyNhss/ Kernel: 4.10.0-26-generic +shmydMMMNy+ Uptime: 4 hours, 45 mins /hNMMMyhhhmNMMMNh/ Packages: 2360 .dMMMNhsshNMMMd. Shell: bash 4.4.7 +hhhyNMMNyyNMMMysss+ Resolution: 1366x768 ossyNMMMNyMMhsshmmmhssso DE: GNOME-Flashback:GNOME ossyNMMMNyMMhsshmmmhssso WM: Compiz +hhhyNMMNyyNMMMysss+ WM Theme: Adwaita .dMMMNhsshNMMMd. Theme: Adwaita [GTK2/3] /hNMMMyhhhdNMMMNh/ Icons: Ubuntu-mono-light [GTK2/3] +sdmydy+ Terminal: gnome-terminal /ssshdmmyNhss/ CPU: Intel Pentium N3710 (4) @ 2.5GH .ossdMMMNyo. GPU: Intel HD Graphics 405 -+syyy+- Memory: 1674MiB / 3862MiB `:+ss+:` .-/+oooo+/-. Stickynotes version: 3.22.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-applets/+bug/1703110/+subscriptions -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-applets in Ubuntu. https://bugs.launchpad.net/bugs/1703110 Title: notes doesn't delete only if empty Status in gnome-applets package in Ubuntu: Fix Released Status in gnome-applets source package in Zesty: Fix Committed Bug description: [Impact] Unnesessary work for the user as he is forced to clear the note from text in order to delete it. It makes it more difficult that selecting text isn't possible with mouse. [Test Case] - Write anything in a note - Try to select text in a note - Try to delete it with 'x' or with 'delete notes' menu item [Proposed Fix] The fix is a backport of three upstream commits: - https://git.gnome.org/browse/gnome-applets/commit/?id=85041d6567c78b4a “sticky-notes: make sure that notes are really saved” - https://git.gnome.org/browse/gnome-applets/commit/?id=0c4e0c4fed0c61bf “sticky-notes: fix path to resource file for delete dialog” - https://git.gnome.org/browse/gnome-applets/commit/?id=e189ba213c0f8db8 “sticky-notes: fix text selection” [Regression Potential] The fix definitely improves the Sticky Notes applet because without ability to save notes that applet is mostly unusable. It does not touch other applets so no regression expected there. [Other Info] System configuration: roland@roland-Lenovo-ideapad-110-15I `:+ss+:` -+ssyy+- OS: Ubuntu 17.04 x86_64 .ossdMMMNyo. Model: 80T7 Lenovo ideapad 110-15IBR /ssshdmmNNmmyNhss/ Kernel: 4.10.0-26-generic +shmydMMMNy+ Uptime: 4 hours, 45 mins /hNMMMyhhhmNMMMNh/Packages: 2360 .dMMMNhsshNMMMd. Shell: bash 4.4.7 +hhhyNMMNyyNMMMysss+ Resolut
[Desktop-packages] [Bug 1703110] Re: notes doesn't delete only if empty
** Tags removed: verification-needed verification-needed-zesty ** Tags added: verification-done-zesty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-applets in Ubuntu. https://bugs.launchpad.net/bugs/1703110 Title: notes doesn't delete only if empty Status in gnome-applets package in Ubuntu: Fix Released Status in gnome-applets source package in Zesty: Fix Committed Bug description: [Impact] Unnesessary work for the user as he is forced to clear the note from text in order to delete it. It makes it more difficult that selecting text isn't possible with mouse. [Test Case] - Write anything in a note - Try to select text in a note - Try to delete it with 'x' or with 'delete notes' menu item [Proposed Fix] The fix is a backport of three upstream commits: - https://git.gnome.org/browse/gnome-applets/commit/?id=85041d6567c78b4a “sticky-notes: make sure that notes are really saved” - https://git.gnome.org/browse/gnome-applets/commit/?id=0c4e0c4fed0c61bf “sticky-notes: fix path to resource file for delete dialog” - https://git.gnome.org/browse/gnome-applets/commit/?id=e189ba213c0f8db8 “sticky-notes: fix text selection” [Regression Potential] The fix definitely improves the Sticky Notes applet because without ability to save notes that applet is mostly unusable. It does not touch other applets so no regression expected there. [Other Info] System configuration: roland@roland-Lenovo-ideapad-110-15I `:+ss+:` -+ssyy+- OS: Ubuntu 17.04 x86_64 .ossdMMMNyo. Model: 80T7 Lenovo ideapad 110-15IBR /ssshdmmNNmmyNhss/ Kernel: 4.10.0-26-generic +shmydMMMNy+ Uptime: 4 hours, 45 mins /hNMMMyhhhmNMMMNh/Packages: 2360 .dMMMNhsshNMMMd. Shell: bash 4.4.7 +hhhyNMMNyyNMMMysss+ Resolution: 1366x768 ossyNMMMNyMMhsshmmmhssso DE: GNOME-Flashback:GNOME ossyNMMMNyMMhsshmmmhssso WM: Compiz +hhhyNMMNyyNMMMysss+ WM Theme: Adwaita .dMMMNhsshNMMMd. Theme: Adwaita [GTK2/3] /hNMMMyhhhdNMMMNh/Icons: Ubuntu-mono-light [GTK2/3] +sdmydy+ Terminal: gnome-terminal /ssshdmmyNhss/ CPU: Intel Pentium N3710 (4) @ 2.5GH .ossdMMMNyo. GPU: Intel HD Graphics 405 -+syyy+- Memory: 1674MiB / 3862MiB `:+ss+:` .-/+oooo+/-. Stickynotes version: 3.22.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-applets/+bug/1703110/+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 1712357] [NEW] xorg
Public bug reported: keyboard on my laptop cant work properly, sometimes gnomes-screeshot appears suddenly ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: xorg 1:7.7+16ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17 Uname: Linux 4.10.0-32-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity:Unity7 Date: Tue Aug 22 21:53:49 2017 DistUpgraded: 2017-08-15 01:14:37,180 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: zesty DistroVariant: ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] 2nd Generation Core Processor Family Integrated Graphics Controller [1025:0724] InstallationDate: Installed on 2015-12-18 (613 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: Acer Aspire V5-471 PlymouthDebug: Error: [Errno 13] Permission denied: '/var/log/plymouth-debug.log' ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-32-generic.efi.signed root=UUID=f2ec44d4-d342-4a4c-8707-c1cd535c7931 ro splash quiet plymouth:debug SourcePackage: xorg UpgradeStatus: Upgraded to zesty on 2017-08-14 (7 days ago) dmi.bios.date: 09/07/2012 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: V1.16 dmi.board.asset.tag: No Asset Tag dmi.board.name: Aspire V5-471 dmi.board.vendor: Acer dmi.board.version: V1.16 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Acer dmi.chassis.version: V1.16 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrV1.16:bd09/07/2012:svnAcer:pnAspireV5-471:pvrV1.16:rvnAcer:rnAspireV5-471:rvrV1.16:cvnAcer:ct9:cvrV1.16: dmi.product.name: Aspire V5-471 dmi.product.version: V1.16 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.17.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.17.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Tue Aug 22 21:30:48 2017 xserver.configfile: default xserver.errors: Failed to load module "fbdev" (module does not exist, 0) Failed to load module "vesa" (module does not exist, 0) Failed to load module "fbdev" (module does not exist, 0) Failed to load module "vesa" (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.3-1ubuntu1.1 xserver.video_driver: modeset ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu zesty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1712357 Title: xorg Status in xorg package in Ubuntu: New Bug description: keyboard on my laptop cant work properly, sometimes gnomes-screeshot appears suddenly ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: xorg 1:7.7+16ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17 Uname: Linux 4.10.0-32-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity:Unity7 Date: Tue Aug 22 21:53:49 2017 DistUpgraded: 2017-08-15 01:14:37,180 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: zesty DistroVariant: ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] 2nd Generation Core Processor Family Integrated Graphics Controller [1025:0724] InstallationDate: Installed on 2015-12-18 (613 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: Acer Aspire V5-471 PlymouthDebug: Error: [Errno 13] Permission denied: '/var/log/plymouth-debug.log' ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-32-generic.efi.signed root=UUID=f2ec44d4-d342-4a4c-8707-c1cd535c7931 ro splash quiet plymouth:debug SourcePackag
[Desktop-packages] [Bug 1704533] Re: French language locale missing : Gnome-Weather
** Bug watch added: GNOME Bug Tracker #786615 https://bugzilla.gnome.org/show_bug.cgi?id=786615 ** Also affects: gnome-weather via https://bugzilla.gnome.org/show_bug.cgi?id=786615 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libgweather in Ubuntu. https://bugs.launchpad.net/bugs/1704533 Title: French language locale missing : Gnome-Weather Status in GNOME Weather: Unknown Status in Ubuntu Translations: New Status in gnome-weather package in Ubuntu: In Progress Status in libgweather package in Ubuntu: Confirmed Bug description: In Gnome Weather, part of it is not translated in french : cloudy, rain showers, etc. Should be : nuageux, pluie fine, etc. I guess it's a missing french localization. Fedora does not have that problem. In Gnome-Software, they have a section for languages, under the extensions section. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-weather/+bug/1704533/+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 1703662] Re: [MIR] rhythmbox-plugin-alternative-toolbar
** Changed in: rhythmbox-plugin-alternative-toolbar (Ubuntu) Status: Fix Committed => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1703662 Title: [MIR] rhythmbox-plugin-alternative-toolbar Status in rhythmbox package in Ubuntu: Fix Released Status in rhythmbox-plugin-alternative-toolbar package in Ubuntu: Fix Committed Status in ubuntu-settings package in Ubuntu: Fix Released Bug description: [Availability] The package is a python plugin and of type arch all, it's building fine in artful https://launchpad.net/ubuntu/+source/rhythmbox-plugin-alternative-toolbar/0.17.3-1 [Rationale] The plugin improves the look of rhythmbox and the desktop team believes it would be a welcome change to the default experience. [Security] The plugin only change UI layouts and has no known security report. [Quality assurance] The package is in sync with Debian and has no open bugs on the Debian BTS nor on launchpad. Upstream seems active though activity is rather low (but there are no open bugs or request so not a lot is needed) [Dependencies] The dependency are minimal and already in main [Standards compliance] The packaging is classic dh and using the current standards. [Maintenance] The package is well maintained upstream and in Debian, the Ubuntu Desktop team is going to keep an eye on it in Ubuntu though (desktop- bugs is subscribed) [Background information] The description summarize what the package is doing "Enhanced play controls and interface for Rhythmbox" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1703662/+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 1696079] Re: prime-select intel freezes for Ubuntu 17.04
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-prime (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1696079 Title: prime-select intel freezes for Ubuntu 17.04 Status in nvidia-prime package in Ubuntu: Confirmed Bug description: prime-select intel freezes for Ubuntu 17.04 after reboot on 17.04's default Kernel 4.10. prime-select nvidia gives the full Nvidia experience. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1696079/+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 1650788] Re: Touchpad not work: psmouse serio2: cypress_ps2: Reconnect: Unable to initialize Cypress absolute mode.
Hi @kaihengfeng With what protocol we can try? Cypress not work fine now with Synaptics, the pointer is crazy. Thanks, -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/1650788 Title: Touchpad not work: psmouse serio2: cypress_ps2: Reconnect: Unable to initialize Cypress absolute mode. Status in xserver-xorg-input-synaptics package in Ubuntu: Confirmed Bug description: Hello, Currently touching the touchpad the cursor does not move, and it seems to click, but it does not work. In the past the Cypress touchpad worked with the Synaptics controller with this solution: http://askubuntu.com/a/428316 I attach detailed files with the error logs. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xserver-xorg-input-synaptics 1.8.2-1ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30 Uname: Linux 4.4.0-53-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 CurrentDesktop: Unity Date: Sat Dec 17 19:23:30 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu InstallationDate: Installed on 2016-12-16 (1 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: SLIMBOOK KATANA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-53-generic.efi.signed root=UUID=ea770e0e-82ee-46ca-b209-a8354f155f68 ro quiet splash SourcePackage: xserver-xorg-input-synaptics UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/25/2016 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 16L dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: KATANA dmi.board.vendor: SLIMBOOK dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SLIMBOOK dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvr16L:bd07/25/2016:svnSLIMBOOK:pnKATANA:pvrTBDbyOEM:rvnSLIMBOOK:rnKATANA:rvrType2-BoardVersion:cvnSLIMBOOK:ct10:cvrChassisVersion: dmi.product.name: KATANA dmi.product.version: TBD by OEM dmi.sys.vendor: SLIMBOOK version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Sat Dec 17 19:13:30 2016 xserver.configfile: default xserver.errors: CyPS/2 Cypress Trackpad: Read error 19 CyPS/2 Cypress Trackpad: Read error 19 CyPS/2 Cypress Trackpad: Read error 19 CyPS/2 Cypress Trackpad: Read error 19 xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 38562 vendor MEI xserver.version: 2:1.18.4-0ubuntu0.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1650788/+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 1661905] Re: upstart script calls non existent file: /usr/bin/start-nvidia-persistenced
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-prime (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1661905 Title: upstart script calls non existent file: /usr/bin/start-nvidia- persistenced Status in nvidia-prime package in Ubuntu: Confirmed Bug description: The executable: /usr/bin/start-nvidia-persistenced does not actually exist. And yet /etc/init/nvidia-prime.conf calls it on boot. Which breaks boot. And that stinks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1661905/+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 1703662] Re: [MIR] rhythmbox-plugin-alternative-toolbar
** Changed in: rhythmbox-plugin-alternative-toolbar (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1703662 Title: [MIR] rhythmbox-plugin-alternative-toolbar Status in rhythmbox package in Ubuntu: Fix Released Status in rhythmbox-plugin-alternative-toolbar package in Ubuntu: Fix Committed Status in ubuntu-settings package in Ubuntu: Fix Released Bug description: [Availability] The package is a python plugin and of type arch all, it's building fine in artful https://launchpad.net/ubuntu/+source/rhythmbox-plugin-alternative-toolbar/0.17.3-1 [Rationale] The plugin improves the look of rhythmbox and the desktop team believes it would be a welcome change to the default experience. [Security] The plugin only change UI layouts and has no known security report. [Quality assurance] The package is in sync with Debian and has no open bugs on the Debian BTS nor on launchpad. Upstream seems active though activity is rather low (but there are no open bugs or request so not a lot is needed) [Dependencies] The dependency are minimal and already in main [Standards compliance] The packaging is classic dh and using the current standards. [Maintenance] The package is well maintained upstream and in Debian, the Ubuntu Desktop team is going to keep an eye on it in Ubuntu though (desktop- bugs is subscribed) [Background information] The description summarize what the package is doing "Enhanced play controls and interface for Rhythmbox" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1703662/+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
Re: [Desktop-packages] [Bug 1712019] Re: Driverless printing only prints a blank sheet 17.10
I have run the ipptool on both 17.04 and 17.10. running diff produces the following: rod@rod-desktop ~> diff out4.txt out10.txt 59c59 < printer-up-time (integer) = 146417546 --- > printer-up-time (integer) = 146414147 On 22 August 2017 at 14:38, Roderic Jones wrote: > Is this OK? > > On 22 August 2017 at 14:16, Till Kamppeter <1712...@bugs.launchpad.net> > wrote: > >> Please run ipptool with the full printer URI, like this: >> >> ipptool -tv ipp://EPSON25B56D.local:631/ipp/print get-printer- >> attributes.test > out.txt >> >> Attach the resulting output (here the file out.txt). >> >> make sure that attachments get the MIME type text/plain, as then one can >> easily read them in a web browser. >> >> -- >> You received this bug notification because you are subscribed to the bug >> report. >> https://bugs.launchpad.net/bugs/1712019 >> >> Title: >> Driverless printing only prints a blank sheet 17.10 >> >> To manage notifications about this bug go to: >> https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1712019/ >> +subscriptions >> > > > > -- > Rod Jones > > -- Rod Jones -- 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/1712019 Title: Driverless printing only prints a blank sheet 17.10 Status in cups package in Ubuntu: Incomplete Bug description: Driverless printing works perfectly in Ubuntu 17.04 with my Epson WF 3620. Scanning is also perfect. I have 17.10 on another SSD and driverless printing was working but recent updates have broken this. I reinstalled from the Aug 14th daily build and have updated it daily but printing still does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1712019/+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 1704533] Re: French language locale missing : Gnome-Weather
** Changed in: gnome-weather Status: Unknown => Confirmed ** Changed in: gnome-weather Importance: Unknown => Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libgweather in Ubuntu. https://bugs.launchpad.net/bugs/1704533 Title: French language locale missing : Gnome-Weather Status in GNOME Weather: Confirmed Status in Ubuntu Translations: New Status in gnome-weather package in Ubuntu: In Progress Status in libgweather package in Ubuntu: Confirmed Bug description: In Gnome Weather, part of it is not translated in french : cloudy, rain showers, etc. Should be : nuageux, pluie fine, etc. I guess it's a missing french localization. Fedora does not have that problem. In Gnome-Software, they have a section for languages, under the extensions section. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-weather/+bug/1704533/+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 1712283] Re: Cannot resolve DNS in artful daily
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: livecd-rootfs (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1712283 Title: Cannot resolve DNS in artful daily Status in casper package in Ubuntu: New Status in livecd-rootfs package in Ubuntu: Confirmed Status in netcfg package in Ubuntu: New Status in network-manager package in Ubuntu: Triaged Status in systemd package in Ubuntu: Confirmed Bug description: in the current daily 21 Aug 2017, I can ping 8.8.8.8 from a live session / installed session - running on virtualbox 5.1.26. However I cannot ping google.com - "Name or service not known" Kind of difficult to run ubuntu-bug here without a fully functioning network. Happy to provide more details - please can someone guide me producing a much better bug-report? my zesty VM is working just fine. As of a week ago, my artful daily was working just fine also. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1712283/+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 1589008] Re: Bluetooth freezing video playback In Ubuntu/Kubuntu 16.04
Also affects Xubuntu 16.06, 16.10 & 17.04. Potentially could/should change bug name to reflect wider generality of problem. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1589008 Title: Bluetooth freezing video playback In Ubuntu/Kubuntu 16.04 Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: In 16.04 when a bluetooth audio device is connected it freezes video playback and also no sound comes from online audio only streams. Issue does not exist with a wired headset. This issue does not exist with 15.10. All updates have been installed on 16.04 including backports but they have not fixed the issue. It is not browser specific and not website specific. It is not hardware specific as it affects my laptop with an intel 7260 card and my pc with an intel 8260 card. The issue exists on both ubuntu and kubuntu 16.04. I have reported it on the ubuntu support forums and after investigation a moderator noticed changed in the kernel from 4.4 and 4.2 that may becausing the issue and asked me to file a bug report. The ubuntu forum thread can be found here. http://ubuntuforums.org/showthread.php?t=2326672 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-23-generic 4.4.0-23.41 ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10 Uname: Linux 4.4.0-23-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: stephen1435 F pulseaudio /dev/snd/controlC0: stephen1435 F pulseaudio CurrentDesktop: KDE Date: Fri Jun 3 23:50:00 2016 HibernationDevice: RESUME=UUID=78e7aefc-d517-4c58-836f-a90f0b6017c6 InstallationDate: Installed on 2016-05-06 (28 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: MSI MS-7978 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-23-generic.efi.signed root=UUID=bccf2ca7-4e23-412a-ba10-7a3f915270dd ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-23-generic N/A linux-backports-modules-4.4.0-23-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-06-03 (0 days ago) dmi.bios.date: 05/16/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: C.60 dmi.board.asset.tag: Default string dmi.board.name: H170 GAMING M3 (MS-7978) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrC.60:bd05/16/2016:svnMSI:pnMS-7978:pvr2.0:rvnMSI:rnH170GAMINGM3(MS-7978):rvr2.0:cvnMSI:ct3:cvr2.0: dmi.product.name: MS-7978 dmi.product.version: 2.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1589008/+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 1712283] Re: Cannot resolve DNS in artful daily
** Also affects: netcfg (Ubuntu) Importance: Undecided Status: New ** Changed in: netcfg (Ubuntu) Importance: Undecided => Critical ** Also affects: casper (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1712283 Title: Cannot resolve DNS in artful daily Status in casper package in Ubuntu: New Status in livecd-rootfs package in Ubuntu: Confirmed Status in netcfg package in Ubuntu: New Status in network-manager package in Ubuntu: Triaged Status in systemd package in Ubuntu: Confirmed Bug description: in the current daily 21 Aug 2017, I can ping 8.8.8.8 from a live session / installed session - running on virtualbox 5.1.26. However I cannot ping google.com - "Name or service not known" Kind of difficult to run ubuntu-bug here without a fully functioning network. Happy to provide more details - please can someone guide me producing a much better bug-report? my zesty VM is working just fine. As of a week ago, my artful daily was working just fine also. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1712283/+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 1712283] Re: Cannot resolve DNS in artful daily
** Changed in: network-manager (Ubuntu) Importance: Critical => Medium ** Changed in: systemd (Ubuntu) Assignee: (unassigned) => Dimitri John Ledkov (xnox) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1712283 Title: Cannot resolve DNS in artful daily Status in casper package in Ubuntu: New Status in livecd-rootfs package in Ubuntu: Confirmed Status in netcfg package in Ubuntu: New Status in network-manager package in Ubuntu: Triaged Status in systemd package in Ubuntu: Confirmed Bug description: in the current daily 21 Aug 2017, I can ping 8.8.8.8 from a live session / installed session - running on virtualbox 5.1.26. However I cannot ping google.com - "Name or service not known" Kind of difficult to run ubuntu-bug here without a fully functioning network. Happy to provide more details - please can someone guide me producing a much better bug-report? my zesty VM is working just fine. As of a week ago, my artful daily was working just fine also. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1712283/+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 1712283] Re: Cannot resolve DNS in artful daily
** Description changed: in the current daily 21 Aug 2017, I can ping 8.8.8.8 from a live session / installed session - running on virtualbox 5.1.26. However I cannot ping google.com - "Name or service not known" Kind of difficult to run ubuntu-bug here without a fully functioning network. Happy to provide more details - please can someone guide me producing a much better bug-report? my zesty VM is working just fine. As of a week ago, my artful daily was working just fine also. + + + + + * /etc/resolv.conf is empty file on most images built, which is not right, it should point to ../run/systemd/resolve/stub-resolv.conf. Should be fixed in image generation? systemd? + + * Adding a hack, to create /etc/resolv.conf if it does not exist, or is + empty. src:systemd + + * network-manager does not consider that dns is managed by resolved if + .53 is present in /etc/resolv.conf or if it points to stub-resolv.conf. + src:network-manager + + * netcfg has integrtation w.r.t. /etc/resolv.conf and resolvconf. Needs + checking / fixing + + * caster has resolvconf integration + + * livecd-rootfs has resolvconf integration -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1712283 Title: Cannot resolve DNS in artful daily Status in casper package in Ubuntu: New Status in livecd-rootfs package in Ubuntu: Confirmed Status in netcfg package in Ubuntu: New Status in network-manager package in Ubuntu: Triaged Status in systemd package in Ubuntu: Confirmed Bug description: in the current daily 21 Aug 2017, I can ping 8.8.8.8 from a live session / installed session - running on virtualbox 5.1.26. However I cannot ping google.com - "Name or service not known" Kind of difficult to run ubuntu-bug here without a fully functioning network. Happy to provide more details - please can someone guide me producing a much better bug-report? my zesty VM is working just fine. As of a week ago, my artful daily was working just fine also. * /etc/resolv.conf is empty file on most images built, which is not right, it should point to ../run/systemd/resolve/stub-resolv.conf. Should be fixed in image generation? systemd? * Adding a hack, to create /etc/resolv.conf if it does not exist, or is empty. src:systemd * network-manager does not consider that dns is managed by resolved if .53 is present in /etc/resolv.conf or if it points to stub- resolv.conf. src:network-manager * netcfg has integrtation w.r.t. /etc/resolv.conf and resolvconf. Needs checking / fixing * caster has resolvconf integration * livecd-rootfs has resolvconf integration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1712283/+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 1368640] Re: When backup system, need to click cancel button twice to close Encryption Password Needed page.
Thanks for the bug! This should be fixed in master now. ** Changed in: deja-dup Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to deja-dup in Ubuntu. https://bugs.launchpad.net/bugs/1368640 Title: When backup system, need to click cancel button twice to close Encryption Password Needed page. Status in Déjà Dup: Fix Committed Status in Ubuntu Kylin: New Status in deja-dup package in Ubuntu: New Bug description: When backup system, need to click cancel button twice to close Encryption Password Needed page. You must backuped your system with encryption before. Steps: 1. Enter into System settings-->Backup, 2. Click back up now, backup the system with encryption 3. Click the back up now button again, 4. Click cancel button in Encryption Password Needed page -->Failed. Need to click cancel button twice to close Encryption Password Needed page. Configuration: PC: Dell Vostro OS: Ubuntu kylin 14.10 daily 0912 To manage notifications about this bug go to: https://bugs.launchpad.net/deja-dup/+bug/1368640/+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 932177] Re: XFCE (and other non-GNOME) desktops do not initialise gnome-keyring correctly / WARNING: gnome-keyring:: couldn't connect to PKCS11
Facing the same. gnome-keyring-daemon often fails to start, if it manages to start it asks for Login keyring password. BTW gnome-keyring-daemon always starts from root, even if I run it from user in terminal! xubuntu 16.04, it became broken in these two months. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/932177 Title: XFCE (and other non-GNOME) desktops do not initialise gnome-keyring correctly / WARNING: gnome-keyring:: couldn't connect to PKCS11 Status in GNOME Keyring: Fix Released Status in xfce4-session: Unknown Status in Xubuntu: New Status in gnome-keyring package in Ubuntu: Invalid Status in kde-workspace package in Ubuntu: Fix Released Status in xfce4-session package in Ubuntu: Fix Released Status in gnome-keyring package in Debian: Confirmed Status in gnome-keyring package in Fedora: Unknown Status in gnome-keyring package in openSUSE: Fix Released Bug description: precise + fluxbox (without gnome-settings-daemon) Postler when sending a message writes: Failed to send a message WARNING: gnome-keyring:: couldn't connect to: /tmp/keyring-rof1VB/pkcs11: No such file or directory In gnome-system-monitor: /usr/bin/gnome-keyring-demon --start --foreground --components=secrets /usr/bin/gnome-keyring-demon --daemonize --login with manual start this: OK /usr/bin/gnome-keyring-daemon --start --components=pkcs11 Is it possible to add a string key '--components=pkcs11', so that the gnome-system-monitor was: /usr/bin/gnome-keyring-demon --start --foreground --components=secrets --components=pkcs11 thanks in advance... ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gnome-keyring 3.2.2-2ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-15.24-generic 3.2.5 Uname: Linux 3.2.0-15-generic x86_64 ApportVersion: 1.91-0ubuntu1 Architecture: amd64 Date: Tue Feb 14 17:47:35 2012 InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) ProcEnviron: PATH=(custom, no user) LANG=ru_UA.UTF-8 SHELL=/bin/bash SourcePackage: gnome-keyring UpgradeStatus: Upgraded to precise on 2012-02-10 (3 days ago) mtime.conffile..etc.xdg.autostart.gnome.keyring.gpg.desktop: 2012-02-14T14:17:23.632015 mtime.conffile..etc.xdg.autostart.gnome.keyring.pkcs11.desktop: 2012-02-14T14:17:23.632015 mtime.conffile..etc.xdg.autostart.gnome.keyring.secrets.desktop: 2012-02-14T14:17:23.632015 mtime.conffile..etc.xdg.autostart.gnome.keyring.ssh.desktop: 2012-02-14T14:17:23.636015 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-keyring/+bug/932177/+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 1690407] Re: Dragging icons on desktop pulls a part of background as well (Artful)
*** This bug is a duplicate of bug 1710999 *** https://bugs.launchpad.net/bugs/1710999 So this is fixed in bug #1710999 ? Marking this as duplicate. ** This bug has been marked a duplicate of bug 1710999 Dragging icons don't have transparent backgrounds -- 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/1690407 Title: Dragging icons on desktop pulls a part of background as well (Artful) Status in caja package in Ubuntu: Triaged Status in nautilus package in Ubuntu: Confirmed Bug description: I am reporting this for artful but it is present for all nautilus >=3.18. Issue : --- While dragging icons on desktop it pulls part of desktop as well. http://i.imgur.com/lr0KQps.png Possible Reason: See Mate issue here: https://github.com/mate-desktop/caja/issues/575 Upstream bug: https://bugzilla.gnome.org/show_bug.cgi?id=768415 From that issue, "Beginning with the various GdkDrawingContext changes to GTK during the 3.21.2 cycle, the desktop background in Caja/Nautilus/Nemo has become "persistant" with a failure to redraw and "erase" when any icon is moved. Possible Related Commit: 1) https://git.gnome.org/browse/gtk+/commit/?id=2c7b21718f18ab743cd79784ae28cad582f58503 2) https://github.com/GNOME/nautilus/commit/6d6bf1e7c6049b4bd300ae1d90833a8b5fcf30c4 3) https://github.com/GNOME/nautilus/commit/f0f36c876e4810b190a82e3a953d9263c106447f How mate fixed it: -- 1) Patching msd: https://github.com/mate-desktop/mate-settings-daemon/pull/157 2) Patching caja: https://github.com/mate-desktop/caja/pull/602 While it may not present a problem for shell (as shell will draw the desktop and nautilus will draw the icons on it), it is still a issue for any non mutter session. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/caja/+bug/1690407/+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 1589008] Re: Bluetooth freezing video playback In Ubuntu/Kubuntu 16.04
I have the same problem on a fresh installation of kubuntu 17.04, -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1589008 Title: Bluetooth freezing video playback In Ubuntu/Kubuntu 16.04 Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: In 16.04 when a bluetooth audio device is connected it freezes video playback and also no sound comes from online audio only streams. Issue does not exist with a wired headset. This issue does not exist with 15.10. All updates have been installed on 16.04 including backports but they have not fixed the issue. It is not browser specific and not website specific. It is not hardware specific as it affects my laptop with an intel 7260 card and my pc with an intel 8260 card. The issue exists on both ubuntu and kubuntu 16.04. I have reported it on the ubuntu support forums and after investigation a moderator noticed changed in the kernel from 4.4 and 4.2 that may becausing the issue and asked me to file a bug report. The ubuntu forum thread can be found here. http://ubuntuforums.org/showthread.php?t=2326672 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-23-generic 4.4.0-23.41 ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10 Uname: Linux 4.4.0-23-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: stephen1435 F pulseaudio /dev/snd/controlC0: stephen1435 F pulseaudio CurrentDesktop: KDE Date: Fri Jun 3 23:50:00 2016 HibernationDevice: RESUME=UUID=78e7aefc-d517-4c58-836f-a90f0b6017c6 InstallationDate: Installed on 2016-05-06 (28 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: MSI MS-7978 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-23-generic.efi.signed root=UUID=bccf2ca7-4e23-412a-ba10-7a3f915270dd ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-23-generic N/A linux-backports-modules-4.4.0-23-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-06-03 (0 days ago) dmi.bios.date: 05/16/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: C.60 dmi.board.asset.tag: Default string dmi.board.name: H170 GAMING M3 (MS-7978) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrC.60:bd05/16/2016:svnMSI:pnMS-7978:pvr2.0:rvnMSI:rnH170GAMINGM3(MS-7978):rvr2.0:cvnMSI:ct3:cvr2.0: dmi.product.name: MS-7978 dmi.product.version: 2.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1589008/+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 1712019] Re: Driverless printing only prints a blank sheet 17.10
The problem you see in the PPDs. Resolutions are different. So can you try to set the Print Quality to Draft to see whether it prints? Another test is creating a new queue with the OLD PPD file. Can you print with this queue, Print Quality set to Norml or High? -- 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/1712019 Title: Driverless printing only prints a blank sheet 17.10 Status in cups package in Ubuntu: Incomplete Bug description: Driverless printing works perfectly in Ubuntu 17.04 with my Epson WF 3620. Scanning is also perfect. I have 17.10 on another SSD and driverless printing was working but recent updates have broken this. I reinstalled from the Aug 14th daily build and have updated it daily but printing still does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1712019/+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 1711241] Re: Unity support patch doesn't build with nautilus 3.25.90
I was under impression that unity is gone from main support. So what is with libunity dependency in nautilus 3.25? Version 3.24 was working fine without it. And nautilus should be without those header bar patches. Please leave it as it is. -- 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/1711241 Title: Unity support patch doesn't build with nautilus 3.25.90 Status in nautilus package in Ubuntu: Fix Released Bug description: I have prepared nautilus 3.25.90 in the GNOME3 Staging PPA for Ubuntu 17.10 "artful". The 12_unity_launcher_support.patch has a problem that fails the build and I don't know how to fix it so I disabled the patch for now. Nautilus 3.25 introduces meson support and drops autotools support so that's one factor when I updated the patch. But when I disable the patch, nautilus crashes on start in Unity. Build log attached. Build Log Excerpt == [164/222] cc -Isrc/nautilus@sta -Isrc -Isubprojects/libgd/libgd -I../src -I. -I../ -Isubprojects/libgd -I../subprojects/libgd -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/gtk-3.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/mirclient -I/usr/include/mircore -I/usr/include/mircookie -I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 -I/usr/include/gnome-autoar-0 -I/usr/include/libxml2 -I/usr/include/zeitgeist-2.0 -I/usr/include/gsettings-desktop-schemas -I/usr/include/gail-3.0 -I/usr/include/gnome-desktop-3.0 -I/usr/include/tracker-2.0 -I/usr/include/tracker-2.0/libtracker-sparql -I/usr/include/libexif -I/usr/include/unity/unity -I/usr/include/dee-1.0 -I/usr/include/libdbusmenu-glib-0.4 -I/usr/include/exempi-2.0 -fdiagnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 -Wno-deprecated-declarations -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -DLIBGD_GTK_HACKS=1 -DLIBGD__VIEW_COMMON=1 -DLIBGD_MAIN_ICON_VIEW=1 -DLIBGD_MAIN_LIST_VIEW=1 -DLIBGD_MAIN_VIEW=1 -DLIBGD_TAGGED_ENTRY=1 -MMD -MQ 'src/nautilus@sta/unity-quicklist-handler.c.o' -MF 'src/nautilus@sta/unity-quicklist-handler.c.o.d' -o 'src/nautilus@sta/unity-quicklist-handler.c.o' -c ../src/unity-quicklist-handler.c FAILED: src/nautilus@sta/unity-quicklist-handler.c.o cc -Isrc/nautilus@sta -Isrc -Isubprojects/libgd/libgd -I../src -I. -I../ -Isubprojects/libgd -I../subprojects/libgd -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/gtk-3.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/mirclient -I/usr/include/mircore -I/usr/include/mircookie -I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 -I/usr/include/gnome-autoar-0 -I/usr/include/libxml2 -I/usr/include/zeitgeist-2.0 -I/usr/include/gsettings-desktop-schemas -I/usr/include/gail-3.0 -I/usr/include/gnome-desktop-3.0 -I/usr/include/tracker-2.0 -I/usr/include/tracker-2.0/libtracker-sparql -I/usr/include/libexif -I/usr/include/unity/unity -I/usr/include/dee-1.0 -I/usr/include/libdbusmenu-glib-0.4 -I/usr/include/exempi-2.0 -fdiagnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 -Wno-deprecated-declarations -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -DLIBGD_GTK_HACKS=1 -DLIBGD__VIEW_COMMON=1 -DLIBGD_MAIN_ICON_VIEW=1 -DLIBGD_MAIN_LIST_VIEW=1 -DLIBGD_MAIN_VIEW=1 -DLIBGD_TAGGED_ENTRY=1 -MMD -MQ 'src/nautilus@sta/unity-quicklist-handler.c.o' -MF 'src/nautilus@sta/unity-quicklist-handler.c.o.d' -o 'src/nautilus@sta/unity-quicklist-handler.c.o' -c ../src/unity-quicklist-handler.c ../src/unity-quicklist-handler.c: In function ‘unity_quicklist_handler_get_singleton’: ../src/unity-quicklist-handler.c:154:9: error: expected declaration or statement at end of input unity_quicklist_handler_singleton = unity_quicklist_handler_new (); ^ ../src/unity-quicklist-handler.c:154:9: error: expected declaration or statement at end of input To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1711241/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages M
[Desktop-packages] [Bug 1703662] Re: [MIR] rhythmbox-plugin-alternative-toolbar
Override component to main rhythmbox-plugin-alternative-toolbar 0.17.4-1 in artful: universe/misc -> main rhythmbox-plugin-alternative-toolbar 0.17.4-1 in artful amd64: universe/misc/optional/100% -> main rhythmbox-plugin-alternative-toolbar 0.17.4-1 in artful arm64: universe/misc/optional/100% -> main rhythmbox-plugin-alternative-toolbar 0.17.4-1 in artful armhf: universe/misc/optional/100% -> main rhythmbox-plugin-alternative-toolbar 0.17.4-1 in artful i386: universe/misc/optional/100% -> main rhythmbox-plugin-alternative-toolbar 0.17.4-1 in artful ppc64el: universe/misc/optional/100% -> main rhythmbox-plugin-alternative-toolbar 0.17.4-1 in artful s390x: universe/misc/optional/100% -> main 7 publications overridden. ** Changed in: rhythmbox-plugin-alternative-toolbar (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1703662 Title: [MIR] rhythmbox-plugin-alternative-toolbar Status in rhythmbox package in Ubuntu: Fix Released Status in rhythmbox-plugin-alternative-toolbar package in Ubuntu: Fix Released Status in ubuntu-settings package in Ubuntu: Fix Released Bug description: [Availability] The package is a python plugin and of type arch all, it's building fine in artful https://launchpad.net/ubuntu/+source/rhythmbox-plugin-alternative-toolbar/0.17.3-1 [Rationale] The plugin improves the look of rhythmbox and the desktop team believes it would be a welcome change to the default experience. [Security] The plugin only change UI layouts and has no known security report. [Quality assurance] The package is in sync with Debian and has no open bugs on the Debian BTS nor on launchpad. Upstream seems active though activity is rather low (but there are no open bugs or request so not a lot is needed) [Dependencies] The dependency are minimal and already in main [Standards compliance] The packaging is classic dh and using the current standards. [Maintenance] The package is well maintained upstream and in Debian, the Ubuntu Desktop team is going to keep an eye on it in Ubuntu though (desktop- bugs is subscribed) [Background information] The description summarize what the package is doing "Enhanced play controls and interface for Rhythmbox" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1703662/+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 1653776] Re: remove imagemagick dependency
** Changed in: cups-filters (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups-filters in Ubuntu. https://bugs.launchpad.net/bugs/1653776 Title: remove imagemagick dependency Status in cups-filters package in Ubuntu: Fix Released Bug description: Please remove imagemagick dependency in cups-filters. Exploit after exploit, just because someone thinks printing to braille should be default for all ubuntu installation. /* Ubuntu tries supporting every obscure codecs, formats with programs/libs coded in thousands lines of crappy C code. If ubuntu had market share comparable to windows, ... */ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1653776/+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 1579504] Re: split gvfs-backend
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gvfs (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1579504 Title: split gvfs-backend Status in gvfs package in Ubuntu: Confirmed Bug description: Why dont you split gvfs backends to multiple packages like fedora does? •gvfs-afc •gvfs-afp •gvfs-archive •gvfs-client •gvfs-fuse •gvfs-goa •gvfs-gphoto2 •gvfs-mtp •gvfs-smb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1579504/+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 1712390] [NEW] nautilus ubuntu 17.10 remove libunity dependency
Public bug reported: I was under impression that unity is gone from main support. So what is with libunity dependency in nautilus 3.25? Version 3.24 was working fine without it. And nautilus(and probably others gnome apps) should be without those headerbar/titlebar patches. Please leave it as it is. If someone wants to use nautilus in other desktop it probably wants to use like it was meant to be(I know you could use export XDG_CURRENT_DESKTOP=GNOME, but why force ugly, out of place title bar for gnome apps designed not to use one... ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New -- 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/1712390 Title: nautilus ubuntu 17.10 remove libunity dependency Status in nautilus package in Ubuntu: New Bug description: I was under impression that unity is gone from main support. So what is with libunity dependency in nautilus 3.25? Version 3.24 was working fine without it. And nautilus(and probably others gnome apps) should be without those headerbar/titlebar patches. Please leave it as it is. If someone wants to use nautilus in other desktop it probably wants to use like it was meant to be(I know you could use export XDG_CURRENT_DESKTOP=GNOME, but why force ugly, out of place title bar for gnome apps designed not to use one... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1712390/+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 1586528] Re: Avahi-daemon withdraws address record
I am seeing the same problem on a physical host running Linux Mint. I too have found that clicking the network icon to toggle it off and back on can restore connections. Additionally, I have found that the connection may be restored without intervention, given sufficient time (potentially hours). Sorry that this is a long post - when trying to add an attachment, the U.R.L. was not found. I have tried to provide anything that may be relevant. The connection was lost at 03:57:51, and regained at 04:24. The computers featured are yoyo, 192.168.42.187, 00:25:64:72:72:14, the Linux Mint computer, and kevin, 192.168.42.129, 00:50:04:23:f7:80, the D.H.C.P. server and Internet gateway. [LinuxMint] graham@yoyo $ cat /etc/network/interfaces # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback Tue Aug 22 17:57:47 ~ [LinuxMint] graham@yoyo $ lspci | grep -i "net" 09:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8040 PCI-E Fast Ethernet Controller (rev 13) 0c:00.0 Network controller: Broadcom Corporation BCM4312 802.11b/g LP-PHY (rev 01) Tue Aug 22 17:59:23 ~ The Broadcom wireless adaptor is not active. [LinuxMint] graham@yoyo $ cat /etc/os-release NAME="Linux Mint" VERSION="18 (Sarah)" ID=linuxmint ID_LIKE=ubuntu PRETTY_NAME="Linux Mint 18" VERSION_ID="18" HOME_URL="http://www.linuxmint.com/"; SUPPORT_URL="http://forums.linuxmint.com/"; BUG_REPORT_URL="http://bugs.launchpad.net/linuxmint/"; UBUNTU_CODENAME=xenial Tue Aug 22 17:48:57 ~ [LinuxMint] graham@yoyo $ uname -a Linux yoyo 4.4.0-21-generic #37-Ubuntu SMP Mon Apr 18 18:33:37 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux Tue Aug 22 18:04:00 ~ Here is a excerpt from kern.log, showing that the D.H.C.P. lease was not renewed and the network connection was lost:- Aug 21 03:00:30 yoyo NetworkManager[1049]: [1503280830.6457] dhcp4 (eth0): state changed bound -> bound Aug 21 03:13:25 yoyo NetworkManager[1049]: [1503281605.4009] address 192.168.42.187 Aug 21 03:13:25 yoyo NetworkManager[1049]: [1503281605.4009] plen 25 (255.255.255.128) Aug 21 03:13:25 yoyo NetworkManager[1049]: [1503281605.4010] gateway 192.168.42.129 Aug 21 03:13:25 yoyo NetworkManager[1049]: [1503281605.4010] server identifier 192.168.42.129 Aug 21 03:13:25 yoyo NetworkManager[1049]: [1503281605.4010] lease time 1800 Aug 21 03:13:25 yoyo NetworkManager[1049]: [1503281605.4010] nameserver '192.168.42.129' Aug 21 03:13:25 yoyo NetworkManager[1049]: [1503281605.4011] nameserver '192.168.42.248' Aug 21 03:13:25 yoyo NetworkManager[1049]: [1503281605.4011] domain name 'example.net' Aug 21 03:13:25 yoyo NetworkManager[1049]: [1503281605.5497] dhcp4 (eth0 ): state changed bound -> bound Aug 21 03:27:49 yoyo NetworkManager[1049]: [1503282469.5210] address 192.168.42.187 Aug 21 03:27:49 yoyo NetworkManager[1049]: [1503282469.5211] plen 25 (255.255.255.128) Aug 21 03:27:49 yoyo NetworkManager[1049]: [1503282469.5211] gateway 192.168.42.129 Aug 21 03:27:49 yoyo NetworkManager[1049]: [1503282469.5211] server identifier 192.168.42.129 Aug 21 03:27:49 yoyo NetworkManager[1049]: [1503282469.5212] lease time 1800 Aug 21 03:27:49 yoyo NetworkManager[1049]: [1503282469.5212] nameserver '192.168.42.129' Aug 21 03:27:49 yoyo NetworkManager[1049]: [1503282469.5212] nameserver '192.168.42.248' Aug 21 03:27:49 yoyo NetworkManager[1049]: [1503282469.5212] domain name 'example.net' Aug 21 03:27:49 yoyo NetworkManager[1049]: [1503282469.5213] dhcp4 (eth0): state changed bound -> bound Aug 21 04:00:55 yoyo kernel: [2364015.580056] nfs: server gerald not responding, timed out Aug 21 04:03:55 yoyo kernel: [2364195.804051] nfs: server gerald not responding, timed out Here is a (slightly edited) excerpt from the same period in syslog:- Aug 21 03:27:48 yoyo dhclient[6325]: DHCPREQUEST of 192.168.42.187 on eth0 to 192.168.42.129 port 67 (xid=0x4ce954e5) Aug 21 03:27:48 yoyo dhclient[6325]: DHCPACK of 192.168.42.187 from 192.168.42.129 Aug 21 03:27:49 yoyo NetworkManager[1049]: [1503282469.5210] address 192.168.42.187 Aug 21 03:27:49 yoyo NetworkManager[1049]: [1503282469.5211] plen 25 (255.255.255.128) Aug 21 03:27:49 yoyo NetworkManager[1049]: [1503282469.5211] gateway 192.168.42.129 Aug 21 03:27:49 yoyo dhclient[6325]: bound to 192.168.42.187 -- renewal in 868 seconds. Aug 21 03:27:49 yoyo NetworkManager[1049]: [1503282469.5211] server identifier 192.168.42.129 Aug 21 03:27:49 yoyo NetworkManager[1049]: [1503282469.5212] lease time 1800 Aug 21 03:27:49 yoyo NetworkManager[1049]: [1503282469.5212] nameserver '192.168.42.129' Aug 21 03:27:49 yoyo NetworkManager[1049]: [1503282469.5212] nameserver '192.168.42.248' Aug 21 03:27:49 yoyo NetworkManager[1049]: [1503282469.5212] domain name 'example.net' Aug 21 03:27:49 yoyo NetworkManager[1049]: [1503282469.5213] dhcp4 (eth0): state changed bound -> bound Aug 21 03:27:49 yoyo dbus[999]: [system] Activ
[Desktop-packages] [Bug 1712392] [NEW] New release 5.0.2RC2
Public bug reported: Hello, https://wiki.documentfoundation.org/Releases/5.0.2/RC2 Regards, -- Cristian ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: libreoffice-gnome 1:5.3.4-0ubuntu1 Uname: Linux 4.13.0-041300rc6-generic x86_64 ApportVersion: 2.20.6-0ubuntu6 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Aug 22 14:05:43 2017 InstallationDate: Installed on 2017-07-05 (47 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: libreoffice UpgradeStatus: Upgraded to artful on 2017-07-05 (47 days ago) ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful upgrade-software-version -- 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/1712392 Title: New release 5.0.2RC2 Status in libreoffice package in Ubuntu: New Bug description: Hello, https://wiki.documentfoundation.org/Releases/5.0.2/RC2 Regards, -- Cristian ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: libreoffice-gnome 1:5.3.4-0ubuntu1 Uname: Linux 4.13.0-041300rc6-generic x86_64 ApportVersion: 2.20.6-0ubuntu6 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Aug 22 14:05:43 2017 InstallationDate: Installed on 2017-07-05 (47 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: libreoffice UpgradeStatus: Upgraded to artful on 2017-07-05 (47 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1712392/+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 1712392] Re: New release 5.4
** Summary changed: - New release 5.0.2RC2 + New release 5.4 ** Description changed: Hello, - https://wiki.documentfoundation.org/Releases/5.0.2/RC2 + https://wiki.documentfoundation.org/ReleaseNotes/5.4 Regards, -- Cristian ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: libreoffice-gnome 1:5.3.4-0ubuntu1 Uname: Linux 4.13.0-041300rc6-generic x86_64 ApportVersion: 2.20.6-0ubuntu6 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Aug 22 14:05:43 2017 InstallationDate: Installed on 2017-07-05 (47 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: libreoffice UpgradeStatus: Upgraded to artful on 2017-07-05 (47 days ago) -- 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/1712392 Title: New release 5.4 Status in libreoffice package in Ubuntu: New Bug description: Hello, https://wiki.documentfoundation.org/ReleaseNotes/5.4 Regards, -- Cristian ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: libreoffice-gnome 1:5.3.4-0ubuntu1 Uname: Linux 4.13.0-041300rc6-generic x86_64 ApportVersion: 2.20.6-0ubuntu6 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Aug 22 14:05:43 2017 InstallationDate: Installed on 2017-07-05 (47 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: libreoffice UpgradeStatus: Upgraded to artful on 2017-07-05 (47 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1712392/+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 1711241] Re: Unity support patch doesn't build with nautilus 3.25.90
I can not debug the issue as I can't install all the debugging symbols. I will try later. @Mike Neac Ubuntu is going to ship Unity-7 to make the transition easier. Also Mate is using hud and unity-gtk-module, xfce is using indicators and all (and hence various unity dependency) and xfce also prefer titlebar instead of headerbar. These patches made carefully so that it doesn't affect gnome-shell anyway. -- 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/1711241 Title: Unity support patch doesn't build with nautilus 3.25.90 Status in nautilus package in Ubuntu: Fix Released Bug description: I have prepared nautilus 3.25.90 in the GNOME3 Staging PPA for Ubuntu 17.10 "artful". The 12_unity_launcher_support.patch has a problem that fails the build and I don't know how to fix it so I disabled the patch for now. Nautilus 3.25 introduces meson support and drops autotools support so that's one factor when I updated the patch. But when I disable the patch, nautilus crashes on start in Unity. Build log attached. Build Log Excerpt == [164/222] cc -Isrc/nautilus@sta -Isrc -Isubprojects/libgd/libgd -I../src -I. -I../ -Isubprojects/libgd -I../subprojects/libgd -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/gtk-3.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/mirclient -I/usr/include/mircore -I/usr/include/mircookie -I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 -I/usr/include/gnome-autoar-0 -I/usr/include/libxml2 -I/usr/include/zeitgeist-2.0 -I/usr/include/gsettings-desktop-schemas -I/usr/include/gail-3.0 -I/usr/include/gnome-desktop-3.0 -I/usr/include/tracker-2.0 -I/usr/include/tracker-2.0/libtracker-sparql -I/usr/include/libexif -I/usr/include/unity/unity -I/usr/include/dee-1.0 -I/usr/include/libdbusmenu-glib-0.4 -I/usr/include/exempi-2.0 -fdiagnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 -Wno-deprecated-declarations -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -DLIBGD_GTK_HACKS=1 -DLIBGD__VIEW_COMMON=1 -DLIBGD_MAIN_ICON_VIEW=1 -DLIBGD_MAIN_LIST_VIEW=1 -DLIBGD_MAIN_VIEW=1 -DLIBGD_TAGGED_ENTRY=1 -MMD -MQ 'src/nautilus@sta/unity-quicklist-handler.c.o' -MF 'src/nautilus@sta/unity-quicklist-handler.c.o.d' -o 'src/nautilus@sta/unity-quicklist-handler.c.o' -c ../src/unity-quicklist-handler.c FAILED: src/nautilus@sta/unity-quicklist-handler.c.o cc -Isrc/nautilus@sta -Isrc -Isubprojects/libgd/libgd -I../src -I. -I../ -Isubprojects/libgd -I../subprojects/libgd -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/gtk-3.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/mirclient -I/usr/include/mircore -I/usr/include/mircookie -I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 -I/usr/include/gnome-autoar-0 -I/usr/include/libxml2 -I/usr/include/zeitgeist-2.0 -I/usr/include/gsettings-desktop-schemas -I/usr/include/gail-3.0 -I/usr/include/gnome-desktop-3.0 -I/usr/include/tracker-2.0 -I/usr/include/tracker-2.0/libtracker-sparql -I/usr/include/libexif -I/usr/include/unity/unity -I/usr/include/dee-1.0 -I/usr/include/libdbusmenu-glib-0.4 -I/usr/include/exempi-2.0 -fdiagnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 -Wno-deprecated-declarations -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -DLIBGD_GTK_HACKS=1 -DLIBGD__VIEW_COMMON=1 -DLIBGD_MAIN_ICON_VIEW=1 -DLIBGD_MAIN_LIST_VIEW=1 -DLIBGD_MAIN_VIEW=1 -DLIBGD_TAGGED_ENTRY=1 -MMD -MQ 'src/nautilus@sta/unity-quicklist-handler.c.o' -MF 'src/nautilus@sta/unity-quicklist-handler.c.o.d' -o 'src/nautilus@sta/unity-quicklist-handler.c.o' -c ../src/unity-quicklist-handler.c ../src/unity-quicklist-handler.c: In function ‘unity_quicklist_handler_get_singleton’: ../src/unity-quicklist-handler.c:154:9: error: expected declaration or statement at end of input unity_quicklist_handler_singleton = unity_quicklist_handler_new (); ^ ../src/unity-quicklist-handler.c:154:9: error: expected declaration or statement at end of input To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1711241/+subscriptio
Re: [Desktop-packages] [Bug 1712019] Re: Driverless printing only prints a blank sheet 17.10
There is no dialog to print in draft either in printing from LibreOffice or from chrome. If I add another printer and it searches for a driver then draft printing is on the menu but printing still does not work. I deleted the PPD files from etc/cups/ppd and copied the old (17.04) PPD file into the directory. This does not help. unfortunately the earliest daily build I have is 14th August when the problem had already occurred. I can not try an earlier Kernal. On 22 August 2017 at 17:41, Till Kamppeter <1712...@bugs.launchpad.net> wrote: > The problem you see in the PPDs. Resolutions are different. > > So can you try to set the Print Quality to Draft to see whether it > prints? > > Another test is creating a new queue with the OLD PPD file. Can you > print with this queue, Print Quality set to Norml or High? > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1712019 > > Title: > Driverless printing only prints a blank sheet 17.10 > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1712019/+subscriptions > -- Rod Jones -- 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/1712019 Title: Driverless printing only prints a blank sheet 17.10 Status in cups package in Ubuntu: Incomplete Bug description: Driverless printing works perfectly in Ubuntu 17.04 with my Epson WF 3620. Scanning is also perfect. I have 17.10 on another SSD and driverless printing was working but recent updates have broken this. I reinstalled from the Aug 14th daily build and have updated it daily but printing still does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1712019/+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 1589008] Re: Bluetooth freezing video playback In Ubuntu/Kubuntu 16.04
It seems to be fixed here on KDE neon... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1589008 Title: Bluetooth freezing video playback In Ubuntu/Kubuntu 16.04 Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: In 16.04 when a bluetooth audio device is connected it freezes video playback and also no sound comes from online audio only streams. Issue does not exist with a wired headset. This issue does not exist with 15.10. All updates have been installed on 16.04 including backports but they have not fixed the issue. It is not browser specific and not website specific. It is not hardware specific as it affects my laptop with an intel 7260 card and my pc with an intel 8260 card. The issue exists on both ubuntu and kubuntu 16.04. I have reported it on the ubuntu support forums and after investigation a moderator noticed changed in the kernel from 4.4 and 4.2 that may becausing the issue and asked me to file a bug report. The ubuntu forum thread can be found here. http://ubuntuforums.org/showthread.php?t=2326672 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-23-generic 4.4.0-23.41 ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10 Uname: Linux 4.4.0-23-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: stephen1435 F pulseaudio /dev/snd/controlC0: stephen1435 F pulseaudio CurrentDesktop: KDE Date: Fri Jun 3 23:50:00 2016 HibernationDevice: RESUME=UUID=78e7aefc-d517-4c58-836f-a90f0b6017c6 InstallationDate: Installed on 2016-05-06 (28 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: MSI MS-7978 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-23-generic.efi.signed root=UUID=bccf2ca7-4e23-412a-ba10-7a3f915270dd ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-23-generic N/A linux-backports-modules-4.4.0-23-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-06-03 (0 days ago) dmi.bios.date: 05/16/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: C.60 dmi.board.asset.tag: Default string dmi.board.name: H170 GAMING M3 (MS-7978) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrC.60:bd05/16/2016:svnMSI:pnMS-7978:pvr2.0:rvnMSI:rnH170GAMINGM3(MS-7978):rvr2.0:cvnMSI:ct3:cvr2.0: dmi.product.name: MS-7978 dmi.product.version: 2.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1589008/+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 1712390] Re: nautilus ubuntu 17.10 remove libunity dependency
(Copied from bug comments:) Ubuntu is going to ship Unity-7 to make the transition easier. Also Mate is using hud and unity-gtk-module, xfce is using indicators and all (and hence various unity dependency) and xfce also prefer titlebar instead of headerbar. These patches made carefully so that it doesn't affect gnome- shell anyway. Gnome-apps designed was designed that way only for gnome. But they also made a door if a distro wants to patch it back. (I personally, like headerbar, but I can't impose my personal choice over everyone else.) -- 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/1712390 Title: nautilus ubuntu 17.10 remove libunity dependency Status in nautilus package in Ubuntu: New Bug description: I was under impression that unity is gone from main support. So what is with libunity dependency in nautilus 3.25? Version 3.24 was working fine without it. And nautilus(and probably others gnome apps) should be without those headerbar/titlebar patches. Please leave it as it is. If someone wants to use nautilus in other desktop it probably wants to use like it was meant to be(I know you could use export XDG_CURRENT_DESKTOP=GNOME, but why force ugly, out of place title bar for gnome apps designed not to use one... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1712390/+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 1712019] Re: Driverless printing only prints a blank sheet 17.10
First, the kernel has no influence to printing results. All the printing logic is happening in user space. Please do the following tests and tell in which cases you get useful printouts (and if so, also tell whether there are quality differences, the PPD files are ones which you had attached in comment #2, file.pdf is an arbitrary PDF file): lpadmin -p oldppd -E -v ipp://EPSON25B56D.local:631/ipp/print -P EPSON-WF-3620-Series17-04.ppd lpadmin -p newppd -E -v ipp://EPSON25B56D.local:631/ipp/print -P EPSON_WF_3620_series17-10.ppd lp -d oldppd -o cupsPrintQuality=Draft file.pdf lp -d oldppd -o cupsPrintQuality=Normal file.pdf lp -d oldppd -o cupsPrintQuality=High file.pdf lp -d newppd -o cupsPrintQuality=Draft file.pdf lp -d newppd -o cupsPrintQuality=Normal file.pdf lp -d newppd -o cupsPrintQuality=High file.pdf For these tests please also follow the instructions of the section "CUPS error_log" on https://wiki.ubuntu.com/DebuggingPrintingProblems -- 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/1712019 Title: Driverless printing only prints a blank sheet 17.10 Status in cups package in Ubuntu: Incomplete Bug description: Driverless printing works perfectly in Ubuntu 17.04 with my Epson WF 3620. Scanning is also perfect. I have 17.10 on another SSD and driverless printing was working but recent updates have broken this. I reinstalled from the Aug 14th daily build and have updated it daily but printing still does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1712019/+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 551950] Re: gnome-bluetooth cannot use pin = 1234
** Changed in: gnome-bluetooth Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/551950 Title: gnome-bluetooth cannot use pin = 1234 Status in GNOME Bluetooth: Expired Status in gnome-bluetooth package in Ubuntu: Incomplete Bug description: Binary package hint: gnome-bluetooth I have a BT serial port with a pin of 1234. I cannot pair to this device with gnome-bluetooth. Every attempt results in gnome-bluetooth requiring a 6 digit random pin. I was able to pair when I uninstalled gnome-bluetooth and installed bluez-gnome. Bluez-gnome will actually send a 4 digit 1234 pin and connect. I am in the process of setting up the serial port in Ubuntu so that I can communicate with the device. My hope is that this will be fixed in Lucid so that I will not have to go through the text based setup of rfcomm for this device. In addition, gnome-bluetooth is very reluctant to connect to the PANU served by my phone. It was set up and after a number of tries I was able to exchange PIN numbers and connect. Unfortunately, I was only able to connect to the PANU once. With bluez-gnome, it works all the time every time. For what it is worth, the OBEX file connection to my Nokia has been very robust under either manager. My BT dongle reports as this one: Bus 005 Device 007: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-bluetooth/+bug/551950/+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 1712392] Re: New release 5.4
libreoffice (1:5.4.0-0ubuntu2) artful; urgency=medium [ Rico Tzschichholz ] * New upstream release * Merge with debian 1:5.4.0-1 ** Changed in: libreoffice (Ubuntu) Status: New => Fix Released -- 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/1712392 Title: New release 5.4 Status in libreoffice package in Ubuntu: Fix Released Bug description: Hello, https://wiki.documentfoundation.org/ReleaseNotes/5.4 Regards, -- Cristian ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: libreoffice-gnome 1:5.3.4-0ubuntu1 Uname: Linux 4.13.0-041300rc6-generic x86_64 ApportVersion: 2.20.6-0ubuntu6 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Aug 22 14:05:43 2017 InstallationDate: Installed on 2017-07-05 (47 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: libreoffice UpgradeStatus: Upgraded to artful on 2017-07-05 (47 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1712392/+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 1570204] Re: Deja-dup tries to save directories that sould be ignored
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: deja-dup (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to deja-dup in Ubuntu. https://bugs.launchpad.net/bugs/1570204 Title: Deja-dup tries to save directories that sould be ignored Status in Déjà Dup: New Status in deja-dup package in Ubuntu: Confirmed Bug description: After running deja-dup, I get the following information: Could not back up the following files. Please make sure you are able to open them. /home/wiktor./cache/dconf /home/wiktor/.dbus /home/wiktor/.gvfs All of the above directories are added to "Folders to ignore" list. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: deja-dup 34.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Thu Apr 14 08:39:24 2016 InstallationDate: Installed on 2016-04-11 (2 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160408) SourcePackage: deja-dup UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/deja-dup/+bug/1570204/+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 1570204] Re: Deja-dup tries to save directories that sould be ignored
** Also affects: deja-dup Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to deja-dup in Ubuntu. https://bugs.launchpad.net/bugs/1570204 Title: Deja-dup tries to save directories that sould be ignored Status in Déjà Dup: New Status in deja-dup package in Ubuntu: Confirmed Bug description: After running deja-dup, I get the following information: Could not back up the following files. Please make sure you are able to open them. /home/wiktor./cache/dconf /home/wiktor/.dbus /home/wiktor/.gvfs All of the above directories are added to "Folders to ignore" list. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: deja-dup 34.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Thu Apr 14 08:39:24 2016 InstallationDate: Installed on 2016-04-11 (2 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160408) SourcePackage: deja-dup UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/deja-dup/+bug/1570204/+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 1397118] Re: Deja Dup finishes with mysterious message
*** This bug is a duplicate of bug 1570204 *** https://bugs.launchpad.net/bugs/1570204 ** This bug has been marked a duplicate of bug 1570204 Deja-dup tries to save directories that sould be ignored -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to deja-dup in Ubuntu. https://bugs.launchpad.net/bugs/1397118 Title: Deja Dup finishes with mysterious message Status in deja-dup package in Ubuntu: New Bug description: After an automated backup I'm left with this message: Backup Finished Could not back up the following files. Please make sure you are able to open them. /home//.cache/dconf /home//.gvfs The beginning of the message implies that the backup job finished but the text after that leaves uncertainty. It's not clear if I am supposed to follow up with an action. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: deja-dup 30.0-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Uname: Linux 3.13.0-36-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CurrentDesktop: Unity Date: Thu Nov 27 20:55:56 2014 InstallationDate: Installed on 2014-09-13 (74 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140308) SourcePackage: deja-dup UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1397118/+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 1712392] Re: New release 5.4
Hello, https://launchpad.net/ubuntu/+source/libreoffice/1:5.4.0-0ubuntu2 Regards, -- Cristian -- 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/1712392 Title: New release 5.4 Status in libreoffice package in Ubuntu: Fix Released Bug description: Hello, https://wiki.documentfoundation.org/ReleaseNotes/5.4 Regards, -- Cristian ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: libreoffice-gnome 1:5.3.4-0ubuntu1 Uname: Linux 4.13.0-041300rc6-generic x86_64 ApportVersion: 2.20.6-0ubuntu6 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Aug 22 14:05:43 2017 InstallationDate: Installed on 2017-07-05 (47 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: libreoffice UpgradeStatus: Upgraded to artful on 2017-07-05 (47 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1712392/+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 1266025] Re: backup folder in ~/.cache/deja-dup/tmp does not exist
*** This bug is a duplicate of bug 1318833 *** https://bugs.launchpad.net/bugs/1318833 ** This bug has been marked a duplicate of bug 1318833 "No such file or directory" during backup -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to deja-dup in Ubuntu. https://bugs.launchpad.net/bugs/1266025 Title: backup folder in ~/.cache/deja-dup/tmp does not exist Status in deja-dup package in Ubuntu: New Bug description: Déjà-dup backups fail with an error message "The backup folder »/home/username/.cache/deja-dup/tmp/duplicity-il-Au69-tempdir/mktemp- 51Sz0x-3« does not exist.". This folder does indeed not exist. When clicking the close button, deja-dup aborted. For weeks not a single deja-dup backup completed successfully due to various reported bugs. When I attempt to restore files, I see that files have been backuped, but I cannot be sure whether the files are complete. This makes the backups absolutely useless because I have no guarantee that I can restore all the files. I would strongly recommend to review _all_ error messages that deja- dup might produce and allow users to continue an interrupted backup process when the issue has been resolved. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1266025/+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 1712417] [NEW] New release 3.22.19
Public bug reported: Hello, https://git.gnome.org/browse/gtk+/commit/?h=3.22.19&id=efbf6f183ecd24cddea743a02fe8ce545f1b55f8 Regards, -- Cristian ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: libgtk-3-0 3.22.18-1ubuntu1 Uname: Linux 4.13.0-041300rc6-generic x86_64 ApportVersion: 2.20.6-0ubuntu6 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Aug 22 16:45:33 2017 InstallationDate: Installed on 2017-07-05 (48 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: gtk+3.0 UpgradeStatus: Upgraded to artful on 2017-07-05 (47 days ago) ** Affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful upgrade-software-version -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1712417 Title: New release 3.22.19 Status in gtk+3.0 package in Ubuntu: New Bug description: Hello, https://git.gnome.org/browse/gtk+/commit/?h=3.22.19&id=efbf6f183ecd24cddea743a02fe8ce545f1b55f8 Regards, -- Cristian ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: libgtk-3-0 3.22.18-1ubuntu1 Uname: Linux 4.13.0-041300rc6-generic x86_64 ApportVersion: 2.20.6-0ubuntu6 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Aug 22 16:45:33 2017 InstallationDate: Installed on 2017-07-05 (48 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: gtk+3.0 UpgradeStatus: Upgraded to artful on 2017-07-05 (47 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1712417/+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 1712416] [NEW] Inastalé Driver y el no funcionó
Public bug reported: Driver tarjeta gráfica no funciona: AMD-RADEON Dual-X R9 280X en ubuntu 17.10 Gracias ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu1 ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5 Uname: Linux 4.12.0-11-generic x86_64 ApportVersion: 2.20.6-0ubuntu6 Architecture: amd64 Date: Tue Aug 22 14:39:30 2017 DistroCodename: artful DistroVariant: ubuntu InstallationDate: Installed on 2017-08-22 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170820) ProcEnviron: LANGUAGE=es_CO:es PATH=(custom, no user) LANG=es_CO.UTF-8 SHELL=/bin/bash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1712416 Title: Inastalé Driver y el no funcionó Status in xorg package in Ubuntu: New Bug description: Driver tarjeta gráfica no funciona: AMD-RADEON Dual-X R9 280X en ubuntu 17.10 Gracias ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu1 ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5 Uname: Linux 4.12.0-11-generic x86_64 ApportVersion: 2.20.6-0ubuntu6 Architecture: amd64 Date: Tue Aug 22 14:39:30 2017 DistroCodename: artful DistroVariant: ubuntu InstallationDate: Installed on 2017-08-22 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170820) ProcEnviron: LANGUAGE=es_CO:es PATH=(custom, no user) LANG=es_CO.UTF-8 SHELL=/bin/bash 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/+bug/1712416/+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 1712400] Re: [RFE] Show Ubuntu logo on the GDM login screen
** Also affects: ubuntu-settings (Ubuntu) Importance: Undecided Status: New ** Also affects: ubuntu-themes (Ubuntu) Importance: Undecided Status: New ** Tags added: gnome-17.10 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1712400 Title: [RFE] Show Ubuntu logo on the GDM login screen Status in gdm3 package in Ubuntu: New Status in ubuntu-settings package in Ubuntu: New Status in ubuntu-themes package in Ubuntu: New Bug description: Fedora, Debian and many other distributions have their logo displayed on the bottom of the GDM screen, Ubuntu has nothing there. I think it could be a good idea to show Ubuntu logo or other Ubuntu branding there. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1712400/+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 1712437] [NEW] libxfont1-dev conflicts with libxfont-dev in Ubuntu 16.04.3 LTS
Public bug reported: Unable to install libxfont1-dev alongside libxfont-dev in Ubuntu 16.04.3 LTS on amd64 and ppc64el. Description:Ubuntu 16.04.3 LTS Release:16.04 Codename: xenial kernel: 4.4.0-92-generic sudo apt-get install libxfont-dev libxfont1-dev Reading package lists... Done Building dependency tree Reading state information... Done The following NEW packages will be installed: libxfont-dev libxfont1-dev 0 upgraded, 2 newly installed, 0 to remove and 5 not upgraded. Need to get 0 B/251 kB of archives. After this operation, 972 kB of additional disk space will be used. Selecting previously unselected package libxfont-dev. (Reading database ... 249388 files and directories currently installed.) Preparing to unpack .../libxfont-dev_1%3a2.0.1-3~ubuntu16.04.1_amd64.deb ... Unpacking libxfont-dev (1:2.0.1-3~ubuntu16.04.1) ... Preparing to unpack .../libxfont1-dev_1%3a1.5.1-1ubuntu0.16.04.1_amd64.deb ... Unpacking libxfont1-dev (1:1.5.1-1ubuntu0.16.04.1) ... dpkg: error processing archive /var/cache/apt/archives/libxfont1-dev_1%3a1.5.1-1ubuntu0.16.04.1_amd64.deb (--unpack): trying to overwrite '/usr/share/doc/libxfont-dev/fontlib.html', which is also in package libxfont-dev 1:2.0.1-3~ubuntu16.04.1 Errors were encountered while processing: /var/cache/apt/archives/libxfont1-dev_1%3a1.5.1-1ubuntu0.16.04.1_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) It appears both packages maintain these files: /usr/share/doc/libxfont-dev/fontlib.html /usr/share/doc/libxfont-dev/fontlib.txt.gz The libxfont1-dev package in zesty and artful do not use the libxfont-dev path: /usr/share/doc/libxfont1-dev/changelog.Debian.gz /usr/share/doc/libxfont1-dev/copyright /usr/share/doc/libxfont1-dev/fontlib.html /usr/share/doc/libxfont1-dev/fontlib.txt.gz This problem did not occur ~1 month ago. ** Affects: libxfont1 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libxfont1 in Ubuntu. https://bugs.launchpad.net/bugs/1712437 Title: libxfont1-dev conflicts with libxfont-dev in Ubuntu 16.04.3 LTS Status in libxfont1 package in Ubuntu: New Bug description: Unable to install libxfont1-dev alongside libxfont-dev in Ubuntu 16.04.3 LTS on amd64 and ppc64el. Description: Ubuntu 16.04.3 LTS Release: 16.04 Codename: xenial kernel: 4.4.0-92-generic sudo apt-get install libxfont-dev libxfont1-dev Reading package lists... Done Building dependency tree Reading state information... Done The following NEW packages will be installed: libxfont-dev libxfont1-dev 0 upgraded, 2 newly installed, 0 to remove and 5 not upgraded. Need to get 0 B/251 kB of archives. After this operation, 972 kB of additional disk space will be used. Selecting previously unselected package libxfont-dev. (Reading database ... 249388 files and directories currently installed.) Preparing to unpack .../libxfont-dev_1%3a2.0.1-3~ubuntu16.04.1_amd64.deb ... Unpacking libxfont-dev (1:2.0.1-3~ubuntu16.04.1) ... Preparing to unpack .../libxfont1-dev_1%3a1.5.1-1ubuntu0.16.04.1_amd64.deb ... Unpacking libxfont1-dev (1:1.5.1-1ubuntu0.16.04.1) ... dpkg: error processing archive /var/cache/apt/archives/libxfont1-dev_1%3a1.5.1-1ubuntu0.16.04.1_amd64.deb (--unpack): trying to overwrite '/usr/share/doc/libxfont-dev/fontlib.html', which is also in package libxfont-dev 1:2.0.1-3~ubuntu16.04.1 Errors were encountered while processing: /var/cache/apt/archives/libxfont1-dev_1%3a1.5.1-1ubuntu0.16.04.1_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) It appears both packages maintain these files: /usr/share/doc/libxfont-dev/fontlib.html /usr/share/doc/libxfont-dev/fontlib.txt.gz The libxfont1-dev package in zesty and artful do not use the libxfont-dev path: /usr/share/doc/libxfont1-dev/changelog.Debian.gz /usr/share/doc/libxfont1-dev/copyright /usr/share/doc/libxfont1-dev/fontlib.html /usr/share/doc/libxfont1-dev/fontlib.txt.gz This problem did not occur ~1 month ago. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxfont1/+bug/1712437/+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
Re: [Desktop-packages] [Bug 1712019] Re: Driverless printing only prints a blank sheet 17.10
I think you discount a kernel problem too lightly. When CUPS has started a print job it has to send it to the printer. In my case over the network. This involves the kernel and or the network driver. I have just tried the daily build of Ubuntu Gnome - the browser can not find google and ubuntu Budgie - same problem. The ppd file for the printer is present in both distributions. I will re-install Ubuntu tomorrow and try again. 17.04 works perfectly. On 22 August 2017 at 19:08, Till Kamppeter <1712...@bugs.launchpad.net> wrote: > First, the kernel has no influence to printing results. All the printing > logic is happening in user space. > > Please do the following tests and tell in which cases you get useful > printouts (and if so, also tell whether there are quality differences, > the PPD files are ones which you had attached in comment #2, file.pdf is > an arbitrary PDF file): > > lpadmin -p oldppd -E -v ipp://EPSON25B56D.local:631/ipp/print -P > EPSON-WF-3620-Series17-04.ppd > lpadmin -p newppd -E -v ipp://EPSON25B56D.local:631/ipp/print -P > EPSON_WF_3620_series17-10.ppd > > lp -d oldppd -o cupsPrintQuality=Draft file.pdf > lp -d oldppd -o cupsPrintQuality=Normal file.pdf > lp -d oldppd -o cupsPrintQuality=High file.pdf > > lp -d newppd -o cupsPrintQuality=Draft file.pdf > lp -d newppd -o cupsPrintQuality=Normal file.pdf > lp -d newppd -o cupsPrintQuality=High file.pdf > > For these tests please also follow the instructions of the section "CUPS > error_log" on https://wiki.ubuntu.com/DebuggingPrintingProblems > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1712019 > > Title: > Driverless printing only prints a blank sheet 17.10 > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1712019/+subscriptions > -- Rod Jones -- 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/1712019 Title: Driverless printing only prints a blank sheet 17.10 Status in cups package in Ubuntu: Incomplete Bug description: Driverless printing works perfectly in Ubuntu 17.04 with my Epson WF 3620. Scanning is also perfect. I have 17.10 on another SSD and driverless printing was working but recent updates have broken this. I reinstalled from the Aug 14th daily build and have updated it daily but printing still does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1712019/+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 1623835] Re: Scrolled Windows in backup/restore progress are too small to read
** Changed in: deja-dup (Ubuntu) Status: In Progress => Fix Released ** No longer affects: deja-dup (Ubuntu Yakkety) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to deja-dup in Ubuntu. https://bugs.launchpad.net/bugs/1623835 Title: Scrolled Windows in backup/restore progress are too small to read Status in Déjà Dup: Fix Released Status in deja-dup package in Ubuntu: Fix Released Bug description: [Impact] * Expanding the scrolled windows for backup or restore progress in deja-dup are just one line high, making them unreadable. [ Test Case ] * Install Ubuntu 16.10 final or 17.04 daily. * Open deja-dup and configure a backup location. * Start a backup and the Details during a running backup, you'll see the scrolled window is just one line high. After installing the patched daja-dup package following the same steps will result in the backup/restore progress scrolled windows defaulting to several lines of readable output. [ Regression Potential ] * None. [ Other Info ] ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: deja-dup 34.2-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16 Uname: Linux 4.4.0-9136-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: Unity Date: Thu Sep 15 09:21:28 2016 InstallationDate: Installed on 2016-07-25 (51 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: deja-dup UpgradeStatus: Upgraded to yakkety on 2016-09-06 (8 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/deja-dup/+bug/1623835/+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 1368640] Re: When backup system, need to click cancel button twice to close Encryption Password Needed page.
** Branch linked: lp:~ubuntu-desktop/deja-dup/ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to deja-dup in Ubuntu. https://bugs.launchpad.net/bugs/1368640 Title: When backup system, need to click cancel button twice to close Encryption Password Needed page. Status in Déjà Dup: Fix Released Status in Ubuntu Kylin: New Status in deja-dup package in Ubuntu: New Bug description: When backup system, need to click cancel button twice to close Encryption Password Needed page. You must backuped your system with encryption before. Steps: 1. Enter into System settings-->Backup, 2. Click back up now, backup the system with encryption 3. Click the back up now button again, 4. Click cancel button in Encryption Password Needed page -->Failed. Need to click cancel button twice to close Encryption Password Needed page. Configuration: PC: Dell Vostro OS: Ubuntu kylin 14.10 daily 0912 To manage notifications about this bug go to: https://bugs.launchpad.net/deja-dup/+bug/1368640/+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 1368640] Re: When backup system, need to click cancel button twice to close Encryption Password Needed page.
** Changed in: deja-dup Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to deja-dup in Ubuntu. https://bugs.launchpad.net/bugs/1368640 Title: When backup system, need to click cancel button twice to close Encryption Password Needed page. Status in Déjà Dup: Fix Released Status in Ubuntu Kylin: New Status in deja-dup package in Ubuntu: New Bug description: When backup system, need to click cancel button twice to close Encryption Password Needed page. You must backuped your system with encryption before. Steps: 1. Enter into System settings-->Backup, 2. Click back up now, backup the system with encryption 3. Click the back up now button again, 4. Click cancel button in Encryption Password Needed page -->Failed. Need to click cancel button twice to close Encryption Password Needed page. Configuration: PC: Dell Vostro OS: Ubuntu kylin 14.10 daily 0912 To manage notifications about this bug go to: https://bugs.launchpad.net/deja-dup/+bug/1368640/+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 1642966] Proposed package upload rejected
An upload of cups to xenial-proposed has been rejected from the upload queue for the following reason: "Please re-upload including the changelog from the not-released-from-proposed 2.1.3-4ubuntu0.2 in the _changes file. This is needed for SRU tracking.". -- 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/1642966 Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 Status in cups package in Ubuntu: Fix Released Status in cups source package in Xenial: In Progress Status in cups source package in Yakkety: Fix Released Status in cups source package in Zesty: Fix Released Bug description: This is in xenial-proposed, please block release to -updates accordingly :) [Impact] * fail to upgrade [testcase] Root cause is believed to be reproducible with: #!/bin/bash systemctl stop cups.path cups.service rm /var/cache/cups/org.cups.cupsd systemctl start cups.path touch /var/cache/cups/org.cups.cupsd sleep 1 rm /var/cache/cups/org.cups.cupsd sleep 1 systemctl stop cups.service echo $? ProblemType: Package DistroRelease: Ubuntu 16.04 Package: cups-daemon 2.1.3-4 ProcVersionSignature: Ubuntu 4.4.0-46.67-generic 4.4.24 Uname: Linux 4.4.0-46-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CupsErrorLog: Date: Fri Nov 18 11:13:15 2016 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2016-05-02 (200 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lpstat: device for mallards-officejet-pro-8600: dnssd://Officejet%20Pro%208600%20%5BD63461%5D._ipp._tcp.local/?uuid=1c852a4d-b800-1f08-abcd-d89d67d63461 MachineType: Dell Inc. XPS 15 9550 Papersize: a4 PpdFiles: mallards-officejet-pro-8600: HP Officejet Pro 8600, hpcups 3.16.3 ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-46-generic.efi.signed root=UUID=3643ef37-7cee-41b3-9387-2faa819c44db ro quiet splash vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-46-generic.efi.signed root=UUID=3643ef37-7cee-41b3-9387-2faa819c44db ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.15 SourcePackage: cups Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.02.00 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 15 9550 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1642966/+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 1642966] Re: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1
Hello Mark, or anyone else affected, Accepted cups into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/cups/2.1.3-4ubuntu0.3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: cups (Ubuntu Xenial) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-xenial -- 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/1642966 Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 Status in cups package in Ubuntu: Fix Released Status in cups source package in Xenial: Fix Committed Status in cups source package in Yakkety: Fix Released Status in cups source package in Zesty: Fix Released Bug description: This is in xenial-proposed, please block release to -updates accordingly :) [Impact] * fail to upgrade [testcase] Root cause is believed to be reproducible with: #!/bin/bash systemctl stop cups.path cups.service rm /var/cache/cups/org.cups.cupsd systemctl start cups.path touch /var/cache/cups/org.cups.cupsd sleep 1 rm /var/cache/cups/org.cups.cupsd sleep 1 systemctl stop cups.service echo $? ProblemType: Package DistroRelease: Ubuntu 16.04 Package: cups-daemon 2.1.3-4 ProcVersionSignature: Ubuntu 4.4.0-46.67-generic 4.4.24 Uname: Linux 4.4.0-46-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CupsErrorLog: Date: Fri Nov 18 11:13:15 2016 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2016-05-02 (200 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lpstat: device for mallards-officejet-pro-8600: dnssd://Officejet%20Pro%208600%20%5BD63461%5D._ipp._tcp.local/?uuid=1c852a4d-b800-1f08-abcd-d89d67d63461 MachineType: Dell Inc. XPS 15 9550 Papersize: a4 PpdFiles: mallards-officejet-pro-8600: HP Officejet Pro 8600, hpcups 3.16.3 ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-46-generic.efi.signed root=UUID=3643ef37-7cee-41b3-9387-2faa819c44db ro quiet splash vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-46-generic.efi.signed root=UUID=3643ef37-7cee-41b3-9387-2faa819c44db ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.15 SourcePackage: cups Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.02.00 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 15 9550 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1642966/+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 1598300] Re: CUPS web interface stops responding after a while
Hello dominix, or anyone else affected, Accepted cups into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/cups/2.1.3-4ubuntu0.3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: cups (Ubuntu Xenial) Status: Triaged => Fix Committed ** Tags added: verification-needed verification-needed-xenial -- 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/1598300 Title: CUPS web interface stops responding after a while Status in cups package in Ubuntu: Fix Released Status in cups source package in Xenial: Fix Committed Bug description: after 6 minutes or so, cups is not responding. it do not produce error on the log, just stop working, worse, it exit with 0 ⌌—⌍ |root@cupsmachine :~# systemctl status cups | |● cups.service - CUPS Scheduler | | Loaded: loaded (/lib/systemd/system/cups.service; enabled; vendor preset: enabled)| | Active: inactive (dead) since ven. 2016-07-01 10:31:32 TAHT; 2min 16s ago | | Docs: man:cupsd(8) | | Process: 28686 ExecStart=/usr/sbin/cupsd -l (code=exited, status=0/SUCCESS)| | Main PID: 28686 (code=exited, status=0/SUCCESS) | | | |juil. 01 10:30:01 appli-client systemd[1]: Started CUPS Scheduler. | ⌎—⌏ I got to launch it again, so I have finish with a cron job like */10 * * * * systemctl status cups.service|grep -q 'inactive (dead)' && systemctl start cups but it is a dirty solution. I have no idea of what make it stop. NB: I have seen problems related to apparmor, this machine has no apparmor package. [Impact] If you want to use the CUPS web interface in Xenial and therefore set "WebInterface Yes" in /etc/cups/cupsd.conf, CUPS could auto-shutdown when it is idle and then an attempt to access http://localhost:631/ via a web browser fails. People get confused as other access to CUPS [Testcase] Take a CUPS setup on Xenial with no shared print queues and CUPS only listening on the domain socket. Activate the web interface via cupsctl WebInterface=Yes Now you are able to access the web interface via http://localhost:631/. Wait for some minutes without accessing CUPS until the CUPS daemon shuts down automatically. Try to open the web interface again and it will not work. With the fixed CUPS package CUPS will not auto-shutdown when the web interface is activated. [Regression Potential] Low, as we are removing a simple distro patch to get back to the original, upstream behavior. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1598300/+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 1709885] Re: package libxfont1-dev (not installed) failed to install/upgrade: trying to overwrite '/usr/share/doc/libxfont-dev/fontlib.html', which is also in package libxfont-
This bug was fixed in the package libxfont - 1:1.5.1-1ubuntu0.16.04.2 --- libxfont (1:1.5.1-1ubuntu0.16.04.2) xenial; urgency=medium * Install developer documentation under the correct path. (LP: #1709885) -- Timo Aaltonen Fri, 11 Aug 2017 01:16:51 +0300 ** Changed in: libxfont (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libxfont in Ubuntu. https://bugs.launchpad.net/bugs/1709885 Title: package libxfont1-dev (not installed) failed to install/upgrade: trying to overwrite '/usr/share/doc/libxfont-dev/fontlib.html', which is also in package libxfont-dev 1:2.0.1-3~ubuntu16.04.1 Status in libxfont package in Ubuntu: Invalid Status in libxfont source package in Xenial: Fix Released Bug description: [Impact] update failed package:libxfont1-dev:(not installed) Unpacking libxfont1-dev (1:1.5.1-1ubuntu0.16.04.1) ... dpkg: error processing archive /var/cache/apt/archives/libxfont1-dev_1%3a1.5.1-1ubuntu0.16.04.1_amd64.deb (--unpack): trying to overwrite '/usr/share/doc/libxfont-dev/fontlib.html', which is also in package libxfont-dev 1:2.0.1-3~ubuntu16.04.1 the devel documentation is in the wrong directory, need to move it [Test case] try to install both libxfont1-dev and libxfont-dev [Regression potential] none, moves two files to the correct location, that's all To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxfont/+bug/1709885/+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 1709885] Update Released
The verification of the Stable Release Update for libxfont 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 libxfont in Ubuntu. https://bugs.launchpad.net/bugs/1709885 Title: package libxfont1-dev (not installed) failed to install/upgrade: trying to overwrite '/usr/share/doc/libxfont-dev/fontlib.html', which is also in package libxfont-dev 1:2.0.1-3~ubuntu16.04.1 Status in libxfont package in Ubuntu: Invalid Status in libxfont source package in Xenial: Fix Released Bug description: [Impact] update failed package:libxfont1-dev:(not installed) Unpacking libxfont1-dev (1:1.5.1-1ubuntu0.16.04.1) ... dpkg: error processing archive /var/cache/apt/archives/libxfont1-dev_1%3a1.5.1-1ubuntu0.16.04.1_amd64.deb (--unpack): trying to overwrite '/usr/share/doc/libxfont-dev/fontlib.html', which is also in package libxfont-dev 1:2.0.1-3~ubuntu16.04.1 the devel documentation is in the wrong directory, need to move it [Test case] try to install both libxfont1-dev and libxfont-dev [Regression potential] none, moves two files to the correct location, that's all To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxfont/+bug/1709885/+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 1703110] Re: notes doesn't delete only if empty
This bug was fixed in the package gnome-applets - 3.22.0-2ubuntu0.2 --- gnome-applets (3.22.0-2ubuntu0.2) zesty; urgency=medium * Extend sticky_notes_fixes.diff with one more upstream commit to fix text selection (LP: #1703110). -- Dmitry Shachnev Mon, 31 Jul 2017 20:29:17 +0300 ** Changed in: gnome-applets (Ubuntu Zesty) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-applets in Ubuntu. https://bugs.launchpad.net/bugs/1703110 Title: notes doesn't delete only if empty Status in gnome-applets package in Ubuntu: Fix Released Status in gnome-applets source package in Zesty: Fix Released Bug description: [Impact] Unnesessary work for the user as he is forced to clear the note from text in order to delete it. It makes it more difficult that selecting text isn't possible with mouse. [Test Case] - Write anything in a note - Try to select text in a note - Try to delete it with 'x' or with 'delete notes' menu item [Proposed Fix] The fix is a backport of three upstream commits: - https://git.gnome.org/browse/gnome-applets/commit/?id=85041d6567c78b4a “sticky-notes: make sure that notes are really saved” - https://git.gnome.org/browse/gnome-applets/commit/?id=0c4e0c4fed0c61bf “sticky-notes: fix path to resource file for delete dialog” - https://git.gnome.org/browse/gnome-applets/commit/?id=e189ba213c0f8db8 “sticky-notes: fix text selection” [Regression Potential] The fix definitely improves the Sticky Notes applet because without ability to save notes that applet is mostly unusable. It does not touch other applets so no regression expected there. [Other Info] System configuration: roland@roland-Lenovo-ideapad-110-15I `:+ss+:` -+ssyy+- OS: Ubuntu 17.04 x86_64 .ossdMMMNyo. Model: 80T7 Lenovo ideapad 110-15IBR /ssshdmmNNmmyNhss/ Kernel: 4.10.0-26-generic +shmydMMMNy+ Uptime: 4 hours, 45 mins /hNMMMyhhhmNMMMNh/Packages: 2360 .dMMMNhsshNMMMd. Shell: bash 4.4.7 +hhhyNMMNyyNMMMysss+ Resolution: 1366x768 ossyNMMMNyMMhsshmmmhssso DE: GNOME-Flashback:GNOME ossyNMMMNyMMhsshmmmhssso WM: Compiz +hhhyNMMNyyNMMMysss+ WM Theme: Adwaita .dMMMNhsshNMMMd. Theme: Adwaita [GTK2/3] /hNMMMyhhhdNMMMNh/Icons: Ubuntu-mono-light [GTK2/3] +sdmydy+ Terminal: gnome-terminal /ssshdmmyNhss/ CPU: Intel Pentium N3710 (4) @ 2.5GH .ossdMMMNyo. GPU: Intel HD Graphics 405 -+syyy+- Memory: 1674MiB / 3862MiB `:+ss+:` .-/+oooo+/-. Stickynotes version: 3.22.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-applets/+bug/1703110/+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 1703110] Update Released
The verification of the Stable Release Update for gnome-applets 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-applets in Ubuntu. https://bugs.launchpad.net/bugs/1703110 Title: notes doesn't delete only if empty Status in gnome-applets package in Ubuntu: Fix Released Status in gnome-applets source package in Zesty: Fix Released Bug description: [Impact] Unnesessary work for the user as he is forced to clear the note from text in order to delete it. It makes it more difficult that selecting text isn't possible with mouse. [Test Case] - Write anything in a note - Try to select text in a note - Try to delete it with 'x' or with 'delete notes' menu item [Proposed Fix] The fix is a backport of three upstream commits: - https://git.gnome.org/browse/gnome-applets/commit/?id=85041d6567c78b4a “sticky-notes: make sure that notes are really saved” - https://git.gnome.org/browse/gnome-applets/commit/?id=0c4e0c4fed0c61bf “sticky-notes: fix path to resource file for delete dialog” - https://git.gnome.org/browse/gnome-applets/commit/?id=e189ba213c0f8db8 “sticky-notes: fix text selection” [Regression Potential] The fix definitely improves the Sticky Notes applet because without ability to save notes that applet is mostly unusable. It does not touch other applets so no regression expected there. [Other Info] System configuration: roland@roland-Lenovo-ideapad-110-15I `:+ss+:` -+ssyy+- OS: Ubuntu 17.04 x86_64 .ossdMMMNyo. Model: 80T7 Lenovo ideapad 110-15IBR /ssshdmmNNmmyNhss/ Kernel: 4.10.0-26-generic +shmydMMMNy+ Uptime: 4 hours, 45 mins /hNMMMyhhhmNMMMNh/Packages: 2360 .dMMMNhsshNMMMd. Shell: bash 4.4.7 +hhhyNMMNyyNMMMysss+ Resolution: 1366x768 ossyNMMMNyMMhsshmmmhssso DE: GNOME-Flashback:GNOME ossyNMMMNyMMhsshmmmhssso WM: Compiz +hhhyNMMNyyNMMMysss+ WM Theme: Adwaita .dMMMNhsshNMMMd. Theme: Adwaita [GTK2/3] /hNMMMyhhhdNMMMNh/Icons: Ubuntu-mono-light [GTK2/3] +sdmydy+ Terminal: gnome-terminal /ssshdmmyNhss/ CPU: Intel Pentium N3710 (4) @ 2.5GH .ossdMMMNyo. GPU: Intel HD Graphics 405 -+syyy+- Memory: 1674MiB / 3862MiB `:+ss+:` .-/+oooo+/-. Stickynotes version: 3.22.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-applets/+bug/1703110/+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 1711876] Re: Firefox version 55 cannot start and crashed on Raspberry Pi 3
** Summary changed: - Firefox version 55 cannot start and crashed on Ubuntun-Mate 16.04.2 for Raspberry Pi 3 + Firefox version 55 cannot start and crashed on Raspberry Pi 3 ** Also affects: firefox (Ubuntu) Importance: Undecided Status: New ** Changed in: ubuntu-mate Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1711876 Title: Firefox version 55 cannot start and crashed on Raspberry Pi 3 Status in ubuntu-mate: Invalid Status in firefox package in Ubuntu: New Bug description: Hi I am currently using a Raspberry Pi 3 for Ubuntu-Mate 16.04.2 After doing a software update, firefox version 55 cannot start up and crashed! I cannot even send Ubuntu software bug for this! Could you please checked and verify. If possible release a working firefox browser the Raspberry Pi 3 version. Thank you. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1711876/+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 1667198] Update Released
The verification of the Stable Release Update for ubuntu-drivers-common 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 ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1667198 Title: gpu-manager should also support using custom xorg.conf files for Nvidia Status in HWE Next: Incomplete Status in OEM Priority Project: Confirmed Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Xenial: Fix Released Status in ubuntu-drivers-common source package in Zesty: Fix Released Bug description: SRU Request: [Impact] Different GPUs may require different options in the xorg.conf file. Currently this is not possible, since the options have been hardcoded in gpu-manager to configure the system automatically. This new (backported) feature allows users to tell gpu-manager to use their own custom xorg.confs for their NVIDIA GPUs. [Test Case] 1) Enable the xenial-proposed repository, and install the ubuntu-drivers-common and the nvidia-prime packages. 2) Install the nvidia driver. 3) Place your configuration file(s) in the /usr/share/gpu-manager.d directory. If you are using a non-hybrid system, you can create the /usr/share /gpu-manager.d/non-hybrid file. In case of a hybrid system, you can specify /usr/share/gpu-manager.d/hybrid-performance and/or /usr/share /gpu-manager.d/hybrid-power-saving, depending on the power profile you intend to apply your settings to. 4) Restart the system and see if it boots correctly. If unsure, please attach your /var/log/gpu-manager.log and /var/log/Xorg.0.log 5) Make sure that the /etc/X11/xorg.conf matches the file you specified in 3) [Regression Potential] Low, the above mentioned changes are already in Artful, and will not affect the system's behaviour unless new configuration files are put in the /usr/share/gpu-manager.d/ directory. __ This feature has been implemented for Intel (ex. gpumanager_uxa), which is parsing kernel parameter to add option in xorg.conf (commit ff3a4e54). And now Nvidia also need this feature to add Option "nvidiaXineramaInfo" "off" to fix some issues. Btw, I'm thinking it might be a more flexible to have a config file which user could add all options as they want so that we could prevent keeping change gpu-manager when some more options are needed in the future. Needed by LP: #1653592 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1667198/+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 1667198] Re: gpu-manager should also support using custom xorg.conf files for Nvidia
This bug was fixed in the package ubuntu-drivers-common - 1:0.4.22.1
---
ubuntu-drivers-common (1:0.4.22.1) zesty-proposed; urgency=medium
* gpu-manager.{c|py}:
- Add support for using custom xorg.confs with the nvidia
driver (LP: #1667198).
Custom xorg files can be named "non-hybrid" (for non hybrid
systems), "hybrid-performance", and "hybrid-power-saving",
and will have to placed in the /usr/share/gpu-manager.d
directory.
The directory can be overridden by passing another directory
along with the "--custom-xorg-conf-path" parameter.
- Add tests for the custom xorg.confs code and for amdgpu-pro
hybrid support.
-- Alberto Milone Wed, 02 Aug 2017
17:17:13 +0200
** Changed in: ubuntu-drivers-common (Ubuntu Zesty)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/1667198
Title:
gpu-manager should also support using custom xorg.conf files for
Nvidia
Status in HWE Next:
Incomplete
Status in OEM Priority Project:
Confirmed
Status in ubuntu-drivers-common package in Ubuntu:
Fix Released
Status in ubuntu-drivers-common source package in Xenial:
Fix Released
Status in ubuntu-drivers-common source package in Zesty:
Fix Released
Bug description:
SRU Request:
[Impact]
Different GPUs may require different options in the xorg.conf file. Currently
this is not possible, since the options have been hardcoded in gpu-manager to
configure the system automatically.
This new (backported) feature allows users to tell gpu-manager to use
their own custom xorg.confs for their NVIDIA GPUs.
[Test Case]
1) Enable the xenial-proposed repository, and install the
ubuntu-drivers-common and the nvidia-prime packages.
2) Install the nvidia driver.
3) Place your configuration file(s) in the /usr/share/gpu-manager.d
directory.
If you are using a non-hybrid system, you can create the /usr/share
/gpu-manager.d/non-hybrid file. In case of a hybrid system, you can
specify /usr/share/gpu-manager.d/hybrid-performance and/or /usr/share
/gpu-manager.d/hybrid-power-saving, depending on the power profile you
intend to apply your settings to.
4) Restart the system and see if it boots correctly. If unsure, please
attach your /var/log/gpu-manager.log and /var/log/Xorg.0.log
5) Make sure that the /etc/X11/xorg.conf matches the file you
specified in 3)
[Regression Potential]
Low, the above mentioned changes are already in Artful, and will not affect
the system's behaviour unless new configuration files are put in the
/usr/share/gpu-manager.d/ directory.
__
This feature has been implemented for Intel (ex. gpumanager_uxa), which is
parsing kernel parameter to add option in xorg.conf (commit ff3a4e54).
And now Nvidia also need this feature to add Option
"nvidiaXineramaInfo" "off" to fix some issues.
Btw, I'm thinking it might be a more flexible to have a config file
which user could add all options as they want so that we could prevent
keeping change gpu-manager when some more options are needed in the
future.
Needed by LP: #1653592
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1667198/+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 1667198] Re: gpu-manager should also support using custom xorg.conf files for Nvidia
This bug was fixed in the package ubuntu-drivers-common - 1:0.4.17.3
---
ubuntu-drivers-common (1:0.4.17.3) xenial-proposed; urgency=medium
* gpu-manager.{c|py}:
- Add support for using custom xorg.confs with the nvidia
driver (LP: #1667198).
Custom xorg files can be named "non-hybrid" (for non hybrid
systems), "hybrid-performance", and "hybrid-power-saving",
and will have to placed in the /usr/share/gpu-manager.d
directory.
The directory can be overridden by passing another directory
along with the "--custom-xorg-conf-path" parameter.
- Add tests for the custom xorg.confs code and for amdgpu-pro
hybrid support.
-- Alberto Milone Mon, 19 Jun 2017
17:27:33 +0200
** Changed in: ubuntu-drivers-common (Ubuntu Xenial)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/1667198
Title:
gpu-manager should also support using custom xorg.conf files for
Nvidia
Status in HWE Next:
Incomplete
Status in OEM Priority Project:
Confirmed
Status in ubuntu-drivers-common package in Ubuntu:
Fix Released
Status in ubuntu-drivers-common source package in Xenial:
Fix Released
Status in ubuntu-drivers-common source package in Zesty:
Fix Released
Bug description:
SRU Request:
[Impact]
Different GPUs may require different options in the xorg.conf file. Currently
this is not possible, since the options have been hardcoded in gpu-manager to
configure the system automatically.
This new (backported) feature allows users to tell gpu-manager to use
their own custom xorg.confs for their NVIDIA GPUs.
[Test Case]
1) Enable the xenial-proposed repository, and install the
ubuntu-drivers-common and the nvidia-prime packages.
2) Install the nvidia driver.
3) Place your configuration file(s) in the /usr/share/gpu-manager.d
directory.
If you are using a non-hybrid system, you can create the /usr/share
/gpu-manager.d/non-hybrid file. In case of a hybrid system, you can
specify /usr/share/gpu-manager.d/hybrid-performance and/or /usr/share
/gpu-manager.d/hybrid-power-saving, depending on the power profile you
intend to apply your settings to.
4) Restart the system and see if it boots correctly. If unsure, please
attach your /var/log/gpu-manager.log and /var/log/Xorg.0.log
5) Make sure that the /etc/X11/xorg.conf matches the file you
specified in 3)
[Regression Potential]
Low, the above mentioned changes are already in Artful, and will not affect
the system's behaviour unless new configuration files are put in the
/usr/share/gpu-manager.d/ directory.
__
This feature has been implemented for Intel (ex. gpumanager_uxa), which is
parsing kernel parameter to add option in xorg.conf (commit ff3a4e54).
And now Nvidia also need this feature to add Option
"nvidiaXineramaInfo" "off" to fix some issues.
Btw, I'm thinking it might be a more flexible to have a config file
which user could add all options as they want so that we could prevent
keeping change gpu-manager when some more options are needed in the
future.
Needed by LP: #1653592
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1667198/+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 1368640] Re: When backup system, need to click cancel button twice to close Encryption Password Needed page.
This bug was fixed in the package deja-dup - 35.5-0ubuntu1 --- deja-dup (35.5-0ubuntu1) artful; urgency=medium * New upstream release - Fix needing to click cancel twice on progress dialog (LP: #1368640) - Fix a bug when restoring missing files that caused not every older missing files to be shown - No longer show a needed dependency with updates as uninstalled * debian/patches/allow-no-packagekit.patch: - Dropped, applied upstream -- Michael Terry Tue, 22 Aug 2017 18:46:40 -0400 ** Changed in: deja-dup (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to deja-dup in Ubuntu. https://bugs.launchpad.net/bugs/1368640 Title: When backup system, need to click cancel button twice to close Encryption Password Needed page. Status in Déjà Dup: Fix Released Status in Ubuntu Kylin: New Status in deja-dup package in Ubuntu: Fix Released Bug description: When backup system, need to click cancel button twice to close Encryption Password Needed page. You must backuped your system with encryption before. Steps: 1. Enter into System settings-->Backup, 2. Click back up now, backup the system with encryption 3. Click the back up now button again, 4. Click cancel button in Encryption Password Needed page -->Failed. Need to click cancel button twice to close Encryption Password Needed page. Configuration: PC: Dell Vostro OS: Ubuntu kylin 14.10 daily 0912 To manage notifications about this bug go to: https://bugs.launchpad.net/deja-dup/+bug/1368640/+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 1693908] Re: Fullscreen issues with dedicated GPU on Laptop
** Also affects: nvidia-graphics-drivers (Ubuntu) Importance: Undecided Status: New ** Changed in: ubuntu-mate Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/1693908 Title: Fullscreen issues with dedicated GPU on Laptop Status in ubuntu-mate: Invalid Status in nvidia-graphics-drivers package in Ubuntu: New Bug description: Hardware: Lenovo P50, integrated graphics and dedicated NVIDIA graphics, using proprietary drivers. Software: Ubuntu Mate 17.04 Issue: When running in the Intel integrated graphics mode to save power, the GPU and all the display ports wired to the GPU are disabled. Therefore, whenever I use external displays/need more power, I switch to the dedicated "performance" mode with the proprietary NVIDIA driver. This results in fullscreen on the laptop's builtin display not working. Whenever you try to drag a window to the top of the screen on the laptop display, the preview shows it on the external display/it goes fullscreen on the external display, and when pressing the fullscreen button it automatically always becomes fullscreen on the external display. Same goes for fullscreen video, it all goes to the external display, not the builtin laptop display. If needed, I can record/upload a video of the behavior so I can better explain it, let me know if there's anything I need to do, thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1693908/+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 874535] Re: Volume Slider Jumps, due to rapidly changing hardware jack sense state
I'm just started experiencing this in 16.04 this evening.
** Tags added: xenial
--
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/874535
Title:
Volume Slider Jumps, due to rapidly changing hardware jack sense state
Status in alsa-driver package in Ubuntu:
Triaged
Bug description:
In Oneiric Release, The volume slider randomly jump down a notch or
two for fraction of a second, even when there is no audio playing on
the system. If mute is selected, the menu will quickly flip out of
mute mode and back again. This change actually affects the audio
output, resulting in pops correlated with the volume changes.
nVidia GF106 Audio Controller
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 1.23-0ubuntu4
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel], device 0: ALC892 Analog [ALC892 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: jfrorie9959 F pulseaudio
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xfb9f8000 irq 54'
Mixer name : 'Realtek ALC892'
Components : 'HDA:10ec0892,1462522c,00100302'
Controls : 35
Simple ctrls : 20
Card2.Amixer.info:
Card hw:2 'Generic'/'HD-Audio Generic at 0xfbcf8000 irq 55'
Mixer name : 'ATI R6xx HDMI'
Components : 'HDA:1002aa01,00aa0100,00100200'
Controls : 4
Simple ctrls : 1
Card2.Amixer.values:
Simple mixer control 'IEC958',0
Capabilities: pswitch pswitch-joined penum
Playback channels: Mono
Mono: Playback [on]
DistroRelease: Ubuntu 11.10
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
Package: pulseaudio 1:1.0-0ubuntu3.1
PackageArchitecture: amd64
ProcEnviron:
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 3.0.0-14.23-generic 3.0.9
Tags: oneiric running-unity
Uname: Linux 3.0.0-14-generic x86_64
UpgradeStatus: Upgraded to oneiric on 2011-10-14 (82 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 11/16/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: V25.0
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: X58A-GD45 (MS-7522)
dmi.board.vendor: MSI
dmi.board.version: 5.0
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
dmi.chassis.version: 5.0
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrV25.0:bd11/16/2010:svnMSI:pnMS-7522:pvr5.0:rvnMSI:rnX58A-GD45(MS-7522):rvr5.0:cvnMICRO-STARINTERNATIONALCO.,LTD:ct3:cvr5.0:
dmi.product.name: MS-7522
dmi.product.version: 5.0
dmi.sys.vendor: MSI
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/874535/+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 1712283] Re: Cannot resolve DNS in artful daily
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: casper (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1712283 Title: Cannot resolve DNS in artful daily Status in casper package in Ubuntu: Confirmed Status in livecd-rootfs package in Ubuntu: Confirmed Status in netcfg package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Triaged Status in systemd package in Ubuntu: Confirmed Bug description: in the current daily 21 Aug 2017, I can ping 8.8.8.8 from a live session / installed session - running on virtualbox 5.1.26. However I cannot ping google.com - "Name or service not known" Kind of difficult to run ubuntu-bug here without a fully functioning network. Happy to provide more details - please can someone guide me producing a much better bug-report? my zesty VM is working just fine. As of a week ago, my artful daily was working just fine also. * /etc/resolv.conf is empty file on most images built, which is not right, it should point to ../run/systemd/resolve/stub-resolv.conf. Should be fixed in image generation? systemd? * Adding a hack, to create /etc/resolv.conf if it does not exist, or is empty. src:systemd * network-manager does not consider that dns is managed by resolved if .53 is present in /etc/resolv.conf or if it points to stub- resolv.conf. src:network-manager * netcfg has integrtation w.r.t. /etc/resolv.conf and resolvconf. Needs checking / fixing * caster has resolvconf integration * livecd-rootfs has resolvconf integration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1712283/+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
