[Desktop-packages] [Bug 1748831] Re: pitivi (UnicodeDecodeError) _newProjectLoadingCb → _setScenarioFile → decode
** Summary changed:
-
/usr/bin/pitivi:UnicodeDecodeError:_newProjectLoadingCb:_setScenarioFile:decode
+ pitivi (UnicodeDecodeError) _newProjectLoadingCb → _setScenarioFile → decode
** Description changed:
The Ubuntu Error Tracker has been receiving reports about a problem regarding
pitivi. This problem was most recently seen with package version 0.99-2, the
problem page at
https://errors.ubuntu.com/problem/4661dc71aaa3ed958acb58e57ea04dea58ad1338
contains more details, including versions of packages affected, stacktrace or
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software
developer, you can request it at http://forms.canonical.com/reports/.
+
+
+ Traceback (most recent call last):
+ File "/usr/lib/x86_64-linux-gnu/pitivi/python/pitivi/application.py", line
259, in _newProjectLoadingCb
+ self._setScenarioFile(uri)
+ File "/usr/lib/x86_64-linux-gnu/pitivi/python/pitivi/application.py", line
254, in _setScenarioFile
+ content = project.read().replace("\n", "")
+ File "/usr/lib/python3.5/codecs.py", line 321, in decode
+ (result, consumed) = self._buffer_decode(data, self.errors, final)
+ UnicodeDecodeError: 'utf-8' codec can't decode byte 0xb2 in position 54:
invalid start byte
** Changed in: pitivi (Ubuntu)
Importance: Undecided => Medium
** Changed in: pitivi (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pitivi in Ubuntu.
https://bugs.launchpad.net/bugs/1748831
Title:
pitivi (UnicodeDecodeError) _newProjectLoadingCb → _setScenarioFile →
decode
Status in pitivi package in Ubuntu:
Triaged
Bug description:
The Ubuntu Error Tracker has been receiving reports about a problem regarding
pitivi. This problem was most recently seen with package version 0.99-2, the
problem page at
https://errors.ubuntu.com/problem/4661dc71aaa3ed958acb58e57ea04dea58ad1338
contains more details, including versions of packages affected, stacktrace or
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software
developer, you can request it at http://forms.canonical.com/reports/.
Traceback (most recent call last):
File "/usr/lib/x86_64-linux-gnu/pitivi/python/pitivi/application.py", line
259, in _newProjectLoadingCb
self._setScenarioFile(uri)
File "/usr/lib/x86_64-linux-gnu/pitivi/python/pitivi/application.py", line
254, in _setScenarioFile
content = project.read().replace("\n", "")
File "/usr/lib/python3.5/codecs.py", line 321, in decode
(result, consumed) = self._buffer_decode(data, self.errors, final)
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xb2 in position 54:
invalid start byte
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pitivi/+bug/1748831/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1748563] Re: /usr/bin/eog:11:gtk_tree_model_get_valist:gtk_tree_model_get:is_file_in_list_store:is_file_in_list_store_file:file_monitor_changed_cb
Fixed in bionic. ** Changed in: eog (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to eog in Ubuntu. https://bugs.launchpad.net/bugs/1748563 Title: /usr/bin/eog:11:gtk_tree_model_get_valist:gtk_tree_model_get:is_file_in_list_store:is_file_in_list_store_file:file_monitor_changed_cb Status in eog package in Ubuntu: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding eog. This problem was most recently seen with package version 3.26.1-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/2e739466ac6b0cecc40e58fd7ec888752657ccdf contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eog/+bug/1748563/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1747717] Re: package gnome-menus 3.13.3-11ubuntu1 failed to install/upgrade: triggers looping, abandoned - gnome-menus -> ufw
>From term.log dpkg: cycle found while processing triggers: chain of packages whose triggers are or may be responsible: gnome-menus -> ufw packages' pending triggers which are or may be unresolvable: gnome-menus: /usr/share/applications systemd: /etc/init.d libc-bin: ldconfig initramfs-tools: update-initramfs menu: /usr/share/menu ureadahead: /etc/init.d tex-common: texmf-format gconf2: /usr/share/GConf/gsettings ufw: /etc/ufw/applications.d dpkg: error processing package gnome-menus (--configure): triggers looping, abandoned ** Also affects: dpkg (Ubuntu) Importance: Undecided Status: New ** Changed in: dpkg (Ubuntu) Importance: Undecided => High ** Tags added: rls-bb-incoming -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-menus in Ubuntu. https://bugs.launchpad.net/bugs/1747717 Title: package gnome-menus 3.13.3-11ubuntu1 failed to install/upgrade: triggers looping, abandoned - gnome-menus -> ufw Status in dpkg package in Ubuntu: New Status in gnome-menus package in Ubuntu: Confirmed Bug description: using the bionic beaver version ProblemType: Package DistroRelease: Ubuntu 18.04 Package: gnome-menus 3.13.3-11ubuntu1 Uname: Linux 4.15.1-041501-generic x86_64 ApportVersion: 2.20.8-0ubuntu8 Architecture: amd64 Date: Tue Feb 6 23:00:47 2018 Dependencies: ErrorMessage: triggers looping, abandoned Python3Details: /usr/bin/python3.6, Python 3.6.4, python3-minimal, 3.6.4-1 PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4 RelatedPackageVersions: dpkg 1.19.0.5ubuntu1 apt 1.6~alpha7ubuntu1 SourcePackage: gnome-menus Title: package gnome-menus 3.13.3-11ubuntu1 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1747717/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1748831] [NEW] pitivi (UnicodeDecodeError) _newProjectLoadingCb → _setScenarioFile → decode
Public bug reported:
The Ubuntu Error Tracker has been receiving reports about a problem regarding
pitivi. This problem was most recently seen with package version 0.99-2, the
problem page at
https://errors.ubuntu.com/problem/4661dc71aaa3ed958acb58e57ea04dea58ad1338
contains more details, including versions of packages affected, stacktrace or
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software
developer, you can request it at http://forms.canonical.com/reports/.
Traceback (most recent call last):
File "/usr/lib/x86_64-linux-gnu/pitivi/python/pitivi/application.py", line
259, in _newProjectLoadingCb
self._setScenarioFile(uri)
File "/usr/lib/x86_64-linux-gnu/pitivi/python/pitivi/application.py", line
254, in _setScenarioFile
content = project.read().replace("\n", "")
File "/usr/lib/python3.5/codecs.py", line 321, in decode
(result, consumed) = self._buffer_decode(data, self.errors, final)
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xb2 in position 54:
invalid start byte
** Affects: pitivi (Ubuntu)
Importance: Medium
Status: Triaged
** Tags: artful bionic xenial yakkety zesty
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pitivi in Ubuntu.
https://bugs.launchpad.net/bugs/1748831
Title:
pitivi (UnicodeDecodeError) _newProjectLoadingCb → _setScenarioFile →
decode
Status in pitivi package in Ubuntu:
Triaged
Bug description:
The Ubuntu Error Tracker has been receiving reports about a problem regarding
pitivi. This problem was most recently seen with package version 0.99-2, the
problem page at
https://errors.ubuntu.com/problem/4661dc71aaa3ed958acb58e57ea04dea58ad1338
contains more details, including versions of packages affected, stacktrace or
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software
developer, you can request it at http://forms.canonical.com/reports/.
Traceback (most recent call last):
File "/usr/lib/x86_64-linux-gnu/pitivi/python/pitivi/application.py", line
259, in _newProjectLoadingCb
self._setScenarioFile(uri)
File "/usr/lib/x86_64-linux-gnu/pitivi/python/pitivi/application.py", line
254, in _setScenarioFile
content = project.read().replace("\n", "")
File "/usr/lib/python3.5/codecs.py", line 321, in decode
(result, consumed) = self._buffer_decode(data, self.errors, final)
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xb2 in position 54:
invalid start byte
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pitivi/+bug/1748831/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1748787] Re: pitivi crashed with AttributeError in _create_next_thumb(): 'NoneType' object has no attribute 'seek'
** Information type changed from Private to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pitivi in Ubuntu. https://bugs.launchpad.net/bugs/1748787 Title: pitivi crashed with AttributeError in _create_next_thumb(): 'NoneType' object has no attribute 'seek' Status in pitivi package in Ubuntu: New Bug description: A crash occurred that I was configuring rendering, but the program kept working. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: pitivi 0.99-2 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.8-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Feb 11 18:52:39 2018 ExecutablePath: /usr/bin/pitivi InstallationDate: Installed on 2017-11-12 (91 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171109) InterpreterPath: /usr/bin/python3.6 ProcCmdline: /usr/bin/python3 /usr/bin/pitivi Python3Details: /usr/bin/python3.6, Python 3.6.4, python3-minimal, 3.6.4-1 PythonArgs: ['/usr/bin/pitivi'] PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4 SourcePackage: pitivi Title: pitivi crashed with AttributeError in _create_next_thumb(): 'NoneType' object has no attribute 'seek' Traceback: Traceback (most recent call last): File "/usr/lib/x86_64-linux-gnu/pitivi/python/pitivi/timeline/previewers.py", line 556, in _create_next_thumb self.pipeline.seek(1.0, AttributeError: 'NoneType' object has no attribute 'seek' UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pitivi/+bug/1748787/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1748716] Re: package gnome-menus 3.13.3-11ubuntu1 failed to install/upgrade: bloqué en boucle sur le traitement des actions différées (« triggers »), abandon
*** This bug is a duplicate of bug 1747717 *** https://bugs.launchpad.net/bugs/1747717 ** This bug has been marked a duplicate of bug 1747717 package gnome-menus 3.13.3-11ubuntu1 failed to install/upgrade: triggers looping, abandoned - gnome-menus -> ufw -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-menus in Ubuntu. https://bugs.launchpad.net/bugs/1748716 Title: package gnome-menus 3.13.3-11ubuntu1 failed to install/upgrade: bloqué en boucle sur le traitement des actions différées (« triggers »), abandon Status in gnome-menus package in Ubuntu: New Bug description: erreur d'installation lors de la mise à jour. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: gnome-menus 3.13.3-11ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.8-0ubuntu8 Architecture: amd64 Date: Sun Feb 11 10:15:38 2018 Dependencies: ErrorMessage: bloqué en boucle sur le traitement des actions différées (« triggers »), abandon Python3Details: /usr/bin/python3.6, Python 3.6.4, python3-minimal, 3.6.4-1 PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu1 apt 1.6~alpha7ubuntu1 SourcePackage: gnome-menus Title: package gnome-menus 3.13.3-11ubuntu1 failed to install/upgrade: bloqué en boucle sur le traitement des actions différées (« triggers »), abandon UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-menus/+bug/1748716/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1748783] Re: package gnome-menus 3.13.3-11ubuntu1 failed to install/upgrade: triggers looping, abandoned
*** This bug is a duplicate of bug 1747717 *** https://bugs.launchpad.net/bugs/1747717 ** This bug has been marked a duplicate of bug 1747717 package gnome-menus 3.13.3-11ubuntu1 failed to install/upgrade: triggers looping, abandoned - gnome-menus -> ufw -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-menus in Ubuntu. https://bugs.launchpad.net/bugs/1748783 Title: package gnome-menus 3.13.3-11ubuntu1 failed to install/upgrade: triggers looping, abandoned Status in gnome-menus package in Ubuntu: New Bug description: Happens every time I log in to any account on this computer. Not a lot of details to be gleaned from the initial error reporting. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: gnome-menus 3.13.3-11ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.8-0ubuntu8 Architecture: amd64 Date: Sun Feb 11 10:39:25 2018 Dependencies: ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2018-01-22 (20 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180121) Python3Details: /usr/bin/python3.6, Python 3.6.4, python3-minimal, 3.6.4-1 PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4 RelatedPackageVersions: dpkg 1.19.0.5ubuntu1 apt 1.6~alpha7ubuntu1 SourcePackage: gnome-menus Title: package gnome-menus 3.13.3-11ubuntu1 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-menus/+bug/1748783/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1747203] Re: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, abandoned
*** This bug is a duplicate of bug 1747717 *** https://bugs.launchpad.net/bugs/1747717 ** This bug has been marked a duplicate of bug 1747717 package gnome-menus 3.13.3-11ubuntu1 failed to install/upgrade: triggers looping, abandoned - gnome-menus -> ufw -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-menus in Ubuntu. https://bugs.launchpad.net/bugs/1747203 Title: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, abandoned Status in gnome-menus package in Ubuntu: Confirmed Bug description: during upgrade from 16.10 to 17.10 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: gnome-menus 3.13.3-6ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98 Uname: Linux 4.4.0-112-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Sat Feb 3 23:35:32 2018 Dependencies: ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2016-02-26 (708 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.24 SourcePackage: gnome-menus Title: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to xenial on 2018-02-03 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-menus/+bug/1747203/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1748752] Re: package gnome-menus 3.13.3-11ubuntu1 failed to install/upgrade: triggers looping, abandoned
*** This bug is a duplicate of bug 1747717 *** https://bugs.launchpad.net/bugs/1747717 ** This bug has been marked a duplicate of bug 1747717 package gnome-menus 3.13.3-11ubuntu1 failed to install/upgrade: triggers looping, abandoned - gnome-menus -> ufw -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-menus in Ubuntu. https://bugs.launchpad.net/bugs/1748752 Title: package gnome-menus 3.13.3-11ubuntu1 failed to install/upgrade: triggers looping, abandoned Status in gnome-menus package in Ubuntu: Confirmed Bug description: This seems to be similar to bugs: #1738194 #1746776 etc ProblemType: Package DistroRelease: Ubuntu 18.04 Package: gnome-menus 3.13.3-11ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.8-0ubuntu8 Architecture: amd64 Date: Sun Feb 11 21:06:53 2018 Dependencies: ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2017-07-24 (201 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170723) Python3Details: /usr/bin/python3.6, Python 3.6.4, python3-minimal, 3.6.4-1 PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu1 apt 1.6~alpha7ubuntu1 SourcePackage: gnome-menus Title: package gnome-menus 3.13.3-11ubuntu1 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-menus/+bug/1748752/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1745785] Re: Package failed to install - triggers looping: gnome-menus -> ufw
*** This bug is a duplicate of bug 1747717 *** https://bugs.launchpad.net/bugs/1747717 ** This bug has been marked a duplicate of bug 1747717 package gnome-menus 3.13.3-11ubuntu1 failed to install/upgrade: triggers looping, abandoned - gnome-menus -> ufw -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-menus in Ubuntu. https://bugs.launchpad.net/bugs/1745785 Title: Package failed to install - triggers looping: gnome-menus -> ufw Status in dpkg package in Ubuntu: New Status in gnome-menus package in Ubuntu: New Bug description: This error pops up about 30 seconds into any desktop session after logging in. No side effects other than the crash report popping up. Ping me if you need me to do additional testing, need logs, etc. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: gnome-menus 3.13.3-11ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-30.33-generic 4.13.13 Uname: Linux 4.13.0-30-generic x86_64 ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 Date: Fri Jan 19 18:59:05 2018 Dependencies: ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2017-10-27 (92 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Python3Details: /usr/bin/python3.6, Python 3.6.4, python3-minimal, 3.6.4-1 PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4 RelatedPackageVersions: dpkg 1.19.0.4ubuntu1 apt 1.6~alpha7 SourcePackage: gnome-menus Title: package gnome-menus 3.13.3-11ubuntu1 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to bionic on 2018-01-19 (7 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1745785/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1747012] Re: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, abandoned
*** This bug is a duplicate of bug 1747717 *** https://bugs.launchpad.net/bugs/1747717 ** This bug has been marked a duplicate of bug 1747717 package gnome-menus 3.13.3-11ubuntu1 failed to install/upgrade: triggers looping, abandoned - gnome-menus -> ufw -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-menus in Ubuntu. https://bugs.launchpad.net/bugs/1747012 Title: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, abandoned Status in gnome-menus package in Ubuntu: New Bug description: the top bar the left bar and the plank have vanished and are not displaying ProblemType: Package DistroRelease: Ubuntu 16.04 Package: gnome-menus 3.13.3-6ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98 Uname: Linux 4.4.0-112-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Fri Feb 2 20:33:19 2018 Dependencies: ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2017-02-11 (355 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.24 SourcePackage: gnome-menus Title: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to xenial on 2018-02-02 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-menus/+bug/1747012/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1672297] Re: gnome-shell uses lots of memory, and grows over time
If we find a fix that works, then yes it will be backported to 17.10.
--
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/1672297
Title:
gnome-shell uses lots of memory, and grows over time
Status in GNOME Shell:
Unknown
Status in Mutter:
Fix Released
Status in gnome-shell package in Ubuntu:
Triaged
Status in mutter package in Ubuntu:
Triaged
Bug description:
gnome-shell's RSS is growing by 1 MiB every few minutes, and is now at
almost 2 GiB.
user 3039 1.8 16.1 4302340 1968476 tty2 Sl+ Mar09 120:17
/usr/bin/gnome-shell
strace output is voluminous; here is a representative sample:
poll([{fd=5, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=5, revents=POLLOUT}])
writev(5, [{"\231\n\10\0\n\0
\0\0\0\0\0\0\0\0\0\0\0\0\0\1\0\0\0\0\0\0\0\0\0\0\0", 32}], 1) = 32
poll([{fd=5, events=POLLIN}], 1, -1)= 1 ([{fd=5, revents=POLLIN}])
recvmsg(5, {msg_name(0)=NULL,
msg_iov(1)=[{"\1\0{\224\0\0\0\0H\0\0\0\0\23\266\32\0\0\0\0\201\242\204\0\0\0\0\0\261.\0\0",
4096}], msg_controllen=0, msg_flags=0}, 0) = 32
recvmsg(5, 0x7fff60efac90, 0) = -1 EAGAIN (Resource temporarily
unavailable)
recvmsg(5, 0x7fff60efac90, 0) = -1 EAGAIN (Resource temporarily
unavailable)
poll([{fd=5, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=5, revents=POLLOUT}])
writev(5, [{"\212\5\4\0a\2228\0y\3\5\0%\3\27\4\231\6\5\0\n\0
\0a\2228\0\0\0\0\0"..., 36}, {NULL, 0}, {"", 0}], 3) = 36
poll([{fd=5, events=POLLIN}], 1, -1)= 1 ([{fd=5, revents=POLLIN}])
recvmsg(5, {msg_name(0)=NULL,
msg_iov(1)=[{"\1\0}\224\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0",
4096}], msg_controllen=0, msg_flags=0}, 0) = 32
recvmsg(5, 0x7fff60efac90, 0) = -1 EAGAIN (Resource temporarily
unavailable)
poll([{fd=5, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=5, revents=POLLOUT}])
writev(5, [{"\212\n\2\0a\2228\0", 8}, {NULL, 0}, {"", 0}], 3) = 8
recvmsg(5, 0x7fff60efb020, 0) = -1 EAGAIN (Resource temporarily
unavailable)
recvmsg(12, 0x7fff60efb000, 0) = -1 EAGAIN (Resource temporarily
unavailable)
poll([{fd=4, events=POLLIN}, {fd=5, events=POLLIN}, {fd=11, events=POLLIN},
{fd=12, events=POLLIN}, {fd=14, events=POLLIN}, {fd=16, events=POLLIN}, {fd=26,
events=POLLIN}, {fd=29, events=POLLIN}, {fd=32, events=POLLIN}, {fd=34,
events=POLLIN}, {fd=37, events=POLLIN}, {fd=38, events=POLLIN}, {fd=40,
events=POLLIN}, {fd=42, events=POLLIN}, {fd=43, events=POLLIN}], 15, 0) = 0
(Timeout)
recvmsg(5, 0x7fff60efb040, 0) = -1 EAGAIN (Resource temporarily
unavailable)
recvmsg(5, 0x7fff60efb020, 0) = -1 EAGAIN (Resource temporarily
unavailable)
recvmsg(12, 0x7fff60efb000, 0) = -1 EAGAIN (Resource temporarily
unavailable)
poll([{fd=4, events=POLLIN}, {fd=5, events=POLLIN}, {fd=11, events=POLLIN},
{fd=12, events=POLLIN}, {fd=14, events=POLLIN}, {fd=16, events=POLLIN}, {fd=26,
events=POLLIN}, {fd=29, events=POLLIN}, {fd=32, events=POLLIN}, {fd=34,
events=POLLIN}, {fd=37, events=POLLIN}, {fd=38, events=POLLIN}, {fd=40,
events=POLLIN}, {fd=42, events=POLLIN}, {fd=43, events=POLLIN}], 15, 0) = 0
(Timeout)
recvmsg(5, 0x7fff60efb040, 0) = -1 EAGAIN (Resource temporarily
unavailable)
open("/proc/self/stat", O_RDONLY) = 36
fstat(36, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0
fcntl(36, F_GETFL) = 0x8000 (flags O_RDONLY|O_LARGEFILE)
fstat(36, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0
read(36, "3039 (gnome-shell) R 2930 2917 2"..., 4096) = 354
read(36, "", 3072) = 0
close(36) = 0
recvmsg(5, 0x7fff60efb020, 0) = -1 EAGAIN (Resource temporarily
unavailable)
recvmsg(12, 0x7fff60efb000, 0) = -1 EAGAIN (Resource temporarily
unavailable)
poll([{fd=4, events=POLLIN}, {fd=5, events=POLLIN}, {fd=11, events=POLLIN},
{fd=12, events=POLLIN}, {fd=14, events=POLLIN}, {fd=16, events=POLLIN}, {fd=26,
events=POLLIN}, {fd=29, events=POLLIN}, {fd=32, events=POLLIN}, {fd=34,
events=POLLIN}, {fd=37, events=POLLIN}, {fd=38, events=POLLIN}, {fd=40,
events=POLLIN}, {fd=42, events=POLLIN}, {fd=43, events=POLLIN}], 15, 117885) =
1 ([{fd=4, revents=POLLIN}])
read(4, "\1\0\0\0\0\0\0\0", 16) = 8
recvmsg(5, 0x7fff60efb040, 0) = -1 EAGAIN (Resource temporarily
unavailable)
recvmsg(5, 0x7fff60efb020, 0) = -1 EAGAIN (Resource temporarily
unavailable)
recvmsg(12, {msg_name(0)=NULL,
msg_iov(1)=[{"[\2\327&h\0@\0i\0@\0(nu\22\n\0I\0\336\2\232\1\265\0038\2\362\2\355\1",
4096}], msg_controllen=0, msg_flags=0}, 0) = 32
recvmsg(12, 0x7fff60efb000, 0) = -1 EAGAIN (Resource temporarily
unavailable)
poll([{fd=4, events=POLLIN}, {fd=5, events=POLLIN}, {fd=11, events=POLLIN},
{fd=12, events=POLLIN}, {fd=14, events=POLLIN}, {fd=16, events=POLLIN}, {fd=26,
events=POLLIN}, {fd=29, even
[Desktop-packages] [Bug 1672297] Re: gnome-shell uses lots of memory, and grows over time
So does that mean this is a wontfix for 17.10, the current version?
I had to double my RAM to 16GB just to get more than a day out of gnome-
shell at work, otherwise as the day goes on, each notification I receive
hangs the system for a few seconds and locking and unlocking the screen
can take up to a minute by the end of the day. If I happened to be at
the bottom of a keystroke at the time it hangs, it acts like the key was
held down for the duration - a nightmare in Vim. As others have said,
actions like pressing the super key or switching windows seem to consume
a few MB each time that it never seems to give back.
--
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/1672297
Title:
gnome-shell uses lots of memory, and grows over time
Status in GNOME Shell:
Unknown
Status in Mutter:
Fix Released
Status in gnome-shell package in Ubuntu:
Triaged
Status in mutter package in Ubuntu:
Triaged
Bug description:
gnome-shell's RSS is growing by 1 MiB every few minutes, and is now at
almost 2 GiB.
user 3039 1.8 16.1 4302340 1968476 tty2 Sl+ Mar09 120:17
/usr/bin/gnome-shell
strace output is voluminous; here is a representative sample:
poll([{fd=5, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=5, revents=POLLOUT}])
writev(5, [{"\231\n\10\0\n\0
\0\0\0\0\0\0\0\0\0\0\0\0\0\1\0\0\0\0\0\0\0\0\0\0\0", 32}], 1) = 32
poll([{fd=5, events=POLLIN}], 1, -1)= 1 ([{fd=5, revents=POLLIN}])
recvmsg(5, {msg_name(0)=NULL,
msg_iov(1)=[{"\1\0{\224\0\0\0\0H\0\0\0\0\23\266\32\0\0\0\0\201\242\204\0\0\0\0\0\261.\0\0",
4096}], msg_controllen=0, msg_flags=0}, 0) = 32
recvmsg(5, 0x7fff60efac90, 0) = -1 EAGAIN (Resource temporarily
unavailable)
recvmsg(5, 0x7fff60efac90, 0) = -1 EAGAIN (Resource temporarily
unavailable)
poll([{fd=5, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=5, revents=POLLOUT}])
writev(5, [{"\212\5\4\0a\2228\0y\3\5\0%\3\27\4\231\6\5\0\n\0
\0a\2228\0\0\0\0\0"..., 36}, {NULL, 0}, {"", 0}], 3) = 36
poll([{fd=5, events=POLLIN}], 1, -1)= 1 ([{fd=5, revents=POLLIN}])
recvmsg(5, {msg_name(0)=NULL,
msg_iov(1)=[{"\1\0}\224\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0",
4096}], msg_controllen=0, msg_flags=0}, 0) = 32
recvmsg(5, 0x7fff60efac90, 0) = -1 EAGAIN (Resource temporarily
unavailable)
poll([{fd=5, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=5, revents=POLLOUT}])
writev(5, [{"\212\n\2\0a\2228\0", 8}, {NULL, 0}, {"", 0}], 3) = 8
recvmsg(5, 0x7fff60efb020, 0) = -1 EAGAIN (Resource temporarily
unavailable)
recvmsg(12, 0x7fff60efb000, 0) = -1 EAGAIN (Resource temporarily
unavailable)
poll([{fd=4, events=POLLIN}, {fd=5, events=POLLIN}, {fd=11, events=POLLIN},
{fd=12, events=POLLIN}, {fd=14, events=POLLIN}, {fd=16, events=POLLIN}, {fd=26,
events=POLLIN}, {fd=29, events=POLLIN}, {fd=32, events=POLLIN}, {fd=34,
events=POLLIN}, {fd=37, events=POLLIN}, {fd=38, events=POLLIN}, {fd=40,
events=POLLIN}, {fd=42, events=POLLIN}, {fd=43, events=POLLIN}], 15, 0) = 0
(Timeout)
recvmsg(5, 0x7fff60efb040, 0) = -1 EAGAIN (Resource temporarily
unavailable)
recvmsg(5, 0x7fff60efb020, 0) = -1 EAGAIN (Resource temporarily
unavailable)
recvmsg(12, 0x7fff60efb000, 0) = -1 EAGAIN (Resource temporarily
unavailable)
poll([{fd=4, events=POLLIN}, {fd=5, events=POLLIN}, {fd=11, events=POLLIN},
{fd=12, events=POLLIN}, {fd=14, events=POLLIN}, {fd=16, events=POLLIN}, {fd=26,
events=POLLIN}, {fd=29, events=POLLIN}, {fd=32, events=POLLIN}, {fd=34,
events=POLLIN}, {fd=37, events=POLLIN}, {fd=38, events=POLLIN}, {fd=40,
events=POLLIN}, {fd=42, events=POLLIN}, {fd=43, events=POLLIN}], 15, 0) = 0
(Timeout)
recvmsg(5, 0x7fff60efb040, 0) = -1 EAGAIN (Resource temporarily
unavailable)
open("/proc/self/stat", O_RDONLY) = 36
fstat(36, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0
fcntl(36, F_GETFL) = 0x8000 (flags O_RDONLY|O_LARGEFILE)
fstat(36, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0
read(36, "3039 (gnome-shell) R 2930 2917 2"..., 4096) = 354
read(36, "", 3072) = 0
close(36) = 0
recvmsg(5, 0x7fff60efb020, 0) = -1 EAGAIN (Resource temporarily
unavailable)
recvmsg(12, 0x7fff60efb000, 0) = -1 EAGAIN (Resource temporarily
unavailable)
poll([{fd=4, events=POLLIN}, {fd=5, events=POLLIN}, {fd=11, events=POLLIN},
{fd=12, events=POLLIN}, {fd=14, events=POLLIN}, {fd=16, events=POLLIN}, {fd=26,
events=POLLIN}, {fd=29, events=POLLIN}, {fd=32, events=POLLIN}, {fd=34,
events=POLLIN}, {fd=37, events=POLLIN}, {fd=38, events=POLLIN}, {fd=40,
events=POLLIN}, {fd=42, events=POLLIN}, {fd=43, events=POLLIN}], 15, 117885) =
1 ([{fd=4, revents=POLLIN}])
read(4, "\1\0\0\0\0\0\0\0", 16) = 8
recvmsg(5, 0x7fff60efb040, 0) = -1 EAGAIN (Resource tempor
[Desktop-packages] [Bug 1729963] Re: chromium-browser crashed in OnConnectionDisconnectedFilter()
** Tags added: trusty -- 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/1729963 Title: chromium-browser crashed in OnConnectionDisconnectedFilter() Status in chromium-browser package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding chromium-browser. This problem was most recently seen with package version 62.0.3202.62-0ubuntu0.17.10.1380, the problem page at https://errors.ubuntu.com/problem/ac572b4fed36983c400b47046ea2445bd14d3884 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1729963/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1658723] Re: /usr/lib/chromium-browser/chromium-browser:6:base::debug::BreakDebugger:logging::LogMessage::~LogMessage:dbus::Bus::OnConnectionDisconnectedFilter:dbus_connection_
*** This bug is a duplicate of bug 1729963 *** https://bugs.launchpad.net/bugs/1729963 ** This bug has been marked a duplicate of bug 1729963 chromium-browser crashed in OnConnectionDisconnectedFilter() -- 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/1658723 Title: /usr/lib/chromium-browser/chromium- browser:6:base::debug::BreakDebugger:logging::LogMessage::~LogMessage:dbus::Bus::OnConnectionDisconnectedFilter:dbus_connection_dispatch:dbus::Bus::ProcessAllIncomingDataIfAny Status in chromium-browser package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding chromium-browser. This problem was most recently seen with package version 55.0.2883.87-0ubuntu0.16.04.1263, the problem page at https://errors.ubuntu.com/problem/780da53650f75928b6557da788e77730c4040c91 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1658723/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1747243] Re: chromium-browser crashed with SIGABRT in base::debug::BreakDebugger()
*** This bug is a duplicate of bug 1729963 *** https://bugs.launchpad.net/bugs/1729963 ** This bug is no longer a duplicate of bug 1658723 /usr/lib/chromium-browser/chromium-browser:6:base::debug::BreakDebugger:logging::LogMessage::~LogMessage:dbus::Bus::OnConnectionDisconnectedFilter:dbus_connection_dispatch:dbus::Bus::ProcessAllIncomingDataIfAny ** This bug has been marked a duplicate of bug 1729963 chromium-browser crashed in OnConnectionDisconnectedFilter() -- 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/1747243 Title: chromium-browser crashed with SIGABRT in base::debug::BreakDebugger() Status in chromium-browser package in Ubuntu: Confirmed Bug description: None ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: chromium-browser 64.0.3282.119-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.8-0ubuntu8 Architecture: amd64 CrashCounter: 1 DRM.card0-DP-1: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-DP-2: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-DP-3: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-HDMI-A-1: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-HDMI-A-2: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-LVDS-1: enabled: enabled dpms: On status: connected edid-base64: AP///wAwrjNPAQOAHhN46s11kVVPiyYhUFQBAQEBAQEBAQEBAQEBAQEBsCegYFGELTAwIDYAL74QAAAZ1R+gQFGEGjAwIDYAL74QAAAZDwCQCjKQCigUAQBMo0JE/gBMVE4xNDFXRC1MMDUKADI= modes: 1440x900 1440x900 DRM.card0-VGA-1: enabled: disabled dpms: Off status: disconnected edid-base64: modes: Date: Sat Feb 3 16:01:01 2018 Desktop-Session: 'ubuntu-xorg' '/etc/xdg/xdg-ubuntu-xorg:/etc/xdg/xdg-ubuntu-xorg:/etc/xdg' '/usr/share/ubuntu-xorg:/usr/share/ubuntu-xorg:/usr/local/share:/usr/share:/var/lib/snapd/desktop' DetectedPlugins: Env: 'None' 'None' ExecutablePath: /usr/lib/chromium-browser/chromium-browser InstallationDate: Installed on 2018-02-01 (2 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180129) InstalledPlugins: /usr/lib/mozilla/plugins: => libgnome-shell-browser-plugin.so (size: 18856 bytes, mtime: Sat Dec 9 12:41:33 2017) Load-Avg-1min: 1.73 Load-Processes-Running-Percent: 0.2% MachineType: LENOVO 6474EC3 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcCmdline: /usr/lib/chromium-browser/chromium-browser\ --enable-pinch ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic root=UUID=86cf24c4-19fe-49af-b076-96df73e0bfd1 ro quiet splash vt.handoff=1 Signal: 6 SourcePackage: chromium-browser StacktraceTop: ?? () ?? () ?? () dbus_connection_dispatch () from /lib/x86_64-linux-gnu/libdbus-1.so.3 ?? () Title: chromium-browser crashed with SIGABRT in dbus_connection_dispatch() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 10/17/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 7UET94WW (3.24 ) dmi.board.name: 6474EC3 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr7UET94WW(3.24):bd10/17/2012:svnLENOVO:pn6474EC3:pvrThinkPadT400:rvnLENOVO:rn6474EC3:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T400 dmi.product.name: 6474EC3 dmi.product.version: ThinkPad T400 dmi.sys.vendor: LENOVO modified.conffile..etc.default.chromium-browser: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1747243/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1747977] Re: chromium-browser crashed with SIGABRT
*** This bug is a duplicate of bug 1729963 *** https://bugs.launchpad.net/bugs/1729963 ** This bug is no longer a duplicate of bug 1658723 /usr/lib/chromium-browser/chromium-browser:6:base::debug::BreakDebugger:logging::LogMessage::~LogMessage:dbus::Bus::OnConnectionDisconnectedFilter:dbus_connection_dispatch:dbus::Bus::ProcessAllIncomingDataIfAny ** This bug has been marked a duplicate of bug 1729963 chromium-browser crashed in OnConnectionDisconnectedFilter() -- 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/1747977 Title: chromium-browser crashed with SIGABRT Status in chromium-browser package in Ubuntu: New Bug description: after power on/boot. Apport popped up by itself, I had not yet started Chromium. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: chromium-browser 64.0.3282.140-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.8-0ubuntu8 Architecture: amd64 Date: Wed Feb 7 10:11:35 2018 DetectedPlugins: ExecutablePath: /usr/lib/chromium-browser/chromium-browser InstallationDate: Installed on 2017-05-26 (257 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcCmdline: /usr/lib/chromium-browser/chromium-browser\ --enable-pinch ProcEnviron: Signal: 6 SourcePackage: chromium-browser StacktraceTop: () () () dbus_connection_dispatch () at /lib/x86_64-linux-gnu/libdbus-1.so.3 () Title: chromium-browser crashed with SIGABRT UpgradeStatus: Upgraded to bionic on 2017-11-13 (86 days ago) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo wireshark modified.conffile..etc.default.chromium-browser: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1747977/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1748812] Re: cannot view wifi networks after resume from suspend
Could you also provide `lspci -nnk > lspci.log`? -- 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/1748812 Title: cannot view wifi networks after resume from suspend Status in network-manager package in Ubuntu: Confirmed Bug description: Hello, On 2 laptops (Dell XPS13 9360 with ath10k and Lenovo T530 with iwlwifi) I have the same issue: After resume from suspend nm-applet doesn't show any information about connected/available wi-fi connections. Please see screenshot in attach. I can see current connection via CLI: nmcli dev DEVICE TYPE STATE CONNECTION docker0 bridgeconnected docker0 wlp58s0 wifi connected Turris lo loopback unmanaged -- Now I have to run `killall nm-applet && nm-applet &` after every suspend. That fixes my issue I think it's a duplicate of https://bugs.launchpad.net/ubuntu/+source /network-manager/+bug/1589401 but I was asked to submit separate bug ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.6-0ubuntu0.16.04.2 Uname: Linux 4.15.0-041500rc9-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: Unity Date: Sun Feb 11 19:41:21 2018 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 EcryptfsInUse: Yes IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-10-06 (493 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 IpRoute: default via 192.168.1.1 dev wlp58s0 proto static metric 600 169.254.0.0/16 dev docker0 scope link metric 1000 linkdown 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 192.168.1.0/24 dev wlp58s0 proto kernel scope link src 192.168.1.137 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH docker0 bridgeconnected /org/freedesktop/NetworkManager/Devices/1 docker0 440d4ade-78be-45c3-a821-903971861d0c /org/freedesktop/NetworkManager/ActiveConnection/0 wlp58s0 wifi connected /org/freedesktop/NetworkManager/Devices/3 Turris e963-362e-4e4a-ac98-54af278d348d /org/freedesktop/NetworkManager/ActiveConnection/88 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.6connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1748812/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1747744] Re: [regression] Video playback in totem is corrupted in X11
WORKAROUND (1): Install these two together: https://launchpad.net/ubuntu/+source/mesa/17.2.4-0ubuntu2/+build/13697262/+files/libgl1-mesa-glx_17.2.4-0ubuntu2_amd64.deb https://launchpad.net/ubuntu/+source/mesa/17.2.4-0ubuntu2/+build/13697262/+files/libglapi-mesa_17.2.4-0ubuntu2_amd64.deb WORKAROUND (2): sudo apt remove gstreamer1.0-vaapi WORKAROUND (3): Log in to "Ubuntu on Wayland" instead of "Ubuntu". -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1747744 Title: [regression] Video playback in totem is corrupted in X11 Status in Mesa: In Progress Status in clutter-gst-3.0 package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in totem package in Ubuntu: Confirmed Bug description: Test case Log inti xorg session Install gstreamer1.0-vaapi plugin Play a supported video (- h.264/avc in .mp4, .mkv or .mov would suffice Expected: hardware decoded playback What happens: totally corrupted screen, see screenshots Does work ok in a wayland session $ vainfo libva info: VA-API version 1.0.0 libva info: va_getDriverName() returns 0 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so libva info: Found init function __vaDriverInit_1_0 libva info: va_openDriver() returns 0 vainfo: VA-API version: 1.0 (libva 2.0.0) vainfo: Driver version: Intel i965 driver for Intel(R) Haswell Mobile - 2.0.0 vainfo: Supported profile and entrypoints VAProfileMPEG2Simple: VAEntrypointVLD VAProfileMPEG2Simple: VAEntrypointEncSlice VAProfileMPEG2Main : VAEntrypointVLD VAProfileMPEG2Main : VAEntrypointEncSlice VAProfileH264ConstrainedBaseline: VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice VAProfileH264Main : VAEntrypointVLD VAProfileH264Main : VAEntrypointEncSlice VAProfileH264High : VAEntrypointVLD VAProfileH264High : VAEntrypointEncSlice VAProfileH264MultiviewHigh : VAEntrypointVLD VAProfileH264MultiviewHigh : VAEntrypointEncSlice VAProfileH264StereoHigh : VAEntrypointVLD VAProfileH264StereoHigh : VAEntrypointEncSlice VAProfileVC1Simple : VAEntrypointVLD VAProfileVC1Main: VAEntrypointVLD VAProfileVC1Advanced: VAEntrypointVLD VAProfileNone : VAEntrypointVideoProc VAProfileJPEGBaseline : VAEntrypointVLD ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gstreamer1.0-vaapi 1.12.4-1ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.8-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Feb 6 14:43:57 2018 InstallationDate: Installed on 2018-02-06 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180204) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gstreamer-vaapi UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1747744/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1748812] Re: cannot view wifi networks after resume from suspend
Yes it's Dell XPS 13 that comes with Ubuntu 16.04 preinstalled. But I have the same issue on Lenovo T530 where I installed Ubuntu manually. >From Dell XPS 13 9360: /etc/buildstamp kakaduplum Fri, 24 Jun 2016 10:26:40 + somerville-xenial-amd64-20160624-2 There is no /mnt/bto.xml. Here is list of files I have on /dev/nvme0n1p2: boot casper debs dell-e-star dists efi.factory factory install installer isolinux md5sum.txt pool prepackage.dell preseed scripts Please find dpkg.log in attachment ** Attachment added: "dpkg.log" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1748812/+attachment/5053415/+files/dpkg.log -- 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/1748812 Title: cannot view wifi networks after resume from suspend Status in network-manager package in Ubuntu: Confirmed Bug description: Hello, On 2 laptops (Dell XPS13 9360 with ath10k and Lenovo T530 with iwlwifi) I have the same issue: After resume from suspend nm-applet doesn't show any information about connected/available wi-fi connections. Please see screenshot in attach. I can see current connection via CLI: nmcli dev DEVICE TYPE STATE CONNECTION docker0 bridgeconnected docker0 wlp58s0 wifi connected Turris lo loopback unmanaged -- Now I have to run `killall nm-applet && nm-applet &` after every suspend. That fixes my issue I think it's a duplicate of https://bugs.launchpad.net/ubuntu/+source /network-manager/+bug/1589401 but I was asked to submit separate bug ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.6-0ubuntu0.16.04.2 Uname: Linux 4.15.0-041500rc9-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: Unity Date: Sun Feb 11 19:41:21 2018 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 EcryptfsInUse: Yes IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-10-06 (493 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 IpRoute: default via 192.168.1.1 dev wlp58s0 proto static metric 600 169.254.0.0/16 dev docker0 scope link metric 1000 linkdown 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 192.168.1.0/24 dev wlp58s0 proto kernel scope link src 192.168.1.137 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH docker0 bridgeconnected /org/freedesktop/NetworkManager/Devices/1 docker0 440d4ade-78be-45c3-a821-903971861d0c /org/freedesktop/NetworkManager/ActiveConnection/0 wlp58s0 wifi connected /org/freedesktop/NetworkManager/Devices/3 Turris e963-362e-4e4a-ac98-54af278d348d /org/freedesktop/NetworkManager/ActiveConnection/88 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.6connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1748812/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1748812] Re: cannot view wifi networks after resume from suspend
It looks like it is a preloaded Ubuntu system. Could you help to provide some logs as the followings? /etc/buildstamp `sudo mount /dev/sda2 /mnt` or `sudo mount /dev/nvme0n1p2 /mnt` and then attach /mnt/bto.xml dpkg -l > dpkg.log and then attach dpkg.log -- 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/1748812 Title: cannot view wifi networks after resume from suspend Status in network-manager package in Ubuntu: Confirmed Bug description: Hello, On 2 laptops (Dell XPS13 9360 with ath10k and Lenovo T530 with iwlwifi) I have the same issue: After resume from suspend nm-applet doesn't show any information about connected/available wi-fi connections. Please see screenshot in attach. I can see current connection via CLI: nmcli dev DEVICE TYPE STATE CONNECTION docker0 bridgeconnected docker0 wlp58s0 wifi connected Turris lo loopback unmanaged -- Now I have to run `killall nm-applet && nm-applet &` after every suspend. That fixes my issue I think it's a duplicate of https://bugs.launchpad.net/ubuntu/+source /network-manager/+bug/1589401 but I was asked to submit separate bug ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.6-0ubuntu0.16.04.2 Uname: Linux 4.15.0-041500rc9-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: Unity Date: Sun Feb 11 19:41:21 2018 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 EcryptfsInUse: Yes IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-10-06 (493 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 IpRoute: default via 192.168.1.1 dev wlp58s0 proto static metric 600 169.254.0.0/16 dev docker0 scope link metric 1000 linkdown 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 192.168.1.0/24 dev wlp58s0 proto kernel scope link src 192.168.1.137 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH docker0 bridgeconnected /org/freedesktop/NetworkManager/Devices/1 docker0 440d4ade-78be-45c3-a821-903971861d0c /org/freedesktop/NetworkManager/ActiveConnection/0 wlp58s0 wifi connected /org/freedesktop/NetworkManager/Devices/3 Turris e963-362e-4e4a-ac98-54af278d348d /org/freedesktop/NetworkManager/ActiveConnection/88 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.6connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1748812/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1748812] Re: cannot view wifi networks after resume from suspend
Kai-Heng Feng, you can see screenshot before restart in original bug description: > screenshot of nm-applet before restart -- 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/1748812 Title: cannot view wifi networks after resume from suspend Status in network-manager package in Ubuntu: Confirmed Bug description: Hello, On 2 laptops (Dell XPS13 9360 with ath10k and Lenovo T530 with iwlwifi) I have the same issue: After resume from suspend nm-applet doesn't show any information about connected/available wi-fi connections. Please see screenshot in attach. I can see current connection via CLI: nmcli dev DEVICE TYPE STATE CONNECTION docker0 bridgeconnected docker0 wlp58s0 wifi connected Turris lo loopback unmanaged -- Now I have to run `killall nm-applet && nm-applet &` after every suspend. That fixes my issue I think it's a duplicate of https://bugs.launchpad.net/ubuntu/+source /network-manager/+bug/1589401 but I was asked to submit separate bug ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.6-0ubuntu0.16.04.2 Uname: Linux 4.15.0-041500rc9-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: Unity Date: Sun Feb 11 19:41:21 2018 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 EcryptfsInUse: Yes IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-10-06 (493 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 IpRoute: default via 192.168.1.1 dev wlp58s0 proto static metric 600 169.254.0.0/16 dev docker0 scope link metric 1000 linkdown 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 192.168.1.0/24 dev wlp58s0 proto kernel scope link src 192.168.1.137 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH docker0 bridgeconnected /org/freedesktop/NetworkManager/Devices/1 docker0 440d4ade-78be-45c3-a821-903971861d0c /org/freedesktop/NetworkManager/ActiveConnection/0 wlp58s0 wifi connected /org/freedesktop/NetworkManager/Devices/3 Turris e963-362e-4e4a-ac98-54af278d348d /org/freedesktop/NetworkManager/ActiveConnection/88 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.6connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1748812/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1748812] Re: cannot view wifi networks after resume from suspend
Shih-Yuan Lee, > `Uname: Linux 4.15.0-041500rc9-generic x86_64` is not the kernel that Ubuntu supported. I have this bug on a wide range of kernels from 4.4 to 4.15 We completely the same behaviour. On 2 laptops with different wi-fi adapters (ath10k and iwlwifi kernel modules) Here is complete list of installed kernel versions and on every kernel I have this bug. linux-image-4.10.0-32-generic 4.10.0-32.36~16.04.1 linux-image-4.10.0-33-generic 4.10.0-33.37~16.04.1 linux-image-4.10.0-35-generic 4.10.0-35.39~16.04.1 linux-image-4.10.0-37-generic 4.10.0-37.41~16.04.1 linux-image-4.10.0-38-generic 4.10.0-38.42~16.04.1 linux-image-4.10.0-40-generic 4.10.0-40.44~16.04.1 linux-image-4.10.0-42-generic 4.10.0-42.46~16.04.1 linux-image-4.13.0-26-generic 4.13.0-26.29~16.04.2 linux-image-4.13.0-31-generic 4.13.0-31.34~16.04.1 linux-image-4.13.0-32-generic 4.13.0-32.35~16.04.1 linux-image-4.13.11-041311-generic 4.13.11-041311.201711020532 linux-image-4.13.3-041303-generic 4.13.3-041303.201709200606 linux-image-4.13.4-041304-generic 4.13.4-041304.201709270931 linux-image-4.14.0-041400-generic 4.14.0-041400.201711122031 linux-image-4.14.2-041402-generic 4.14.2-041402.201711240330 linux-image-4.14.7-041407-generic 4.14.7-041407.201712171031 linux-image-4.14.8-041408-generic 4.14.8-041408.201712200555 linux-image-4.15.0-041500-generic 4.15.0-041500.201802011154 linux-image-4.15.0-041500rc9-generic 4.15.0-041500rc9.201801212130 linux-image-4.4.0-101-generic 4.4.0-101.124 linux-image-4.4.0-103-generic 4.4.0-103.126 linux-image-4.4.0-104-generic 4.4.0-104.127 linux-image-4.4.0-109-generic 4.4.0-109.132 linux-image-4.4.0-112-generic 4.4.0-112.135 linux-image-4.4.0-93-generic 4.4.0-93.116 linux-image-4.4.0-96-generic 4.4.0-96.119 linux-image-4.4.0-97-generic 4.4.0-97.120 linux-image-4.4.0-98-generic 4.4.0-98.121 linux-image-4.8.0-58-generic 4.8.0-58.63~16.04.1 linux-image-4.9.32-040932-generic 4.9.32-040932.201706141032 linux-image-extra-4.10.0-32-generic 4.10.0-32.36~16.04.1 linux-image-extra-4.10.0-33-generic 4.10.0-33.37~16.04.1 linux-image-extra-4.10.0-35-generic 4.10.0-35.39~16.04.1 linux-image-extra-4.10.0-37-generic 4.10.0-37.41~16.04.1 linux-image-extra-4.10.0-38-generic 4.10.0-38.42~16.04.1 linux-image-extra-4.10.0-40-generic 4.10.0-40.44~16.04.1 linux-image-extra-4.10.0-42-generic 4.10.0-42.46~16.04.1 linux-image-extra-4.13.0-26-generic 4.13.0-26.29~16.04.2 linux-image-extra-4.13.0-31-generic 4.13.0-31.34~16.04.1 linux-image-extra-4.13.0-32-generic 4.13.0-32.35~16.04.1 linux-image-extra-4.4.0-101-generic 4.4.0-101.124 linux-image-extra-4.4.0-103-generic 4.4.0-103.126 linux-image-extra-4.4.0-104-generic 4.4.0-104.127 linux-image-extra-4.4.0-109-generic 4.4.0-109.132 linux-image-extra-4.4.0-112-generic 4.4.0-112.135 linux-image-extra-4.4.0-93-generic 4.4.0-93.116 linux-image-extra-4.4.0-96-generic 4.4.0-96.119 linux-image-extra-4.4.0-97-generic 4.4.0-97.120 linux-image-extra-4.4.0-98-generic 4.4.0-98.121 linux-image-extra-4.8.0-58-generic 4.8.0-58.63~16.04.1 linux-image-generic 4.4.0.112.118 linux-image-generic-hwe-16.04 4.13.0.32.52 -- 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/1748812 Title: cannot view wifi networks after resume from suspend Status in network-manager package in Ubuntu: Confirmed Bug description: Hello, On 2 laptops (Dell XPS13 9360 with ath10k and Lenovo T530 with iwlwifi) I have the same issue: After resume from suspend nm-applet doesn't show any information about connected/available wi-fi connections. Please see screenshot in attach. I can see current connection via CLI: nmcli dev DEVICE TYPE STATE CONNECTION docker0 bridgeconnected docker0 wlp58s0 wifi connected Turris lo loopback unmanaged -- Now I have to run `killall nm-applet && nm-applet &` after every suspend. That fixes my issue I think it's a duplicate of https://bugs.launchpad.net/ubuntu/+source /network-manager/+bug/1589401 but I was asked to submit separate bug ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.6-0ubuntu0.16.04.2 Uname: Linux 4.15.0-041500rc9-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: Unity Date: Sun Feb 11 19:41:21 2018 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 EcryptfsInUse: Yes IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-10-06 (493 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 IpRoute: default via 192.168.1.1 dev wlp58s0 proto static metric 600 169.254.0.0/16 dev docker0 scope link metric 1000 l
[Desktop-packages] [Bug 1281250] Re: VNC accessible from non-linux machines only with encryption disabled
I use vino in ubuntu 16.04.3 LTS and the clients that work with encryption are vinagre and remmina. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vino in Ubuntu. https://bugs.launchpad.net/bugs/1281250 Title: VNC accessible from non-linux machines only with encryption disabled Status in TigerVNC: New Status in vino: Confirmed Status in vino package in Ubuntu: Triaged Status in vino source package in Trusty: Triaged Status in vino package in Fedora: Invalid Bug description: Since a recent update, it is impossible to connect to my Ubuntu box using VNC from a Windows machine unless I disable encryption on the vino server. I tested up-to-date tightVNC client and TigerVNC client on the Windows machine, with the same result. As soon I try to connect, I receive the following error: [ 5872/ 6448] 2014-01-20 12:11:18:247 List of security type is read [ 5872/ 6448] 2014-01-20 12:11:18:247 : Security Types received (1): Unknown type (18) [ 5872/ 6448] 2014-01-20 12:11:18:247 Selecting auth-handler [ 5872/ 6448] 2014-01-20 12:11:18:247 + RemoteViewerCore. Exception: No security types supported. Server sent security types, but we do not support any of their. So it seems that the update changed the security type of vino to a new one. I searched for a way to go back to the old one (until the clients catches up) with no avail. A solution is disabling the encryption completely, by gsettings set org.gnome.Vino require-encryption false ...but this is subotpimal. Is there a way to switch the encryption back to the old one? To manage notifications about this bug go to: https://bugs.launchpad.net/tigervnc/+bug/1281250/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1748812] Re: cannot view wifi networks after resume from suspend
The same here: Linux E7470 4.13.0-33-generic #36~16.04.1-Ubuntu SMP Wed Feb 7 23:32:33 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux -- 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/1748812 Title: cannot view wifi networks after resume from suspend Status in network-manager package in Ubuntu: Confirmed Bug description: Hello, On 2 laptops (Dell XPS13 9360 with ath10k and Lenovo T530 with iwlwifi) I have the same issue: After resume from suspend nm-applet doesn't show any information about connected/available wi-fi connections. Please see screenshot in attach. I can see current connection via CLI: nmcli dev DEVICE TYPE STATE CONNECTION docker0 bridgeconnected docker0 wlp58s0 wifi connected Turris lo loopback unmanaged -- Now I have to run `killall nm-applet && nm-applet &` after every suspend. That fixes my issue I think it's a duplicate of https://bugs.launchpad.net/ubuntu/+source /network-manager/+bug/1589401 but I was asked to submit separate bug ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.6-0ubuntu0.16.04.2 Uname: Linux 4.15.0-041500rc9-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: Unity Date: Sun Feb 11 19:41:21 2018 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 EcryptfsInUse: Yes IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-10-06 (493 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 IpRoute: default via 192.168.1.1 dev wlp58s0 proto static metric 600 169.254.0.0/16 dev docker0 scope link metric 1000 linkdown 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 192.168.1.0/24 dev wlp58s0 proto kernel scope link src 192.168.1.137 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH docker0 bridgeconnected /org/freedesktop/NetworkManager/Devices/1 docker0 440d4ade-78be-45c3-a821-903971861d0c /org/freedesktop/NetworkManager/ActiveConnection/0 wlp58s0 wifi connected /org/freedesktop/NetworkManager/Devices/3 Turris e963-362e-4e4a-ac98-54af278d348d /org/freedesktop/NetworkManager/ActiveConnection/88 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.6connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1748812/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1589401] Re: cannot view wifi networks after re-enabling wifi
Sure thing. But 2 more points that maake me believe it's user space bug: 1. nmcli dev shows correct information (I believe under the hood it uses the same syscalls as nm-applet) 2. I have this bug on a wide range of kernels from 4.4 to 4.15 We completely the same behaviour. On 2 laptops with different wi-fi adapters (ath10k and iwlwifi kernel modules) -- 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/1589401 Title: cannot view wifi networks after re-enabling wifi Status in NetworkManager: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: after re enabling wifi, up-down arrows just like wired network. cannot see any wifi ssid. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1589401/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1748812] Re: cannot view wifi networks after resume from suspend
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: network-manager (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1748812 Title: cannot view wifi networks after resume from suspend Status in network-manager package in Ubuntu: Confirmed Bug description: Hello, On 2 laptops (Dell XPS13 9360 with ath10k and Lenovo T530 with iwlwifi) I have the same issue: After resume from suspend nm-applet doesn't show any information about connected/available wi-fi connections. Please see screenshot in attach. I can see current connection via CLI: nmcli dev DEVICE TYPE STATE CONNECTION docker0 bridgeconnected docker0 wlp58s0 wifi connected Turris lo loopback unmanaged -- Now I have to run `killall nm-applet && nm-applet &` after every suspend. That fixes my issue I think it's a duplicate of https://bugs.launchpad.net/ubuntu/+source /network-manager/+bug/1589401 but I was asked to submit separate bug ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.6-0ubuntu0.16.04.2 Uname: Linux 4.15.0-041500rc9-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: Unity Date: Sun Feb 11 19:41:21 2018 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 EcryptfsInUse: Yes IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-10-06 (493 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 IpRoute: default via 192.168.1.1 dev wlp58s0 proto static metric 600 169.254.0.0/16 dev docker0 scope link metric 1000 linkdown 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 192.168.1.0/24 dev wlp58s0 proto kernel scope link src 192.168.1.137 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH docker0 bridgeconnected /org/freedesktop/NetworkManager/Devices/1 docker0 440d4ade-78be-45c3-a821-903971861d0c /org/freedesktop/NetworkManager/ActiveConnection/0 wlp58s0 wifi connected /org/freedesktop/NetworkManager/Devices/3 Turris e963-362e-4e4a-ac98-54af278d348d /org/freedesktop/NetworkManager/ActiveConnection/88 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.6connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1748812/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1748812] Re: cannot view wifi networks after resume from suspend
So what does it look like before restart? -- 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/1748812 Title: cannot view wifi networks after resume from suspend Status in network-manager package in Ubuntu: Confirmed Bug description: Hello, On 2 laptops (Dell XPS13 9360 with ath10k and Lenovo T530 with iwlwifi) I have the same issue: After resume from suspend nm-applet doesn't show any information about connected/available wi-fi connections. Please see screenshot in attach. I can see current connection via CLI: nmcli dev DEVICE TYPE STATE CONNECTION docker0 bridgeconnected docker0 wlp58s0 wifi connected Turris lo loopback unmanaged -- Now I have to run `killall nm-applet && nm-applet &` after every suspend. That fixes my issue I think it's a duplicate of https://bugs.launchpad.net/ubuntu/+source /network-manager/+bug/1589401 but I was asked to submit separate bug ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.6-0ubuntu0.16.04.2 Uname: Linux 4.15.0-041500rc9-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: Unity Date: Sun Feb 11 19:41:21 2018 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 EcryptfsInUse: Yes IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-10-06 (493 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 IpRoute: default via 192.168.1.1 dev wlp58s0 proto static metric 600 169.254.0.0/16 dev docker0 scope link metric 1000 linkdown 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 192.168.1.0/24 dev wlp58s0 proto kernel scope link src 192.168.1.137 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH docker0 bridgeconnected /org/freedesktop/NetworkManager/Devices/1 docker0 440d4ade-78be-45c3-a821-903971861d0c /org/freedesktop/NetworkManager/ActiveConnection/0 wlp58s0 wifi connected /org/freedesktop/NetworkManager/Devices/3 Turris e963-362e-4e4a-ac98-54af278d348d /org/freedesktop/NetworkManager/ActiveConnection/88 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.6connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1748812/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1748812] Re: cannot view wifi networks after resume from suspend
`Uname: Linux 4.15.0-041500rc9-generic x86_64` is not the kernel that Ubuntu supported. -- 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/1748812 Title: cannot view wifi networks after resume from suspend Status in network-manager package in Ubuntu: Confirmed Bug description: Hello, On 2 laptops (Dell XPS13 9360 with ath10k and Lenovo T530 with iwlwifi) I have the same issue: After resume from suspend nm-applet doesn't show any information about connected/available wi-fi connections. Please see screenshot in attach. I can see current connection via CLI: nmcli dev DEVICE TYPE STATE CONNECTION docker0 bridgeconnected docker0 wlp58s0 wifi connected Turris lo loopback unmanaged -- Now I have to run `killall nm-applet && nm-applet &` after every suspend. That fixes my issue I think it's a duplicate of https://bugs.launchpad.net/ubuntu/+source /network-manager/+bug/1589401 but I was asked to submit separate bug ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.6-0ubuntu0.16.04.2 Uname: Linux 4.15.0-041500rc9-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: Unity Date: Sun Feb 11 19:41:21 2018 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 EcryptfsInUse: Yes IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-10-06 (493 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 IpRoute: default via 192.168.1.1 dev wlp58s0 proto static metric 600 169.254.0.0/16 dev docker0 scope link metric 1000 linkdown 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 192.168.1.0/24 dev wlp58s0 proto kernel scope link src 192.168.1.137 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH docker0 bridgeconnected /org/freedesktop/NetworkManager/Devices/1 docker0 440d4ade-78be-45c3-a821-903971861d0c /org/freedesktop/NetworkManager/ActiveConnection/0 wlp58s0 wifi connected /org/freedesktop/NetworkManager/Devices/3 Turris e963-362e-4e4a-ac98-54af278d348d /org/freedesktop/NetworkManager/ActiveConnection/88 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.6connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1748812/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1589401] Re: cannot view wifi networks after re-enabling wifi
Here is how nm-applet looks after restart (killall nm-applet && nm- applet &) ** Attachment added: "Here is how nm-applet looks after restart" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1589401/+attachment/5053390/+files/Screenshot%20from%202018-02-11%2019-50-55.png -- 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/1589401 Title: cannot view wifi networks after re-enabling wifi Status in NetworkManager: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: after re enabling wifi, up-down arrows just like wired network. cannot see any wifi ssid. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1589401/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1589401] Re: cannot view wifi networks after re-enabling wifi
It can not prove if it is a linux kernel bug or not even when you can recover it from the UI. -- 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/1589401 Title: cannot view wifi networks after re-enabling wifi Status in NetworkManager: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: after re enabling wifi, up-down arrows just like wired network. cannot see any wifi ssid. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1589401/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1589401] Re: cannot view wifi networks after re-enabling wifi
I've filed separate bug https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1748812 -- 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/1589401 Title: cannot view wifi networks after re-enabling wifi Status in NetworkManager: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: after re enabling wifi, up-down arrows just like wired network. cannot see any wifi ssid. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1589401/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1748812] Re: cannot view wifi networks after resume from suspend
Here is how nm-applet looks after restart (killall nm-applet && nm- applet &) ** Attachment added: "Here is how nm-applet looks after restart" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1748812/+attachment/5053391/+files/Screenshot%20from%202018-02-11%2019-50-55.png -- 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/1748812 Title: cannot view wifi networks after resume from suspend Status in network-manager package in Ubuntu: New Bug description: Hello, On 2 laptops (Dell XPS13 9360 with ath10k and Lenovo T530 with iwlwifi) I have the same issue: After resume from suspend nm-applet doesn't show any information about connected/available wi-fi connections. Please see screenshot in attach. I can see current connection via CLI: nmcli dev DEVICE TYPE STATE CONNECTION docker0 bridgeconnected docker0 wlp58s0 wifi connected Turris lo loopback unmanaged -- Now I have to run `killall nm-applet && nm-applet &` after every suspend. That fixes my issue I think it's a duplicate of https://bugs.launchpad.net/ubuntu/+source /network-manager/+bug/1589401 but I was asked to submit separate bug ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.6-0ubuntu0.16.04.2 Uname: Linux 4.15.0-041500rc9-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: Unity Date: Sun Feb 11 19:41:21 2018 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 EcryptfsInUse: Yes IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-10-06 (493 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 IpRoute: default via 192.168.1.1 dev wlp58s0 proto static metric 600 169.254.0.0/16 dev docker0 scope link metric 1000 linkdown 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 192.168.1.0/24 dev wlp58s0 proto kernel scope link src 192.168.1.137 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH docker0 bridgeconnected /org/freedesktop/NetworkManager/Devices/1 docker0 440d4ade-78be-45c3-a821-903971861d0c /org/freedesktop/NetworkManager/ActiveConnection/0 wlp58s0 wifi connected /org/freedesktop/NetworkManager/Devices/3 Turris e963-362e-4e4a-ac98-54af278d348d /org/freedesktop/NetworkManager/ActiveConnection/88 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.6connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1748812/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1748812] [NEW] cannot view wifi networks after resume from suspend
Public bug reported: Hello, On 2 laptops (Dell XPS13 9360 with ath10k and Lenovo T530 with iwlwifi) I have the same issue: After resume from suspend nm-applet doesn't show any information about connected/available wi-fi connections. Please see screenshot in attach. I can see current connection via CLI: nmcli dev DEVICE TYPE STATE CONNECTION docker0 bridgeconnected docker0 wlp58s0 wifi connected Turris lo loopback unmanaged -- Now I have to run `killall nm-applet && nm-applet &` after every suspend. That fixes my issue I think it's a duplicate of https://bugs.launchpad.net/ubuntu/+source /network-manager/+bug/1589401 but I was asked to submit separate bug ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.6-0ubuntu0.16.04.2 Uname: Linux 4.15.0-041500rc9-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: Unity Date: Sun Feb 11 19:41:21 2018 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 EcryptfsInUse: Yes IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-10-06 (493 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 IpRoute: default via 192.168.1.1 dev wlp58s0 proto static metric 600 169.254.0.0/16 dev docker0 scope link metric 1000 linkdown 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 192.168.1.0/24 dev wlp58s0 proto kernel scope link src 192.168.1.137 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH docker0 bridgeconnected /org/freedesktop/NetworkManager/Devices/1 docker0 440d4ade-78be-45c3-a821-903971861d0c /org/freedesktop/NetworkManager/ActiveConnection/0 wlp58s0 wifi connected /org/freedesktop/NetworkManager/Devices/3 Turris e963-362e-4e4a-ac98-54af278d348d /org/freedesktop/NetworkManager/ActiveConnection/88 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.6connected started full enabled enabled enabled enabled enabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages xenial ** Attachment added: "screenshot of nm-applet before restart" https://bugs.launchpad.net/bugs/1748812/+attachment/5053374/+files/Screenshot%20from%202018-02-11%2019-44-31.png -- 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/1748812 Title: cannot view wifi networks after resume from suspend Status in network-manager package in Ubuntu: New Bug description: Hello, On 2 laptops (Dell XPS13 9360 with ath10k and Lenovo T530 with iwlwifi) I have the same issue: After resume from suspend nm-applet doesn't show any information about connected/available wi-fi connections. Please see screenshot in attach. I can see current connection via CLI: nmcli dev DEVICE TYPE STATE CONNECTION docker0 bridgeconnected docker0 wlp58s0 wifi connected Turris lo loopback unmanaged -- Now I have to run `killall nm-applet && nm-applet &` after every suspend. That fixes my issue I think it's a duplicate of https://bugs.launchpad.net/ubuntu/+source /network-manager/+bug/1589401 but I was asked to submit separate bug ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.6-0ubuntu0.16.04.2 Uname: Linux 4.15.0-041500rc9-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: Unity Date: Sun Feb 11 19:41:21 2018 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 EcryptfsInUse: Yes IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-10-06 (493 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 IpRoute: default via 192.168.1.1 dev wlp58s0 proto static metric 600 169.254.
[Desktop-packages] [Bug 1589401] Re: cannot view wifi networks after re-enabling wifi
It's not seems as linux bug because there is how I'm fixing it: killall nm-applet && nm-applet & -- 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/1589401 Title: cannot view wifi networks after re-enabling wifi Status in NetworkManager: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: after re enabling wifi, up-down arrows just like wired network. cannot see any wifi ssid. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1589401/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1589401] Re: cannot view wifi networks after re-enabling wifi
Yuriy, please file a separate bug. Run `ubuntu-bug linux`. -- 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/1589401 Title: cannot view wifi networks after re-enabling wifi Status in NetworkManager: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: after re enabling wifi, up-down arrows just like wired network. cannot see any wifi ssid. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1589401/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1746353] Re: Evince cannot open file from Firefox (beta), failed to load libnss3.so
It's a firefox issues, and this is fix now in the last version. Look at https://bugzilla.mozilla.org/show_bug.cgi?id=1434033 ** Bug watch added: Mozilla Bugzilla #1434033 https://bugzilla.mozilla.org/show_bug.cgi?id=1434033 ** Package changed: evince (Ubuntu) => ubuntu ** Changed in: ubuntu Status: Confirmed => Fix Released -- 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/1746353 Title: Evince cannot open file from Firefox (beta), failed to load libnss3.so Status in Ubuntu: Fix Released Bug description: Whenever I try to open a PDF file from the Firefox download manager, I get the following error: Failed to load backend for 'application/pdf': libnss3.so: failed to map segment from shared object. This only happens from Firefox Developer edition (same as beta), which I have running from my home directory. So this is probably somehow an issue with that, but I don't know how to debug it. I don't know why it's different from running Evince from nautilus, or just starting it directly, or even from Firefox stable, which is fine. But I suppose there might also be an issue with Evince if it's crashing when launched in this way. I would appreciate any help in debugging this matter. Thanks! ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: evince 3.26.0-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: Awesome GNOME Date: Tue Jan 30 13:12:05 2018 InstallationDate: Installed on 2013-11-24 (1528 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) SourcePackage: evince UpgradeStatus: Upgraded to artful on 2017-10-30 (92 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1746353/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1748620] Re: PulseAudio can not remember my settings between reboots
I'm not sure, but suspect PulseAudio has nothing to do with remembering settings. That's the job of your settings daemon/backend... Can you please help us to find the right package(s) to assign this bug to? Just open your settings app, and search the list of running processes for which one is *-control-center or similar, and then find which package provides that by running something like: dpkg -S `which YOUR-SETTINGS-APP` ** Changed in: pulseaudio (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1748620 Title: PulseAudio can not remember my settings between reboots Status in pulseaudio package in Ubuntu: Incomplete Bug description: Pulseaudio can not remember my settings between reboots. I have a usb mic named WUP-021-0 Analog Mono and i use for output Built-in Audio Analog Stereo. But every time i open my pc or reboot it my output setings will default to my mic WUP-021-0 Analog Mono. Tested in ubuntu 18.04 daily ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu6 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.8-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: apolihron 1590 F pulseaudio /dev/snd/controlC0: apolihron 1590 F pulseaudio /dev/snd/controlC2: apolihron 1590 F pulseaudio CurrentDesktop: MATE Date: Sat Feb 10 15:34:51 2018 InstallationDate: Installed on 2018-02-10 (0 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180210) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/05/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.40 dmi.board.name: A88M-G/3.1 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.40:bd05/05/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnA88M-G/3.1:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1748620/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1736664] Re: /usr/bin/gnome-shell:5:_g_log_abort:g_log_default_handler:default_log_handler:g_logv:g_log
*** This bug is a duplicate of bug 1748450 *** https://bugs.launchpad.net/bugs/1748450 ** This bug is no longer a duplicate of bug 1505409 gnome-shell crashed with SIGTRAP in x_io_error() from _XIOError() from _XEventsQueued() from XPending() from gdk_check_xpending() ["Connection to xwayland lost"] ** This bug has been marked a duplicate of bug 1748450 gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_default_handler() from default_log_handler(message="Connection to xwayland lost") from g_logv() from g_log() from -- 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/1736664 Title: /usr/bin/gnome- shell:5:_g_log_abort:g_log_default_handler:default_log_handler:g_logv:g_log Status in gnome-shell package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.26.2-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/8ef857b2fe07d60742cd02d7d8f988f78ecd0f95 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1736664/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1746353] Re: Evince cannot open file from Firefox (beta), failed to load libnss3.so
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: evince (Ubuntu) Status: New => Confirmed -- 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/1746353 Title: Evince cannot open file from Firefox (beta), failed to load libnss3.so Status in evince package in Ubuntu: Confirmed Bug description: Whenever I try to open a PDF file from the Firefox download manager, I get the following error: Failed to load backend for 'application/pdf': libnss3.so: failed to map segment from shared object. This only happens from Firefox Developer edition (same as beta), which I have running from my home directory. So this is probably somehow an issue with that, but I don't know how to debug it. I don't know why it's different from running Evince from nautilus, or just starting it directly, or even from Firefox stable, which is fine. But I suppose there might also be an issue with Evince if it's crashing when launched in this way. I would appreciate any help in debugging this matter. Thanks! ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: evince 3.26.0-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: Awesome GNOME Date: Tue Jan 30 13:12:05 2018 InstallationDate: Installed on 2013-11-24 (1528 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) SourcePackage: evince UpgradeStatus: Upgraded to artful on 2017-10-30 (92 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1746353/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1748450] Re: gnome-shell crashed with signal 5
*** This is a duplicate of bug 1505409, but is being kept separate so as to automatically collect duplicate reports since the stacktrace signature has changed recently. Any resolution and discussion should occur in bug 1505409. *** See also: https://errors.ubuntu.com/problem/8ef857b2fe07d60742cd02d7d8f988f78ecd0f95 ** Information type changed from Private to Public ** Summary changed: - gnome-shell crashed with signal 5 + gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_default_handler() from default_log_handler(message="Connection to xwayland lost") from g_logv() from g_log() from ** Description changed: - unknown 18.04 beta after initial startup and trying to run software - update app. - - Don Walters - Hilbert Space Technical Arts - (an L^2 sub-space of Banach L^p Space, where p= ~5/3)) - - w9dki / w9gty + *** This is a duplicate of bug 1505409, but is being kept separate so as + to automatically collect duplicate reports since the stacktrace + signature has changed recently. Any resolution and discussion should + occur in bug 1505409. *** ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.26.2-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-33.36-generic 4.13.13 Uname: Linux 4.13.0-33-generic x86_64 ApportVersion: 2.20.8-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME-Greeter:GNOME Date: Thu Feb 8 23:50:23 2018 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: - + InstallationDate: Installed on 2016-03-21 (690 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/false + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/false Signal: 5 SourcePackage: gnome-shell StacktraceTop: - () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 - _XIOError () at /usr/lib/x86_64-linux-gnu/libX11.so.6 - _XEventsQueued () at /usr/lib/x86_64-linux-gnu/libX11.so.6 - XPending () at /usr/lib/x86_64-linux-gnu/libX11.so.6 - () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 + () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 + _XIOError () at /usr/lib/x86_64-linux-gnu/libX11.so.6 + _XEventsQueued () at /usr/lib/x86_64-linux-gnu/libX11.so.6 + XPending () at /usr/lib/x86_64-linux-gnu/libX11.so.6 + () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 Title: gnome-shell crashed with signal 5 UpgradeStatus: Upgraded to bionic on 2018-02-08 (0 days ago) UserGroups: ** Changed in: gnome-shell (Ubuntu) Importance: Medium => High ** Changed in: gnome-shell (Ubuntu) Status: Confirmed => Triaged ** Description changed: *** This is a duplicate of bug 1505409, but is being kept separate so as to automatically collect duplicate reports since the stacktrace signature has changed recently. Any resolution and discussion should occur in bug 1505409. *** + + See also: + https://errors.ubuntu.com/problem/8ef857b2fe07d60742cd02d7d8f988f78ecd0f95 ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.26.2-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-33.36-generic 4.13.13 Uname: Linux 4.13.0-33-generic x86_64 ApportVersion: 2.20.8-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME-Greeter:GNOME Date: Thu Feb 8 23:50:23 2018 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2016-03-21 (690 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/false Signal: 5 SourcePackage: gnome-shell StacktraceTop: () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 _XIOError () at /usr/lib/x86_64-linux-gnu/libX11.so.6 _XEventsQueued () at /usr/lib/x86_64-linux-gnu/libX11.so.6 XPending () at /usr/lib/x86_64-linux-gnu/libX11.so.6 () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 Title: gnome-shell crashed with signal 5 UpgradeStatus: Upgraded to bionic on 2018-02-08 (0 days ago) UserGroups: -- 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/1748450 Title: gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_default_handler() from default_log_handler(message="Connection to xwayland lost") from g_logv() from g_log() from Status in gnome-shell package in Ubuntu: Triaged Bug description: *** This is a duplicate of bug 1505409, but is being kept separate so as to automatically collect duplicate reports since the stacktrace signature has changed recently. Any resolution and discussion should occur in bug 1505409. *** See also: https://errors.ubuntu.com/problem/8ef857b2fe07d60742cd02d7d8f988f78ecd0f95 ProblemType: Crash
[Desktop-packages] [Bug 1747827] Re: alt-tab no longer lets me switch between terminal windows
*** This bug is a duplicate of bug 1723831 *** https://bugs.launchpad.net/bugs/1723831 Switching between windows of the same app requires Alt+` (backtick or whatever key is above your Tab key). But also... Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1723831, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1723831 Alt+Tab doesn't work for same application with multiple windows -- 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/1747827 Title: alt-tab no longer lets me switch between terminal windows Status in gnome-shell package in Ubuntu: New Bug description: I typically use multiple terminal windows, rather than tabs within terminal windows, because I find that the context of the visible part of the overlapping windows is highly useful. Up to 17.04, I could use alt-tab to switch between different windows that were each running a terminal instance. As of 17.10, I can only switch between "the current terminal focus window" and "other apps" -- other terminal windows are not part of the alt-tab "ring" Especially going back and forth between the two latest terminal windows with a single alt-tab is crucial to a productive workflow, and all OS-es I've used have supported this for the last 20 years. Except now, I'm expected to Alt-tab a few times to get "back" to terminal, then press arrow-down and arrow-right to select another terminal window. Wot? That's not helpful. This fundamentally breaks my workflow, and is not something I can live with. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: unity 7.5.0+17.10.20171010-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.gpus..42.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:42:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 384.111 Tue Dec 19 23:51:45 PST 2017 GCC version: gcc version 7.2.0 (Ubuntu 7.2.0-8ubuntu3) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. .tmp.unity_support_test.0: ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Feb 6 20:30:28 2018 DistUpgraded: 2018-02-05 15:47:10,383 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: artful DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.10.0-42-generic, x86_64: installed bbswitch, 0.8, 4.13.0-32-generic, x86_64: installed nvidia-384, 384.111, 4.10.0-42-generic, x86_64: installed nvidia-384, 384.111, 4.13.0-32-generic, x86_64: installed GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85ea] InstallationDate: Installed on 2017-08-26 (164 days ago) InstallationMedia: Ubuntu-Server 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-32-generic.efi.signed root=/dev/mapper/nvm--vg0-root ro rd.driver.blacklist=nouveau SourcePackage: unity UpgradeStatus: Upgraded to artful on 2018-02-05 (1 days ago) dmi.bios.date: 08/11/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0318 dmi.board.asset.tag: Default string dmi.board.name: PRIME X399-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0318:bd08/11/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX399-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:
[Desktop-packages] [Bug 520118] Re: thunar select freezes after using mouse to select folders ("detailed view" mode)
** Changed in: gtk
Status: Confirmed => Expired
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gtk+2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/520118
Title:
thunar select freezes after using mouse to select folders ("detailed
view" mode)
Status in GTK+:
Expired
Status in thunar:
Fix Released
Status in exo package in Ubuntu:
Fix Released
Status in gtk+2.0 package in Ubuntu:
Triaged
Status in libfm package in Ubuntu:
Fix Released
Status in pcmanfm package in Ubuntu:
Fix Released
Status in exo source package in Lucid:
Fix Released
Status in gtk+2.0 source package in Lucid:
Invalid
Status in libfm source package in Lucid:
Fix Released
Status in pcmanfm source package in Lucid:
Fix Released
Bug description:
Binary package hint: thunar
In thunar, in "detailed view" mode, if you enter a subrepertory by using the
mouse, once inside you cannot select files, or subfiles to go deeper in the
repertories. Neither right- click nor left-click are available. However, if you
entered using the keyboard everything works.
Once the bug happens, there is no way to interact with the contents of the
repertory through the window. You have to close the window to open a new one
This bug will happen every time
ProblemType: Bug
Architecture: i386
Date: Wed Feb 10 23:01:21 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/bin/Thunar
InstallationMedia: Xubuntu 10.04 "Lucid Lynx" - Alpha i386 (20091209)
NonfreeKernelModules: wl
Package: thunar 1.0.1-2ubuntu4
ProcEnviron:
LANGUAGE=fr_FR.utf8
LANG=fr_FR.utf8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-11.15-generic
SourcePackage: thunar
Uname: Linux 2.6.32-11-generic i686
WORKAROUND:
Use icon view or compact view to navigate to the desired folder, then a
simple Ctrl+2 will show you the detailed view. Another very easy Ctrl+1 or
Ctrl+3 puts you back in icon view or compact view to navigate again.
To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/520118/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1718824] Re: The analogue audio does not work on the Dell USB Dock
Tested Bionic 1:11.1-1ubuntu6, this bug is fixed by pulseaudio 1:11.1-1ubuntu6. Please put artful 1:10.0-2ubuntu4 and xenial 1:8.0-0ubuntu3.8 to proposed channel. I will test them later. thanks. ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1718824 Title: The analogue audio does not work on the Dell USB Dock Status in HWE Next: In Progress Status in OEM Priority Project: Triaged Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Xenial: Confirmed Status in pulseaudio source package in Artful: Confirmed Bug description: SRU Document: [Impact] If users use the latest Dell USB Dock, e.g. TB16, they will found the analog audio (lineout jack) can't work under ubuntu linux [Test Case] After applying the fix, users can play sound via analog speaker or lineout freely. Without the fix, users can't play sound from lineout jack. [Regression Potential] No any possibility to introduce regression since this fix just adding a new dock's support, it does not change any existing code. [Other Info] No more info here Steps: 1. Cold boot system with BME/IE connected 2. Plug in a speaker to Line-out jack 3. Set Analog Stereo Output from Sound settings Expected results: Line-out port can work Actual results: Line-out port not work To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1718824/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1722725] Re: GNOME Shell disabling wrong screen when docking laptop
** Tags added: fixed-in-3.26.3 -- 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/1722725 Title: GNOME Shell disabling wrong screen when docking laptop Status in GNOME Shell: Fix Released Status in gnome-shell package in Ubuntu: Fix Committed Bug description: I often switch between working with a docking station, closed laptop and an external monitor, and an open laptop without docking station or monitor. I noticed since updating to 17.10 that GNOME Shell would not switch correctly from the setup where the laptop was being used open without a docking station to the other. When I opened the laptop in the docking station the external monitor would come on, and when I closed the laptop it went off again. I manually switched the primary screen to be the external one and that solved it for now, so I assume that GNOME Shell was disabling the external screen instead of the internal one (it is a bit hard to see, and I have not yet tried ssh- ing in). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Oct 11 09:06:34 2017 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'favorite-apps' b"['ubiquity.desktop', 'org.gnome.Nautilus.desktop', 'firefox.desktop', 'libreoffice-writer.desktop', 'libreoffice-calc.desktop', 'libreoffice-impress.desktop', 'org.gnome.Software.desktop', 'gnome-control-center.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2016-05-31 (497 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: gnome-shell UpgradeStatus: Upgraded to artful on 2017-10-05 (6 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1722725/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1725180] Re: Shell animations are not smooth
There is a variety of reasons for this. I have tried to start listing (and fixing) them here: https://trello.com/c/Q6JYXPPs However please note that a resolution for the original reporter will result in this bug being closed. If you feel your issues are in any way different then please open a new bug of your own using the command: ubuntu-bug mutter ** Changed in: mutter (Ubuntu) Assignee: (unassigned) => Daniel van Vugt (vanvugt) -- 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/1725180 Title: Shell animations are not smooth Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: +++UBUNTU RELEASE+++ Description: Ubuntu 17.10 Release: 17.10 +++PACKAGE VERSION+++ xwayland: Installed: 2:1.19.5-0ubuntu2 Candidate: 2:1.19.5-0ubuntu2 Version table: *** 2:1.19.5-0ubuntu2 500 500 http://archive.ubuntu.com/ubuntu artful/main amd64 Packages 100 /var/lib/dpkg/status Bug found on Dell XPS 9560 4K model with GTX1050/Intel HD 630. Currently using Intel HD Graphics 630 as Nvidia seems to have no support for xwayland. The window/dock/launcher animations are lagging/shaky (not smooth). __ ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xwayland 2:1.19.5-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Oct 20 19:09:27 2017 DistUpgraded: 2017-10-20 04:51:46,123 DEBUG icon theme changed, re-reading DistroCodename: artful DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.10.0-37-generic, x86_64: installed bbswitch, 0.8, 4.13.0-16-generic, x86_64: installed nvidia-387, 387.12, 4.13.0-16-generic, x86_64: installed v4l2loopback, 0.10.0, 4.10.0-37-generic, x86_64: installed v4l2loopback, 0.10.0, 4.13.0-16-generic, x86_64: installed ExecutablePath: /usr/bin/Xwayland ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:07be] Subsystem: Dell GP107M [GeForce GTX 1050 Mobile] [1028:07be] InstallationDate: Installed on 2017-05-24 (149 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 138a:0091 Validity Sensors, Inc. Bus 001 Device 002: ID 0cf3:e300 Atheros Communications, Inc. Bus 001 Device 004: ID 1bcf:2b95 Sunplus Innovation Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9560 ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed root=UUID=38514616-2735-4966-91f7-71f1d60beb73 ro quiet splash vt.handoff=7 SourcePackage: xorg-server UpgradeStatus: Upgraded to artful on 2017-10-19 (0 days ago) dmi.bios.date: 08/30/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.0 dmi.board.name: 05FFDN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.0:bd08/30/2017:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9560 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1 version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1725180/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1672297] Re: gnome-shell uses lots of memory, and grows over time
See also comment #29. It's probably not worth commenting further here
till we're on at least version 3.26.3.
--
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/1672297
Title:
gnome-shell uses lots of memory, and grows over time
Status in GNOME Shell:
Unknown
Status in Mutter:
Fix Released
Status in gnome-shell package in Ubuntu:
Triaged
Status in mutter package in Ubuntu:
Triaged
Bug description:
gnome-shell's RSS is growing by 1 MiB every few minutes, and is now at
almost 2 GiB.
user 3039 1.8 16.1 4302340 1968476 tty2 Sl+ Mar09 120:17
/usr/bin/gnome-shell
strace output is voluminous; here is a representative sample:
poll([{fd=5, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=5, revents=POLLOUT}])
writev(5, [{"\231\n\10\0\n\0
\0\0\0\0\0\0\0\0\0\0\0\0\0\1\0\0\0\0\0\0\0\0\0\0\0", 32}], 1) = 32
poll([{fd=5, events=POLLIN}], 1, -1)= 1 ([{fd=5, revents=POLLIN}])
recvmsg(5, {msg_name(0)=NULL,
msg_iov(1)=[{"\1\0{\224\0\0\0\0H\0\0\0\0\23\266\32\0\0\0\0\201\242\204\0\0\0\0\0\261.\0\0",
4096}], msg_controllen=0, msg_flags=0}, 0) = 32
recvmsg(5, 0x7fff60efac90, 0) = -1 EAGAIN (Resource temporarily
unavailable)
recvmsg(5, 0x7fff60efac90, 0) = -1 EAGAIN (Resource temporarily
unavailable)
poll([{fd=5, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=5, revents=POLLOUT}])
writev(5, [{"\212\5\4\0a\2228\0y\3\5\0%\3\27\4\231\6\5\0\n\0
\0a\2228\0\0\0\0\0"..., 36}, {NULL, 0}, {"", 0}], 3) = 36
poll([{fd=5, events=POLLIN}], 1, -1)= 1 ([{fd=5, revents=POLLIN}])
recvmsg(5, {msg_name(0)=NULL,
msg_iov(1)=[{"\1\0}\224\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0",
4096}], msg_controllen=0, msg_flags=0}, 0) = 32
recvmsg(5, 0x7fff60efac90, 0) = -1 EAGAIN (Resource temporarily
unavailable)
poll([{fd=5, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=5, revents=POLLOUT}])
writev(5, [{"\212\n\2\0a\2228\0", 8}, {NULL, 0}, {"", 0}], 3) = 8
recvmsg(5, 0x7fff60efb020, 0) = -1 EAGAIN (Resource temporarily
unavailable)
recvmsg(12, 0x7fff60efb000, 0) = -1 EAGAIN (Resource temporarily
unavailable)
poll([{fd=4, events=POLLIN}, {fd=5, events=POLLIN}, {fd=11, events=POLLIN},
{fd=12, events=POLLIN}, {fd=14, events=POLLIN}, {fd=16, events=POLLIN}, {fd=26,
events=POLLIN}, {fd=29, events=POLLIN}, {fd=32, events=POLLIN}, {fd=34,
events=POLLIN}, {fd=37, events=POLLIN}, {fd=38, events=POLLIN}, {fd=40,
events=POLLIN}, {fd=42, events=POLLIN}, {fd=43, events=POLLIN}], 15, 0) = 0
(Timeout)
recvmsg(5, 0x7fff60efb040, 0) = -1 EAGAIN (Resource temporarily
unavailable)
recvmsg(5, 0x7fff60efb020, 0) = -1 EAGAIN (Resource temporarily
unavailable)
recvmsg(12, 0x7fff60efb000, 0) = -1 EAGAIN (Resource temporarily
unavailable)
poll([{fd=4, events=POLLIN}, {fd=5, events=POLLIN}, {fd=11, events=POLLIN},
{fd=12, events=POLLIN}, {fd=14, events=POLLIN}, {fd=16, events=POLLIN}, {fd=26,
events=POLLIN}, {fd=29, events=POLLIN}, {fd=32, events=POLLIN}, {fd=34,
events=POLLIN}, {fd=37, events=POLLIN}, {fd=38, events=POLLIN}, {fd=40,
events=POLLIN}, {fd=42, events=POLLIN}, {fd=43, events=POLLIN}], 15, 0) = 0
(Timeout)
recvmsg(5, 0x7fff60efb040, 0) = -1 EAGAIN (Resource temporarily
unavailable)
open("/proc/self/stat", O_RDONLY) = 36
fstat(36, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0
fcntl(36, F_GETFL) = 0x8000 (flags O_RDONLY|O_LARGEFILE)
fstat(36, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0
read(36, "3039 (gnome-shell) R 2930 2917 2"..., 4096) = 354
read(36, "", 3072) = 0
close(36) = 0
recvmsg(5, 0x7fff60efb020, 0) = -1 EAGAIN (Resource temporarily
unavailable)
recvmsg(12, 0x7fff60efb000, 0) = -1 EAGAIN (Resource temporarily
unavailable)
poll([{fd=4, events=POLLIN}, {fd=5, events=POLLIN}, {fd=11, events=POLLIN},
{fd=12, events=POLLIN}, {fd=14, events=POLLIN}, {fd=16, events=POLLIN}, {fd=26,
events=POLLIN}, {fd=29, events=POLLIN}, {fd=32, events=POLLIN}, {fd=34,
events=POLLIN}, {fd=37, events=POLLIN}, {fd=38, events=POLLIN}, {fd=40,
events=POLLIN}, {fd=42, events=POLLIN}, {fd=43, events=POLLIN}], 15, 117885) =
1 ([{fd=4, revents=POLLIN}])
read(4, "\1\0\0\0\0\0\0\0", 16) = 8
recvmsg(5, 0x7fff60efb040, 0) = -1 EAGAIN (Resource temporarily
unavailable)
recvmsg(5, 0x7fff60efb020, 0) = -1 EAGAIN (Resource temporarily
unavailable)
recvmsg(12, {msg_name(0)=NULL,
msg_iov(1)=[{"[\2\327&h\0@\0i\0@\0(nu\22\n\0I\0\336\2\232\1\265\0038\2\362\2\355\1",
4096}], msg_controllen=0, msg_flags=0}, 0) = 32
recvmsg(12, 0x7fff60efb000, 0) = -1 EAGAIN (Resource temporarily
unavailable)
poll([{fd=4, events=POLLIN}, {fd=5, events=POLLIN}, {fd=11, events=POLLIN},
{fd=12, events=POLLIN}, {fd=14, events=POLLIN}, {fd=16, events=POLLIN}
[Desktop-packages] [Bug 1747827] Re: alt-tab no longer lets me switch between terminal windows
Yes, this bug should move to gnome-shell -- I'm using the default in ubuntu-17.10, which is gnome-shell. ** Package changed: unity (Ubuntu) => gnome-shell (Ubuntu) -- 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/1747827 Title: alt-tab no longer lets me switch between terminal windows Status in gnome-shell package in Ubuntu: New Bug description: I typically use multiple terminal windows, rather than tabs within terminal windows, because I find that the context of the visible part of the overlapping windows is highly useful. Up to 17.04, I could use alt-tab to switch between different windows that were each running a terminal instance. As of 17.10, I can only switch between "the current terminal focus window" and "other apps" -- other terminal windows are not part of the alt-tab "ring" Especially going back and forth between the two latest terminal windows with a single alt-tab is crucial to a productive workflow, and all OS-es I've used have supported this for the last 20 years. Except now, I'm expected to Alt-tab a few times to get "back" to terminal, then press arrow-down and arrow-right to select another terminal window. Wot? That's not helpful. This fundamentally breaks my workflow, and is not something I can live with. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: unity 7.5.0+17.10.20171010-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.gpus..42.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:42:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 384.111 Tue Dec 19 23:51:45 PST 2017 GCC version: gcc version 7.2.0 (Ubuntu 7.2.0-8ubuntu3) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. .tmp.unity_support_test.0: ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Feb 6 20:30:28 2018 DistUpgraded: 2018-02-05 15:47:10,383 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: artful DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.10.0-42-generic, x86_64: installed bbswitch, 0.8, 4.13.0-32-generic, x86_64: installed nvidia-384, 384.111, 4.10.0-42-generic, x86_64: installed nvidia-384, 384.111, 4.13.0-32-generic, x86_64: installed GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85ea] InstallationDate: Installed on 2017-08-26 (164 days ago) InstallationMedia: Ubuntu-Server 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-32-generic.efi.signed root=/dev/mapper/nvm--vg0-root ro rd.driver.blacklist=nouveau SourcePackage: unity UpgradeStatus: Upgraded to artful on 2018-02-05 (1 days ago) dmi.bios.date: 08/11/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0318 dmi.board.asset.tag: Default string dmi.board.name: PRIME X399-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0318:bd08/11/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX399-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1 version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~17.10.2 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~17.10.2 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications abou
[Desktop-packages] [Bug 1747827] [NEW] alt-tab no longer lets me switch between terminal windows
You have been subscribed to a public bug: I typically use multiple terminal windows, rather than tabs within terminal windows, because I find that the context of the visible part of the overlapping windows is highly useful. Up to 17.04, I could use alt-tab to switch between different windows that were each running a terminal instance. As of 17.10, I can only switch between "the current terminal focus window" and "other apps" -- other terminal windows are not part of the alt-tab "ring" Especially going back and forth between the two latest terminal windows with a single alt-tab is crucial to a productive workflow, and all OS-es I've used have supported this for the last 20 years. Except now, I'm expected to Alt-tab a few times to get "back" to terminal, then press arrow-down and arrow-right to select another terminal window. Wot? That's not helpful. This fundamentally breaks my workflow, and is not something I can live with. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: unity 7.5.0+17.10.20171010-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.gpus..42.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:42:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 384.111 Tue Dec 19 23:51:45 PST 2017 GCC version: gcc version 7.2.0 (Ubuntu 7.2.0-8ubuntu3) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. .tmp.unity_support_test.0: ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Feb 6 20:30:28 2018 DistUpgraded: 2018-02-05 15:47:10,383 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: artful DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.10.0-42-generic, x86_64: installed bbswitch, 0.8, 4.13.0-32-generic, x86_64: installed nvidia-384, 384.111, 4.10.0-42-generic, x86_64: installed nvidia-384, 384.111, 4.13.0-32-generic, x86_64: installed GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85ea] InstallationDate: Installed on 2017-08-26 (164 days ago) InstallationMedia: Ubuntu-Server 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-32-generic.efi.signed root=/dev/mapper/nvm--vg0-root ro rd.driver.blacklist=nouveau SourcePackage: unity UpgradeStatus: Upgraded to artful on 2018-02-05 (1 days ago) dmi.bios.date: 08/11/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0318 dmi.board.asset.tag: Default string dmi.board.name: PRIME X399-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0318:bd08/11/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX399-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1 version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~17.10.2 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~17.10.2 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful ubuntu -- alt-tab no longer lets me switch between terminal windows https://bugs.launchpad.net/bugs/1747827 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 405294] Re: A2DP Bluetooth audio skips terribly ["Skipping NNN us (= MMM bytes) in audio stream"]
Please note most users won't have an ath9k chip, so that bug won't be relevant to them. If you _do_ have an ath9k chip (see your 'lsmod' or 'lspci -k') then yeah bug 1746164 is probably the answer. Everyone else, please reply to my question in comment #149. ** Attachment removed: "The output of lspci on my system." https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/405294/+attachment/5045388/+files/lspci.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/405294 Title: A2DP Bluetooth audio skips terribly ["Skipping NNN us (= MMM bytes) in audio stream"] Status in PulseAudio: Confirmed Status in bluez package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: As I upgraded to the Karmic alpha, bluetooth audio (via a2dp) stopped working properly. It was working fine in Jaunty. My headphones are detected and configured by pulse, but the audio skips as if it's spending half of each second paused. Music is buffered so that after I click stop on rhythmbox (or whatever--it happens with whatever player I use) the audio continues until it's caught up. syslog is full of the following lines: Jul 27 08:55:45 carlin1 pulseaudio[3218]: alsa-source.c: Increasing minimal latency to 1.00 ms Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 15128 us (= 2668 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 36586 us (= 6452 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 35593 us (= 6276 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 36597 us (= 6452 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 32601 us (= 5748 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 32589 us (= 5748 bytes) in audio stream This is with bluez 4.45-0ubuntu4 pulseaudio1:0.9.15-4ubuntu2 0 pulseaudio version 1:0.9.16~test2-0ubuntu1~ppa3 from ubuntu-audio-dev didn't help. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/405294/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 298268] Re: shortcuts for view resize are not displayed in menu
Thank you for reporting this bug to Ubuntu. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. ** Changed in: totem (Ubuntu) Status: Triaged => Incomplete ** Changed in: gtk+2.0 (Ubuntu) Status: Triaged => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/298268 Title: shortcuts for view resize are not displayed in menu Status in GTK+: Expired Status in gtk+2.0 package in Ubuntu: Incomplete Status in totem package in Ubuntu: Incomplete Bug description: Binary package hint: totem Shortcuts exist in Totem to resize the movie window to different zoom ratios: 1:1, 2:1, 1:2. There are keyboard shortcuts for these (namely '1', '2', and '0') but they are not displayed in the menu. Displaying keyboard shortcuts in the menus is the most usable way for a user to discover what those shortcuts are, and so they should most definitely be displayed there. Please add the keyboard shortcuts for these commands to the Totem menus. To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/298268/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1748797] [NEW] tabs are closable if non-terminated jobs are stopped
Public bug reported: Just like `gnome-terminal` refuses to close a tab or the window if a process is running in the foreground, it should refuse to close if a started job has been interrupted using Ctrl+Z. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-terminal 3.24.2-0ubuntu4 Uname: Linux 4.15.0-041500-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Feb 12 01:07:35 2018 JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-terminal (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-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1748797 Title: tabs are closable if non-terminated jobs are stopped Status in gnome-terminal package in Ubuntu: New Bug description: Just like `gnome-terminal` refuses to close a tab or the window if a process is running in the foreground, it should refuse to close if a started job has been interrupted using Ctrl+Z. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-terminal 3.24.2-0ubuntu4 Uname: Linux 4.15.0-041500-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Feb 12 01:07:35 2018 JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1748797/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 202210] Re: gcalctool has problem with big sums
** Changed in: gcalctool Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gcalctool in Ubuntu. https://bugs.launchpad.net/bugs/202210 Title: gcalctool has problem with big sums Status in GCalctool: Incomplete Status in gcalctool package in Ubuntu: Fix Released Status in gcalctool source package in Hardy: Fix Released Status in gcalctool source package in Intrepid: Fix Released Bug description: How to reproduce : 1) Open gnome-calculator 2) Type 1+1+1+1+1000+1000 Results: You don't see the result unless you resize the window (make it wider). To manage notifications about this bug go to: https://bugs.launchpad.net/gcalctool/+bug/202210/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1748795] Re: gnome-terminal-server crashed with SIGSEGV in g_type_check_instance_is_a()
*** This bug is a duplicate of bug 1438014 *** https://bugs.launchpad.net/bugs/1438014 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1438014, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1748795/+attachment/5053251/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1748795/+attachment/5053253/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1748795/+attachment/5053257/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1748795/+attachment/5053258/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1748795/+attachment/5053259/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1748795/+attachment/5053260/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1748795/+attachment/5053261/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1438014 gnome-terminal-server and mate-terminal crash when setting keyboard shortcuts ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1748795 Title: gnome-terminal-server crashed with SIGSEGV in g_type_check_instance_is_a() Status in gnome-terminal package in Ubuntu: New Bug description: When i will change shortcut or edit profile in terminal from (edit=> preferences) after that terminal be crashed several time!!! ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-terminal 3.26.2-3ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.8-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Feb 12 00:12:57 2018 ExecutablePath: /usr/lib/gnome-terminal/gnome-terminal-server InstallationDate: Installed on 2018-02-11 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180210) ProcCmdline: /usr/lib/gnome-terminal/gnome-terminal-server SegvAnalysis: Segfault happened at: 0x7f36cff2677e : testb $0x4,0x16(%rdx) PC (0x7f36cff2677e) ok source "$0x4" ok destination "0x16(%rdx)" (0x7001e) not located in a known VMA region (needed writable region)! SegvReason: writing unknown VMA Signal: 11 SourcePackage: gnome-terminal StacktraceTop: g_type_check_instance_is_a () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 gtk_widget_get_toplevel () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 gtk_window_group_add_window () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 gtk_window_set_transient_for () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 Title: gnome-terminal-server crashed with SIGSEGV in g_type_check_instance_is_a() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1748795/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1748366] Re: LibreOffice 6.0.0.3 missing Elementary icons?
> I think the expectation here is that we would automatically get the > full suite of libreoffice-style packages via dependencies ... but that > may not be reality. Any reason why it can't be? Styles are not a dependency of any core libreoffice package because they're not needed for libreoffice to work correctly. They simply enhance the visual style, and as such can be manually installed by users according to their personal preferences. So not having a given style installed by default is, in the general case, expected. Note that libreoffice-style-elementary is recommended by ubuntustudio- desktop and xubuntu-desktop: $ apt rdepends libreoffice-style-elementary libreoffice-style-elementary Reverse Depends: Recommends: ubuntustudio-desktop Recommends: xubuntu-desktop ** Changed in: libreoffice (Ubuntu) Status: Confirmed => Invalid -- 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/1748366 Title: LibreOffice 6.0.0.3 missing Elementary icons? Status in libreoffice package in Ubuntu: Invalid Bug description: 09.02.2018 06:00 CET Ubuntu Mate 16.04.3 LTS Kernal 4.13.0-32-genericx86_64 Mate 1.16.2 Installed via software updater from LO 5.4.4 to LO 6.0.0.3 LO Build ID: 1:6.0.0~rc3-OubuntuO.16.04.1~lo7 There is no selection for the "elementary" icon set available under: Tools>Options>LibreOffice>View>Icon style Steps taken to resolve this: re-booted - no change apparent Currently only galaxy and tango icons available for selection on my installation. Is this a bug? 09.02.2018 21:39 CET You can install icons called "Elementary" via Synaptic. I don't understand the why and how. I'm merely reporting this in case it helps someone sort out whatever is happening. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1748366/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1728184] Re: mozjs38 is no longer supported by Mozilla
** Changed in: cinnamon-project Status: Unknown => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libproxy in Ubuntu. https://bugs.launchpad.net/bugs/1728184 Title: mozjs38 is no longer supported by Mozilla Status in Cinnamon: Fix Released Status in libproxy: New Status in 0ad package in Ubuntu: Confirmed Status in cjs package in Ubuntu: Triaged Status in libproxy package in Ubuntu: Triaged Status in mozjs38 package in Ubuntu: Triaged Bug description: mozjs38 is the SpiderMonkey JavaScript engine from Firefox 38 ESR. It has not been supported by Mozilla since June 2016. Please migrate to mozjs52, the only version currently supported by Mozilla. mozjs52 is available in Ubuntu 17.10 and 18.04 LTS and in Debian Testing. Currently these packages depend on mozjs38 -- 0ad (embedded code copy) cjs libproxy1-plugin-mozjs https://github.com/linuxmint/cjs/issues/52 https://github.com/libproxy/libproxy/issues/71 To manage notifications about this bug go to: https://bugs.launchpad.net/cinnamon-project/+bug/1728184/+subscriptions -- Mailing list: https://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 1748785] Re: Title Bar Buttons Obscured by Garbage
Any application started in it will show the problem. Example: mc (Midnight Commander). Thanks. Guido On 02/11/2018 01:21 PM, Hans Joachim Desserud wrote: > Thanks for taking your time to repor this issue and help making Ubuntu > better. > > Could you please attach a screen shot demonstrating the issue? Is this > limited to gnome-terminal alone, or are other windows affected as well? > > ** Changed in: gnome-terminal (Ubuntu) > Status: New => Incomplete > ** Attachment added: "Screenshot from 2018-02-11 13-57-36.png" https://bugs.launchpad.net/bugs/1748785/+attachment/5053237/+files/Screenshot%20from%202018-02-11%2013-57-36.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1748785 Title: Title Bar Buttons Obscured by Garbage Status in gnome-terminal package in Ubuntu: Incomplete Bug description: Gnome Terminal application has title bar upper right corner buttons obscured by an overlaid "chrome frame fragment". The buttons do, however, function. Please note. This annoying decoration has been around in Ubuntu for *many* years! Currently looking at the daily live build installed 2018 Feb 11. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-terminal 3.26.2-3ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.8-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Feb 11 12:10:12 2018 InstallationDate: Installed on 2018-02-11 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180210) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1748785/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1728184] Re: mozjs38 is no longer supported by Mozilla
** Bug watch added: github.com/linuxmint/cjs/issues #52 https://github.com/linuxmint/cjs/issues/52 ** Also affects: cinnamon-project via https://github.com/linuxmint/cjs/issues/52 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libproxy in Ubuntu. https://bugs.launchpad.net/bugs/1728184 Title: mozjs38 is no longer supported by Mozilla Status in Cinnamon: Unknown Status in libproxy: New Status in 0ad package in Ubuntu: Confirmed Status in cjs package in Ubuntu: Triaged Status in libproxy package in Ubuntu: Triaged Status in mozjs38 package in Ubuntu: Triaged Bug description: mozjs38 is the SpiderMonkey JavaScript engine from Firefox 38 ESR. It has not been supported by Mozilla since June 2016. Please migrate to mozjs52, the only version currently supported by Mozilla. mozjs52 is available in Ubuntu 17.10 and 18.04 LTS and in Debian Testing. Currently these packages depend on mozjs38 -- 0ad (embedded code copy) cjs libproxy1-plugin-mozjs https://github.com/linuxmint/cjs/issues/52 https://github.com/libproxy/libproxy/issues/71 To manage notifications about this bug go to: https://bugs.launchpad.net/cinnamon-project/+bug/1728184/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1748788] Re: gnome-shell crashed with signal 5 in g_log_default_handler()
*** This bug is a duplicate of bug 1748450 *** https://bugs.launchpad.net/bugs/1748450 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1748450, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1748788/+attachment/5053206/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1748788/+attachment/5053208/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1748788/+attachment/5053212/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1748788/+attachment/5053213/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1748788/+attachment/5053214/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1748788/+attachment/5053215/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1748788/+attachment/5053216/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1748450 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1748788 Title: gnome-shell crashed with signal 5 in g_log_default_handler() Status in gnome-shell package in Ubuntu: New Bug description: I installed PiTiVi and was seeing properties from some mp4 files when this message occurred. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.26.2-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.8-0ubuntu8 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME-Greeter:GNOME Date: Sun Feb 11 19:09:37 2018 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2017-11-12 (91 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171109) ProcCmdline: /usr/bin/gnome-shell Signal: 5 SourcePackage: gnome-shell StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-shell crashed with signal 5 in g_log_default_handler() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1748788/+subscriptions -- Mailing list: https://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 1727653] Re: error: can't start new thread
I would bet the update will fix it. Huge manifests go into memory, in
bulk, and in lists. The lists stay around and if Python GC is not working
properly, the bulk reads do as well. During processing, there were as many
as 3 copies of the manifest in memory, one bulk, one the result of re
iteration, and the other in the collection list. That kind of misuse can
really screw up GC.
As answer to your question, changing to 'ulimit -n 10240' could help in a
very cases, but I would try both individually to see which one does the job.
If they are still on the 0.6-series, the 'ulimit' fix is the only one that
would work.
On Sun, Feb 11, 2018 at 12:34 PM, Michael Terry
wrote:
> I'd also be curious if this is because of duplicity <0.7.16 or because
> of the ulimit line we use for deja-dup-monitor. It's not clear to me if
> I should change the ulimit line or if we just need to update duplicity
> for those users affected.
>
> --
> You received this bug notification because you are a bug assignee.
> 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:
> Triaged
> 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.la
[Desktop-packages] [Bug 1747566] Re: org.gnome.Shell.desktop stacktraces; tweener.js:73
Just to add a possible cause for concern. This is creating about 100G of syslog per day on my bionic system that is just mostly idling. -- 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/1747566 Title: org.gnome.Shell.desktop stacktraces; tweener.js:73 Status in gnome-shell package in Ubuntu: In Progress Bug description: I'm running Ubuntu Bionic. After latest dist-upgrade today I'm not getting a lot of stacktraces in my syslog: Feb 5 16:14:04 fog gnome-shell[5676]: Object Clutter.Actor (0x55c40613dde0), has been already finalized. Impossible to get any property from it. Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: == Stack trace for context 0x55c40593a000 == Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: #0 0x7fff5f700870 b resource:///org/gnome/shell/ui/tweener.js:73 (0x7f38c40ddef0 @ 9) Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: #1 0x7fff5f700910 b resource:///org/gnome/shell/ui/tweener.js:105 (0x7f38c40df230 @ 36) Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: #2 0x7fff5f7009b0 b resource:///org/gnome/shell/ui/tweener.js:92 (0x7f38c40df098 @ 52) Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: #3 0x7fff5f700a20 I resource:///org/gnome/gjs/modules/tweener/tweener.js:203 (0x7f38c40e9cd0 @ 54) Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: #4 0x7fff5f700b70 b resource:///org/gnome/gjs/modules/tweener/tweener.js:332 (0x7f38c40e9d58 @ 1626) Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: #5 0x7fff5f700c20 b resource:///org/gnome/gjs/modules/tweener/tweener.js:345 (0x7f38c40e9de0 @ 100) Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: #6 0x7fff5f700cb0 b resource:///org/gnome/gjs/modules/tweener/tweener.js:360 (0x7f38c40e9e68 @ 10) Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: #7 0x7fff5f700da0 b resource:///org/gnome/gjs/modules/signals.js:126 (0x7f38c40e2b38 @ 386) Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: #8 0x7fff5f700e50 b resource:///org/gnome/shell/ui/tweener.js:208 (0x7f38c40df808 @ 159) Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: #9 0x7fff5f700eb0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f38c40c2bc0 @ 71) Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: #10 0x7fff5f700eb0 I resource:///org/gnome/shell/ui/tweener.js:183 (0x7f38c40df780 @ 20) Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: #11 0x7fff5f700f50 I self-hosted:917 (0x7f38c40ee5e8 @ 394) Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: == Stack trace for context 0x55c40593a000 == Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: #0 0x7fff5f700870 b resource:///org/gnome/shell/ui/tweener.js:80 (0x7f38c40ddef0 @ 82) Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: #1 0x7fff5f700910 b resource:///org/gnome/shell/ui/tweener.js:105 (0x7f38c40df230 @ 36) Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: #2 0x7fff5f7009b0 b resource:///org/gnome/shell/ui/tweener.js:92 (0x7f38c40df098 @ 52) Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: #3 0x7fff5f700a20 I resource:///org/gnome/gjs/modules/tweener/tweener.js:203 (0x7f38c40e9cd0 @ 54) Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: #4 0x7fff5f700b70 b resource:///org/gnome/gjs/modules/tweener/tweener.js:332 (0x7f38c40e9d58 @ 1626) Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: #5 0x7fff5f700c20 b resource:///org/gnome/gjs/modules/tweener/tweener.js:345 (0x7f38c40e9de0 @ 100) Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: #6 0x7fff5f700cb0 b resource:///org/gnome/gjs/modules/tweener/tweener.js:360 (0x7f38c40e9e68 @ 10) Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: #7 0x7fff5f700da0 b resource:///org/gnome/gjs/modules/signals.js:126 (0x7f38c40e2b38 @ 386) Feb 5 16:14:04 fog gnome-shell[5676]: Object Clutter.Actor (0x55c40613dde0), has been already finalized. Impossible to set any property to it. Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: #8 0x7fff5f700e50 b resource:///org/gnome/shell/ui/tweener.js:208 (0x7f38c40df808 @ 159) Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: #9 0x7fff5f700eb0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f38c40c2bc0 @ 71) Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: #10 0x7fff5f700eb0 I resource:///org/gnome/shell/ui/tweener.js:183 (0x7f38c40df780 @ 20) Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: #11 0x7fff5f700f50 I self-hosted:917 (0x7f38c40ee5e8 @ 394) Feb 5 16:14:04 fog gnome-shell[5676]: Object St.BoxLayout (0x55c407f24860), has been already finalized. Impossible to get any property from it. Feb 5 16:14:04 fog gnome-shell[5676]: Object St.BoxLayout (0x55c407f24860), has been already finalized. Impossible to set any property to it. Feb 5 16:14:04 fog org.gnome.Shell.desktop[5676]: == Stack trace for context 0x55c40593a000 == Feb 5 16:14:04 fog org.gnome.Shell.desktop
[Desktop-packages] [Bug 1748785] Re: Title Bar Buttons Obscured by Garbage
Thanks for taking your time to repor this issue and help making Ubuntu better. Could you please attach a screen shot demonstrating the issue? Is this limited to gnome-terminal alone, or are other windows affected as well? ** Changed in: gnome-terminal (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1748785 Title: Title Bar Buttons Obscured by Garbage Status in gnome-terminal package in Ubuntu: Incomplete Bug description: Gnome Terminal application has title bar upper right corner buttons obscured by an overlaid "chrome frame fragment". The buttons do, however, function. Please note. This annoying decoration has been around in Ubuntu for *many* years! Currently looking at the daily live build installed 2018 Feb 11. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-terminal 3.26.2-3ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.8-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Feb 11 12:10:12 2018 InstallationDate: Installed on 2018-02-11 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180210) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1748785/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1626731] Re: uvcvideo 1-1.4:1.0: Entity type for entity Extension 4 was not initialized!
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu-drivers-common (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1626731 Title: uvcvideo 1-1.4:1.0: Entity type for entity Extension 4 was not initialized! Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Status in ubuntu-drivers-common package in Ubuntu: Confirmed Bug description: [6.453850] uvcvideo 1-1.4:1.0: Entity type for entity Extension 4 was not initialized! [6.453858] uvcvideo 1-1.4:1.0: Entity type for entity Processing 2 was not initialized! [6.453862] uvcvideo 1-1.4:1.0: Entity type for entity Camera 1 was not initialized! ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-image-4.8.0-14-generic 4.8.0-14.15 ProcVersionSignature: Ubuntu 4.8.0-14.15-generic 4.8.0-rc7 Uname: Linux 4.8.0-14-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: caravena 2032 F...m pulseaudio /dev/snd/controlC0: caravena 2032 F pulseaudio CurrentDesktop: GNOME Date: Thu Sep 22 17:20:51 2016 HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87 InstallationDate: Installed on 2015-07-26 (424 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150723) MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-14-generic root=UUID=4f4435ca-b877-47a5-9065-3dd624c0514e ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.8.0-14-generic N/A linux-backports-modules-4.8.0-14-generic N/A linux-firmware1.161 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P14AAJ dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SAMSUNG_NP1234567890 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.name: 530U3C/530U4C dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1626731/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1748785] [NEW] Title Bar Buttons Obscured by Garbage
Public bug reported: Gnome Terminal application has title bar upper right corner buttons obscured by an overlaid "chrome frame fragment". The buttons do, however, function. Please note. This annoying decoration has been around in Ubuntu for *many* years! Currently looking at the daily live build installed 2018 Feb 11. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-terminal 3.26.2-3ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.8-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Feb 11 12:10:12 2018 InstallationDate: Installed on 2018-02-11 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180210) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-terminal (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 gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1748785 Title: Title Bar Buttons Obscured by Garbage Status in gnome-terminal package in Ubuntu: New Bug description: Gnome Terminal application has title bar upper right corner buttons obscured by an overlaid "chrome frame fragment". The buttons do, however, function. Please note. This annoying decoration has been around in Ubuntu for *many* years! Currently looking at the daily live build installed 2018 Feb 11. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-terminal 3.26.2-3ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.8-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Feb 11 12:10:12 2018 InstallationDate: Installed on 2018-02-11 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180210) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1748785/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1748783] [NEW] package gnome-menus 3.13.3-11ubuntu1 failed to install/upgrade: triggers looping, abandoned
Public bug reported: Happens every time I log in to any account on this computer. Not a lot of details to be gleaned from the initial error reporting. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: gnome-menus 3.13.3-11ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.8-0ubuntu8 Architecture: amd64 Date: Sun Feb 11 10:39:25 2018 Dependencies: ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2018-01-22 (20 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180121) Python3Details: /usr/bin/python3.6, Python 3.6.4, python3-minimal, 3.6.4-1 PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4 RelatedPackageVersions: dpkg 1.19.0.5ubuntu1 apt 1.6~alpha7ubuntu1 SourcePackage: gnome-menus Title: package gnome-menus 3.13.3-11ubuntu1 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-menus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-menus in Ubuntu. https://bugs.launchpad.net/bugs/1748783 Title: package gnome-menus 3.13.3-11ubuntu1 failed to install/upgrade: triggers looping, abandoned Status in gnome-menus package in Ubuntu: New Bug description: Happens every time I log in to any account on this computer. Not a lot of details to be gleaned from the initial error reporting. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: gnome-menus 3.13.3-11ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.8-0ubuntu8 Architecture: amd64 Date: Sun Feb 11 10:39:25 2018 Dependencies: ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2018-01-22 (20 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180121) Python3Details: /usr/bin/python3.6, Python 3.6.4, python3-minimal, 3.6.4-1 PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4 RelatedPackageVersions: dpkg 1.19.0.5ubuntu1 apt 1.6~alpha7ubuntu1 SourcePackage: gnome-menus Title: package gnome-menus 3.13.3-11ubuntu1 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-menus/+bug/1748783/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1738984] Re: slowness
Wagner Toscano: >" I'm just finding it very slow." 1) What are you finding slow, the booting process, using the OS after login, etc.? By how much is it slow in seconds, minutes, etc.? 2) Is this something that started to happen after an update? If so, which precisely? 3) Could you please attach a video that demonstrates the slowness? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1738984 Title: slowness Status in xorg package in Ubuntu: Incomplete Bug description: The boot sometimes fails. Many applications, such as Firefox, Chromium, Eclipse and even Nautilus crash the system for a while. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-104.127-generic 4.4.98 Uname: Linux 4.4.0-104-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.14 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Tue Dec 19 07:19:17 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Curacao XT [Radeon R7 370 / R9 270X/370 OEM] [1002:6810] (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Curacao XT [Radeon R7 370 / R9 270X/370 OEM] [1458:2272] InstallationDate: Installed on 2017-08-15 (125 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-104-generic root=UUID=d065c847-7bd5-4dda-ad58-74db9d131eb7 ro drm.debug=0xe plymouth:debug SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/23/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FB dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 990FXA-UD5 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFB:bd01/23/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rn990FXA-UD5:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Tue Dec 19 05:45:23 2017 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputPixArt Microsoft USB Optical Mouse MOUSE, id 8 inputMicrosoft Wired Keyboard 400 KEYBOARD, id 9 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.7 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1738984/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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
I'd also be curious if this is because of duplicity <0.7.16 or because
of the ulimit line we use for deja-dup-monitor. It's not clear to me if
I should change the ulimit line or if we just need to update duplicity
for those users affected.
--
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:
Triaged
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 1715357] Re: I am unable to update firefox installed on my vmware based ubuntu
Thank you for reporting this issue to Ubuntu. The Wily (15.10) release reached EOL on 28th July 2016. The repositories that you are trying to download from have long since been moved. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases See also https://help.ubuntu.com/community/EOLUpgrades ** Changed in: firefox (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1715357 Title: I am unable to update firefox installed on my vmware based ubuntu Status in firefox package in Ubuntu: Invalid Bug description: I want to create reps on github . Its asking updated version of firefox.If i click on help and about firefox nothing is getting updated. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: firefox 42.0+build2-0ubuntu0.15.10.1 ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3 Uname: Linux 4.2.0-18-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.19.1-0ubuntu4 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: BuildID: 20151030083518 Channel: Unavailable CurrentDesktop: Unity Date: Wed Sep 6 02:54:35 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 2015-11-12 (663 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) IpRoute: default via 192.168.29.2 dev ens33 proto static metric 100 169.254.0.0/16 dev ens33 scope link metric 1000 192.168.29.0/24 dev ens33 proto kernel scope link src 192.168.29.128 metric 100 IwConfig: ens33 no wireless extensions. lono wireless extensions. Locales: extensions.sqlite corrupt or missing PrefSources: prefs.js ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Profiles: Profile0 (Default) - LastVersion=42.0/20151030083518 (In use) RfKill: RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/02/2015 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/02/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1715357/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1747199] Re: Cannot monitor nor stop/resume automatic deja-dup backup: monitor window absent
If you click on the "backup started" notification, you should be able to see the progress. ** Changed in: deja-dup (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to deja-dup in Ubuntu. https://bugs.launchpad.net/bugs/1747199 Title: Cannot monitor nor stop/resume automatic deja-dup backup: monitor window absent Status in deja-dup package in Ubuntu: Incomplete Bug description: In latest versions of deja dup, there is no window created to monitor the progress of an automated backup. This means there's no way to tell how much is left to go, and no way to stop it cleanly if it is taking too long or if one wishes to resume it later. It should, I think, still be the case that when an automatic backup is started, a window appears which shows the status/progress, offers details, and gives an option to abort or pause the backup process. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: deja-dup 36.3-0ubuntu0.1 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Feb 3 13:53:29 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-18 (77 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/1747199/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1701783] Re: xdg-mime query default inode/directory returns wrong result
** Changed in: lubuntu-next Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-utils in Ubuntu. https://bugs.launchpad.net/bugs/1701783 Title: xdg-mime query default inode/directory returns wrong result Status in Lubuntu Next: Fix Released Status in xdg-utils package in Ubuntu: Fix Released Status in xdg-utils package in Debian: Confirmed Bug description: On 17.10 alpha: $ xdg-mime query default inode/directory nautilus-folder-handler.desktop I assume the correct result for now would be pcmanfm.desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/lubuntu-next/+bug/1701783/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1748748] Re: Evolutiion fails to start. Cannot connect /tmp/dbus-*
Yet another follow-up: I did a 'pkill -9 evolution' after which I could start evolution. After a logout/login evolution would not start. After a pkill it did. Removing the evolution background servers from the session startup cleared the problem. I could then also start evolution automatically at session startup. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1748748 Title: Evolutiion fails to start. Cannot connect /tmp/dbus-* Status in evolution package in Ubuntu: New Bug description: I have a new installation of xubuntu 16.04 fully updated within the past hour, running on a Lenovo T550. I have been using Evolution for a couple oof dys, but after this morning's update it is failing to start. Error message is $ evolution ** (evolution:3169): WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-4Me0oN1k69: Connection refused Nothing in syslog. $ lsb_release -rd Description: Ubuntu 16.04.3 LTS Release: 16.04 $ apt-cache policy evolution evolution: Installed: 3.18.5.2-0ubuntu3.2 Candidate: 3.18.5.2-0ubuntu3.2 Version table: *** 3.18.5.2-0ubuntu3.2 500 500 http://gb.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 Packages 100 /var/lib/dpkg/status 3.18.5.2-0ubuntu1 500 500 http://gb.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: evolution 3.18.5.2-0ubuntu3.2 ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98 Uname: Linux 4.4.0-112-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Sun Feb 11 12:19:26 2018 InstallationDate: Installed on 2018-02-09 (2 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: evolution UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1748748/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1737618] Re: ibus not working in Ubuntu wayland session: traps: ibus-ui-gtk3[1565] general protection ip:7fd4204dd253 sp:7ffd74de90b0 error:0 in libX11.so.6.3.0[7fd420440000+13
Hi, ibus is not working after months gone by. If I check ps aux |grep ibus shows that ibus is launched. But, there is nothing visible. No panel menu, no input option if I press SUPER+L . Kindly, let me know if anything can be done to resolve this. :~$ ps aux |grep -i ibus gdm 4848 0.0 0.1 368428 9876 tty1 Sl 20:39 0:00 ibus-daemon --xim --panel disable gdm 4851 0.0 0.0 287000 7508 tty1 Sl 20:39 0:00 /usr/lib/ibus/ibus-dconf gdm 4854 0.0 0.3 409656 28012 tty1 Sl 20:39 0:00 /usr/lib/ibus/ibus-x11 --kill-daemon gdm 4917 0.0 0.0 211084 7460 tty1 Sl 20:39 0:00 /usr/lib/ibus/ibus-engine-simple admin20+ 5154 0.0 0.1 370704 10304 tty2 Sl 20:40 0:02 ibus-daemon --xim --panel disable admin20+ 5164 0.0 0.0 289112 7564 tty2 Sl 20:40 0:00 /usr/lib/ibus/ibus-dconf admin20+ 5166 0.0 0.3 411336 28176 tty2 Sl 20:40 0:01 /usr/lib/ibus/ibus-x11 --kill-daemon admin20+ 5290 0.0 0.0 213380 7512 tty2 Sl 20:40 0:00 /usr/lib/ibus/ibus-engine-simple -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1737618 Title: ibus not working in Ubuntu wayland session: traps: ibus-ui-gtk3[1565] general protection ip:7fd4204dd253 sp:7ffd74de90b0 error:0 in libX11.so.6.3.0[7fd42044+134000] Status in ibus package in Ubuntu: Confirmed Bug description: Hi, ibus is not loading neither the applet appearing in Gnome Shell wayland session in Ubuntu 17.10. These are the error messages I can find: :~$ cat /var/log/kern.log |grep ibus* Dec 11 02:47:32 HP-LAPTOP kernel: [ 356.188579] SGI XFS with ACLs, security attributes, realtime, no debug enabled Dec 11 05:26:54 HP-LAPTOP kernel: [ 77.136259] traps: ibus-ui-gtk3[1565] general protection ip:7fd4204dd253 sp:7ffd74de90b0 error:0 in libX11.so.6.3.0[7fd42044+134000] Dec 11 05:54:19 HP-LAPTOP kernel: [ 138.126513] traps: ibus-ui-gtk3[2277] general protection ip:7f4b7a06b253 sp:7fffe3c94860 error:0 in libX11.so.6.3.0[7f4b79fce000+134000] Dec 12 00:39:20 HP-LAPTOP kernel: [ 1355.581927] SGI XFS with ACLs, security attributes, realtime, no debug enabled I tried changing input method using im-config to xim and it did not yield any positive results. Also, I remember one time, there was a segmentation fault happened with ibus which I cannot reproduce again on this system. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: ibus-wayland 1.5.14-2ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 Uname: Linux 4.13.0-19-generic x86_64 NonfreeKernelModules: ndiswrapper ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Dec 12 02:20:20 2017 InstallationDate: Installed on 2017-11-22 (19 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: ibus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1737618/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1727174] Re: ibus not working, Error: traps: ibus-ui-gtk3[4578] general protection ip:7fb85293d253 sp:7ffeecf73800 error:0 in libX11.so.6.3.0[7fb8528a0000+134000]
*** This bug is a duplicate of bug 1737618 *** https://bugs.launchpad.net/bugs/1737618 Hi, ibus is not working after months gone by. If I check ps aux |grep ibus shows that ibus is launched. But, there is nothing visible. No panel menu, no input option if I press SUPER+L . Kindly, let me know if anything can be done to resolve this. :~$ ps aux |grep -i ibus gdm 4848 0.0 0.1 368428 9876 tty1 Sl 20:39 0:00 ibus-daemon --xim --panel disable gdm 4851 0.0 0.0 287000 7508 tty1 Sl 20:39 0:00 /usr/lib/ibus/ibus-dconf gdm 4854 0.0 0.3 409656 28012 tty1 Sl 20:39 0:00 /usr/lib/ibus/ibus-x11 --kill-daemon gdm 4917 0.0 0.0 211084 7460 tty1 Sl 20:39 0:00 /usr/lib/ibus/ibus-engine-simple admin20+ 5154 0.0 0.1 370704 10304 tty2 Sl 20:40 0:02 ibus-daemon --xim --panel disable admin20+ 5164 0.0 0.0 289112 7564 tty2 Sl 20:40 0:00 /usr/lib/ibus/ibus-dconf admin20+ 5166 0.0 0.3 411336 28176 tty2 Sl 20:40 0:01 /usr/lib/ibus/ibus-x11 --kill-daemon admin20+ 5290 0.0 0.0 213380 7512 tty2 Sl 20:40 0:00 /usr/lib/ibus/ibus-engine-simple -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1727174 Title: ibus not working, Error: traps: ibus-ui-gtk3[4578] general protection ip:7fb85293d253 sp:7ffeecf73800 error:0 in libX11.so.6.3.0[7fb8528a+134000] Status in ibus package in Ubuntu: Incomplete Bug description: uname -a Linux Danny-Yoga 4.13.0-16-lowlatency #19-Ubuntu SMP PREEMPT Wed Oct 11 19:51:52 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux lsb_release -a LSB Version: core-9.20160110ubuntu5-amd64:core-9.20160110ubuntu5-noarch:security-9.20160110ubuntu5-amd64:security-9.20160110ubuntu5-noarch Distributor ID: Ubuntu Description: Ubuntu 17.10 Release: 17.10 Codename: artful read-config SCHEMA: org.freedesktop.ibus.general dconf-preserve-name-prefixes: ['/desktop/ibus/engine/pinyin', '/desktop/ibus/engine/bopomofo', '/desktop/ibus/engine/hangul'] use-system-keyboard-layout: true embed-preedit-text: true enable-by-default: false use-global-engine: false use-xmodmap: true switcher-delay-time: 400 version: '1.5.14' engines-order: ['libpinyin'] preload-engines: ['libpinyin', 'xkb:us::eng'] xkb-latin-layouts: ['ara', 'bg', 'cz', 'dev', 'gr', 'gur', 'in', 'jp(kana)', 'mal', 'mkd', 'ru', 'ua'] SCHEMA: org.freedesktop.ibus.general.hotkey next-engine: ['Alt+Shift_L'] disable-unconditional: @as [] enable-unconditional: @as [] trigger: ['Control+space', 'Zenkaku_Hankaku', 'Alt+Kanji', 'Alt+grave', 'Hangul', 'Alt+Release+Alt_R'] previous-engine: @as [] prev-engine: @as [] next-engine-in-menu: ['Alt+Shift_L'] triggers: ['space'] SCHEMA: org.freedesktop.ibus.panel x: -1 property-icon-delay-time: 500 y: -1 lookup-table-orientation: 1 show: 2 xkb-icon-rgba: '#415099' auto-hide-timeout: 1 show-im-name: false follow-input-cursor-when-always-shown: false custom-font: 'Sans 10' show-icon-on-systray: true use-custom-font: false ibus engine xkb:us::eng ps -ef|grep ibus gdm 1969 1647 0 12:42 tty1 00:00:00 ibus-daemon --xim --panel disable gdm 1972 1969 0 12:42 tty1 00:00:00 /usr/lib/ibus/ibus-dconf gdm 1975 1 0 12:42 tty1 00:00:00 /usr/lib/ibus/ibus-x11 --kill-daemon gdm 2046 1969 0 12:42 tty1 00:00:00 /usr/lib/ibus/ibus-engine-simple hdzhong 2516 2433 0 12:42 tty2 00:00:02 ibus-daemon --xim --panel disable hdzhong 3966 2516 0 12:53 tty2 00:00:00 /usr/lib/ibus/ibus-dconf hdzhong 3968 1 0 12:53 tty2 00:00:00 /usr/lib/ibus/ibus-x11 --kill-daemon hdzhong 3984 2516 0 12:53 tty2 00:00:00 /usr/lib/ibus/ibus-engine-simple hdzhong 4198 3939 0 12:58 pts/100:00:00 grep --color=auto ibus dpkg: ii ibus 1.5.14-2ubuntu1 amd64 Intelligent Input Bus - core ii ibus-anthy 1.5.9-2 amd64anthy engine for IBus ii ibus-clutter:amd64 0.0+git20090728.a936bacf-5.1 amd64ibus input method framework for clutter ii ibus-gtk:amd64 1.5.14-2ubuntu1 amd64 Intelligent Input Bus - GTK+2 support ii ibus-gtk3:amd64 1.5.14-2ubuntu1 amd64 Intelligent Input Bus - GTK+3 support ii ibus-libpinyin 1.7.3-2 amd64 Intelligent Pinyin engine based on libpinyin for IBus ii ibus-qt4 1.3.3-1 amd64 qt-immodule for ibus (QT4) (plugin) ii ibus-sunpinyin 2.0.3-5build3amd64 sunpinyin engine for ibus ii ibus-table 1.9.14-3 all table e
[Desktop-packages] [Bug 1722454] Re: Duplicity fails with MemoryError
*** This bug is a duplicate of bug 1720159 ***
https://bugs.launchpad.net/bugs/1720159
Please upgrade to the current version of duplicity, 0.7.16. This will assure
that any bugs fixed since your release are available and may fix your issue.
This applies especially to duplicity versions between 0.7.03 and 0.7.14
inclusive. There was a fix in 0.7.15 that reduced memory usage drastically,
and will help with memory errors and inability to start new threads.
The bug that was resolved in 0.7.15:
* Fixed bug #1720159 - Cannot allocate memory with large manifest file since
0.7.03
- filelist is not read if --file-changed option in collection-status not
present
- This will keep memory usage lower in non collection-status operations
There are three options:
* Release tarball Install - https://launchpad.net/duplicity/+download
* Daily duplicity builds -
https://launchpad.net/~duplicity-team/+archive/ubuntu/daily
* Stable duplicity builds -
https://launchpad.net/~duplicity-team/+archive/ubuntu/ppa
NOTE: UNinstall duplicity first if it was installed via the distribution
repository. For Ubuntu, that would be "sudo apt-get purge duplicity".
--
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/1722454
Title:
Duplicity fails with MemoryError
Status in Duplicity:
New
Status in duplicity package in Ubuntu:
Confirmed
Bug description:
Running the following command:
/usr/bin/python /usr/bin/duplicity collection-status
--exclude=/mnt/jabba/juergh/backup/gollum
--include=/home/juergh/.cache/deja-dup/metadata --exclude=/home/juergh
/.uk-pkg --exclude=/home/juergh/Music --exclude=/home/juergh/debug
--exclude=/home/juergh/canonical/cve-matrix/cve-matrix/cve-tracker
--exclude=/home/juergh/canonical/cve-matrix/cve-autotriage
--exclude=/home/juergh/Desktop --exclude=/home/juergh/.cache
--exclude=/home/juergh/tmp --exclude=/home/juergh/git
--exclude=/home/juergh/Downloads
--exclude=/home/juergh/.local/share/Trash
--exclude=/home/juergh/.cache/deja-dup/tmp
--exclude=/home/juergh/.thumbnails --exclude=/home/juergh/.cache/deja-
dup --exclude=/home/juergh/.cache --include=/home/juergh
--exclude=/sys --exclude=/run --exclude=/proc --exclude=/var/tmp
--exclude=/tmp --exclude=** --gio
file:///mnt/jabba/juergh/backup/gollum --no-encryption --verbosity=9
--gpg-options=--no-use-agent --archive-dir=/home/juergh/.cache/deja-
dup --tempdir=/home/juergh/.cache/deja-dup/tmp --log-fd=19
results in:
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 1416, in do_backup
globals.archive_dir).set_values()
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 710,
in set_values
self.get_backup_chains(partials + backend_filename_list)
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 836,
in get_backup_chains
add_to_sets(f)
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 824,
in add_to_sets
if set.add_filename(filename):
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 101,
in add_filename
self.set_manifest(filename)
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 148,
in set_manifest
self.set_files_changed()
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 128,
in set_files_changed
mf = self.get_manifest()
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 250,
in get_manifest
return self.get_local_manifest()
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 224,
in get_local_manifest
return manifest.Manifest().from_string(manifest_buffer)
File "/usr/lib/python2.7/dist-packages/duplicity/manifest.py", line 215, in
from_string
vi = VolumeInfo().from_string(match.group(1))
File "/usr/lib/python2.7/dist-packages/duplicity/manifest.py", line 383, in
from_string
linelist = s.strip().split("\n")
MemoryError
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: duplicity 0.7.12-1ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
Uname: Linux 4.13.0-12-generic x86_64
ApportVersion: 2.20.7-0ubuntu2
Architecture: amd64
CurrentDesktop: GNOME
Date: Tue Oct 10 08:05:45 2017
InstallationDate: Installed on 2017-05-25 (137 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
SourcePackage: duplicity
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/duplicity/+bug/1722454/+subscriptions
--
Mailing list: https://launchp
[Desktop-packages] [Bug 1748762] Re: GNOME Characters translation is missing
Thanks for your report. This is a new package in main. I have approved the template in the import queue, and that's probably it. Let's confirm it when the language packs have been updated next time. ** Changed in: ubuntu-translations Importance: Undecided => High ** Changed in: ubuntu-translations Status: New => In Progress ** Changed in: ubuntu-translations Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj) ** Changed in: gnome-characters (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-characters in Ubuntu. https://bugs.launchpad.net/bugs/1748762 Title: GNOME Characters translation is missing Status in Ubuntu Translations: In Progress Status in gnome-characters package in Ubuntu: Invalid Bug description: GNOME Characters is untranslated on non-English Ubuntu 18.04. It looks like the translations are missing or not applied for some reason. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/1748762/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1683080] Re: package libcuda1-352 361.45.11-0ubuntu0.16.04.1 failed to install/upgrade: there is no script in the new version of the package - giving up
That version is now dead http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml ** Changed in: nvidia-graphics-drivers-361 (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-361 in Ubuntu. https://bugs.launchpad.net/bugs/1683080 Title: package libcuda1-352 361.45.11-0ubuntu0.16.04.1 failed to install/upgrade: there is no script in the new version of the package - giving up Status in nvidia-graphics-drivers-361 package in Ubuntu: Invalid Bug description: failed during 'sudo aptitude dist-upgrade' ProblemType: Package DistroRelease: Ubuntu 17.04 Package: libcuda1-352 361.45.11-0ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 Date: Sat Apr 15 15:37:45 2017 ErrorMessage: there is no script in the new version of the package - giving up InstallationDate: Installed on 2015-03-23 (754 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: nvidia-graphics-drivers-361 Title: package libcuda1-352 361.45.11-0ubuntu0.16.04.1 failed to install/upgrade: there is no script in the new version of the package - giving up UpgradeStatus: Upgraded to zesty on 2017-04-15 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-361/+bug/1683080/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1722454] Re: Duplicity fails with MemoryError
*** This bug is a duplicate of bug 1720159 ***
https://bugs.launchpad.net/bugs/1720159
Adding my own t/b. It is little different from other posts on this page.
Version info:
$ apt show duplicity
Package: duplicity
Version: 0.7.12-1ubuntu1
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 763, in get_fileobj_iter
manifest = backup_set.get_manifest()
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 250,
in get_manifest
return self.get_local_manifest()
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 224,
in get_local_manifest
return manifest.Manifest().from_string(manifest_buffer)
File "/usr/lib/python2.7/dist-packages/duplicity/manifest.py", line 207, in
from_string
self.files_changed = list(map(parse_fileinfo, match.group(3).split('\n')))
File "/usr/lib/python2.7/dist-packages/duplicity/manifest.py", line 204, in
parse_fileinfo
fileinfo = line.strip().split()
MemoryError
--
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/1722454
Title:
Duplicity fails with MemoryError
Status in Duplicity:
New
Status in duplicity package in Ubuntu:
Confirmed
Bug description:
Running the following command:
/usr/bin/python /usr/bin/duplicity collection-status
--exclude=/mnt/jabba/juergh/backup/gollum
--include=/home/juergh/.cache/deja-dup/metadata --exclude=/home/juergh
/.uk-pkg --exclude=/home/juergh/Music --exclude=/home/juergh/debug
--exclude=/home/juergh/canonical/cve-matrix/cve-matrix/cve-tracker
--exclude=/home/juergh/canonical/cve-matrix/cve-autotriage
--exclude=/home/juergh/Desktop --exclude=/home/juergh/.cache
--exclude=/home/juergh/tmp --exclude=/home/juergh/git
--exclude=/home/juergh/Downloads
--exclude=/home/juergh/.local/share/Trash
--exclude=/home/juergh/.cache/deja-dup/tmp
--exclude=/home/juergh/.thumbnails --exclude=/home/juergh/.cache/deja-
dup --exclude=/home/juergh/.cache --include=/home/juergh
--exclude=/sys --exclude=/run --exclude=/proc --exclude=/var/tmp
--exclude=/tmp --exclude=** --gio
file:///mnt/jabba/juergh/backup/gollum --no-encryption --verbosity=9
--gpg-options=--no-use-agent --archive-dir=/home/juergh/.cache/deja-
dup --tempdir=/home/juergh/.cache/deja-dup/tmp --log-fd=19
results in:
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 1416, in do_backup
globals.archive_dir).set_values()
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 710,
in set_values
self.get_backup_chains(partials + backend_filename_list)
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 836,
in get_backup_chains
add_to_sets(f)
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 824,
in add_to_sets
if set.add_filename(filename):
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 101,
in add_filename
self.set_manifest(filename)
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 148,
in set_manifest
self.set_files_changed()
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 128,
in set_files_changed
mf = self.get_manifest()
File "/usr/lib/python2.7/dist-packages/duplicity/collections
[Desktop-packages] [Bug 1704765] Re: can't drag file from desktop to folder window on Artful
Confirming that I'm seeing this as well. Switched to running Xorg to avoid it. Xorg drag and drop across screens results in a copy instead of a move but at least doesn't freeze. -- 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/1704765 Title: can't drag file from desktop to folder window on Artful Status in Nautilus: Confirmed Status in nautilus package in Ubuntu: Triaged Bug description: I'm running Ubuntu 17.10 (Artful). If I create a text file on my desktop and then attempt to drag it into a Nautilus folder window, it fails: when I release the mouse cursor over the folder window nothing happens and the file is not moved. To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1704765/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1683081] Re: package nvidia-opencl-icd-352 361.45.11-0ubuntu0.16.04.1 failed to install/upgrade: there is no script in the new version of the package - giving up
That version is now dead http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml ** Changed in: nvidia-graphics-drivers-361 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-361 in Ubuntu. https://bugs.launchpad.net/bugs/1683081 Title: package nvidia-opencl-icd-352 361.45.11-0ubuntu0.16.04.1 failed to install/upgrade: there is no script in the new version of the package - giving up Status in nvidia-graphics-drivers-361 package in Ubuntu: Invalid Bug description: failed during 'sudo aptitude dist-upgrade' ProblemType: Package DistroRelease: Ubuntu 17.04 Package: nvidia-opencl-icd-352 361.45.11-0ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 Date: Sat Apr 15 15:37:50 2017 ErrorMessage: there is no script in the new version of the package - giving up InstallationDate: Installed on 2015-03-23 (754 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: nvidia-graphics-drivers-361 Title: package nvidia-opencl-icd-352 361.45.11-0ubuntu0.16.04.1 failed to install/upgrade: there is no script in the new version of the package - giving up UpgradeStatus: Upgraded to zesty on 2017-04-15 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-361/+bug/1683081/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1683122] Re: mouse input permanently locks to a single window
That version is now dead http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml ** Changed in: gnome-shell (Ubuntu) Status: New => Invalid -- 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/1683122 Title: mouse input permanently locks to a single window Status in gnome-shell package in Ubuntu: Invalid Bug description: Once every few days or so, mouse/touchpad input in Gnome suddenly breaks. The mouse cursor still moves around the screen as usual, but all click events go to a random single window. Events such as clicks on parts of the screen outside that window, or even on other workspaces, are interpreted as events in that one window. Only the window content receives events; decorations (and in the case of gnome- terminal, even menus and scroll bars) do not. Keyboard input in other windows continues to work fine, as does Alt+Tab and Ctrl+Alt+arrows. Bizarrely, touchscreen input works just fine. And if the touchscreen is used to change to a different window, that window (or a nearby window) may then become the single window selected for mouse input. If the affected window is closed, another window is selected to receive input in the same way. The only way to clear the problem is to log out of Gnome. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: gnome-shell 3.24.0-0ubuntu2 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Apr 16 17:31:57 2017 DisplayManager: gdm3 InstallationDate: Installed on 2016-12-02 (134 days ago) InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 (20161012.1) 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/1683122/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1683148] Re: Sound delay with ASUS GL552VW in 17.04
That version is now dead http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml ** Changed in: alsa-driver (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1683148 Title: Sound delay with ASUS GL552VW in 17.04 Status in alsa-driver package in Ubuntu: Invalid Bug description: When I had 16.10 everything was fine but when I've installed 17.04 (update was failed because X server crashed because of nvidia drivers) there is few seconds delay after sound is played, the sound and video is in sync but it look like sound is muted when it starts it work when playing next sound or when pausing the sound (for instance in audacious) but I've got delay when I stop and play again. I've try this in /etc/modprobe.d/alsa-base.conf file as mention in this thread https://ubuntuforums.org/showthread.php?t=1308604 options snd-hda-intel model=laptop enable=1 index=0 options snd-hda-intel power save=0 but got error in dmesg that those options are not supported: [ 15.253198] snd_hda_intel: unknown parameter 'power' ignored [ 15.253199] snd_hda_intel: unknown parameter 'save' ignored the first sound test was without delay but the second one was. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic i686 ApportVersion: 2.20.4-0ubuntu4 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kuba 15418 F pulseaudio CurrentDesktop: XFCE Date: Sun Apr 16 16:27:58 2017 InstallationDate: Installed on 2017-04-15 (1 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release i386 (20170412) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Wbudowany dźwięk - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: None of the above Title: [GL552VW, Conexant CX20751/2, Speaker, Internal] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/06/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GL552VW.300 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GL552VW dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGL552VW.300:bd09/06/2016:svnASUSTeKCOMPUTERINC.:pnGL552VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL552VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: GL552VW dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. modified.conffile..etc.modprobe.d.alsa-base.conf: [modified] mtime.conffile..etc.modprobe.d.alsa-base.conf: 2017-04-16T15:59:40.113763 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1683148/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1683293] Re: fails to show processes tab after upgrade to 17.04
That version is now dead http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml ** Changed in: gnome-system-monitor (Ubuntu) Status: New => Invalid -- 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/1683293 Title: fails to show processes tab after upgrade to 17.04 Status in gnome-system-monitor package in Ubuntu: Invalid Bug description: When monitor starts, it shows Resources tab by default. Clicking on Processes tab does nothing, only this error message is produced. (gnome-system-monitor:11370): dconf-WARNING **: failed to commit changes to dconf: Could not connect: Connection refused ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: gnome-system-monitor 3.24.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 CurrentDesktop: XFCE Date: Mon Apr 17 12:49:18 2017 SourcePackage: gnome-system-monitor UpgradeStatus: Upgraded to zesty on 2017-04-15 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1683293/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1683326] Re: package libmetis5:amd64 5.1.0.dfsg-5 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configurati
That version is now dead http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml ** Changed in: metis (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metis in Ubuntu. https://bugs.launchpad.net/bugs/1683326 Title: package libmetis5:amd64 5.1.0.dfsg-5 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in metis package in Ubuntu: Invalid Bug description: Error after sudo apt-get -f install ProblemType: Package DistroRelease: Ubuntu 17.04 Package: libmetis5:amd64 5.1.0.dfsg-5 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 AptOrdering: NULL: ConfigurePending Architecture: amd64 Date: Mon Apr 17 16:59:53 2017 Dependencies: gcc-6-base 6.3.0-12ubuntu2 libc6 2.24-9ubuntu2 libgcc1 1:6.3.0-12ubuntu2 DpkgTerminalLog: dpkg: error processing package libmetis5:amd64 (--configure): package is in a very bad inconsistent state; you should reinstall it before attempting configuration ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2017-04-11 (5 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170407) RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: metis Title: package libmetis5:amd64 5.1.0.dfsg-5 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metis/+bug/1683326/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1748761] Re: "Open a New Private Window" Firefox Desktop Action is not translated into Czech language
The attachment "firefox.desktop.in.patch" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** Tags added: patch -- 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/1748761 Title: "Open a New Private Window" Firefox Desktop Action is not translated into Czech language Status in firefox package in Ubuntu: New Bug description: The "Open a New Private Window" Firefox Desktop Action is not translated into Czech language. The attached patch fixes this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1748761/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1683887] Re: Tap-to-click and two finger scrolling not working after upgrading to zesty
That version is now dead http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml ** Changed in: xserver-xorg-input-synaptics (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/1683887 Title: Tap-to-click and two finger scrolling not working after upgrading to zesty Status in xserver-xorg-input-synaptics package in Ubuntu: Invalid Bug description: It seems that syndaemon is not working properly and never reactivates the tap-to-click functionality. The problem occurs only when I use the enter key to validate my password on the login screen. If I validate with the mouse, the touchpad is working correctly. (It took me hours of investigation to figure out why it was always working with guest account: because I do not use the keyboard to log in) When broken, I make it work again with synclient TouchpadOff=0. In that case tap-to-click is not disabled when I use the keyboard. Syndaemon is running but seems to be stuck. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: xserver-xorg-input-synaptics 1.9.0-1ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity:Unity7 Date: Tue Apr 18 19:37:07 2017 DistUpgraded: 2017-04-15 12:31:17,011 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: L'exécution du processus fils « ./xorg_fix_proprietary.py » a échoué (No such file or directory) (8)) DistroCodename: zesty DistroVariant: ubuntu MachineType: Dell Inc. Latitude E5440 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic root=UUID=a1748360-88e9-482a-a704-a8608e20b6f3 ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-input-synaptics UpgradeStatus: Upgraded to zesty on 2017-04-15 (3 days ago) dmi.bios.date: 05/01/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 08RCYC dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA06:bd05/01/2014:svnDellInc.:pnLatitudeE5440:pvr01:rvnDellInc.:rn08RCYC:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5440 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.3-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.3-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.14-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1683887/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1684276] Re: interface clone MAC is the string "permanent", which isn't accepted
That version is now dead http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml ** Changed in: network-manager-applet (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1684276 Title: interface clone MAC is the string "permanent", which isn't accepted Status in network-manager-applet package in Ubuntu: Invalid Bug description: After upgrading to zesty, my network configs failed because the "Clone MAC" is listed as the string "permanent", which you only notice because the "Save" button is greyed out and you have to check syslog for a message like this: Apr 19 13:56:58 quelbo nm-connection-e[7252]: Cannot save connection due to error: Invalid setting Wi-Fi: invalid MAC address for cloned MAC (permanent) ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: network-manager-gnome 1.4.2-1ubuntu4 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity:Unity7 Date: Wed Apr 19 14:07:48 2017 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2014-05-29 (1055 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager-applet UpgradeStatus: Upgraded to zesty on 2017-04-19 (0 days ago) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.4.4connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1684276/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1684293] Re: Reading text file corrupted
That version is now dead http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml ** Changed in: gedit (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1684293 Title: Reading text file corrupted Status in gedit package in Ubuntu: Invalid Bug description: Not sure, but it looks like text data is being displayed multiple times in the text window in an overlapping way, such that the contents of the text file cannot be seen. However, if one does "select" on any area of the file, the contents, under the selected area, does show up... ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: gedit 3.22.0-2ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity:Unity7 Date: Wed Apr 19 17:07:11 2017 ExecutablePath: /usr/bin/gedit InstallationDate: Installed on 2014-02-09 (1165 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) ProcEnviron: LANGUAGE=en_US PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gedit UpgradeStatus: Upgraded to zesty on 2017-04-15 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1684293/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1684324] Re: [Vostro 200, Realtek ALC888, Green Line Out, Rear] No sound at all
That version is now dead http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml ** Changed in: pulseaudio (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1684324 Title: [Vostro 200, Realtek ALC888, Green Line Out, Rear] No sound at all Status in pulseaudio package in Ubuntu: Invalid Bug description: Upgraded to 17.04 from 16.10 today. Sound worked ok in previous versions. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: pulseaudio 1:10.0-1ubuntu2 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tim1857 F pulseaudio CurrentDesktop: Unity:Unity7 Date: Wed Apr 19 19:36:52 2017 InstallationDate: Installed on 2015-03-28 (753 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel successful Symptom_Card: Built-in Audio - HDA Intel Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tim1857 F pulseaudio Symptom_Jack: Green Line Out, Rear Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: No sound at all Title: [Vostro 200, Realtek ALC888, Green Line Out, Rear] No sound at all UpgradeStatus: Upgraded to zesty on 2017-04-19 (0 days ago) dmi.bios.vendor: Dell Inc. dmi.board.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1684324/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1684463] Re: [X555UB, Realtek ALC256, Black Headphone Out, Right] No sound at all
That version is now dead http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml ** Changed in: alsa-driver (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1684463 Title: [X555UB, Realtek ALC256, Black Headphone Out, Right] No sound at all Status in alsa-driver package in Ubuntu: Invalid Bug description: There is no sound on my pc. I had sound yesterday! ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D3p: work 2046 F...m pulseaudio /dev/snd/pcmC0D0c: work 2046 F...m pulseaudio /dev/snd/controlC0: work 2046 F pulseaudio CurrentDesktop: Unity:Unity7 Date: Thu Apr 20 10:12:51 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2016-11-07 (164 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D3p: work 2046 F...m pulseaudio /dev/snd/pcmC0D0c: work 2046 F...m pulseaudio /dev/snd/controlC0: work 2046 F pulseaudio Symptom_Jack: Black Headphone Out, Right Symptom_Type: No sound at all Title: [X555UB, Realtek ALC256, Black Headphone Out, Right] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/06/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X555UB.300 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X555UB dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX555UB.300:bd07/06/2016:svnASUSTeKCOMPUTERINC.:pnX555UB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555UB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X555UB dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1684463/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 990377] Re: lock icon in User Accounts is at best confusing
** Changed in: gnome-control-center Status: Incomplete => Confirmed -- 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/990377 Title: lock icon in User Accounts is at best confusing Status in gnome-control-center: Confirmed Status in gnome-control-center package in Ubuntu: Triaged Bug description: This is a UI issue. Description: Ubuntu 12.04 LTS Release: 12.04 The lock/unlock button in User Accounts goes against the normal use of a lock to indicate the locked state, instead meaning the action of locking. This makes the icon confusing. A better approach would be to use the commonly used convention, and not have the lock in the button. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/990377/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1748762] [NEW] GNOME Characters translation is missing
Public bug reported: GNOME Characters is untranslated on non-English Ubuntu 18.04. It looks like the translations are missing or not applied for some reason. ** Affects: ubuntu-translations Importance: Undecided Status: New ** Affects: gnome-characters (Ubuntu) Importance: Undecided Status: New ** Tags: bionic l10n ** Also affects: ubuntu-translations Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-characters in Ubuntu. https://bugs.launchpad.net/bugs/1748762 Title: GNOME Characters translation is missing Status in Ubuntu Translations: New Status in gnome-characters package in Ubuntu: New Bug description: GNOME Characters is untranslated on non-English Ubuntu 18.04. It looks like the translations are missing or not applied for some reason. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/1748762/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1748761] [NEW] "Open a New Private Window" Firefox Desktop Action is not translated into Czech language
Public bug reported: The "Open a New Private Window" Firefox Desktop Action is not translated into Czech language. The attached patch fixes this. ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: l10n ** Patch added: "firefox.desktop.in.patch" https://bugs.launchpad.net/bugs/1748761/+attachment/5053125/+files/firefox.desktop.in.patch -- 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/1748761 Title: "Open a New Private Window" Firefox Desktop Action is not translated into Czech language Status in firefox package in Ubuntu: New Bug description: The "Open a New Private Window" Firefox Desktop Action is not translated into Czech language. The attached patch fixes this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1748761/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1748752] Re: package gnome-menus 3.13.3-11ubuntu1 failed to install/upgrade: triggers looping, abandoned
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-menus (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-menus in Ubuntu. https://bugs.launchpad.net/bugs/1748752 Title: package gnome-menus 3.13.3-11ubuntu1 failed to install/upgrade: triggers looping, abandoned Status in gnome-menus package in Ubuntu: Confirmed Bug description: This seems to be similar to bugs: #1738194 #1746776 etc ProblemType: Package DistroRelease: Ubuntu 18.04 Package: gnome-menus 3.13.3-11ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.8-0ubuntu8 Architecture: amd64 Date: Sun Feb 11 21:06:53 2018 Dependencies: ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2017-07-24 (201 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170723) Python3Details: /usr/bin/python3.6, Python 3.6.4, python3-minimal, 3.6.4-1 PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu1 apt 1.6~alpha7ubuntu1 SourcePackage: gnome-menus Title: package gnome-menus 3.13.3-11ubuntu1 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-menus/+bug/1748752/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1748541] Re: gnome-shell crashed with signal 5
*** This bug is a duplicate of bug 1748450 *** https://bugs.launchpad.net/bugs/1748450 I suppose bug #1748450 is private, as I can't access it. -- 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/1748541 Title: gnome-shell crashed with signal 5 Status in gnome-shell package in Ubuntu: New Bug description: I got this message when I logged in (Ubuntu 17.10 with gnome shell, wayland) ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.26.2-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.8-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME-Greeter:GNOME Date: Tue Feb 6 19:16:22 2018 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2017-07-19 (205 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170718) ProcCmdline: /usr/bin/gnome-shell Signal: 5 SourcePackage: gnome-shell StacktraceTop: () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 _XIOError () at /usr/lib/x86_64-linux-gnu/libX11.so.6 _XEventsQueued () at /usr/lib/x86_64-linux-gnu/libX11.so.6 XPending () at /usr/lib/x86_64-linux-gnu/libX11.so.6 () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 Title: gnome-shell crashed with signal 5 UpgradeStatus: Upgraded to bionic on 2018-02-05 (4 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1748541/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1748752] [NEW] package gnome-menus 3.13.3-11ubuntu1 failed to install/upgrade: triggers looping, abandoned
Public bug reported: This seems to be similar to bugs: #1738194 #1746776 etc ProblemType: Package DistroRelease: Ubuntu 18.04 Package: gnome-menus 3.13.3-11ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.8-0ubuntu8 Architecture: amd64 Date: Sun Feb 11 21:06:53 2018 Dependencies: ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2017-07-24 (201 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170723) Python3Details: /usr/bin/python3.6, Python 3.6.4, python3-minimal, 3.6.4-1 PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu1 apt 1.6~alpha7ubuntu1 SourcePackage: gnome-menus Title: package gnome-menus 3.13.3-11ubuntu1 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-menus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-menus in Ubuntu. https://bugs.launchpad.net/bugs/1748752 Title: package gnome-menus 3.13.3-11ubuntu1 failed to install/upgrade: triggers looping, abandoned Status in gnome-menus package in Ubuntu: New Bug description: This seems to be similar to bugs: #1738194 #1746776 etc ProblemType: Package DistroRelease: Ubuntu 18.04 Package: gnome-menus 3.13.3-11ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.8-0ubuntu8 Architecture: amd64 Date: Sun Feb 11 21:06:53 2018 Dependencies: ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2017-07-24 (201 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170723) Python3Details: /usr/bin/python3.6, Python 3.6.4, python3-minimal, 3.6.4-1 PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu1 apt 1.6~alpha7ubuntu1 SourcePackage: gnome-menus Title: package gnome-menus 3.13.3-11ubuntu1 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-menus/+bug/1748752/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1748723] [NEW] HP Laserjet1018 detected by 17.10 but not print anything
You have been subscribed to a public bug: Cuos and HPLIB are installed but HP-Check show errors The Printer HP Laserjet1018 has been detected by Ubuntu 17.01 an is defined as standard printer I can start a print request, it goes in the print queue and finished without printing. On Ubuntu 16.04 everything works fine after install HPLIP See same in attachment THANKS cyborg2058@cyborg2058-Z370-HD3P:~$ hp-check Saving output in log file: /home/cyborg2058/hp-check.log HP Linux Imaging and Printing System (ver. 3.17.7) Dependency/Version Check Utility ver. 15.1 Copyright (c) 2001-15 HP Development Company, LP This software comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to distribute it under certain conditions. See COPYING file for more details. Note: hp-check can be run in three modes: 1. Compile-time check mode (-c or --compile): Use this mode before compiling the HPLIP supplied tarball (.tar.gz or .run) to determine if the proper dependencies are installed to successfully compile HPLIP. 2. Run-time check mode (-r or --run): Use this mode to determine if a distro supplied package (.deb, .rpm, etc) or an already built HPLIP supplied tarball has the proper dependencies installed to successfully run. 3. Both compile- and run-time check mode (-b or --both) (Default): This mode will check both of the above cases (both compile- and run-time dependencies). Check types: a. EXTERNALDEP - External Dependencies b. GENERALDEP - General Dependencies (required both at compile and run time) c. COMPILEDEP - Compile time Dependencies d. [All are run-time checks] PYEXT SCANCONF QUEUES PERMISSION Status Types: OK MISSING - Missing Dependency or Permission or Plug-in INCOMPAT - Incompatible dependency-version or Plugin-version warning: 12-17.10 version is not supported. Using 12-17.04 versions dependencies to verify and install... --- | SYSTEM INFO | --- Kernel: 4.13.0-32-generic #35-Ubuntu SMP Thu Jan 25 09:13:46 UTC 2018 GNU/Linux Host: cyborg2058-Z370-HD3P Proc: 4.13.0-32-generic #35-Ubuntu SMP Thu Jan 25 09:13:46 UTC 2018 GNU/Linux Distribution: 12 17.10 Bitness: 64 bit --- | HPLIP CONFIGURATION | --- HPLIP-Version: HPLIP 3.17.7 HPLIP-Home: /usr/share/hplip warning: HPLIP-Installation: Auto installation is not supported for 12 distro 17.10 version Current contents of '/etc/hp/hplip.conf' file: # hplip.conf. Generated from hplip.conf.in by configure. [hplip] version=3.17.7 [dirs] home=/usr/share/hplip run=/var/run ppd=/usr/share/ppd/hplip/HP ppdbase=/usr/share/ppd/hplip doc=/usr/share/doc/hplip html=/usr/share/doc/hplip-doc icon=no cupsbackend=/usr/lib/cups/backend cupsfilter=/usr/lib/cups/filter drv=/usr/share/cups/drv bin=/usr/bin apparmor=/etc/apparmor.d # Following values are determined at configure time and cannot be changed. [configure] network-build=yes libusb01-build=no pp-build=yes gui-build=yes scanner-build=yes fax-build=yes dbus-build=yes cups11-build=no doc-build=yes shadow-build=no hpijs-install=yes foomatic-drv-install=yes foomatic-ppd-install=yes foomatic-rip-hplip-install=no hpcups-install=yes cups-drv-install=yes cups-ppd-install=no internal-tag=3.17.7 restricted-build=no ui-toolkit=qt5 qt3=no qt4=no qt5=yes policy-kit=yes lite-build=no udev_sysfs_rules=no hpcups-only-build=no hpijs-only-build=no apparmor_build=no Current contents of '/var/lib/hp/hplip.state' file: Plugins are not installed. Could not access file: No such file or directory Current contents of '~/.hplip/hplip.conf' file: [installation] date_time = 02/11/18 10:25:05 version = 3.17.7 - | External Dependencies | - error: cups CUPS - Common Unix Printing System REQUIRED1.1 - INCOMPAT 'CUPS may not be installed or not running' gs GhostScript - PostScript and PDF language interpreter and previewer REQUIRED7.059.21OK - error: xsane xsane - Graphical scanner frontend for SANE OPTIONAL0.9 - MISSING'xsane needs to be installed' scanimagescanimage - Shell scanning program OPTIONAL1.0 1.0.27 OK - error: dbus DBus - Message bus system REQUIRED- 1.10.22 MISSING'DBUS may not be installed or not running' policykitPolicyKit - Administrative policy framework
[Desktop-packages] [Bug 1748723] Re: HP Laserjet1018 detected by 17.10 but not print anything
** Package changed: ubuntu => cups (Ubuntu) -- 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/1748723 Title: HP Laserjet1018 detected by 17.10 but not print anything Status in cups package in Ubuntu: New Bug description: Cuos and HPLIB are installed but HP-Check show errors The Printer HP Laserjet1018 has been detected by Ubuntu 17.01 an is defined as standard printer I can start a print request, it goes in the print queue and finished without printing. On Ubuntu 16.04 everything works fine after install HPLIP See same in attachment THANKS cyborg2058@cyborg2058-Z370-HD3P:~$ hp-check Saving output in log file: /home/cyborg2058/hp-check.log HP Linux Imaging and Printing System (ver. 3.17.7) Dependency/Version Check Utility ver. 15.1 Copyright (c) 2001-15 HP Development Company, LP This software comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to distribute it under certain conditions. See COPYING file for more details. Note: hp-check can be run in three modes: 1. Compile-time check mode (-c or --compile): Use this mode before compiling the HPLIP supplied tarball (.tar.gz or .run) to determine if the proper dependencies are installed to successfully compile HPLIP. 2. Run-time check mode (-r or --run): Use this mode to determine if a distro supplied package (.deb, .rpm, etc) or an already built HPLIP supplied tarball has the proper dependencies installed to successfully run. 3. Both compile- and run-time check mode (-b or --both) (Default): This mode will check both of the above cases (both compile- and run-time dependencies). Check types: a. EXTERNALDEP - External Dependencies b. GENERALDEP - General Dependencies (required both at compile and run time) c. COMPILEDEP - Compile time Dependencies d. [All are run-time checks] PYEXT SCANCONF QUEUES PERMISSION Status Types: OK MISSING - Missing Dependency or Permission or Plug-in INCOMPAT - Incompatible dependency-version or Plugin-version warning: 12-17.10 version is not supported. Using 12-17.04 versions dependencies to verify and install... --- | SYSTEM INFO | --- Kernel: 4.13.0-32-generic #35-Ubuntu SMP Thu Jan 25 09:13:46 UTC 2018 GNU/Linux Host: cyborg2058-Z370-HD3P Proc: 4.13.0-32-generic #35-Ubuntu SMP Thu Jan 25 09:13:46 UTC 2018 GNU/Linux Distribution: 12 17.10 Bitness: 64 bit --- | HPLIP CONFIGURATION | --- HPLIP-Version: HPLIP 3.17.7 HPLIP-Home: /usr/share/hplip warning: HPLIP-Installation: Auto installation is not supported for 12 distro 17.10 version Current contents of '/etc/hp/hplip.conf' file: # hplip.conf. Generated from hplip.conf.in by configure. [hplip] version=3.17.7 [dirs] home=/usr/share/hplip run=/var/run ppd=/usr/share/ppd/hplip/HP ppdbase=/usr/share/ppd/hplip doc=/usr/share/doc/hplip html=/usr/share/doc/hplip-doc icon=no cupsbackend=/usr/lib/cups/backend cupsfilter=/usr/lib/cups/filter drv=/usr/share/cups/drv bin=/usr/bin apparmor=/etc/apparmor.d # Following values are determined at configure time and cannot be changed. [configure] network-build=yes libusb01-build=no pp-build=yes gui-build=yes scanner-build=yes fax-build=yes dbus-build=yes cups11-build=no doc-build=yes shadow-build=no hpijs-install=yes foomatic-drv-install=yes foomatic-ppd-install=yes foomatic-rip-hplip-install=no hpcups-install=yes cups-drv-install=yes cups-ppd-install=no internal-tag=3.17.7 restricted-build=no ui-toolkit=qt5 qt3=no qt4=no qt5=yes policy-kit=yes lite-build=no udev_sysfs_rules=no hpcups-only-build=no hpijs-only-build=no apparmor_build=no Current contents of '/var/lib/hp/hplip.state' file: Plugins are not installed. Could not access file: No such file or directory Current contents of '~/.hplip/hplip.conf' file: [installation] date_time = 02/11/18 10:25:05 version = 3.17.7 - | External Dependencies | - error: cups CUPS - Common Unix Printing System REQUIRED1.1 - INCOMPAT 'CUPS may not be installed or not running' gs GhostScript - PostScript and PDF language interpreter and previewer REQUIRED7.059.21OK - error: xsane xsane - Graphical s
[Desktop-packages] [Bug 883138] Re: Dim file extensions
** Changed in: gtk Status: Incomplete => Confirmed -- 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/883138 Title: Dim file extensions Status in GTK+: Confirmed Status in Nautilus: Confirmed Status in Wine: New Status in enlightenment package in Ubuntu: New Status in gtk+3.0 package in Ubuntu: Triaged Status in lesstif2 package in Ubuntu: New Status in mono package in Ubuntu: New Status in nautilus package in Ubuntu: Triaged Status in qt4-x11 package in Ubuntu: Opinion Status in tcltk-defaults package in Ubuntu: New Status in wine package in Ubuntu: Incomplete Bug description: Many web browsers have now began dimming less relevant parts of the URL, such as the protocol, subdomain, path, and query string. I propose we have an option/setting/feature that does the same Nautilus and Gtk file dialogs. Dim the the file extension. To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/883138/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1748748] Re: Evolutiion fails to start. Cannot connect /tmp/dbus-*
Another follow-up: I get the same error from ubuntu-bug. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1748748 Title: Evolutiion fails to start. Cannot connect /tmp/dbus-* Status in evolution package in Ubuntu: New Bug description: I have a new installation of xubuntu 16.04 fully updated within the past hour, running on a Lenovo T550. I have been using Evolution for a couple oof dys, but after this morning's update it is failing to start. Error message is $ evolution ** (evolution:3169): WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-4Me0oN1k69: Connection refused Nothing in syslog. $ lsb_release -rd Description: Ubuntu 16.04.3 LTS Release: 16.04 $ apt-cache policy evolution evolution: Installed: 3.18.5.2-0ubuntu3.2 Candidate: 3.18.5.2-0ubuntu3.2 Version table: *** 3.18.5.2-0ubuntu3.2 500 500 http://gb.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 Packages 100 /var/lib/dpkg/status 3.18.5.2-0ubuntu1 500 500 http://gb.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: evolution 3.18.5.2-0ubuntu3.2 ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98 Uname: Linux 4.4.0-112-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Sun Feb 11 12:19:26 2018 InstallationDate: Installed on 2018-02-09 (2 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: evolution UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1748748/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1748748] [NEW] Evolutiion fails to start. Cannot connect /tmp/dbus-*
Public bug reported: I have a new installation of xubuntu 16.04 fully updated within the past hour, running on a Lenovo T550. I have been using Evolution for a couple oof dys, but after this morning's update it is failing to start. Error message is $ evolution ** (evolution:3169): WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-4Me0oN1k69: Connection refused Nothing in syslog. $ lsb_release -rd Description:Ubuntu 16.04.3 LTS Release:16.04 $ apt-cache policy evolution evolution: Installed: 3.18.5.2-0ubuntu3.2 Candidate: 3.18.5.2-0ubuntu3.2 Version table: *** 3.18.5.2-0ubuntu3.2 500 500 http://gb.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 Packages 100 /var/lib/dpkg/status 3.18.5.2-0ubuntu1 500 500 http://gb.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: evolution 3.18.5.2-0ubuntu3.2 ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98 Uname: Linux 4.4.0-112-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Sun Feb 11 12:19:26 2018 InstallationDate: Installed on 2018-02-09 (2 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: evolution UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: evolution (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1748748 Title: Evolutiion fails to start. Cannot connect /tmp/dbus-* Status in evolution package in Ubuntu: New Bug description: I have a new installation of xubuntu 16.04 fully updated within the past hour, running on a Lenovo T550. I have been using Evolution for a couple oof dys, but after this morning's update it is failing to start. Error message is $ evolution ** (evolution:3169): WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-4Me0oN1k69: Connection refused Nothing in syslog. $ lsb_release -rd Description: Ubuntu 16.04.3 LTS Release: 16.04 $ apt-cache policy evolution evolution: Installed: 3.18.5.2-0ubuntu3.2 Candidate: 3.18.5.2-0ubuntu3.2 Version table: *** 3.18.5.2-0ubuntu3.2 500 500 http://gb.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 Packages 100 /var/lib/dpkg/status 3.18.5.2-0ubuntu1 500 500 http://gb.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: evolution 3.18.5.2-0ubuntu3.2 ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98 Uname: Linux 4.4.0-112-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Sun Feb 11 12:19:26 2018 InstallationDate: Installed on 2018-02-09 (2 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: evolution UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1748748/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
