[Desktop-packages] [Bug 997913] Re: thunderbird fails to connect to mail server
Thanks for getting back.
The issue could not be resolved in Ubuntu due to an error in the name
resolution (which the author of the service claims to be correct).
Having a DNS server point to two domains under Ubuntu resolves the first
one (which can be any of the two). This was the issue.
A work-around would be to set the smtp server to an IP-Adress (which
makes this solution a little inflexible).
However, due to the overwhelming amount of issues in Ubuntu I decided to
move to Mac. I have not regretted this move as the basics work fine.
You may close this issue.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to thunderbird in Ubuntu.
https://bugs.launchpad.net/bugs/997913
Title:
thunderbird fails to connect to mail server
Status in thunderbird package in Ubuntu:
Incomplete
Bug description:
Thunderbird 12.0.1 fails to connect to server.
Network addresses get resolved correctly but Thunderbird still insists
it cannot connect.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: thunderbird 12.0.1+build1-0ubuntu0.12.04.1
ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14
Uname: Linux 3.2.0-24-generic x86_64
NonfreeKernelModules: nvidia
AddonCompatCheckDisabled: False
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu7
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: michi 2521 F pulseaudio
BuildID: 20120430060637
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xe8044000 irq 48'
Mixer name : 'Analog Devices AD1981'
Components : 'HDA:11d41981,103c30c5,00100200
HDA:14f12c06,103c1379,0010'
Controls : 16
Simple ctrls : 11
Channel: release
Date: Fri May 11 08:22:27 2012
ForcedLayersAccel: False
IfupdownConfig:
auto lo
iface lo inet loopback
IncompatibleExtensions:
Timezone Definitions for Mozilla Calendar -
ID=calendar-timezo...@mozilla.org, Version=1.2011n, minVersion=2.0,
maxVersion=12.0, Location=app-system-share, Type=extension, Active=Yes
Messaging Menu and Unity Launcher integration -
ID=messagingm...@mozilla.com, Version=0.9.3, minVersion=3.3a1pre,
maxVersion=12.0a1, Location=app-global, Type=extension, Active=Yes
EDS Contact Integration - ID=edsintegrat...@mozilla.com, Version=0.3.9,
minVersion=7.0, maxVersion=11.0a1, Location=app-global, Type=extension,
Active=Yes
Provider for Google Calendar - ID={a62ef8ec-5fdc-40c2-873c-223b8a6925cc},
Version=0.13, minVersion=8.0a1, maxVersion=12.0, Location=app-profile,
Type=extension, Active=Yes
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64+mac
(20111012)
IpRoute:
default via 10.1.0.254 dev wlan0 proto static
10.0.0.0/8 dev wlan0 proto kernel scope link src 10.1.0.191 metric 2
169.254.0.0/16 dev wlan0 scope link metric 1000
Profiles: Profile0 (Default) - LastVersion=12.0.1/20120430060637 (Running)
RunningIncompatibleAddons: True
SourcePackage: thunderbird
UpgradeStatus: Upgraded to precise on 2012-04-30 (10 days ago)
dmi.bios.date: 07/25/2007
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68MVD Ver. F.05
dmi.board.name: 30C5
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 71.32
dmi.chassis.asset.tag: CNU7402CLM
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias:
dmi:bvnHewlett-Packard:bvr68MVDVer.F.05:bd07/25/2007:svnHewlett-Packard:pnHPCompaq8510w:pvrF.05:rvnHewlett-Packard:rn30C5:rvrKBCVersion71.32:cvnHewlett-Packard:ct10:cvr:
dmi.product.name: HP Compaq 8510w
dmi.product.version: F.05
dmi.sys.vendor: Hewlett-Packard
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/997913/+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 1826420] Re: Nautilus disk properties shows black circle
Hi to all, I used a MacOS icon theme. The issue did occur with Yaru but not with Ambience. I switched to macOS after the ongoing issues that reoccured with 19.04. I could not bear with it any longer (12 years are a long time). Sorry to be of no assistance to this and any other issues any longer. cheers -- 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/1826420 Title: Nautilus disk properties shows black circle Status in nautilus package in Ubuntu: Incomplete Bug description: Ubuntu 19.04 / Nautilus 3.32.0 stable (?) Mounting a disk (which does not show on the desktop may I add here as well) and asking for disk properties gives a black circle. Expected behaviour: different colours for used and unused parts, maybe gray for the unusable meta data. Current behaviour: a black disk telling me nothing. (I have no idea as to why a perfectly working file manager had to get crippled further, but someone managed). I do have a custom theme but it happens with the default theme as well. (Sorry my tone gets harsher every time but I really get tired being an alpha tester). ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: nautilus 1:3.32.0-0ubuntu2 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 25 16:48:33 2019 InstallationDate: Installed on 2018-04-30 (360 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: nautilus UpgradeStatus: Upgraded to disco on 2019-04-19 (5 days ago) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1826420/+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 1801382] Re: printing complex documents does not reproduce screen image on paper
Hi to all, I switched to macOS after the ongoing issues that reoccured with 19.04 (including this one). I could not bear with it any longer (12 years are a long time). Sorry to be of no assistance to this and any other issues any longer. cheers -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1801382 Title: printing complex documents does not reproduce screen image on paper Status in evince package in Ubuntu: Incomplete Status in gtk+3.0 package in Ubuntu: Incomplete Bug description: Ubuntu 18.10 latest update (by 2.11.2018) printing PDF documents that contain embedded images, these images get printed nearly black and completely illegible. I have attached a sample file and a printout of my cups pdf writer (which produces the exact same results as the printer) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: cups 2.2.8-5ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CupsErrorLog: W [02/Nov/2018:16:18:30 +0100] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'HP_Color_LaserJet_MFP_M477fdw_AF82F1_-Gray..\' already exists W [02/Nov/2018:16:18:30 +0100] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'HP_Color_LaserJet_MFP_M477fdw_AF82F1_-DeviceN..\' already exists W [02/Nov/2018:16:20:30 +0100] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'HP_Color_LaserJet_MFP_M477fdw_AF82F1_-Gray..\' already exists W [02/Nov/2018:16:20:30 +0100] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'HP_Color_LaserJet_MFP_M477fdw_AF82F1_-DeviceN..\' already exists CurrentDesktop: ubuntu:GNOME Date: Fri Nov 2 16:21:51 2018 InstallationDate: Installed on 2018-04-30 (186 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lpstat: device for HP_Color_LaserJet_MFP_M477fdw: hp:/net/HP_Color_LaserJet_MFP_M477fdw?ip=10.1.0.21 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 05ac:0273 Apple, Inc. Bus 001 Device 002: ID 05ac:8290 Apple, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Apple Inc. MacBookPro12,1 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP_Color_LaserJet_MFP_M477fdw.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP_Color_LaserJet_MFP_M477fdw.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: cups UpgradeStatus: Upgraded to cosmic on 2018-10-20 (13 days ago) dmi.bios.date: 08/08/2017 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP121.88Z.0171.B00.1708080033 dmi.board.name: Mac-E43C1C25D4880AD6 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro12,1 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-E43C1C25D4880AD6 dmi.modalias: dmi:bvnAppleInc.:bvrMBP121.88Z.0171.B00.1708080033:bd08/08/2017:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro12,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1801382/+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 1826420] [NEW] Nautilus disk properties shows black circle
Public bug reported: Ubuntu 19.04 / Nautilus 3.32.0 stable (?) Mounting a disk (which does not show on the desktop may I add here as well) and asking for disk properties gives a black circle. Expected behaviour: different colours for used and unused parts, maybe gray for the unusable meta data. Current behaviour: a black disk telling me nothing. (I have no idea as to why a perfectly working file manager had to get crippled further, but someone managed). I do have a custom theme but it happens with the default theme as well. (Sorry my tone gets harsher every time but I really get tired being an alpha tester). ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: nautilus 1:3.32.0-0ubuntu2 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 25 16:48:33 2019 InstallationDate: Installed on 2018-04-30 (360 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: nautilus UpgradeStatus: Upgraded to disco on 2019-04-19 (5 days ago) usr_lib_nautilus: ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco ** Attachment added: "So much information" https://bugs.launchpad.net/bugs/1826420/+attachment/5259049/+files/Screenshot%20from%202019-04-25%2016-48-58.png -- 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/1826420 Title: Nautilus disk properties shows black circle Status in nautilus package in Ubuntu: New Bug description: Ubuntu 19.04 / Nautilus 3.32.0 stable (?) Mounting a disk (which does not show on the desktop may I add here as well) and asking for disk properties gives a black circle. Expected behaviour: different colours for used and unused parts, maybe gray for the unusable meta data. Current behaviour: a black disk telling me nothing. (I have no idea as to why a perfectly working file manager had to get crippled further, but someone managed). I do have a custom theme but it happens with the default theme as well. (Sorry my tone gets harsher every time but I really get tired being an alpha tester). ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: nautilus 1:3.32.0-0ubuntu2 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 25 16:48:33 2019 InstallationDate: Installed on 2018-04-30 (360 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: nautilus UpgradeStatus: Upgraded to disco on 2019-04-19 (5 days ago) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1826420/+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 1825625] Re: Some apps appear blurry with framebuffer scaling
Re #7: 90% of the applications experience this and that should be normal? Huhh. Re #8: Fix released? So it could be fixed? What was the issue? How do we get the fix? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1825625 Title: Some apps appear blurry with framebuffer scaling Status in firefox package in Ubuntu: New Status in libreoffice package in Ubuntu: New Status in mutter package in Ubuntu: Invalid Status in thunderbird package in Ubuntu: New Bug description: Setting the framebuffer scaling (with gsettings set org.gnome.mutter experimental-features "['scale-monitor-framebuffer']") allows the display on HiDPi to be scaled to something different than 100%/200%/300%. Which would be fine. However, the display is rendered such that most applications provide blurred display of text and graphics. This is not always the case (e.g. system settings are displayed correctly, Thunderbird and Firefox are blurred). Also the screen flickers when selection menus or resizing the windows. A black border appears around the windows where the shadow should appear. It gets removed a few seconds later but still is irritating. This issue is not urgent, just annoying. It can be worked around by removing the settings in gsetting / dconf. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: mutter 3.32.0+git20190410-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 20 11:11:55 2019 InstallationDate: Installed on 2018-04-30 (355 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: mutter UpgradeStatus: Upgraded to disco on 2019-04-19 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1825625/+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 1825893] Re: Mounted disks not shown on desktop after enabling ubuntu-dock in Tweaks
I think triaging to gnome-shell-extensions might be the wrong approach in this case. The icons did appear before and do appear in other installations. It is just on this machine that after enabling ubuntu-dock they do not appear any more (I do not want to verify this behaviour on any other machines as the missing icon leads to dirty unmounts) There must be a setting somewhere to enable disks again. There used to be a setting in gnome-tweak-tools (but was left out in gnome-tweaks). Also there was a setting in gsettings / dconf which is gone as well. So the question is: Where does UBUNTU (and not Gnome) store its setting about how to deal with mounted devices? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1825893 Title: Mounted disks not shown on desktop after enabling ubuntu-dock in Tweaks Status in gnome-shell-extension-desktop-icons: New Status in gnome-shell-extension-desktop-icons package in Ubuntu: Triaged Bug description: After enabling ubuntu-dock in Tweaks, disks get mounted, are shown in Nautilus side bar but the desktop icon is missing. This leads to the risk of disconnecting a disk that is mounted or write operations are in progress. How can I enable the feature again that disks that get mounted are shown on the desktop? ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell-extension-ubuntu-dock 64ubuntu7 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 22 23:25:53 2019 InstallationDate: Installed on 2018-04-30 (357 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: Upgraded to disco on 2019-04-19 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1825893/+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 1825625] Re: mutter framebuffer scaling blurs display
** Attachment added: "Black frame around windows" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1825625/+attachment/5258146/+files/Screenshot%20from%202019-04-23%2009-34-08.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1825625 Title: mutter framebuffer scaling blurs display Status in mutter package in Ubuntu: Incomplete Bug description: Setting the framebuffer scaling (with gsettings set org.gnome.mutter experimental-features "['scale-monitor-framebuffer']") allows the display on HiDPi to be scaled to something different than 100%/200%/300%. Which would be fine. However, the display is rendered such that most applications provide blurred display of text and graphics. This is not always the case (e.g. system settings are displayed correctly, Thunderbird and Firefox are blurred). Also the screen flickers when selection menus or resizing the windows. A black border appears around the windows where the shadow should appear. It gets removed a few seconds later but still is irritating. This issue is not urgent, just annoying. It can be worked around by removing the settings in gsetting / dconf. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: mutter 3.32.0+git20190410-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 20 11:11:55 2019 InstallationDate: Installed on 2018-04-30 (355 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: mutter UpgradeStatus: Upgraded to disco on 2019-04-19 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1825625/+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 1825625] Re: mutter framebuffer scaling blurs display
** Attachment added: "With framebuffer scaling" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1825625/+attachment/5258145/+files/Screenshot%20from%202019-04-23%2009-32-15.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1825625 Title: mutter framebuffer scaling blurs display Status in mutter package in Ubuntu: Incomplete Bug description: Setting the framebuffer scaling (with gsettings set org.gnome.mutter experimental-features "['scale-monitor-framebuffer']") allows the display on HiDPi to be scaled to something different than 100%/200%/300%. Which would be fine. However, the display is rendered such that most applications provide blurred display of text and graphics. This is not always the case (e.g. system settings are displayed correctly, Thunderbird and Firefox are blurred). Also the screen flickers when selection menus or resizing the windows. A black border appears around the windows where the shadow should appear. It gets removed a few seconds later but still is irritating. This issue is not urgent, just annoying. It can be worked around by removing the settings in gsetting / dconf. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: mutter 3.32.0+git20190410-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 20 11:11:55 2019 InstallationDate: Installed on 2018-04-30 (355 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: mutter UpgradeStatus: Upgraded to disco on 2019-04-19 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1825625/+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 1825625] Re: mutter framebuffer scaling blurs display
With framebuffer scaling some applications (e.g. the settings app) do work fine. Others don't (e.g. Firefox, but also LibreOffice) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1825625 Title: mutter framebuffer scaling blurs display Status in mutter package in Ubuntu: Incomplete Bug description: Setting the framebuffer scaling (with gsettings set org.gnome.mutter experimental-features "['scale-monitor-framebuffer']") allows the display on HiDPi to be scaled to something different than 100%/200%/300%. Which would be fine. However, the display is rendered such that most applications provide blurred display of text and graphics. This is not always the case (e.g. system settings are displayed correctly, Thunderbird and Firefox are blurred). Also the screen flickers when selection menus or resizing the windows. A black border appears around the windows where the shadow should appear. It gets removed a few seconds later but still is irritating. This issue is not urgent, just annoying. It can be worked around by removing the settings in gsetting / dconf. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: mutter 3.32.0+git20190410-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 20 11:11:55 2019 InstallationDate: Installed on 2018-04-30 (355 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: mutter UpgradeStatus: Upgraded to disco on 2019-04-19 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1825625/+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 1825625] Re: mutter framebuffer scaling blurs display
** Attachment added: "Without framebuffer scaling" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1825625/+attachment/5258144/+files/Screenshot%20from%202019-04-23%2009-33-17.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1825625 Title: mutter framebuffer scaling blurs display Status in mutter package in Ubuntu: Incomplete Bug description: Setting the framebuffer scaling (with gsettings set org.gnome.mutter experimental-features "['scale-monitor-framebuffer']") allows the display on HiDPi to be scaled to something different than 100%/200%/300%. Which would be fine. However, the display is rendered such that most applications provide blurred display of text and graphics. This is not always the case (e.g. system settings are displayed correctly, Thunderbird and Firefox are blurred). Also the screen flickers when selection menus or resizing the windows. A black border appears around the windows where the shadow should appear. It gets removed a few seconds later but still is irritating. This issue is not urgent, just annoying. It can be worked around by removing the settings in gsetting / dconf. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: mutter 3.32.0+git20190410-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 20 11:11:55 2019 InstallationDate: Installed on 2018-04-30 (355 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: mutter UpgradeStatus: Upgraded to disco on 2019-04-19 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1825625/+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 1825893] [NEW] Mounted disks not shown on desktop after enabling ubuntu-dock in Tweaks
Public bug reported: After enabling ubuntu-dock in Tweaks, disks get mounted, are shown in Nautilus side bar but the desktop icon is missing. This leads to the risk of disconnecting a disk that is mounted or write operations are in progress. How can I enable the feature again that disks that get mounted are shown on the desktop? ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell-extension-ubuntu-dock 64ubuntu7 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 22 23:25:53 2019 InstallationDate: Installed on 2018-04-30 (357 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: Upgraded to disco on 2019-04-19 (3 days ago) ** Affects: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1825893 Title: Mounted disks not shown on desktop after enabling ubuntu-dock in Tweaks Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: After enabling ubuntu-dock in Tweaks, disks get mounted, are shown in Nautilus side bar but the desktop icon is missing. This leads to the risk of disconnecting a disk that is mounted or write operations are in progress. How can I enable the feature again that disks that get mounted are shown on the desktop? ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell-extension-ubuntu-dock 64ubuntu7 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 22 23:25:53 2019 InstallationDate: Installed on 2018-04-30 (357 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: Upgraded to disco on 2019-04-19 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1825893/+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 1825625] [NEW] mutter framebuffer scaling blurs display
Public bug reported: Setting the framebuffer scaling (with gsettings set org.gnome.mutter experimental-features "['scale-monitor-framebuffer']") allows the display on HiDPi to be scaled to something different than 100%/200%/300%. Which would be fine. However, the display is rendered such that most applications provide blurred display of text and graphics. This is not always the case (e.g. system settings are displayed correctly, Thunderbird and Firefox are blurred). Also the screen flickers when selection menus or resizing the windows. A black border appears around the windows where the shadow should appear. It gets removed a few seconds later but still is irritating. This issue is not urgent, just annoying. It can be worked around by removing the settings in gsetting / dconf. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: mutter 3.32.0+git20190410-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 20 11:11:55 2019 InstallationDate: Installed on 2018-04-30 (355 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: mutter UpgradeStatus: Upgraded to disco on 2019-04-19 (0 days ago) ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1825625 Title: mutter framebuffer scaling blurs display Status in mutter package in Ubuntu: New Bug description: Setting the framebuffer scaling (with gsettings set org.gnome.mutter experimental-features "['scale-monitor-framebuffer']") allows the display on HiDPi to be scaled to something different than 100%/200%/300%. Which would be fine. However, the display is rendered such that most applications provide blurred display of text and graphics. This is not always the case (e.g. system settings are displayed correctly, Thunderbird and Firefox are blurred). Also the screen flickers when selection menus or resizing the windows. A black border appears around the windows where the shadow should appear. It gets removed a few seconds later but still is irritating. This issue is not urgent, just annoying. It can be worked around by removing the settings in gsetting / dconf. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: mutter 3.32.0+git20190410-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 20 11:11:55 2019 InstallationDate: Installed on 2018-04-30 (355 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: mutter UpgradeStatus: Upgraded to disco on 2019-04-19 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1825625/+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 1825623] [NEW] AppIndicatorSupport in Gnome-shell crashes
Public bug reported: After startup or login, An error occurs that just states cancel or report... but does not open a detail dialog Error messages in the syslog: ... Apr 20 10:47:19 mbpr13b gnome-shell[3595]: [AppIndicatorSupport-DEBUG] Registering StatusNotifierItem:1.95/org/ayatana/NotificationItem/software_update_available Apr 20 10:47:19 mbpr13b gnome-shell[3595]: [AppIndicatorSupport-FATAL] unable to update overlay icon Apr 20 10:47:19 mbpr13b gnome-shell[3595]: [AppIndicatorSupport-FATAL] unable to update overlay icon ... It seems that the update notifier cannot register its icon in the top bar. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.32.0+git20190410-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 20 10:49:27 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-04-30 (354 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gnome-shell UpgradeStatus: Upgraded to disco on 2019-04-19 (0 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1825623 Title: AppIndicatorSupport in Gnome-shell crashes Status in gnome-shell package in Ubuntu: New Bug description: After startup or login, An error occurs that just states cancel or report... but does not open a detail dialog Error messages in the syslog: ... Apr 20 10:47:19 mbpr13b gnome-shell[3595]: [AppIndicatorSupport-DEBUG] Registering StatusNotifierItem:1.95/org/ayatana/NotificationItem/software_update_available Apr 20 10:47:19 mbpr13b gnome-shell[3595]: [AppIndicatorSupport-FATAL] unable to update overlay icon Apr 20 10:47:19 mbpr13b gnome-shell[3595]: [AppIndicatorSupport-FATAL] unable to update overlay icon ... It seems that the update notifier cannot register its icon in the top bar. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.32.0+git20190410-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 20 10:49:27 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-04-30 (354 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gnome-shell UpgradeStatus: Upgraded to disco on 2019-04-19 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1825623/+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 1824874] Re: undismissable, unclickable authentication dialog left on screen after policykit authentication [pushModal: invocation of begin_modal failed]
I saw the authentication window only once after resume from suspend to RAM. But I do get the error messages and my syslog is filled up -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1824874 Title: undismissable, unclickable authentication dialog left on screen after policykit authentication [pushModal: invocation of begin_modal failed] Status in gnome-shell package in Ubuntu: Confirmed Bug description: In disco, when policykit prompted me for a password in order for update-manager to dispatch instructions to aptdaemon to perform package updates, the password dialog remained on the screen after I clicked 'authenticate'. The window is not clickable, it appears not to even be a window - mouse presses are received by the window underneath. The exception is that the 'cancel' button is active and receives mouse events - but clicking it does nothing. This may be a gnome-shell issue rather than policykit. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: policykit-1 0.105-25 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 15 13:14:33 2019 InstallationDate: Installed on 2010-09-24 (3125 days ago) InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1) SourcePackage: policykit-1 UpgradeStatus: Upgraded to disco on 2019-04-11 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1824874/+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 1694145] Re: nautilus does not automount USB hard disks on plug-in
Hi Sebastien, I have upgraded to Ubuntu 18.04 and 18.10. Did not experience this issue there. -- 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/1694145 Title: nautilus does not automount USB hard disks on plug-in Status in nautilus package in Ubuntu: Incomplete Bug description: Ubuntu Budgie 17.04 (fresh install) Inserting a USB hard disk does not automount like in Ubuntu Unity. dconf settings are similar. Device is connected and can be mounted in Nautilus manually. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: nautilus 1:3.20.4-0ubuntu2 ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 NonfreeKernelModules: nvidia_uvm wl nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Sun May 28 20:09:16 2017 InstallationDate: Installed on 2017-05-25 (2 days ago) InstallationMedia: Ubuntu-Budgie 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1694145/+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 1769383] Re: Ubuntu dock/launcher is shown on the lock screen
I long have given up on this. However here are two more observations. Confirming Simon P.'s (simpre) observation that applications are not docked. Another issue: when clicking on the activities button once, it does not show the app overview. It requires a second click. This is also true with any activation (like Meta-L to lock the machine). Another anecdote: Yesterday I did some programming. I locked the machine and put it to sleep (another function that used to work reliably and now is completely broken) but when I came back, it was up and running. The IDE was visible. I could position the cursor and enter text. The text was not echoed on the screen but after unlocking the text was there. If this was crucial code anyone could render it unusable or add to it. @Andrea Azzarone: This is a severe security issue to me and many others. I hope the proposed fix (as noted above) is really fixing this issue and comes out soon. It's a shame that something like this passes rollout (although I have some understanding for that) but even more so the initial ignorance and reluctance to trust hundreds of users that there is an issue that needs quick fixing (which I have no understanding for whatsoever). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1769383 Title: Ubuntu dock/launcher is shown on the lock screen Status in gnome-shell package in Ubuntu: Invalid Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Status in gnome-shell source package in Bionic: Invalid Status in gnome-shell-extension-ubuntu-dock source package in Bionic: In Progress Status in gnome-shell source package in Cosmic: Invalid Status in gnome-shell-extension-ubuntu-dock source package in Cosmic: In Progress Status in gnome-shell source package in Disco: Invalid Status in gnome-shell-extension-ubuntu-dock source package in Disco: Fix Released Bug description: [Impact] When entering the lock-screen mode, gnome-shell disables all the extensions. It can happen that under certain conditions ubuntu-dock re-enables itself, causing the ubuntu-dock to appear in the lock-screen, exposing sensitive information. One possible way to reproduce this is to enable dash-to-dock and ubuntu-dock at the same time. [Test Case] 1. Make sure ubuntu-dock is enabled 2. Enable dash-to-dock too 3. Lock the screen 4. Make sure the dock does not appear on the lock screen 5. Make sure there is no warning is the journal [Possible Regressions] Even if it's something we don't really support please make sure that you can use dash-to-dock without uninstalling ubuntu-dock. [Original Bug] After an update from ubuntu 16.04 to 18.04 the dock is aviable on the lockscreen after user login. I did not configure this knowingly. Also i can start every application which is available on the dock. Settings, virtual box, visualstudio code and so on. After the update to 18.04 i just configure the screen frequency to 144Hz and the night mode on. And attach the dock on bottom. I later undid these customizations back to configuration before, but the dock is stil aviable on lockscreen. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-settings-daemon 3.28.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat May 5 18:30:16 2018 InstallationDate: Installed on 2018-04-08 (27 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: gnome-settings-daemon UpgradeStatus: Upgraded to bionic on 2018-05-01 (3 days ago) --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-08 (27 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell-extension-ubuntu-dock 0.9.1 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-05-01 (4 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1769383/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to :
[Desktop-packages] [Bug 1208121] Re: Nautilus saves files under wrong name
My dear, I use 18.10 and the above stated issue is long but resolved. But thanks for getting back to me. Merry Christmas Wolf Rogner -- 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/1208121 Title: Nautilus saves files under wrong name Status in nautilus package in Ubuntu: Incomplete Bug description: Nautilus saves file under wrong name During a rename process, if you copy a file into a directory where a file name is still under renaming, the newly copied file gets the name of the renamed file and the to-be renamed file stays the same How to verify: in a directory with one file test.txt rename test.txt to test2.txt but DO not confirm (by clicking somewhere else or hit Enter) copy file something.txt into this directory (from a separate window or from a browser) you see 2 files in the directory test.txt test2.txt (which is something.txt you copied into the directory) It should be test2.txt (which was test.txt originally) something.txt Not critical if you know it but serious if you want to find the files later ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: nautilus 1:3.6.3-0ubuntu16 ProcVersionSignature: Ubuntu 3.8.0-26.38-generic 3.8.13.2 Uname: Linux 3.8.0-26-generic x86_64 NonfreeKernelModules: wl nvidia ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 Date: Sun Aug 4 10:14:26 2013 GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b"'2428x1466+0+24'" b'org.gnome.nautilus.window-state' b'sidebar-width' b'330' InstallationDate: Installed on 2013-05-17 (78 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64+mac (20130424) MarkForUpload: True SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1208121/+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 1722455] Re: Creation of mail/contact/calendar accounts impossible
@Sebastian: I wish you a very merry Christmas and a happy new year. -- 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/1722455 Title: Creation of mail/contact/calendar accounts impossible Status in gnome-control-center package in Ubuntu: Incomplete Bug description: If one wants to use Gnome Calendar or Gnome Contacts one has to create accounts to access the server. Gnome control centre provides prepared account templates for common public providers. There is an IMAP template that is broken (does not allow to connect to inhouse mail servers). Also adding Calendar or Contact connection is not possible. In Gnome Calendar adding new calendars is impossible (there is a workaround by temporarily installing California but that is very unstable). There needs to be a way to install DAV connectors to CALDav and CARDDav as is possible in Thunderbird. Possible workaround (which is not stable): Under ~/.config/evolution one can add a text file containing the configuration to the required service. As there is no refresh function in Calendar or Contacts, this is a fragile solution though (requires constant session creation aka logout/login) ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-control-center 1:3.26.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4 Uname: Linux 4.13.0-15-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 10 08:11:26 2017 InstallationDate: Installed on 2017-09-05 (34 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1722455/+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 1722455] Re: Creation of mail/contact/calendar accounts impossible
I want to connect to an IMAP and SMTP service. I have to enter the email address (which is something other than the login name). Do I give the login name, I cannot forward, do I give the email address, I can forward but the login into the server fails. "Error connecting to IMAP server Invalid certificate." Ignoring brings me to SMTP "Error connecting to SMTP server Could not connect to : Connection refused" I can use Encryption: None, STARTTLS after connecting or SSL on a dedicated port (where I cannot specify the port) Here I can press Try Again as long as I want. No config file is generated, I can Cancel the process and have no way to access CAL or CARDs There are some providers (mostly cloud services) hard coded but a general connection option is not available (as is in Thunderbird). If this does not work, Gnome Calendar, Addressbook, Geary and related applications are extremly limited in the usefulness. I first filed this with Ubuntu 17.10, then tested with Budgy 17.10, then 18.04 and now with 18.10. -- 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/1722455 Title: Creation of mail/contact/calendar accounts impossible Status in gnome-control-center package in Ubuntu: Incomplete Bug description: If one wants to use Gnome Calendar or Gnome Contacts one has to create accounts to access the server. Gnome control centre provides prepared account templates for common public providers. There is an IMAP template that is broken (does not allow to connect to inhouse mail servers). Also adding Calendar or Contact connection is not possible. In Gnome Calendar adding new calendars is impossible (there is a workaround by temporarily installing California but that is very unstable). There needs to be a way to install DAV connectors to CALDav and CARDDav as is possible in Thunderbird. Possible workaround (which is not stable): Under ~/.config/evolution one can add a text file containing the configuration to the required service. As there is no refresh function in Calendar or Contacts, this is a fragile solution though (requires constant session creation aka logout/login) ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-control-center 1:3.26.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4 Uname: Linux 4.13.0-15-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 10 08:11:26 2017 InstallationDate: Installed on 2017-09-05 (34 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1722455/+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 1769383] Re: Ubuntu dock/launcher is shown on the lock screen
It is not fixed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1769383 Title: Ubuntu dock/launcher is shown on the lock screen Status in gnome-shell package in Ubuntu: Invalid Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Status in gnome-shell source package in Bionic: Invalid Status in gnome-shell-extension-ubuntu-dock source package in Bionic: In Progress Status in gnome-shell source package in Cosmic: Invalid Status in gnome-shell-extension-ubuntu-dock source package in Cosmic: In Progress Status in gnome-shell source package in Disco: Invalid Status in gnome-shell-extension-ubuntu-dock source package in Disco: Fix Released Bug description: [Impact] When entering the lock-screen mode, gnome-shell disables all the extensions. It can happen that under certain conditions ubuntu-dock re-enables itself, causing the ubuntu-dock to appear in the lock-screen, exposing sensitive information. One possible way to reproduce this is to enable dash-to-dock and ubuntu-dock at the same time. [Test Case] 1. Make sure ubuntu-dock is enabled 2. Enable dash-to-dock too 3. Lock the screen 4. Make sure the dock does not appear on the lock screen 5. Make sure there is no warning is the journal [Possible Regressions] Even if it's something we don't really support please make sure that you can use dash-to-dock without uninstalling ubuntu-dock. [Original Bug] After an update from ubuntu 16.04 to 18.04 the dock is aviable on the lockscreen after user login. I did not configure this knowingly. Also i can start every application which is available on the dock. Settings, virtual box, visualstudio code and so on. After the update to 18.04 i just configure the screen frequency to 144Hz and the night mode on. And attach the dock on bottom. I later undid these customizations back to configuration before, but the dock is stil aviable on lockscreen. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-settings-daemon 3.28.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat May 5 18:30:16 2018 InstallationDate: Installed on 2018-04-08 (27 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: gnome-settings-daemon UpgradeStatus: Upgraded to bionic on 2018-05-01 (3 days ago) --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-08 (27 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell-extension-ubuntu-dock 0.9.1 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-05-01 (4 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1769383/+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 1722455] Re: Creation of mail/contact/calendar accounts impossible
There is no error message it just does not work or allow the creation of calendars. Try to install SOGo and connect to a user calendar. You will see that you cannot even enter the parameters. I found a workaround and currently use Thunderbird. A solution would be to install Evolution, create the calendar entries and then delete Evolution again. This works as well (and creates the config file mentioned above). I cannot add any more information to this. Sorry However, have a merry Christmas -- 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/1722455 Title: Creation of mail/contact/calendar accounts impossible Status in gnome-control-center package in Ubuntu: Incomplete Bug description: If one wants to use Gnome Calendar or Gnome Contacts one has to create accounts to access the server. Gnome control centre provides prepared account templates for common public providers. There is an IMAP template that is broken (does not allow to connect to inhouse mail servers). Also adding Calendar or Contact connection is not possible. In Gnome Calendar adding new calendars is impossible (there is a workaround by temporarily installing California but that is very unstable). There needs to be a way to install DAV connectors to CALDav and CARDDav as is possible in Thunderbird. Possible workaround (which is not stable): Under ~/.config/evolution one can add a text file containing the configuration to the required service. As there is no refresh function in Calendar or Contacts, this is a fragile solution though (requires constant session creation aka logout/login) ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-control-center 1:3.26.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4 Uname: Linux 4.13.0-15-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 10 08:11:26 2017 InstallationDate: Installed on 2017-09-05 (34 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1722455/+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 1804296] Re: firefox deletes saved web pages
Sorry for this - ignore it. I did validate this by eliminating each add-on a time. However this seems to be triggered by a combination of two add-ons. And - mea culpa - I did not verify with all extensions off. I set it to Invalid already ** Changed in: firefox (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1804296 Title: firefox deletes saved web pages Status in firefox package in Ubuntu: Invalid Bug description: Firefox 63.0 deletes saved web pages. Reproduce: Open any web page File -> Save page as Save it (I saved into several different locations to verify this was not related to the directory) This will save the html file and a folder containing all embedded elements Close tab or application This will delete (=rm) the html file but will leave the folder and sub-content intact. Expected: Saved files should remain on the disk ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: firefox 63.0+build2-0ubuntu0.18.10.2 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: wolf 26184 F pulseaudio /dev/snd/controlC1: wolf 26184 F pulseaudio BuildID: 20181023213305 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Tue Nov 20 20:37:54 2018 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2018-04-30 (204 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IpRoute: default via 10.1.0.254 dev wlp3s0 proto dhcp metric 600 10.0.0.0/8 dev wlp3s0 proto kernel scope link src 10.1.0.155 metric 600 169.254.0.0/16 dev wlp3s0 scope link metric 1000 Locales: extensions.sqlite corrupt or missing MostRecentCrashID: bp-4827540e-d81d-42af-8cb9-c30b51180711 PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=63.0/20181023213305 RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to cosmic on 2018-10-20 (31 days ago) dmi.bios.date: 08/08/2017 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP121.88Z.0171.B00.1708080033 dmi.board.name: Mac-E43C1C25D4880AD6 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro12,1 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-E43C1C25D4880AD6 dmi.modalias: dmi:bvnAppleInc.:bvrMBP121.88Z.0171.B00.1708080033:bd08/08/2017:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro12,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1804296/+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 1804364] [NEW] Thunderbird fails to print duplex
Public bug reported: Thunderbird does not print duplex even when set to do so. Printer settings, about:config is ignored. Resetting about:configs print.print_duplex restores a string value. When setting it, an integer is set. This is the same behaviour that firefox exposes. Did not happen before the change to the new engine. Behaviour can only be observed on Linux (not on Mac). ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: thunderbird 1:60.2.1+build1-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: wolf 14366 F pulseaudio /dev/snd/controlC1: wolf 14366 F pulseaudio BuildID: 20181011091051 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Wed Nov 21 06:52:45 2018 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2018-04-30 (204 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IpRoute: default via 10.201.255.254 dev wlp3s0 proto dhcp metric 600 10.201.0.0/16 dev wlp3s0 proto kernel scope link src 10.201.41.123 metric 600 169.254.0.0/16 dev wlp3s0 scope link metric 1000 Locales: extensions.sqlite corrupt or missing PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=60.2.1/20181011091051 (In use) RunningIncompatibleAddons: False SourcePackage: thunderbird Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to cosmic on 2018-10-20 (31 days ago) dmi.bios.date: 08/08/2017 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP121.88Z.0171.B00.1708080033 dmi.board.name: Mac-E43C1C25D4880AD6 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro12,1 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-E43C1C25D4880AD6 dmi.modalias: dmi:bvnAppleInc.:bvrMBP121.88Z.0171.B00.1708080033:bd08/08/2017:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro12,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. ** Affects: thunderbird (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1804364 Title: Thunderbird fails to print duplex Status in thunderbird package in Ubuntu: New Bug description: Thunderbird does not print duplex even when set to do so. Printer settings, about:config is ignored. Resetting about:configs print.print_duplex restores a string value. When setting it, an integer is set. This is the same behaviour that firefox exposes. Did not happen before the change to the new engine. Behaviour can only be observed on Linux (not on Mac). ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: thunderbird 1:60.2.1+build1-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: wolf 14366 F pulseaudio /dev/snd/controlC1: wolf 14366 F pulseaudio BuildID: 20181011091051 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Wed Nov 21 06:52:45 2018 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2018-04-30 (204 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IpRoute: default via 10.201.255.254 dev wlp3s0 proto dhcp metric 600 10.201.0.0/16 dev wlp3s0 proto kernel scope link src 10.201.41.123 metric 600 169.254.0.0/16 dev wlp3s0 scope link metric 1000 Locales: extensions.sqlite corrupt or missing PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=60.2.1/20181011091051 (In use) RunningIncompatibleAddons: False SourcePackage: thunderbird Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to cosmic on 2018-10-20 (31 days ago) dmi.bios.date: 08/08/2017 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP121.88Z.0171.B00.1708080033 dmi.board.name: Mac-E43C1C25D4880AD6 dmi.board.vendor: Apple Inc. dmi.board.version:
[Desktop-packages] [Bug 1736680] Re: firefox duplex printing fails
18.10 and still not working -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1736680 Title: firefox duplex printing fails Status in firefox package in Ubuntu: Confirmed Bug description: Duplex printing in Firefox does not work. Printer is set to duplex, printer settings are set to duplex by default. LibreOffice and Chromium print pages duplex by default. Firefox does not even though duplex printing is set in the default settings and in the document printer settings. It simply ignores it. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: firefox 57.0.1+build2-0ubuntu0.17.10.1 ProcVersionSignature: Ubuntu 4.13.0-18.21-generic 4.13.13 Uname: Linux 4.13.0-18-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: wolf 1420 F pulseaudio /dev/snd/controlC0: wolf 1420 F pulseaudio BuildID: 20171129230227 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Wed Dec 6 09:49:10 2017 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2017-10-20 (46 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) IpRoute: default via 10.1.0.254 dev wlp3s0 proto static metric 600 10.0.0.0/8 dev wlp3s0 proto kernel scope link src 10.1.0.155 metric 600 169.254.0.0/16 dev wlp3s0 scope link metric 1000 Locales: extensions.sqlite corrupt or missing PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=57.0.1/20171129230227 (In use) RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2017 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP121.88Z.0171.B00.1708080033 dmi.board.name: Mac-E43C1C25D4880AD6 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro12,1 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-E43C1C25D4880AD6 dmi.modalias: dmi:bvnAppleInc.:bvrMBP121.88Z.0171.B00.1708080033:bd08/08/2017:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro12,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1736680/+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 1804296] [NEW] firefox deletes saved web pages
Public bug reported: Firefox 63.0 deletes saved web pages. Reproduce: Open any web page File -> Save page as Save it (I saved into several different locations to verify this was not related to the directory) This will save the html file and a folder containing all embedded elements Close tab or application This will delete (=rm) the html file but will leave the folder and sub-content intact. Expected: Saved files should remain on the disk ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: firefox 63.0+build2-0ubuntu0.18.10.2 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: wolf 26184 F pulseaudio /dev/snd/controlC1: wolf 26184 F pulseaudio BuildID: 20181023213305 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Tue Nov 20 20:37:54 2018 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2018-04-30 (204 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IpRoute: default via 10.1.0.254 dev wlp3s0 proto dhcp metric 600 10.0.0.0/8 dev wlp3s0 proto kernel scope link src 10.1.0.155 metric 600 169.254.0.0/16 dev wlp3s0 scope link metric 1000 Locales: extensions.sqlite corrupt or missing MostRecentCrashID: bp-4827540e-d81d-42af-8cb9-c30b51180711 PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=63.0/20181023213305 RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to cosmic on 2018-10-20 (31 days ago) dmi.bios.date: 08/08/2017 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP121.88Z.0171.B00.1708080033 dmi.board.name: Mac-E43C1C25D4880AD6 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro12,1 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-E43C1C25D4880AD6 dmi.modalias: dmi:bvnAppleInc.:bvrMBP121.88Z.0171.B00.1708080033:bd08/08/2017:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro12,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1804296 Title: firefox deletes saved web pages Status in firefox package in Ubuntu: New Bug description: Firefox 63.0 deletes saved web pages. Reproduce: Open any web page File -> Save page as Save it (I saved into several different locations to verify this was not related to the directory) This will save the html file and a folder containing all embedded elements Close tab or application This will delete (=rm) the html file but will leave the folder and sub-content intact. Expected: Saved files should remain on the disk ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: firefox 63.0+build2-0ubuntu0.18.10.2 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: wolf 26184 F pulseaudio /dev/snd/controlC1: wolf 26184 F pulseaudio BuildID: 20181023213305 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Tue Nov 20 20:37:54 2018 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2018-04-30 (204 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IpRoute: default via 10.1.0.254 dev wlp3s0 proto dhcp metric 600 10.0.0.0/8 dev wlp3s0 proto kernel scope link src 10.1.0.155 metric 600 169.254.0.0/16 dev wlp3s0 scope link metric 1000 Locales: extensions.sqlite corrupt or missing MostRecentCrashID: bp-4827540e-d81d-42af-8cb9-c30b51180711 PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=63.0/20181023213305 RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to cosmic on 2018-10-20 (31 days ago) dmi.bios.date:
[Desktop-packages] [Bug 1797796] Re: embedding OLE objects in Writer leads to blurred print
played around a little more: Downloaded LibreOffice 6.2.0.0-beta1 AppImage and low and behold, the embedded objects and icons are blurred again. Only the current production version seems to work correctly. I suggest we drop this bug report and I accept the blurred embeddiments. Seems like some regression on LOs side. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1797796 Title: embedding OLE objects in Writer leads to blurred print Status in libreoffice package in Ubuntu: Incomplete Bug description: Steps to create: Open blank Writer document Insert OLE object -> Libreoffice Calc enter some numbers leave OLE object -> The object is rendered blurred. Enter OLE object (double click) -> the content is rendered correctly Print document -> the content of the OLE object is printed in lower quality than rest of document Combined documents with text and calculations cannot be printed in unified quality. -> This type of document is not up to office standards. Only on Ubuntu (on Mac this cannot be observed) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libreoffice-writer 1:6.0.6-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Oct 14 20:29:01 2018 InstallationDate: Installed on 2018-04-30 (167 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1797796/+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 1797796] Re: embedding OLE objects in Writer leads to blurred print
Some console messages: wolf@mbpr13b:~$ sudo snap install libreoffice [sudo] password for wolf: libreoffice 6.1.3.2 from Canonical✓ installed wolf@mbpr13b:~$ snap run libreoffice.writer main.go:192: cannot change mount namespace of snap "libreoffice" according to change mount (/snap/gtk-common-themes/818/share/icons/Suru /snap/libreoffice/90/data-dir/icons/Suru none bind,ro 0 0): cannot use "/snap/gtk-common-themes/818/share/icons/Suru" as bind-mount source: not a directory (soffice:3000): GLib-GIO-WARNING **: 14:55:35.776: Error creating IO channel for /proc/self/mountinfo: Permission denied (g-file-error-quark, 2) wolf@mbpr13b:~$ man snap wolf@mbpr13b:~$ sudo snap remove libreoffice libreoffice removed wolf@mbpr13b:~$ Personally I think that an application should not provide WARNINGS that are ERRORS but should handle this gracefully. Add: I figured out which theme was used. Is it true that snap uses gtk2 only (I have not seen any gtk3 themes in the /snap/gtk-common-themes/... folders. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1797796 Title: embedding OLE objects in Writer leads to blurred print Status in libreoffice package in Ubuntu: Incomplete Bug description: Steps to create: Open blank Writer document Insert OLE object -> Libreoffice Calc enter some numbers leave OLE object -> The object is rendered blurred. Enter OLE object (double click) -> the content is rendered correctly Print document -> the content of the OLE object is printed in lower quality than rest of document Combined documents with text and calculations cannot be printed in unified quality. -> This type of document is not up to office standards. Only on Ubuntu (on Mac this cannot be observed) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libreoffice-writer 1:6.0.6-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Oct 14 20:29:01 2018 InstallationDate: Installed on 2018-04-30 (167 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1797796/+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 1797796] Re: embedding OLE objects in Writer leads to blurred print
@Oliver: I installed the snap version (I do not like snap as it leaves artefacts lying around). a) the same blurred effect as with the apt installation b) path's, settings and other customisation is lost c) theme is ... well which one does get used there? Certainly not mine Concluding: The issue is the same in snap packages. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1797796 Title: embedding OLE objects in Writer leads to blurred print Status in libreoffice package in Ubuntu: Incomplete Bug description: Steps to create: Open blank Writer document Insert OLE object -> Libreoffice Calc enter some numbers leave OLE object -> The object is rendered blurred. Enter OLE object (double click) -> the content is rendered correctly Print document -> the content of the OLE object is printed in lower quality than rest of document Combined documents with text and calculations cannot be printed in unified quality. -> This type of document is not up to office standards. Only on Ubuntu (on Mac this cannot be observed) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libreoffice-writer 1:6.0.6-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Oct 14 20:29:01 2018 InstallationDate: Installed on 2018-04-30 (167 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1797796/+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 1797796] Re: embedding OLE objects in Writer leads to blurred print
Sorry about my unprecise report last time. In 18.04(.1) I observed this issue only when embedding OLE objects. I first attributed this to maybe a slight difference in width or height of the embedded object. I can reign out this as I have adjusted the size. Under 18.10 I not only see this obscured embeddiment happen with OLE objects but with any object that I include. Be it presentations, documents or spread sheets. Further, the icons from the toolbar are blurred as well. This regards the default installation (6.1.2.1) I tried to pin it down to screen resolution (my Mac has 2550 x 1600 with a default of 200% scaling). Even with 100% I can verify the blurred display (although it requires a magnifying glass to see). Today I figured that using cropped images in presentations has negative impact on the display of fonts (font size and font family change randomly). In comparison, I tried AppImage (6.1.3) from LO site. Here I cannot see any of the blurred effects at all. Embedded components and icons are displayed sharp. Personally I come to the conclusion that the default installation packages must be compiled with settings incompatible with the display manager. Concluding: Anything other than bare text gets rendered blurred in some way. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1797796 Title: embedding OLE objects in Writer leads to blurred print Status in libreoffice package in Ubuntu: Incomplete Bug description: Steps to create: Open blank Writer document Insert OLE object -> Libreoffice Calc enter some numbers leave OLE object -> The object is rendered blurred. Enter OLE object (double click) -> the content is rendered correctly Print document -> the content of the OLE object is printed in lower quality than rest of document Combined documents with text and calculations cannot be printed in unified quality. -> This type of document is not up to office standards. Only on Ubuntu (on Mac this cannot be observed) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libreoffice-writer 1:6.0.6-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Oct 14 20:29:01 2018 InstallationDate: Installed on 2018-04-30 (167 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1797796/+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 1797796] Re: embedding OLE objects in Writer leads to blurred print
This issue does not happen under 18.04(.1). Only on 18.10. It happens in the default installation. Current version is 6.1.2.1 and any embedded file or object gets rendered blurred. Haven't tried snap only AppImage. With AppImage, all embediments are rendered precisely. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1797796 Title: embedding OLE objects in Writer leads to blurred print Status in libreoffice package in Ubuntu: Incomplete Bug description: Steps to create: Open blank Writer document Insert OLE object -> Libreoffice Calc enter some numbers leave OLE object -> The object is rendered blurred. Enter OLE object (double click) -> the content is rendered correctly Print document -> the content of the OLE object is printed in lower quality than rest of document Combined documents with text and calculations cannot be printed in unified quality. -> This type of document is not up to office standards. Only on Ubuntu (on Mac this cannot be observed) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libreoffice-writer 1:6.0.6-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Oct 14 20:29:01 2018 InstallationDate: Installed on 2018-04-30 (167 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1797796/+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 1799430] Re: Icon dock visible on lock screen
Just to let others know: @Plurto 's suggestion to set the dock transparency to FIXED (which makes the dock assume a static color) does not remedy the situation on my machines. I tried with different transparency settings as well. The issue still exists -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1799430 Title: Icon dock visible on lock screen Status in gnome-shell-extension-dashtodock package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: When locking the machine with alt-L the icon dock is still visible. After Login, the dock does not get adjusted to the top menu. In rare cases, the dock does not respond any more. This requires a reboot of the machine ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: mutter 3.30.1-1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 23 12:59:27 2018 InstallationDate: Installed on 2018-04-30 (176 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: mutter UpgradeStatus: Upgraded to cosmic on 2018-10-20 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-dashtodock/+bug/1799430/+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 1799430] Re: Icon dock visible on lock screen
It gets better all the while. Now the desktop shows completely (with open application windows). Interaction is not possible in the windows but the content can be seen. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1799430 Title: Icon dock visible on lock screen Status in gnome-shell-extension-dashtodock package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: When locking the machine with alt-L the icon dock is still visible. After Login, the dock does not get adjusted to the top menu. In rare cases, the dock does not respond any more. This requires a reboot of the machine ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: mutter 3.30.1-1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 23 12:59:27 2018 InstallationDate: Installed on 2018-04-30 (176 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: mutter UpgradeStatus: Upgraded to cosmic on 2018-10-20 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-dashtodock/+bug/1799430/+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 1801382] Re: printing complex documents does not reproduce screen image on paper
Todays update of evince (3.30.1-1ubuntu1.2) did not change anything. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1801382 Title: printing complex documents does not reproduce screen image on paper Status in evince package in Ubuntu: Confirmed Status in gtk+3.0 package in Ubuntu: Confirmed Bug description: Ubuntu 18.10 latest update (by 2.11.2018) printing PDF documents that contain embedded images, these images get printed nearly black and completely illegible. I have attached a sample file and a printout of my cups pdf writer (which produces the exact same results as the printer) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: cups 2.2.8-5ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CupsErrorLog: W [02/Nov/2018:16:18:30 +0100] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'HP_Color_LaserJet_MFP_M477fdw_AF82F1_-Gray..\' already exists W [02/Nov/2018:16:18:30 +0100] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'HP_Color_LaserJet_MFP_M477fdw_AF82F1_-DeviceN..\' already exists W [02/Nov/2018:16:20:30 +0100] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'HP_Color_LaserJet_MFP_M477fdw_AF82F1_-Gray..\' already exists W [02/Nov/2018:16:20:30 +0100] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'HP_Color_LaserJet_MFP_M477fdw_AF82F1_-DeviceN..\' already exists CurrentDesktop: ubuntu:GNOME Date: Fri Nov 2 16:21:51 2018 InstallationDate: Installed on 2018-04-30 (186 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lpstat: device for HP_Color_LaserJet_MFP_M477fdw: hp:/net/HP_Color_LaserJet_MFP_M477fdw?ip=10.1.0.21 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 05ac:0273 Apple, Inc. Bus 001 Device 002: ID 05ac:8290 Apple, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Apple Inc. MacBookPro12,1 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP_Color_LaserJet_MFP_M477fdw.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP_Color_LaserJet_MFP_M477fdw.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: cups UpgradeStatus: Upgraded to cosmic on 2018-10-20 (13 days ago) dmi.bios.date: 08/08/2017 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP121.88Z.0171.B00.1708080033 dmi.board.name: Mac-E43C1C25D4880AD6 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro12,1 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-E43C1C25D4880AD6 dmi.modalias: dmi:bvnAppleInc.:bvrMBP121.88Z.0171.B00.1708080033:bd08/08/2017:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro12,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1801382/+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 1801382] Re: printing complex documents does not reproduce screen image on paper
** Attachment added: "This is the printed document with blackened images (s. page 7)" https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1801382/+attachment/5208359/+files/StepStone_Eyetracking_Whitepaper_after_printing_with_cups.pdf -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1801382 Title: printing complex documents does not reproduce screen image on paper Status in cups package in Ubuntu: New Bug description: Ubuntu 18.10 latest update (by 2.11.2018) printing PDF documents that contain embedded images, these images get printed nearly black and completely illegible. I have attached a sample file and a printout of my cups pdf writer (which produces the exact same results as the printer) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: cups 2.2.8-5ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CupsErrorLog: W [02/Nov/2018:16:18:30 +0100] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'HP_Color_LaserJet_MFP_M477fdw_AF82F1_-Gray..\' already exists W [02/Nov/2018:16:18:30 +0100] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'HP_Color_LaserJet_MFP_M477fdw_AF82F1_-DeviceN..\' already exists W [02/Nov/2018:16:20:30 +0100] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'HP_Color_LaserJet_MFP_M477fdw_AF82F1_-Gray..\' already exists W [02/Nov/2018:16:20:30 +0100] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'HP_Color_LaserJet_MFP_M477fdw_AF82F1_-DeviceN..\' already exists CurrentDesktop: ubuntu:GNOME Date: Fri Nov 2 16:21:51 2018 InstallationDate: Installed on 2018-04-30 (186 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lpstat: device for HP_Color_LaserJet_MFP_M477fdw: hp:/net/HP_Color_LaserJet_MFP_M477fdw?ip=10.1.0.21 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 05ac:0273 Apple, Inc. Bus 001 Device 002: ID 05ac:8290 Apple, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Apple Inc. MacBookPro12,1 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP_Color_LaserJet_MFP_M477fdw.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP_Color_LaserJet_MFP_M477fdw.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: cups UpgradeStatus: Upgraded to cosmic on 2018-10-20 (13 days ago) dmi.bios.date: 08/08/2017 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP121.88Z.0171.B00.1708080033 dmi.board.name: Mac-E43C1C25D4880AD6 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro12,1 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-E43C1C25D4880AD6 dmi.modalias: dmi:bvnAppleInc.:bvrMBP121.88Z.0171.B00.1708080033:bd08/08/2017:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro12,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1801382/+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 1801382] [NEW] printing complex documents does not reproduce screen image on paper
Public bug reported: Ubuntu 18.10 latest update (by 2.11.2018) printing PDF documents that contain embedded images, these images get printed nearly black and completely illegible. I have attached a sample file and a printout of my cups pdf writer (which produces the exact same results as the printer) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: cups 2.2.8-5ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CupsErrorLog: W [02/Nov/2018:16:18:30 +0100] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'HP_Color_LaserJet_MFP_M477fdw_AF82F1_-Gray..\' already exists W [02/Nov/2018:16:18:30 +0100] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'HP_Color_LaserJet_MFP_M477fdw_AF82F1_-DeviceN..\' already exists W [02/Nov/2018:16:20:30 +0100] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'HP_Color_LaserJet_MFP_M477fdw_AF82F1_-Gray..\' already exists W [02/Nov/2018:16:20:30 +0100] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'HP_Color_LaserJet_MFP_M477fdw_AF82F1_-DeviceN..\' already exists CurrentDesktop: ubuntu:GNOME Date: Fri Nov 2 16:21:51 2018 InstallationDate: Installed on 2018-04-30 (186 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lpstat: device for HP_Color_LaserJet_MFP_M477fdw: hp:/net/HP_Color_LaserJet_MFP_M477fdw?ip=10.1.0.21 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 05ac:0273 Apple, Inc. Bus 001 Device 002: ID 05ac:8290 Apple, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Apple Inc. MacBookPro12,1 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP_Color_LaserJet_MFP_M477fdw.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP_Color_LaserJet_MFP_M477fdw.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: cups UpgradeStatus: Upgraded to cosmic on 2018-10-20 (13 days ago) dmi.bios.date: 08/08/2017 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP121.88Z.0171.B00.1708080033 dmi.board.name: Mac-E43C1C25D4880AD6 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro12,1 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-E43C1C25D4880AD6 dmi.modalias: dmi:bvnAppleInc.:bvrMBP121.88Z.0171.B00.1708080033:bd08/08/2017:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro12,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic ** Attachment added: "Original PDF with embedded images" https://bugs.launchpad.net/bugs/1801382/+attachment/5208346/+files/StepStone_Eyetracking_Whitepaper.pdf -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1801382 Title: printing complex documents does not reproduce screen image on paper Status in cups package in Ubuntu: New Bug description: Ubuntu 18.10 latest update (by 2.11.2018) printing PDF documents that contain embedded images, these images get printed nearly black and completely illegible. I have attached a sample file and a printout of my cups pdf writer (which produces the exact same results as the printer) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: cups 2.2.8-5ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CupsErrorLog: W [02/Nov/2018:16:18:30 +0100] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'HP_Color_LaserJet_MFP_M477fdw_AF82F1_-Gray..\' already exists W [02/Nov/2018:16:18:30 +0100] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'HP_Color_LaserJet_MFP_M477fdw_AF82F1_-DeviceN..\' already exists W [02/Nov/2018:16:20:30 +0100] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'HP_Color_LaserJet_MFP_M477fdw_AF82F1_-Gray..\' already exists W [02/Nov/2018:16:20:30 +0100] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'HP_Color_LaserJet_MFP_M477fdw_AF82F1_-DeviceN..\' already exists CurrentDesktop: ubuntu:GNOME Date: Fri Nov 2 16:21:51 2018 InstallationDate: Installed on 2018-04-30 (186 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lpstat: device for HP_Color_LaserJet_MFP_M477fdw:
[Desktop-packages] [Bug 1800333] Re: Ubuntu dock not working properly
@Marc re d) I have a terminal on my dock. I can open this terminal from the lock screen I do have sudo rights on my account I can enter commands that are kept in the buffer I can press ENTER to get the command executed I just leave it up to your judgement if this is a security issue. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1800333 Title: Ubuntu dock not working properly Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: Ubuntu 18.10 Linux mbpr13b 4.18.0-10-generic #11-Ubuntu SMP Thu Oct 11 15:13:55 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux Upgrade from Ubuntu 18.04, all updates applied Ubuntu dock has several issues (some reported elsewhere) a) dock does not allow to relocate on screen (does not honour gsetting dock-position) b) dock does not react to hotkeys (even though are set in gsettings) c) dock does not hide on lock screen (https://www.queryxchange.com/q/3_1085426/desktop-is-visible-is-visible-after-suspend/) d) dock does allow application launch, termination and some commands when machine in locked e) dock appears after resume from RAM f) dash button does not react on first mouse click when applications are open g) dock changes size if applications are open and a dot indicates the fact here are the Gnome settings: gsettings list-recursively org.gnome.shell.extensions.dash-to-dock org.gnome.shell.extensions.dash-to-dock click-action 'previews' org.gnome.shell.extensions.dash-to-dock preferred-monitor -1 org.gnome.shell.extensions.dash-to-dock force-straight-corner false org.gnome.shell.extensions.dash-to-dock show-show-apps-button true org.gnome.shell.extensions.dash-to-dock show-windows-preview true org.gnome.shell.extensions.dash-to-dock animation-time 0.20001 org.gnome.shell.extensions.dash-to-dock scroll-action 'switch-workspace' org.gnome.shell.extensions.dash-to-dock height-fraction 0.90002 org.gnome.shell.extensions.dash-to-dock activate-single-window true org.gnome.shell.extensions.dash-to-dock running-indicator-dominant-color false org.gnome.shell.extensions.dash-to-dock custom-theme-customize-running-dots true org.gnome.shell.extensions.dash-to-dock minimize-shift true org.gnome.shell.extensions.dash-to-dock show-apps-at-top true org.gnome.shell.extensions.dash-to-dock pressure-threshold 100.0 org.gnome.shell.extensions.dash-to-dock show-delay 0.25 org.gnome.shell.extensions.dash-to-dock icon-size-fixed true org.gnome.shell.extensions.dash-to-dock intellihide-mode 'ALL_WINDOWS' org.gnome.shell.extensions.dash-to-dock customize-alphas false org.gnome.shell.extensions.dash-to-dock apply-custom-theme false org.gnome.shell.extensions.dash-to-dock hot-keys true org.gnome.shell.extensions.dash-to-dock extend-height true org.gnome.shell.extensions.dash-to-dock background-color '#ff' org.gnome.shell.extensions.dash-to-dock shortcut-timeout 2.0 org.gnome.shell.extensions.dash-to-dock transparency-mode 'ADAPTIVE' org.gnome.shell.extensions.dash-to-dock multi-monitor false org.gnome.shell.extensions.dash-to-dock shortcut-text 'q' org.gnome.shell.extensions.dash-to-dock isolate-workspaces false org.gnome.shell.extensions.dash-to-dock max-alpha 0.80004 org.gnome.shell.extensions.dash-to-dock app-shift-hotkey-10 ['0'] org.gnome.shell.extensions.dash-to-dock hide-delay 0.20001 org.gnome.shell.extensions.dash-to-dock show-favorites true org.gnome.shell.extensions.dash-to-dock custom-theme-running-dots-border-color '#e95420' org.gnome.shell.extensions.dash-to-dock custom-theme-running-dots-border-width 0 org.gnome.shell.extensions.dash-to-dock app-hotkey-10 ['0'] org.gnome.shell.extensions.dash-to-dock app-ctrl-hotkey-1 ['1'] org.gnome.shell.extensions.dash-to-dock app-ctrl-hotkey-2 ['2'] org.gnome.shell.extensions.dash-to-dock app-ctrl-hotkey-3 ['3'] org.gnome.shell.extensions.dash-to-dock app-ctrl-hotkey-4 ['4'] org.gnome.shell.extensions.dash-to-dock app-ctrl-hotkey-5 ['5'] org.gnome.shell.extensions.dash-to-dock app-ctrl-hotkey-6 ['6'] org.gnome.shell.extensions.dash-to-dock app-ctrl-hotkey-8 ['8'] org.gnome.shell.extensions.dash-to-dock app-ctrl-hotkey-9 ['9'] org.gnome.shell.extensions.dash-to-dock app-hotkey-1 ['1'] org.gnome.shell.extensions.dash-to-dock app-hotkey-2 ['2'] org.gnome.shell.extensions.dash-to-dock isolate-monitors false org.gnome.shell.extensions.dash-to-dock app-hotkey-4 ['4'] org.gnome.shell.extensions.dash-to-dock app-hotkey-5 ['5'] org.gnome.shell.extensions.dash-to-dock app-hotkey-6 ['6'] org.gnome.shell.extensions.dash-to-dock app-hotkey-3 ['3'] org.gnome.shell.extensions.dash-to-dock app-hotkey-8 ['8'] org.gnome.shell.extensions.dash-to-dock app-hotkey-9 ['9'] org.gnome.shell.extensions.dash-to-dock
[Desktop-packages] [Bug 1799430] Re: Icon dock visible on lock screen
The activity menu remains operational. This leads to the situation that applications can be started, stopped and system tools be launched. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1799430 Title: Icon dock visible on lock screen Status in gnome-shell-extension-dashtodock package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: When locking the machine with alt-L the icon dock is still visible. After Login, the dock does not get adjusted to the top menu. In rare cases, the dock does not respond any more. This requires a reboot of the machine ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: mutter 3.30.1-1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 23 12:59:27 2018 InstallationDate: Installed on 2018-04-30 (176 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: mutter UpgradeStatus: Upgraded to cosmic on 2018-10-20 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-dashtodock/+bug/1799430/+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 1799430] [NEW] Icon dock visible on lock screen
Public bug reported: When locking the machine with alt-L the icon dock is still visible. After Login, the dock does not get adjusted to the top menu. In rare cases, the dock does not respond any more. This requires a reboot of the machine ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: mutter 3.30.1-1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 23 12:59:27 2018 InstallationDate: Installed on 2018-04-30 (176 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: mutter UpgradeStatus: Upgraded to cosmic on 2018-10-20 (2 days ago) ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1799430 Title: Icon dock visible on lock screen Status in mutter package in Ubuntu: New Bug description: When locking the machine with alt-L the icon dock is still visible. After Login, the dock does not get adjusted to the top menu. In rare cases, the dock does not respond any more. This requires a reboot of the machine ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: mutter 3.30.1-1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 23 12:59:27 2018 InstallationDate: Installed on 2018-04-30 (176 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: mutter UpgradeStatus: Upgraded to cosmic on 2018-10-20 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1799430/+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 1798939] [NEW] package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-com
Public bug reported: Just tried to install NVIDIA drivers ProblemType: Package DistroRelease: Ubuntu 18.04 Package: nvidia-340 (not installed) ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 Date: Sat Oct 20 09:31:09 2018 DuplicateSignature: package:nvidia-340:(not installed) Unpacking nvidia-340 (340.107-0ubuntu0.18.04.1) ... dpkg: error processing archive /tmp/apt-dpkg-install-h4ndlf/3-nvidia-340_340.107-0ubuntu0.18.04.1_amd64.deb (--unpack): trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-390 390.48-0ubuntu3 ErrorMessage: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-390 390.48-0ubuntu3 InstallationDate: Installed on 2018-04-28 (174 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3ubuntu0.1 SourcePackage: nvidia-graphics-drivers-340 Title: package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-390 390.48-0ubuntu3 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-340 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic package-conflict -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1798939 Title: package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-390 390.48-0ubuntu3 Status in nvidia-graphics-drivers-340 package in Ubuntu: New Bug description: Just tried to install NVIDIA drivers ProblemType: Package DistroRelease: Ubuntu 18.04 Package: nvidia-340 (not installed) ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 Date: Sat Oct 20 09:31:09 2018 DuplicateSignature: package:nvidia-340:(not installed) Unpacking nvidia-340 (340.107-0ubuntu0.18.04.1) ... dpkg: error processing archive /tmp/apt-dpkg-install-h4ndlf/3-nvidia-340_340.107-0ubuntu0.18.04.1_amd64.deb (--unpack): trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-390 390.48-0ubuntu3 ErrorMessage: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-390 390.48-0ubuntu3 InstallationDate: Installed on 2018-04-28 (174 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3ubuntu0.1 SourcePackage: nvidia-graphics-drivers-340 Title: package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-390 390.48-0ubuntu3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1798939/+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 1797796] Re: embedding OLE objects in Writer leads to blurred print
OpenCL is installed. Activating in LibreOffice is not possible (settings are ignored) Screenshot of document attached (font of document is clear, that of the embeddement not) As mentioned above: Using the AppImage from LibreOffice.org works fine. I have an up-to-date installation as well and the issue can be observed on several computers. It occurred with 6.0.6 update of LO ** Attachment added: "Screenshot from 2018-10-16 09-55-04.png" https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1797796/+attachment/5201566/+files/Screenshot%20from%202018-10-16%2009-55-04.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1797796 Title: embedding OLE objects in Writer leads to blurred print Status in libreoffice package in Ubuntu: Incomplete Bug description: Steps to create: Open blank Writer document Insert OLE object -> Libreoffice Calc enter some numbers leave OLE object -> The object is rendered blurred. Enter OLE object (double click) -> the content is rendered correctly Print document -> the content of the OLE object is printed in lower quality than rest of document Combined documents with text and calculations cannot be printed in unified quality. -> This type of document is not up to office standards. Only on Ubuntu (on Mac this cannot be observed) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libreoffice-writer 1:6.0.6-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Oct 14 20:29:01 2018 InstallationDate: Installed on 2018-04-30 (167 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1797796/+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 1797796] Re: embedding OLE objects in Writer leads to blurred print
Downloading LibreOffice 6.1.2.1 AppImage (Full) this issue does not exist in the image version. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1797796 Title: embedding OLE objects in Writer leads to blurred print Status in libreoffice package in Ubuntu: New Bug description: Steps to create: Open blank Writer document Insert OLE object -> Libreoffice Calc enter some numbers leave OLE object -> The object is rendered blurred. Enter OLE object (double click) -> the content is rendered correctly Print document -> the content of the OLE object is printed in lower quality than rest of document Combined documents with text and calculations cannot be printed in unified quality. -> This type of document is not up to office standards. Only on Ubuntu (on Mac this cannot be observed) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libreoffice-writer 1:6.0.6-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Oct 14 20:29:01 2018 InstallationDate: Installed on 2018-04-30 (167 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1797796/+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 1797796] [NEW] embedding OLE objects in Writer leads to blurred print
Public bug reported: Steps to create: Open blank Writer document Insert OLE object -> Libreoffice Calc enter some numbers leave OLE object -> The object is rendered blurred. Enter OLE object (double click) -> the content is rendered correctly Print document -> the content of the OLE object is printed in lower quality than rest of document Combined documents with text and calculations cannot be printed in unified quality. -> This type of document is not up to office standards. Only on Ubuntu (on Mac this cannot be observed) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libreoffice-writer 1:6.0.6-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Oct 14 20:29:01 2018 InstallationDate: Installed on 2018-04-30 (167 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1797796 Title: embedding OLE objects in Writer leads to blurred print Status in libreoffice package in Ubuntu: New Bug description: Steps to create: Open blank Writer document Insert OLE object -> Libreoffice Calc enter some numbers leave OLE object -> The object is rendered blurred. Enter OLE object (double click) -> the content is rendered correctly Print document -> the content of the OLE object is printed in lower quality than rest of document Combined documents with text and calculations cannot be printed in unified quality. -> This type of document is not up to office standards. Only on Ubuntu (on Mac this cannot be observed) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libreoffice-writer 1:6.0.6-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Oct 14 20:29:01 2018 InstallationDate: Installed on 2018-04-30 (167 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1797796/+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 663534] Re: Printing errors after upgrade
Bug fixed since several versions ** Changed in: cups (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/663534 Title: Printing errors after upgrade Status in cups package in Ubuntu: Fix Released Bug description: Binary package hint: cups Updated cups and pdf printing today (auto upgrade) Now printing double-sided does not work (even when set on the printer). Printing of PDFs stalls and does not print anything. ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: cups 1.4.4-6ubuntu2.1 ProcVersionSignature: Ubuntu 2.6.35-22.35-generic 2.6.35.4 Uname: Linux 2.6.35-22-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Tue Oct 19 23:07:49 2010 InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release Candidate amd64 (20091020.3) Lpstat: device for HP-Color-LaserJet-CP2025dn: hp:/net/HP_Color_LaserJet_CP2025dn?zc=NPI33DED8 MachineType: Hewlett-Packard HP Compaq 8510w Papersize: letter PccardctlStatus: Socket 0: no card Socket 1: 3.3V 16-bit PC Card Subdevice 0 (function 0) bound to driver "pata_pcmcia" PpdFiles: HP-Color-LaserJet-CP2025dn: HP Color LaserJet cp2025dn pcl3, hpcups 3.10.6 ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-22-generic root=UUID=b921775a-49a7-48e8-985e-1907bc29f71e ro quiet splash ProcEnviron: LANGUAGE=en_GB:en LANG=en_GB.utf8 SHELL=/bin/bash SourcePackage: cups dmi.bios.date: 07/25/2007 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68MVD Ver. F.05 dmi.board.name: 30C5 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 71.32 dmi.chassis.asset.tag: CNU7402CLM dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68MVDVer.F.05:bd07/25/2007:svnHewlett-Packard:pnHPCompaq8510w:pvrF.05:rvnHewlett-Packard:rn30C5:rvrKBCVersion71.32:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP Compaq 8510w dmi.product.version: F.05 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/663534/+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 663534] Re: Printing errors after upgrade
can be closed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/663534 Title: Printing errors after upgrade Status in cups package in Ubuntu: Fix Released Bug description: Binary package hint: cups Updated cups and pdf printing today (auto upgrade) Now printing double-sided does not work (even when set on the printer). Printing of PDFs stalls and does not print anything. ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: cups 1.4.4-6ubuntu2.1 ProcVersionSignature: Ubuntu 2.6.35-22.35-generic 2.6.35.4 Uname: Linux 2.6.35-22-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Tue Oct 19 23:07:49 2010 InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release Candidate amd64 (20091020.3) Lpstat: device for HP-Color-LaserJet-CP2025dn: hp:/net/HP_Color_LaserJet_CP2025dn?zc=NPI33DED8 MachineType: Hewlett-Packard HP Compaq 8510w Papersize: letter PccardctlStatus: Socket 0: no card Socket 1: 3.3V 16-bit PC Card Subdevice 0 (function 0) bound to driver "pata_pcmcia" PpdFiles: HP-Color-LaserJet-CP2025dn: HP Color LaserJet cp2025dn pcl3, hpcups 3.10.6 ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-22-generic root=UUID=b921775a-49a7-48e8-985e-1907bc29f71e ro quiet splash ProcEnviron: LANGUAGE=en_GB:en LANG=en_GB.utf8 SHELL=/bin/bash SourcePackage: cups dmi.bios.date: 07/25/2007 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68MVD Ver. F.05 dmi.board.name: 30C5 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 71.32 dmi.chassis.asset.tag: CNU7402CLM dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68MVDVer.F.05:bd07/25/2007:svnHewlett-Packard:pnHPCompaq8510w:pvrF.05:rvnHewlett-Packard:rn30C5:rvrKBCVersion71.32:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP Compaq 8510w dmi.product.version: F.05 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/663534/+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 1699605] Re: Panes in Thunderbird and Firefox unreadable
Hi G, this bug has been eliminated on my computer a long time ago (I did a fresh install for 18.04 as well) It seems as Alberto Donato (ack) has this issue still. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1699605 Title: Panes in Thunderbird and Firefox unreadable Status in arc-theme package in Ubuntu: Confirmed Status in firefox package in Ubuntu: Incomplete Bug description: Arc-darc theme for budgie provides a comforting color scheme. However fonts and background colors in thunderbird (HTML messages) and firefox (input fields, text entries) are hard to read as the bgcolor and fgcolor differ only slightly (dark blue to dark gray). Is there a way to fix this? (I tried to work myself through the css file but did not find any indication which element is responsible) ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: arc-theme 20170302-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15 Uname: Linux 4.10.0-24-generic x86_64 NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Wed Jun 21 23:24:03 2017 InstallationDate: Installed on 2017-05-25 (27 days ago) InstallationMedia: Ubuntu-Budgie 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all SourcePackage: arc-theme UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/arc-theme/+bug/1699605/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1646455] Re: Unacceptably slow performance in Thunderbird
This issue has been resolved long time ago.
Thanks for asking and please close the issue.
Wolf Rogner
On 2018-07-14 18:45, gf wrote:
> Hello Wolf,
> Thank you for submitting this bug and reporting a problem with slow
> performance in Thunderbird. You made this bug report in 2016 and there have
> been several versions of Ubuntu and Thunderbird since then.
>
> Could you confirm that this is no longer a problem and that we can close the
> ticket?
> If it is still a problem, are you still interested in finding a solution to
> this bug?
> If you are, could you run the following (only once):
> apport-collect BUGNUMBER
> and upload the updated logs and and any other logs that are relevant for this
> particular issue.
>
> Thank you again for helping make Ubuntu and Thunderbird better.
> G
>
> ** Changed in: thunderbird (Ubuntu)
>Status: New => Incomplete
>
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to thunderbird in Ubuntu.
https://bugs.launchpad.net/bugs/1646455
Title:
Unacceptably slow performance in Thunderbird
Status in thunderbird package in Ubuntu:
Incomplete
Bug description:
Starting with 16.10 Thunderbirds startup time became agonizingly slow
From less than 3 seconds (to the blank window) and less than 7 seconds (to
accepting input)
to 17 seconds (blank window) and 28 seconds (to accepting input)
[same machine, same plugins]
Now, with the update to 45.5.1 sending an email increase the time from
pressing send to the disappearance of the window from 1 second to more
than 9 seconds (on average).
ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: thunderbird 1:45.5.1+build1-0ubuntu0.16.10.1
ProcVersionSignature: Ubuntu 4.8.0-28.30-generic 4.8.6
Uname: Linux 4.8.0-28-generic x86_64
NonfreeKernelModules: nvidia_uvm wl nvidia_drm nvidia_modeset nvidia
AddonCompatCheckDisabled: False
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: wolf 2669 F pulseaudio
/dev/snd/controlC0: wolf 2669 F pulseaudio
BuildID: 20161130102337
Channel: Unavailable
CurrentDesktop: Unity
Date: Thu Dec 1 11:57:31 2016
ForcedLayersAccel: False
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
IncompatibleExtensions:
Enigmail - {847b3a00-7ab1-11d4-8f02-006008948af5}
English (GB) Language Pack - langpack-en...@thunderbird.mozilla.org
Deutsch (DE) Language Pack - langpack...@thunderbird.mozilla.org
Thunderbird (default) - {972ce4c6-7e08-4474-a285-3208198ce6fd}
InstallationDate: Installed on 2016-10-22 (40 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
IpRoute:
default via 10.1.0.254 dev wlp4s0 proto static metric 600
10.0.0.0/8 dev wlp4s0 proto kernel scope link src 10.1.0.168 metric 600
169.254.0.0/16 dev wlp4s0 scope link metric 1000
172.16.220.0/24 dev vmnet1 proto kernel scope link src 172.16.220.1
192.168.68.0/24 dev vmnet8 proto kernel scope link src 192.168.68.1
MostRecentCrashID: bp-09b01898-5a57-4940-bf7b-9ce882161021
PrefSources:
prefs.js
[Profile]/extensions/{25cf5f06-b211-4df3-9d5a-c0ab253a5561}.xpi:defaults/preferences.js
[Profile]/extensions/{847b3a00-7ab1-11d4-8f02-006008948af5}/defaults/preferences/enigmail.js
/usr/lib/thunderbird/extensions/{a62ef8ec-5fdc-40c2-873c-223b8a6925cc}/defaults/preferences/preferences.js
/usr/lib/thunderbird/extensions/{e2fda1a4-762b-4020-b5ad-a41df1933103}/defaults/preferences/lightning.js
Profiles: Profile0 (Default) - LastVersion=45.5.1/20161130102337 (In use)
RunningIncompatibleAddons: True
SourcePackage: thunderbird
SubmittedCrashIDs:
bp-09b01898-5a57-4940-bf7b-9ce882161021
bp-57849896-c2e9-45b1-9cbf-0bf392160823
bp-47c994ab-4894-4453-a743-08c592160525
bp-407af357-4517-4945-a8da-f0d482151002
bp-b1c86d9c-9939-42a2-af8d-f9e6c2150903
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/21/2012
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBP101.88Z.00EE.B03.1212211437
dmi.board.asset.tag: Base Board Asset Tag#
dmi.board.name: Mac-C3EC7CD22292981F
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookPro10,1
dmi.chassis.type: 10
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-C3EC7CD22292981F
dmi.modalias:
dmi:bvnAppleInc.:bvrMBP101.88Z.00EE.B03.1212211437:bd12/21/2012:svnAppleInc.:pnMacBookPro10,1:pvr1.0:rvnAppleInc.:rnMac-C3EC7CD22292981F:rvrMacBookPro10,1:cvnAppleInc.:ct10:cvrMac-C3EC7CD22292981F:
dmi.product.name: MacBookPro10,1
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1646455/+subscriptions
--
Ma
[Desktop-packages] [Bug 1073879] Re: thunderbird does not sort mails right
Oh dear, this indeed is no longer an issue. I have long since forgotten about it. But thanks for asking. cheers Wolf ** Changed in: thunderbird (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1073879 Title: thunderbird does not sort mails right Status in thunderbird package in Ubuntu: Fix Released Bug description: I store my mail in subfolders. Selecting the following viewing parameters provides wrong results: - Sort by Date - Descending - Threaded will show the threads in descending order with the thread containing the latest mail topmost However within the threads the mails are sorted ascending. Ascending works right but gives the latest mails at the bottom. btw. Evolution demonstrates the correct behaviour. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: thunderbird 16.0.2+build1-0ubuntu0.12.10.1 ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7 Uname: Linux 3.5.0-18-generic x86_64 NonfreeKernelModules: nvidia wl AddonCompatCheckDisabled: False ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: wolf 2732 F pulseaudio /dev/snd/controlC0: wolf 2732 F pulseaudio BuildID: 20121028144326 CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Channel: Unavailable Date: Thu Nov 1 11:21:44 2012 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2011-10-16 (381 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64+mac (20111012) IpRoute: default via 10.1.0.254 dev eth1 proto static 10.0.0.0/8 dev eth1 proto kernel scope link src 10.1.0.123 metric 9 169.254.0.0/16 dev eth1 scope link metric 1000 172.16.164.0/24 dev vmnet8 proto kernel scope link src 172.16.164.1 192.168.179.0/24 dev vmnet1 proto kernel scope link src 192.168.179.1 Locales: extensions.sqlite corrupt or missing MarkForUpload: True Profiles: Profile0 (Default) - LastVersion=16.0.2/20121028144326 (In use) RelatedPackageVersions: adobe-flashplugin 11.2.202.243-0quantal1 rhythmbox-mozilla 2.97-1ubuntu5 totem-mozilla 3.4.3-0ubuntu4 icedtea-7-plugin 1.3-1ubuntu1 browser-plugin-vlc 2.0.0-1 RunningIncompatibleAddons: False SourcePackage: thunderbird Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to quantal on 2012-10-19 (12 days ago) WifiSyslog: dmi.bios.date: 07/26/10 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP61.88Z.0057.B0C.1007261552 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-F22586C8 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro6,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F22586C8 dmi.modalias: dmi:bvnAppleInc.:bvrMBP61.88Z.0057.B0C.1007261552:bd07/26/10:svnAppleInc.:pnMacBookPro6,2:pvr1.0:rvnAppleInc.:rnMac-F22586C8:rvrMacBookPro6,2:cvnAppleInc.:ct10:cvrMac-F22586C8: dmi.product.name: MacBookPro6,2 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1073879/+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 1768741] Re: hplip does not wake up printer
This seems to be related to systemd-resolved rather than hplip. I set the printer to static IP and wakeup works fine. Can be closed ** Changed in: hplip (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1768741 Title: hplip does not wake up printer Status in hplip package in Ubuntu: Invalid Bug description: Ubuntu 18.04 fresh install Printer: Color Laserjet Pro MFP M477fdw The printer suspends after 5 mins to save power. Expected: A print request should wake the printer and print. Actual: The printer queue goes on hold Mitigation measures: 1) wake printer manually (from the display) + unpause queue -> does not print 2) wake printer manually + restart queue -> does not print 3) restart printer (WHY???) + unpause queue -> PRINTS !!! This behaviour can be reproduced in 18.04 and does not exist in previous versions of Ubuntu ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: hplip 3.17.10+repack0-5 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu May 3 08:30:01 2018 InstallationDate: Installed on 2018-04-30 (2 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lpstat: device for HP_Color_LaserJet_MFP_M477fdw: hp:/net/HP_Color_LaserJet_MFP_M477fdw?ip=10.1.0.21 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 05ac:0273 Apple, Inc. Bus 001 Device 002: ID 05ac:8290 Apple, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Apple Inc. MacBookPro12,1 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP_Color_LaserJet_MFP_M477fdw.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP_Color_LaserJet_MFP_M477fdw.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: hplip UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2017 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP121.88Z.0171.B00.1708080033 dmi.board.name: Mac-E43C1C25D4880AD6 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro12,1 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-E43C1C25D4880AD6 dmi.modalias: dmi:bvnAppleInc.:bvrMBP121.88Z.0171.B00.1708080033:bd08/08/2017:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro12,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1768741/+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 1768741] Re: hplip does not wake up printer
Cudos to my wife: Here is a more detailed and accurate description of the issue: Preset: Printer is installed on Ubuntu 18.04 Turning on the printer and printing any document -> works Putting notebook into suspend, after wakeup printing a document -> not printing Mitigation: - reboot printer - reinstall printer software After printer suspended (usually after 5 mins), printing a document -> not printing After manually waking up the printer from the display and printing a document -> not printing In all cases of not printing: If the printer queue was held, resuming from the GUI (both methods, from Settings and the Additional printer settings queue view) the queue goes into printing status and reverts to held. If the printer is freshly rebooted, starting a held queue leads to printing the document. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1768741 Title: hplip does not wake up printer Status in hplip package in Ubuntu: New Bug description: Ubuntu 18.04 fresh install Printer: Color Laserjet Pro MFP M477fdw The printer suspends after 5 mins to save power. Expected: A print request should wake the printer and print. Actual: The printer queue goes on hold Mitigation measures: 1) wake printer manually (from the display) + unpause queue -> does not print 2) wake printer manually + restart queue -> does not print 3) restart printer (WHY???) + unpause queue -> PRINTS !!! This behaviour can be reproduced in 18.04 and does not exist in previous versions of Ubuntu ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: hplip 3.17.10+repack0-5 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu May 3 08:30:01 2018 InstallationDate: Installed on 2018-04-30 (2 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lpstat: device for HP_Color_LaserJet_MFP_M477fdw: hp:/net/HP_Color_LaserJet_MFP_M477fdw?ip=10.1.0.21 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 05ac:0273 Apple, Inc. Bus 001 Device 002: ID 05ac:8290 Apple, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Apple Inc. MacBookPro12,1 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP_Color_LaserJet_MFP_M477fdw.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP_Color_LaserJet_MFP_M477fdw.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: hplip UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2017 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP121.88Z.0171.B00.1708080033 dmi.board.name: Mac-E43C1C25D4880AD6 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro12,1 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-E43C1C25D4880AD6 dmi.modalias: dmi:bvnAppleInc.:bvrMBP121.88Z.0171.B00.1708080033:bd08/08/2017:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro12,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1768741/+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 1768741] [NEW] hplip does not wake up printer
Public bug reported: Ubuntu 18.04 fresh install Printer: Color Laserjet Pro MFP M477fdw The printer suspends after 5 mins to save power. Expected: A print request should wake the printer and print. Actual: The printer queue goes on hold Mitigation measures: 1) wake printer manually (from the display) + unpause queue -> does not print 2) wake printer manually + restart queue -> does not print 3) restart printer (WHY???) + unpause queue -> PRINTS !!! This behaviour can be reproduced in 18.04 and does not exist in previous versions of Ubuntu ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: hplip 3.17.10+repack0-5 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu May 3 08:30:01 2018 InstallationDate: Installed on 2018-04-30 (2 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lpstat: device for HP_Color_LaserJet_MFP_M477fdw: hp:/net/HP_Color_LaserJet_MFP_M477fdw?ip=10.1.0.21 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 05ac:0273 Apple, Inc. Bus 001 Device 002: ID 05ac:8290 Apple, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Apple Inc. MacBookPro12,1 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP_Color_LaserJet_MFP_M477fdw.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP_Color_LaserJet_MFP_M477fdw.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: hplip UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2017 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP121.88Z.0171.B00.1708080033 dmi.board.name: Mac-E43C1C25D4880AD6 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro12,1 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-E43C1C25D4880AD6 dmi.modalias: dmi:bvnAppleInc.:bvrMBP121.88Z.0171.B00.1708080033:bd08/08/2017:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro12,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. ** Affects: hplip (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1768741 Title: hplip does not wake up printer Status in hplip package in Ubuntu: New Bug description: Ubuntu 18.04 fresh install Printer: Color Laserjet Pro MFP M477fdw The printer suspends after 5 mins to save power. Expected: A print request should wake the printer and print. Actual: The printer queue goes on hold Mitigation measures: 1) wake printer manually (from the display) + unpause queue -> does not print 2) wake printer manually + restart queue -> does not print 3) restart printer (WHY???) + unpause queue -> PRINTS !!! This behaviour can be reproduced in 18.04 and does not exist in previous versions of Ubuntu ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: hplip 3.17.10+repack0-5 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu May 3 08:30:01 2018 InstallationDate: Installed on 2018-04-30 (2 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lpstat: device for HP_Color_LaserJet_MFP_M477fdw: hp:/net/HP_Color_LaserJet_MFP_M477fdw?ip=10.1.0.21 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 05ac:0273 Apple, Inc. Bus 001 Device 002: ID 05ac:8290 Apple, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Apple Inc. MacBookPro12,1 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP_Color_LaserJet_MFP_M477fdw.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP_Color_LaserJet_MFP_M477fdw.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: hplip UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2017 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP121.88Z.0171.B00.1708080033 dmi.board.name: Mac-E43C1C25D4880AD6 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro12,1 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-E43C1C25D4880AD6 dmi.modalias:
[Desktop-packages] [Bug 1736820] Re: Laptop doesn't suspend on lid close
I could narrow this issue to the NVIDIA graphics card. If Intel is enabled (prime-select) the issue disappears and the machine sleeps sound and quiet. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1736820 Title: Laptop doesn't suspend on lid close Status in gnome-shell package in Ubuntu: Confirmed Bug description: Laptop is Thinkpad T450. On previous releases of Ubuntu I would close the lid to suspend it. 17.10 doesn't suspend on lid close, which has caused my laptop to overheat in my bag a couple of times. I have installed tweak tool and made sure the power section toggle switch is on. But it makes no difference. I have also tried rebooting, flipping the toggle back and forth, and still nothing. Should I see a key change somewhere in dconf-editor once I flip the switch? Does suspend work for others, on the T450? ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 Uname: Linux 4.13.0-17-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Dec 6 23:25:07 2017 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'command-history' b"['xkill', 'goxel']" b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true' b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' b"['org.gnome.Nautilus.desktop', 'org.gnome.Software.desktop', 'google-chrome.desktop', 'chrome-hebeiaianhihkafkbopcfpkgloimgagb-Default.desktop', 'discord.desktop', 'chrome-flidaonfhnkbealpaagddgffpppelhhb-Profile_1.desktop', 'chrome-celnaknmndcdcjcagffhbhciignkeokb-Default.desktop', 'chrome-dcdbodpaldbchkfinnjphocleggfceip-Default.desktop', 'chrome-ddiddklncfgbfaaahngklemobghhjkim-Default.desktop', 'chrome-fimghoffjcofmboofohmacdeabiimdeg-Profile_1.desktop', 'irccloud-desktop_irccloud-desktop.desktop', 'telegramdesktop.desktop', 'org.gnome.Terminal.desktop', 'code.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2017-08-02 (126 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170712) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1736820/+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 1767715] [NEW] suspend to RAM not working in 18.04
Public bug reported: System: Ubuntu 18.04 fresh install HW: Macbook Pro Retina 15" Settings in Tweak: Suspend on Lid closed The machine does not suspend after lid is closed syslog: --- Apr 28 21:42:18 mbpr15a /usr/lib/gdm3/gdm-x-session[2063]: (EE) event7 - bcm5974: kernel bug: Touch jump detected and discarded. Apr 28 21:42:18 mbpr15a /usr/lib/gdm3/gdm-x-session[2063]: See https://wayland.freedesktop.org/libinput/doc/1.10.4/touchpad_jumping_cursor.html for details Apr 28 21:42:19 mbpr15a /usr/lib/gdm3/gdm-x-session[2063]: (EE) event7 - bcm5974: kernel bug: Touch jump detected and discarded. Apr 28 21:42:19 mbpr15a /usr/lib/gdm3/gdm-x-session[2063]: See https://wayland.freedesktop.org/libinput/doc/1.10.4/touchpad_jumping_cursor.html for details Apr 28 21:42:22 mbpr15a /usr/lib/gdm3/gdm-x-session[2063]: (EE) event7 - bcm5974: kernel bug: Touch jump detected and discarded. Apr 28 21:42:22 mbpr15a /usr/lib/gdm3/gdm-x-session[2063]: See https://wayland.freedesktop.org/libinput/doc/1.10.4/touchpad_jumping_cursor.html for details Apr 28 21:42:26 mbpr15a /usr/lib/gdm3/gdm-x-session[2063]: (EE) event7 - bcm5974: kernel bug: Touch jump detected and discarded. Apr 28 21:42:26 mbpr15a /usr/lib/gdm3/gdm-x-session[2063]: See https://wayland.freedesktop.org/libinput/doc/1.10.4/touchpad_jumping_cursor.html for details Apr 28 21:42:26 mbpr15a /usr/lib/gdm3/gdm-x-session[2063]: (EE) event7 - bcm5974: kernel bug: Touch jump detected and discarded. Apr 28 21:42:26 mbpr15a /usr/lib/gdm3/gdm-x-session[2063]: See https://wayland.freedesktop.org/libinput/doc/1.10.4/touchpad_jumping_cursor.html for details Apr 28 21:42:27 mbpr15a /usr/lib/gdm3/gdm-x-session[2063]: (EE) event7 - bcm5974: kernel bug: Touch jump detected and discarded. Apr 28 21:42:27 mbpr15a /usr/lib/gdm3/gdm-x-session[2063]: See https://wayland.freedesktop.org/libinput/doc/1.10.4/touchpad_jumping_cursor.html for details Apr 28 21:42:27 mbpr15a /usr/lib/gdm3/gdm-x-session[2063]: (EE) event7 - bcm5974: kernel bug: Touch jump detected and discarded. Apr 28 21:42:27 mbpr15a /usr/lib/gdm3/gdm-x-session[2063]: See https://wayland.freedesktop.org/libinput/doc/1.10.4/touchpad_jumping_cursor.html for details Apr 28 21:42:27 mbpr15a /usr/lib/gdm3/gdm-x-session[2063]: (EE) event7 - bcm5974: kernel bug: Touch jump detected and discarded. Apr 28 21:42:27 mbpr15a /usr/lib/gdm3/gdm-x-session[2063]: See https://wayland.freedesktop.org/libinput/doc/1.10.4/touchpad_jumping_cursor.html for details Apr 28 21:42:27 mbpr15a /usr/lib/gdm3/gdm-x-session[2063]: (EE) event7 - bcm5974: kernel bug: Touch jump detected and discarded. Apr 28 21:42:27 mbpr15a /usr/lib/gdm3/gdm-x-session[2063]: See https://wayland.freedesktop.org/libinput/doc/1.10.4/touchpad_jumping_cursor.html for details Apr 28 21:42:34 mbpr15a /usr/lib/gdm3/gdm-x-session[2063]: (EE) event7 - bcm5974: kernel bug: Touch jump detected and discarded. Apr 28 21:42:34 mbpr15a /usr/lib/gdm3/gdm-x-session[2063]: See https://wayland.freedesktop.org/libinput/doc/1.10.4/touchpad_jumping_cursor.html for details Apr 28 21:42:34 mbpr15a /usr/lib/gdm3/gdm-x-session[2063]: (EE) event7 - bcm5974: kernel bug: Touch jump detected and discarded. Apr 28 21:42:34 mbpr15a /usr/lib/gdm3/gdm-x-session[2063]: See https://wayland.freedesktop.org/libinput/doc/1.10.4/touchpad_jumping_cursor.html for details Apr 28 21:42:35 mbpr15a gnome-shell[1460]: _st_paint_shadow_with_opacity: assertion 'shadow_pipeline != NULL' failed ... - ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: wl nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 28 21:46:37 2018 InstallationDate: Installed on 2018-04-28 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1767715 Title: suspend to RAM not working in 18.04 Status in gdm3 package in Ubuntu: New Bug description: System: Ubuntu 18.04 fresh install HW: Macbook Pro Retina 15" Settings in Tweak: Suspend on Lid closed The machine does not suspend after lid is closed syslog: --- Apr 28 21:42:18 mbpr15a /usr/lib/gdm3/gdm-x-session[2063]: (EE) event7 - bcm5974: kernel bug: Touch jump detected and discarded. Apr 28 21:42:18 mbpr15a /usr/lib/gdm3/gdm-x-session[2063]: See https://wayland.freedesktop.org/libinput/doc/1.10.4/touchpad_jumping_cursor.html for details Apr 28 21:42:19 mbpr15a /usr/lib/gdm3/gdm-x-session[2063]: (EE) event7 -
[Desktop-packages] [Bug 1715582] Re: "Operation not supported by backend" when backing up to smb server
Did you try all the settings that I described in this thread? 1. I had to create a /var/cache/samba directory (which you might probably have already). 2. The settings dialog has changed. Storage location Storage location: Network Server Server Address: smb://server/share_name Folder: /complete/path/to/backup/directory I had to play around for a while myself to figure this out. Setting the / was essential (as the path is concatenated as python strings). On the backend, you must have write permission (the whole path, not just the destination directory). I hope this helps. -- 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/1715582 Title: "Operation not supported by backend" when backing up to smb server Status in Déjà Dup: Fix Released Status in deja-dup package in Ubuntu: Fix Released Bug description: OS: Ubuntu 17.10 beta setting up deja-dup to backup to smb/ssh server fails With ssh: Permission denied syslog: Sep 7 10:30:05 mbpr13b deja-dup[30252]: Allocating size to AssistantBackup 0x55d581f75f50 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Sep 7 10:30:05 mbpr13b PackageKit: resolve transaction /149_caabebdc from uid 1000 finished with success after 414ms with smb: Backup failed InvalidBackendURL: missing // - relative paths not supported for scheme gio+invalid: gio+invalid:// syslog: Sep 7 10:32:45 mbpr13b deja-dup[30252]: Allocating size to AssistantBackup 0x55d581fecb70 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Sep 7 10:32:45 mbpr13b PackageKit: resolve transaction /150_abaacaad from uid 1000 finished with success after 402ms ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: deja-dup 35.6-0ubuntu1 ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10 Uname: Linux 4.12.0-13-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Sep 7 10:30:37 2017 InstallationDate: Installed on 2017-09-05 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902) 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/1715582/+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 1754713] Re: Android device not accessible after suspend to RAM
Addition: The issue occured in Ubuntu 17.10 beta and was never removed (I tried a dozen of kernels). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libmtp in Ubuntu. https://bugs.launchpad.net/bugs/1754713 Title: Android device not accessible after suspend to RAM Status in libmtp package in Ubuntu: New Bug description: After reboot connecting an Android phone, on the phone, I get asked if I want to allow device access. Confirming mounts the devices storage in Nautilus. Access to files stored on the internal storage of the phone is possible (r/w). After suspend and resume, the same connection procedure provides notification that the device is available, the device seems mounted normally but access to internal phone storage provides an empty nautilus window (no "Internal storage" device can be seen). Several dismount/mount operations leave the situation unchanged. I cannot get access to the internal data of the phone. The device gets detected and mounted but access to storage is not possible. Rebooting the computer remedies the issue (but a reboot can't be a solution to connection problems). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: libmtp9 1.1.13-1 ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 9 18:13:15 2018 InstallationDate: Installed on 2017-10-20 (140 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: Apple Inc. MacBookPro12,1 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-37-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: udev 234-2ubuntu12.3 SourcePackage: libmtp UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2017 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP121.88Z.0171.B00.1708080033 dmi.board.name: Mac-E43C1C25D4880AD6 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro12,1 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-E43C1C25D4880AD6 dmi.modalias: dmi:bvnAppleInc.:bvrMBP121.88Z.0171.B00.1708080033:bd08/08/2017:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro12,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmtp/+bug/1754713/+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 1754713] [NEW] Android device not accessible after suspend to RAM
Public bug reported: After reboot connecting an Android phone, on the phone, I get asked if I want to allow device access. Confirming mounts the devices storage in Nautilus. Access to files stored on the internal storage of the phone is possible (r/w). After suspend and resume, the same connection procedure provides notification that the device is available, the device seems mounted normally but access to internal phone storage provides an empty nautilus window (no "Internal storage" device can be seen). Several dismount/mount operations leave the situation unchanged. I cannot get access to the internal data of the phone. The device gets detected and mounted but access to storage is not possible. Rebooting the computer remedies the issue (but a reboot can't be a solution to connection problems). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: libmtp9 1.1.13-1 ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 9 18:13:15 2018 InstallationDate: Installed on 2017-10-20 (140 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: Apple Inc. MacBookPro12,1 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-37-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: udev 234-2ubuntu12.3 SourcePackage: libmtp UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2017 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP121.88Z.0171.B00.1708080033 dmi.board.name: Mac-E43C1C25D4880AD6 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro12,1 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-E43C1C25D4880AD6 dmi.modalias: dmi:bvnAppleInc.:bvrMBP121.88Z.0171.B00.1708080033:bd08/08/2017:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro12,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. ** Affects: libmtp (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libmtp in Ubuntu. https://bugs.launchpad.net/bugs/1754713 Title: Android device not accessible after suspend to RAM Status in libmtp package in Ubuntu: New Bug description: After reboot connecting an Android phone, on the phone, I get asked if I want to allow device access. Confirming mounts the devices storage in Nautilus. Access to files stored on the internal storage of the phone is possible (r/w). After suspend and resume, the same connection procedure provides notification that the device is available, the device seems mounted normally but access to internal phone storage provides an empty nautilus window (no "Internal storage" device can be seen). Several dismount/mount operations leave the situation unchanged. I cannot get access to the internal data of the phone. The device gets detected and mounted but access to storage is not possible. Rebooting the computer remedies the issue (but a reboot can't be a solution to connection problems). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: libmtp9 1.1.13-1 ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 9 18:13:15 2018 InstallationDate: Installed on 2017-10-20 (140 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: Apple Inc. MacBookPro12,1 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-37-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: udev 234-2ubuntu12.3 SourcePackage: libmtp UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2017 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP121.88Z.0171.B00.1708080033 dmi.board.name: Mac-E43C1C25D4880AD6 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro12,1 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-E43C1C25D4880AD6 dmi.modalias: dmi:bvnAppleInc.:bvrMBP121.88Z.0171.B00.1708080033:bd08/08/2017:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro12,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmtp/+bug/1754713/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net
[Desktop-packages] [Bug 1723750] Re: firefox 56 overrides printer settings
Same issue in FF 58.0.2 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1723750 Title: firefox 56 overrides printer settings Status in firefox package in Ubuntu: New Bug description: When trying to print a webpage > 1 paper pages firefox refuses to print duplex. Default printer settings set to duplex. Printer settings set to duplex Pages printed single page. In Chromium the pages get printed duplex correctly. So: Firefox overrides system-wide and software settings. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: firefox 56.0+build6-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: wolf 1428 F pulseaudio /dev/snd/controlC0: wolf 1428 F pulseaudio BuildID: 20171003222101 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Sun Oct 15 16:56:39 2017 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2017-09-05 (40 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902) IpRoute: default via 10.1.0.254 dev wlp3s0 proto static metric 600 10.0.0.0/8 dev wlp3s0 proto kernel scope link src 10.1.0.155 metric 600 169.254.0.0/16 dev wlp3s0 scope link metric 1000 Locales: extensions.sqlite corrupt or missing PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=56.0/20171003222101 (In use) RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2017 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP121.88Z.0171.B00.1708080033 dmi.board.name: Mac-E43C1C25D4880AD6 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro12,1 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-E43C1C25D4880AD6 dmi.modalias: dmi:bvnAppleInc.:bvrMBP121.88Z.0171.B00.1708080033:bd08/08/2017:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro12,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1723750/+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 1727653] Re: error: can't start new thread
Just adding -n 4096 or -s 16384 alone or in combination does not do the
trick.
Only adding these two PLUS removing -v 100 works.
This and the fact that on my mbpr15a the original line works fine
confuses me.
--
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/1727653
Title:
error: can't start new thread
Status in Duplicity:
In Progress
Status in deja-dup package in Ubuntu:
Confirmed
Status in duplicity package in Ubuntu:
In Progress
Bug description:
$ uname -a
Linux mbpr13b 4.13.0-16-generic #19-Ubuntu SMP Wed Oct 11 18:35:14 UTC 2017
x86_64 x86_64 x86_64 GNU/Linux
duplicity gets started daily via deja-dup automatically.
Every now and then (approx. every third time) I get the following
error:
--
Failed with an unknown error.
Traceback (most recent call last):
File "/usr/bin/duplicity", line 1546, in
with_tempdir(main)
File "/usr/bin/duplicity", line 1540, in with_tempdir
fn()
File "/usr/bin/duplicity", line 1391, in main
do_backup(action)
File "/usr/bin/duplicity", line 1468, in do_backup
restore(col_stats)
File "/usr/bin/duplicity", line 731, in restore
restore_get_patched_rop_iter(col_stats)):
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 560, in
Write_ROPaths
for ropath in rop_iter:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 523, in
integrate_patch_iters
for patch_seq in collated:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 389, in
yield_tuples
setrorps(overflow, elems)
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 378, in
setrorps
elems[i] = iter_list[i].next()
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 107, in
filter_path_iter
for path in path_iter:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 121, in
difftar2path_iter
tarinfo_list = [tar_iter.next()]
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 339, in
next
self.set_tarfile()
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 333, in
set_tarfile
self.current_fp = self.fileobj_iter.next()
File "/usr/bin/duplicity", line 768, in get_fileobj_iter
manifest.volume_info_dict[vol_num])
File "/usr/bin/duplicity", line 811, in restore_get_enc_fileobj
fileobj = tdp.filtered_open_with_delete("rb")
File "/usr/lib/python2.7/dist-packages/duplicity/dup_temp.py", line 119, in
filtered_open_with_delete
fh = FileobjHooked(path.DupPath.filtered_open(self, mode))
File "/usr/lib/python2.7/dist-packages/duplicity/path.py", line 778, in
filtered_open
return gpg.GPGFile(False, self, gpg_profile)
File "/usr/lib/python2.7/dist-packages/duplicity/gpg.py", line 202, in
__init__
'logger': self.logger_fp})
File "/usr/lib/python2.7/dist-packages/duplicity/gpginterface.py", line
374, in run
create_fhs, attach_fhs)
File "/usr/lib/python2.7/dist-packages/duplicity/gpginterface.py", line
420, in _attach_fork_exec
process.thread.start()
File "/usr/lib/python2.7/threading.py", line 736, in start
_start_new_thread(self.__bootstrap, ())
error: can't start new thread
--
Restarting deja-dup manually fixes the problem and the next few days,
automatic backup will run correctly until (see above).
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: duplicity 0.7.12-1ubuntu1
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
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Oct 26 10:49:45 2017
InstallationDate: Installed on 2017-10-20 (5 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
SourcePackage: duplicity
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/duplicity/+bug/1727653/+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 1727653] Re: error: can't start new thread
Sorry for the delay, I wanted to make sure my answer is accurate.
I have three machines set up with 17.10 afresh.
mbpr13a 8GB, 4.13.0-25-generic
mbpr15a 16GB, 4.13.0-25-generic
mbpr13b 16GB, 4.13.0-32-generic
mbpr15a does backups ooB
mbpr13a/b have the reported issue
The original line in
/etc/xdg/autostart/org.gnome.DejaDup.Monitor.desktop
Exec=sh -c "ulimit -v 100; exec /usr/lib/x86_64-linux-gnu/deja-dup
/deja-dup-monitor"
leads to the issue
Setting ulimit -n or ulimit -s additionally does not remedy the error
This line worked
Exec=sh -c "ulimit -s 16384; ulimit -n 4096; exec /usr/lib/x86_64-linux-
gnu/deja-dup/deja-dup-monitor"
@Vaclav #35: I always test after reboot and consequently after suspend to RAM.
The solution works under those conditions.
What irritates my: mbpr15a works with the original line. ???
--
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/1727653
Title:
error: can't start new thread
Status in Duplicity:
In Progress
Status in deja-dup package in Ubuntu:
Confirmed
Status in duplicity package in Ubuntu:
In Progress
Bug description:
$ uname -a
Linux mbpr13b 4.13.0-16-generic #19-Ubuntu SMP Wed Oct 11 18:35:14 UTC 2017
x86_64 x86_64 x86_64 GNU/Linux
duplicity gets started daily via deja-dup automatically.
Every now and then (approx. every third time) I get the following
error:
--
Failed with an unknown error.
Traceback (most recent call last):
File "/usr/bin/duplicity", line 1546, in
with_tempdir(main)
File "/usr/bin/duplicity", line 1540, in with_tempdir
fn()
File "/usr/bin/duplicity", line 1391, in main
do_backup(action)
File "/usr/bin/duplicity", line 1468, in do_backup
restore(col_stats)
File "/usr/bin/duplicity", line 731, in restore
restore_get_patched_rop_iter(col_stats)):
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 560, in
Write_ROPaths
for ropath in rop_iter:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 523, in
integrate_patch_iters
for patch_seq in collated:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 389, in
yield_tuples
setrorps(overflow, elems)
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 378, in
setrorps
elems[i] = iter_list[i].next()
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 107, in
filter_path_iter
for path in path_iter:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 121, in
difftar2path_iter
tarinfo_list = [tar_iter.next()]
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 339, in
next
self.set_tarfile()
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 333, in
set_tarfile
self.current_fp = self.fileobj_iter.next()
File "/usr/bin/duplicity", line 768, in get_fileobj_iter
manifest.volume_info_dict[vol_num])
File "/usr/bin/duplicity", line 811, in restore_get_enc_fileobj
fileobj = tdp.filtered_open_with_delete("rb")
File "/usr/lib/python2.7/dist-packages/duplicity/dup_temp.py", line 119, in
filtered_open_with_delete
fh = FileobjHooked(path.DupPath.filtered_open(self, mode))
File "/usr/lib/python2.7/dist-packages/duplicity/path.py", line 778, in
filtered_open
return gpg.GPGFile(False, self, gpg_profile)
File "/usr/lib/python2.7/dist-packages/duplicity/gpg.py", line 202, in
__init__
'logger': self.logger_fp})
File "/usr/lib/python2.7/dist-packages/duplicity/gpginterface.py", line
374, in run
create_fhs, attach_fhs)
File "/usr/lib/python2.7/dist-packages/duplicity/gpginterface.py", line
420, in _attach_fork_exec
process.thread.start()
File "/usr/lib/python2.7/threading.py", line 736, in start
_start_new_thread(self.__bootstrap, ())
error: can't start new thread
--
Restarting deja-dup manually fixes the problem and the next few days,
automatic backup will run correctly until (see above).
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: duplicity 0.7.12-1ubuntu1
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
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Oct 26 10:49:45 2017
InstallationDate: Installed on 2017-10-20 (5 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
SourcePackage: duplicity
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/duplicity/+bug/1727653/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help
[Desktop-packages] [Bug 1727653] Re: error: can't start new thread
I cannot confirm that ulimit -s 16384 will heal the issue (suggested in
#30). I have inserted ulimit -s 16384 to no avail.
Exec=sh -c "ulimit -v 100; ulimit -s 16384; ulimit -n 4096; exec
/usr/lib/x86_64-linux-gnu/deja-dup/deja-dup-monitor"
-> still causes the issue.
Trying to check my file count I realized that Nautilus interupts file
count and restarts regularly. This behaviour might be triggered by
several symlinks.
Can it be that duplicity tries to follow a directory structure and gets
confused if circular references via symlinks exist?
If so, I have to draw a link tree for further analysis.
--
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/1727653
Title:
error: can't start new thread
Status in Duplicity:
In Progress
Status in deja-dup package in Ubuntu:
Confirmed
Status in duplicity package in Ubuntu:
In Progress
Bug description:
$ uname -a
Linux mbpr13b 4.13.0-16-generic #19-Ubuntu SMP Wed Oct 11 18:35:14 UTC 2017
x86_64 x86_64 x86_64 GNU/Linux
duplicity gets started daily via deja-dup automatically.
Every now and then (approx. every third time) I get the following
error:
--
Failed with an unknown error.
Traceback (most recent call last):
File "/usr/bin/duplicity", line 1546, in
with_tempdir(main)
File "/usr/bin/duplicity", line 1540, in with_tempdir
fn()
File "/usr/bin/duplicity", line 1391, in main
do_backup(action)
File "/usr/bin/duplicity", line 1468, in do_backup
restore(col_stats)
File "/usr/bin/duplicity", line 731, in restore
restore_get_patched_rop_iter(col_stats)):
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 560, in
Write_ROPaths
for ropath in rop_iter:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 523, in
integrate_patch_iters
for patch_seq in collated:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 389, in
yield_tuples
setrorps(overflow, elems)
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 378, in
setrorps
elems[i] = iter_list[i].next()
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 107, in
filter_path_iter
for path in path_iter:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 121, in
difftar2path_iter
tarinfo_list = [tar_iter.next()]
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 339, in
next
self.set_tarfile()
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 333, in
set_tarfile
self.current_fp = self.fileobj_iter.next()
File "/usr/bin/duplicity", line 768, in get_fileobj_iter
manifest.volume_info_dict[vol_num])
File "/usr/bin/duplicity", line 811, in restore_get_enc_fileobj
fileobj = tdp.filtered_open_with_delete("rb")
File "/usr/lib/python2.7/dist-packages/duplicity/dup_temp.py", line 119, in
filtered_open_with_delete
fh = FileobjHooked(path.DupPath.filtered_open(self, mode))
File "/usr/lib/python2.7/dist-packages/duplicity/path.py", line 778, in
filtered_open
return gpg.GPGFile(False, self, gpg_profile)
File "/usr/lib/python2.7/dist-packages/duplicity/gpg.py", line 202, in
__init__
'logger': self.logger_fp})
File "/usr/lib/python2.7/dist-packages/duplicity/gpginterface.py", line
374, in run
create_fhs, attach_fhs)
File "/usr/lib/python2.7/dist-packages/duplicity/gpginterface.py", line
420, in _attach_fork_exec
process.thread.start()
File "/usr/lib/python2.7/threading.py", line 736, in start
_start_new_thread(self.__bootstrap, ())
error: can't start new thread
--
Restarting deja-dup manually fixes the problem and the next few days,
automatic backup will run correctly until (see above).
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: duplicity 0.7.12-1ubuntu1
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
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Oct 26 10:49:45 2017
InstallationDate: Installed on 2017-10-20 (5 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
SourcePackage: duplicity
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/duplicity/+bug/1727653/+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 1731718] Re: screencast freezes
In my case, the machine hangs up completely -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1731718 Title: screencast freezes Status in gnome-shell package in Ubuntu: Incomplete Bug description: running ubuntu 17.10 it was a fresh install, i didn't upgrade to 17.10 not running in xorg expected: Press Ctrl+Alt+Shift+R to start recording what is on your screen. A red circle is displayed in the top right corner of the screen when the recording is in progress. Once you have finished, press Ctrl+Alt+Shift+R again to stop the recording. The video is automatically saved in your Videos folder in your home folder, with a file name that starts with Screencast and includes the date and time it was taken. actual: i press ctrl+alt+shift+r, and nothing happens. no red dot appears. i press it again, everything freezes. music keeps playing. can't move mouse. gtx 1080, i5-8400 i had chrome, sublime, some terminals, discord open had to reboot physically To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1731718/+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 1743013] Re: deja-dup fails when launched automatically
Hello Vej, to hear that an issue is not an issue is quite irritating. -- 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/1743013 Title: deja-dup fails when launched automatically Status in deja-dup package in Ubuntu: Invalid Bug description: In #1727653 an error was reported that stated that backup using duplicity failed. However, the error only manifests in duplicity but is triggered by the calling Deja-Dup. Launching Deja-Dup automatically will ALWAYS lead to the error. Launching Deja-Dup from the console/bash will NEVER lead to the error. Any attempts to set number of open file limits do not remedy the issue. Please refer to #1727653 and associated errors as all analysis have gone into duplicity so far. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: deja-dup 36.3-0ubuntu0.1 ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 Uname: Linux 4.13.0-25-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jan 12 18:55:12 2018 InstallationDate: Installed on 2017-10-20 (84 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) 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/1743013/+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 1743013] [NEW] deja-dup fails when launched automatically
Public bug reported: In #1727653 an error was reported that stated that backup using duplicity failed. However, the error only manifests in duplicity but is triggered by the calling Deja-Dup. Launching Deja-Dup automatically will ALWAYS lead to the error. Launching Deja-Dup from the console/bash will NEVER lead to the error. Any attempts to set number of open file limits do not remedy the issue. Please refer to #1727653 and associated errors as all analysis have gone into duplicity so far. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: deja-dup 36.3-0ubuntu0.1 ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 Uname: Linux 4.13.0-25-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jan 12 18:55:12 2018 InstallationDate: Installed on 2017-10-20 (84 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: deja-dup UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: deja-dup (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful package-from-proposed wayland-session -- 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/1743013 Title: deja-dup fails when launched automatically Status in deja-dup package in Ubuntu: New Bug description: In #1727653 an error was reported that stated that backup using duplicity failed. However, the error only manifests in duplicity but is triggered by the calling Deja-Dup. Launching Deja-Dup automatically will ALWAYS lead to the error. Launching Deja-Dup from the console/bash will NEVER lead to the error. Any attempts to set number of open file limits do not remedy the issue. Please refer to #1727653 and associated errors as all analysis have gone into duplicity so far. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: deja-dup 36.3-0ubuntu0.1 ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 Uname: Linux 4.13.0-25-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jan 12 18:55:12 2018 InstallationDate: Installed on 2017-10-20 (84 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) 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/1743013/+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 1727653] Re: error: can't start new thread
@Kenneth #17:
I verified that the settings recommended in comment #17 change nothing
(several kernel updates later)
a) if anything, it should be nofile and not nfile
b) /etc/security/limits.conf may be altered but any settings there are ignored
c) ulimit is a bash parameter and cannot be applied system-wide.
d) even when called from the command line with as little as soft limit of 1024
(the default) Deja-Dup/duplicity works fine.
@abautu #19:
Nice try, nevertheless, it does not make Deja-Dup work either.
As I mentioned before: It's not a problem of duplicity but of Deja-Dup.
--
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/1727653
Title:
error: can't start new thread
Status in Duplicity:
In Progress
Status in duplicity package in Ubuntu:
In Progress
Bug description:
$ uname -a
Linux mbpr13b 4.13.0-16-generic #19-Ubuntu SMP Wed Oct 11 18:35:14 UTC 2017
x86_64 x86_64 x86_64 GNU/Linux
duplicity gets started daily via deja-dup automatically.
Every now and then (approx. every third time) I get the following
error:
--
Failed with an unknown error.
Traceback (most recent call last):
File "/usr/bin/duplicity", line 1546, in
with_tempdir(main)
File "/usr/bin/duplicity", line 1540, in with_tempdir
fn()
File "/usr/bin/duplicity", line 1391, in main
do_backup(action)
File "/usr/bin/duplicity", line 1468, in do_backup
restore(col_stats)
File "/usr/bin/duplicity", line 731, in restore
restore_get_patched_rop_iter(col_stats)):
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 560, in
Write_ROPaths
for ropath in rop_iter:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 523, in
integrate_patch_iters
for patch_seq in collated:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 389, in
yield_tuples
setrorps(overflow, elems)
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 378, in
setrorps
elems[i] = iter_list[i].next()
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 107, in
filter_path_iter
for path in path_iter:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 121, in
difftar2path_iter
tarinfo_list = [tar_iter.next()]
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 339, in
next
self.set_tarfile()
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 333, in
set_tarfile
self.current_fp = self.fileobj_iter.next()
File "/usr/bin/duplicity", line 768, in get_fileobj_iter
manifest.volume_info_dict[vol_num])
File "/usr/bin/duplicity", line 811, in restore_get_enc_fileobj
fileobj = tdp.filtered_open_with_delete("rb")
File "/usr/lib/python2.7/dist-packages/duplicity/dup_temp.py", line 119, in
filtered_open_with_delete
fh = FileobjHooked(path.DupPath.filtered_open(self, mode))
File "/usr/lib/python2.7/dist-packages/duplicity/path.py", line 778, in
filtered_open
return gpg.GPGFile(False, self, gpg_profile)
File "/usr/lib/python2.7/dist-packages/duplicity/gpg.py", line 202, in
__init__
'logger': self.logger_fp})
File "/usr/lib/python2.7/dist-packages/duplicity/gpginterface.py", line
374, in run
create_fhs, attach_fhs)
File "/usr/lib/python2.7/dist-packages/duplicity/gpginterface.py", line
420, in _attach_fork_exec
process.thread.start()
File "/usr/lib/python2.7/threading.py", line 736, in start
_start_new_thread(self.__bootstrap, ())
error: can't start new thread
--
Restarting deja-dup manually fixes the problem and the next few days,
automatic backup will run correctly until (see above).
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: duplicity 0.7.12-1ubuntu1
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
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Oct 26 10:49:45 2017
InstallationDate: Installed on 2017-10-20 (5 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
SourcePackage: duplicity
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/duplicity/+bug/1727653/+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 1727653] Re: error: can't start new thread
Deja-Dup and duplicity seemed to work with kernel 4.13.0-19. After that
(21 and 22) the issue reappeared.
Very frustrating.
Workaround: Start Deja-Dup manually after it failed.
Careful: Deja-dup claims that the backup has been carried out even when
the above error occurs. In my case, there is no backup on the server
(so, no, it did not back up, it might have collected the files).
Merry Christmas
--
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/1727653
Title:
error: can't start new thread
Status in Duplicity:
In Progress
Status in duplicity package in Ubuntu:
In Progress
Bug description:
$ uname -a
Linux mbpr13b 4.13.0-16-generic #19-Ubuntu SMP Wed Oct 11 18:35:14 UTC 2017
x86_64 x86_64 x86_64 GNU/Linux
duplicity gets started daily via deja-dup automatically.
Every now and then (approx. every third time) I get the following
error:
--
Failed with an unknown error.
Traceback (most recent call last):
File "/usr/bin/duplicity", line 1546, in
with_tempdir(main)
File "/usr/bin/duplicity", line 1540, in with_tempdir
fn()
File "/usr/bin/duplicity", line 1391, in main
do_backup(action)
File "/usr/bin/duplicity", line 1468, in do_backup
restore(col_stats)
File "/usr/bin/duplicity", line 731, in restore
restore_get_patched_rop_iter(col_stats)):
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 560, in
Write_ROPaths
for ropath in rop_iter:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 523, in
integrate_patch_iters
for patch_seq in collated:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 389, in
yield_tuples
setrorps(overflow, elems)
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 378, in
setrorps
elems[i] = iter_list[i].next()
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 107, in
filter_path_iter
for path in path_iter:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 121, in
difftar2path_iter
tarinfo_list = [tar_iter.next()]
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 339, in
next
self.set_tarfile()
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 333, in
set_tarfile
self.current_fp = self.fileobj_iter.next()
File "/usr/bin/duplicity", line 768, in get_fileobj_iter
manifest.volume_info_dict[vol_num])
File "/usr/bin/duplicity", line 811, in restore_get_enc_fileobj
fileobj = tdp.filtered_open_with_delete("rb")
File "/usr/lib/python2.7/dist-packages/duplicity/dup_temp.py", line 119, in
filtered_open_with_delete
fh = FileobjHooked(path.DupPath.filtered_open(self, mode))
File "/usr/lib/python2.7/dist-packages/duplicity/path.py", line 778, in
filtered_open
return gpg.GPGFile(False, self, gpg_profile)
File "/usr/lib/python2.7/dist-packages/duplicity/gpg.py", line 202, in
__init__
'logger': self.logger_fp})
File "/usr/lib/python2.7/dist-packages/duplicity/gpginterface.py", line
374, in run
create_fhs, attach_fhs)
File "/usr/lib/python2.7/dist-packages/duplicity/gpginterface.py", line
420, in _attach_fork_exec
process.thread.start()
File "/usr/lib/python2.7/threading.py", line 736, in start
_start_new_thread(self.__bootstrap, ())
error: can't start new thread
--
Restarting deja-dup manually fixes the problem and the next few days,
automatic backup will run correctly until (see above).
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: duplicity 0.7.12-1ubuntu1
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
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Oct 26 10:49:45 2017
InstallationDate: Installed on 2017-10-20 (5 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
SourcePackage: duplicity
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/duplicity/+bug/1727653/+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 1722455] Re: Creation of mail/contact/calendar accounts impossible
As a workaround: in ~/.config/evolution/sources create a file calendar.source $ touch calendar.source edit it: [Data Source] DisplayName= Enabled=true Parent=webcal-stub [WebDAV Backend] AvoidIfmatch=false CalendarAutoSchedule=false DisplayName= EmailAddress= ResourcePath= ResourceQuery= SslTrust= [Offline] StaySynchronized=true [Calendar] BackendName=caldav Color=#CC Selected=true [Authentication] Host= Method=plain/password Port=80 ProxyUid=system-proxy RememberPassword=true User= CredentialName= [Security] Method=none [Refresh] Enabled=true IntervalMinutes=1 -- 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/1722455 Title: Creation of mail/contact/calendar accounts impossible Status in gnome-control-center package in Ubuntu: New Bug description: If one wants to use Gnome Calendar or Gnome Contacts one has to create accounts to access the server. Gnome control centre provides prepared account templates for common public providers. There is an IMAP template that is broken (does not allow to connect to inhouse mail servers). Also adding Calendar or Contact connection is not possible. In Gnome Calendar adding new calendars is impossible (there is a workaround by temporarily installing California but that is very unstable). There needs to be a way to install DAV connectors to CALDav and CARDDav as is possible in Thunderbird. Possible workaround (which is not stable): Under ~/.config/evolution one can add a text file containing the configuration to the required service. As there is no refresh function in Calendar or Contacts, this is a fragile solution though (requires constant session creation aka logout/login) ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-control-center 1:3.26.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4 Uname: Linux 4.13.0-15-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 10 08:11:26 2017 InstallationDate: Installed on 2017-09-05 (34 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1722455/+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 1722455] Re: Creation of mail/contact/calendar accounts impossible
How do you add a calendar in GNOME calendar? I tried: Calendar Settings -> Add from Web -> entered my CalDAV calendar URL -> The Add button remains disabled It should be enabled and a control file should be created in ~/.config/evolution/sources. This does not happen. Without Evolution or text fiddling, it is not possible to attach to a calendar other than the predefined (Google, Yahoo, etc.). -- 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/1722455 Title: Creation of mail/contact/calendar accounts impossible Status in gnome-control-center package in Ubuntu: New Bug description: If one wants to use Gnome Calendar or Gnome Contacts one has to create accounts to access the server. Gnome control centre provides prepared account templates for common public providers. There is an IMAP template that is broken (does not allow to connect to inhouse mail servers). Also adding Calendar or Contact connection is not possible. In Gnome Calendar adding new calendars is impossible (there is a workaround by temporarily installing California but that is very unstable). There needs to be a way to install DAV connectors to CALDav and CARDDav as is possible in Thunderbird. Possible workaround (which is not stable): Under ~/.config/evolution one can add a text file containing the configuration to the required service. As there is no refresh function in Calendar or Contacts, this is a fragile solution though (requires constant session creation aka logout/login) ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-control-center 1:3.26.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4 Uname: Linux 4.13.0-15-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 10 08:11:26 2017 InstallationDate: Installed on 2017-09-05 (34 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1722455/+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 1722455] Re: Creation of mail/contact/calendar accounts impossible
** Changed in: gnome-control-center (Ubuntu) Status: Expired => 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/1722455 Title: Creation of mail/contact/calendar accounts impossible Status in gnome-control-center package in Ubuntu: New Bug description: If one wants to use Gnome Calendar or Gnome Contacts one has to create accounts to access the server. Gnome control centre provides prepared account templates for common public providers. There is an IMAP template that is broken (does not allow to connect to inhouse mail servers). Also adding Calendar or Contact connection is not possible. In Gnome Calendar adding new calendars is impossible (there is a workaround by temporarily installing California but that is very unstable). There needs to be a way to install DAV connectors to CALDav and CARDDav as is possible in Thunderbird. Possible workaround (which is not stable): Under ~/.config/evolution one can add a text file containing the configuration to the required service. As there is no refresh function in Calendar or Contacts, this is a fragile solution though (requires constant session creation aka logout/login) ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-control-center 1:3.26.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4 Uname: Linux 4.13.0-15-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 10 08:11:26 2017 InstallationDate: Installed on 2017-09-05 (34 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1722455/+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 1737391] [NEW] Libreoffice Calc Show reference in color fails
Public bug reported: LibreOffice 5.4.2.2 40m0(Build:2) After upgrade, highlighting of referenced cells (as controlled by Tools - Options - Libreoffice Calc - View: Show references in color) stopped working (Build 1 works fine) Example: A1 = 1 B1 = 2 C1 = "=A1+B1" Editing should hilight A1 and B1 cells as they are referenced but they are not. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: libreoffice-calc 1:5.4.2-0ubuntu0.17.10.1 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 Uname: Linux 4.13.0-19-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Dec 10 11:20:10 2017 InstallationDate: Installed on 2017-10-20 (50 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1737391 Title: Libreoffice Calc Show reference in color fails Status in libreoffice package in Ubuntu: New Bug description: LibreOffice 5.4.2.2 40m0(Build:2) After upgrade, highlighting of referenced cells (as controlled by Tools - Options - Libreoffice Calc - View: Show references in color) stopped working (Build 1 works fine) Example: A1 = 1 B1 = 2 C1 = "=A1+B1" Editing should hilight A1 and B1 cells as they are referenced but they are not. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: libreoffice-calc 1:5.4.2-0ubuntu0.17.10.1 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 Uname: Linux 4.13.0-19-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Dec 10 11:20:10 2017 InstallationDate: Installed on 2017-10-20 (50 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1737391/+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 1736680] [NEW] fixefox duplex printing fails
Public bug reported: Duplex printing in Firefox does not work. Printer is set to duplex, printer settings are set to duplex by default. LibreOffice and Chromium print pages duplex by default. Firefox does not even though duplex printing is set in the default settings and in the document printer settings. It simply ignores it. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: firefox 57.0.1+build2-0ubuntu0.17.10.1 ProcVersionSignature: Ubuntu 4.13.0-18.21-generic 4.13.13 Uname: Linux 4.13.0-18-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: wolf 1420 F pulseaudio /dev/snd/controlC0: wolf 1420 F pulseaudio BuildID: 20171129230227 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Wed Dec 6 09:49:10 2017 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2017-10-20 (46 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) IpRoute: default via 10.1.0.254 dev wlp3s0 proto static metric 600 10.0.0.0/8 dev wlp3s0 proto kernel scope link src 10.1.0.155 metric 600 169.254.0.0/16 dev wlp3s0 scope link metric 1000 Locales: extensions.sqlite corrupt or missing PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=57.0.1/20171129230227 (In use) RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2017 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP121.88Z.0171.B00.1708080033 dmi.board.name: Mac-E43C1C25D4880AD6 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro12,1 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-E43C1C25D4880AD6 dmi.modalias: dmi:bvnAppleInc.:bvrMBP121.88Z.0171.B00.1708080033:bd08/08/2017:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro12,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1736680 Title: fixefox duplex printing fails Status in firefox package in Ubuntu: New Bug description: Duplex printing in Firefox does not work. Printer is set to duplex, printer settings are set to duplex by default. LibreOffice and Chromium print pages duplex by default. Firefox does not even though duplex printing is set in the default settings and in the document printer settings. It simply ignores it. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: firefox 57.0.1+build2-0ubuntu0.17.10.1 ProcVersionSignature: Ubuntu 4.13.0-18.21-generic 4.13.13 Uname: Linux 4.13.0-18-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: wolf 1420 F pulseaudio /dev/snd/controlC0: wolf 1420 F pulseaudio BuildID: 20171129230227 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Wed Dec 6 09:49:10 2017 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2017-10-20 (46 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) IpRoute: default via 10.1.0.254 dev wlp3s0 proto static metric 600 10.0.0.0/8 dev wlp3s0 proto kernel scope link src 10.1.0.155 metric 600 169.254.0.0/16 dev wlp3s0 scope link metric 1000 Locales: extensions.sqlite corrupt or missing PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=57.0.1/20171129230227 (In use) RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2017 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP121.88Z.0171.B00.1708080033 dmi.board.name: Mac-E43C1C25D4880AD6 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro12,1 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-E43C1C25D4880AD6 dmi.modalias:
[Desktop-packages] [Bug 1723750] Re: firefox 56 overrides printer settings
The issue still prevails in FF57. about:config -> print.print-duplex 1 Settings: Duplex printing -> Long-Side FF Print Dialog: print duplex -> Long-Side Pages printed singlesided. Chromium 61 -> prints duplex -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1723750 Title: firefox 56 overrides printer settings Status in firefox package in Ubuntu: New Bug description: When trying to print a webpage > 1 paper pages firefox refuses to print duplex. Default printer settings set to duplex. Printer settings set to duplex Pages printed single page. In Chromium the pages get printed duplex correctly. So: Firefox overrides system-wide and software settings. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: firefox 56.0+build6-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: wolf 1428 F pulseaudio /dev/snd/controlC0: wolf 1428 F pulseaudio BuildID: 20171003222101 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Sun Oct 15 16:56:39 2017 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2017-09-05 (40 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902) IpRoute: default via 10.1.0.254 dev wlp3s0 proto static metric 600 10.0.0.0/8 dev wlp3s0 proto kernel scope link src 10.1.0.155 metric 600 169.254.0.0/16 dev wlp3s0 scope link metric 1000 Locales: extensions.sqlite corrupt or missing PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=56.0/20171003222101 (In use) RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2017 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP121.88Z.0171.B00.1708080033 dmi.board.name: Mac-E43C1C25D4880AD6 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro12,1 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-E43C1C25D4880AD6 dmi.modalias: dmi:bvnAppleInc.:bvrMBP121.88Z.0171.B00.1708080033:bd08/08/2017:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro12,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1723750/+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 1727653] Re: error: can't start new thread
@Kenneth:
I increased ulimit to 4096 -> same error
Then I wanted to understand how ulimit works:
ulimit influences the shell (bash!).
I can start duplicity via deja-dup from the console -> works
I can start deja-dup from the launcher (GNOME-Shell) and manually trigger
backup (from the running application) -> works
If deja-dup is started via automatic mechanism (daily launch) -> error
Concluding:
The issue does not lie within duplicity (well this generates the error)
but in the calling mechanism of deja-dup (which must provide duplicity
with different environments depending on how it calls duplicity).
If my conclusion is correct:
Changing ulimit will not help locate the problem
Getting debug traces via console commands will not help locate the problem
We are looking in the wrong place
Maybe the issue should be forwarded to the deja-dup developers to see
how they call duplicity on auto-backup.
--
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/1727653
Title:
error: can't start new thread
Status in Duplicity:
In Progress
Status in duplicity package in Ubuntu:
In Progress
Bug description:
$ uname -a
Linux mbpr13b 4.13.0-16-generic #19-Ubuntu SMP Wed Oct 11 18:35:14 UTC 2017
x86_64 x86_64 x86_64 GNU/Linux
duplicity gets started daily via deja-dup automatically.
Every now and then (approx. every third time) I get the following
error:
--
Failed with an unknown error.
Traceback (most recent call last):
File "/usr/bin/duplicity", line 1546, in
with_tempdir(main)
File "/usr/bin/duplicity", line 1540, in with_tempdir
fn()
File "/usr/bin/duplicity", line 1391, in main
do_backup(action)
File "/usr/bin/duplicity", line 1468, in do_backup
restore(col_stats)
File "/usr/bin/duplicity", line 731, in restore
restore_get_patched_rop_iter(col_stats)):
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 560, in
Write_ROPaths
for ropath in rop_iter:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 523, in
integrate_patch_iters
for patch_seq in collated:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 389, in
yield_tuples
setrorps(overflow, elems)
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 378, in
setrorps
elems[i] = iter_list[i].next()
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 107, in
filter_path_iter
for path in path_iter:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 121, in
difftar2path_iter
tarinfo_list = [tar_iter.next()]
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 339, in
next
self.set_tarfile()
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 333, in
set_tarfile
self.current_fp = self.fileobj_iter.next()
File "/usr/bin/duplicity", line 768, in get_fileobj_iter
manifest.volume_info_dict[vol_num])
File "/usr/bin/duplicity", line 811, in restore_get_enc_fileobj
fileobj = tdp.filtered_open_with_delete("rb")
File "/usr/lib/python2.7/dist-packages/duplicity/dup_temp.py", line 119, in
filtered_open_with_delete
fh = FileobjHooked(path.DupPath.filtered_open(self, mode))
File "/usr/lib/python2.7/dist-packages/duplicity/path.py", line 778, in
filtered_open
return gpg.GPGFile(False, self, gpg_profile)
File "/usr/lib/python2.7/dist-packages/duplicity/gpg.py", line 202, in
__init__
'logger': self.logger_fp})
File "/usr/lib/python2.7/dist-packages/duplicity/gpginterface.py", line
374, in run
create_fhs, attach_fhs)
File "/usr/lib/python2.7/dist-packages/duplicity/gpginterface.py", line
420, in _attach_fork_exec
process.thread.start()
File "/usr/lib/python2.7/threading.py", line 736, in start
_start_new_thread(self.__bootstrap, ())
error: can't start new thread
--
Restarting deja-dup manually fixes the problem and the next few days,
automatic backup will run correctly until (see above).
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: duplicity 0.7.12-1ubuntu1
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
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Oct 26 10:49:45 2017
InstallationDate: Installed on 2017-10-20 (5 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
SourcePackage: duplicity
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/duplicity/+bug/1727653/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe :
[Desktop-packages] [Bug 1722182] Re: Cannot connect Android phone to Ubuntu 17.10
The issue remains after a complete reinstall. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libmtp in Ubuntu. https://bugs.launchpad.net/bugs/1722182 Title: Cannot connect Android phone to Ubuntu 17.10 Status in libmtp package in Ubuntu: New Bug description: $ uname -a Linux mbpr13b 4.13.0-15-generic #16-Ubuntu SMP Wed Oct 4 21:59:25 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux libmtp9 1.1.13-1 installed Attaching Android phone brings up the Android mounted notification, shows the icon on the desktop but selecting the phone in Nautilus does not work (no files shown). => cant read/write files to/from Anddroid phones syslog gets flooded with these messages: ... Oct 9 10:37:38 mbpr13b gvfsd[18269]: Android device detected, assigning default bug flags Oct 9 10:37:38 mbpr13b kernel: [19068.065076] usb 1-1: new high-speed USB device number 93 using xhci_hcd Oct 9 10:37:38 mbpr13b kernel: [19068.449126] usb 1-1: new high-speed USB device number 94 using xhci_hcd Oct 9 10:37:39 mbpr13b kernel: [19068.590300] usb 1-1: New USB device found, idVendor=2a47, idProduct=7f10 Oct 9 10:37:39 mbpr13b kernel: [19068.590304] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Oct 9 10:37:39 mbpr13b kernel: [19068.590306] usb 1-1: Product: Aquaris X5 Plus Oct 9 10:37:39 mbpr13b kernel: [19068.590308] usb 1-1: Manufacturer: bq Oct 9 10:37:39 mbpr13b kernel: [19068.590309] usb 1-1: SerialNumber: XM020064 Oct 9 10:37:39 mbpr13b gvfs-gphoto2-vo[18365]: device (null) has no BUSNUM property, ignoring Oct 9 10:37:39 mbpr13b gvfsd[18269]: Device 0 (VID=2a47 and PID=7f10) is a bq Aquarius E5-4G. Oct 9 10:37:39 mbpr13b kernel: [19068.680431] usb 1-1: USB disconnect, device number 94 Oct 9 10:37:39 mbpr13b gvfsd[18269]: LIBMTP PANIC: could not inspect object property descriptions! Oct 9 10:37:39 mbpr13b gvfsd[18269]: message repeated 25 times: [ LIBMTP PANIC: could not inspect object property descriptions!] Oct 9 10:37:39 mbpr13b gvfsd[18269]: Error 7: Unable to read Maximum Battery Level for this device even though the device supposedly supports this functionality Oct 9 10:37:39 mbpr13b gvfsd[18269]: Error 1: Get Storage information failed. Oct 9 10:37:39 mbpr13b gnome-shell[18263]: invalid cast from 'GTask' to 'GSimpleAsyncResult' Oct 9 10:37:39 mbpr13b gnome-shell[18263]: g_simple_async_result_propagate_error: assertion 'G_IS_SIMPLE_ASYNC_RESULT (simple)' failed Oct 9 10:37:39 mbpr13b gvfsd[18269]: Android device detected, assigning default bug flags Oct 9 10:37:39 mbpr13b kernel: [19069.053047] usb 1-1: new high-speed USB device number 95 using xhci_hcd Oct 9 10:37:39 mbpr13b kernel: [19069.195211] usb 1-1: New USB device found, idVendor=2a47, idProduct=7f10 Oct 9 10:37:39 mbpr13b kernel: [19069.195216] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Oct 9 10:37:39 mbpr13b kernel: [19069.195218] usb 1-1: Product: Aquaris X5 Plus Oct 9 10:37:39 mbpr13b kernel: [19069.195221] usb 1-1: Manufacturer: bq Oct 9 10:37:39 mbpr13b kernel: [19069.195222] usb 1-1: SerialNumber: XM020064 Oct 9 10:37:39 mbpr13b gvfs-gphoto2-vo[18365]: device (null) has no BUSNUM property, ignoring Oct 9 10:37:39 mbpr13b gvfsd[18269]: Device 0 (VID=2a47 and PID=7f10) is a bq Aquarius E5-4G. Oct 9 10:37:39 mbpr13b kernel: [19069.293253] xhci_hcd :00:14.0: WARN Event TRB for slot 8 ep 1 with no TDs queued? Oct 9 10:37:39 mbpr13b gvfsd[18269]: LIBMTP PANIC: could not inspect object property descriptions! Oct 9 10:37:39 mbpr13b kernel: [19069.293359] usb 1-1: USB disconnect, device number 95 Oct 9 10:37:39 mbpr13b kernel: [19069.293468] xhci_hcd :00:14.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state. Oct 9 10:37:39 mbpr13b gvfsd[18269]: message repeated 25 times: [ LIBMTP PANIC: could not inspect object property descriptions!] Oct 9 10:37:39 mbpr13b gvfsd[18269]: Error 7: Unable to read Maximum Battery Level for this device even though the device supposedly supports this functionality Oct 9 10:37:39 mbpr13b gvfsd[18269]: Error 1: Get Storage information failed. Oct 9 10:37:39 mbpr13b gnome-shell[18263]: invalid cast from 'GTask' to 'GSimpleAsyncResult' Oct 9 10:37:39 mbpr13b gnome-shell[18263]: g_simple_async_result_propagate_error: assertion 'G_IS_SIMPLE_ASYNC_RESULT (simple)' failed Oct 9 10:37:40 mbpr13b kernel: [19069.633015] usb 1-1: new high-speed USB device number 96 using xhci_hcd Oct 9 10:37:40 mbpr13b kernel: [19069.775904] usb 1-1: New USB device found, idVendor=2a47, idProduct=7f10 Oct 9 10:37:40 mbpr13b kernel: [19069.775910] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Oct 9 10:37:40 mbpr13b kernel: [19069.775913] usb 1-1: Product: Aquaris X5 Plus Oct 9 10:37:40 mbpr13b kernel: [19069.775915] usb 1-1: Manufacturer: bq Oct 9
[Desktop-packages] [Bug 1727653] Re: error: can't start new thread
Tested 0.7.14-bzr1335-0ubuntu3-ubuntu17.10.1 and it produces the
following error:
Failed with an unknown error.
Traceback (innermost last):
File "/usr/bin/duplicity", line 1559, in
with_tempdir(main)
File "/usr/bin/duplicity", line 1545, in with_tempdir
fn()
File "/usr/bin/duplicity", line 1394, in main
do_backup(action)
File "/usr/bin/duplicity", line 1473, in do_backup
restore(col_stats)
File "/usr/bin/duplicity", line 729, in restore
restore_get_patched_rop_iter(col_stats)):
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 558, in
Write_ROPaths
for ropath in rop_iter:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 521, in
integrate_patch_iters
for patch_seq in collated:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 389, in
yield_tuples
setrorps(overflow, elems)
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 378, in
setrorps
elems[i] = iter_list[i].next()
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 107, in
filter_path_iter
for path in path_iter:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 121, in
difftar2path_iter
tarinfo_list = [tar_iter.next()]
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 339, in
next
self.set_tarfile()
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 333, in
set_tarfile
self.current_fp = self.fileobj_iter.next()
File "/usr/bin/duplicity", line 766, in get_fileobj_iter
manifest.volume_info_dict[vol_num])
File "/usr/bin/duplicity", line 809, in restore_get_enc_fileobj
fileobj = tdp.filtered_open_with_delete("rb")
File "/usr/lib/python2.7/dist-packages/duplicity/dup_temp.py", line 120, in
filtered_open_with_delete
fh = FileobjHooked(path.DupPath.filtered_open(self, mode))
File "/usr/lib/python2.7/dist-packages/duplicity/path.py", line 779, in
filtered_open
return gpg.GPGFile(False, self, gpg_profile)
File "/usr/lib/python2.7/dist-packages/duplicity/gpg.py", line 224, in
__init__
'logger': self.logger_fp})
File "/usr/lib/python2.7/dist-packages/duplicity/gpginterface.py", line 374,
in run
create_fhs, attach_fhs)
File "/usr/lib/python2.7/dist-packages/duplicity/gpginterface.py", line 420,
in _attach_fork_exec
process.thread.start()
File "/usr/lib/python2.7/threading.py", line 736, in start
_start_new_thread(self.__bootstrap, ())
error: can't start new thread
I saw there were 0.7.15 and 0.7.16 available already?
--
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/1727653
Title:
error: can't start new thread
Status in Duplicity:
In Progress
Status in duplicity package in Ubuntu:
In Progress
Bug description:
$ uname -a
Linux mbpr13b 4.13.0-16-generic #19-Ubuntu SMP Wed Oct 11 18:35:14 UTC 2017
x86_64 x86_64 x86_64 GNU/Linux
duplicity gets started daily via deja-dup automatically.
Every now and then (approx. every third time) I get the following
error:
--
Failed with an unknown error.
Traceback (most recent call last):
File "/usr/bin/duplicity", line 1546, in
with_tempdir(main)
File "/usr/bin/duplicity", line 1540, in with_tempdir
fn()
File "/usr/bin/duplicity", line 1391, in main
do_backup(action)
File "/usr/bin/duplicity", line 1468, in do_backup
restore(col_stats)
File "/usr/bin/duplicity", line 731, in restore
restore_get_patched_rop_iter(col_stats)):
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 560, in
Write_ROPaths
for ropath in rop_iter:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 523, in
integrate_patch_iters
for patch_seq in collated:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 389, in
yield_tuples
setrorps(overflow, elems)
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 378, in
setrorps
elems[i] = iter_list[i].next()
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 107, in
filter_path_iter
for path in path_iter:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 121, in
difftar2path_iter
tarinfo_list = [tar_iter.next()]
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 339, in
next
self.set_tarfile()
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 333, in
set_tarfile
self.current_fp = self.fileobj_iter.next()
File "/usr/bin/duplicity", line 768, in get_fileobj_iter
manifest.volume_info_dict[vol_num])
File "/usr/bin/duplicity", line 811, in restore_get_enc_fileobj
fileobj = tdp.filtered_open_with_delete("rb")
File "/usr/lib/python2.7/dist-packages/duplicity/dup_temp.py", line 119, in
[Desktop-packages] [Bug 1727653] Re: duplicity fails with unknown error
ulimit -n -> 1024 (default install)
--
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/1727653
Title:
duplicity fails with unknown error
Status in duplicity package in Ubuntu:
In Progress
Bug description:
$ uname -a
Linux mbpr13b 4.13.0-16-generic #19-Ubuntu SMP Wed Oct 11 18:35:14 UTC 2017
x86_64 x86_64 x86_64 GNU/Linux
duplicity gets started daily via deja-dup automatically.
Every now and then (approx. every third time) I get the following
error:
--
Failed with an unknown error.
Traceback (most recent call last):
File "/usr/bin/duplicity", line 1546, in
with_tempdir(main)
File "/usr/bin/duplicity", line 1540, in with_tempdir
fn()
File "/usr/bin/duplicity", line 1391, in main
do_backup(action)
File "/usr/bin/duplicity", line 1468, in do_backup
restore(col_stats)
File "/usr/bin/duplicity", line 731, in restore
restore_get_patched_rop_iter(col_stats)):
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 560, in
Write_ROPaths
for ropath in rop_iter:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 523, in
integrate_patch_iters
for patch_seq in collated:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 389, in
yield_tuples
setrorps(overflow, elems)
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 378, in
setrorps
elems[i] = iter_list[i].next()
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 107, in
filter_path_iter
for path in path_iter:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 121, in
difftar2path_iter
tarinfo_list = [tar_iter.next()]
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 339, in
next
self.set_tarfile()
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 333, in
set_tarfile
self.current_fp = self.fileobj_iter.next()
File "/usr/bin/duplicity", line 768, in get_fileobj_iter
manifest.volume_info_dict[vol_num])
File "/usr/bin/duplicity", line 811, in restore_get_enc_fileobj
fileobj = tdp.filtered_open_with_delete("rb")
File "/usr/lib/python2.7/dist-packages/duplicity/dup_temp.py", line 119, in
filtered_open_with_delete
fh = FileobjHooked(path.DupPath.filtered_open(self, mode))
File "/usr/lib/python2.7/dist-packages/duplicity/path.py", line 778, in
filtered_open
return gpg.GPGFile(False, self, gpg_profile)
File "/usr/lib/python2.7/dist-packages/duplicity/gpg.py", line 202, in
__init__
'logger': self.logger_fp})
File "/usr/lib/python2.7/dist-packages/duplicity/gpginterface.py", line
374, in run
create_fhs, attach_fhs)
File "/usr/lib/python2.7/dist-packages/duplicity/gpginterface.py", line
420, in _attach_fork_exec
process.thread.start()
File "/usr/lib/python2.7/threading.py", line 736, in start
_start_new_thread(self.__bootstrap, ())
error: can't start new thread
--
Restarting deja-dup manually fixes the problem and the next few days,
automatic backup will run correctly until (see above).
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: duplicity 0.7.12-1ubuntu1
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
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Oct 26 10:49:45 2017
InstallationDate: Installed on 2017-10-20 (5 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
SourcePackage: duplicity
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/1727653/+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 1727653] Re: duplicity fails with unknown error
Please read my comment again:
Only when autostarted the error occurs. When launched manually (the
memory situation is the same) it works.
And: I have 16 GB RAM on this machine. I think there will be some
contiguous memory available.
--
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/1727653
Title:
duplicity fails with unknown error
Status in duplicity package in Ubuntu:
In Progress
Bug description:
$ uname -a
Linux mbpr13b 4.13.0-16-generic #19-Ubuntu SMP Wed Oct 11 18:35:14 UTC 2017
x86_64 x86_64 x86_64 GNU/Linux
duplicity gets started daily via deja-dup automatically.
Every now and then (approx. every third time) I get the following
error:
--
Failed with an unknown error.
Traceback (most recent call last):
File "/usr/bin/duplicity", line 1546, in
with_tempdir(main)
File "/usr/bin/duplicity", line 1540, in with_tempdir
fn()
File "/usr/bin/duplicity", line 1391, in main
do_backup(action)
File "/usr/bin/duplicity", line 1468, in do_backup
restore(col_stats)
File "/usr/bin/duplicity", line 731, in restore
restore_get_patched_rop_iter(col_stats)):
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 560, in
Write_ROPaths
for ropath in rop_iter:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 523, in
integrate_patch_iters
for patch_seq in collated:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 389, in
yield_tuples
setrorps(overflow, elems)
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 378, in
setrorps
elems[i] = iter_list[i].next()
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 107, in
filter_path_iter
for path in path_iter:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 121, in
difftar2path_iter
tarinfo_list = [tar_iter.next()]
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 339, in
next
self.set_tarfile()
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 333, in
set_tarfile
self.current_fp = self.fileobj_iter.next()
File "/usr/bin/duplicity", line 768, in get_fileobj_iter
manifest.volume_info_dict[vol_num])
File "/usr/bin/duplicity", line 811, in restore_get_enc_fileobj
fileobj = tdp.filtered_open_with_delete("rb")
File "/usr/lib/python2.7/dist-packages/duplicity/dup_temp.py", line 119, in
filtered_open_with_delete
fh = FileobjHooked(path.DupPath.filtered_open(self, mode))
File "/usr/lib/python2.7/dist-packages/duplicity/path.py", line 778, in
filtered_open
return gpg.GPGFile(False, self, gpg_profile)
File "/usr/lib/python2.7/dist-packages/duplicity/gpg.py", line 202, in
__init__
'logger': self.logger_fp})
File "/usr/lib/python2.7/dist-packages/duplicity/gpginterface.py", line
374, in run
create_fhs, attach_fhs)
File "/usr/lib/python2.7/dist-packages/duplicity/gpginterface.py", line
420, in _attach_fork_exec
process.thread.start()
File "/usr/lib/python2.7/threading.py", line 736, in start
_start_new_thread(self.__bootstrap, ())
error: can't start new thread
--
Restarting deja-dup manually fixes the problem and the next few days,
automatic backup will run correctly until (see above).
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: duplicity 0.7.12-1ubuntu1
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
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Oct 26 10:49:45 2017
InstallationDate: Installed on 2017-10-20 (5 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
SourcePackage: duplicity
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/1727653/+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 1727653] Re: duplicity fails with unknown error
*** This bug is a duplicate of bug 1720159 ***
https://bugs.launchpad.net/bugs/1720159
I doubt this being a duplicate:
The error message differs and it only happens when deja-dup starts
automatically.
When launched manually, deja-dup and duplicity work fine.
Currently only the first automatic launch after a reboot works. Every
other attempt leads to the above mentioned 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/1727653
Title:
duplicity fails with unknown error
Status in duplicity package in Ubuntu:
New
Bug description:
$ uname -a
Linux mbpr13b 4.13.0-16-generic #19-Ubuntu SMP Wed Oct 11 18:35:14 UTC 2017
x86_64 x86_64 x86_64 GNU/Linux
duplicity gets started daily via deja-dup automatically.
Every now and then (approx. every third time) I get the following
error:
--
Failed with an unknown error.
Traceback (most recent call last):
File "/usr/bin/duplicity", line 1546, in
with_tempdir(main)
File "/usr/bin/duplicity", line 1540, in with_tempdir
fn()
File "/usr/bin/duplicity", line 1391, in main
do_backup(action)
File "/usr/bin/duplicity", line 1468, in do_backup
restore(col_stats)
File "/usr/bin/duplicity", line 731, in restore
restore_get_patched_rop_iter(col_stats)):
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 560, in
Write_ROPaths
for ropath in rop_iter:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 523, in
integrate_patch_iters
for patch_seq in collated:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 389, in
yield_tuples
setrorps(overflow, elems)
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 378, in
setrorps
elems[i] = iter_list[i].next()
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 107, in
filter_path_iter
for path in path_iter:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 121, in
difftar2path_iter
tarinfo_list = [tar_iter.next()]
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 339, in
next
self.set_tarfile()
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 333, in
set_tarfile
self.current_fp = self.fileobj_iter.next()
File "/usr/bin/duplicity", line 768, in get_fileobj_iter
manifest.volume_info_dict[vol_num])
File "/usr/bin/duplicity", line 811, in restore_get_enc_fileobj
fileobj = tdp.filtered_open_with_delete("rb")
File "/usr/lib/python2.7/dist-packages/duplicity/dup_temp.py", line 119, in
filtered_open_with_delete
fh = FileobjHooked(path.DupPath.filtered_open(self, mode))
File "/usr/lib/python2.7/dist-packages/duplicity/path.py", line 778, in
filtered_open
return gpg.GPGFile(False, self, gpg_profile)
File "/usr/lib/python2.7/dist-packages/duplicity/gpg.py", line 202, in
__init__
'logger': self.logger_fp})
File "/usr/lib/python2.7/dist-packages/duplicity/gpginterface.py", line
374, in run
create_fhs, attach_fhs)
File "/usr/lib/python2.7/dist-packages/duplicity/gpginterface.py", line
420, in _attach_fork_exec
process.thread.start()
File "/usr/lib/python2.7/threading.py", line 736, in start
_start_new_thread(self.__bootstrap, ())
error: can't start new thread
--
Restarting deja-dup manually fixes the problem and the next few days,
automatic backup will run correctly until (see above).
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: duplicity 0.7.12-1ubuntu1
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
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Oct 26 10:49:45 2017
InstallationDate: Installed on 2017-10-20 (5 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
SourcePackage: duplicity
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/1727653/+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 1727653] [NEW] duplicity fails with unknown error
Public bug reported:
$ uname -a
Linux mbpr13b 4.13.0-16-generic #19-Ubuntu SMP Wed Oct 11 18:35:14 UTC 2017
x86_64 x86_64 x86_64 GNU/Linux
duplicity gets started daily via deja-dup automatically.
Every now and then (approx. every third time) I get the following error:
--
Failed with an unknown error.
Traceback (most recent call last):
File "/usr/bin/duplicity", line 1546, in
with_tempdir(main)
File "/usr/bin/duplicity", line 1540, in with_tempdir
fn()
File "/usr/bin/duplicity", line 1391, in main
do_backup(action)
File "/usr/bin/duplicity", line 1468, in do_backup
restore(col_stats)
File "/usr/bin/duplicity", line 731, in restore
restore_get_patched_rop_iter(col_stats)):
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 560, in
Write_ROPaths
for ropath in rop_iter:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 523, in
integrate_patch_iters
for patch_seq in collated:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 389, in
yield_tuples
setrorps(overflow, elems)
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 378, in
setrorps
elems[i] = iter_list[i].next()
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 107, in
filter_path_iter
for path in path_iter:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 121, in
difftar2path_iter
tarinfo_list = [tar_iter.next()]
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 339, in
next
self.set_tarfile()
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 333, in
set_tarfile
self.current_fp = self.fileobj_iter.next()
File "/usr/bin/duplicity", line 768, in get_fileobj_iter
manifest.volume_info_dict[vol_num])
File "/usr/bin/duplicity", line 811, in restore_get_enc_fileobj
fileobj = tdp.filtered_open_with_delete("rb")
File "/usr/lib/python2.7/dist-packages/duplicity/dup_temp.py", line 119, in
filtered_open_with_delete
fh = FileobjHooked(path.DupPath.filtered_open(self, mode))
File "/usr/lib/python2.7/dist-packages/duplicity/path.py", line 778, in
filtered_open
return gpg.GPGFile(False, self, gpg_profile)
File "/usr/lib/python2.7/dist-packages/duplicity/gpg.py", line 202, in
__init__
'logger': self.logger_fp})
File "/usr/lib/python2.7/dist-packages/duplicity/gpginterface.py", line 374,
in run
create_fhs, attach_fhs)
File "/usr/lib/python2.7/dist-packages/duplicity/gpginterface.py", line 420,
in _attach_fork_exec
process.thread.start()
File "/usr/lib/python2.7/threading.py", line 736, in start
_start_new_thread(self.__bootstrap, ())
error: can't start new thread
--
Restarting deja-dup manually fixes the problem and the next few days,
automatic backup will run correctly until (see above).
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: duplicity 0.7.12-1ubuntu1
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
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Oct 26 10:49:45 2017
InstallationDate: Installed on 2017-10-20 (5 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
SourcePackage: duplicity
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: duplicity (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug artful wayland-session
--
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/1727653
Title:
duplicity fails with unknown error
Status in duplicity package in Ubuntu:
New
Bug description:
$ uname -a
Linux mbpr13b 4.13.0-16-generic #19-Ubuntu SMP Wed Oct 11 18:35:14 UTC 2017
x86_64 x86_64 x86_64 GNU/Linux
duplicity gets started daily via deja-dup automatically.
Every now and then (approx. every third time) I get the following
error:
--
Failed with an unknown error.
Traceback (most recent call last):
File "/usr/bin/duplicity", line 1546, in
with_tempdir(main)
File "/usr/bin/duplicity", line 1540, in with_tempdir
fn()
File "/usr/bin/duplicity", line 1391, in main
do_backup(action)
File "/usr/bin/duplicity", line 1468, in do_backup
restore(col_stats)
File "/usr/bin/duplicity", line 731, in restore
restore_get_patched_rop_iter(col_stats)):
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 560, in
Write_ROPaths
for ropath in rop_iter:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 523, in
integrate_patch_iters
for patch_seq in collated:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 389, in
yield_tuples
setrorps(overflow, elems)
File
[Desktop-packages] [Bug 1715582] Re: "Operation not supported by backend" when backing up to smb server
:-) agree -- 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/1715582 Title: "Operation not supported by backend" when backing up to smb server Status in deja-dup package in Ubuntu: Confirmed Bug description: OS: Ubuntu 17.10 beta setting up deja-dup to backup to smb/ssh server fails With ssh: Permission denied syslog: Sep 7 10:30:05 mbpr13b deja-dup[30252]: Allocating size to AssistantBackup 0x55d581f75f50 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Sep 7 10:30:05 mbpr13b PackageKit: resolve transaction /149_caabebdc from uid 1000 finished with success after 414ms with smb: Backup failed InvalidBackendURL: missing // - relative paths not supported for scheme gio+invalid: gio+invalid:// syslog: Sep 7 10:32:45 mbpr13b deja-dup[30252]: Allocating size to AssistantBackup 0x55d581fecb70 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Sep 7 10:32:45 mbpr13b PackageKit: resolve transaction /150_abaacaad from uid 1000 finished with success after 402ms ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: deja-dup 35.6-0ubuntu1 ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10 Uname: Linux 4.12.0-13-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Sep 7 10:30:37 2017 InstallationDate: Installed on 2017-09-05 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902) 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/1715582/+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 1715582] Re: "Operation not supported by backend" when backing up to smb server
I installed smbclient (which is not installed by default) and tested the connection. Worked fine. Then I applied the connection string to deja-dup. Selected drop-down Network Server Server address: smb://10.1.0.4/nethome Folder: /backup/mbpr13b The difference to previous tests: Entering the smb service (//server/servicename) works, entering just the server (smb://server) does not. I will attach a screenshot that demonstrates the issue (compared to previous screenshots). Maybe you want to exchange "Server Address" with "Service path" and in the help modal add "smb://gnome.org/backup_dir" as the current description and help is definitely missleading. ** Attachment added: "Screenshot from 2017-10-19 12-09-27.png" https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1715582/+attachment/4975691/+files/Screenshot%20from%202017-10-19%2012-09-27.png -- 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/1715582 Title: "Operation not supported by backend" when backing up to smb server Status in deja-dup package in Ubuntu: New Bug description: OS: Ubuntu 17.10 beta setting up deja-dup to backup to smb/ssh server fails With ssh: Permission denied syslog: Sep 7 10:30:05 mbpr13b deja-dup[30252]: Allocating size to AssistantBackup 0x55d581f75f50 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Sep 7 10:30:05 mbpr13b PackageKit: resolve transaction /149_caabebdc from uid 1000 finished with success after 414ms with smb: Backup failed InvalidBackendURL: missing // - relative paths not supported for scheme gio+invalid: gio+invalid:// syslog: Sep 7 10:32:45 mbpr13b deja-dup[30252]: Allocating size to AssistantBackup 0x55d581fecb70 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Sep 7 10:32:45 mbpr13b PackageKit: resolve transaction /150_abaacaad from uid 1000 finished with success after 402ms ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: deja-dup 35.6-0ubuntu1 ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10 Uname: Linux 4.12.0-13-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Sep 7 10:30:37 2017 InstallationDate: Installed on 2017-09-05 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902) 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/1715582/+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 1723750] [NEW] firefox 56 overrides printer settings
Public bug reported: When trying to print a webpage > 1 paper pages firefox refuses to print duplex. Default printer settings set to duplex. Printer settings set to duplex Pages printed single page. In Chromium the pages get printed duplex correctly. So: Firefox overrides system-wide and software settings. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: firefox 56.0+build6-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: wolf 1428 F pulseaudio /dev/snd/controlC0: wolf 1428 F pulseaudio BuildID: 20171003222101 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Sun Oct 15 16:56:39 2017 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2017-09-05 (40 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902) IpRoute: default via 10.1.0.254 dev wlp3s0 proto static metric 600 10.0.0.0/8 dev wlp3s0 proto kernel scope link src 10.1.0.155 metric 600 169.254.0.0/16 dev wlp3s0 scope link metric 1000 Locales: extensions.sqlite corrupt or missing PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=56.0/20171003222101 (In use) RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2017 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP121.88Z.0171.B00.1708080033 dmi.board.name: Mac-E43C1C25D4880AD6 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro12,1 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-E43C1C25D4880AD6 dmi.modalias: dmi:bvnAppleInc.:bvrMBP121.88Z.0171.B00.1708080033:bd08/08/2017:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro12,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1723750 Title: firefox 56 overrides printer settings Status in firefox package in Ubuntu: New Bug description: When trying to print a webpage > 1 paper pages firefox refuses to print duplex. Default printer settings set to duplex. Printer settings set to duplex Pages printed single page. In Chromium the pages get printed duplex correctly. So: Firefox overrides system-wide and software settings. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: firefox 56.0+build6-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: wolf 1428 F pulseaudio /dev/snd/controlC0: wolf 1428 F pulseaudio BuildID: 20171003222101 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Sun Oct 15 16:56:39 2017 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2017-09-05 (40 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902) IpRoute: default via 10.1.0.254 dev wlp3s0 proto static metric 600 10.0.0.0/8 dev wlp3s0 proto kernel scope link src 10.1.0.155 metric 600 169.254.0.0/16 dev wlp3s0 scope link metric 1000 Locales: extensions.sqlite corrupt or missing PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=56.0/20171003222101 (In use) RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2017 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP121.88Z.0171.B00.1708080033 dmi.board.name: Mac-E43C1C25D4880AD6 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro12,1 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-E43C1C25D4880AD6 dmi.modalias:
[Desktop-packages] [Bug 1722455] [NEW] Creation of mail/contact/calendar accounts impossible
Public bug reported: If one wants to use Gnome Calendar or Gnome Contacts one has to create accounts to access the server. Gnome control centre provides prepared account templates for common public providers. There is an IMAP template that is broken (does not allow to connect to inhouse mail servers). Also adding Calendar or Contact connection is not possible. In Gnome Calendar adding new calendars is impossible (there is a workaround by temporarily installing California but that is very unstable). There needs to be a way to install DAV connectors to CALDav and CARDDav as is possible in Thunderbird. Possible workaround (which is not stable): Under ~/.config/evolution one can add a text file containing the configuration to the required service. As there is no refresh function in Calendar or Contacts, this is a fragile solution though (requires constant session creation aka logout/login) ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-control-center 1:3.26.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4 Uname: Linux 4.13.0-15-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 10 08:11:26 2017 InstallationDate: Installed on 2017-09-05 (34 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful wayland-session -- 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/1722455 Title: Creation of mail/contact/calendar accounts impossible Status in gnome-control-center package in Ubuntu: New Bug description: If one wants to use Gnome Calendar or Gnome Contacts one has to create accounts to access the server. Gnome control centre provides prepared account templates for common public providers. There is an IMAP template that is broken (does not allow to connect to inhouse mail servers). Also adding Calendar or Contact connection is not possible. In Gnome Calendar adding new calendars is impossible (there is a workaround by temporarily installing California but that is very unstable). There needs to be a way to install DAV connectors to CALDav and CARDDav as is possible in Thunderbird. Possible workaround (which is not stable): Under ~/.config/evolution one can add a text file containing the configuration to the required service. As there is no refresh function in Calendar or Contacts, this is a fragile solution though (requires constant session creation aka logout/login) ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-control-center 1:3.26.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4 Uname: Linux 4.13.0-15-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 10 08:11:26 2017 InstallationDate: Installed on 2017-09-05 (34 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1722455/+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 1722182] [NEW] Cannot connect Android phone to Ubuntu 17.10
Public bug reported: $ uname -a Linux mbpr13b 4.13.0-15-generic #16-Ubuntu SMP Wed Oct 4 21:59:25 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux libmtp9 1.1.13-1 installed Attaching Android phone brings up the Android mounted notification, shows the icon on the desktop but selecting the phone in Nautilus does not work (no files shown). => cant read/write files to/from Anddroid phones syslog gets flooded with these messages: ... Oct 9 10:37:38 mbpr13b gvfsd[18269]: Android device detected, assigning default bug flags Oct 9 10:37:38 mbpr13b kernel: [19068.065076] usb 1-1: new high-speed USB device number 93 using xhci_hcd Oct 9 10:37:38 mbpr13b kernel: [19068.449126] usb 1-1: new high-speed USB device number 94 using xhci_hcd Oct 9 10:37:39 mbpr13b kernel: [19068.590300] usb 1-1: New USB device found, idVendor=2a47, idProduct=7f10 Oct 9 10:37:39 mbpr13b kernel: [19068.590304] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Oct 9 10:37:39 mbpr13b kernel: [19068.590306] usb 1-1: Product: Aquaris X5 Plus Oct 9 10:37:39 mbpr13b kernel: [19068.590308] usb 1-1: Manufacturer: bq Oct 9 10:37:39 mbpr13b kernel: [19068.590309] usb 1-1: SerialNumber: XM020064 Oct 9 10:37:39 mbpr13b gvfs-gphoto2-vo[18365]: device (null) has no BUSNUM property, ignoring Oct 9 10:37:39 mbpr13b gvfsd[18269]: Device 0 (VID=2a47 and PID=7f10) is a bq Aquarius E5-4G. Oct 9 10:37:39 mbpr13b kernel: [19068.680431] usb 1-1: USB disconnect, device number 94 Oct 9 10:37:39 mbpr13b gvfsd[18269]: LIBMTP PANIC: could not inspect object property descriptions! Oct 9 10:37:39 mbpr13b gvfsd[18269]: message repeated 25 times: [ LIBMTP PANIC: could not inspect object property descriptions!] Oct 9 10:37:39 mbpr13b gvfsd[18269]: Error 7: Unable to read Maximum Battery Level for this device even though the device supposedly supports this functionality Oct 9 10:37:39 mbpr13b gvfsd[18269]: Error 1: Get Storage information failed. Oct 9 10:37:39 mbpr13b gnome-shell[18263]: invalid cast from 'GTask' to 'GSimpleAsyncResult' Oct 9 10:37:39 mbpr13b gnome-shell[18263]: g_simple_async_result_propagate_error: assertion 'G_IS_SIMPLE_ASYNC_RESULT (simple)' failed Oct 9 10:37:39 mbpr13b gvfsd[18269]: Android device detected, assigning default bug flags Oct 9 10:37:39 mbpr13b kernel: [19069.053047] usb 1-1: new high-speed USB device number 95 using xhci_hcd Oct 9 10:37:39 mbpr13b kernel: [19069.195211] usb 1-1: New USB device found, idVendor=2a47, idProduct=7f10 Oct 9 10:37:39 mbpr13b kernel: [19069.195216] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Oct 9 10:37:39 mbpr13b kernel: [19069.195218] usb 1-1: Product: Aquaris X5 Plus Oct 9 10:37:39 mbpr13b kernel: [19069.195221] usb 1-1: Manufacturer: bq Oct 9 10:37:39 mbpr13b kernel: [19069.195222] usb 1-1: SerialNumber: XM020064 Oct 9 10:37:39 mbpr13b gvfs-gphoto2-vo[18365]: device (null) has no BUSNUM property, ignoring Oct 9 10:37:39 mbpr13b gvfsd[18269]: Device 0 (VID=2a47 and PID=7f10) is a bq Aquarius E5-4G. Oct 9 10:37:39 mbpr13b kernel: [19069.293253] xhci_hcd :00:14.0: WARN Event TRB for slot 8 ep 1 with no TDs queued? Oct 9 10:37:39 mbpr13b gvfsd[18269]: LIBMTP PANIC: could not inspect object property descriptions! Oct 9 10:37:39 mbpr13b kernel: [19069.293359] usb 1-1: USB disconnect, device number 95 Oct 9 10:37:39 mbpr13b kernel: [19069.293468] xhci_hcd :00:14.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state. Oct 9 10:37:39 mbpr13b gvfsd[18269]: message repeated 25 times: [ LIBMTP PANIC: could not inspect object property descriptions!] Oct 9 10:37:39 mbpr13b gvfsd[18269]: Error 7: Unable to read Maximum Battery Level for this device even though the device supposedly supports this functionality Oct 9 10:37:39 mbpr13b gvfsd[18269]: Error 1: Get Storage information failed. Oct 9 10:37:39 mbpr13b gnome-shell[18263]: invalid cast from 'GTask' to 'GSimpleAsyncResult' Oct 9 10:37:39 mbpr13b gnome-shell[18263]: g_simple_async_result_propagate_error: assertion 'G_IS_SIMPLE_ASYNC_RESULT (simple)' failed Oct 9 10:37:40 mbpr13b kernel: [19069.633015] usb 1-1: new high-speed USB device number 96 using xhci_hcd Oct 9 10:37:40 mbpr13b kernel: [19069.775904] usb 1-1: New USB device found, idVendor=2a47, idProduct=7f10 Oct 9 10:37:40 mbpr13b kernel: [19069.775910] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Oct 9 10:37:40 mbpr13b kernel: [19069.775913] usb 1-1: Product: Aquaris X5 Plus Oct 9 10:37:40 mbpr13b kernel: [19069.775915] usb 1-1: Manufacturer: bq Oct 9 10:37:40 mbpr13b kernel: [19069.775917] usb 1-1: SerialNumber: XM020064 Oct 9 10:37:40 mbpr13b gvfs-gphoto2-vo[18365]: device (null) has no BUSNUM property, ignoring Oct 9 10:37:40 mbpr13b gvfsd[18269]: Device 0 (VID=2a47 and PID=7f10) is a bq Aquarius E5-4G. Oct 9 10:37:40 mbpr13b gvfsd[18269]: LIBMTP PANIC: could not inspect object property descriptions! Oct 9 10:37:40 mbpr13b kernel: [19069.873566]
[Desktop-packages] [Bug 1721189] Re: Thunderbird 1:52.4.0+build1-0ubuntu1 broken user interface
thunderbird 1:52.4.0+build1-0ubuntu2 works fine again -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1721189 Title: Thunderbird 1:52.4.0+build1-0ubuntu1 broken user interface Status in thunderbird package in Ubuntu: Fix Released Bug description: Just received the update 1:52.4.0+build1-0ubuntu1 which has a broken user interface. See attached screenshot. Downgraded to thunderbird_52.3.0+build1-0ubuntu0.17.04.1_amd64.deb which solved the problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1721189/+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 1721189] Re: Thunderbird 1:52.4.0+build1-0ubuntu1 broken user interface
Have to confirm under: Linux mbpr13b 4.13.0-12-generic #13-Ubuntu SMP Sat Sep 23 03:40:16 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux ** Attachment added: "Thunderbird 52.4" https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1721189/+attachment/4961948/+files/Screenshot%20from%202017-10-04%2011-39-16.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1721189 Title: Thunderbird 1:52.4.0+build1-0ubuntu1 broken user interface Status in thunderbird package in Ubuntu: Confirmed Bug description: Just received the update 1:52.4.0+build1-0ubuntu1 which has a broken user interface. See attached screenshot. Downgraded to thunderbird_52.3.0+build1-0ubuntu0.17.04.1_amd64.deb which solved the problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1721189/+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 1715582] Re: "Operation not supported by backend" when backing up to smb server
Uups, I just saw that deja-dup is written in Vala. I fear, I will not be of much help there. -- 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/1715582 Title: "Operation not supported by backend" when backing up to smb server Status in deja-dup package in Ubuntu: New Bug description: OS: Ubuntu 17.10 beta setting up deja-dup to backup to smb/ssh server fails With ssh: Permission denied syslog: Sep 7 10:30:05 mbpr13b deja-dup[30252]: Allocating size to AssistantBackup 0x55d581f75f50 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Sep 7 10:30:05 mbpr13b PackageKit: resolve transaction /149_caabebdc from uid 1000 finished with success after 414ms with smb: Backup failed InvalidBackendURL: missing // - relative paths not supported for scheme gio+invalid: gio+invalid:// syslog: Sep 7 10:32:45 mbpr13b deja-dup[30252]: Allocating size to AssistantBackup 0x55d581fecb70 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Sep 7 10:32:45 mbpr13b PackageKit: resolve transaction /150_abaacaad from uid 1000 finished with success after 402ms ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: deja-dup 35.6-0ubuntu1 ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10 Uname: Linux 4.12.0-13-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Sep 7 10:30:37 2017 InstallationDate: Installed on 2017-09-05 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902) 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/1715582/+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 1715582] Re: "Operation not supported by backend" when backing up to smb server
** Attachment added: "Config in 36.2." https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1715582/+attachment/4961947/+files/Screenshot%20from%202017-10-04%2011-49-06.png -- 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/1715582 Title: "Operation not supported by backend" when backing up to smb server Status in deja-dup package in Ubuntu: New Bug description: OS: Ubuntu 17.10 beta setting up deja-dup to backup to smb/ssh server fails With ssh: Permission denied syslog: Sep 7 10:30:05 mbpr13b deja-dup[30252]: Allocating size to AssistantBackup 0x55d581f75f50 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Sep 7 10:30:05 mbpr13b PackageKit: resolve transaction /149_caabebdc from uid 1000 finished with success after 414ms with smb: Backup failed InvalidBackendURL: missing // - relative paths not supported for scheme gio+invalid: gio+invalid:// syslog: Sep 7 10:32:45 mbpr13b deja-dup[30252]: Allocating size to AssistantBackup 0x55d581fecb70 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Sep 7 10:32:45 mbpr13b PackageKit: resolve transaction /150_abaacaad from uid 1000 finished with success after 402ms ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: deja-dup 35.6-0ubuntu1 ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10 Uname: Linux 4.12.0-13-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Sep 7 10:30:37 2017 InstallationDate: Installed on 2017-09-05 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902) 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/1715582/+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 1715582] Re: "Operation not supported by backend" when backing up to smb server
There is no difference whether I prepend a / in front of nethome. I always get "Operation not allowed" -- 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/1715582 Title: "Operation not supported by backend" when backing up to smb server Status in deja-dup package in Ubuntu: New Bug description: OS: Ubuntu 17.10 beta setting up deja-dup to backup to smb/ssh server fails With ssh: Permission denied syslog: Sep 7 10:30:05 mbpr13b deja-dup[30252]: Allocating size to AssistantBackup 0x55d581f75f50 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Sep 7 10:30:05 mbpr13b PackageKit: resolve transaction /149_caabebdc from uid 1000 finished with success after 414ms with smb: Backup failed InvalidBackendURL: missing // - relative paths not supported for scheme gio+invalid: gio+invalid:// syslog: Sep 7 10:32:45 mbpr13b deja-dup[30252]: Allocating size to AssistantBackup 0x55d581fecb70 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Sep 7 10:32:45 mbpr13b PackageKit: resolve transaction /150_abaacaad from uid 1000 finished with success after 402ms ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: deja-dup 35.6-0ubuntu1 ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10 Uname: Linux 4.12.0-13-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Sep 7 10:30:37 2017 InstallationDate: Installed on 2017-09-05 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902) 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/1715582/+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 1715582] Re: "Operation not supported by backend" when backing up to smb server
** Attachment added: "Storage config in 34.4." https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1715582/+attachment/4961946/+files/Screenshot%20from%202017-10-04%2011-43-19.png -- 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/1715582 Title: "Operation not supported by backend" when backing up to smb server Status in deja-dup package in Ubuntu: New Bug description: OS: Ubuntu 17.10 beta setting up deja-dup to backup to smb/ssh server fails With ssh: Permission denied syslog: Sep 7 10:30:05 mbpr13b deja-dup[30252]: Allocating size to AssistantBackup 0x55d581f75f50 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Sep 7 10:30:05 mbpr13b PackageKit: resolve transaction /149_caabebdc from uid 1000 finished with success after 414ms with smb: Backup failed InvalidBackendURL: missing // - relative paths not supported for scheme gio+invalid: gio+invalid:// syslog: Sep 7 10:32:45 mbpr13b deja-dup[30252]: Allocating size to AssistantBackup 0x55d581fecb70 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Sep 7 10:32:45 mbpr13b PackageKit: resolve transaction /150_abaacaad from uid 1000 finished with success after 402ms ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: deja-dup 35.6-0ubuntu1 ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10 Uname: Linux 4.12.0-13-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Sep 7 10:30:37 2017 InstallationDate: Installed on 2017-09-05 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902) 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/1715582/+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 1715582] Re: "Operation not supported by backend" when backing up to smb server
I have no issues connecting to the share from Nautilus. The code in 34.4 worked flawless and reliably In 34.4. the protocol was set using a dropdown and the server entered alone (see screenshots) In 36.2 one has to enter the protocol and server but the path in a different location (see screenshots). I have tried a simple Python script to connect to my server and it works fine (so I don't think it is an issue with Gnome but rather an issue in the new selection box). Today the gnome gvfs package came in updated. The issue still persists. If you want I can have a look at the source code and see if I can be of assistance. Currently after every upgrade I revert to 34.4 as the last working solution. -- 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/1715582 Title: "Operation not supported by backend" when backing up to smb server Status in deja-dup package in Ubuntu: New Bug description: OS: Ubuntu 17.10 beta setting up deja-dup to backup to smb/ssh server fails With ssh: Permission denied syslog: Sep 7 10:30:05 mbpr13b deja-dup[30252]: Allocating size to AssistantBackup 0x55d581f75f50 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Sep 7 10:30:05 mbpr13b PackageKit: resolve transaction /149_caabebdc from uid 1000 finished with success after 414ms with smb: Backup failed InvalidBackendURL: missing // - relative paths not supported for scheme gio+invalid: gio+invalid:// syslog: Sep 7 10:32:45 mbpr13b deja-dup[30252]: Allocating size to AssistantBackup 0x55d581fecb70 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Sep 7 10:32:45 mbpr13b PackageKit: resolve transaction /150_abaacaad from uid 1000 finished with success after 402ms ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: deja-dup 35.6-0ubuntu1 ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10 Uname: Linux 4.12.0-13-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Sep 7 10:30:37 2017 InstallationDate: Installed on 2017-09-05 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902) 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/1715582/+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 1715582] Re: "Operation not supported by backend" when backing up to smb server
Today update to deja-dup:amd64 (36.2-0ubuntu1) was offered. Issue with gvfs still exists. I am questioning whether I set up the backup path incorrectly: server: "smb://server/" path: "/absolute/path/to/backup" is this correct? (I tried every possible combination though) -- 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/1715582 Title: "Operation not supported by backend" when backing up to smb server Status in deja-dup package in Ubuntu: New Bug description: OS: Ubuntu 17.10 beta setting up deja-dup to backup to smb/ssh server fails With ssh: Permission denied syslog: Sep 7 10:30:05 mbpr13b deja-dup[30252]: Allocating size to AssistantBackup 0x55d581f75f50 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Sep 7 10:30:05 mbpr13b PackageKit: resolve transaction /149_caabebdc from uid 1000 finished with success after 414ms with smb: Backup failed InvalidBackendURL: missing // - relative paths not supported for scheme gio+invalid: gio+invalid:// syslog: Sep 7 10:32:45 mbpr13b deja-dup[30252]: Allocating size to AssistantBackup 0x55d581fecb70 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Sep 7 10:32:45 mbpr13b PackageKit: resolve transaction /150_abaacaad from uid 1000 finished with success after 402ms ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: deja-dup 35.6-0ubuntu1 ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10 Uname: Linux 4.12.0-13-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Sep 7 10:30:37 2017 InstallationDate: Installed on 2017-09-05 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902) 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/1715582/+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 1715582] Re: "Operation not supported by backend" when backing up to smb server
Just as a hint: maybe you want to remove the new code for storage location and replace it with the old working one. -- 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/1715582 Title: "Operation not supported by backend" when backing up to smb server Status in deja-dup package in Ubuntu: New Bug description: OS: Ubuntu 17.10 beta setting up deja-dup to backup to smb/ssh server fails With ssh: Permission denied syslog: Sep 7 10:30:05 mbpr13b deja-dup[30252]: Allocating size to AssistantBackup 0x55d581f75f50 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Sep 7 10:30:05 mbpr13b PackageKit: resolve transaction /149_caabebdc from uid 1000 finished with success after 414ms with smb: Backup failed InvalidBackendURL: missing // - relative paths not supported for scheme gio+invalid: gio+invalid:// syslog: Sep 7 10:32:45 mbpr13b deja-dup[30252]: Allocating size to AssistantBackup 0x55d581fecb70 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Sep 7 10:32:45 mbpr13b PackageKit: resolve transaction /150_abaacaad from uid 1000 finished with success after 402ms ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: deja-dup 35.6-0ubuntu1 ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10 Uname: Linux 4.12.0-13-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Sep 7 10:30:37 2017 InstallationDate: Installed on 2017-09-05 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902) 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/1715582/+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 1715582] Re: "Operation not supported by backend" when backing up to smb server
I tried to monitor via jouralctl -f
first attempts suggest that the application can't create a directory
/var/cache/samba
I added write access to /var/cache for world.
Then I got this
Sep 23 14:05:35 mbpr13b dbus-daemon[2751]: Activating service
name='org.gnome.DejaDup'
Sep 23 14:05:35 mbpr13b dbus-daemon[2751]: Successfully activated service
'org.gnome.DejaDup'
Sep 23 14:05:37 mbpr13b PackageKit[1129]: resolve transaction /511_eccbbeed
from uid 1000 finished with success after 394ms
Sep 23 14:05:37 mbpr13b deja-dup[4000]: BackendRemote.vala:83: Could not find
enclosing mount
Sep 23 14:05:37 mbpr13b deja-dup[4000]: BackendRemote.vala:83: Could not find
enclosing mount
Mounting the directory manually
Sep 23 14:08:18 mbpr13b dbus-daemon[2751]: Activating service
name='org.gnome.Nautilus'
Sep 23 14:08:18 mbpr13b dbus-daemon[2751]: Successfully activated service
'org.gnome.Nautilus'
Sep 23 14:08:18 mbpr13b org.gnome.Nautilus[2751]: sys:1: PyGIWarning: Nautilus
was imported without specifying a version first. Use
gi.require_version('Nautilus', '3.0') before import to ensure that the right
version gets loaded.
Sep 23 14:08:18 mbpr13b dbus[891]: [system] Activating via systemd: service
name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service'
Sep 23 14:08:18 mbpr13b systemd[1]: Starting Hostname Service...
Sep 23 14:08:18 mbpr13b nautilus[4157]: Called "net usershare info" but it
failed: Failed to execute child process “net” (No such file or directory)
Sep 23 14:08:18 mbpr13b dbus[891]: [system] Successfully activated service
'org.freedesktop.hostname1'
Sep 23 14:08:18 mbpr13b systemd[1]: Started Hostname Service.
Sep 23 14:08:20 mbpr13b gvfsd[2791]: mkdir failed on directory
/var/cache/samba: Permission denied
Sep 23 14:08:20 mbpr13b gvfsd[2791]: mkdir failed on directory
/var/cache/samba: Permission denied
Sep 23 14:08:20 mbpr13b gvfsd[2791]: mkdir failed on directory
/var/cache/samba: Permission denied
Sep 23 14:08:20 mbpr13b gvfsd[2791]: mkdir failed on directory
/var/cache/samba: Permission denied
The mount works though.
Sep 23 14:10:56 mbpr13b dbus-daemon[2751]: Activating service
name='org.gnome.DejaDup'
Sep 23 14:10:56 mbpr13b dbus-daemon[2751]: Successfully activated service
'org.gnome.DejaDup'
Sep 23 14:11:00 mbpr13b PackageKit[1129]: resolve transaction /512_dedcceee
from uid 1000 finished with success after 422ms
Sep 23 14:11:00 mbpr13b deja-dup[4216]: BackendRemote.vala:83: Could not find
enclosing mount
Sep 23 14:11:00 mbpr13b deja-dup[4216]: BackendRemote.vala:83: Could not find
enclosing mount
Same issue.
Sep 23 14:15:08 mbpr13b org.gnome.Nautilus[2751]: **
Sep 23 14:15:08 mbpr13b org.gnome.Nautilus[2751]:
ERROR:../src/nautilus-bookmark.c:387:nautilus_bookmark_connect_file: assertion
failed: (!nautilus_file_is_gone (bookmark->file))
Sep 23 14:15:11 mbpr13b dbus-daemon[2751]: Activating service
name='org.gnome.Nautilus'
Sep 23 14:15:11 mbpr13b dbus-daemon[2751]: Successfully activated service
'org.gnome.Nautilus'
Sep 23 14:15:11 mbpr13b gsd-media-keys[2953]: Couldn't lock screen: Timeout was
reached
Sep 23 14:15:11 mbpr13b org.gnome.Nautilus[2751]: sys:1: PyGIWarning: Nautilus
was imported without specifying a version first. Use
gi.require_version('Nautilus', '3.0') before import to ensure that the right
version gets loaded.
Sep 23 14:15:11 mbpr13b dbus[891]: [system] Activating via systemd: service
name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service'
Sep 23 14:15:11 mbpr13b systemd[1]: Starting Hostname Service...
Sep 23 14:15:11 mbpr13b nautilus[4292]: Called "net usershare info" but it
failed: Failed to execute child process “net” (No such file or directory)
Sep 23 14:15:11 mbpr13b dbus[891]: [system] Successfully activated service
'org.freedesktop.hostname1'
Sep 23 14:15:11 mbpr13b systemd[1]: Started Hostname Service.
Sep 23 14:15:14 mbpr13b gvfsd[2791]: mkdir failed on directory /var/run/samba:
Permission denied
Sep 23 14:15:14 mbpr13b gvfsd[2791]: mkdir failed on directory /var/run/samba:
Permission denied
Sep 23 14:15:14 mbpr13b gvfsd[2791]: mkdir failed on directory /var/run/samba:
Permission denied
Sep 23 14:15:14 mbpr13b gvfsd[2791]: mkdir failed on directory /var/run/samba:
Permission denied
Sep 23 14:15:14 mbpr13b gvfsd[2791]: mkdir failed on directory /var/run/samba:
Permission denied
Sep 23 14:15:14 mbpr13b gvfsd[2791]: mkdir failed on directory /var/run/samba:
Permission denied
Tried sudo chown o+w /run
Mounting the share does not bring up any error messages any more.
Deja-dup still fails
and there are no files created in cache or run
Still: the old deja-dup from Ubuntu 17.04 works fine.
--
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/1715582
Title:
"Operation not supported by backend" when backing up to smb server
Status in deja-dup package in Ubuntu:
New
Bug
[Desktop-packages] [Bug 1711382] Re: Slow Firefox performance and high CPU load when tlp is installed
I'm not seeking advice, I report issues. I have tlp deinstalled and the symptoms are gone. If you don't need any further testing that is fine with me. Thanks for your efforts. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1711382 Title: Slow Firefox performance and high CPU load when tlp is installed Status in firefox package in Ubuntu: New Status in tlp package in Ubuntu: Invalid Bug description: After installing Firefox 55 the browser generates huge cpu load, startup is extremely slow (it takes > 10s for the taskbar to accept entries after launch (this is new to 55) Due to high cpu load the computer tends to overheat, ventilation jumps in making the machine extremely loud. Using Chromium does not show these symptoms (on the same page). --- LSB Ubuntu 17.04 (budgie desktop) firefox: Installed: 55.0.1+build2-0ubuntu0.17.04.2 Candidate: 55.0.1+build2-0ubuntu0.17.04.2 Version table: *** 55.0.1+build2-0ubuntu0.17.04.2 500 500 http://archive.ubuntu.com/ubuntu zesty-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu zesty-security/main amd64 Packages 100 /var/lib/dpkg/status 50.1.0+build2-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu zesty/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: firefox 55.0.1+build2-0ubuntu0.17.04.2 ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17 Uname: Linux 4.10.0-32-generic x86_64 NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 BuildID: 20170814193419 CurrentDesktop: Budgie:GNOME Date: Thu Aug 17 16:30:30 2017 InstallationDate: Installed on 2017-05-25 (83 days ago) InstallationMedia: Ubuntu-Budgie 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1711382/+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 1711382] Re: Slow Firefox performance and high CPU load when tlp is installed
Which Thinkpad? None. Tlp comes by default in every Ubuntu installation (even 17.10) Removing tlp allows the battery to be loaded up to 98%. On other machines up to 100% (newer system). The battery life is extended after deinstall by approx 15%. (I don't have an exact test suite though, just average work). Currently I experiment with Ubuntu 17.10. I have tlp deinstalled and a) my network is reasonable stable b) bluetooth is broken c) Firefox does not cause high CPU and fan speeds Haven't got the time to experiment with tlp. At least, it's deinstallable on its own. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1711382 Title: Slow Firefox performance and high CPU load when tlp is installed Status in firefox package in Ubuntu: New Status in tlp package in Ubuntu: New Bug description: After installing Firefox 55 the browser generates huge cpu load, startup is extremely slow (it takes > 10s for the taskbar to accept entries after launch (this is new to 55) Due to high cpu load the computer tends to overheat, ventilation jumps in making the machine extremely loud. Using Chromium does not show these symptoms (on the same page). --- LSB Ubuntu 17.04 (budgie desktop) firefox: Installed: 55.0.1+build2-0ubuntu0.17.04.2 Candidate: 55.0.1+build2-0ubuntu0.17.04.2 Version table: *** 55.0.1+build2-0ubuntu0.17.04.2 500 500 http://archive.ubuntu.com/ubuntu zesty-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu zesty-security/main amd64 Packages 100 /var/lib/dpkg/status 50.1.0+build2-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu zesty/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: firefox 55.0.1+build2-0ubuntu0.17.04.2 ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17 Uname: Linux 4.10.0-32-generic x86_64 NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 BuildID: 20170814193419 CurrentDesktop: Budgie:GNOME Date: Thu Aug 17 16:30:30 2017 InstallationDate: Installed on 2017-05-25 (83 days ago) InstallationMedia: Ubuntu-Budgie 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1711382/+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 1715582] Re: deja-dup fails to backup
Connecting from Nautilus works fine but slow -- 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/1715582 Title: deja-dup fails to backup Status in deja-dup package in Ubuntu: Fix Committed Bug description: OS: Ubuntu 17.10 beta setting up deja-dup to backup to smb/ssh server fails With ssh: Permission denied syslog: Sep 7 10:30:05 mbpr13b deja-dup[30252]: Allocating size to AssistantBackup 0x55d581f75f50 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Sep 7 10:30:05 mbpr13b PackageKit: resolve transaction /149_caabebdc from uid 1000 finished with success after 414ms with smb: Backup failed InvalidBackendURL: missing // - relative paths not supported for scheme gio+invalid: gio+invalid:// syslog: Sep 7 10:32:45 mbpr13b deja-dup[30252]: Allocating size to AssistantBackup 0x55d581fecb70 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Sep 7 10:32:45 mbpr13b PackageKit: resolve transaction /150_abaacaad from uid 1000 finished with success after 402ms ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: deja-dup 35.6-0ubuntu1 ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10 Uname: Linux 4.12.0-13-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Sep 7 10:30:37 2017 InstallationDate: Installed on 2017-09-05 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902) 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/1715582/+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 1715582] Re: deja-dup fails to backup
[global] workgroup = RSB netbios name = s4 passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword: * %n\n *password\supdated\ssuccessfully* . obey pam restrictions = Yes unix password sync = Yes invalid users = root preferred master = yes os level = 20 idmap config * : backend = tdb log file = /var/log/samba/log.%m passwd program = /usr/bin/passwd %u server string = %h server (Samba, Ubuntu) ... [nethome] comment = Network home share writable = yes path = /home/%u force directory mode = 0700 force group = users force create mode = 0700 create mode = 0700 directory mode = 0700 ; valid users = %u -- 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/1715582 Title: deja-dup fails to backup Status in deja-dup package in Ubuntu: Fix Committed Bug description: OS: Ubuntu 17.10 beta setting up deja-dup to backup to smb/ssh server fails With ssh: Permission denied syslog: Sep 7 10:30:05 mbpr13b deja-dup[30252]: Allocating size to AssistantBackup 0x55d581f75f50 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Sep 7 10:30:05 mbpr13b PackageKit: resolve transaction /149_caabebdc from uid 1000 finished with success after 414ms with smb: Backup failed InvalidBackendURL: missing // - relative paths not supported for scheme gio+invalid: gio+invalid:// syslog: Sep 7 10:32:45 mbpr13b deja-dup[30252]: Allocating size to AssistantBackup 0x55d581fecb70 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Sep 7 10:32:45 mbpr13b PackageKit: resolve transaction /150_abaacaad from uid 1000 finished with success after 402ms ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: deja-dup 35.6-0ubuntu1 ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10 Uname: Linux 4.12.0-13-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Sep 7 10:30:37 2017 InstallationDate: Installed on 2017-09-05 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902) 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/1715582/+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 1717486] Re: gnome visual issues
Figured out how to reproduce this: Appended screenshot 1 demonstrates how my favorites bar looks like normally. When scrolling down with two fingers with the mouse over the bar, the icons are gone (see screenshot 2). Icons cannot be called back by reverse scrolling with the mouse cursor in the favorites bar. Workaround: Screen-lock and unlock will bring up the fav-bar correctly. ** Attachment added: "Screenshot with fav icons in place" https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1717486/+attachment/4951676/+files/Screenshot%20from%202017-09-17%2013-12-30.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1717486 Title: gnome visual issues Status in gnome-session package in Ubuntu: New Bug description: since the upgrade of gnome-session from 3.25.90 to 3.26.0 I observe weird visual phenomena. 1. Icons in the task bar disappear (and only appear after logout/login) 2. Windows get drawn with black margins and sometimes with black canvas (gets away after a second or so) Issue can be related to upgrade of libmutter (libmutter-1-0:amd64 3.25.91+20170902~ce515c5-1ubuntu1 -> 3.26.0-1) ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-session (not installed) ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1 Uname: Linux 4.13.0-11-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Sep 15 12:33:43 2017 InstallationDate: Installed on 2017-09-05 (9 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902) SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1717486/+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 1717486] Re: gnome visual issues
** Attachment added: "Screenshot without fav icons" https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1717486/+attachment/4951677/+files/Screenshot%20from%202017-09-17%2013-14-04.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1717486 Title: gnome visual issues Status in gnome-session package in Ubuntu: New Bug description: since the upgrade of gnome-session from 3.25.90 to 3.26.0 I observe weird visual phenomena. 1. Icons in the task bar disappear (and only appear after logout/login) 2. Windows get drawn with black margins and sometimes with black canvas (gets away after a second or so) Issue can be related to upgrade of libmutter (libmutter-1-0:amd64 3.25.91+20170902~ce515c5-1ubuntu1 -> 3.26.0-1) ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-session (not installed) ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1 Uname: Linux 4.13.0-11-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Sep 15 12:33:43 2017 InstallationDate: Installed on 2017-09-05 (9 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902) SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1717486/+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 1717486] [NEW] gnome visual issues
Public bug reported: since the upgrade of gnome-session from 3.25.90 to 3.26.0 I observe weird visual phenomena. 1. Icons in the task bar disappear (and only appear after logout/login) 2. Windows get drawn with black margins and sometimes with black canvas (gets away after a second or so) Issue can be related to upgrade of libmutter (libmutter-1-0:amd64 3.25.91+20170902~ce515c5-1ubuntu1 -> 3.26.0-1) ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-session (not installed) ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1 Uname: Linux 4.13.0-11-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Sep 15 12:33:43 2017 InstallationDate: Installed on 2017-09-05 (9 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902) SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-session (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1717486 Title: gnome visual issues Status in gnome-session package in Ubuntu: New Bug description: since the upgrade of gnome-session from 3.25.90 to 3.26.0 I observe weird visual phenomena. 1. Icons in the task bar disappear (and only appear after logout/login) 2. Windows get drawn with black margins and sometimes with black canvas (gets away after a second or so) Issue can be related to upgrade of libmutter (libmutter-1-0:amd64 3.25.91+20170902~ce515c5-1ubuntu1 -> 3.26.0-1) ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-session (not installed) ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1 Uname: Linux 4.13.0-11-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Sep 15 12:33:43 2017 InstallationDate: Installed on 2017-09-05 (9 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902) SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1717486/+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 1715582] Re: deja-dup fails to backup
upgraded to deja-dup 36.1. -> Backup failed Operation not supported by backend syslog: Sep 15 12:27:23 mbpr13b deja-dup[1983]: BackendRemote.vala:83: The specified loc ation is not mounted Sep 15 12:27:23 mbpr13b gvfsd[1375]: mkdir failed on directory /var/cache/samba: Permission denied Sep 15 12:27:25 mbpr13b gvfsd[1375]: message repeated 9 times: [ mkdir failed on directory /var/cache/samba: Permission denied] Sep 15 12:27:25 mbpr13b deja-dup[1983]: BackendRemote.vala:83: Could not find enclosing mount Sep 15 12:27:25 mbpr13b dbus-daemon[1335]: Activating via systemd: service name='org.gtk.vfs.Metadata' unit='gvfs-metadata.service' Sep 15 12:27:25 mbpr13b systemd[1321]: Starting Virtual filesystem metadata service... Sep 15 12:27:25 mbpr13b dbus-daemon[1335]: Successfully activated service 'org.gtk.vfs.Metadata' -- 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/1715582 Title: deja-dup fails to backup Status in deja-dup package in Ubuntu: Fix Committed Bug description: OS: Ubuntu 17.10 beta setting up deja-dup to backup to smb/ssh server fails With ssh: Permission denied syslog: Sep 7 10:30:05 mbpr13b deja-dup[30252]: Allocating size to AssistantBackup 0x55d581f75f50 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Sep 7 10:30:05 mbpr13b PackageKit: resolve transaction /149_caabebdc from uid 1000 finished with success after 414ms with smb: Backup failed InvalidBackendURL: missing // - relative paths not supported for scheme gio+invalid: gio+invalid:// syslog: Sep 7 10:32:45 mbpr13b deja-dup[30252]: Allocating size to AssistantBackup 0x55d581fecb70 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Sep 7 10:32:45 mbpr13b PackageKit: resolve transaction /150_abaacaad from uid 1000 finished with success after 402ms ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: deja-dup 35.6-0ubuntu1 ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10 Uname: Linux 4.12.0-13-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Sep 7 10:30:37 2017 InstallationDate: Installed on 2017-09-05 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902) 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/1715582/+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
