[Desktop-packages] [Bug 1945368] Re: Thunderbird 91 forgets default calendar
Forgive me if this is not the bug in question here (I didn't read the
whole thread) but I found this issue while searching for a resolution to
a lost calendar, and I thought I would share my solution, in case anyone
else encounters the same problem.
I have an old Thunderbird installation, in which I never used the
Calendar before.
I couldn't find the Calendar anywhere, even though it should be part of
Thunderbird. I finally managed to get Calendar working, but not sure
which of these steps did it, so sharing them all:
WARNING: This will delete everything from your Calendar, so only do this
for a fresh start.
- Removed a couple of old Calendar lines from prefs.js
- Deleted all folders and files inside the /calendar-data folder
- Set Offline to "On" (wasn't set) under Edit-Preferences
- Added Calendar icon at the top (Views-Toolbars-Customize) clicked and added a
calendar
Now "Events and Tasks" are shown in the menu at the top (I am pretty
sure it was missing) and I have a working Thunderbird Calendar.
--
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/1945368
Title:
Thunderbird 91 forgets default calendar
Status in Mozilla Thunderbird:
Invalid
Status in thunderbird package in Ubuntu:
Confirmed
Bug description:
Upon upgrading from Thunderbird 78 to 91, the default calendar for new
events that I selected has been forgotten. I has Google set as the
default, but Thunderbird 91 has changed the default to a local
calendar that I rarely use.
ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: thunderbird 1:91.1.1+build2-0ubuntu1
ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
Uname: Linux 5.13.0-16-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.11-0ubuntu69
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: alistair 2076 F pulseaudio
BuildID: 20210916142849
CasperMD5CheckResult: unknown
Channel: Unavailable
CurrentDesktop: Unity:Unity7:ubuntu
Date: Tue Sep 28 22:11:42 2021
ForcedLayersAccel: False
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
# Include files from /etc/network/interfaces.d:
source-directory /etc/network/interfaces.d
IncompatibleExtensions:
Lightning - {e2fda1a4-762b-4020-b5ad-a41df1933103}
English (GB) Language Pack - langpack-en...@thunderbird.mozilla.org
Thunderbird (default) - {972ce4c6-7e08-4474-a285-3208198ce6fd}
InstallationDate: Installed on 2020-07-14 (441 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
IpRoute:
default via 172.30.3.254 dev wlp0s20f3 proto dhcp metric 600
10.0.0.0/24 dev wg0 proto kernel scope link src 10.0.0.2
169.254.0.0/16 dev wg0 scope link metric 1000
172.30.0.0/22 dev wlp0s20f3 proto kernel scope link src 172.30.0.92 metric
600
PrefErrors: Unexpected character ',' before close parenthesis @
/usr/lib/thunderbird/omni.ja:greprefs.js:359
PrefSources: prefs.js
Profiles: Profile0 (Default) - LastVersion=91.1.1/20210916142849 (In use)
RunningIncompatibleAddons: True
SourcePackage: thunderbird
UpgradeStatus: Upgraded to impish on 2021-09-24 (4 days ago)
dmi.bios.date: 06/21/2021
dmi.bios.release: 1.19
dmi.bios.vendor: LENOVO
dmi.bios.version: N2WET29W (1.19 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20U9CTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0R32862 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.8
dmi.modalias:
dmi:bvnLENOVO:bvrN2WET29W(1.19):bd06/21/2021:br1.19:efr1.8:svnLENOVO:pn20U9CTO1WW:pvrThinkPadX1CarbonGen8:skuLENOVO_MT_20U9_BU_Think_FM_ThinkPadX1CarbonGen8:rvnLENOVO:rn20U9CTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad X1 Carbon Gen 8
dmi.product.name: 20U9CTO1WW
dmi.product.sku: LENOVO_MT_20U9_BU_Think_FM_ThinkPad X1 Carbon Gen 8
dmi.product.version: ThinkPad X1 Carbon Gen 8
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/thunderbird/+bug/1945368/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1959097] [NEW] Check for updates right after boot, if Automatically check for updates: Daily is chosen
Public bug reported: If "Software & Updates" > "Updates" > "Automatically check for updates" is set to "Daily" as a user, I would expect it to check right after start up, and perhaps every third hour? Currently, you need to manually trigger a check by opening "Software Updater", for example by hitting "Super" button, type "upda ..." and select the grey "Software Updater" icon. Also, maybe a new option "Every hour" could be added for those extra security conscious? $ lsb_release -rd Description:Ubuntu 20.04.3 LTS Release:20.04 ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1959097 Title: Check for updates right after boot, if Automatically check for updates: Daily is chosen Status in software-properties package in Ubuntu: New Bug description: If "Software & Updates" > "Updates" > "Automatically check for updates" is set to "Daily" as a user, I would expect it to check right after start up, and perhaps every third hour? Currently, you need to manually trigger a check by opening "Software Updater", for example by hitting "Super" button, type "upda ..." and select the grey "Software Updater" icon. Also, maybe a new option "Every hour" could be added for those extra security conscious? $ lsb_release -rd Description: Ubuntu 20.04.3 LTS Release: 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1959097/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1632027] Re: New Document feature missing from Nautilus 3.20+
So, https://help.launchpad.net/HelpOnFormatting says that the MoinMoin wiki syntax is supported, which it is evidently not, so here's the code bit from my post, cleaned up: [...] this experiment, which worked well: mkdir ~/.templates touch ~/.templates/document.txt Edit relevant bit in ~/.config/user-dirs.dirs: XDG_TEMPLATES_DIR="$HOME/.templates" -- 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/1632027 Title: New Document feature missing from Nautilus 3.20+ Status in Nautilus: Invalid Status in nautilus package in Ubuntu: Confirmed Bug description: Ubuntu has a patch ( 16_unity_new_documents.patch ) to enable a 'New Document' function in the right-click context menu. This patch was not ported to Nautilus 3.20 so this Ubuntu-specific feature is missing in Ubuntu 16.10. https://bazaar.launchpad.net/~ubuntu- desktop/nautilus/ubuntu/view/head:/debian/patches/16_unity_new_documents.patch While this patch being disabled is noted in the debian/changelog, here's a formal bug to document the issue and maybe give it a bit more visibility so that it will be fixed. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: nautilus 1:3.20.3-1ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7 Uname: Linux 4.8.0-17-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Oct 10 12:54:50 2016 EcryptfsInUse: Yes GsettingsChanges: b'org.gnome.nautilus.preferences' b'open-folder-on-dnd-hover' b'false' b'org.gnome.nautilus.window-state' b'sidebar-width' b'171' b'org.gnome.nautilus.window-state' b'geometry' b"'1106x542+436+438'" b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'small'" InstallationDate: Installed on 2016-08-11 (59 days ago) InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Alpha amd64 (20160811) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: gnome-terminal 3.20.2-1ubuntu5 To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1632027/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1632027] Re: New Document feature missing from Nautilus 3.20+
This still (surprisingly) seems to be an issue in Ubuntu 22.04 ... Perhaps Ubuntu could add support for having the templates in a hidden folder such as `~/.templates`, and ship it just a single empty file, as a starting example? I just tried this experiment, which worked well: `mkdir ~/.templates` `touch ~/.templates/document.txt` Edit relevant bit in `~/.config/user-dirs.dirs`: `XDG_TEMPLATES_DIR="$HOME/.templates"` I was able to right-click in a folder and given a "New Document > document" option. (Comment also added in Gitlab issue #407 mentioned by 林博仁 (Buo-ren, Lin) on 2018-05-06 above) -- 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/1632027 Title: New Document feature missing from Nautilus 3.20+ Status in Nautilus: Invalid Status in nautilus package in Ubuntu: Confirmed Bug description: Ubuntu has a patch ( 16_unity_new_documents.patch ) to enable a 'New Document' function in the right-click context menu. This patch was not ported to Nautilus 3.20 so this Ubuntu-specific feature is missing in Ubuntu 16.10. https://bazaar.launchpad.net/~ubuntu- desktop/nautilus/ubuntu/view/head:/debian/patches/16_unity_new_documents.patch While this patch being disabled is noted in the debian/changelog, here's a formal bug to document the issue and maybe give it a bit more visibility so that it will be fixed. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: nautilus 1:3.20.3-1ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7 Uname: Linux 4.8.0-17-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Oct 10 12:54:50 2016 EcryptfsInUse: Yes GsettingsChanges: b'org.gnome.nautilus.preferences' b'open-folder-on-dnd-hover' b'false' b'org.gnome.nautilus.window-state' b'sidebar-width' b'171' b'org.gnome.nautilus.window-state' b'geometry' b"'1106x542+436+438'" b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'small'" InstallationDate: Installed on 2016-08-11 (59 days ago) InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Alpha amd64 (20160811) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: gnome-terminal 3.20.2-1ubuntu5 To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1632027/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1951830] [NEW] Low Disk Space is too late
Public bug reported: With today's bandwidth, downloading 1 GB doesn't take long, so you could end up running out of space only seconds after the "Low Disk Space" warning pops up, since the thresholds are pretty tight, with less than 95% and less than 1 GB. /org/gnome/settings-daemon/plugins/housekeeping/free-percent-notify 95% /org/gnome/settings-daemon/plugins/housekeeping/free-size-gb-no-notify 1 GB Suggested solution: 1. Change these values to 85% and 10 GB 2. Make them available through the GUI under "Notifications", and add "Change thresholds under Settings > Notifications" under the "Low Disk Space" warning message window ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1951830 Title: Low Disk Space is too late Status in gnome-settings-daemon package in Ubuntu: New Bug description: With today's bandwidth, downloading 1 GB doesn't take long, so you could end up running out of space only seconds after the "Low Disk Space" warning pops up, since the thresholds are pretty tight, with less than 95% and less than 1 GB. /org/gnome/settings-daemon/plugins/housekeeping/free-percent-notify 95% /org/gnome/settings-daemon/plugins/housekeeping/free-size-gb-no-notify 1 GB Suggested solution: 1. Change these values to 85% and 10 GB 2. Make them available through the GUI under "Notifications", and add "Change thresholds under Settings > Notifications" under the "Low Disk Space" warning message window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1951830/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1931612] Re: Print dialog box shows same printer twice
I also see this in Ubuntu 20.04 Gnome. I have installed my Brother HL-L3270CDW printer using the official driver, for all features to be available: https://support.brother.com/g/b/producttop.aspx?c=us=en=hll3270cdw_us_eu_as Now, if I open the "Printers" dialogue, the manually installed Brother printer instance is shown as "Brother HL-L3270CDW CUPS", as well as a doublet called "Brother Brother HL-L3270CDW series[en]". If I remove the automatically added printer, it immediately re-appears. See also these two issues, where many Ubuntu 20.04 users see an already installed printer twice, so it seems quite a few users are affected by this: https://askubuntu.com/questions/996020/cannot-stop-network-printers-are-being-automatically-added https://askubuntu.com/questions/345083/how-do-i-disable-automatic-remote-printer-installation Things I tried, suggested on pages above: #1, With this, Libreoffice Write stalls for 30-40 seconds: enable-dbus=no #2 This didn't make any difference: sudo systemctl stop cups-browsed sudo systemctl disable cups-browsed Shows same printer twice: Printers (via Ubuntu GUI) Image Viewer (default, with Ubuntu) LibreOffice Write Shows only the correct printer: Firefox (and other browsers) Like Timur Tabi (timur-tabi) wrote on 2021-06-14: > The GTK developers tell me that this is fixed in the latest version of libgtk. How do I upgrade libgtk to the latest version on Ubuntu 20.04? Is there a way I can pull in an update for just this package from a newer version of Ubuntu, without breaking everything else? Is there a way we can try this latest version of libgtk on Ubuntu 20.04? -- 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/1931612 Title: Print dialog box shows same printer twice Status in cups package in Ubuntu: Confirmed Bug description: I have set up a single HP printer which is attached to my network. The setup process went smoothly, and when I open the Printers system setup panel, I see only my printer there. However, when I print from an application, and that application uses the system print dialog box, my printer appears twice. One entry, matching the name correctly, works fine. The other, which a slightly changed name, does not work at all. See attached screenshot. Applications that have their own print dialog box do not have this problem. For example, Firefox shows only my printer once. Same thing with Libre Office. Description:Ubuntu 20.04.2 LTS Release:20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1931612/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1874578] Re: [wayland] dock has very long load time when show-mounts is enabled
Thanks, I will add some more info in bug #1900907. -- 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/1874578 Title: [wayland] dock has very long load time when show-mounts is enabled Status in Dash to dock: New Status in gnome-shell-extension-dashtodock package in Ubuntu: Confirmed Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Bug description: I just upgraded from Ubuntu 18.04 to 20.04. When I boot my system I have to wait at least 10 to 15 seconds for the application icons to load on dock. Meanwhile everything else seems to be working properly. I didn't experience this behavior in Ubuntu 18.04. Also the dock doesn't trigger when I move my cursor to the left of the screen. (I have set the docker to Auto-Hide mode and it's position is on the left of my screen). --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2016-08-03 (1359 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Package: gnome-shell-extension-ubuntu-dock 67ubuntu20.04.5 PackageArchitecture: all ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Tags: focal third-party-packages wayland-session Uname: Linux 5.4.0-26-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-04-23 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1874578/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1874578] Re: [wayland] dock has very long load time when show-mounts is enabled
Using Ubuntu 20.04, I have a disk mounted automatically via /etc/fstab when booting. I tried with show-mounts enabled and disabled, and both are delayed. -- 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/1874578 Title: [wayland] dock has very long load time when show-mounts is enabled Status in Dash to dock: New Status in gnome-shell-extension-dashtodock package in Ubuntu: Confirmed Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Bug description: I just upgraded from Ubuntu 18.04 to 20.04. When I boot my system I have to wait at least 10 to 15 seconds for the application icons to load on dock. Meanwhile everything else seems to be working properly. I didn't experience this behavior in Ubuntu 18.04. Also the dock doesn't trigger when I move my cursor to the left of the screen. (I have set the docker to Auto-Hide mode and it's position is on the left of my screen). --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2016-08-03 (1359 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Package: gnome-shell-extension-ubuntu-dock 67ubuntu20.04.5 PackageArchitecture: all ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Tags: focal third-party-packages wayland-session Uname: Linux 5.4.0-26-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-04-23 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1874578/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1903337] Re: [Feature Request] Replace Nautilus with Nemo?
Thanks for a fast answer, is it this web site? https://discourse.ubuntu.com/ -- 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/1903337 Title: [Feature Request] Replace Nautilus with Nemo? Status in nautilus package in Ubuntu: Opinion Bug description: This bug is a feature request to replace Nautilus with Nemo. The Desktop is not working too well in Ubuntu 20.04: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1813441 https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1855711 https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1857014 https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1886322 https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1901150 Could it be considered to replace Nautilus with Nemo as the default file manager, including managing desktop icons? With the tweaks outlined in this post, the Desktop works pretty well, and more or less as expected: https://askubuntu.com/questions/1066752/how-to-set-nemo-as-the- default-file-manager-in-ubuntu-18-04/1173861#1173861 I always switch to Nemo when I install a fresh Ubuntu, due to all the extra configuration options it offers. Nautilus seems too minimalistic for a modern file manager. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1903337/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1903337] [NEW] [Feature Request] Replace Nautilus with Nemo?
Public bug reported: This bug is a feature request to replace Nautilus with Nemo. The Desktop is not working too well in Ubuntu 20.04: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1813441 https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1855711 https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1857014 https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1886322 https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1901150 Could it be considered to replace Nautilus with Nemo as the default file manager, including managing desktop icons? With the tweaks outlined in this post, the Desktop works pretty well, and more or less as expected: https://askubuntu.com/questions/1066752/how-to-set-nemo-as-the-default- file-manager-in-ubuntu-18-04/1173861#1173861 I always switch to Nemo when I install a fresh Ubuntu, due to all the extra configuration options it offers. Nautilus seems too minimalistic for a modern file manager. ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1903337 Title: [Feature Request] Replace Nautilus with Nemo? Status in nautilus package in Ubuntu: New Bug description: This bug is a feature request to replace Nautilus with Nemo. The Desktop is not working too well in Ubuntu 20.04: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1813441 https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1855711 https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1857014 https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1886322 https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1901150 Could it be considered to replace Nautilus with Nemo as the default file manager, including managing desktop icons? With the tweaks outlined in this post, the Desktop works pretty well, and more or less as expected: https://askubuntu.com/questions/1066752/how-to-set-nemo-as-the- default-file-manager-in-ubuntu-18-04/1173861#1173861 I always switch to Nemo when I install a fresh Ubuntu, due to all the extra configuration options it offers. Nautilus seems too minimalistic for a modern file manager. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1903337/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1184699] Re: Canon LIDE 110 can only scan once, then I need to replug the usb cable
Just a note that Canon LiDE 210 scanner has worked perfectly for me in both Ubuntu 18.04 and 20.04, out of the box with the included Document Scanner (3.36.3) program, without having to install programs or drivers. It just works. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1184699 Title: Canon LIDE 110 can only scan once, then I need to replug the usb cable Status in sane-backends package in Ubuntu: Confirmed Bug description: I have a Canon LIDE 110 scanner which works by default on ubuntu 13.04. The problem is after first scan, I can not scan for second time. I need to reconnect the USB cable to use the scanner again. # TEST 1 : without reconnecting the usb cable francois@pc:~$ scanimage -v > test1.jpg # success scanimage: scanning image of size 636x885 pixels at 8 bits/pixel scanimage: acquiring gray frame scanimage: min/max graylevel value = 0/255 scanimage: read 562860 bytes in total # I don't unplug plug the usb cable. francois@pc:~$ scanimage -v > test2.jpg # FAIL scanimage: no SANE devices found # TEST 2 : reconnect usb cable between scan attempts francois@pc:~$ scanimage -v > test1.jpg # success scanimage: scanning image of size 636x885 pixels at 8 bits/pixel scanimage: acquiring gray frame scanimage: min/max graylevel value = 0/255 scanimage: read 562860 bytes in total # I unplug and replug the usb cable. francois@pc:~$ scanimage -v > test2.jpg # SUCCESS scanimage: scanning image of size 636x885 pixels at 8 bits/pixel scanimage: acquiring gray frame scanimage: min/max graylevel value = 0/255 scanimage: read 562860 bytes in total francois@pc:~$ dmesg # extract [ 829.365158] usb 3-1: USB disconnect, device number 2 [ 834.935000] usb 3-1: new high-speed USB device number 4 using xhci_hcd [ 834.952515] usb 3-1: New USB device found, idVendor=04a9, idProduct=1909 [ 834.952519] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 834.952522] usb 3-1: Product: CanoScan [ 834.952524] usb 3-1: Manufacturer: Canon [ 1623.738811] usb 3-1: USB disconnect, device number 4 [ 1623.739072] xhci_hcd :00:14.0: Slot 3 endpoint 6 not removed from BW list! [ 1625.528827] usb 3-1: new high-speed USB device number 5 using xhci_hcd [ 1625.546327] usb 3-1: New USB device found, idVendor=04a9, idProduct=1909 [ 1625.546331] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 1625.546334] usb 3-1: Product: CanoScan [ 1625.546336] usb 3-1: Manufacturer: Canon francois@pc:~$ uname -a && cat /etc/issue Linux pc 3.8.0-22-generic #33-Ubuntu SMP Thu May 16 15:17:14 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux Ubuntu 13.04 \n \l The problem was reported here by someone else : http://askubuntu.com/questions/278473/canon-lide-110-should-reconnect- usb-for-each-scan Thanks François To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1184699/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1764417] Re: Unrecoverable failure in required component org.gnome.SettingsDaemon.Color.desktop
This seems to have been fixed in Ubuntu 20.04.1 ... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1764417 Title: Unrecoverable failure in required component org.gnome.SettingsDaemon.Color.desktop Status in gnome-settings-daemon package in Ubuntu: Confirmed Bug description: I've had this happen a couple of times now since upgrading to 18.04: soon (perhaps within a minute) after logging in, Gnome session ends abruptly and I'm thrown back to the login screen. IIRC, in both instances this occurred on the first login after boot, so it does not reoccur on the subsequent re-login, and not on every login (very rarely in fact), and for now I have no better steps to reproduce this other than "boot, log in". Bug #1663839 (reported against 17.04) seems similar, as does bug #1731428 (reported against 17.10). journalctl output during the issue: Apr 16 07:00:30 saegusa gnome-session[4342]: gnome-session-binary[4342]: WARNING: Application 'org.gnome.SettingsDaemon.Color.desktop' failed to register before timeout Apr 16 07:00:30 saegusa gnome-session-binary[4342]: WARNING: Application 'org.gnome.SettingsDaemon.Color.desktop' failed to register before timeout Apr 16 07:00:30 saegusa gnome-session-binary[4342]: Unrecoverable failure in required component org.gnome.SettingsDaemon.Color.desktop Apr 16 07:00:30 saegusa gnome-session[4342]: gnome-session-binary[4342]: CRITICAL: We failed, but the fail whale is dead. Sorry Apr 16 07:00:30 saegusa gnome-session-binary[4342]: CRITICAL: We failed, but the fail whale is dead. Sorry ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-settings-daemon 3.28.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 16 17:07:14 2018 InstallationDate: Installed on 2016-10-13 (550 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash SourcePackage: gnome-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1764417/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1813441] Re: Can no longer drag and drop files between desktop and applications
I was quite surprised to find the icons on the Desktop not navigable with arrow keys. Also, I couldn't cut and paste files to and from the Desktop. For many years, I have always replaced Nautilus with Nemo, it's so much more flexible. I managed to get the Desktop in a great state using Nemo, following the steps outlined here: https://askubuntu.com/questions/1066752/how-to-set-nemo-as-the-default- file-manager-in-ubuntu-18-04/1173861#1173861 I would suggest the Ubuntu software managers to replace Nautilus with Nemo, it seems like the logical choice, by far. -- 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/1813441 Title: Can no longer drag and drop files between desktop and applications Status in gnome-shell-extension-desktop-icons: New Status in gnome-shell-extension-desktop-icons package in Ubuntu: Triaged Bug description: In releases before 19.04, you could drag and drop files from the desktop into applications. This no longer works. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell-extension-desktop-icons 19.01-1 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu19 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Jan 26 21:47:14 2019 InstallationDate: Installed on 2019-01-02 (24 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) PackageArchitecture: all SourcePackage: gnome-shell-extension-desktop-icons UpgradeStatus: Upgraded to disco on 2019-01-21 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1813441/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1764417] Re: Unrecoverable failure in required component org.gnome.SettingsDaemon.Color.desktop
Also getting an org.gnome.SettingsDaemon.Color.desktop error using Ubuntu 18.04 with Nvidia graphics card, no Chrome Desktop installed. The Desktop drops into a black screen, with this text: dev/sda1: clean, 123456/1234567 files, 1234567/12345678 blocks I can get back into Ubuntu by pressing Alt+F2. >From journalctl -b: nov 12 09:01:43 USER gnome-software[3843]: json_object_has_member: assertion 'member_name != NULL' failed nov 12 09:01:43 USER gnome-software[3843]: g_strsplit: assertion 'string != NULL' failed nov 12 09:01:43 USER gnome-software[3843]: g_strv_length: assertion 'str_array != NULL' failed nov 12 09:01:43 USER PackageKit[3036]: get-updates transaction /20427_ababeceb from uid 1000 finished with success after 440ms nov 12 09:01:50 USER gnome-session[1816]: gnome-session-binary[1816]: WARNING: Application 'org.gnome.SettingsDaemon.Color.desktop' failed to register before timeout nov 12 09:01:50 USER gnome-session-binary[1816]: WARNING: Application 'org.gnome.SettingsDaemon.Color.desktop' failed to register before timeout nov 12 09:01:50 USER gnome-session-binary[1816]: Unrecoverable failure in required component org.gnome.SettingsDaemon.Color.desktop nov 12 09:01:50 USER gnome-session[1816]: gnome-session-binary[1816]: CRITICAL: We failed, but the fail whale is dead. Sorry nov 12 09:01:50 USER gnome-session-binary[1816]: CRITICAL: We failed, but the fail whale is dead. Sorry nov 12 09:01:50 USER gnome-shell[1835]: gnome-shell: Fatal IO error 0 (Success) on X server :0. nov 12 09:01:50 USER at-spi-bus-launcher[1819]: XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0" nov 12 09:01:50 USER at-spi-bus-launcher[1819]: after 71 requests (71 known processed) with 0 events remaining. nov 12 09:01:50 USER gsd-xsettings[3061]: gsd-xsettings: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. nov 12 09:01:50 USER gsd-clipboard[3067]: gsd-clipboard: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. nov 12 09:01:50 USER gsd-media-keys[3093]: gsd-media-keys: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. nov 12 09:01:50 USER gsd-keyboard[3082]: gsd-keyboard: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. nov 12 09:01:50 USER gsd-power[3100]: gsd-power: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. nov 12 09:01:50 USER gsd-wacom[3143]: gsd-wacom: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. nov 12 09:01:50 USER /usr/lib/gdm3/gdm-x-session[1735]: (II) UnloadModule: "libinput" nov 12 09:01:50 USER /usr/lib/gdm3/gdm-x-session[1735]: (II) systemd-logind: releasing fd for 13:66 nov 12 09:01:50 USER polkitd(authority=local)[1175]: Unregistered Authentication Agent for unix-session:c2 (system bus name :1.37, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) (disconnected from bus) nov 12 09:01:50 USER /usr/lib/gdm3/gdm-x-session[1735]: (II) UnloadModule: "libinput" nov 12 09:01:50 USER /usr/lib/gdm3/gdm-x-session[1735]: (II) systemd-logind: releasing fd for 13:67 nov 12 09:01:50 USER /usr/lib/gdm3/gdm-x-session[1735]: (II) UnloadModule: "libinput" nov 12 09:01:50 USER /usr/lib/gdm3/gdm-x-session[1735]: (II) systemd-logind: releasing fd for 13:64 nov 12 09:01:50 USER /usr/lib/gdm3/gdm-x-session[1735]: (II) UnloadModule: "libinput" nov 12 09:01:50 USER /usr/lib/gdm3/gdm-x-session[1735]: (II) systemd-logind: releasing fd for 13:65 nov 12 09:01:50 USER /usr/lib/gdm3/gdm-x-session[1735]: (II) NVIDIA(GPU-0): Deleting GPU-0 nov 12 09:01:50 USER rtkit-daemon[1844]: Supervising 3 threads of 1 processes of 1 users. nov 12 09:01:50 USER rtkit-daemon[1844]: Successfully made thread 4339 of process 3602 (n/a) owned by '1000' RT at priority 5. nov 12 09:01:50 USER rtkit-daemon[1844]: Supervising 4 threads of 1 processes of 1 users. nov 12 09:01:50 USER kernel: rfkill: input handler enabled nov 12 09:01:50 USER /usr/lib/gdm3/gdm-x-session[1735]: (II) Server terminated successfully (0). Closing log file. nov 12 09:01:50 USER gdm-launch-environment][1648]: pam_unix(gdm-launch-environment:session): session closed for user gdm nov 12 09:01:50 USER systemd-logind[927]: Removed session c2. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1764417 Title: Unrecoverable failure in required component org.gnome.SettingsDaemon.Color.desktop Status in gnome-settings-daemon package in Ubuntu: Confirmed Bug description: I've had this happen a couple of times now since upgrading to 18.04: soon (perhaps within a minute) after logging in, Gnome session ends abruptly and I'm thrown back to the login screen. IIRC, in both instances this occurred on the first login after boot, so it does not reoccur on the subsequent re-login, and not on every login (very rarely in fact),
[Desktop-packages] [Bug 1800196] Re: spice-vdagent[1345]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0
Thanks for sharing yas! That approach seems to take care of the problem, it doesn't show up in my log any longer. Now all I need is to get rid of the "Unrecoverable failure in required component org.gnome.Shell.desktop", for a totally clean log after a fresh boot in Ubuntu 18.04 ... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to spice-vdagent in Ubuntu. https://bugs.launchpad.net/bugs/1800196 Title: spice-vdagent[1345]: Cannot access vdagent virtio channel /dev/virtio- ports/com.redhat.spice.0 Status in spice-vdagent package in Ubuntu: Confirmed Bug description: Hello, $ journalctl -b [...] oct 26 07:26:57 romanescu spice-vdagent[1345]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0 Best regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: spice-vdagent 0.17.0-1ubuntu2 Uname: Linux 4.19.0-gnu x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 26 14:34:00 2018 InstallationDate: Installed on 2017-10-13 (378 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) SourcePackage: spice-vdagent UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/spice-vdagent/+bug/1800196/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1821897] Re: Unrecoverable failure in required component org.gnome.Shell.desktop
Also a problem in Ubuntu 18.04. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1821897 Title: Unrecoverable failure in required component org.gnome.Shell.desktop Status in gnome-settings-daemon package in Ubuntu: Confirmed Bug description: os: ubuntu 18.10 kernel: 4.18.0-16-generic bug: Thg 3 27 17:06:28 smay-X556UR gnome-session-binary[971]: Unrecoverable failure in required component org.gnome.Shell.desktop help me. please! thanks you. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1821897/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1832913] Re: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0
*** This bug is a duplicate of bug 1800196 *** https://bugs.launchpad.net/bugs/1800196 Thanks for pointing me in the right direction Daniel, I'll follow the other bug report. Have a nice day! -- 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/1832913 Title: Cannot access vdagent virtio channel /dev/virtio- ports/com.redhat.spice.0 Status in gnome-session package in Ubuntu: New Bug description: I am getting this error in my log, Ubuntu 18.04: Cannot access vdagent virtio channel /dev/virtio- ports/com.redhat.spice.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1832913/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1832913] [NEW] Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0
Public bug reported: I am getting this error in my log, Ubuntu 18.04: Cannot access vdagent virtio channel /dev/virtio- ports/com.redhat.spice.0 ** Affects: gnome-session (Ubuntu) Importance: Undecided Status: New -- 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/1832913 Title: Cannot access vdagent virtio channel /dev/virtio- ports/com.redhat.spice.0 Status in gnome-session package in Ubuntu: New Bug description: I am getting this error in my log, Ubuntu 18.04: Cannot access vdagent virtio channel /dev/virtio- ports/com.redhat.spice.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1832913/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1819919] Re: Too much information in File Systems
I have created an issue here: https://gitlab.gnome.org/GNOME/gnome- system-monitor/issues/101 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-system-monitor/issues #101 https://gitlab.gnome.org/GNOME/gnome-system-monitor/issues/101 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-system-monitor in Ubuntu. https://bugs.launchpad.net/bugs/1819919 Title: Too much information in File Systems Status in gnome-system-monitor package in Ubuntu: New Bug description: Previous versions of File Systems only showed my two harddrives, and was pretty useful. In Ubuntu 18.04 gnome-system-monitor > File Systems now shows 35 lines of uninteresting lines, like /var/lib/snapd ... I tried switching from Snap- to classic apt-based version, with these commands: sudo snap remove gnome-system-monitor sudo apt-get install gnome-system-monitor I got the good old System Files back, showing just the two hard drives of interest to me, but "snap remove gnome-system-monitor" removed a lot of extra packages, so my shortcuts stopped working, and possibly other stuff as well. I had to revert to snap-based gnome-system- monitor to get them working again. How can I get the previous and useful File Systems back, only showing my two hard drives? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1819919/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1819919] Re: Too much useless information in File Systems
** Summary changed: - Lots of useless info in File Systems + Too much useless information in File Systems ** Summary changed: - Too much useless information in File Systems + Too much information in File Systems -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-system-monitor in Ubuntu. https://bugs.launchpad.net/bugs/1819919 Title: Too much information in File Systems Status in gnome-system-monitor package in Ubuntu: New Bug description: Previous versions of File Systems only showed my two harddrives, and was pretty useful. In Ubuntu 18.04 gnome-system-monitor > File Systems now shows 35 lines of uninteresting lines, like /var/lib/snapd ... I tried switching from Snap- to classic apt-based version, with these commands: sudo snap remove gnome-system-monitor sudo apt-get install gnome-system-monitor I got the good old System Files back, showing just the two hard drives of interest to me, but "snap remove gnome-system-monitor" removed a lot of extra packages, so my shortcuts stopped working, and possibly other stuff as well. I had to revert to snap-based gnome-system- monitor to get them working again. How can I get the previous and useful File Systems back, only showing my two hard drives? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1819919/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1819920] Re: gnome-session-quit --power-off option ignored
Thank you @Daniel van Vugt for your thorough explanation and @Sebastien Bacher for suggestion of reporting at gitlab.gnome.org, I have created this issue: https://gitlab.gnome.org/GNOME/gnome-session/issues/16 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-session/issues #16 https://gitlab.gnome.org/GNOME/gnome-session/issues/16 -- 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/1819920 Title: gnome-session-quit --power-off option ignored Status in gnome-session package in Ubuntu: Confirmed Bug description: OS: Ubuntu 18.04 Command: gnome-session-quit --power-off Expected behaviour: Power off dialogue, with "Power Off" selected Actual behaviour: Power off dialogue, with "Cancel" selected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1819920/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1819920] [NEW] gnome-session-quit --power-off option ignored
Public bug reported: OS: Ubuntu 18.04 Command: gnome-session-quit --power-off Expected behaviour: Power off dialogue, with "Power Off" selected Actual behaviour: Power off dialogue, with "Cancel" selected ** Affects: gnome-session (Ubuntu) Importance: Undecided Status: New -- 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/1819920 Title: gnome-session-quit --power-off option ignored Status in gnome-session package in Ubuntu: New Bug description: OS: Ubuntu 18.04 Command: gnome-session-quit --power-off Expected behaviour: Power off dialogue, with "Power Off" selected Actual behaviour: Power off dialogue, with "Cancel" selected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1819920/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1819919] [NEW] Lots of useless info in File Systems
Public bug reported: Previous versions of File Systems only showed my two harddrives, and was pretty useful. In Ubuntu 18.04 gnome-system-monitor > File Systems now shows 35 lines of uninteresting lines, like /var/lib/snapd ... I tried switching from Snap- to classic apt-based version, with these commands: sudo snap remove gnome-system-monitor sudo apt-get install gnome-system-monitor I got the good old System Files back, showing just the two hard drives of interest to me, but "snap remove gnome-system-monitor" removed a lot of extra packages, so my shortcuts stopped working, and possibly other stuff as well. I had to revert to snap-based gnome-system-monitor to get them working again. How can I get the previous and useful File Systems back, only showing my two hard drives? ** Affects: gnome-system-monitor (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-system-monitor in Ubuntu. https://bugs.launchpad.net/bugs/1819919 Title: Lots of useless info in File Systems Status in gnome-system-monitor package in Ubuntu: New Bug description: Previous versions of File Systems only showed my two harddrives, and was pretty useful. In Ubuntu 18.04 gnome-system-monitor > File Systems now shows 35 lines of uninteresting lines, like /var/lib/snapd ... I tried switching from Snap- to classic apt-based version, with these commands: sudo snap remove gnome-system-monitor sudo apt-get install gnome-system-monitor I got the good old System Files back, showing just the two hard drives of interest to me, but "snap remove gnome-system-monitor" removed a lot of extra packages, so my shortcuts stopped working, and possibly other stuff as well. I had to revert to snap-based gnome-system- monitor to get them working again. How can I get the previous and useful File Systems back, only showing my two hard drives? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1819919/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1800196] Re: spice-vdagent[1345]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0
I am also getting this error in my Ubuntu 18.04 logs during boot. I tried disabling it under Startup Applications: Spice vdagent /usr/bin/spice-vdagent Agent for Spice guests ... yet I still get the error. I tested the service path by temporarily renaming /usr/bin/spice-vdagent and rebooting, which stopped the error occurring in the log. I don't need the Spice vdagent service, so is there an elegant way to prevent the service from even trying to run? The easiest solution would be to uninstall spice-vdagent, but that doesn't seem to be possible, since it would also remove ubuntu-desktop, which would be unfortunate, to say the least. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to spice-vdagent in Ubuntu. https://bugs.launchpad.net/bugs/1800196 Title: spice-vdagent[1345]: Cannot access vdagent virtio channel /dev/virtio- ports/com.redhat.spice.0 Status in spice-vdagent package in Ubuntu: Confirmed Bug description: Hello, $ journalctl -b [...] oct 26 07:26:57 romanescu spice-vdagent[1345]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0 Best regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: spice-vdagent 0.17.0-1ubuntu2 Uname: Linux 4.19.0-gnu x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 26 14:34:00 2018 InstallationDate: Installed on 2017-10-13 (378 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) SourcePackage: spice-vdagent UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/spice-vdagent/+bug/1800196/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1184699] Re: Canon LIDE 110 can only scan once, then I need to replug the usb cable
Thanks @brulaz, after updating the drivers I can scan more than one time with my Canon LiDE 210 scanner, and the scanner no longer "disappears". See comment #27. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1184699 Title: Canon LIDE 110 can only scan once, then I need to replug the usb cable Status in Simple Scan: Invalid Status in sane-backends package in Ubuntu: Fix Committed Bug description: I have a Canon LIDE 110 scanner which works by default on ubuntu 13.04. The problem is after first scan, I can not scan for second time. I need to reconnect the USB cable to use the scanner again. # TEST 1 : without reconnecting the usb cable francois@pc:~$ scanimage -v > test1.jpg # success scanimage: scanning image of size 636x885 pixels at 8 bits/pixel scanimage: acquiring gray frame scanimage: min/max graylevel value = 0/255 scanimage: read 562860 bytes in total # I don't unplug plug the usb cable. francois@pc:~$ scanimage -v > test2.jpg # FAIL scanimage: no SANE devices found # TEST 2 : reconnect usb cable between scan attempts francois@pc:~$ scanimage -v > test1.jpg # success scanimage: scanning image of size 636x885 pixels at 8 bits/pixel scanimage: acquiring gray frame scanimage: min/max graylevel value = 0/255 scanimage: read 562860 bytes in total # I unplug and replug the usb cable. francois@pc:~$ scanimage -v > test2.jpg # SUCCESS scanimage: scanning image of size 636x885 pixels at 8 bits/pixel scanimage: acquiring gray frame scanimage: min/max graylevel value = 0/255 scanimage: read 562860 bytes in total francois@pc:~$ dmesg # extract [ 829.365158] usb 3-1: USB disconnect, device number 2 [ 834.935000] usb 3-1: new high-speed USB device number 4 using xhci_hcd [ 834.952515] usb 3-1: New USB device found, idVendor=04a9, idProduct=1909 [ 834.952519] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 834.952522] usb 3-1: Product: CanoScan [ 834.952524] usb 3-1: Manufacturer: Canon [ 1623.738811] usb 3-1: USB disconnect, device number 4 [ 1623.739072] xhci_hcd :00:14.0: Slot 3 endpoint 6 not removed from BW list! [ 1625.528827] usb 3-1: new high-speed USB device number 5 using xhci_hcd [ 1625.546327] usb 3-1: New USB device found, idVendor=04a9, idProduct=1909 [ 1625.546331] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 1625.546334] usb 3-1: Product: CanoScan [ 1625.546336] usb 3-1: Manufacturer: Canon francois@pc:~$ uname -a && cat /etc/issue Linux pc 3.8.0-22-generic #33-Ubuntu SMP Thu May 16 15:17:14 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux Ubuntu 13.04 \n \l The problem was reported here by someone else : http://askubuntu.com/questions/278473/canon-lide-110-should-reconnect- usb-for-each-scan Thanks François To manage notifications about this bug go to: https://bugs.launchpad.net/simple-scan/+bug/1184699/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1539634] Re: network-manager crashes when using libnl-3-200-3.21.1-1ubuntu1
Todays regular updates via the Ubuntu "Software Updater" has fixed this issue. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1539634 Title: network-manager crashes when using libnl-3-200-3.21.1-1ubuntu1 Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Trusty: Fix Released Bug description: [Triage Notes] This regression is caused by a libnl proposed update tracked in bug 1511735. It has not been released as an update, only proposed as an update for early testing. If you volunteered to test proposed updates, then thank you. Your care and attention will stop this regression from hitting ordinary users, and we appreciate your contribution to Ubuntu. If you are not aware that you volunteered to test proposed updates, then please be aware that your system is configured to do so. In this case, you probably should turn this off. I'd appreciate if someone could explain how to do this in the comments. [Impact] * NetworkManager depends on libnl (libnl-3-200 libnl-genl-3-200 libnl-route-3-200) and when libnl is updated to proposed 3.2.21-1ubuntu1 NM segfaults due to libnl exposing a bug in NM validation packets. This affects the 0.98 release of NetworkManager and has already been fixed in newer releases. * Backporting fixes from upstream release is required to prevent NetworkManager from faulting which breaks networking on most Desktop releases. * All patches applied are already accepted upstream and newer Ubuntu releases are not affected. * Upgrading NetworkManager to 0.9.8.8-0ubuntu7.3 prior to updating libnl-3.2.21-1ubuntu1 is required to prevent NetworkManager crashing. [Test Case] * Reproduce crash test: 1. Download 14.04.03 Desktop iso, amd64 2. Launched in a VM, run from iso 3. In terminal, enable proposed 4. sudo apt-get install libnl-3-200 libnl-genl-3-200 libnl-route-3-200 5. sudo restart network-manager # note the nm-applet disappears as NM has now crashed, no network conn. 6. dmesg to confirm network-manager crash 7. sudo dpkg --install gir1.2-networkmanager-1.0_0.9.8.8-0ubuntu7.3_amd64.deb libnm-glib4_0.9.8.8-0ubuntu7.3_amd64.deb libnm-glib-vpn1_0.9.8.8-0ubuntu7.3_amd64.deb libnm-util2_0.9.8.8-0ubuntu7.3_amd64.deb network-manager_0.9.8.8-0ubuntu7.3_amd64.deb 8. sudo start network-manager # nm-applet reappears, network connectivity restored * Successful upgrade test: 1. Download 14.04.03 Desktop iso, amd64 2. Launched in a VM, run from iso 3. In a terminal, sudo dpkg --install gir1.2-networkmanager-1.0_0.9.8.8-0ubuntu7.3_amd64.deb libnm-glib4_0.9.8.8-0ubuntu7.3_amd64.deb libnm-glib-vpn1_0.9.8.8-0ubuntu7.3_amd64.deb libnm-util2_0.9.8.8-0ubuntu7.3_amd64.deb network-manager_0.9.8.8-0ubuntu7.3_amd64.deb 4. sudo restart network-manager # NM still runs, no crash, net up 5. enable trusty-proposed in /etc/apt/sources.list 6. sudo apt-get update 7. sudo apt-get install libnl-3-200 libnl-genl-3-200 libnl-route-3-200 8. sudo restart network-manager # NM still runs, no crash, net up. [Regression Potential] * NetworkManager is a highly visible package, so testing NetworkManager functionality is critical. The patch does address the crash specificly introduced by the updated libnl SRU. * We need to ensure that users have installed this NetworkManager update before installing libnl3 update (special phasing needed). [Original Description] Testing out proposed libnl-3 package[1] exposed a bug in NM 0.98. After installing updated libnl3 and restarting networkmanager, NM crashes with: /var/log/syslog shows: init: network-manager main process (1057) killed by SEGV signal init: network-manager main process ended, respawning init: network-manager main process (1065) killed by SEGV signal init: network-manager respawning too fast, stopped The bug has been fixed in upstream 0.98 with these patches: http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=8e4576b9fdb5c888d20a13aa2cc198df790dba54 http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=65981edb9f562c07e78815c98093da67c50bfdcf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1539634/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 885146] Re: Archive Manager fails to handle password-protected ZIP files
I can confirm that installing p7zip-full fixes this problem. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to file-roller in Ubuntu. https://bugs.launchpad.net/bugs/885146 Title: Archive Manager fails to handle password-protected ZIP files Status in file-roller package in Ubuntu: Confirmed Bug description: Upon trying to open a password-protect ZIP file in Archive Manager/file-roller, I'm correctly prompted for a password. However, on pressing enter/clicking "OK", I then get an error dialog stating: An error occurred while extracting files. > Command Line Output error: must give decryption password with -P option ... on trying again without quitting file-roller, I'm not prompted for a password - it simply shows the same dialog. If I deliberately enter the *wrong* password, then the "Password required" dialog immediately re-opens - so it's not a mis-typed password issue. $ lsb_release -rd Description: Ubuntu 11.10 Release: 11.10 $ apt-cache policy file-roller file-roller: Installed: 3.2.1-0ubuntu1 Candidate: 3.2.1-0ubuntu1 Version table: *** 3.2.1-0ubuntu1 0 500 http://gb.archive.ubuntu.com/ubuntu/ oneiric-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.2.0-0ubuntu1 0 500 http://gb.archive.ubuntu.com/ubuntu/ oneiric/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/885146/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1539634] Re: network-manager crashes when using libnl-3-200-3.21.1-1ubuntu1
I am getting no internet after booting and the "network-manager main process ... killed by SEGV signal" error in my log file today, after having used internet via my computer this morning. I can bring Internet back by using: sudo ifconfig eth0 up sudo dhclient -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1539634 Title: network-manager crashes when using libnl-3-200-3.21.1-1ubuntu1 Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Trusty: Fix Released Bug description: [Triage Notes] This regression is caused by a libnl proposed update tracked in bug 1511735. It has not been released as an update, only proposed as an update for early testing. If you volunteered to test proposed updates, then thank you. Your care and attention will stop this regression from hitting ordinary users, and we appreciate your contribution to Ubuntu. If you are not aware that you volunteered to test proposed updates, then please be aware that your system is configured to do so. In this case, you probably should turn this off. I'd appreciate if someone could explain how to do this in the comments. [Impact] * NetworkManager depends on libnl (libnl-3-200 libnl-genl-3-200 libnl-route-3-200) and when libnl is updated to proposed 3.2.21-1ubuntu1 NM segfaults due to libnl exposing a bug in NM validation packets. This affects the 0.98 release of NetworkManager and has already been fixed in newer releases. * Backporting fixes from upstream release is required to prevent NetworkManager from faulting which breaks networking on most Desktop releases. * All patches applied are already accepted upstream and newer Ubuntu releases are not affected. * Upgrading NetworkManager to 0.9.8.8-0ubuntu7.3 prior to updating libnl-3.2.21-1ubuntu1 is required to prevent NetworkManager crashing. [Test Case] * Reproduce crash test: 1. Download 14.04.03 Desktop iso, amd64 2. Launched in a VM, run from iso 3. In terminal, enable proposed 4. sudo apt-get install libnl-3-200 libnl-genl-3-200 libnl-route-3-200 5. sudo restart network-manager # note the nm-applet disappears as NM has now crashed, no network conn. 6. dmesg to confirm network-manager crash 7. sudo dpkg --install gir1.2-networkmanager-1.0_0.9.8.8-0ubuntu7.3_amd64.deb libnm-glib4_0.9.8.8-0ubuntu7.3_amd64.deb libnm-glib-vpn1_0.9.8.8-0ubuntu7.3_amd64.deb libnm-util2_0.9.8.8-0ubuntu7.3_amd64.deb network-manager_0.9.8.8-0ubuntu7.3_amd64.deb 8. sudo start network-manager # nm-applet reappears, network connectivity restored * Successful upgrade test: 1. Download 14.04.03 Desktop iso, amd64 2. Launched in a VM, run from iso 3. In a terminal, sudo dpkg --install gir1.2-networkmanager-1.0_0.9.8.8-0ubuntu7.3_amd64.deb libnm-glib4_0.9.8.8-0ubuntu7.3_amd64.deb libnm-glib-vpn1_0.9.8.8-0ubuntu7.3_amd64.deb libnm-util2_0.9.8.8-0ubuntu7.3_amd64.deb network-manager_0.9.8.8-0ubuntu7.3_amd64.deb 4. sudo restart network-manager # NM still runs, no crash, net up 5. enable trusty-proposed in /etc/apt/sources.list 6. sudo apt-get update 7. sudo apt-get install libnl-3-200 libnl-genl-3-200 libnl-route-3-200 8. sudo restart network-manager # NM still runs, no crash, net up. [Regression Potential] * NetworkManager is a highly visible package, so testing NetworkManager functionality is critical. The patch does address the crash specificly introduced by the updated libnl SRU. * We need to ensure that users have installed this NetworkManager update before installing libnl3 update (special phasing needed). [Original Description] Testing out proposed libnl-3 package[1] exposed a bug in NM 0.98. After installing updated libnl3 and restarting networkmanager, NM crashes with: /var/log/syslog shows: init: network-manager main process (1057) killed by SEGV signal init: network-manager main process ended, respawning init: network-manager main process (1065) killed by SEGV signal init: network-manager respawning too fast, stopped The bug has been fixed in upstream 0.98 with these patches: http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=8e4576b9fdb5c888d20a13aa2cc198df790dba54 http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=65981edb9f562c07e78815c98093da67c50bfdcf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1539634/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
