[Desktop-packages] [Bug 1878109] Re: Certain features in the Sharing panel fail with D-Bus related messages when gnome-control-center is run over ssh -X
Issue reported upstream and bug watch added -- 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/1878109 Title: Certain features in the Sharing panel fail with D-Bus related messages when gnome-control-center is run over ssh -X Status in gnome-control-center: Unknown Status in gnome-control-center package in Ubuntu: New Bug description: When I run gnome-control-center (1:3.36.1-1ubuntu5) on a remote Ubuntu 20.04 host over ssh -X, trying to enable Screen Sharing (VNC) or Media Sharing in the Sharing panel (*) fails with the following D-Bus related messages on the standard error: -- (gnome-control-center:25937): sharing-cc-panel-WARNING **: 00:15:12.770: couldn't list networks: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SettingsDaemon.Sharing was not provided by any .service files (gnome-control-center:25937): sharing-cc-panel-WARNING **: 00:15:28.646: Failed to enable service vino-server: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SettingsDaemon.Sharing was not provided by any .service files (gnome-control-center:25937): sharing-cc-panel-WARNING **: 00:15:54.309: Failed to enable service rygel: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SettingsDaemon.Sharing was not provided by any .service files -- What does this mean? Can I do anything about it? A remote user, sitting in front of the remote computer, can enable Screen Sharing or Media Sharing in gnome-control-center themselves. Failure to enable only occurs over ssh -X, as far as I can tell. Looking up this error online led me down a D-Bus rabbit hole. I found many year-old StackExchange answers that recommend setting various environment variables and/or running dbus-launch to start a session bus instance of dbus-daemon, in case of D-Bus related errors. I am rather unfamiliar with D-Bus, but I can see using ps -ef | grep dbus that a session bus instance of dbus-daemon is already running. It has been started under my UID at the time of my SSH login. So I'm wary of those old resources. I have tried following their instructions though, for completeness sake, but to no avail. I can provide more information if necessary. (*) This odd situation happened when I had to provide technical support over VNC to an older user whose computer I had previously set up with SSH access. Hence why I was using ssh -X to try and enable VNC in gnome-control-center... To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1878109/+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 1878109] Re: Certain features in the Sharing panel fail with D-Bus related messages when gnome-control-center is run over ssh -X
** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/-/issues #999 https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/999 ** Also affects: gnome-control-center via https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/999 Importance: Unknown Status: Unknown -- 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/1878109 Title: Certain features in the Sharing panel fail with D-Bus related messages when gnome-control-center is run over ssh -X Status in gnome-control-center: Unknown Status in gnome-control-center package in Ubuntu: New Bug description: When I run gnome-control-center (1:3.36.1-1ubuntu5) on a remote Ubuntu 20.04 host over ssh -X, trying to enable Screen Sharing (VNC) or Media Sharing in the Sharing panel (*) fails with the following D-Bus related messages on the standard error: -- (gnome-control-center:25937): sharing-cc-panel-WARNING **: 00:15:12.770: couldn't list networks: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SettingsDaemon.Sharing was not provided by any .service files (gnome-control-center:25937): sharing-cc-panel-WARNING **: 00:15:28.646: Failed to enable service vino-server: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SettingsDaemon.Sharing was not provided by any .service files (gnome-control-center:25937): sharing-cc-panel-WARNING **: 00:15:54.309: Failed to enable service rygel: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SettingsDaemon.Sharing was not provided by any .service files -- What does this mean? Can I do anything about it? A remote user, sitting in front of the remote computer, can enable Screen Sharing or Media Sharing in gnome-control-center themselves. Failure to enable only occurs over ssh -X, as far as I can tell. Looking up this error online led me down a D-Bus rabbit hole. I found many year-old StackExchange answers that recommend setting various environment variables and/or running dbus-launch to start a session bus instance of dbus-daemon, in case of D-Bus related errors. I am rather unfamiliar with D-Bus, but I can see using ps -ef | grep dbus that a session bus instance of dbus-daemon is already running. It has been started under my UID at the time of my SSH login. So I'm wary of those old resources. I have tried following their instructions though, for completeness sake, but to no avail. I can provide more information if necessary. (*) This odd situation happened when I had to provide technical support over VNC to an older user whose computer I had previously set up with SSH access. Hence why I was using ssh -X to try and enable VNC in gnome-control-center... To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1878109/+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 1878109] Re: Certain features in the Sharing panel fail with D-Bus related messages when gnome-control-center is run over ssh -X
Here is another user reporting the same GDBus errors when trying to enable Screen Sharing on Ubuntu Server 20.04, if I understand correctly: https://askubuntu.com/questions/1238329 -- 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/1878109 Title: Certain features in the Sharing panel fail with D-Bus related messages when gnome-control-center is run over ssh -X Status in gnome-control-center package in Ubuntu: New Bug description: When I run gnome-control-center (1:3.36.1-1ubuntu5) on a remote Ubuntu 20.04 host over ssh -X, trying to enable Screen Sharing (VNC) or Media Sharing in the Sharing panel (*) fails with the following D-Bus related messages on the standard error: -- (gnome-control-center:25937): sharing-cc-panel-WARNING **: 00:15:12.770: couldn't list networks: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SettingsDaemon.Sharing was not provided by any .service files (gnome-control-center:25937): sharing-cc-panel-WARNING **: 00:15:28.646: Failed to enable service vino-server: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SettingsDaemon.Sharing was not provided by any .service files (gnome-control-center:25937): sharing-cc-panel-WARNING **: 00:15:54.309: Failed to enable service rygel: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SettingsDaemon.Sharing was not provided by any .service files -- What does this mean? Can I do anything about it? A remote user, sitting in front of the remote computer, can enable Screen Sharing or Media Sharing in gnome-control-center themselves. Failure to enable only occurs over ssh -X, as far as I can tell. Looking up this error online led me down a D-Bus rabbit hole. I found many year-old StackExchange answers that recommend setting various environment variables and/or running dbus-launch to start a session bus instance of dbus-daemon, in case of D-Bus related errors. I am rather unfamiliar with D-Bus, but I can see using ps -ef | grep dbus that a session bus instance of dbus-daemon is already running. It has been started under my UID at the time of my SSH login. So I'm wary of those old resources. I have tried following their instructions though, for completeness sake, but to no avail. I can provide more information if necessary. (*) This odd situation happened when I had to provide technical support over VNC to an older user whose computer I had previously set up with SSH access. Hence why I was using ssh -X to try and enable VNC in gnome-control-center... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1878109/+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 1878109] [NEW] Certain features in the Sharing panel fail with D-Bus related messages when gnome-control-center is run over ssh -X
Public bug reported: When I run gnome-control-center (1:3.36.1-1ubuntu5) on a remote Ubuntu 20.04 host over ssh -X, trying to enable Screen Sharing (VNC) or Media Sharing in the Sharing panel (*) fails with the following D-Bus related messages on the standard error: -- (gnome-control-center:25937): sharing-cc-panel-WARNING **: 00:15:12.770: couldn't list networks: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SettingsDaemon.Sharing was not provided by any .service files (gnome-control-center:25937): sharing-cc-panel-WARNING **: 00:15:28.646: Failed to enable service vino-server: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SettingsDaemon.Sharing was not provided by any .service files (gnome-control-center:25937): sharing-cc-panel-WARNING **: 00:15:54.309: Failed to enable service rygel: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SettingsDaemon.Sharing was not provided by any .service files -- What does this mean? Can I do anything about it? A remote user, sitting in front of the remote computer, can enable Screen Sharing or Media Sharing in gnome-control-center themselves. Failure to enable only occurs over ssh -X, as far as I can tell. Looking up this error online led me down a D-Bus rabbit hole. I found many year-old StackExchange answers that recommend setting various environment variables and/or running dbus-launch to start a session bus instance of dbus-daemon, in case of D-Bus related errors. I am rather unfamiliar with D-Bus, but I can see using ps -ef | grep dbus that a session bus instance of dbus-daemon is already running. It has been started under my UID at the time of my SSH login. So I'm wary of those old resources. I have tried following their instructions though, for completeness sake, but to no avail. I can provide more information if necessary. (*) This odd situation happened when I had to provide technical support over VNC to an older user whose computer I had previously set up with SSH access. Hence why I was using ssh -X to try and enable VNC in gnome- control-center... ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New -- 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/1878109 Title: Certain features in the Sharing panel fail with D-Bus related messages when gnome-control-center is run over ssh -X Status in gnome-control-center package in Ubuntu: New Bug description: When I run gnome-control-center (1:3.36.1-1ubuntu5) on a remote Ubuntu 20.04 host over ssh -X, trying to enable Screen Sharing (VNC) or Media Sharing in the Sharing panel (*) fails with the following D-Bus related messages on the standard error: -- (gnome-control-center:25937): sharing-cc-panel-WARNING **: 00:15:12.770: couldn't list networks: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SettingsDaemon.Sharing was not provided by any .service files (gnome-control-center:25937): sharing-cc-panel-WARNING **: 00:15:28.646: Failed to enable service vino-server: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SettingsDaemon.Sharing was not provided by any .service files (gnome-control-center:25937): sharing-cc-panel-WARNING **: 00:15:54.309: Failed to enable service rygel: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SettingsDaemon.Sharing was not provided by any .service files -- What does this mean? Can I do anything about it? A remote user, sitting in front of the remote computer, can enable Screen Sharing or Media Sharing in gnome-control-center themselves. Failure to enable only occurs over ssh -X, as far as I can tell. Looking up this error online led me down a D-Bus rabbit hole. I found many year-old StackExchange answers that recommend setting various environment variables and/or running dbus-launch to start a session bus instance of dbus-daemon, in case of D-Bus related errors. I am rather unfamiliar with D-Bus, but I can see using ps -ef | grep dbus that a session bus instance of dbus-daemon is already running. It has been started under my UID at the time of my SSH login. So I'm wary of those old resources. I have tried following their instructions though, for completeness sake, but to no avail. I can provide more information if necessary. (*) This odd situation happened when I had to provide technical support over VNC to an older user whose computer I had previously set up with SSH access. Hence why I was using ssh -X to try and enable VNC in gnome-control-center... To
[Desktop-packages] [Bug 1847829] Re: Three finger tap to middle click stopped working
Hi Rip, > Three fingers results in a right-click now for whatever > reason. I have the appropriate settings enabled in KDE > (I haven't changed them). > > Middle click works sometimes after restarting the device > via xinput, but this is very rare. If your three-finger taps are inconsistent (sometimes registered as left clicks, sometimes as right clicks, sometimes as middle clicks), it could be related to the following upstream issues: https://gitlab.freedesktop.org/libinput/libinput/-/issues/361 https://gitlab.freedesktop.org/libinput/libinput/-/issues/473 I am also affected by inconsistent three-finger taps (most often registered as right clicks) on a "SynPS/2 Synaptics TouchPad". ** Bug watch added: gitlab.freedesktop.org/libinput/libinput/-/issues #361 https://gitlab.freedesktop.org/libinput/libinput/-/issues/361 ** Bug watch added: gitlab.freedesktop.org/libinput/libinput/-/issues #473 https://gitlab.freedesktop.org/libinput/libinput/-/issues/473 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu. https://bugs.launchpad.net/bugs/1847829 Title: Three finger tap to middle click stopped working Status in xserver-xorg-input-libinput package in Ubuntu: New Bug description: I haven't expereinced this before, though a google search shows complaints from at least 2016. Three fingers results in a right-click now for whatever reason. I have the appropriate settings enabled in KDE (I haven't changed them). Middle click works sometimes after restarting the device via xinput, but this is very rare. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xserver-xorg-input-libinput 0.28.2-2 ProcVersionSignature: Ubuntu 5.0.0-31.33-generic 5.0.21 Uname: Linux 5.0.0-31-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CurrentDesktop: KDE Date: Sat Oct 12 03:40:48 2019 DistUpgraded: 2019-04-27 18:56:54,539 DEBUG new topwidget None DistroCodename: disco DistroVariant: ubuntu InstallationDate: Installed on 2018-11-15 (330 days ago) InstallationMedia: Kubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) MachineType: LENOVO 20AQCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-31-generic root=/dev/mapper/kubuntu--vg-root ro psmouse.synaptics_intertouch=0 quiet splash vt.handoff=1 SourcePackage: xserver-xorg-input-libinput UpgradeStatus: Upgraded to disco on 2019-04-27 (167 days ago) dmi.bios.date: 03/20/2018 dmi.bios.vendor: LENOVO dmi.bios.version: GJET98WW (2.48 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AQCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 PRO dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGJET98WW(2.48):bd03/20/2018:svnLENOVO:pn20AQCTO1WW:pvrThinkPadT440s:rvnLENOVO:rn20AQCTO1WW:rvrSDK0E50510PRO:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T440s dmi.product.name: 20AQCTO1WW dmi.product.sku: LENOVO_MT_20AQ_BU_Think_FM_ThinkPad T440s dmi.product.version: ThinkPad T440s dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~19.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~19.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-libinput/+bug/1847829/+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 1877798] [NEW] The "areas" click-method doesn't work with "SynPS/2 Synaptics TouchPad" on "Clevo N141ZU" laptop
Public bug reported: I'm trying to switch from the "fingers" click-method to the "areas" click-method, because tapping with three fingers is awkward and I find that my three-fingers taps are rarely registered as such. * "fingers": single-finger tap for a click, two-finger tap for a right click, three-finger tap for a middle click * "areas": tap in the lower right corner for a right click, tap in the upper right corner for a middle click After running the following command: gsettings set org.gnome.desktop.peripherals.touchpad click-method \ "'areas'" I can verify with gsettings get... that the click-method is now "areas", however tapping in the lower/upper right corners of the touchpad does not elicit the expected right/middle clicks, whereas tapping with two fingers elicits a right click. This remains the case even after rebooting the computer. It's as if the click-method was ignored and defaulted to "fingers". I couldn't find any similar bug reports and don't know how to investigate this problem further. I assume this problem is specific to my hardware, otherwise it would have been noticed already. I attach the output of the following commands: cat /proc/bus/input/devices xinput --list xinput --list-props 13 # where 13 is the touchpad's ID Should I report this issue to upstream libinput (www.freedesktop.org/wiki/Software/libinput)? Or could this be something to do with GNOME instead? Using Ubuntu 20.04 with libinput 1.15.5-1 and xserver-xorg-input- libinput 0.29.0-1. ** Affects: xserver-xorg-input-libinput (Ubuntu) Importance: Undecided Status: New ** Attachment added: "cat /proc/bus/input/devices" https://bugs.launchpad.net/bugs/1877798/+attachment/5369253/+files/devices.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu. https://bugs.launchpad.net/bugs/1877798 Title: The "areas" click-method doesn't work with "SynPS/2 Synaptics TouchPad" on "Clevo N141ZU" laptop Status in xserver-xorg-input-libinput package in Ubuntu: New Bug description: I'm trying to switch from the "fingers" click-method to the "areas" click-method, because tapping with three fingers is awkward and I find that my three-fingers taps are rarely registered as such. * "fingers": single-finger tap for a click, two-finger tap for a right click, three-finger tap for a middle click * "areas": tap in the lower right corner for a right click, tap in the upper right corner for a middle click After running the following command: gsettings set org.gnome.desktop.peripherals.touchpad click-method \ "'areas'" I can verify with gsettings get... that the click-method is now "areas", however tapping in the lower/upper right corners of the touchpad does not elicit the expected right/middle clicks, whereas tapping with two fingers elicits a right click. This remains the case even after rebooting the computer. It's as if the click-method was ignored and defaulted to "fingers". I couldn't find any similar bug reports and don't know how to investigate this problem further. I assume this problem is specific to my hardware, otherwise it would have been noticed already. I attach the output of the following commands: cat /proc/bus/input/devices xinput --list xinput --list-props 13 # where 13 is the touchpad's ID Should I report this issue to upstream libinput (www.freedesktop.org/wiki/Software/libinput)? Or could this be something to do with GNOME instead? Using Ubuntu 20.04 with libinput 1.15.5-1 and xserver-xorg-input- libinput 0.29.0-1. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-libinput/+bug/1877798/+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 1877798] Re: The "areas" click-method doesn't work with "SynPS/2 Synaptics TouchPad" on "Clevo N141ZU" laptop
** Attachment added: "xinput --list-props 13" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-libinput/+bug/1877798/+attachment/5369255/+files/xinput--list-props13.txt ** Description changed: I'm trying to switch from the "fingers" click-method to the "areas" click-method, because tapping with three fingers is awkward and I find that my three-fingers taps are rarely registered as such. - * "fingers": single-finger tap for a click, two-finger tap for a right click, - three-finger tap for a middle click - * "areas": tap in the lower right corner for a right click, tap in the upper - right corner for a middle click + * "fingers": single-finger tap for a click, two-finger tap for a right + click, three-finger tap for a middle click + * "areas": tap in the lower right corner for a right click, tap in the + upper right corner for a middle click After running the following command: - gsettings set org.gnome.desktop.peripherals.touchpad click-method - "'areas'" + gsettings set org.gnome.desktop.peripherals.touchpad click-method \ + "'areas'" I can verify with gsettings get... that the click-method is now "areas", however tapping in the lower/upper right corners of the touchpad does not elicit the expected right/middle clicks, whereas tapping with two fingers elicits a right click. This remains the case even after rebooting the computer. It's as if the click-method was ignored and defaulted to "fingers". I couldn't find any similar bug reports and don't know how to investigate this problem further. I assume this problem is specific to my hardware, otherwise it would have been noticed already. I attach the output of the following commands: - cat /proc/bus/input/devices - xinput --list - xinput --list-props 13 # where 13 is the touchpad's ID + cat /proc/bus/input/devices + xinput --list + xinput --list-props 13 # where 13 is the touchpad's ID Should I report this issue to upstream libinput (www.freedesktop.org/wiki/Software/libinput)? Or could this be something to do with GNOME instead? Using Ubuntu 20.04 with libinput 1.15.5-1 and xserver-xorg-input- libinput 0.29.0-1. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu. https://bugs.launchpad.net/bugs/1877798 Title: The "areas" click-method doesn't work with "SynPS/2 Synaptics TouchPad" on "Clevo N141ZU" laptop Status in xserver-xorg-input-libinput package in Ubuntu: New Bug description: I'm trying to switch from the "fingers" click-method to the "areas" click-method, because tapping with three fingers is awkward and I find that my three-fingers taps are rarely registered as such. * "fingers": single-finger tap for a click, two-finger tap for a right click, three-finger tap for a middle click * "areas": tap in the lower right corner for a right click, tap in the upper right corner for a middle click After running the following command: gsettings set org.gnome.desktop.peripherals.touchpad click-method \ "'areas'" I can verify with gsettings get... that the click-method is now "areas", however tapping in the lower/upper right corners of the touchpad does not elicit the expected right/middle clicks, whereas tapping with two fingers elicits a right click. This remains the case even after rebooting the computer. It's as if the click-method was ignored and defaulted to "fingers". I couldn't find any similar bug reports and don't know how to investigate this problem further. I assume this problem is specific to my hardware, otherwise it would have been noticed already. I attach the output of the following commands: cat /proc/bus/input/devices xinput --list xinput --list-props 13 # where 13 is the touchpad's ID Should I report this issue to upstream libinput (www.freedesktop.org/wiki/Software/libinput)? Or could this be something to do with GNOME instead? Using Ubuntu 20.04 with libinput 1.15.5-1 and xserver-xorg-input- libinput 0.29.0-1. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-libinput/+bug/1877798/+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 1877798] Re: The "areas" click-method doesn't work with "SynPS/2 Synaptics TouchPad" on "Clevo N141ZU" laptop
** Attachment added: "xinput --list" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-libinput/+bug/1877798/+attachment/5369254/+files/xinput--list.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu. https://bugs.launchpad.net/bugs/1877798 Title: The "areas" click-method doesn't work with "SynPS/2 Synaptics TouchPad" on "Clevo N141ZU" laptop Status in xserver-xorg-input-libinput package in Ubuntu: New Bug description: I'm trying to switch from the "fingers" click-method to the "areas" click-method, because tapping with three fingers is awkward and I find that my three-fingers taps are rarely registered as such. * "fingers": single-finger tap for a click, two-finger tap for a right click, three-finger tap for a middle click * "areas": tap in the lower right corner for a right click, tap in the upper right corner for a middle click After running the following command: gsettings set org.gnome.desktop.peripherals.touchpad click-method \ "'areas'" I can verify with gsettings get... that the click-method is now "areas", however tapping in the lower/upper right corners of the touchpad does not elicit the expected right/middle clicks, whereas tapping with two fingers elicits a right click. This remains the case even after rebooting the computer. It's as if the click-method was ignored and defaulted to "fingers". I couldn't find any similar bug reports and don't know how to investigate this problem further. I assume this problem is specific to my hardware, otherwise it would have been noticed already. I attach the output of the following commands: cat /proc/bus/input/devices xinput --list xinput --list-props 13 # where 13 is the touchpad's ID Should I report this issue to upstream libinput (www.freedesktop.org/wiki/Software/libinput)? Or could this be something to do with GNOME instead? Using Ubuntu 20.04 with libinput 1.15.5-1 and xserver-xorg-input- libinput 0.29.0-1. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-libinput/+bug/1877798/+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 1864539] Re: gnome-screenshot adds unnecessary transparent padding around window screenshots
Indeed! Thank you for pointing that out. I also found https://gitlab.gnome.org/GNOME/gnome-screenshot/-/issues/82 and linked issues and merge requests, for additional context. So the option to include/remove-border is removed from the upstream GUI and so are the border effects. The CLI isn't updated yet though. Window screenshots now always include a faint shadow on all four sides of the window, and that's why there's transparent padding added all around. That's the new expected behavior. Would it make sense, and would it be possible, for the recently released 3.37.1 version of gnome-screenshot to be SRU'd into Ubuntu 19.10 and 20.04 then? With the current 3.36.0 version, it looks like border inclusion/removal and the border shadow/none effect are broken, or at least really don't work as the GUI states. ** Bug watch added: gitlab.gnome.org/GNOME/gnome-screenshot/-/issues #82 https://gitlab.gnome.org/GNOME/gnome-screenshot/-/issues/82 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screenshot in Ubuntu. https://bugs.launchpad.net/bugs/1864539 Title: gnome-screenshot adds unnecessary transparent padding around window screenshots Status in gnome-screenshot package in Ubuntu: Triaged Bug description: When taking a window screenshot with gnome-screenshot in 19.10 and 20.04, a 20 to 25 pixel wide area of transparent padding (alpha) is added around the screenshot. See attached screenshots, possibly with an external image viewer that displays transparency as e.g. a checkered pattern, if your browser doesn't. The expected behavior is that of 18.04: * If a border effect is selected, the smallest necessary amount of transparent padding is added to accommodate the effect. * If no border effect is selected, no transparent padding is added (is there even a need for an alpha channel in this case?). ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-screenshot 3.33.90-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Feb 24 14:45:28 2020 ExecutablePath: /usr/bin/gnome-screenshot InstallationDate: Installed on 2019-10-20 (127 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191014) ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=en_US.UTF-8 SourcePackage: gnome-screenshot UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screenshot/+bug/1864539/+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 1864539] Re: gnome-screenshot adds unnecessary transparent padding around window screenshots
It appears to be an upstream issue, as the only Ubuntu patches in gnome- screenshot 3.36.0 are related to: * Unity support * Disabling the possibility of taking a screenshot of a window or an area by right-clicking on gnome-screenshot's desktop icon, because this feature doesn't work in Wayland (bug 1720262) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screenshot in Ubuntu. https://bugs.launchpad.net/bugs/1864539 Title: gnome-screenshot adds unnecessary transparent padding around window screenshots Status in gnome-screenshot package in Ubuntu: Confirmed Bug description: When taking a window screenshot with gnome-screenshot in 19.10 and 20.04, a 20 to 25 pixel wide area of transparent padding (alpha) is added around the screenshot. See attached screenshots, possibly with an external image viewer that displays transparency as e.g. a checkered pattern, if your browser doesn't. The expected behavior is that of 18.04: * If a border effect is selected, the smallest necessary amount of transparent padding is added to accommodate the effect. * If no border effect is selected, no transparent padding is added (is there even a need for an alpha channel in this case?). ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-screenshot 3.33.90-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Feb 24 14:45:28 2020 ExecutablePath: /usr/bin/gnome-screenshot InstallationDate: Installed on 2019-10-20 (127 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191014) ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=en_US.UTF-8 SourcePackage: gnome-screenshot UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screenshot/+bug/1864539/+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 1864539] Re: gnome-screenshot adds unnecessary transparent padding around window screenshots
** Attachment added: "With --include-border and --border-effect=shadow" https://bugs.launchpad.net/ubuntu/+source/gnome-screenshot/+bug/1864539/+attachment/5367065/+files/include-border-and-shadow-border-effect.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screenshot in Ubuntu. https://bugs.launchpad.net/bugs/1864539 Title: gnome-screenshot adds unnecessary transparent padding around window screenshots Status in gnome-screenshot package in Ubuntu: Confirmed Bug description: When taking a window screenshot with gnome-screenshot in 19.10 and 20.04, a 20 to 25 pixel wide area of transparent padding (alpha) is added around the screenshot. See attached screenshots, possibly with an external image viewer that displays transparency as e.g. a checkered pattern, if your browser doesn't. The expected behavior is that of 18.04: * If a border effect is selected, the smallest necessary amount of transparent padding is added to accommodate the effect. * If no border effect is selected, no transparent padding is added (is there even a need for an alpha channel in this case?). ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-screenshot 3.33.90-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Feb 24 14:45:28 2020 ExecutablePath: /usr/bin/gnome-screenshot InstallationDate: Installed on 2019-10-20 (127 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191014) ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=en_US.UTF-8 SourcePackage: gnome-screenshot UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screenshot/+bug/1864539/+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 1864539] Re: gnome-screenshot adds unnecessary transparent padding around window screenshots
** Attachment added: "With --include-border and --border-effect=none" https://bugs.launchpad.net/ubuntu/+source/gnome-screenshot/+bug/1864539/+attachment/5367064/+files/include-border-and-no-border-effect.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screenshot in Ubuntu. https://bugs.launchpad.net/bugs/1864539 Title: gnome-screenshot adds unnecessary transparent padding around window screenshots Status in gnome-screenshot package in Ubuntu: Confirmed Bug description: When taking a window screenshot with gnome-screenshot in 19.10 and 20.04, a 20 to 25 pixel wide area of transparent padding (alpha) is added around the screenshot. See attached screenshots, possibly with an external image viewer that displays transparency as e.g. a checkered pattern, if your browser doesn't. The expected behavior is that of 18.04: * If a border effect is selected, the smallest necessary amount of transparent padding is added to accommodate the effect. * If no border effect is selected, no transparent padding is added (is there even a need for an alpha channel in this case?). ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-screenshot 3.33.90-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Feb 24 14:45:28 2020 ExecutablePath: /usr/bin/gnome-screenshot InstallationDate: Installed on 2019-10-20 (127 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191014) ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=en_US.UTF-8 SourcePackage: gnome-screenshot UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screenshot/+bug/1864539/+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 1864539] Re: gnome-screenshot adds unnecessary transparent padding around window screenshots
** Attachment added: "With --remove-border" https://bugs.launchpad.net/ubuntu/+source/gnome-screenshot/+bug/1864539/+attachment/5367066/+files/remove-border.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screenshot in Ubuntu. https://bugs.launchpad.net/bugs/1864539 Title: gnome-screenshot adds unnecessary transparent padding around window screenshots Status in gnome-screenshot package in Ubuntu: Confirmed Bug description: When taking a window screenshot with gnome-screenshot in 19.10 and 20.04, a 20 to 25 pixel wide area of transparent padding (alpha) is added around the screenshot. See attached screenshots, possibly with an external image viewer that displays transparency as e.g. a checkered pattern, if your browser doesn't. The expected behavior is that of 18.04: * If a border effect is selected, the smallest necessary amount of transparent padding is added to accommodate the effect. * If no border effect is selected, no transparent padding is added (is there even a need for an alpha channel in this case?). ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-screenshot 3.33.90-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Feb 24 14:45:28 2020 ExecutablePath: /usr/bin/gnome-screenshot InstallationDate: Installed on 2019-10-20 (127 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191014) ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=en_US.UTF-8 SourcePackage: gnome-screenshot UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screenshot/+bug/1864539/+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 1864539] Re: gnome-screenshot adds unnecessary transparent padding around window screenshots
I can confirm this bug. I have updated the bug report with more precise information, and I'm adding additional screenshots to demonstrate the issue. Additionally, I've noted that: * There is no difference between --include-border and --remove-border: the window border is included in the screenshot in any case. It may be an unrelated bug though. * The documentation (man and --help) doesn't state which of --include- border or --remove-border is the default. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screenshot in Ubuntu. https://bugs.launchpad.net/bugs/1864539 Title: gnome-screenshot adds unnecessary transparent padding around window screenshots Status in gnome-screenshot package in Ubuntu: Confirmed Bug description: When taking a window screenshot with gnome-screenshot in 19.10 and 20.04, a 20 to 25 pixel wide area of transparent padding (alpha) is added around the screenshot. See attached screenshots, possibly with an external image viewer that displays transparency as e.g. a checkered pattern, if your browser doesn't. The expected behavior is that of 18.04: * If a border effect is selected, the smallest necessary amount of transparent padding is added to accommodate the effect. * If no border effect is selected, no transparent padding is added (is there even a need for an alpha channel in this case?). ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-screenshot 3.33.90-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Feb 24 14:45:28 2020 ExecutablePath: /usr/bin/gnome-screenshot InstallationDate: Installed on 2019-10-20 (127 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191014) ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=en_US.UTF-8 SourcePackage: gnome-screenshot UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screenshot/+bug/1864539/+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 1864539] Re: gnome-screenshot adds unnecessary transparent padding around window screenshots
** Description changed: - Screenshot tool inserts corrupt border area. + When taking a window screenshot with gnome-screenshot in 19.10 and + 20.04, a 20 to 25 pixel wide area of transparent padding (alpha) is + added around the screenshot. - This also applies to Ubuntu 20.04 daily build. + See attached screenshots, possibly with an external image viewer that + displays transparency as e.g. a checkered pattern, if your browser + doesn't. - See attached screenshot. + The expected behavior is that of 18.04: + + * If a border effect is selected, the smallest necessary amount of + transparent padding is added to accommodate the effect. + + * If no border effect is selected, no transparent padding is added (is + there even a need for an alpha channel in this case?). ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-screenshot 3.33.90-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Feb 24 14:45:28 2020 ExecutablePath: /usr/bin/gnome-screenshot InstallationDate: Installed on 2019-10-20 (127 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191014) ProcEnviron: - SHELL=/bin/bash - XDG_RUNTIME_DIR= - PATH=(custom, no user) - LANG=en_US.UTF-8 + SHELL=/bin/bash + XDG_RUNTIME_DIR= + PATH=(custom, no user) + LANG=en_US.UTF-8 SourcePackage: gnome-screenshot UpgradeStatus: No upgrade log present (probably fresh install) ** Tags added: focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screenshot in Ubuntu. https://bugs.launchpad.net/bugs/1864539 Title: gnome-screenshot adds unnecessary transparent padding around window screenshots Status in gnome-screenshot package in Ubuntu: Confirmed Bug description: When taking a window screenshot with gnome-screenshot in 19.10 and 20.04, a 20 to 25 pixel wide area of transparent padding (alpha) is added around the screenshot. See attached screenshots, possibly with an external image viewer that displays transparency as e.g. a checkered pattern, if your browser doesn't. The expected behavior is that of 18.04: * If a border effect is selected, the smallest necessary amount of transparent padding is added to accommodate the effect. * If no border effect is selected, no transparent padding is added (is there even a need for an alpha channel in this case?). ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-screenshot 3.33.90-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Feb 24 14:45:28 2020 ExecutablePath: /usr/bin/gnome-screenshot InstallationDate: Installed on 2019-10-20 (127 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191014) ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=en_US.UTF-8 SourcePackage: gnome-screenshot UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screenshot/+bug/1864539/+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 1864539] Re: gnome-screenshot adds unnecessary transparent padding around window screenshots
** Summary changed: - screenshot tool inserts corrupt border area + gnome-screenshot adds unnecessary transparent padding around window screenshots -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screenshot in Ubuntu. https://bugs.launchpad.net/bugs/1864539 Title: gnome-screenshot adds unnecessary transparent padding around window screenshots Status in gnome-screenshot package in Ubuntu: Confirmed Bug description: When taking a window screenshot with gnome-screenshot in 19.10 and 20.04, a 20 to 25 pixel wide area of transparent padding (alpha) is added around the screenshot. See attached screenshots, possibly with an external image viewer that displays transparency as e.g. a checkered pattern, if your browser doesn't. The expected behavior is that of 18.04: * If a border effect is selected, the smallest necessary amount of transparent padding is added to accommodate the effect. * If no border effect is selected, no transparent padding is added (is there even a need for an alpha channel in this case?). ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-screenshot 3.33.90-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Feb 24 14:45:28 2020 ExecutablePath: /usr/bin/gnome-screenshot InstallationDate: Installed on 2019-10-20 (127 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191014) ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=en_US.UTF-8 SourcePackage: gnome-screenshot UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screenshot/+bug/1864539/+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 1861631] Re: "The AppStream system cache was updated, but some components were ignored. Refer to the verbose log for more information."
*** This bug is a duplicate of bug 1872258 *** https://bugs.launchpad.net/bugs/1872258 Jonathan: Actually that sounds like a question for the update-manager developers, so I've asked it there and subscribed you to it: https://answers.launchpad.net/ubuntu/+source/update- manager/+question/690201 Matthias: Thanks for the downstream patch! It's awesome to see this fixed without having to wait for a new upstream version. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to appstream in Ubuntu. https://bugs.launchpad.net/bugs/1861631 Title: "The AppStream system cache was updated, but some components were ignored. Refer to the verbose log for more information." Status in appstream package in Ubuntu: Invalid Status in gnome-software package in Ubuntu: In Progress Bug description: `apt-get update` and the nightly `apticron --cron` job are reporting: "The AppStream system cache was updated, but some components were ignored. Refer to the verbose log for more information." This is pretty much meaningless to most people who have no idea what AppStream is and what "verbose log" is being referred to. I dug around and managed to discover `appstreamcli refresh-cache --force --verbose`, whose output is attached. I don't know what the "bad" output is or how to fix it. All I know is that I hope Focal isn't going to be generating this message when it ships, because it isn't going to make sense to most people and most people won't know how to fix it and it causes annoying emails from apticron every night. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: appstream 0.12.10-1 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Feb 2 16:01:24 2020 InstallationDate: Installed on 2019-08-16 (170 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: appstream UpgradeStatus: Upgraded to focal on 2020-01-31 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1861631/+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 1861631] Re: "The AppStream system cache was updated, but some components were ignored. Refer to the verbose log for more information."
Hi Jonathan and Dan:
> I don't think either apt nor snap auto-updates will handle this.
I don't think so either, and nor will manual snap updates ("snap
refresh" command).
My assumption is that deb-to-snap and snap-to-deb transitions are
limited to development releases. It would be very surprising to have
such transitions happen once a release is out, wouldn't it? But then
again I don't know.
Canonical's Marcus Tomlinson, who implemented the special deb-to-snap
/snap-to-deb logic in update-manager to fix bug 1868409 and bug 1872958,
could tell us more, and let us know if we now need to do more than run
apt to keep our systems up-to-date. But I'm not sure how to contact him
or his team. This bug, or Launchpad in general, don't seem like the
right place, as it's not a bug. Perhaps a mailing list (which one?), the
Freenode IRC network (which channel?), Ubuntu Discourse or Ask Ubuntu
are better places for this question.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to appstream in Ubuntu.
https://bugs.launchpad.net/bugs/1861631
Title:
"The AppStream system cache was updated, but some components were
ignored. Refer to the verbose log for more information."
Status in appstream package in Ubuntu:
Invalid
Status in gnome-software package in Ubuntu:
In Progress
Bug description:
`apt-get update` and the nightly `apticron --cron` job are reporting:
"The AppStream system cache was updated, but some components were
ignored. Refer to the verbose log for more information."
This is pretty much meaningless to most people who have no idea what
AppStream is and what "verbose log" is being referred to. I dug around
and managed to discover `appstreamcli refresh-cache --force
--verbose`, whose output is attached.
I don't know what the "bad" output is or how to fix it. All I know is
that I hope Focal isn't going to be generating this message when it
ships, because it isn't going to make sense to most people and most
people won't know how to fix it and it causes annoying emails from
apticron every night.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: appstream 0.12.10-1
ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
Uname: Linux 5.4.0-12-generic x86_64
ApportVersion: 2.20.11-0ubuntu16
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun Feb 2 16:01:24 2020
InstallationDate: Installed on 2019-08-16 (170 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
SourcePackage: appstream
UpgradeStatus: Upgraded to focal on 2020-01-31 (2 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1861631/+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 1872221] Re: Updates installed snap-store snap and uninstalled ubuntu-software
Fixed by update-manager version 1:20.04.6 in bug 1872958 ** Package changed: gnome-software (Ubuntu) => update-manager (Ubuntu) ** Changed in: update-manager (Ubuntu) Status: New => Fix Released -- 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/1872221 Title: Updates installed snap-store snap and uninstalled ubuntu-software Status in update-manager package in Ubuntu: Fix Released Bug description: snap store app is also see thru (100% transparent) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-software 3.35.91-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: Budgie:GNOME Date: Sat Apr 11 14:29:33 2020 InstallationDate: Installed on 2020-02-05 (66 days ago) InstallationMedia: Ubuntu-Budgie 20.04 LTS "Focal Fossa" - Alpha amd64 (20200204) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-snap3.35.91-0ubuntu1 SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1872221/+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 1872221] Re: Updates installed snap-store snap and uninstalled ubuntu-software
> Updates installed snap-store snap and uninstalled ubuntu-software This is normal behavior, unless you have manually installed the "gnome- software" package. The Ubuntu Software application on 20.04 is now provided by the "snap-store" snap instead of the "gnome-software" package. More info in https://discourse.ubuntu.com/t/is-ubuntu-software- going-to-be-remove-for-snap-snap-store/14542/ and bug 1868409. > snap store app is also see thru (100% transparent) I'm not sure what you mean, but it sounds like a different bug, possibly against the display system? -- 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/1872221 Title: Updates installed snap-store snap and uninstalled ubuntu-software Status in gnome-software package in Ubuntu: New Bug description: snap store app is also see thru (100% transparent) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-software 3.35.91-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: Budgie:GNOME Date: Sat Apr 11 14:29:33 2020 InstallationDate: Installed on 2020-02-05 (66 days ago) InstallationMedia: Ubuntu-Budgie 20.04 LTS "Focal Fossa" - Alpha amd64 (20200204) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-snap3.35.91-0ubuntu1 SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1872221/+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 1861631] Re: "The AppStream system cache was updated, but some components were ignored. Refer to the verbose log for more information."
Hi Jonathan and Dan: > I am not sure what you mean. There is no "snap-store" deb on my > 20.04 system, nor does "apt search snap-store" yield any results. It's a snap application, which you'll see in the output of the "snap list" command if it is installed. It provides the Ubuntu Software application on 20.04 and replaces the "gnome-software" deb, cf https://discourse.ubuntu.com/t/is-ubuntu-software-going-to-be-remove- for-snap-snap-store/14542 and bug 1868409. If I understand correctly, at this point in time, your system shouldn't have the "gnome-software" deb any longer unless you've manually installed it yourself, and it should have the "snap-store" snap instead. > Furthermore, this bug was initially reported about the output of > apticron showing up in cron job emails; as far as I know, apticron > is independent of gnome-software. This is unclear to me too, but Matthias Klumpp identified the cause of this error as lying with gnome-software metadata, and he fixed it upstream in gnome-software, cf comment 3 on this bug. Perhaps apticron runs apt-get update? > I have an up-to-date focal system and I am still seeing this. I don't see it any more. The plot thickens. You may still have the "gnome-software" deb? If yes, and you don't mind migrating to the "snap- store" snap for you Ubuntu Software application, then you could run the update-manager (the graphical application), it will take care of the transition, see bug 1868409 for details. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to appstream in Ubuntu. https://bugs.launchpad.net/bugs/1861631 Title: "The AppStream system cache was updated, but some components were ignored. Refer to the verbose log for more information." Status in appstream package in Ubuntu: Invalid Status in gnome-software package in Ubuntu: In Progress Bug description: `apt-get update` and the nightly `apticron --cron` job are reporting: "The AppStream system cache was updated, but some components were ignored. Refer to the verbose log for more information." This is pretty much meaningless to most people who have no idea what AppStream is and what "verbose log" is being referred to. I dug around and managed to discover `appstreamcli refresh-cache --force --verbose`, whose output is attached. I don't know what the "bad" output is or how to fix it. All I know is that I hope Focal isn't going to be generating this message when it ships, because it isn't going to make sense to most people and most people won't know how to fix it and it causes annoying emails from apticron every night. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: appstream 0.12.10-1 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Feb 2 16:01:24 2020 InstallationDate: Installed on 2019-08-16 (170 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: appstream UpgradeStatus: Upgraded to focal on 2020-01-31 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1861631/+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 1861631] Re: "The AppStream system cache was updated, but some components were ignored. Refer to the verbose log for more information."
With the replacement of gnome-software by snap-store in 20.04, this bug is no longer apparent. Only users who manually (re-)install gnome- software will see it. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to appstream in Ubuntu. https://bugs.launchpad.net/bugs/1861631 Title: "The AppStream system cache was updated, but some components were ignored. Refer to the verbose log for more information." Status in appstream package in Ubuntu: Invalid Status in gnome-software package in Ubuntu: In Progress Bug description: `apt-get update` and the nightly `apticron --cron` job are reporting: "The AppStream system cache was updated, but some components were ignored. Refer to the verbose log for more information." This is pretty much meaningless to most people who have no idea what AppStream is and what "verbose log" is being referred to. I dug around and managed to discover `appstreamcli refresh-cache --force --verbose`, whose output is attached. I don't know what the "bad" output is or how to fix it. All I know is that I hope Focal isn't going to be generating this message when it ships, because it isn't going to make sense to most people and most people won't know how to fix it and it causes annoying emails from apticron every night. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: appstream 0.12.10-1 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Feb 2 16:01:24 2020 InstallationDate: Installed on 2019-08-16 (170 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: appstream UpgradeStatus: Upgraded to focal on 2020-01-31 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1861631/+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 1861631] Re: "The AppStream system cache was updated, but some components were ignored. Refer to the verbose log for more information."
Please disregard my previous comment. Looking at the code, I realize that the maintainer packaged the upstream gnome-software "3.36.0" tag, not the "gnome-3-36" branch, which makes a lot more sense indeed. So even though the fix is made upstream, it is NOT YET released, and therefore not packaged for Ubuntu. I think this bug is stuck until upstream releases 3.36.1. ** Changed in: gnome-software (Ubuntu) Status: Fix Committed => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to appstream in Ubuntu. https://bugs.launchpad.net/bugs/1861631 Title: "The AppStream system cache was updated, but some components were ignored. Refer to the verbose log for more information." Status in appstream package in Ubuntu: Invalid Status in gnome-software package in Ubuntu: In Progress Bug description: `apt-get update` and the nightly `apticron --cron` job are reporting: "The AppStream system cache was updated, but some components were ignored. Refer to the verbose log for more information." This is pretty much meaningless to most people who have no idea what AppStream is and what "verbose log" is being referred to. I dug around and managed to discover `appstreamcli refresh-cache --force --verbose`, whose output is attached. I don't know what the "bad" output is or how to fix it. All I know is that I hope Focal isn't going to be generating this message when it ships, because it isn't going to make sense to most people and most people won't know how to fix it and it causes annoying emails from apticron every night. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: appstream 0.12.10-1 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Feb 2 16:01:24 2020 InstallationDate: Installed on 2019-08-16 (170 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: appstream UpgradeStatus: Upgraded to focal on 2020-01-31 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1861631/+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 1861631] Re: "The AppStream system cache was updated, but some components were ignored. Refer to the verbose log for more information."
The fix was made upstream on Mar 24 [1], released as part of gnome- software 3.36 on Apr 3 [2], which was packaged for Ubuntu today Apr 6 [3]. I'd say it's just a matter of hours before it's available in the repository :) [1] https://gitlab.gnome.org/GNOME/gnome-software/-/commit/bb7f58f5f88381857cd9b5dbe608e75d459873f1 [2] https://gitlab.gnome.org/GNOME/gnome-software/-/commits/gnome-3-36 [3] https://launchpadlibrarian.net/473131226/gnome-software_3.36.0-0ubuntu1_source.changes ** Changed in: appstream (Ubuntu) Status: Triaged => Invalid ** Changed in: gnome-software (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to appstream in Ubuntu. https://bugs.launchpad.net/bugs/1861631 Title: "The AppStream system cache was updated, but some components were ignored. Refer to the verbose log for more information." Status in appstream package in Ubuntu: Invalid Status in gnome-software package in Ubuntu: Fix Committed Bug description: `apt-get update` and the nightly `apticron --cron` job are reporting: "The AppStream system cache was updated, but some components were ignored. Refer to the verbose log for more information." This is pretty much meaningless to most people who have no idea what AppStream is and what "verbose log" is being referred to. I dug around and managed to discover `appstreamcli refresh-cache --force --verbose`, whose output is attached. I don't know what the "bad" output is or how to fix it. All I know is that I hope Focal isn't going to be generating this message when it ships, because it isn't going to make sense to most people and most people won't know how to fix it and it causes annoying emails from apticron every night. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: appstream 0.12.10-1 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Feb 2 16:01:24 2020 InstallationDate: Installed on 2019-08-16 (170 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: appstream UpgradeStatus: Upgraded to focal on 2020-01-31 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1861631/+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 1730231] Re: Nautilus opens for every mediafile a seperate player when selecting a group of files and pressing Enter
** Bug watch added: gitlab.gnome.org/GNOME/nautilus/issues #117 https://gitlab.gnome.org/GNOME/nautilus/issues/117 ** Also affects: nautilus via https://gitlab.gnome.org/GNOME/nautilus/issues/117 Importance: Unknown Status: Unknown -- 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/1730231 Title: Nautilus opens for every mediafile a seperate player when selecting a group of files and pressing Enter Status in Nautilus: Unknown Status in nautilus package in Ubuntu: Triaged Bug description: Expected behavior: The Player selected as standard opens with a playlist of the (media)files. (This is what actually happens if you select an application with the open with ... dialog) What happens: Nautilus launches for each file a separate instance of the standard-application. Example: 10 mp3 files selected opens 10 player-windows of audacious, qmmp, vlc, mpv or what ever is selected as standard. (I did try all of the named programs) This happens only if the group of files is open via pressing Return or selecting 'open' in context-menu. It does not happen when selecting an application via 'open with ...' in context-menu. Same behavior with groups of png or jpg files and photo-viewers. Reconstruction: 1. Open Nautilus 2. Set a mediaplayer as standard-application for mp3-files. 3. Open a group of mp3-files by selecting them and pressing 'Enter' or using the 'Open'-Item in the context-menu ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: nautilus 1:3.26.0-0ubuntu1 [modified: usr/share/applications/org.gnome.Nautilus.desktop] ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Nov 5 21:02:23 2017 InstallationDate: Installed on 2017-10-28 (7 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1730231/+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 1868409] Re: gnome-{calculator, logs, characters} snaps not removed after the equivalent APT packages are installed on 20.04, and gnome-software APT package not replaced by sna
Thanks for the insight Brian. I indeed rarely use the graphical update
manager. I'm starting to suspect I should manually install the snap-
store and uninstall the gnome-{calculator,logs,characters} snaps to get
in sync with the development release.
** Also affects: gnome-logs (Ubuntu)
Importance: Undecided
Status: New
** Also affects: gnome-characters (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-calculator in Ubuntu.
https://bugs.launchpad.net/bugs/1868409
Title:
gnome-{calculator,logs,characters} snaps not removed after the
equivalent APT packages are installed on 20.04, and gnome-software APT
package not replaced by snap-store
Status in gnome-calculator package in Ubuntu:
New
Status in gnome-characters package in Ubuntu:
New
Status in gnome-logs package in Ubuntu:
New
Status in ubuntu-meta package in Ubuntu:
Confirmed
Bug description:
I'm trialing the development release of Ubuntu 20.04, installed in
December and kept up-to-date by regularly running apt full-upgrade.
I understand from [1] that 20.04 will ship
gnome-{calculator,logs,characters} as APT packages rather than snap
apps, and gnome-software as a snap app (called snap-store) rather than
an APT package.
Following an apt full-upgrade in late February, I now have:
* both the snap and the APT versions of gnome-{calculator,logs,characters}
* still only the APT version of gnome-software, no snap-store
Is this normal? A user in the #ubuntu+1 IRC channel reports that a
fresh install of the development release:
* only features the APT versions of gnome-{calculator,logs,characters}
* features the snap-store (but also the APT version of gnome-software)
Are users of older installs of the development release supposed to
manually uninstall the snap versions of
gnome-{calculator,logs,characters} and manually install the snap-
store?
[1] https://discourse.ubuntu.com/t/is-ubuntu-software-going-to-be-
remove-for-snap-snap-store/14542
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1868409/+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 1861631] Re: "The AppStream system cache was updated, but some components were ignored. Refer to the verbose log for more information."
This bug is still present because the change that Matthias did was unintentionally undone the following week. So it was not shipped as it should have been, as part of gnome-software 3.35.91, which is the current version in Ubuntu. I have signaled this issue upstream. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to appstream in Ubuntu. https://bugs.launchpad.net/bugs/1861631 Title: "The AppStream system cache was updated, but some components were ignored. Refer to the verbose log for more information." Status in appstream package in Ubuntu: Triaged Status in gnome-software package in Ubuntu: Confirmed Bug description: `apt-get update` and the nightly `apticron --cron` job are reporting: "The AppStream system cache was updated, but some components were ignored. Refer to the verbose log for more information." This is pretty much meaningless to most people who have no idea what AppStream is and what "verbose log" is being referred to. I dug around and managed to discover `appstreamcli refresh-cache --force --verbose`, whose output is attached. I don't know what the "bad" output is or how to fix it. All I know is that I hope Focal isn't going to be generating this message when it ships, because it isn't going to make sense to most people and most people won't know how to fix it and it causes annoying emails from apticron every night. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: appstream 0.12.10-1 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Feb 2 16:01:24 2020 InstallationDate: Installed on 2019-08-16 (170 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: appstream UpgradeStatus: Upgraded to focal on 2020-01-31 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1861631/+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 1868409] [NEW] gnome-{calculator, logs, characters} snaps not removed after the equivalent APT packages are installed on 20.04, and gnome-software APT package not replaced by s
Public bug reported:
I'm trialing the development release of Ubuntu 20.04, installed in
December and kept up-to-date by regularly running apt full-upgrade.
I understand from [1] that 20.04 will ship
gnome-{calculator,logs,characters} as APT packages rather than snap
apps, and gnome-software as a snap app (called snap-store) rather than
an APT package.
Following an apt full-upgrade in late February, I now have:
* both the snap and the APT versions of gnome-{calculator,logs,characters}
* still only the APT version of gnome-software, no snap-store
Is this normal? A user in the #ubuntu+1 IRC channel reports that a fresh
install of the development release:
* only features the APT versions of gnome-{calculator,logs,characters}
* features the snap-store (but also the APT version of gnome-software)
Are users of older installs of the development release supposed to
manually uninstall the snap versions of
gnome-{calculator,logs,characters} and manually install the snap-store?
[1] https://discourse.ubuntu.com/t/is-ubuntu-software-going-to-be-
remove-for-snap-snap-store/14542
** Affects: ubuntu-meta (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1868409
Title:
gnome-{calculator,logs,characters} snaps not removed after the
equivalent APT packages are installed on 20.04, and gnome-software APT
package not replaced by snap-store
Status in ubuntu-meta package in Ubuntu:
New
Bug description:
I'm trialing the development release of Ubuntu 20.04, installed in
December and kept up-to-date by regularly running apt full-upgrade.
I understand from [1] that 20.04 will ship
gnome-{calculator,logs,characters} as APT packages rather than snap
apps, and gnome-software as a snap app (called snap-store) rather than
an APT package.
Following an apt full-upgrade in late February, I now have:
* both the snap and the APT versions of gnome-{calculator,logs,characters}
* still only the APT version of gnome-software, no snap-store
Is this normal? A user in the #ubuntu+1 IRC channel reports that a
fresh install of the development release:
* only features the APT versions of gnome-{calculator,logs,characters}
* features the snap-store (but also the APT version of gnome-software)
Are users of older installs of the development release supposed to
manually uninstall the snap versions of
gnome-{calculator,logs,characters} and manually install the snap-
store?
[1] https://discourse.ubuntu.com/t/is-ubuntu-software-going-to-be-
remove-for-snap-snap-store/14542
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1868409/+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 1685754] Re: gnome-terminal unduly forces umask=0022
Ah, OK, thanks. No news since 2018-08 then - I was hoping the GNOME
GitLab would have something new :(
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/1685754
Title:
gnome-terminal unduly forces umask=0022
Status in gedit:
Invalid
Status in gnome-session:
New
Status in GNOME Terminal:
Confirmed
Status in Nautilus:
Confirmed
Status in dbus package in Ubuntu:
Confirmed
Status in gnome-terminal package in Ubuntu:
Confirmed
Bug description:
In order to set the default umask of my users to 027 or 007, I
followed the instructions provided in 'man pam_umask' :
In the 'gecos' field of '/etc/passwd', I have inserted 'umask=027' or
'umask=007' (for myself).
Then, MOST graphical applications systematically run with the correct
umask.
In particular, when I press Alt-F2, run 'xterm sh' and type 'umask',
it systematically displays 0007.
But when I press Alt-F2, run 'gnome-terminal -e sh' and type 'umask',
it systematically displays 0022.
That is BAD, and is a security issue.
Workaround : Inside the newly created '/etc/profile.d/umask.sh', and in each
'~/.bashrc', add following content :
UMASK="$(grep -o "^$USER:.*,umask=0[0-7]*" /etc/passwd)"
if [ "$UMASK" ]; then
umask "${UMASK#$USER:*,umask=}"
fi
In fact, 'gnome-terminal' MUST NOT force umask=022, but keep umask unchanged.
Thank you in advance for a quick correction.
ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: gnome-terminal 3.20.2-1ubuntu8
ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
Uname: Linux 4.10.0-19-generic x86_64
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
CurrentDesktop: X-Cinnamon
Date: Mon Apr 24 08:36:58 2017
InstallationDate: Installed on 2017-03-28 (26 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321)
SourcePackage: gnome-terminal
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/gedit/+bug/1685754/+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 1685754] Re: gnome-terminal unduly forces umask=0022
Does anyone know where this bug is being tracked upstream now? GNOME has
migrated from Bugzilla to GitLab, and I haven't been able to find the
GitLab version of the Bugzilla bug.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/1685754
Title:
gnome-terminal unduly forces umask=0022
Status in gedit:
Invalid
Status in gnome-session:
New
Status in GNOME Terminal:
Confirmed
Status in Nautilus:
Confirmed
Status in dbus package in Ubuntu:
Confirmed
Status in gnome-terminal package in Ubuntu:
Confirmed
Bug description:
In order to set the default umask of my users to 027 or 007, I
followed the instructions provided in 'man pam_umask' :
In the 'gecos' field of '/etc/passwd', I have inserted 'umask=027' or
'umask=007' (for myself).
Then, MOST graphical applications systematically run with the correct
umask.
In particular, when I press Alt-F2, run 'xterm sh' and type 'umask',
it systematically displays 0007.
But when I press Alt-F2, run 'gnome-terminal -e sh' and type 'umask',
it systematically displays 0022.
That is BAD, and is a security issue.
Workaround : Inside the newly created '/etc/profile.d/umask.sh', and in each
'~/.bashrc', add following content :
UMASK="$(grep -o "^$USER:.*,umask=0[0-7]*" /etc/passwd)"
if [ "$UMASK" ]; then
umask "${UMASK#$USER:*,umask=}"
fi
In fact, 'gnome-terminal' MUST NOT force umask=022, but keep umask unchanged.
Thank you in advance for a quick correction.
ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: gnome-terminal 3.20.2-1ubuntu8
ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
Uname: Linux 4.10.0-19-generic x86_64
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
CurrentDesktop: X-Cinnamon
Date: Mon Apr 24 08:36:58 2017
InstallationDate: Installed on 2017-03-28 (26 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321)
SourcePackage: gnome-terminal
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/gedit/+bug/1685754/+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 1132736] Re: Xorg fails to start after installing the Hardware Enablement Stack due to missing symlink after purging old xserver-xorg
Sounds right. I just assumed that there wasn't any users of releases < Trusty any more, as all those releases are EOL. But actually there may still be, indeed. Bug should stay Confirmed until Trusty itself is EOL. -- 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/1132736 Title: Xorg fails to start after installing the Hardware Enablement Stack due to missing symlink after purging old xserver-xorg Status in xorg package in Ubuntu: Invalid Status in xorg-lts-trusty package in Ubuntu: Confirmed Status in xorg-lts-utopic package in Ubuntu: Won't Fix Status in xorg-lts-vivid package in Ubuntu: Fix Released Bug description: Bug: The bug happens whenever the remaining configuration files of the original X stack is removed, ie purging. It does not happen for users who do not explicitly remove those. Workaround: For example, if upgraded 14.04 LTS to the 14.04.2 HWE stack (=14.10/utopic): sudo dpkg-reconfigure xserver-xorg-lts-utopic This restores the symlink /etc/X11/X -> /usr/bin/Xorg --- After installing the hardware enablement stack on precise by running: sudo apt-get install linux-generic-lts-quantal xserver-xorg-lts-quantal Xorg fail to start. There is no error message or anything, just a black screen. Switching to a vt i possible and lightdm/x-0.log shows that a symlink is missing: X: cannot stat /etc/X11/X (No such file or directory), aborting. I updates two computers running precise x86_64 and both had the problem. Just recreating the symlink fixes the problem and then precise runs perfectly fine with the new stack (in fact, it's more stable so far). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1132736/+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 1132736] Re: Xorg fails to start after installing the Hardware Enablement Stack due to missing symlink after purging old xserver-xorg
Still affects xorg-lts-trusty for the users of releases < Trusty LTS, but all of those releases e.g. Precise LTS are EOL now. There is therefore no point in fixing this package, it won't be installed by anybody any more. -- 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/1132736 Title: Xorg fails to start after installing the Hardware Enablement Stack due to missing symlink after purging old xserver-xorg Status in xorg package in Ubuntu: Invalid Status in xorg-lts-trusty package in Ubuntu: Confirmed Status in xorg-lts-utopic package in Ubuntu: Won't Fix Status in xorg-lts-vivid package in Ubuntu: Fix Released Bug description: Bug: The bug happens whenever the remaining configuration files of the original X stack is removed, ie purging. It does not happen for users who do not explicitly remove those. Workaround: For example, if upgraded 14.04 LTS to the 14.04.2 HWE stack (=14.10/utopic): sudo dpkg-reconfigure xserver-xorg-lts-utopic This restores the symlink /etc/X11/X -> /usr/bin/Xorg --- After installing the hardware enablement stack on precise by running: sudo apt-get install linux-generic-lts-quantal xserver-xorg-lts-quantal Xorg fail to start. There is no error message or anything, just a black screen. Switching to a vt i possible and lightdm/x-0.log shows that a symlink is missing: X: cannot stat /etc/X11/X (No such file or directory), aborting. I updates two computers running precise x86_64 and both had the problem. Just recreating the symlink fixes the problem and then precise runs perfectly fine with the new stack (in fact, it's more stable so far). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1132736/+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 989750] Re: repeatedly asks for encryption password when backing up, even though "remember password" is ticked
Awesome, thanks for weighting in Kenneth. I've set the status to "Invalid" (not a bug) for deja-dup since the bug was in duplicity. ** No longer affects: deja-dup ** Changed in: deja-dup (Ubuntu) Status: Confirmed => Invalid -- 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/989750 Title: repeatedly asks for encryption password when backing up, even though "remember password" is ticked Status in Duplicity: Fix Released Status in deja-dup package in Ubuntu: Invalid Bug description: I've set deja-dup to back up automatically, and to encrypt files. But it never gets far: every few seconds, it brings up a "password needed" window somewhere out of sight (behind other windows; but that is another problem/feature), even though I've told it to remember the password. So using this backup software seems entirely impractical; it will never finish. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: deja-dup 20.1-0ubuntu0.2 ProcVersionSignature: Ubuntu 3.0.0-17.30-generic 3.0.22 Uname: Linux 3.0.0-17-generic x86_64 ApportVersion: 1.23-0ubuntu4 Architecture: amd64 Date: Fri Apr 27 09:50:47 2012 InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110921.2) ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, user) LANG=en_CA.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/duplicity/+bug/989750/+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 883742] Re: Deja Dup keeps asking for password
*** This bug is a duplicate of bug 989750 *** https://bugs.launchpad.net/bugs/989750 ** This bug has been marked a duplicate of bug 989750 repeatedly asks for encryption password when backing up, even though "remember password" is ticked -- 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/883742 Title: Deja Dup keeps asking for password Status in deja-dup package in Ubuntu: Confirmed Bug description: Ubuntu 11.10 The last 2 days whenever an automatic backup runs it asks me for my password, which I input. The GUI then says 'preparing backup', before asking for the password again. The password I am inputting is correct, so I am not sure why the backup is not running ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: deja-dup 20.1-0ubuntu0.1 ProcVersionSignature: Ubuntu 3.0.0-13.21-generic 3.0.6 Uname: Linux 3.0.0-13-generic x86_64 ApportVersion: 1.23-0ubuntu4 Architecture: amd64 Date: Sun Oct 30 06:11:29 2011 InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) 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/883742/+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 989750] Re: repeatedly asks for encryption password when backing up, even though "remember password" is ticked
@Joseph: When Vej wrote "the first backup", I think he meant "a full backup" (as opposed to an incremental backup), not the actual first backup of your documents. You can force a full backup by backing up to a new location, e.g. a different folder on the server/disk that you are backing up to. Don't forget to log Déjà-Dup's output in case the issue occurs. Beware that a full backup can take some time, depending on how much data you have, so when running tests, you may want to only backup a few files and folders. Thanks -- 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/989750 Title: repeatedly asks for encryption password when backing up, even though "remember password" is ticked Status in Déjà Dup: Confirmed Status in Duplicity: New Status in deja-dup package in Ubuntu: Confirmed Bug description: I've set deja-dup to back up automatically, and to encrypt files. But it never gets far: every few seconds, it brings up a "password needed" window somewhere out of sight (behind other windows; but that is another problem/feature), even though I've told it to remember the password. So using this backup software seems entirely impractical; it will never finish. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: deja-dup 20.1-0ubuntu0.2 ProcVersionSignature: Ubuntu 3.0.0-17.30-generic 3.0.22 Uname: Linux 3.0.0-17-generic x86_64 ApportVersion: 1.23-0ubuntu4 Architecture: amd64 Date: Fri Apr 27 09:50:47 2012 InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110921.2) ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, user) LANG=en_CA.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/deja-dup/+bug/989750/+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 989750] Re: repeatedly asks for encryption password when backing up, even though "remember password" is ticked
Added this bug to the Duplicity project, as it looks more like a bug in Duplicity than a bug in Déjà-Dup, judging from the currently available log files. Also it's worth noticing that the GPG error reported by Joseph Hedgcorth in comment 24 is not the same as the GPG error reported by Mathias Binke in comment 15, so these two reporters may encounter different issues resulting in the same GPG error code (31). -- 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/989750 Title: repeatedly asks for encryption password when backing up, even though "remember password" is ticked Status in Déjà Dup: Confirmed Status in Duplicity: New Status in deja-dup package in Ubuntu: Confirmed Bug description: I've set deja-dup to back up automatically, and to encrypt files. But it never gets far: every few seconds, it brings up a "password needed" window somewhere out of sight (behind other windows; but that is another problem/feature), even though I've told it to remember the password. So using this backup software seems entirely impractical; it will never finish. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: deja-dup 20.1-0ubuntu0.2 ProcVersionSignature: Ubuntu 3.0.0-17.30-generic 3.0.22 Uname: Linux 3.0.0-17-generic x86_64 ApportVersion: 1.23-0ubuntu4 Architecture: amd64 Date: Fri Apr 27 09:50:47 2012 InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110921.2) ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, user) LANG=en_CA.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/deja-dup/+bug/989750/+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 989750] Re: repeatedly asks for encryption password when backing up, even though "remember password" is ticked
Status changed to "Confirmed" because some users are still affected, on recent Ubuntu releases. We still don't have enough information for triaging though. Everyone affected, please provide the full log when replicating the problem, not just the GPG error: $ DEJA_DUP_DEBUG=1 deja-dup --backup > deja-dup.log You may want to scrub the log of any incriminating file names or details. Also, if the log is really too large, limit it to e.g. the last 1000 lines or whatever number of lines is enough to include enough information about the issue: $ DEJA_DUP_DEBUG=1 deja-dup --backup | tail -n 1000 > deja-dup.log Also of interest may be your settings (please scrub the file of any incriminating file names or details): $ gsettings list-recursively org.gnome.DejaDup > deja-dup.gsettings And I've also found in the past that the content of Déjà-Dup's cache directory could provide valuable insight over the available backup chains: $ ls -lR .cache/deja-dup/ > deja-dup.cachedir Thanks. ** Also affects: deja-dup Importance: Undecided Status: New ** Changed in: deja-dup Status: New => Confirmed ** Also affects: duplicity 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/989750 Title: repeatedly asks for encryption password when backing up, even though "remember password" is ticked Status in Déjà Dup: Confirmed Status in Duplicity: New Status in deja-dup package in Ubuntu: Confirmed Bug description: I've set deja-dup to back up automatically, and to encrypt files. But it never gets far: every few seconds, it brings up a "password needed" window somewhere out of sight (behind other windows; but that is another problem/feature), even though I've told it to remember the password. So using this backup software seems entirely impractical; it will never finish. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: deja-dup 20.1-0ubuntu0.2 ProcVersionSignature: Ubuntu 3.0.0-17.30-generic 3.0.22 Uname: Linux 3.0.0-17-generic x86_64 ApportVersion: 1.23-0ubuntu4 Architecture: amd64 Date: Fri Apr 27 09:50:47 2012 InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110921.2) ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, user) LANG=en_CA.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/deja-dup/+bug/989750/+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 989750] Re: repeatedly asks for encryption password when backing up, even though "remember password" is ticked
** Changed in: deja-dup (Ubuntu) Status: Expired => Confirmed ** Tags removed: amd64 oneiric running-unity ** Tags added: xenial -- 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/989750 Title: repeatedly asks for encryption password when backing up, even though "remember password" is ticked Status in deja-dup package in Ubuntu: Confirmed Bug description: I've set deja-dup to back up automatically, and to encrypt files. But it never gets far: every few seconds, it brings up a "password needed" window somewhere out of sight (behind other windows; but that is another problem/feature), even though I've told it to remember the password. So using this backup software seems entirely impractical; it will never finish. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: deja-dup 20.1-0ubuntu0.2 ProcVersionSignature: Ubuntu 3.0.0-17.30-generic 3.0.22 Uname: Linux 3.0.0-17-generic x86_64 ApportVersion: 1.23-0ubuntu4 Architecture: amd64 Date: Fri Apr 27 09:50:47 2012 InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110921.2) ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, user) LANG=en_CA.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/989750/+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 1685294] Re: Deja-dup won't run backup in Xubuntu 17.04
** Changed in: deja-dup (Ubuntu) Status: New => Incomplete -- 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/1685294 Title: Deja-dup won't run backup in Xubuntu 17.04 Status in deja-dup package in Ubuntu: Incomplete Bug description: Deja-dup backup won't run in Xubuntu 17.04; It works OK in Ubuntu MATE and Kubuntu (both 17.04 version), though. I attach you the error message it spawns when trying to make a backup. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: deja-dup 34.4-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Apr 21 17:50:14 2017 InstallationDate: Installed on 2017-04-19 (1 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) 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/1685294/+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 1681679] Re: package deja-dup 34.2-0ubuntu3.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
I'm converting this bug report to a question, as it doesn't appear to be a bug in Déjà-Dup (upstream or package), but a support request after an installation failure. Please comment and/or convert the question back to a bug if more help is needed and/or more information can be provided and/or it turns out to be a bug. ** Changed in: deja-dup (Ubuntu) Status: New => Invalid ** Converted to question: https://answers.launchpad.net/ubuntu/+source/deja-dup/+question/629854 -- 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/1681679 Title: package deja-dup 34.2-0ubuntu3.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in deja-dup package in Ubuntu: Invalid Bug description: system gets hang whenever multiple apps are running simultaneously, i have to remove the battery to make it again work.. ProblemType: Package DistroRelease: Ubuntu 16.10 Package: deja-dup 34.2-0ubuntu3.1 ProcVersionSignature: Ubuntu 4.8.0-46.49-generic 4.8.17 Uname: Linux 4.8.0-46-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 AptOrdering: file-roller:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Tue Apr 11 12:18:26 2017 DpkgTerminalLog: Preparing to unpack .../file-roller_3.22.1-0ubuntu1_amd64.deb ... Unpacking file-roller (3.22.1-0ubuntu1) over (3.22.0-1ubuntu1) ... dpkg: error processing package deja-dup (--configure): package is in a very bad inconsistent state; you should reinstall it before attempting configuration DuplicateSignature: package:deja-dup:34.2-0ubuntu3.1 Unpacking file-roller (3.22.1-0ubuntu1) over (3.22.0-1ubuntu1) ... dpkg: error processing package deja-dup (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2017-04-10 (1 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3.4 SourcePackage: deja-dup Title: package deja-dup 34.2-0ubuntu3.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1681679/+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 238606] Re: [MASTER] Flash player doesn't work properly on Firefox 3 64bits (crash, gray square)
I am setting this old bug to expire, seeing how it concerns ancient releases of Ubuntu with antediluvian versions of Flash and Firefox. To install and keep the Flash plugin up-to-date, one can nowadays use the flashplugin-installer package in the multiverse repository (NPAPI version) or the adobe-flashplugin package in Canonical's partner repository (NPAPI and PPAPI versions, recommended). https://help.ubuntu.com/stable/ubuntu-help/net-install-flash.html -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to flashplugin-nonfree in Ubuntu. https://bugs.launchpad.net/bugs/238606 Title: [MASTER] Flash player doesn't work properly on Firefox 3 64bits (crash,gray square) Status in adobe-flashplugin package in Ubuntu: Incomplete Status in firefox-3.0 package in Ubuntu: Invalid Status in flashplugin-nonfree package in Ubuntu: Incomplete Bug description: Binary package hint: firefox-3.0 Adobe's Flash plugin doesn't work every time. Some times it work properly, and some times it show just a gray square where it should show the embed flash object. On konqueror it works ok, so this is an issue of Firefox, not of flash. Some info of my system: janus@ernestina:~$ lsb_release -rd Description:Ubuntu 8.04 Release:8.04 janus@ernestina:~$ apt-cache policy flashplugin-nonfree flashplugin-nonfree: Instalados: 9.0.124.0ubuntu2 Candidato: 9.0.124.0ubuntu2 Tabla de versión: *** 9.0.124.0ubuntu2 0 500 http://ftp.usf.edu hardy/multiverse Packages 100 /var/lib/dpkg/status janus@ernestina:~$ apt-cache policy firefox firefox: Instalados: 3.0~rc2+nobinonly-0ubuntu1~fta1~hardy Candidato: 3.0~rc2+nobinonly-0ubuntu1~fta1~hardy Tabla de versión: *** 3.0~rc2+nobinonly-0ubuntu1~fta1~hardy 0 500 http://ppa.launchpad.net hardy/main Packages 100 /var/lib/dpkg/status 3.0~b5+nobinonly-0ubuntu3 0 500 http://ftp.usf.edu hardy/main Packages (I'm using FF3RC2, but it also didn't work properly on FF3RC1 nor FF3b5) ProblemType: Bug Architecture: amd64 Date: Mon Jun 9 13:11:53 2008 DistroRelease: Ubuntu 8.04 NonfreeKernelModules: nvidia Package: firefox-3.0 3.0~rc2+nobinonly-0ubuntu1~fta1~hardy [modified: usr/lib/firefox-3.0/ffox-3-beta-profile-migration-dialog usr/lib/firefox-3.0/firefox] PackageArchitecture: amd64 ProcEnviron: LANGUAGE=es_AR:es PATH=/home/username/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=es_AR.UTF-8 SHELL=/bin/bash SourcePackage: firefox-3.0 Uname: Linux 2.6.24-18-generic x86_64 UnreportableReason: Este no es un genuino paquete Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adobe-flashplugin/+bug/238606/+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 238606] Re: [MASTER] Flash player doesn't work properly on Firefox 3 64bits (crash, gray square)
** Changed in: adobe-flashplugin (Ubuntu) Status: Confirmed => Incomplete ** Changed in: flashplugin-nonfree (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to flashplugin-nonfree in Ubuntu. https://bugs.launchpad.net/bugs/238606 Title: [MASTER] Flash player doesn't work properly on Firefox 3 64bits (crash,gray square) Status in adobe-flashplugin package in Ubuntu: Incomplete Status in firefox-3.0 package in Ubuntu: Invalid Status in flashplugin-nonfree package in Ubuntu: Incomplete Bug description: Binary package hint: firefox-3.0 Adobe's Flash plugin doesn't work every time. Some times it work properly, and some times it show just a gray square where it should show the embed flash object. On konqueror it works ok, so this is an issue of Firefox, not of flash. Some info of my system: janus@ernestina:~$ lsb_release -rd Description:Ubuntu 8.04 Release:8.04 janus@ernestina:~$ apt-cache policy flashplugin-nonfree flashplugin-nonfree: Instalados: 9.0.124.0ubuntu2 Candidato: 9.0.124.0ubuntu2 Tabla de versión: *** 9.0.124.0ubuntu2 0 500 http://ftp.usf.edu hardy/multiverse Packages 100 /var/lib/dpkg/status janus@ernestina:~$ apt-cache policy firefox firefox: Instalados: 3.0~rc2+nobinonly-0ubuntu1~fta1~hardy Candidato: 3.0~rc2+nobinonly-0ubuntu1~fta1~hardy Tabla de versión: *** 3.0~rc2+nobinonly-0ubuntu1~fta1~hardy 0 500 http://ppa.launchpad.net hardy/main Packages 100 /var/lib/dpkg/status 3.0~b5+nobinonly-0ubuntu3 0 500 http://ftp.usf.edu hardy/main Packages (I'm using FF3RC2, but it also didn't work properly on FF3RC1 nor FF3b5) ProblemType: Bug Architecture: amd64 Date: Mon Jun 9 13:11:53 2008 DistroRelease: Ubuntu 8.04 NonfreeKernelModules: nvidia Package: firefox-3.0 3.0~rc2+nobinonly-0ubuntu1~fta1~hardy [modified: usr/lib/firefox-3.0/ffox-3-beta-profile-migration-dialog usr/lib/firefox-3.0/firefox] PackageArchitecture: amd64 ProcEnviron: LANGUAGE=es_AR:es PATH=/home/username/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=es_AR.UTF-8 SHELL=/bin/bash SourcePackage: firefox-3.0 Uname: Linux 2.6.24-18-generic x86_64 UnreportableReason: Este no es un genuino paquete Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adobe-flashplugin/+bug/238606/+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 727064] Re: [Natty] Strange beeping sound when viewing flash video
** Changed in: adobe-flashplugin (Ubuntu) Status: Confirmed => Fix Released ** Changed in: flashplugin-nonfree (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to flashplugin-nonfree in Ubuntu. https://bugs.launchpad.net/bugs/727064 Title: [Natty] Strange beeping sound when viewing flash video Status in GLibC: Fix Released Status in adobe-flashplugin package in Ubuntu: Fix Released Status in eglibc package in Ubuntu: Fix Released Status in flashplugin-nonfree package in Ubuntu: Fix Released Status in glibc package in Fedora: Unknown Bug description: Binary package hint: adobe-flashplugin As describe in the thread http://ubuntuforums.org/showthread.php?t=1692707 the sound is bad in natty. Workaround: patch the flash plugin to change memcpy call to memmove - Download https://bugzilla.redhat.com/attachment.cgi?id=460254 - Run this script: $ sudo bash ./fix-flash.sh /usr/lib/flashplugin-installer/libflashplayer.so - Restart the browser To manage notifications about this bug go to: https://bugs.launchpad.net/glibc/+bug/727064/+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 1685294] Re: Deja-dup won't run backup in Xubuntu 17.04
Hi Victor, you're just missing a Python module ("no module named
gi.repository"). This has been encountered before, e.g. bug 1641423. No
reason why it is sometimes missing has been found yet.
The module is provided by the python-gi package, which should have been
installed as a dependency of the deja-dup-backend-gvfs package, which
you have normally installed when you first opened Déjà-Dup's GUI (System
Settings > Backups, a.k.a. deja-dup-preferences) and clicked the Install
button at the bottom of the message informing you that additional
packages were required.
You did click that button, did you? Or was it not available?
Can you also please report which packages are installed and which ones
aren't, by running the following commands:
apt-cache policy deja-dup-backend-gvfs
apt-cache policy deja-dup-backend-cloudfiles
apt-cache policy deja-dup-backend-s3
apt-cache policy duplicity
apt-cache policy python-gi
Look for the "Installed: (none)" and "Installed: "
lines. Thanks.
--
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/1685294
Title:
Deja-dup won't run backup in Xubuntu 17.04
Status in deja-dup package in Ubuntu:
New
Bug description:
Deja-dup backup won't run in Xubuntu 17.04; It works OK in Ubuntu MATE
and Kubuntu (both 17.04 version), though.
I attach you the error message it spawns when trying to make a backup.
ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: deja-dup 34.4-0ubuntu1
ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
Uname: Linux 4.10.0-19-generic x86_64
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
CurrentDesktop: XFCE
Date: Fri Apr 21 17:50:14 2017
InstallationDate: Installed on 2017-04-19 (1 days ago)
InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
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/1685294/+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 1641423] Re: Backup fails with message: 'Failed to execute child process "duplicity" (No such file or directory)' or 'No module named gi.repository': missing deja-dup-backend-g
** Summary changed: - Back up failed with message: Failed to execute child process "duplicity" (No such file or directory) + Backup fails with message: 'Failed to execute child process "duplicity" (No such file or directory)' or 'No module named gi.repository': missing deja-dup-backend-gvfs, duplicity, and/or python-gi packages -- 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/1641423 Title: Backup fails with message: 'Failed to execute child process "duplicity" (No such file or directory)' or 'No module named gi.repository': missing deja-dup-backend-gvfs, duplicity, and/or python-gi packages Status in Déjà Dup: Triaged Status in deja-dup package in Ubuntu: Confirmed Bug description: Ubantu 16.04 Cant find out version of backup but it was loaded with distro 16.04 and all software is up to date so it should be latest I dont know how to get the information in 3 & 4 from the error maessage: Failed to execute child process "duplicity" (No such file or directory) It looks like a required file is missing I tried removing backup and reinstalling but it still fails with the same error To manage notifications about this bug go to: https://bugs.launchpad.net/deja-dup/+bug/1641423/+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 1681679] Re: package deja-dup 34.2-0ubuntu3.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
@mohan: Have you tried doing what APT suggests: reinstalling deja-dup, which is apparently "in a very bad inconsistent state" (possibly because something failed during your system update on 2017-04-11 11:02:02, although I don't know what did)? For instance, from the command line: sudo apt-get install --reinstall deja-dup You may also want to check next if there are broken dependencies: sudo apt-get check And fix any broken dependencies with: sudo apt-get install --fix-broken Before upgrading your system again: sudo apt-get update sudo apt-get dist-upgrade Also, instead of removing the battery to shutdown your laptop when it freezes, you can try switching to a virtual text console with Ctrl+Alt+F1 (or F2, F3, ..., F6). Explore the process list with commands such as "ps", "ps aux | more", "top" and kill whichever process you can identify as a cause for the freeze with "kill ", "kill -9 ", "killall ". Then go back to the graphical interface with Ctrl+Alt+F7 to check if it's unfrozen. If that fails, you can try restarting the graphical session with "sudo service lightdm restart" in a virtual text console. And if you can't even get to a virtual text console, you can try powering off your laptop by long pressing the power button instead of removing the battery. That works on many laptops. -- 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/1681679 Title: package deja-dup 34.2-0ubuntu3.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in deja-dup package in Ubuntu: New Bug description: system gets hang whenever multiple apps are running simultaneously, i have to remove the battery to make it again work.. ProblemType: Package DistroRelease: Ubuntu 16.10 Package: deja-dup 34.2-0ubuntu3.1 ProcVersionSignature: Ubuntu 4.8.0-46.49-generic 4.8.17 Uname: Linux 4.8.0-46-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 AptOrdering: file-roller:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Tue Apr 11 12:18:26 2017 DpkgTerminalLog: Preparing to unpack .../file-roller_3.22.1-0ubuntu1_amd64.deb ... Unpacking file-roller (3.22.1-0ubuntu1) over (3.22.0-1ubuntu1) ... dpkg: error processing package deja-dup (--configure): package is in a very bad inconsistent state; you should reinstall it before attempting configuration DuplicateSignature: package:deja-dup:34.2-0ubuntu3.1 Unpacking file-roller (3.22.1-0ubuntu1) over (3.22.0-1ubuntu1) ... dpkg: error processing package deja-dup (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2017-04-10 (1 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3.4 SourcePackage: deja-dup Title: package deja-dup 34.2-0ubuntu3.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1681679/+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 1600783] Re: Not translated string
Thanks for your feedback and the video. Never mind the untranslated string, this behavior is not normal at all. When I plug my external hard disk, backup starts and completes successfully. I'm thinking we could add unique error IDs in the code to find out which particular error is triggered in your case. That would give us a lead to fix the translation and also hopefully the issue itself. -- 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/1600783 Title: Not translated string Status in Déjà Dup: Confirmed Status in Ubuntu Translations: Confirmed Status in deja-dup package in Ubuntu: Confirmed Bug description: See https://dl.dropboxusercontent.com/u/26959244/Capture%20du%202016-07-08%2011-59-38.png To manage notifications about this bug go to: https://bugs.launchpad.net/deja-dup/+bug/1600783/+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 1572106] Re: deja-dup needs expressions for ignored-folders
*** This bug is a duplicate of bug 374274 *** https://bugs.launchpad.net/bugs/374274 This is a much-required feature, so I'm adding duplicate status as needed. Ideas and designs have been shared but nobody has started implementing them: the code base is rather large and takes time getting acquainted to, the main developer is busy working on other projects, and it's not clear if he would accept such a feature as it can be considered too advanced for Déjà-Dup's intended users. I would like to work on that feature at some point in the future, but that's not going to be soon. ** This bug has been marked a duplicate of bug 374274 Advanced include/exclude support -- 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/1572106 Title: deja-dup needs expressions for ignored-folders Status in Déjà Dup: Triaged Status in deja-dup package in Ubuntu: Triaged Bug description: At least I would really appreciate (and I bet all developers out there as well), if deja-dup would allow to have glob-expressions or regular expressions for ignored-folders. On a normal installation it is really a pain in the a** to sort out all those .cache .obj tmp/* build/* especially, since those will be generated dynamically during the day. There's absolutely no need to back those up, but the frontend now only allows for specific pathes to be entered on ignore list. Please add this feature. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: deja-dup 34.0-1ubuntu3 ProcVersionSignature: Ubuntu 4.2.0-35.40-generic 4.2.8-ckt5 Uname: Linux 4.2.0-35-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Apr 19 14:08:35 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-03-31 (19 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 (20151021) JournalErrors: No journal files were found. -- No entries -- ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= 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/deja-dup/+bug/1572106/+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 1437514] Re: Feature Request Déjà Dup Exit Prompt
It's no big deal to exit Déjà-Dup while it runs. As far as I can tell, whatever backup volumes were already made are kept on the backup location, and the backup will resume later, or can be resumed manually. Or at least that's what my previous experience of Déjà-Dup has been. I don't know if the OP is still around but I see no reason to implement a "Confirm Exit" prompt, unless I'm wrong about backups resuming of course. -- 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/1437514 Title: Feature Request Déjà Dup Exit Prompt Status in Déjà Dup: Triaged Status in deja-dup package in Ubuntu: Triaged Bug description: I have raged at this and this is probably a simple request, but when accidentally exiting said backup program after it was running for TWO HOURS, I wish it had prompted me so I could deny. Please add this feature. To manage notifications about this bug go to: https://bugs.launchpad.net/deja-dup/+bug/1437514/+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 1600783] Re: Not translated string
@Olivier:
It's the disk you use as backup location I suppose? Does the error show
up every time you plug it? Does it prevent automatic backups from
happening or do they occur later? Does the error prevent you from
running manual backups too? Does it also show up during manual backups?
@Vej:
Might be, but a network issue isn't very consistent with Olivier's
report that the error occurs when he plugs in his USB disk.
There are several places in the code where a caught exception is printed
out, grep warning("%s for a list. This one, in deja-
dup/monitor/monitor.vala, is one of my top suspects (but I may be
wrong):
static async void kickoff()
{
[...]
// Don't run right now if an instance is already running
if (pid == (Pid)0 && !op_active) {
try {
debug("Running automatic backup.");
[...]
[calls to GLib.Process and GLib.ChildWatch functions]
[...]
}
catch (Error e) {
warning("%s\n", e.message);
}
}
else
debug("Not rerunning deja-dup, already doing so.");
}
--
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/1600783
Title:
Not translated string
Status in Déjà Dup:
Confirmed
Status in Ubuntu Translations:
Confirmed
Status in deja-dup package in Ubuntu:
Confirmed
Bug description:
See
https://dl.dropboxusercontent.com/u/26959244/Capture%20du%202016-07-08%2011-59-38.png
To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1600783/+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 1600783] Re: Not translated string
I can't find this message in Déjà-Dup's or duplicity's source code and .po files at the revisions corresponding to their versions in 16.10. No idea where it comes from. Olivier, if you can identify and tell us how to trigger this error, this might give us a chance to find out where the message comes from. -- 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/1600783 Title: Not translated string Status in Déjà Dup: Confirmed Status in Ubuntu Translations: Confirmed Status in deja-dup package in Ubuntu: Confirmed Bug description: See https://dl.dropboxusercontent.com/u/26959244/Capture%20du%202016-07-08%2011-59-38.png To manage notifications about this bug go to: https://bugs.launchpad.net/deja-dup/+bug/1600783/+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 1657092] Re: deja-dup refers to "Files" instead of "Caja"
I'm still not convinced that this is worth a SRU, or qualifies for one. The provision about "bugs which [...] (1) have an obviously safe patch and (2) affect an application" in the SRU guidelines applies only to bugs which have "high potential for improving the user experience", and I'm just not sure this particular bug has high potential for that (just potential). Nevertheless, the debdiff looks good to me, if I understand it correctly. Shouldn't you subscribe ubuntu-sponsors? Or they won't notice it. (Again, IIUC.) -- 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/1657092 Title: deja-dup refers to "Files" instead of "Caja" Status in Déjà Dup: Fix Committed Status in deja-dup package in Ubuntu: In Progress Status in deja-dup source package in Xenial: Confirmed Status in deja-dup source package in Yakkety: Confirmed Status in deja-dup source package in Zesty: In Progress Bug description: The Backups application's Overview screen says "You can restore the entire backup with the Restore... button or use Files" It should say "or use Caja", since the file manager in Mate has been renamed Caja. Screenshot attached. [Impact] * Users of Mate which use Déjà Dup get confused by the wrong terminology regarding their file manager. * The upstream fix detects Mate desktops using XDG_CURRENT_DESKTOP and fills a new variable with "Caja" or "Files". That variable is included in the string afterwards. [Test Case] * Open Déjà Dup inside Ubuntu Mate (launch "deja-dup-preferences" from a terminal) * Install the necessary software by clicking the "Install..."-button. * Create a backup: - Choose a location on the "Storage Location" tab (or use the default local folder) - On the "Overview" tab perform a backup using the button "Backup now" * On the "Overview" tab: Look at the description above the restore button. * It refers to Files instead of Caja [Regression Potential] * None that I am aware of. The worst case should be limited to a broken (or untranslated) string in Déjà Dup itself. To manage notifications about this bug go to: https://bugs.launchpad.net/deja-dup/+bug/1657092/+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 1576394] Re: deja-dup package dependencies in 16.04
Yes, the suggested packages should not be made dependencies or recommended packages (for Python 2 reasons). However the OP and comments raise the issue that as of now, on-demand installation of duplicity (or deja-dup-backend-gvfs) is only triggered when one opens the deja-dup-preferences GUI and clicks the button that says to install additional software. Other use cases, e.g. setting up Déjà Dup by using gsettings on the command line or by restoring a previous dconf database, are not covered and result in unfriendly error messages. That should be fixed (with a friendly error message). I think this bug report should be marked a duplicate of bug 1641423. -- 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/1576394 Title: deja-dup package dependencies in 16.04 Status in deja-dup package in Ubuntu: Confirmed Bug description: After a fresh install of Ubuntu 16.04 amd64 desktop, deja-dup did not work with some existing backup settings. I discovered duplicity was not installed... After manually installing "duplicity", deja-dup still did not work (reporting error "BackendException") and I discovered I needed to manually install "python-gi" as well. Once these were installed, deja-dup began to work as expected. Listing the dependencies of deja-dup (34.2-0ubuntu1) in Ubuntu 16.04 gives the following: $ apt-cache depends deja-dup deja-dup Depends: libatk1.0-0 Depends: libc6 Depends: libdbusmenu-glib4 Depends: libgdk-pixbuf2.0-0 Depends: libglib2.0-0 Depends: libgtk-3-0 Depends: libnautilus-extension1a Depends: libnotify4 Depends: libpackagekit-glib2-16 Depends: libpango-1.0-0 Depends: libpeas-1.0-0 Depends: libsecret-1-0 Depends: libunity-control-center1 Depends: libunity9 |Depends: dconf-gsettings-backend Depends: dconf-gsettings-backend Depends: adwaita-icon-theme Recommends: policykit-1 policykit-1:i386 Suggests: deja-dup-backend-cloudfiles Suggests: deja-dup-backend-gvfs Suggests: deja-dup-backend-s3 Suggests: duplicity As one of the popular backends to deja-dup, it might be helpful to classify duplicity not as "suggests" but a "depends" package (even though its nice to see other backends are also supported). In addition, the deja-dup package should include the "python-gi" package as a "depends" as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1576394/+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 1450429] Re: Backups configuration duplicated folders
Not reproducible every time in my case. Sometimes the folders are listed twice, sometimes once. In both the include and exclude lists. This bug and bug 1599662 are probably duplicates indeed. Also: I cannot reproduce the bug at all on Trusty (deja-dup 30.0-0ubuntu4.1, duplicity 0.6.23-1ubuntu4.1), only when building from source (current revision 1575), and the OP reports that against Vivid (deja-dup 32.0-0ubuntu5), so perhaps check the changes introduced between these versions first. Or I could just have been lucky. -- 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/1450429 Title: Backups configuration duplicated folders Status in deja-dup package in Ubuntu: Confirmed Bug description: Ubuntu 15.04 unity-control-center 15.04.0+15.04.20150410-0ubuntu1 Just a small UI bug. I'm using the Backups UI from Settings/System to backup files to a network share. I've removed the ~/Downloads folder from the 'Folders to ignore' section. When I open the Backups UI now for the first time, the folders in 'Folders to save' and 'Folders to ignore' are correct. But when I go back to All Settings and then open Backups again, each folder in these sections will be shown twice. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity-control-center 15.04.0+15.04.20150410-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Thu Apr 30 13:03:05 2015 ExecutablePath: /usr/bin/unity-control-center InstallationDate: Installed on 2015-02-11 (77 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) ProcEnviron: LANGUAGE=en_US PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: unity-control-center UpgradeStatus: Upgraded to vivid on 2015-04-30 (0 days ago) usr_lib_unity-control-center: deja-dup 32.0-0ubuntu5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1450429/+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 1657092] Re: deja-dup refers to "Files" instead of "Caja"
@Michael: Sweet, thanks for merging! @Vej, C de-Avillez: It's nice to nominate this bug for Xenial and Yakkety, but I'm not sure it's really worth fixing in these series, or that it fits the SRU requirements (I would personally go with Won't Fix for the published releases). -- 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/1657092 Title: deja-dup refers to "Files" instead of "Caja" Status in Déjà Dup: Fix Committed Status in deja-dup package in Ubuntu: Triaged Status in deja-dup source package in Xenial: New Status in deja-dup source package in Yakkety: New Status in deja-dup source package in Zesty: Triaged Bug description: The Backups application's Overview screen says "You can restore the entire backup with the Restore... button or use Files" It should say "or use Caja", since the file manager in Mate has been renamed Caja. Screenshot attached. [Impact] * Users of Mate which use Déjà Dup get confused by the wrong terminology regarding their file manager. * The upstream fix detects Mate desktops using XDG_CURRENT_DESKTOP and fills a new variable with "Caja" or "Files". That variable is included in the string afterwards. [Test Case] * Open Déjà Dup inside Ubuntu Mate (launch "deja-dup-preferences" from a terminal) * Look at the description above the restore button. * It refers to Files instead of Caja [Regression Potential] * None that I am aware of. The worst case should be limited to a broken (or untranslated) string in Déjà Dup itself. To manage notifications about this bug go to: https://bugs.launchpad.net/deja-dup/+bug/1657092/+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 1657092] Re: deja-dup refers to "Files" instead of "Caja"
I wish I was knowledgeable enough to fix less trivial bugs. In the
meantime, here are two branches. Michael, which one would you like I
request a merge of?
https://code.launchpad.net/~nathanael-naeri/deja-dup/fix-1657092-a
Changes the word "Files" to "the file manager". The more accurate "a
compatible file manager" or "a supported file manager" can be considered
too.
https://code.launchpad.net/~nathanael-naeri/deja-dup/fix-1657092-b
Uses "Files" or "Caja" depending on the environment variable
XDG_CURRENT_DESKTOP ("Caja" if it's MATE, "Files" if it's something else
or unset). To test in the test shell, make a first backup, and open
deja-dup-preferences as follow:
$ XDG_CURRENT_DESKTOP=Unity deja-dup-preferences
$ XDG_CURRENT_DESKTOP=MATE deja-dup-preferences
PS [Michael]: I don't know if Launchpad notified you, but you'll want to
read my follow-up comments on my last merge request :
https://code.launchpad.net/~nathanael-naeri/deja-
dup/fix-1549776/+merge/317042
--
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/1657092
Title:
deja-dup refers to "Files" instead of "Caja"
Status in Déjà Dup:
In Progress
Status in deja-dup package in Ubuntu:
In Progress
Bug description:
The Backups application's Overview screen says "You can restore the
entire backup with the Restore... button or use Files"
It should say "or use Caja", since the file manager in Mate has been
renamed Caja.
Screenshot attached.
To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1657092/+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 1657092] Re: deja-dup refers to "Files" instead of "Caja"
Russ, can you please post the values of the following environment variables in MATE, I'm going to try and implement something and I'm not sure which one to use (probably the last one). You can use printenv var or echo $var to find them out. Thanks. SESSION GDMSESSION DESKTOP_SESSION XDG_CURRENT_DESKTOP -- 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/1657092 Title: deja-dup refers to "Files" instead of "Caja" Status in Déjà Dup: In Progress Status in deja-dup package in Ubuntu: In Progress Bug description: The Backups application's Overview screen says "You can restore the entire backup with the Restore... button or use Files" It should say "or use Caja", since the file manager in Mate has been renamed Caja. Screenshot attached. To manage notifications about this bug go to: https://bugs.launchpad.net/deja-dup/+bug/1657092/+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 1442111] Re: Scanner is correctly identified but scan fails with "sane_start: Invalid argument" as root, and rebooting the computer sometimes makes things work, sometimes not
Yes I am marking this Invalid because the issue hasn't manifested itself
since mid-2015. See comment 3 for more details. Fingers crossed that it
doesn't come back.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to sane-backends in Ubuntu.
https://bugs.launchpad.net/bugs/1442111
Title:
Scanner is correctly identified but scan fails with "sane_start:
Invalid argument" as root, and rebooting the computer sometimes makes
things work, sometimes not
Status in sane-backends package in Ubuntu:
Invalid
Bug description:
OS/Kernel: Ubuntu 12.04.5 LTS (GNU/Linux 3.2.0-80-generic x86_64)
Scanner: Epson Stylus Office BX305FW, USB 2.0, id 0x04b8/0x0863
SANE: libsane_1.0.22-7ubuntu1, libsane-common_1.0.22-7ubuntu1,
sane-utils_1.0.22-7ubuntu1 (up-to-date 12.04 LTS)
Epson IScan: iscan_2.30.1-1, iscan-data_1.36.0-1 (latest versions, 2015-03-23)
The scanner is correctly identified, when logged in as root:
# sane-find-scanner
found USB scanner (vendor=0x04b8, product=0x0863) at libusb:001:004
# lsusb
Bus 001 Device 004: ID 04b8:0863 Seiko Epson Corp.
# scanimage -L
device `epkowa:usb:001:004' is a Epson Stylus Office
BX305F/BX305FW/TX320F/ME OFFICE 620F/WorkForce 320 Series flatbed scanner
But scan fails with "scanimage: sane_start: Invalid argument"
(scanimage frontend) or "Échec de la numérisation: Impossible de
démarrer la numérisation" (simple-scan frontend):
# scanimage -d epkowa:usb:001:004 -v -T
scanimage: sane_start: Invalid argument
The permissions of the device seem nominal:
# ls -l /dev/bus/usb/001/004
crw-rw-r--+ 1 root lp 189, 1 avril 9 12:32 /dev/bus/usb/001/004
And the following line is present in /lib/udev/rules.d/40-iscan.rules:
ATTRS{idVendor}=="04b8", ATTRS{idProduct}=="0863",
ENV{libsane_matched}="yes"
When this problems appears, it stays so for the whole session, but
rebooting the computer sometimes makes the problem go away, sometimes
not. The only thing I can see that a reboot changes is the USB device
ID, all the rest stays the same in the previous commands output.
For instance right now the USB device ID was 001:004 and scan wasn't
working, I rebooted and it's 001:002 and scan is working. I don't know
if it is relevant, I don't understand what is causing the problem, and
I don't know how to investigate further.
SANE support for this scanner with external backend epkowa is normally
complete, and everything runs smoothly on the reboots when the problem
does not appear. Any help is appreciated. Should I report the bug
upstream, or against a different package, perhaps a USB-related or
boot-related one?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1442111/+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 1657092] Re: deja-dup refers to "Files" instead of "Caja"
@Vej (and @Russ too): I have uploaded my (trivial) patch to an upstream branch, but haven't proposed it for merging yet. To be honest, I'm not too wild about changing the name "Files" to accommodate Caja (sorry), because of the reasons I wrote down in the branch's description: https://code.launchpad.net/~nathanael-naeri/deja-dup/fix-1657092 Vej, could you please consult with Michael, directly or on the mailing- list, to get his opinion on supporting another desktop environment and/or Nautilus fork (MATE/Caja), and potentially, supporting all DE that use Nautilus forks? Right now Déjà-Dup only officially integrates with GNOME/Nautilus and Unity/Nautilus as far as I know. If he's OK with Russ's suggestion then I'll be happy to propose for merging of course. ** Changed in: deja-dup Assignee: (unassigned) => Nathanaël Naeri (Naël) (nathanael-naeri) ** Changed in: deja-dup (Ubuntu) Assignee: (unassigned) => Nathanaël Naeri (Naël) (nathanael-naeri) ** Changed in: deja-dup Status: Triaged => In Progress ** Changed in: deja-dup (Ubuntu) Status: Confirmed => In Progress -- 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/1657092 Title: deja-dup refers to "Files" instead of "Caja" Status in Déjà Dup: In Progress Status in deja-dup package in Ubuntu: In Progress Bug description: The Backups application's Overview screen says "You can restore the entire backup with the Restore... button or use Files" It should say "or use Caja", since the file manager in Mate has been renamed Caja. Screenshot attached. To manage notifications about this bug go to: https://bugs.launchpad.net/deja-dup/+bug/1657092/+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 1657092] Re: deja-dup refers to "Files" instead of "Caja"
@Russ Phillips: Don't bother, I checked by myself in the .desktop file. -- 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/1657092 Title: deja-dup refers to "Files" instead of "Caja" Status in Déjà Dup: Triaged Status in deja-dup package in Ubuntu: Confirmed Bug description: The Backups application's Overview screen says "You can restore the entire backup with the Restore... button or use Files" It should say "or use Caja", since the file manager in Mate has been renamed Caja. Screenshot attached. To manage notifications about this bug go to: https://bugs.launchpad.net/deja-dup/+bug/1657092/+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 1657092] Re: deja-dup refers to "Files" instead of "Caja"
@Russ Phillips (or anyone using MATE): Can you confirm that "Caja" is the user-facing name of the file manager in MATE desktop environment? And by that I mean, its name in the menus. Thanks. Cause in Unity DE and Cinnamon DE, I'm quite certain that the user- facing name of Nautilus and Nemo, respectively, is "Files", even though many people refer to them by their internal names Nautilus and Nemo. -- 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/1657092 Title: deja-dup refers to "Files" instead of "Caja" Status in Déjà Dup: Triaged Status in deja-dup package in Ubuntu: Confirmed Bug description: The Backups application's Overview screen says "You can restore the entire backup with the Restore... button or use Files" It should say "or use Caja", since the file manager in Mate has been renamed Caja. Screenshot attached. To manage notifications about this bug go to: https://bugs.launchpad.net/deja-dup/+bug/1657092/+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 1013386] Re: unity 2d dash doesn't open office files
*** This bug is a duplicate of bug 1002710 *** https://bugs.launchpad.net/bugs/1002710 ** Changed in: unity-2d (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-2d in Ubuntu. Matching subscriptions: dp-unity2d https://bugs.launchpad.net/bugs/1013386 Title: unity 2d dash doesn't open office files Status in unity-2d package in Ubuntu: Fix Released Bug description: When i click within the dash - either on the home lens, or on the files lens on a LibreOffice type of file (.doc file, in this case) - the file doesn't open. Opening the file from within Nautilus works fine. Within Unity-3d this does NOT occur. Everything works flawlessly in this matter. cheers ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: unity 5.12-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.2.0-25.40-generic 3.2.18 Uname: Linux 3.2.0-25-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.0.1-0ubuntu8 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] Date: Thu Jun 14 23:25:34 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-2d/+bug/1013386/+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 992717] Re: Opening files from the Dash randomly doesn't work
*** This bug is a duplicate of bug 1002710 *** https://bugs.launchpad.net/bugs/1002710 ** Changed in: unity-2d (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-2d in Ubuntu. Matching subscriptions: dp-unity2d https://bugs.launchpad.net/bugs/992717 Title: Opening files from the Dash randomly doesn't work Status in unity-2d package in Ubuntu: Fix Released Bug description: My problem is really simple: if I click on a file in the dash (either an exact search result or a recent file), sometimes nothing happens. But in some cases, it works. I can't say that it has a problem with file types - for example, I can open a .jpeg file that's on my desktop, but neither can I open a .JPG that's in my pictures folder, nor one that's on an external HDD, nor one that's _also_ on the desktop. This problem doesn't come up when using 3D unity. If needed, I can try a live cd/fresh install, but my network connection is really slow so I would only do that if that's the only solution. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: unity-2d 5.12.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-24.37-generic-pae 3.2.14 Uname: Linux 3.2.0-24-generic-pae i686 ApportVersion: 2.0.1-0ubuntu7 Architecture: i386 Date: Tue May 1 18:34:14 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha i386 (20120112) PackageArchitecture: all SourcePackage: unity-2d UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-2d/+bug/992717/+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 1442111] Re: Scanner is correctly identified but scan fails with "sane_start: Invalid argument" as root, and rebooting the computer sometimes makes things work, sometimes not
** Changed in: sane-backends (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to sane-backends in Ubuntu.
https://bugs.launchpad.net/bugs/1442111
Title:
Scanner is correctly identified but scan fails with "sane_start:
Invalid argument" as root, and rebooting the computer sometimes makes
things work, sometimes not
Status in sane-backends package in Ubuntu:
Invalid
Bug description:
OS/Kernel: Ubuntu 12.04.5 LTS (GNU/Linux 3.2.0-80-generic x86_64)
Scanner: Epson Stylus Office BX305FW, USB 2.0, id 0x04b8/0x0863
SANE: libsane_1.0.22-7ubuntu1, libsane-common_1.0.22-7ubuntu1,
sane-utils_1.0.22-7ubuntu1 (up-to-date 12.04 LTS)
Epson IScan: iscan_2.30.1-1, iscan-data_1.36.0-1 (latest versions, 2015-03-23)
The scanner is correctly identified, when logged in as root:
# sane-find-scanner
found USB scanner (vendor=0x04b8, product=0x0863) at libusb:001:004
# lsusb
Bus 001 Device 004: ID 04b8:0863 Seiko Epson Corp.
# scanimage -L
device `epkowa:usb:001:004' is a Epson Stylus Office
BX305F/BX305FW/TX320F/ME OFFICE 620F/WorkForce 320 Series flatbed scanner
But scan fails with "scanimage: sane_start: Invalid argument"
(scanimage frontend) or "Échec de la numérisation: Impossible de
démarrer la numérisation" (simple-scan frontend):
# scanimage -d epkowa:usb:001:004 -v -T
scanimage: sane_start: Invalid argument
The permissions of the device seem nominal:
# ls -l /dev/bus/usb/001/004
crw-rw-r--+ 1 root lp 189, 1 avril 9 12:32 /dev/bus/usb/001/004
And the following line is present in /lib/udev/rules.d/40-iscan.rules:
ATTRS{idVendor}=="04b8", ATTRS{idProduct}=="0863",
ENV{libsane_matched}="yes"
When this problems appears, it stays so for the whole session, but
rebooting the computer sometimes makes the problem go away, sometimes
not. The only thing I can see that a reboot changes is the USB device
ID, all the rest stays the same in the previous commands output.
For instance right now the USB device ID was 001:004 and scan wasn't
working, I rebooted and it's 001:002 and scan is working. I don't know
if it is relevant, I don't understand what is causing the problem, and
I don't know how to investigate further.
SANE support for this scanner with external backend epkowa is normally
complete, and everything runs smoothly on the reboots when the problem
does not appear. Any help is appreciated. Should I report the bug
upstream, or against a different package, perhaps a USB-related or
boot-related one?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1442111/+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 1652410] Re: Undescriptive duplicity/collection-status error when the backup directory contains two volumes with different file names and same volume number in the same backup
Added this bug to duplicity, since it is probably better suited for
resolution there than in Déjà-Dup.
Also updated the description.
** Tags removed: amd64 xenial
** Tags added: testcase
** Description changed:
- Deja-dup has never worked for me (last 5 years) always errors.
- No after a new system reinstall 16.04 I was determined to get it up and
running and learn about it's use,and perhaps recover some old data.
- Still fails with see attached text
+ [System]
- ProblemType: Bug
- DistroRelease: Ubuntu 16.04
- Package: deja-dup 34.2-0ubuntu1.1
- ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
- Uname: Linux 4.4.0-57-generic x86_64
- ApportVersion: 2.20.1-0ubuntu2.4
- Architecture: amd64
- CurrentDesktop: Unity
- Date: Fri Dec 23 16:56:43 2016
- ExecutablePath: /usr/bin/deja-dup
- InstallationDate: Installed on 2016-12-02 (21 days ago)
- InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64
(20160719)
- ProcEnviron:
- PATH=(custom, user)
- SHELL=/usr/bin/fish
- LANG=en_CA.UTF-8
- LANGUAGE=en_CA:en
- XDG_RUNTIME_DIR=
- SourcePackage: deja-dup
- UpgradeStatus: No upgrade log present (probably fresh install)
+ Ubuntu 16.04
+ deja-dup 34.2-0ubuntu1.1
+ duplicity 0.7.06-2ubuntu2
+
+ [Symptoms]
+
+ When the backup location unfortunately contains two backup volumes with
+ different file names and same volume number in the same backup set, for
+ instance:
+
+ duplicity-full.20161129T015237Z.vol1.difftar
+ duplicity-full.20161129T015237Z.vol1.difftar.gz
+
+ this confuses duplicity collection-status, which ends up returning an
+ undescriptive Python assertion error, as seen in this Déjà-Dup log file:
+
+ DUPLICITY: INFO 1
+ DUPLICITY: . Args: /usr/bin/duplicity collection-status [...]
+
+ [...]
+
+ DUPLICITY: DEBUG 1
+ DUPLICITY: . 12 files exist on backend
+
+ DUPLICITY: DEBUG 1
+ DUPLICITY: . Extracting backup chains from list of files:
+[u'duplicity-full.20161129T015237Z.vol1.difftar',
+ u'duplicity-full.20161129T015237Z.manifest',
+ u'duplicity-full.20161129T015237Z.vol1.difftar.gz',
+ u'duplicity-full-signatures.20161129T015237Z.sigtar.gz',
+ u'duplicity-full-signatures.20161129T015237Z.sigtar',
+ [...]
+
+ DUPLICITY: DEBUG 1
+ DUPLICITY: . File duplicity-full.20161129T015237Z.vol1.difftar is not
+ part of a known set; creating new set
+
+ DUPLICITY: DEBUG 1
+ DUPLICITY: . File duplicity-full.20161129T015237Z.manifest is part of
+ known set
+
+ DUPLICITY: ERROR 30 AssertionError
+ [...]
+ DUPLICITY: . File "/usr/lib/python2.7/dist-packages/duplicity/collections.
+ py", line 105, in add_filename(self.volume_name_dict, filename)
+ DUPLICITY: . AssertionError:
+ ({1: 'duplicity-full.20161129T015237Z.vol1.difftar'},
+ 'duplicity-full.20161129T015237Z.vol1.difftar.gz')
+
+ What happens is that duplicity collection-status takes the uncompressed
+ duplicity-full.20161129T015237Z.vol1.difftar for the start of a backup
+ set, then tries to add the compressed duplicity-
+ full.20161129T015237Z.vol1.difftar.gz to this set, and fails because the
+ volume number of this file has already been added to the set. Otherwise
+ there would be two backup volumes with the same volume number in the
+ backup set.
+
+ Note that a similar issue may also happen for file signatures instead of
+ backup volumes, e.g.:
+
+ duplicity-full-signatures.20161129T015237Z.sigtar
+ duplicity-full-signatures.20161129T015237Z.sigtar.gz
+
+ but backup volumes appear to be tripped on first, perhaps because of
+ alphabetic order.
+
+ Note also that under normal operation, the backup location isn't
+ supposed to contain a mixed of compressed and uncompressed files (or
+ encrypted and unencrypted files), but this situation was still reported
+ by the bug reporter in the original bug report.
+
+ [Test case]
+
+ See comment 19, written for Déjà-Dup, but easily adaptable to pure
+ duplicity I think.
+
+ [Ideas for fixing]
+
+ Duplicity already has checks to avoid considering files whose names
+ don't look like they could be part of a backup set (see comment 19,
+ point 4). Perhaps this filename filter could be improved on so that
+ duplicity doesn't burp so hard when a backup volume is present in both
+ compressed and uncompressed forms? Perhaps it could have duplicity
+ prefer a particular filename when there are two volumes with the same
+ number in the same backup set? But then which one and on what grounds?
+
+ Please also see comment 23.
+
+ [Easier fix]
+
+ Worst case, if this situation can't be handled automatically and the
+ situation requires a human to examine the contents of the backup
+ repository to take adequate action, then it would be helpful that
+ duplicity return a more descriptive message than the current terse
+ assertion error.
--
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/1652410
[Desktop-packages] [Bug 1652410] Re: Undescriptive duplicity/collection-status error when the backup directory contains two volumes with different file names and same volume number in the same backup
** Also affects: duplicity Importance: Undecided Status: New ** Also affects: duplicity (Ubuntu) Importance: Undecided Status: New ** Changed in: duplicity Status: New => Confirmed ** Changed in: duplicity (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/1652410 Title: Undescriptive duplicity/collection-status error when the backup directory contains two volumes with different file names and same volume number in the same backup set Status in Déjà Dup: Confirmed Status in Duplicity: Confirmed Status in deja-dup package in Ubuntu: Confirmed Status in duplicity package in Ubuntu: Confirmed Bug description: Deja-dup has never worked for me (last 5 years) always errors. No after a new system reinstall 16.04 I was determined to get it up and running and learn about it's use,and perhaps recover some old data. Still fails with see attached text ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: deja-dup 34.2-0ubuntu1.1 ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35 Uname: Linux 4.4.0-57-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 CurrentDesktop: Unity Date: Fri Dec 23 16:56:43 2016 ExecutablePath: /usr/bin/deja-dup InstallationDate: Installed on 2016-12-02 (21 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: PATH=(custom, user) SHELL=/usr/bin/fish LANG=en_CA.UTF-8 LANGUAGE=en_CA:en XDG_RUNTIME_DIR= 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/1652410/+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 1442111] Re: Scanner is correctly identified but scan fails with "sane_start: Invalid argument" as root, and rebooting the computer sometimes makes things work, sometimes not
Hi Christopher, thank you for resurrecting this bug report.
The affected machine has since been upgraded to Xenial. It still uses
the same scanner. The current versions of sane-backends and iscan are
barely more recent, so one could suppose the behavior I reported in
2015-05 could still occur. However, it hasn't manifested itself since
mid-2015, or I would have moved this bug report upstream to get help.
Perhaps I've just been lucky. After all, this scanner isn't used very
frequently and this bug doesn't show up every time. Still, my opinion is
to close this bug as Invalid (can't reproduce). I'll re-open it in the
future if necessary.
Do you still want the apport information?
OS/Kernel: Ubuntu 16.04.2 LTS (GNU/Linux 4.4.0-62-generic x86_64)
Scanner: Epson Stylus Office BX305FW, USB 2.0, id 0x04b8/0x0863
SANE: libsane, libsane-common, sane-utils version 1.0.25+git20150528-1ubuntu2
(up-to-date 16.04 LTS)
Epson IScan: iscan_2.30.3-1, iscan-data_1.39.0-1 (latest versions, 2016-12-01)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to sane-backends in Ubuntu.
https://bugs.launchpad.net/bugs/1442111
Title:
Scanner is correctly identified but scan fails with "sane_start:
Invalid argument" as root, and rebooting the computer sometimes makes
things work, sometimes not
Status in sane-backends package in Ubuntu:
Incomplete
Bug description:
OS/Kernel: Ubuntu 12.04.5 LTS (GNU/Linux 3.2.0-80-generic x86_64)
Scanner: Epson Stylus Office BX305FW, USB 2.0, id 0x04b8/0x0863
SANE: libsane_1.0.22-7ubuntu1, libsane-common_1.0.22-7ubuntu1,
sane-utils_1.0.22-7ubuntu1 (up-to-date 12.04 LTS)
Epson IScan: iscan_2.30.1-1, iscan-data_1.36.0-1 (latest versions, 2015-03-23)
The scanner is correctly identified, when logged in as root:
# sane-find-scanner
found USB scanner (vendor=0x04b8, product=0x0863) at libusb:001:004
# lsusb
Bus 001 Device 004: ID 04b8:0863 Seiko Epson Corp.
# scanimage -L
device `epkowa:usb:001:004' is a Epson Stylus Office
BX305F/BX305FW/TX320F/ME OFFICE 620F/WorkForce 320 Series flatbed scanner
But scan fails with "scanimage: sane_start: Invalid argument"
(scanimage frontend) or "Échec de la numérisation: Impossible de
démarrer la numérisation" (simple-scan frontend):
# scanimage -d epkowa:usb:001:004 -v -T
scanimage: sane_start: Invalid argument
The permissions of the device seem nominal:
# ls -l /dev/bus/usb/001/004
crw-rw-r--+ 1 root lp 189, 1 avril 9 12:32 /dev/bus/usb/001/004
And the following line is present in /lib/udev/rules.d/40-iscan.rules:
ATTRS{idVendor}=="04b8", ATTRS{idProduct}=="0863",
ENV{libsane_matched}="yes"
When this problems appears, it stays so for the whole session, but
rebooting the computer sometimes makes the problem go away, sometimes
not. The only thing I can see that a reboot changes is the USB device
ID, all the rest stays the same in the previous commands output.
For instance right now the USB device ID was 001:004 and scan wasn't
working, I rebooted and it's 001:002 and scan is working. I don't know
if it is relevant, I don't understand what is causing the problem, and
I don't know how to investigate further.
SANE support for this scanner with external backend epkowa is normally
complete, and everything runs smoothly on the reboots when the problem
does not appear. Any help is appreciated. Should I report the bug
upstream, or against a different package, perhaps a USB-related or
boot-related one?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1442111/+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
