[Desktop-packages] [Bug 1968405] [NEW] File missing in package?
Public bug reported: The upgrade from Ubuntu 21.10 to 22.04 - Ubuntu Jammy Jellyfish (development branch) - stopped. An "apt install -f" shows that a file is missing in the Yaru package: - root@besa:/home/daniele/Downloads# apt install -f Lettura elenco dei pacchetti... Fatto Generazione albero delle dipendenze... Fatto Lettura informazioni sullo stato... Fatto Correzione delle dipendenze... Fatto I seguenti pacchetti aggiuntivi saranno inoltre installati: yaru-theme-gnome-shell I seguenti pacchetti saranno aggiornati: yaru-theme-gnome-shell 1 aggiornati, 0 installati, 0 da rimuovere e 0 non aggiornati. 4 non completamente installati o rimossi. È necessario scaricare 0 B/85,4 kB di archivi. Dopo quest'operazione, verranno occupati 14,9 MB di spazio su disco. Continuare? [Y/n] (Lettura del database... 392424 file e directory attualmente installati.) Preparativi per estrarre .../yaru-theme-gnome-shell_22.04.3.1_all.deb... Estrazione di yaru-theme-gnome-shell (22.04.3.1) su (21.10.2)... dpkg: errore nell'elaborare l'archivio /var/cache/apt/archives/yaru-theme-gnome-shell_22.04.3.1_all.deb (--unpack): impossibile aprire "/usr/share/themes/Yaru/gnome-shell/calendar-today-light.svg.dpkg-new": No such file or directory Segnalazione apport non scritta poiché il messaggio di errore indica un errore nel sistema locale. Si sono verificati degli errori nell'elaborazione: /var/cache/apt/archives/yaru-theme-gnome-shell_22.04.3.1_all.deb The error line is: "/usr/share/themes/Yaru/gnome-shell/calendar-today-light.svg.dpkg-new": No such file or directory I unpacked the deb file and indeed there's no calendar-today- light.svg.dpkg-new file, the right name is calendar-today-light.svg It looks like a bug. ** Affects: yaru-theme (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/1968405 Title: File missing in package? Status in yaru-theme package in Ubuntu: New Bug description: The upgrade from Ubuntu 21.10 to 22.04 - Ubuntu Jammy Jellyfish (development branch) - stopped. An "apt install -f" shows that a file is missing in the Yaru package: - root@besa:/home/daniele/Downloads# apt install -f Lettura elenco dei pacchetti... Fatto Generazione albero delle dipendenze... Fatto Lettura informazioni sullo stato... Fatto Correzione delle dipendenze... Fatto I seguenti pacchetti aggiuntivi saranno inoltre installati: yaru-theme-gnome-shell I seguenti pacchetti saranno aggiornati: yaru-theme-gnome-shell 1 aggiornati, 0 installati, 0 da rimuovere e 0 non aggiornati. 4 non completamente installati o rimossi. È necessario scaricare 0 B/85,4 kB di archivi. Dopo quest'operazione, verranno occupati 14,9 MB di spazio su disco. Continuare? [Y/n] (Lettura del database... 392424 file e directory attualmente installati.) Preparativi per estrarre .../yaru-theme-gnome-shell_22.04.3.1_all.deb... Estrazione di yaru-theme-gnome-shell (22.04.3.1) su (21.10.2)... dpkg: errore nell'elaborare l'archivio /var/cache/apt/archives/yaru-theme-gnome-shell_22.04.3.1_all.deb (--unpack): impossibile aprire "/usr/share/themes/Yaru/gnome-shell/calendar-today-light.svg.dpkg-new": No such file or directory Segnalazione apport non scritta poiché il messaggio di errore indica un errore nel sistema locale. Si sono verificati degli errori nell'elaborazione: /var/cache/apt/archives/yaru-theme-gnome-shell_22.04.3.1_all.deb The error line is: "/usr/share/themes/Yaru/gnome-shell/calendar-today-light.svg.dpkg-new": No such file or directory I unpacked the deb file and indeed there's no calendar-today- light.svg.dpkg-new file, the right name is calendar-today-light.svg It looks like a bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1968405/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1774188] Re: Unlocking the screen takes 5 seconds in Xorg sessions (not so much in Wayland sessions)
I just upgraded to Ubuntu 19.10 but nothing changed. I see the status of the bug is 'expired', is anyone working on this? Thanks -- 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/1774188 Title: Unlocking the screen takes 5 seconds in Xorg sessions (not so much in Wayland sessions) Status in gdm3 package in Ubuntu: Expired Status in gnome-shell package in Ubuntu: Expired Status in mutter package in Ubuntu: Expired Status in xorg-server package in Ubuntu: Expired Bug description: This is a fresh installation of 18.04. After entering the password and pressing enter, it takes 5 seconds for the lock screen to disappear. This problem didn't happen on the same machine with 16.04 or 14.04. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed May 30 15:31:48 2018 InstallationDate: Installed on 2018-05-04 (25 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1774188/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1828785] [NEW] Unlocking the screen takes >4 seconds Ubuntu 19.04
Public bug reported: As suggested in https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1774188 I'm opening a new bug report. Unlocking the screen takes 4+ seconds, hardware is Lenovo i7 with 16GB RAM. Attached the output of 'journalctl -b'. 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: Mon May 13 11:03:28 2019 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true' b'org.gnome.shell' b'enabled-extensions' b"['gsconn...@andyholmes.github.io']" b'org.gnome.shell' b'remember-mount-password' b'true' b'org.gnome.desktop.interface' b'gtk-im-module' b"'ibus'" InstallationDate: Installed on 2019-02-22 (79 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: gnome-shell UpgradeStatus: Upgraded to disco on 2019-05-03 (9 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco ** Attachment added: "journalctl.txt" https://bugs.launchpad.net/bugs/1828785/+attachment/5263406/+files/journalctl.txt -- 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/1828785 Title: Unlocking the screen takes >4 seconds Ubuntu 19.04 Status in gnome-shell package in Ubuntu: New Bug description: As suggested in https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1774188 I'm opening a new bug report. Unlocking the screen takes 4+ seconds, hardware is Lenovo i7 with 16GB RAM. Attached the output of 'journalctl -b'. 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: Mon May 13 11:03:28 2019 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true' b'org.gnome.shell' b'enabled-extensions' b"['gsconn...@andyholmes.github.io']" b'org.gnome.shell' b'remember-mount-password' b'true' b'org.gnome.desktop.interface' b'gtk-im-module' b"'ibus'" InstallationDate: Installed on 2019-02-22 (79 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: gnome-shell UpgradeStatus: Upgraded to disco on 2019-05-03 (9 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1828785/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1774188] Re: Unlocking the screen takes 5 seconds in Xorg sessions (not so much in Wayland sessions)
/metoo Attached the relevant "journalctl -b" output file. Is this giving any indication? mei 12 10:58:22 besa gdm-password][21317]: gkr-pam: unlocked login keyring mei 12 10:58:23 besa NetworkManager[1034]: [1557651503.3134] agent-manager: req[0xd1141cf0, :1.312/org.gnome.Shell.NetworkAgent/1000]: agent registered mei 12 10:58:23 besa gnome-shell[2013]: [AppIndicatorSupport-DEBUG] Registering StatusNotifierItem :1.91/org/ayatana/NotificationItem/chrome_app_indicator_1 mei 12 10:58:23 besa gnome-shell[2013]: [AppIndicatorSupport-DEBUG] Registering StatusNotifierItem :1.69/org/ayatana/NotificationItem/Slack1 mei 12 10:58:23 besa gnome-shell[2013]: [AppIndicatorSupport-DEBUG] Registering StatusNotifierItem :1.67/org/ayatana/NotificationItem/blueman mei 12 10:58:23 besa gnome-shell[2013]: [AppIndicatorSupport-DEBUG] Registering StatusNotifierItem :1.94/org/ayatana/NotificationItem/software_update_available mei 12 10:58:23 besa gnome-shell[2013]: [AppIndicatorSupport-FATAL] unable to update overlay icon mei 12 10:58:23 besa gnome-shell[2013]: [AppIndicatorSupport-FATAL] unable to update overlay icon mei 12 10:58:23 besa gnome-shell[2013]: [AppIndicatorSupport-FATAL] unable to update overlay icon mei 12 10:58:23 besa gnome-shell[2013]: [AppIndicatorSupport-FATAL] unable to update overlay icon mei 12 10:58:23 besa gnome-shell[2013]: [AppIndicatorSupport-FATAL] unable to update overlay icon mei 12 10:58:23 besa gnome-shell[2013]: [AppIndicatorSupport-FATAL] unable to update overlay icon mei 12 10:58:23 besa gnome-shell[2013]: [AppIndicatorSupport-FATAL] unable to update overlay icon mei 12 10:58:23 besa gnome-shell[2013]: [AppIndicatorSupport-FATAL] unable to update overlay icon mei 12 10:58:26 besa org.gnome.Shell.desktop[2013]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a). mei 12 10:58:26 besa org.gnome.Shell.desktop[2013]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b). mei 12 10:58:26 besa org.gnome.Shell.desktop[2013]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c). mei 12 10:58:26 besa org.gnome.Shell.desktop[2013]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d). mei 12 10:58:26 besa org.gnome.Shell.desktop[2013]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e). mei 12 10:58:26 besa org.gnome.Shell.desktop[2013]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f). mei 12 10:58:26 besa org.gnome.Shell.desktop[2013]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11). mei 12 10:58:26 besa org.gnome.Shell.desktop[2013]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12). mei 12 10:58:26 besa org.gnome.Shell.desktop[2013]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). Thanks ** Attachment added: "journalctl.txt" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1774188/+attachment/5263207/+files/journalctl.txt -- 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/1774188 Title: Unlocking the screen takes 5 seconds in Xorg sessions (not so much in Wayland sessions) Status in gdm3 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: This is a fresh installation of 18.04. After entering the password and pressing enter, it takes 5 seconds for the lock screen to disappear. This problem didn't happen on the same machine with 16.04 or 14.04. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed May 30 15:31:48 2018 InstallationDate: Installed on 2018-05-04 (25 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1774188/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1689825] Re: gnome-keyring not unlocked on xenial when dbus-user-session is installed
Hi guys, This bug is still present on latest versions (seahorse 3.30). Why is assigned to chromium-browser package? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1689825 Title: gnome-keyring not unlocked on xenial when dbus-user-session is installed Status in chromium-browser package in Ubuntu: Invalid Status in dbus package in Ubuntu: Triaged Status in flatpak package in Ubuntu: Fix Released Bug description: 1) Release: 16.04.2 2) gnome-keyring: 3.18.3-0ubuntu2 3) Login. gnome-keyring unlocks "login" features including for google chrome 4) gnome-keyring is not unlocked, chrome takes 2 minutes to open and with no secure password features(sync) functioning. For the past couple days, chrome on Ubuntu 16.04 takes a REALLY long time (maybe 2 minutes) to start. Once chrome is started, I am not able to sync and any secure password features are broken. I found out this is due to gnome-keyring not being unlocked at login. There's also no way to unlock the "login" portion of the keyring from the running daemon by default. I have to kill the gnome-keyring process and start without "--login" as a parameter. Then the "login" section shows up which I'm able to unlock. From there chrome starts up instantly but asks the following: Enter password to unlock your login keyring The login keyring did not get unlocked when you logged into your computer After that, all of it's sync and secure features are functional. Starting google-chrome-stable from a command line at boot without running the above workaround shows the following error messages: Gkr-Message: secret service operation failed: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. Gkr-Message: secret service operation failed: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. [4364:4393:0510/100407.740292:ERROR:token_service_table.cc(130)] Failed to decrypt token for service AccountId-108842767310111573264 [4364:4445:0510/100407.740292:ERROR:gcm_store_impl.cc(929)] Failed to restore security token. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-keyring 3.18.3-0ubuntu2 ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-52-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: GNOME-Flashback:Unity Date: Wed May 10 09:43:37 2017 SourcePackage: gnome-keyring UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1689825/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1811588] Re: Seahorse doesn't show passwords anymore
Hi Olivier, Yes, that was it :) Under "View" I see two categories (Personal / Trusted), but no way to assign the saved passwords to them. Is it a bug? Thanks -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to seahorse in Ubuntu. https://bugs.launchpad.net/bugs/1811588 Title: Seahorse doesn't show passwords anymore Status in seahorse package in Ubuntu: New Bug description: After upgrade to Ubuntu 18.10, Seahorse doesn't show passwords anymore. Here the behavior: 1. I open seahorse and I see Certificates, GPG keys, secure shell. 2. After ~10 seconds, the Passwords section appears 3. It contains two folders: Login and Default. 4. Both folders are empty and saved passwords are not visible. I already removed "dbus-user-session" as suggested here: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1689825 But it didn't solve. Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/1811588/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1811588] [NEW] Seahorse doesn't show passwords anymore
Public bug reported: After upgrade to Ubuntu 18.10, Seahorse doesn't show passwords anymore. Here the behavior: 1. I open seahorse and I see Certificates, GPG keys, secure shell. 2. After ~10 seconds, the Passwords section appears 3. It contains two folders: Login and Default. 4. Both folders are empty and saved passwords are not visible. I already removed "dbus-user-session" as suggested here: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1689825 But it didn't solve. Thanks ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1811588 Title: Seahorse doesn't show passwords anymore Status in chromium-browser package in Ubuntu: New Bug description: After upgrade to Ubuntu 18.10, Seahorse doesn't show passwords anymore. Here the behavior: 1. I open seahorse and I see Certificates, GPG keys, secure shell. 2. After ~10 seconds, the Passwords section appears 3. It contains two folders: Login and Default. 4. Both folders are empty and saved passwords are not visible. I already removed "dbus-user-session" as suggested here: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1689825 But it didn't solve. Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1811588/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1742482] Re: Double-click doesn't open default application
** Summary changed: - Bluefish asks to download files from Nautilus FTP window + Double-click doesn't open default application ** Description changed: Ubuntu 18.04 Nautilus 1:3.26.0-0ubuntu1 - Bluefish 2.2.9-1 + Bluefish 2.2.10 - When I open a file from a FTP server browsed with Nautilus, Bluefish - asks to download the file instead of open it as it was in the previous - versions. + When I open a .php file from a FTP server browsed with Nautilus, Chrome + is opened instead of the default application Bluefish. Steps to reproduce: - 1. Connect to an FTP server via Nautilus - 2. Open the file with Nautilus - 3. Nautilus will ask for the download location + 1. Connect to an FTP server via Nautilus + 2a. Double-click on a .php file: chrome opens and the file is downloaded + 2b. Right click and select 'open with' and then Bluefish: the file is opened in bluefish as expected - If I try to open the same file with gedit it works well, that's why I - think is Bluefish bug. + So, on the double-click from Nautilus the wrong app (chrome!) is opened + even if the .php files are associated with bluefish. Thanks ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluefish 2.2.9-1 ProcVersionSignature: Ubuntu 4.14.0-15.18-generic 4.14.12 Uname: Linux 4.14.0-15-generic x86_64 ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jan 10 17:12:27 2018 ExecutablePath: /usr/bin/bluefish InstallationDate: Installed on 2015-12-07 (765 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: bluefish UpgradeStatus: No upgrade log present (probably fresh install) -- 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/1742482 Title: Double-click doesn't open default application Status in nautilus package in Ubuntu: New Bug description: Ubuntu 18.04 Nautilus 1:3.26.0-0ubuntu1 Bluefish 2.2.10 When I open a .php file from a FTP server browsed with Nautilus, Chrome is opened instead of the default application Bluefish. Steps to reproduce: 1. Connect to an FTP server via Nautilus 2a. Double-click on a .php file: chrome opens and the file is downloaded 2b. Right click and select 'open with' and then Bluefish: the file is opened in bluefish as expected So, on the double-click from Nautilus the wrong app (chrome!) is opened even if the .php files are associated with bluefish. Thanks ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluefish 2.2.9-1 ProcVersionSignature: Ubuntu 4.14.0-15.18-generic 4.14.12 Uname: Linux 4.14.0-15-generic x86_64 ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jan 10 17:12:27 2018 ExecutablePath: /usr/bin/bluefish InstallationDate: Installed on 2015-12-07 (765 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: bluefish UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1742482/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
