[Touch-packages] [Bug 1720570] Re: Open button in headerbar is not themed when no file is selected
Also the button is not themed properly when the dialogue goes to the background (lose focus) and a file is selected. It becomes green (the same when focused) and changes into black when the mouse pointer hovers over it. I think it should behave like the Cancel button; goes pale. See the attached screencast in comment #2, at the end of the video. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1720570 Title: Open button in headerbar is not themed when no file is selected Status in ubuntu-themes package in Ubuntu: Triaged Bug description: Steps: 1. Open LibreOffice Writer 2. Choose Open a file 3. Make sure that there are no files selected 4. The Open button in the headerbar in not themed See attached screenshot. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: light-themes 16.10+17.10.20170929-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-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Sep 30 21:06:07 2017 InstallationDate: Installed on 2017-09-21 (9 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170919) PackageArchitecture: all SourcePackage: ubuntu-themes UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1720570/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1582950] Re: broken apport hook: TypeError: a bytes-like object is required, not 'str'
This bug was fixed in the package apport - 2.20.7-0ubuntu2
---
apport (2.20.7-0ubuntu2) artful; urgency=medium
* data/package-hooks/source_ubiquity.py: Convert the content of syslog from
bytes to string so comparison and regex matches in the hook work.
(LP: #1582950)
-- Brian Murray Wed, 27 Sep 2017 14:44:40 -0700
** Changed in: apport (Ubuntu Artful)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1582950
Title:
broken apport hook: TypeError: a bytes-like object is required, not
'str'
Status in apport package in Ubuntu:
Fix Released
Status in ubiquity package in Ubuntu:
Invalid
Status in apport source package in Artful:
Fix Released
Bug description:
The apport hook for ubiquity appears broken. (Ignore the Wnck error,
that's bug 1580412).
$ ubuntu-bug ubiquity
/usr/share/apport/apport-gtk:16: PyGIWarning: Wnck was imported without
specifying a version first. Use gi.require_version('Wnck', '3.0') before import
to ensure that the right version gets loaded.
from gi.repository import GLib, Wnck, GdkX11, Gdk
dpkg-query: no packages found matching ubiquity
ERROR: hook /usr/share/apport/package-hooks/source_ubiquity.py crashed:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apport/report.py", line 197, in
_run_hook
symb['add_info'](report, ui)
File "/usr/share/apport/package-hooks/source_ubiquity.py", line 61, in
add_info
if 'Buffer I/O error on device' in syslog:
TypeError: a bytes-like object is required, not 'str'
Thanks
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ubiquity (not installed)
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
CurrentDesktop: Unity
Date: Tue May 17 17:31:33 2016
InstallationDate: Installed on 2012-10-18 (1307 days ago)
InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64
(20120823.1)
SourcePackage: ubiquity
UpgradeStatus: Upgraded to xenial on 2016-04-30 (17 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1582950/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1720541] Re: flock does not lock dpkg lock file properly
** Description changed: - Test: sudo flock /var/lib/dpkg/lock -c \ 'echo 1; apt-get -o Debug::NoLocking=true check; echo 2; apt-get check' Expected behavior: apt-get fails in stage 2. - Workaround (needs moreutils package) + Workaround (needs moreutils package, which is not installed by default): sudo lckdo /var/lib/dpkg/lock /bin/sh -c \ 'echo 1; apt-get -o Debug::NoLocking=true check; echo 2; apt-get check' Similarly, flock does not recognize lock set by e.g. apt-get. + + man lckdo: + "Now that util-linux contains a similar command named flock, lckdo is deprecated, and will be removed from some future version of moreutils." + + So developer can not rely on lckdo. + ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: util-linux 2.20.1-5.1ubuntu20.9 ProcVersionSignature: Ubuntu 4.4.0-96.119~14.04.1-generic 4.4.83 Uname: Linux 4.4.0-96-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.25 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Sep 30 16:30:50 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2014-09-21 (1105 days ago) InstallationMedia: Ubuntu-Studio 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.1) SourcePackage: util-linux UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.cron.weekly.fstrim: 2014-09-21T13:07:51.420447 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1720541 Title: flock does not lock dpkg lock file properly Status in util-linux package in Ubuntu: New Bug description: Test: sudo flock /var/lib/dpkg/lock -c \ 'echo 1; apt-get -o Debug::NoLocking=true check; echo 2; apt-get check' Expected behavior: apt-get fails in stage 2. Workaround (needs moreutils package, which is not installed by default): sudo lckdo /var/lib/dpkg/lock /bin/sh -c \ 'echo 1; apt-get -o Debug::NoLocking=true check; echo 2; apt-get check' Similarly, flock does not recognize lock set by e.g. apt-get. man lckdo: "Now that util-linux contains a similar command named flock, lckdo is deprecated, and will be removed from some future version of moreutils." So developer can not rely on lckdo. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: util-linux 2.20.1-5.1ubuntu20.9 ProcVersionSignature: Ubuntu 4.4.0-96.119~14.04.1-generic 4.4.83 Uname: Linux 4.4.0-96-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.25 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Sep 30 16:30:50 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2014-09-21 (1105 days ago) InstallationMedia: Ubuntu-Studio 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.1) SourcePackage: util-linux UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.cron.weekly.fstrim: 2014-09-21T13:07:51.420447 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1720541/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1582950] Re: broken apport hook: TypeError: a bytes-like object is required, not 'str'
Hello Seth, or anyone else affected,
Accepted apport into artful-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/apport/2.20.7-0ubuntu2
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-artful to verification-done-artful. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-artful. In either case, details of your
testing will help us make a better decision.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance!
** Changed in: apport (Ubuntu Artful)
Status: In Progress => Fix Committed
** Tags added: verification-needed verification-needed-artful
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1582950
Title:
broken apport hook: TypeError: a bytes-like object is required, not
'str'
Status in apport package in Ubuntu:
Fix Committed
Status in ubiquity package in Ubuntu:
Invalid
Status in apport source package in Artful:
Fix Committed
Bug description:
The apport hook for ubiquity appears broken. (Ignore the Wnck error,
that's bug 1580412).
$ ubuntu-bug ubiquity
/usr/share/apport/apport-gtk:16: PyGIWarning: Wnck was imported without
specifying a version first. Use gi.require_version('Wnck', '3.0') before import
to ensure that the right version gets loaded.
from gi.repository import GLib, Wnck, GdkX11, Gdk
dpkg-query: no packages found matching ubiquity
ERROR: hook /usr/share/apport/package-hooks/source_ubiquity.py crashed:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apport/report.py", line 197, in
_run_hook
symb['add_info'](report, ui)
File "/usr/share/apport/package-hooks/source_ubiquity.py", line 61, in
add_info
if 'Buffer I/O error on device' in syslog:
TypeError: a bytes-like object is required, not 'str'
Thanks
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ubiquity (not installed)
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
CurrentDesktop: Unity
Date: Tue May 17 17:31:33 2016
InstallationDate: Installed on 2012-10-18 (1307 days ago)
InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64
(20120823.1)
SourcePackage: ubiquity
UpgradeStatus: Upgraded to xenial on 2016-04-30 (17 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1582950/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1720517] Re: Software and Updates /Other Software greys out when clicking on "Canonical Partners"
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions: * Is this reproducible? * If so, what specific steps should we take to recreate this bug? This will help us to find and resolve the problem. ** Changed in: software-properties (Ubuntu) Importance: Undecided => Low ** Changed in: software-properties (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1720517 Title: Software and Updates /Other Software greys out when clicking on "Canonical Partners" Status in software-properties package in Ubuntu: Incomplete Bug description: "Other Software" only works after having clicked on "Ubuntu Software", "Updates", etc and changing some settings on those pages. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: software-properties-gtk 0.96.24.16 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Sep 30 10:44:47 2017 EcryptfsInUse: Yes ExecutablePath: /usr/bin/software-properties-gtk InstallationDate: Installed on 2017-09-29 (0 days ago) InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 (20170919) InterpreterPath: /usr/bin/python3.6 PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash Python3Details: /usr/bin/python3.6, Python 3.6.3rc1, python3-minimal, 3.6.2-1ubuntu4 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1720517/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1720570] Re: Open button in headerbar is not themed when no file is selected
** Changed in: ubuntu-themes (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1720570 Title: Open button in headerbar is not themed when no file is selected Status in ubuntu-themes package in Ubuntu: Triaged Bug description: Steps: 1. Open LibreOffice Writer 2. Choose Open a file 3. Make sure that there are no files selected 4. The Open button in the headerbar in not themed See attached screenshot. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: light-themes 16.10+17.10.20170929-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-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Sep 30 21:06:07 2017 InstallationDate: Installed on 2017-09-21 (9 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170919) PackageArchitecture: all SourcePackage: ubuntu-themes UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1720570/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1720570] Re: Open button in headerbar is not themed when no file is selected
** Branch linked: lp:ubuntu-themes -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1720570 Title: Open button in headerbar is not themed when no file is selected Status in ubuntu-themes package in Ubuntu: Triaged Bug description: Steps: 1. Open LibreOffice Writer 2. Choose Open a file 3. Make sure that there are no files selected 4. The Open button in the headerbar in not themed See attached screenshot. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: light-themes 16.10+17.10.20170929-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-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Sep 30 21:06:07 2017 InstallationDate: Installed on 2017-09-21 (9 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170919) PackageArchitecture: all SourcePackage: ubuntu-themes UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1720570/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1720525] Re: Update package to newer version
Thanks for taking your time to report this issue and help making Ubuntu better. Indeed, Debian Sid contains a newer version of this package. However, I don't know whether that could be synced as-is or if there are any additional changes in the current Ubuntu package which would require a merge. ** Tags added: upgrade-software-version -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-evdev in Ubuntu. https://bugs.launchpad.net/bugs/1720525 Title: Update package to newer version Status in python-evdev package in Ubuntu: New Bug description: In Artful (and older releases) the version of the package is 0.4.7 even though 0.7.0 is already out. Debian Buster and Sid has 0.7.0 in the repos. The changes are bug fixes and features (see http://python-evdev.readthedocs.io/en/latest/changelog.html). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-evdev/+bug/1720525/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1720570] Re: Open button in headerbar is not themed when no file is selected
That's correct, when you are in an empty directory without any file selected, it's in the disabled state which looks weird. Need fixing (same with gedit/save with no name entered). ** Changed in: ubuntu-themes (Ubuntu) Assignee: (unassigned) => Didier Roche (didrocks) ** Changed in: ubuntu-themes (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1720570 Title: Open button in headerbar is not themed when no file is selected Status in ubuntu-themes package in Ubuntu: Triaged Bug description: Steps: 1. Open LibreOffice Writer 2. Choose Open a file 3. Make sure that there are no files selected 4. The Open button in the headerbar in not themed See attached screenshot. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: light-themes 16.10+17.10.20170929-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-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Sep 30 21:06:07 2017 InstallationDate: Installed on 2017-09-21 (9 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170919) PackageArchitecture: all SourcePackage: ubuntu-themes UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1720570/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1574278] Re: AbiWord text cursor starts to flicker after adding some text
** No longer affects: lubuntu-artwork (Ubuntu) ** No longer affects: gtk+3.0 (Ubuntu) ** No longer affects: gtk+3.0 (Ubuntu Xenial) ** No longer affects: lubuntu-artwork (Ubuntu Xenial) ** Also affects: abiword (Ubuntu Artful) Importance: High Status: Confirmed ** Also affects: abiword (Ubuntu Zesty) Importance: Undecided Status: New ** Changed in: abiword (Ubuntu Zesty) Importance: Undecided => High ** Changed in: abiword (Ubuntu Artful) Status: Confirmed => In Progress ** Changed in: abiword (Ubuntu Zesty) Status: New => Confirmed ** Changed in: abiword (Ubuntu Xenial) Status: In Progress => Confirmed ** Changed in: abiword (Ubuntu Artful) Assignee: (unassigned) => Simon Quigley (tsimonq2) ** Changed in: abiword (Ubuntu Zesty) Assignee: (unassigned) => Simon Quigley (tsimonq2) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1574278 Title: AbiWord text cursor starts to flicker after adding some text Status in AbiWord: In Progress Status in abiword package in Ubuntu: Fix Committed Status in abiword source package in Xenial: Confirmed Status in abiword source package in Zesty: Confirmed Status in abiword source package in Artful: Fix Committed Bug description: After adding some text in a new document, the entire document (including gray page background, text, text cursor) starts to flicker very fast. The UI above does not flicker. This happens too on a different system in VirtualBox. (Lubuntu 16.04 i386) Workaround for Ubuntu 16.04 LTS === 1. Open the Lubuntu menu. 2. Open Preferences>Customize Look and Feel 3. Change the theme to something other than Lubuntu-default or Lubuntu-dark-panel ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: abiword 3.0.1-6 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic i686 ApportVersion: 2.20.1-0ubuntu2 Architecture: i386 CurrentDesktop: LXDE Date: Sun Apr 24 16:12:14 2016 ExecutablePath: /usr/bin/abiword InstallationDate: Installed on 2016-04-22 (2 days ago) InstallationMedia: Lubuntu 15.10 "Wily Werewolf" - Release i386 (20151021) ProcEnviron: LANGUAGE=de_DE PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: abiword UpgradeStatus: Upgraded to xenial on 2016-04-22 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/abiword/+bug/1574278/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1720576] [NEW] package console-setup-linux 1.164 failed to install/upgrade: попытка перезаписать «/lib/systemd/system/console-setup.service», который уже имеется в пакете keyboar
Public bug reported: Problem appeared when i upgrade PC from debian repo. I don't know what i doing do. Please help. Thanks you. ProblemType: Package DistroRelease: Debian 9 Package: console-setup-linux 1.164 ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-35-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Sat Sep 30 22:28:34 2017 ErrorMessage: попытка перезаписать «/lib/systemd/system/console-setup.service», который уже имеется в пакете keyboard-configuration 1.108ubuntu15.3 InstallationDate: Installed on 2017-09-26 (4 days ago) InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.24 apt 1.2.24 SourcePackage: console-setup Title: package console-setup-linux 1.164 failed to install/upgrade: попытка перезаписать «/lib/systemd/system/console-setup.service», который уже имеется в пакете keyboard-configuration 1.108ubuntu15.3 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: console-setup (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package third-party-packages xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1720576 Title: package console-setup-linux 1.164 failed to install/upgrade: попытка перезаписать «/lib/systemd/system/console-setup.service», который уже имеется в пакете keyboard-configuration 1.108ubuntu15.3 Status in console-setup package in Ubuntu: New Bug description: Problem appeared when i upgrade PC from debian repo. I don't know what i doing do. Please help. Thanks you. ProblemType: Package DistroRelease: Debian 9 Package: console-setup-linux 1.164 ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-35-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Sat Sep 30 22:28:34 2017 ErrorMessage: попытка перезаписать «/lib/systemd/system/console-setup.service», который уже имеется в пакете keyboard-configuration 1.108ubuntu15.3 InstallationDate: Installed on 2017-09-26 (4 days ago) InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.24 apt 1.2.24 SourcePackage: console-setup Title: package console-setup-linux 1.164 failed to install/upgrade: попытка перезаписать «/lib/systemd/system/console-setup.service», который уже имеется в пакете keyboard-configuration 1.108ubuntu15.3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1720576/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1713313] Re: Unable to launch pkexec'ed applications on Wayland session
@Jeremy Bicha (jbicha) FYI on other similar bug report dino99 was pleasant about one big bug report (see his comment - https://bugs.launchpad.net/ubuntu/+source/nmap/+bug/1713311/comments/4 ). So we can choose this bug-report style here too. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1713313 Title: Unable to launch pkexec'ed applications on Wayland session Status in apport package in Ubuntu: New Status in apt-offline package in Ubuntu: New Status in backintime package in Ubuntu: Confirmed Status in budgie-welcome package in Ubuntu: Invalid Status in caja-admin package in Ubuntu: New Status in cinnamon package in Ubuntu: Invalid Status in ettercap package in Ubuntu: Confirmed Status in gdebi package in Ubuntu: Confirmed Status in gnunet-gtk package in Ubuntu: Confirmed Status in gparted package in Ubuntu: Invalid Status in gui-ufw package in Ubuntu: New Status in guidedog package in Ubuntu: New Status in hplip package in Ubuntu: Confirmed Status in italc package in Ubuntu: New Status in laptop-mode-tools package in Ubuntu: New Status in lightdm-gtk-greeter-settings package in Ubuntu: Confirmed Status in nautilus-admin package in Ubuntu: New Status in needrestart-session package in Ubuntu: Confirmed Status in nemo package in Ubuntu: Confirmed Status in policykit-1 package in Ubuntu: Invalid Status in scanmem package in Ubuntu: New Status in scap-workbench package in Ubuntu: Confirmed Status in sirikali package in Ubuntu: New Status in synaptic package in Ubuntu: Confirmed Status in thunar package in Ubuntu: New Status in tuned package in Ubuntu: New Status in ubuntustudio-controls package in Ubuntu: New Status in ubuntustudio-default-settings package in Ubuntu: Invalid Status in update-notifier package in Ubuntu: New Status in xdiagnose package in Ubuntu: Confirmed Status in xubuntu-default-settings package in Ubuntu: Invalid Status in zulucrypt package in Ubuntu: New Bug description: Posting here what gnome says about porting to wayland, and their tests: GNOME Applications under Wayland GTK+ has a Wayland backend. If it was enabled at compile-time, you can run a GTK+ application under Wayland simply by: GDK_BACKEND=wayland gnome-calculator Applications that use Clutter or clutter-gtk also need the Clutter Wayland backend enabled: GDK_BACKEND=wayland CLUTTER_BACKEND=wayland cheese https://wiki.gnome.org/Initiatives/Wayland/Applications ==> so hope the settings are well set at compile time; maybe a rebuilt to get sure all apps are ok. Steps to reproduce: 1. Install Ubuntu 17.10 2. Install backintime-qt4 or gparted application from above list (full may be acquired from https://codesearch.debian.net/search?q=pkexec+filetype%3Adesktop+path%3A*%2Fapplications%2F*&perpkg=1&page=4 ) 3a. Try to launch backintime-qt4 from shortcut "Back In Time (root)" (located in /usr/share/applications/backintime-qt4-root.desktop, it uses pkexec ($ cat /usr/share/applications/backintime-qt4-root.desktop | grep Exec Exec=pkexec backintime-qt4) 3b. Try to launch Gparted from shortcut "GParted" (located in /usr/share/applications/gparted.desktop, it uses gparted-pkexec) 4a.1. Back In Time does not start from GUI. 4a.2. Back In Time shows error message in console: 4b. gparted-pkexec does not start, reports error $ gparted-pkexec Created symlink /run/systemd/system/-.mount → /dev/null. Created symlink /run/systemd/system/run-user-1000.mount → /dev/null. Created symlink /run/systemd/system/run-user-121.mount → /dev/null. Created symlink /run/systemd/system/tmp.mount → /dev/null. No protocol specified (gpartedbin:12831): Gtk-WARNING **: cannot open display: :0 Removed /run/systemd/system/-.mount. Removed /run/systemd/system/run-user-1000.mount. Removed /run/systemd/system/run-user-121.mount. Removed /run/systemd/system/tmp.mount. $ pkexec backintime-qt4 Back In Time Version: 1.1.12 Back In Time comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to redistribute it under certain conditions; type `backintime --license' for details. No protocol specified app.py: cannot connect to X server :0 Expected results: * backintime-qt4 may be run as root Actual results: * unable to run backintime-qt4 as root Workaround: * setting "xhost +si:localuser:root" helps. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: backintime-qt4 1.1.12-2 ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5 Uname: Linux 4.12.0-11-generic i686 ApportVersion: 2.20.6-0ubuntu7 Architecture: i386 CurrentDesktop: GNOME Date: Sun Aug 27 14:23:14 2017 InstallationDa
[Touch-packages] [Bug 1713313] Re: Unable to launch pkexec'ed applications on Wayland session
This appears to be a false positive. ** Changed in: ubuntustudio-default-settings (Ubuntu) Status: New => Invalid ** Changed in: xubuntu-default-settings (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1713313 Title: Unable to launch pkexec'ed applications on Wayland session Status in apport package in Ubuntu: New Status in apt-offline package in Ubuntu: New Status in backintime package in Ubuntu: Confirmed Status in budgie-welcome package in Ubuntu: Invalid Status in caja-admin package in Ubuntu: New Status in cinnamon package in Ubuntu: Invalid Status in ettercap package in Ubuntu: Confirmed Status in gdebi package in Ubuntu: Confirmed Status in gnunet-gtk package in Ubuntu: Confirmed Status in gparted package in Ubuntu: Invalid Status in gui-ufw package in Ubuntu: New Status in guidedog package in Ubuntu: New Status in hplip package in Ubuntu: Confirmed Status in italc package in Ubuntu: New Status in laptop-mode-tools package in Ubuntu: New Status in lightdm-gtk-greeter-settings package in Ubuntu: Confirmed Status in nautilus-admin package in Ubuntu: New Status in needrestart-session package in Ubuntu: Confirmed Status in nemo package in Ubuntu: Confirmed Status in policykit-1 package in Ubuntu: Invalid Status in scanmem package in Ubuntu: New Status in scap-workbench package in Ubuntu: Confirmed Status in sirikali package in Ubuntu: New Status in synaptic package in Ubuntu: Confirmed Status in thunar package in Ubuntu: New Status in tuned package in Ubuntu: New Status in ubuntustudio-controls package in Ubuntu: New Status in ubuntustudio-default-settings package in Ubuntu: Invalid Status in update-notifier package in Ubuntu: New Status in xdiagnose package in Ubuntu: Confirmed Status in xubuntu-default-settings package in Ubuntu: Invalid Status in zulucrypt package in Ubuntu: New Bug description: Posting here what gnome says about porting to wayland, and their tests: GNOME Applications under Wayland GTK+ has a Wayland backend. If it was enabled at compile-time, you can run a GTK+ application under Wayland simply by: GDK_BACKEND=wayland gnome-calculator Applications that use Clutter or clutter-gtk also need the Clutter Wayland backend enabled: GDK_BACKEND=wayland CLUTTER_BACKEND=wayland cheese https://wiki.gnome.org/Initiatives/Wayland/Applications ==> so hope the settings are well set at compile time; maybe a rebuilt to get sure all apps are ok. Steps to reproduce: 1. Install Ubuntu 17.10 2. Install backintime-qt4 or gparted application from above list (full may be acquired from https://codesearch.debian.net/search?q=pkexec+filetype%3Adesktop+path%3A*%2Fapplications%2F*&perpkg=1&page=4 ) 3a. Try to launch backintime-qt4 from shortcut "Back In Time (root)" (located in /usr/share/applications/backintime-qt4-root.desktop, it uses pkexec ($ cat /usr/share/applications/backintime-qt4-root.desktop | grep Exec Exec=pkexec backintime-qt4) 3b. Try to launch Gparted from shortcut "GParted" (located in /usr/share/applications/gparted.desktop, it uses gparted-pkexec) 4a.1. Back In Time does not start from GUI. 4a.2. Back In Time shows error message in console: 4b. gparted-pkexec does not start, reports error $ gparted-pkexec Created symlink /run/systemd/system/-.mount → /dev/null. Created symlink /run/systemd/system/run-user-1000.mount → /dev/null. Created symlink /run/systemd/system/run-user-121.mount → /dev/null. Created symlink /run/systemd/system/tmp.mount → /dev/null. No protocol specified (gpartedbin:12831): Gtk-WARNING **: cannot open display: :0 Removed /run/systemd/system/-.mount. Removed /run/systemd/system/run-user-1000.mount. Removed /run/systemd/system/run-user-121.mount. Removed /run/systemd/system/tmp.mount. $ pkexec backintime-qt4 Back In Time Version: 1.1.12 Back In Time comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to redistribute it under certain conditions; type `backintime --license' for details. No protocol specified app.py: cannot connect to X server :0 Expected results: * backintime-qt4 may be run as root Actual results: * unable to run backintime-qt4 as root Workaround: * setting "xhost +si:localuser:root" helps. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: backintime-qt4 1.1.12-2 ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5 Uname: Linux 4.12.0-11-generic i686 ApportVersion: 2.20.6-0ubuntu7 Architecture: i386 CurrentDesktop: GNOME Date: Sun Aug 27 14:23:14 2017 InstallationDate: Installed on 2017-08-26 (0 days ago)
[Touch-packages] [Bug 1713313] Re: Unable to launch pkexec'ed applications on Wayland session
It doesn't make sense to run cinnamon inside GNOME on Wayland. ** Changed in: cinnamon (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1713313 Title: Unable to launch pkexec'ed applications on Wayland session Status in apport package in Ubuntu: New Status in apt-offline package in Ubuntu: New Status in backintime package in Ubuntu: Confirmed Status in budgie-welcome package in Ubuntu: Invalid Status in caja-admin package in Ubuntu: New Status in cinnamon package in Ubuntu: Invalid Status in ettercap package in Ubuntu: Confirmed Status in gdebi package in Ubuntu: Confirmed Status in gnunet-gtk package in Ubuntu: Confirmed Status in gparted package in Ubuntu: Invalid Status in gui-ufw package in Ubuntu: New Status in guidedog package in Ubuntu: New Status in hplip package in Ubuntu: Confirmed Status in italc package in Ubuntu: New Status in laptop-mode-tools package in Ubuntu: New Status in lightdm-gtk-greeter-settings package in Ubuntu: Confirmed Status in nautilus-admin package in Ubuntu: New Status in needrestart-session package in Ubuntu: Confirmed Status in nemo package in Ubuntu: Confirmed Status in policykit-1 package in Ubuntu: Invalid Status in scanmem package in Ubuntu: New Status in scap-workbench package in Ubuntu: Confirmed Status in sirikali package in Ubuntu: New Status in synaptic package in Ubuntu: Confirmed Status in thunar package in Ubuntu: New Status in tuned package in Ubuntu: New Status in ubuntustudio-controls package in Ubuntu: New Status in ubuntustudio-default-settings package in Ubuntu: Invalid Status in update-notifier package in Ubuntu: New Status in xdiagnose package in Ubuntu: Confirmed Status in xubuntu-default-settings package in Ubuntu: Invalid Status in zulucrypt package in Ubuntu: New Bug description: Posting here what gnome says about porting to wayland, and their tests: GNOME Applications under Wayland GTK+ has a Wayland backend. If it was enabled at compile-time, you can run a GTK+ application under Wayland simply by: GDK_BACKEND=wayland gnome-calculator Applications that use Clutter or clutter-gtk also need the Clutter Wayland backend enabled: GDK_BACKEND=wayland CLUTTER_BACKEND=wayland cheese https://wiki.gnome.org/Initiatives/Wayland/Applications ==> so hope the settings are well set at compile time; maybe a rebuilt to get sure all apps are ok. Steps to reproduce: 1. Install Ubuntu 17.10 2. Install backintime-qt4 or gparted application from above list (full may be acquired from https://codesearch.debian.net/search?q=pkexec+filetype%3Adesktop+path%3A*%2Fapplications%2F*&perpkg=1&page=4 ) 3a. Try to launch backintime-qt4 from shortcut "Back In Time (root)" (located in /usr/share/applications/backintime-qt4-root.desktop, it uses pkexec ($ cat /usr/share/applications/backintime-qt4-root.desktop | grep Exec Exec=pkexec backintime-qt4) 3b. Try to launch Gparted from shortcut "GParted" (located in /usr/share/applications/gparted.desktop, it uses gparted-pkexec) 4a.1. Back In Time does not start from GUI. 4a.2. Back In Time shows error message in console: 4b. gparted-pkexec does not start, reports error $ gparted-pkexec Created symlink /run/systemd/system/-.mount → /dev/null. Created symlink /run/systemd/system/run-user-1000.mount → /dev/null. Created symlink /run/systemd/system/run-user-121.mount → /dev/null. Created symlink /run/systemd/system/tmp.mount → /dev/null. No protocol specified (gpartedbin:12831): Gtk-WARNING **: cannot open display: :0 Removed /run/systemd/system/-.mount. Removed /run/systemd/system/run-user-1000.mount. Removed /run/systemd/system/run-user-121.mount. Removed /run/systemd/system/tmp.mount. $ pkexec backintime-qt4 Back In Time Version: 1.1.12 Back In Time comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to redistribute it under certain conditions; type `backintime --license' for details. No protocol specified app.py: cannot connect to X server :0 Expected results: * backintime-qt4 may be run as root Actual results: * unable to run backintime-qt4 as root Workaround: * setting "xhost +si:localuser:root" helps. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: backintime-qt4 1.1.12-2 ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5 Uname: Linux 4.12.0-11-generic i686 ApportVersion: 2.20.6-0ubuntu7 Architecture: i386 CurrentDesktop: GNOME Date: Sun Aug 27 14:23:14 2017 InstallationDate: Installed on 2017-08-26 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha i386 (20170826)
[Touch-packages] [Bug 1720570] Re: Open button in headerbar is not themed when no file is selected
The button also has wrong theming when the dialogue goes to the background (not focused). See the attached screencast. ** Attachment added: "Open-button-wrong-theming.ogv" https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1720570/+attachment/4959465/+files/Open-button-wrong-theming.ogv -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1720570 Title: Open button in headerbar is not themed when no file is selected Status in ubuntu-themes package in Ubuntu: New Bug description: Steps: 1. Open LibreOffice Writer 2. Choose Open a file 3. Make sure that there are no files selected 4. The Open button in the headerbar in not themed See attached screenshot. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: light-themes 16.10+17.10.20170929-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-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Sep 30 21:06:07 2017 InstallationDate: Installed on 2017-09-21 (9 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170919) PackageArchitecture: all SourcePackage: ubuntu-themes UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1720570/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1713313] Re: Unable to launch pkexec'ed applications on Wayland session
@Jeremy Bicha (jbicha) As you may know I created script for automation - see my comment #20 https://bugs.launchpad.net/ubuntu/+source/gui-ufw/+bug/1713313/comments/20 ). And I collected all found problems here. I added more affected packages here: * `apport` because of /usr/share/apport/root_info_wrapper and /usr/share/apport/apport-gtk . * `cinnamon` and `cinnamon-common` because of /usr/share/cinnamon/cinnamon-settings-users/cinnamon-settings-users.py . * `caja-admin` because of /usr/bin/caja as root. * `guidedog` because of "Authentication is required to run Guidedog script" /bin/sh. * `update-notifier-common` because of /usr/lib/update-notifier/cddistupgrader and /usr/lib/update-notifier/package-system-locked . It was too difficult to create separate bug reports for each application for me. I hope that community may help here. I hope that all we make Ubuntu better. ** Also affects: update-notifier (Ubuntu) Importance: Undecided Status: New ** Also affects: apport (Ubuntu) Importance: Undecided Status: New ** Also affects: caja-admin (Ubuntu) Importance: Undecided Status: New ** Also affects: cinnamon (Ubuntu) Importance: Undecided Status: New ** Also affects: guidedog (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1713313 Title: Unable to launch pkexec'ed applications on Wayland session Status in apport package in Ubuntu: New Status in apt-offline package in Ubuntu: New Status in backintime package in Ubuntu: Confirmed Status in budgie-welcome package in Ubuntu: Invalid Status in caja-admin package in Ubuntu: New Status in cinnamon package in Ubuntu: New Status in ettercap package in Ubuntu: Confirmed Status in gdebi package in Ubuntu: Confirmed Status in gnunet-gtk package in Ubuntu: Confirmed Status in gparted package in Ubuntu: Invalid Status in gui-ufw package in Ubuntu: New Status in guidedog package in Ubuntu: New Status in hplip package in Ubuntu: Confirmed Status in italc package in Ubuntu: New Status in laptop-mode-tools package in Ubuntu: New Status in lightdm-gtk-greeter-settings package in Ubuntu: Confirmed Status in nautilus-admin package in Ubuntu: New Status in needrestart-session package in Ubuntu: Confirmed Status in nemo package in Ubuntu: Confirmed Status in policykit-1 package in Ubuntu: Invalid Status in scanmem package in Ubuntu: New Status in scap-workbench package in Ubuntu: Confirmed Status in sirikali package in Ubuntu: New Status in synaptic package in Ubuntu: Confirmed Status in thunar package in Ubuntu: New Status in tuned package in Ubuntu: New Status in ubuntustudio-controls package in Ubuntu: New Status in ubuntustudio-default-settings package in Ubuntu: New Status in update-notifier package in Ubuntu: New Status in xdiagnose package in Ubuntu: Confirmed Status in xubuntu-default-settings package in Ubuntu: New Status in zulucrypt package in Ubuntu: New Bug description: Posting here what gnome says about porting to wayland, and their tests: GNOME Applications under Wayland GTK+ has a Wayland backend. If it was enabled at compile-time, you can run a GTK+ application under Wayland simply by: GDK_BACKEND=wayland gnome-calculator Applications that use Clutter or clutter-gtk also need the Clutter Wayland backend enabled: GDK_BACKEND=wayland CLUTTER_BACKEND=wayland cheese https://wiki.gnome.org/Initiatives/Wayland/Applications ==> so hope the settings are well set at compile time; maybe a rebuilt to get sure all apps are ok. Steps to reproduce: 1. Install Ubuntu 17.10 2. Install backintime-qt4 or gparted application from above list (full may be acquired from https://codesearch.debian.net/search?q=pkexec+filetype%3Adesktop+path%3A*%2Fapplications%2F*&perpkg=1&page=4 ) 3a. Try to launch backintime-qt4 from shortcut "Back In Time (root)" (located in /usr/share/applications/backintime-qt4-root.desktop, it uses pkexec ($ cat /usr/share/applications/backintime-qt4-root.desktop | grep Exec Exec=pkexec backintime-qt4) 3b. Try to launch Gparted from shortcut "GParted" (located in /usr/share/applications/gparted.desktop, it uses gparted-pkexec) 4a.1. Back In Time does not start from GUI. 4a.2. Back In Time shows error message in console: 4b. gparted-pkexec does not start, reports error $ gparted-pkexec Created symlink /run/systemd/system/-.mount → /dev/null. Created symlink /run/systemd/system/run-user-1000.mount → /dev/null. Created symlink /run/systemd/system/run-user-121.mount → /dev/null. Created symlink /run/systemd/system/tmp.mount → /dev/null. No protocol specified
[Touch-packages] [Bug 1709500] Re: [UIFe] Headerbar buttons that are highlighted/coloured in Adwaita are not coloured at all in Ambiance.
I think this caused this regression Bug #1720570. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1709500 Title: [UIFe] Headerbar buttons that are highlighted/coloured in Adwaita are not coloured at all in Ambiance. Status in ubuntu-themes package in Ubuntu: Fix Released Status in ubuntu-themes source package in Artful: Fix Released Bug description: Using Ambiance on artful, the "action buttons" used in GtkHeaderBar are using a color similar to bar background which makes them not stand out. One example is the file-roller extract dialog, when using Adwaita the "extract" button is blue which make it an obvious click target, that's not the case under our themes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1709500/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1720570] [NEW] Open button in headerbar is not themed when no file is selected
Public bug reported: Steps: 1. Open LibreOffice Writer 2. Choose Open a file 3. Make sure that there are no files selected 4. The Open button in the headerbar in not themed See attached screenshot. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: light-themes 16.10+17.10.20170929-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-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Sep 30 21:06:07 2017 InstallationDate: Installed on 2017-09-21 (9 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170919) PackageArchitecture: all SourcePackage: ubuntu-themes UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu-themes (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful regression-release ** Attachment added: "Open-button-not-themed.png" https://bugs.launchpad.net/bugs/1720570/+attachment/4959450/+files/Open-button-not-themed.png ** Tags added: regression-release -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1720570 Title: Open button in headerbar is not themed when no file is selected Status in ubuntu-themes package in Ubuntu: New Bug description: Steps: 1. Open LibreOffice Writer 2. Choose Open a file 3. Make sure that there are no files selected 4. The Open button in the headerbar in not themed See attached screenshot. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: light-themes 16.10+17.10.20170929-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-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Sep 30 21:06:07 2017 InstallationDate: Installed on 2017-09-21 (9 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170919) PackageArchitecture: all SourcePackage: ubuntu-themes UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1720570/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1596200] Re: Ubuntu 16.04: unresponsive keyboard (15 sec) after grub
*** This bug is a duplicate of bug 1599306 *** https://bugs.launchpad.net/bugs/1599306 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xinput (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kbd in Ubuntu. https://bugs.launchpad.net/bugs/1596200 Title: Ubuntu 16.04: unresponsive keyboard (15 sec) after grub Status in kbd package in Ubuntu: Confirmed Status in udev package in Ubuntu: Confirmed Status in xinput package in Ubuntu: Confirmed Bug description: I've upgraded my notebook with an SSD. All works fine and I can reach the login in less than 10 seconds. Problem is I can't use the internal keyboard (perfectly working on grub) for at least 10-15 seconds, then it starts to working just fine. The touchpad and capacitive buttons are working without issues. Luckily I have a second HDD on my machine and I've made some tests with the old mechanical drive, with this unit I can input my password on LightDM without any delay. The issue is not (only) related to Xorg or LightDM, because starting in recovery mode shown the same issue with both disks: if I use an external keyboard (a Logitech k400r in my case) I have no issue at all on both login and recovery mode. Seems kdb needs some time to be up and running. Here's a video showing a full cycle of boots: https://youtu.be/yseDPvqWNw4 And here a video of the recovery mode: https://youtu.be/vbsD9tb-Dn8 Fresh install of Ubuntu 16.04 LTS without any other packages. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2 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 CurrentDesktop: Unity Date: Sat Jun 25 12:01:50 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) [8086:2a02] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Mobile GM965/GL960 Integrated Graphics Controller (primary) [103c:30cd] Subsystem: Hewlett-Packard Company Mobile GM965/GL960 Integrated Graphics Controller (secondary) [103c:30cd] InstallationDate: Installed on 2016-06-25 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Hewlett-Packard HP Pavilion dv2700 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic root=UUID=56bb4994-c2b0-4ada-9f3d-493898e2ad39 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/07/2008 dmi.bios.vendor: Phoenix dmi.bios.version: F.2B dmi.board.name: 30CD dmi.board.vendor: Wistron dmi.board.version: 80.52 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenix:bvrF.2B:bd05/07/2008:svnHewlett-Packard:pnHPPaviliondv2700NotebookPC:pvrF.2B:rvnWistron:rn30CD:rvr80.52:cvnHewlett-Packard:ct10:cvrN/A: dmi.product.name: HP Pavilion dv2700 Notebook PC dmi.product.version: F.2B dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2 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 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Sat Jun 25 12:00:23 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 19778 vendor SEC xserver.version: 2:1.18.3-1ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kbd/+bug/1596200/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1596200] Re: Ubuntu 16.04: unresponsive keyboard (15 sec) after grub
*** This bug is a duplicate of bug 1599306 *** https://bugs.launchpad.net/bugs/1599306 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: udev (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kbd in Ubuntu. https://bugs.launchpad.net/bugs/1596200 Title: Ubuntu 16.04: unresponsive keyboard (15 sec) after grub Status in kbd package in Ubuntu: Confirmed Status in udev package in Ubuntu: Confirmed Status in xinput package in Ubuntu: Confirmed Bug description: I've upgraded my notebook with an SSD. All works fine and I can reach the login in less than 10 seconds. Problem is I can't use the internal keyboard (perfectly working on grub) for at least 10-15 seconds, then it starts to working just fine. The touchpad and capacitive buttons are working without issues. Luckily I have a second HDD on my machine and I've made some tests with the old mechanical drive, with this unit I can input my password on LightDM without any delay. The issue is not (only) related to Xorg or LightDM, because starting in recovery mode shown the same issue with both disks: if I use an external keyboard (a Logitech k400r in my case) I have no issue at all on both login and recovery mode. Seems kdb needs some time to be up and running. Here's a video showing a full cycle of boots: https://youtu.be/yseDPvqWNw4 And here a video of the recovery mode: https://youtu.be/vbsD9tb-Dn8 Fresh install of Ubuntu 16.04 LTS without any other packages. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2 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 CurrentDesktop: Unity Date: Sat Jun 25 12:01:50 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) [8086:2a02] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Mobile GM965/GL960 Integrated Graphics Controller (primary) [103c:30cd] Subsystem: Hewlett-Packard Company Mobile GM965/GL960 Integrated Graphics Controller (secondary) [103c:30cd] InstallationDate: Installed on 2016-06-25 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Hewlett-Packard HP Pavilion dv2700 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic root=UUID=56bb4994-c2b0-4ada-9f3d-493898e2ad39 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/07/2008 dmi.bios.vendor: Phoenix dmi.bios.version: F.2B dmi.board.name: 30CD dmi.board.vendor: Wistron dmi.board.version: 80.52 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenix:bvrF.2B:bd05/07/2008:svnHewlett-Packard:pnHPPaviliondv2700NotebookPC:pvrF.2B:rvnWistron:rn30CD:rvr80.52:cvnHewlett-Packard:ct10:cvrN/A: dmi.product.name: HP Pavilion dv2700 Notebook PC dmi.product.version: F.2B dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2 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 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Sat Jun 25 12:00:23 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 19778 vendor SEC xserver.version: 2:1.18.3-1ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kbd/+bug/1596200/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1596200] Re: Ubuntu 16.04: unresponsive keyboard (15 sec) after grub
*** This bug is a duplicate of bug 1599306 *** https://bugs.launchpad.net/bugs/1599306 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: kbd (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kbd in Ubuntu. https://bugs.launchpad.net/bugs/1596200 Title: Ubuntu 16.04: unresponsive keyboard (15 sec) after grub Status in kbd package in Ubuntu: Confirmed Status in udev package in Ubuntu: Confirmed Status in xinput package in Ubuntu: Confirmed Bug description: I've upgraded my notebook with an SSD. All works fine and I can reach the login in less than 10 seconds. Problem is I can't use the internal keyboard (perfectly working on grub) for at least 10-15 seconds, then it starts to working just fine. The touchpad and capacitive buttons are working without issues. Luckily I have a second HDD on my machine and I've made some tests with the old mechanical drive, with this unit I can input my password on LightDM without any delay. The issue is not (only) related to Xorg or LightDM, because starting in recovery mode shown the same issue with both disks: if I use an external keyboard (a Logitech k400r in my case) I have no issue at all on both login and recovery mode. Seems kdb needs some time to be up and running. Here's a video showing a full cycle of boots: https://youtu.be/yseDPvqWNw4 And here a video of the recovery mode: https://youtu.be/vbsD9tb-Dn8 Fresh install of Ubuntu 16.04 LTS without any other packages. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2 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 CurrentDesktop: Unity Date: Sat Jun 25 12:01:50 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) [8086:2a02] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Mobile GM965/GL960 Integrated Graphics Controller (primary) [103c:30cd] Subsystem: Hewlett-Packard Company Mobile GM965/GL960 Integrated Graphics Controller (secondary) [103c:30cd] InstallationDate: Installed on 2016-06-25 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Hewlett-Packard HP Pavilion dv2700 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic root=UUID=56bb4994-c2b0-4ada-9f3d-493898e2ad39 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/07/2008 dmi.bios.vendor: Phoenix dmi.bios.version: F.2B dmi.board.name: 30CD dmi.board.vendor: Wistron dmi.board.version: 80.52 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenix:bvrF.2B:bd05/07/2008:svnHewlett-Packard:pnHPPaviliondv2700NotebookPC:pvrF.2B:rvnWistron:rn30CD:rvr80.52:cvnHewlett-Packard:ct10:cvrN/A: dmi.product.name: HP Pavilion dv2700 Notebook PC dmi.product.version: F.2B dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2 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 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Sat Jun 25 12:00:23 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 19778 vendor SEC xserver.version: 2:1.18.3-1ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kbd/+bug/1596200/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1713313] Re: Unable to launch pkexec'ed applications on Wayland session
Norbert, yes but the package name was wrong. There already is LP: #1713238 It's difficult to manage a single bug affecting large number of packages like this in Launchpad in my opinion. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1713313 Title: Unable to launch pkexec'ed applications on Wayland session Status in apt-offline package in Ubuntu: New Status in backintime package in Ubuntu: Confirmed Status in budgie-welcome package in Ubuntu: Invalid Status in ettercap package in Ubuntu: Confirmed Status in gdebi package in Ubuntu: Confirmed Status in gnunet-gtk package in Ubuntu: Confirmed Status in gparted package in Ubuntu: Invalid Status in gui-ufw package in Ubuntu: New Status in hplip package in Ubuntu: Confirmed Status in italc package in Ubuntu: New Status in laptop-mode-tools package in Ubuntu: New Status in lightdm-gtk-greeter-settings package in Ubuntu: Confirmed Status in nautilus-admin package in Ubuntu: New Status in needrestart-session package in Ubuntu: Confirmed Status in nemo package in Ubuntu: Confirmed Status in policykit-1 package in Ubuntu: Invalid Status in scanmem package in Ubuntu: New Status in scap-workbench package in Ubuntu: Confirmed Status in sirikali package in Ubuntu: New Status in synaptic package in Ubuntu: Confirmed Status in thunar package in Ubuntu: New Status in tuned package in Ubuntu: New Status in ubuntustudio-controls package in Ubuntu: New Status in ubuntustudio-default-settings package in Ubuntu: New Status in xdiagnose package in Ubuntu: Confirmed Status in xubuntu-default-settings package in Ubuntu: New Status in zulucrypt package in Ubuntu: New Bug description: Posting here what gnome says about porting to wayland, and their tests: GNOME Applications under Wayland GTK+ has a Wayland backend. If it was enabled at compile-time, you can run a GTK+ application under Wayland simply by: GDK_BACKEND=wayland gnome-calculator Applications that use Clutter or clutter-gtk also need the Clutter Wayland backend enabled: GDK_BACKEND=wayland CLUTTER_BACKEND=wayland cheese https://wiki.gnome.org/Initiatives/Wayland/Applications ==> so hope the settings are well set at compile time; maybe a rebuilt to get sure all apps are ok. Steps to reproduce: 1. Install Ubuntu 17.10 2. Install backintime-qt4 or gparted application from above list (full may be acquired from https://codesearch.debian.net/search?q=pkexec+filetype%3Adesktop+path%3A*%2Fapplications%2F*&perpkg=1&page=4 ) 3a. Try to launch backintime-qt4 from shortcut "Back In Time (root)" (located in /usr/share/applications/backintime-qt4-root.desktop, it uses pkexec ($ cat /usr/share/applications/backintime-qt4-root.desktop | grep Exec Exec=pkexec backintime-qt4) 3b. Try to launch Gparted from shortcut "GParted" (located in /usr/share/applications/gparted.desktop, it uses gparted-pkexec) 4a.1. Back In Time does not start from GUI. 4a.2. Back In Time shows error message in console: 4b. gparted-pkexec does not start, reports error $ gparted-pkexec Created symlink /run/systemd/system/-.mount → /dev/null. Created symlink /run/systemd/system/run-user-1000.mount → /dev/null. Created symlink /run/systemd/system/run-user-121.mount → /dev/null. Created symlink /run/systemd/system/tmp.mount → /dev/null. No protocol specified (gpartedbin:12831): Gtk-WARNING **: cannot open display: :0 Removed /run/systemd/system/-.mount. Removed /run/systemd/system/run-user-1000.mount. Removed /run/systemd/system/run-user-121.mount. Removed /run/systemd/system/tmp.mount. $ pkexec backintime-qt4 Back In Time Version: 1.1.12 Back In Time comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to redistribute it under certain conditions; type `backintime --license' for details. No protocol specified app.py: cannot connect to X server :0 Expected results: * backintime-qt4 may be run as root Actual results: * unable to run backintime-qt4 as root Workaround: * setting "xhost +si:localuser:root" helps. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: backintime-qt4 1.1.12-2 ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5 Uname: Linux 4.12.0-11-generic i686 ApportVersion: 2.20.6-0ubuntu7 Architecture: i386 CurrentDesktop: GNOME Date: Sun Aug 27 14:23:14 2017 InstallationDate: Installed on 2017-08-26 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha i386 (20170826) PackageArchitecture: all SourcePackage: backintime UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.
[Touch-packages] [Bug 207135] Re: pulseaudio uses too much CPU
My system was doing the same thing. It went from working properly one minute then broken for no reason. Very high CPU usage for pulseaudio, polkitd, dbus-daemon. PulseAudio sound was stuttering. Trying to edit the sound settings in the volume control was impossible because it kept losing the connection to PulseAudio. Syslog was full of thousands of this message repeated: [pulseaudio] alsa-mixer.c: Failed to set switch of IEC958: Operation not permitted I've had issues on this system where the sound output would randomly switch from analog out to some other method or even another device like HDMI which I don't use. I believe due to the plug auto-detection on the audio connector. So I unplugged, replugged, and jiggled the audio connector on the back of the computer and that fixed everything. I guess the plug was loose or the motherboard is buggy and doesn't properly detect when an analog plug is in the audio connector. This was causing pulseaudio to go haywire and hammer the system (not a surprise considering the history of that software). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/207135 Title: pulseaudio uses too much CPU Status in pulseaudio package in Ubuntu: Fix Released Bug description: Binary package hint: pulseaudio Pulseaudio uses between 6 and 8% of my CPU (AMD Athlon(tm) 64 Processor 3500+) when I'm just listening music using Rhythmbox. Seems too much IMHO. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/207135/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1713313] Re: Unable to launch pkexec'ed applications on Wayland session
Gufw is really affected. See below: $ apt-cache policy gufw gufw: Installed: 17.10.0-0ubuntu1 Candidate: 17.10.0-0ubuntu1 Version table: *** 17.10.0-0ubuntu1 500 500 http://ru.archive.ubuntu.com/ubuntu artful/universe i386 Packages 100 /var/lib/dpkg/status artful@artful:~$ dpkg -L gufw | grep desktop /etc/gufw/app_profiles/remote-desktop-protocol.jhansonxi /usr/share/applications/gufw.desktop artful@artful:~$ cat /usr/share/applications/gufw.desktop | grep Exec Exec=gufw artful@artful:~$ gufw # !!! # enter password here # !!! # No protocol specified Unable to init server: Could not connect: Connection refused No protocol specified Unable to init server: Could not connect: Connection refused (gufw.py:3873): Gdk-CRITICAL **: gdk_keymap_get_for_display: assertion 'GDK_IS_DISPLAY (display)' failed (gufw.py:3873): Gdk-CRITICAL **: gdk_keymap_get_modifier_mask: assertion 'GDK_IS_KEYMAP (keymap)' failed (gufw.py:3873): Gdk-CRITICAL **: gdk_keymap_get_for_display: assertion 'GDK_IS_DISPLAY (display)' failed (gufw.py:3873): Gtk-CRITICAL **: _gtk_replace_virtual_modifiers: assertion 'GDK_IS_KEYMAP (keymap)' failed (gufw.py:3873): Gdk-CRITICAL **: gdk_keymap_get_for_display: assertion 'GDK_IS_DISPLAY (display)' failed (gufw.py:3873): Gdk-CRITICAL **: gdk_keymap_get_modifier_mask: assertion 'GDK_IS_KEYMAP (keymap)' failed (gufw.py:3873): Gdk-CRITICAL **: gdk_keymap_get_for_display: assertion 'GDK_IS_DISPLAY (display)' failed (gufw.py:3873): Gtk-CRITICAL **: _gtk_replace_virtual_modifiers: assertion 'GDK_IS_KEYMAP (keymap)' failed (gufw.py:3873): Gdk-CRITICAL **: gdk_keymap_get_for_display: assertion 'GDK_IS_DISPLAY (display)' failed (gufw.py:3873): Gdk-CRITICAL **: gdk_keymap_get_modifier_mask: assertion 'GDK_IS_KEYMAP (keymap)' failed (gufw.py:3873): Gdk-CRITICAL **: gdk_keymap_get_for_display: assertion 'GDK_IS_DISPLAY (display)' failed (gufw.py:3873): Gtk-CRITICAL **: _gtk_replace_virtual_modifiers: assertion 'GDK_IS_KEYMAP (keymap)' failed (gufw.py:3873): Gdk-CRITICAL **: gdk_keymap_get_for_display: assertion 'GDK_IS_DISPLAY (display)' failed (gufw.py:3873): Gdk-CRITICAL **: gdk_keymap_get_modifier_mask: assertion 'GDK_IS_KEYMAP (keymap)' failed (gufw.py:3873): Gdk-CRITICAL **: gdk_keymap_get_for_display: assertion 'GDK_IS_DISPLAY (display)' failed (gufw.py:3873): Gtk-CRITICAL **: _gtk_replace_virtual_modifiers: assertion 'GDK_IS_KEYMAP (keymap)' failed (gufw.py:3873): Gdk-CRITICAL **: gdk_keymap_get_for_display: assertion 'GDK_IS_DISPLAY (display)' failed (gufw.py:3873): Gdk-CRITICAL **: gdk_keymap_get_modifier_mask: assertion 'GDK_IS_KEYMAP (keymap)' failed (gufw.py:3873): Gdk-CRITICAL **: gdk_keymap_get_for_display: assertion 'GDK_IS_DISPLAY (display)' failed (gufw.py:3873): Gtk-CRITICAL **: _gtk_replace_virtual_modifiers: assertion 'GDK_IS_KEYMAP (keymap)' failed (gufw.py:3873): Gdk-CRITICAL **: gdk_keymap_get_for_display: assertion 'GDK_IS_DISPLAY (display)' failed (gufw.py:3873): Gdk-CRITICAL **: gdk_keymap_get_modifier_mask: assertion 'GDK_IS_KEYMAP (keymap)' failed (gufw.py:3873): Gdk-CRITICAL **: gdk_keymap_get_for_display: assertion 'GDK_IS_DISPLAY (display)' failed (gufw.py:3873): Gtk-CRITICAL **: _gtk_replace_virtual_modifiers: assertion 'GDK_IS_KEYMAP (keymap)' failed (gufw.py:3873): Gdk-CRITICAL **: gdk_keymap_get_for_display: assertion 'GDK_IS_DISPLAY (display)' failed (gufw.py:3873): Gdk-CRITICAL **: gdk_keymap_get_modifier_mask: assertion 'GDK_IS_KEYMAP (keymap)' failed (gufw.py:3873): Gdk-CRITICAL **: gdk_keymap_get_for_display: assertion 'GDK_IS_DISPLAY (display)' failed (gufw.py:3873): Gtk-CRITICAL **: _gtk_replace_virtual_modifiers: assertion 'GDK_IS_KEYMAP (keymap)' failed (gufw.py:3873): Gdk-CRITICAL **: gdk_keymap_get_for_display: assertion 'GDK_IS_DISPLAY (display)' failed (gufw.py:3873): Gdk-CRITICAL **: gdk_keymap_get_modifier_mask: assertion 'GDK_IS_KEYMAP (keymap)' failed (gufw.py:3873): Gdk-CRITICAL **: gdk_keymap_get_for_display: assertion 'GDK_IS_DISPLAY (display)' failed (gufw.py:3873): Gtk-CRITICAL **: _gtk_replace_virtual_modifiers: assertion 'GDK_IS_KEYMAP (keymap)' failed (gufw.py:3873): Gdk-CRITICAL **: gdk_keymap_get_for_display: assertion 'GDK_IS_DISPLAY (display)' failed (gufw.py:3873): Gdk-CRITICAL **: gdk_keymap_get_modifier_mask: assertion 'GDK_IS_KEYMAP (keymap)' failed (gufw.py:3873): Gdk-CRITICAL **: gdk_keymap_get_for_display: assertion 'GDK_IS_DISPLAY (display)' failed (gufw.py:3873): Gtk-CRITICAL **: _gtk_replace_virtual_modifiers: assertion 'GDK_IS_KEYMAP (keymap)' failed (gufw.py:3873): Gdk-CRITICAL **: gdk_keymap_get_for_display: assertion 'GDK_IS_DISPLAY (display)' failed (gufw.py:3873): Gdk-CRITICAL **: gdk_keymap_get_modifier_mask: assertion 'GDK_IS_KEYMAP (keymap)' failed (gufw.py:3873): Gdk-CRITICAL **: gdk_keymap_get_for_display: assertion 'GDK_IS_DISPLAY (display)' failed (gufw.py:3873): Gtk-CRITICAL **: _gtk_replace_virtual_modifiers: assertion 'GDK_IS_KEYMAP (keymap)' failed /usr/bin/guf
[Touch-packages] [Bug 1713313] Re: Unable to launch pkexec'ed applications on Wayland session
Budgie welcome in its current form will never be run on a Wayland session. Marked as invalid ** Changed in: budgie-welcome (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1713313 Title: Unable to launch pkexec'ed applications on Wayland session Status in apt-offline package in Ubuntu: New Status in backintime package in Ubuntu: Confirmed Status in budgie-welcome package in Ubuntu: Invalid Status in ettercap package in Ubuntu: Confirmed Status in gdebi package in Ubuntu: Confirmed Status in gnunet-gtk package in Ubuntu: Confirmed Status in gparted package in Ubuntu: Invalid Status in hplip package in Ubuntu: Confirmed Status in italc package in Ubuntu: New Status in laptop-mode-tools package in Ubuntu: New Status in lightdm-gtk-greeter-settings package in Ubuntu: Confirmed Status in nautilus-admin package in Ubuntu: New Status in needrestart-session package in Ubuntu: Confirmed Status in nemo package in Ubuntu: Confirmed Status in policykit-1 package in Ubuntu: Invalid Status in scanmem package in Ubuntu: New Status in scap-workbench package in Ubuntu: Confirmed Status in sirikali package in Ubuntu: New Status in synaptic package in Ubuntu: Confirmed Status in thunar package in Ubuntu: New Status in tuned package in Ubuntu: New Status in ubuntustudio-controls package in Ubuntu: New Status in ubuntustudio-default-settings package in Ubuntu: New Status in xdiagnose package in Ubuntu: Confirmed Status in xubuntu-default-settings package in Ubuntu: New Status in zulucrypt package in Ubuntu: New Bug description: Posting here what gnome says about porting to wayland, and their tests: GNOME Applications under Wayland GTK+ has a Wayland backend. If it was enabled at compile-time, you can run a GTK+ application under Wayland simply by: GDK_BACKEND=wayland gnome-calculator Applications that use Clutter or clutter-gtk also need the Clutter Wayland backend enabled: GDK_BACKEND=wayland CLUTTER_BACKEND=wayland cheese https://wiki.gnome.org/Initiatives/Wayland/Applications ==> so hope the settings are well set at compile time; maybe a rebuilt to get sure all apps are ok. Steps to reproduce: 1. Install Ubuntu 17.10 2. Install backintime-qt4 or gparted application from above list (full may be acquired from https://codesearch.debian.net/search?q=pkexec+filetype%3Adesktop+path%3A*%2Fapplications%2F*&perpkg=1&page=4 ) 3a. Try to launch backintime-qt4 from shortcut "Back In Time (root)" (located in /usr/share/applications/backintime-qt4-root.desktop, it uses pkexec ($ cat /usr/share/applications/backintime-qt4-root.desktop | grep Exec Exec=pkexec backintime-qt4) 3b. Try to launch Gparted from shortcut "GParted" (located in /usr/share/applications/gparted.desktop, it uses gparted-pkexec) 4a.1. Back In Time does not start from GUI. 4a.2. Back In Time shows error message in console: 4b. gparted-pkexec does not start, reports error $ gparted-pkexec Created symlink /run/systemd/system/-.mount → /dev/null. Created symlink /run/systemd/system/run-user-1000.mount → /dev/null. Created symlink /run/systemd/system/run-user-121.mount → /dev/null. Created symlink /run/systemd/system/tmp.mount → /dev/null. No protocol specified (gpartedbin:12831): Gtk-WARNING **: cannot open display: :0 Removed /run/systemd/system/-.mount. Removed /run/systemd/system/run-user-1000.mount. Removed /run/systemd/system/run-user-121.mount. Removed /run/systemd/system/tmp.mount. $ pkexec backintime-qt4 Back In Time Version: 1.1.12 Back In Time comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to redistribute it under certain conditions; type `backintime --license' for details. No protocol specified app.py: cannot connect to X server :0 Expected results: * backintime-qt4 may be run as root Actual results: * unable to run backintime-qt4 as root Workaround: * setting "xhost +si:localuser:root" helps. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: backintime-qt4 1.1.12-2 ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5 Uname: Linux 4.12.0-11-generic i686 ApportVersion: 2.20.6-0ubuntu7 Architecture: i386 CurrentDesktop: GNOME Date: Sun Aug 27 14:23:14 2017 InstallationDate: Installed on 2017-08-26 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha i386 (20170826) PackageArchitecture: all SourcePackage: backintime UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt-offline/+bug/1713313/+subscription
[Touch-packages] [Bug 1713313] Re: Unable to launch pkexec'ed applications on Wayland session
** No longer affects: gufw (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1713313 Title: Unable to launch pkexec'ed applications on Wayland session Status in apt-offline package in Ubuntu: New Status in backintime package in Ubuntu: Confirmed Status in budgie-welcome package in Ubuntu: New Status in ettercap package in Ubuntu: Confirmed Status in gdebi package in Ubuntu: Confirmed Status in gnunet-gtk package in Ubuntu: Confirmed Status in gparted package in Ubuntu: Invalid Status in hplip package in Ubuntu: Confirmed Status in italc package in Ubuntu: New Status in laptop-mode-tools package in Ubuntu: New Status in lightdm-gtk-greeter-settings package in Ubuntu: Confirmed Status in nautilus-admin package in Ubuntu: New Status in needrestart-session package in Ubuntu: Confirmed Status in nemo package in Ubuntu: Confirmed Status in policykit-1 package in Ubuntu: Invalid Status in scanmem package in Ubuntu: New Status in scap-workbench package in Ubuntu: Confirmed Status in sirikali package in Ubuntu: New Status in synaptic package in Ubuntu: Confirmed Status in thunar package in Ubuntu: New Status in tuned package in Ubuntu: New Status in ubuntustudio-controls package in Ubuntu: New Status in ubuntustudio-default-settings package in Ubuntu: New Status in xdiagnose package in Ubuntu: Confirmed Status in xubuntu-default-settings package in Ubuntu: New Status in zulucrypt package in Ubuntu: New Bug description: Posting here what gnome says about porting to wayland, and their tests: GNOME Applications under Wayland GTK+ has a Wayland backend. If it was enabled at compile-time, you can run a GTK+ application under Wayland simply by: GDK_BACKEND=wayland gnome-calculator Applications that use Clutter or clutter-gtk also need the Clutter Wayland backend enabled: GDK_BACKEND=wayland CLUTTER_BACKEND=wayland cheese https://wiki.gnome.org/Initiatives/Wayland/Applications ==> so hope the settings are well set at compile time; maybe a rebuilt to get sure all apps are ok. Steps to reproduce: 1. Install Ubuntu 17.10 2. Install backintime-qt4 or gparted application from above list (full may be acquired from https://codesearch.debian.net/search?q=pkexec+filetype%3Adesktop+path%3A*%2Fapplications%2F*&perpkg=1&page=4 ) 3a. Try to launch backintime-qt4 from shortcut "Back In Time (root)" (located in /usr/share/applications/backintime-qt4-root.desktop, it uses pkexec ($ cat /usr/share/applications/backintime-qt4-root.desktop | grep Exec Exec=pkexec backintime-qt4) 3b. Try to launch Gparted from shortcut "GParted" (located in /usr/share/applications/gparted.desktop, it uses gparted-pkexec) 4a.1. Back In Time does not start from GUI. 4a.2. Back In Time shows error message in console: 4b. gparted-pkexec does not start, reports error $ gparted-pkexec Created symlink /run/systemd/system/-.mount → /dev/null. Created symlink /run/systemd/system/run-user-1000.mount → /dev/null. Created symlink /run/systemd/system/run-user-121.mount → /dev/null. Created symlink /run/systemd/system/tmp.mount → /dev/null. No protocol specified (gpartedbin:12831): Gtk-WARNING **: cannot open display: :0 Removed /run/systemd/system/-.mount. Removed /run/systemd/system/run-user-1000.mount. Removed /run/systemd/system/run-user-121.mount. Removed /run/systemd/system/tmp.mount. $ pkexec backintime-qt4 Back In Time Version: 1.1.12 Back In Time comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to redistribute it under certain conditions; type `backintime --license' for details. No protocol specified app.py: cannot connect to X server :0 Expected results: * backintime-qt4 may be run as root Actual results: * unable to run backintime-qt4 as root Workaround: * setting "xhost +si:localuser:root" helps. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: backintime-qt4 1.1.12-2 ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5 Uname: Linux 4.12.0-11-generic i686 ApportVersion: 2.20.6-0ubuntu7 Architecture: i386 CurrentDesktop: GNOME Date: Sun Aug 27 14:23:14 2017 InstallationDate: Installed on 2017-08-26 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha i386 (20170826) PackageArchitecture: all SourcePackage: backintime UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt-offline/+bug/1713313/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://l
[Touch-packages] [Bug 1718719] Re: qemu can't capture keys properly under wayland
Now the question is should the patch be dropped or wait for a fix from upstream. I'm leaning towards the first option, since artful is about to be released. ** Package changed: wayland (Ubuntu) => xorg-server (Ubuntu) ** Changed in: xorg-server (Ubuntu) Status: New => Triaged ** Changed in: xorg-server (Ubuntu) Assignee: (unassigned) => Timo Aaltonen (tjaalton) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1718719 Title: qemu can't capture keys properly under wayland Status in QEMU: New Status in XServer: Incomplete Status in qemu package in Ubuntu: New Status in xorg-server package in Ubuntu: Triaged Bug description: This appears to be different than the previous similar bugs; patches do look to be applied to use libinput in the wayland case. Still: unknown keycodes `(unnamed)', please report to qemu-de...@nongnu.org I am using qemu-system-x86 1:2.10+dfsg-0ubuntu1 on artful. Many key inputs work correctly, but at boot the system will not properly catch the arrow keys, the above error shows up immediately after hitting Esc (for instance) to get to the boot menu. Booting from CD onto a daily Ubuntu desktop image, I can't navigate the splash menu. The same works correctly through virt-manager (which uses spice AFAICT, but wayland tends to crash when running virt-manager), and things work if I switch my session to Xorg rather than wayland. To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1718719/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1720116] Re: apport-gtk sigfault in libgtk-3
Reviewed all the available syslogs and found 2-3 of the apport-gtk failures per day from 9/22 to 9/27. Only one failure on 9/28 and none on 9/29. Had other problems on 9/30 which required a re-install at the 9/29 build level. Will add a comment if this problem reappears. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1720116 Title: apport-gtk sigfault in libgtk-3 Status in apport package in Ubuntu: Incomplete Bug description: Daily notification of system error and request to report it but nothing get sent. Syslog shows apport-gtk sigfault in libgtk-3. There us usually no crash dump generated. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: apport 2.20.7-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-0ubuntu1 Architecture: amd64 CrashReports: 640:0:119:6940216:2017-09-22 05:36:31.895203406 -0400:2017-09-22 05:36:27.979332060 -0400:/var/crash/_usr_share_apport_apport-gtk.0.crash CurrentDesktop: GNOME-Classic:GNOME Date: Thu Sep 28 06:54:23 2017 InstallationDate: Installed on 2017-07-24 (65 days ago) InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 (20170723) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1720116/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1720446] Re: Freefont is buggy and produce broken rendering for many indian languages
** Changed in: fonts-freefont (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fonts-freefont in Ubuntu. https://bugs.launchpad.net/bugs/1720446 Title: Freefont is buggy and produce broken rendering for many indian languages Status in fonts-freefont package in Ubuntu: Confirmed Bug description: Freefont is last updated in 2012& not maintained. It is buggy and not producing quality rendering in Most Indian Languages. This is the only font in Ubuntu as of now supported in indtaller. But this results in broken rendering. I suggest to remove this font from installer and make it optional. I also suggest to remove this from ubuntu-desktop & vlc dependency In past there was a package called ttf-indic-fonts-core as an installer dependency to support indian languages. But now that is also removed and producing Square boxes for many Indian languages. Ref : https://bugs.launchpad.net/ubuntu/+source/ttf-indic-fonts/+bug/958345/comments/39 There is a need of better addressing of Indian language support in Ubuntu prior to 17.10 . The support must come from seperate font package & not via broken ttf-freefont. As of now Beta 2 of 17.10 produces rendering errors for many languages including Malayalam because of fonts-freefont. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-freefont/+bug/1720446/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1409166] Re: Popup dialog "could not set the configuration for CRTC 65" steals keyboard, hinders login in 3-monitor configuration
I've been using LVDS + HDMI for a few years first under Ubuntu 14.04 and currently under Ubuntu 16.04. Today I setup an second external TV using the VGA port and an in-line VGA to HDMI converter box that's worked before. The necessary xrandr commands are given: `xrandr --newmode "1920x1080_60.00" 173.00 1920 2048 2248 2576 1080 1083 1088 1120 -hsync +vsync` `xrandr --addmode VGA1 "1920x1080"` However the CRTC 65 popup error message results. Although I am long-term shopping for a new laptop with HDMI + one or two DP's, it would be nice to have HDMI+VGA working now. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1409166 Title: Popup dialog "could not set the configuration for CRTC 65" steals keyboard, hinders login in 3-monitor configuration Status in xorg package in Ubuntu: Triaged Bug description: Every time I boot, while I'm trying to enter my password in the initial login screen (from Unity?), a dialog box pops up saying "Could not switch the monitor configuration could not set the configuration for CRTC 65". The dialog box also steals the keyboard focus, which is very confusing if for some reason you're entering the password on an external display while the normally unused laptop display is not visible. For example, three times in a row this morning I rebooted and tried unsuccessfully to log in. Since the dialog box is only displayed on the laptop display, which I never use when external monitors are available, I had no idea why my keyboard seemed broken. Background: My Lenovo Thinkpad X230 Tablet laptop has a VGA and a DVI connector. I have the VGA hooked up to a Viewsonic 1920x1080 monitor, positioned above the laptop display. I have a Samsung monitor to the right of the Viewsonic. Since my laptop seems to only support two displays (which also seems true in Windows), I normally disable and totally ignore my laptop display, and may have papers propped up in front of it etc. Note that when I initially configured the third display I saw the following highly confusing behavior. From Settings I tried to add a Samsung monitor to the right of the Viewsonic, via a DVI-to-HDMI passive connector, and got this dialog box when I hit "Apply": The selected configuration for displays could not be applied could not set the configuration for CRTC 65 I clicked "OK" and got another dialog box: Failed to apply configuration: %s Can't add monitor: GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._gnome_2drr_2derror_2dquark.Code2: could not set the configuration for CRTC 65 It works if I disable my laptop monitor, so it looks like the problem is with adding a third display. I would think it would be a pretty common use case to use two nice external displays and disable the laptop display. Even when the hardware can't handle a third display, the error messages should not be so confusing, and the login process shouldn't result in the keyboard being mysteriously stolen by a dialog box on a display which may never be visible. This is on Trusty 64-bit, up-to-date with upgrades. This bug seems similar to bug 1304627, but it seemed cleanest to get all the right information reported via ubuntu-bug. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11 Uname: Linux 3.13.0-43-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.6 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 CurrentDesktop: Unity Date: Fri Jan 9 15:35:57 2015 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:2203] InstallationDate: Installed on 2015-01-01 (8 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: LENOVO 343522U ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.13.0-43-generic root=UUID=6dce26c4-3d5b-4980-880e-06f249f77c57 ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/22/2013 dmi.bios.vendor: LENOVO dmi.bios.version: GCET96WW (2.56 ) dmi.board.asset.tag: Not Available dmi.board.name: 343522U dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO
[Touch-packages] [Bug 1589008] Re: Bluetooth freezing video playback In Ubuntu/Kubuntu 16.04
Still an issue; Ubuntu 17.04; 4.10.0-35-generic. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1589008 Title: Bluetooth freezing video playback In Ubuntu/Kubuntu 16.04 Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: In 16.04 when a bluetooth audio device is connected it freezes video playback and also no sound comes from online audio only streams. Issue does not exist with a wired headset. This issue does not exist with 15.10. All updates have been installed on 16.04 including backports but they have not fixed the issue. It is not browser specific and not website specific. It is not hardware specific as it affects my laptop with an intel 7260 card and my pc with an intel 8260 card. The issue exists on both ubuntu and kubuntu 16.04. I have reported it on the ubuntu support forums and after investigation a moderator noticed changed in the kernel from 4.4 and 4.2 that may becausing the issue and asked me to file a bug report. The ubuntu forum thread can be found here. http://ubuntuforums.org/showthread.php?t=2326672 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-23-generic 4.4.0-23.41 ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10 Uname: Linux 4.4.0-23-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: stephen1435 F pulseaudio /dev/snd/controlC0: stephen1435 F pulseaudio CurrentDesktop: KDE Date: Fri Jun 3 23:50:00 2016 HibernationDevice: RESUME=UUID=78e7aefc-d517-4c58-836f-a90f0b6017c6 InstallationDate: Installed on 2016-05-06 (28 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: MSI MS-7978 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-23-generic.efi.signed root=UUID=bccf2ca7-4e23-412a-ba10-7a3f915270dd ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-23-generic N/A linux-backports-modules-4.4.0-23-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-06-03 (0 days ago) dmi.bios.date: 05/16/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: C.60 dmi.board.asset.tag: Default string dmi.board.name: H170 GAMING M3 (MS-7978) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrC.60:bd05/16/2016:svnMSI:pnMS-7978:pvr2.0:rvnMSI:rnH170GAMINGM3(MS-7978):rvr2.0:cvnMSI:ct3:cvr2.0: dmi.product.name: MS-7978 dmi.product.version: 2.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1589008/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1530350] Re: package qml-module-qtquick-xmllistmodel 5.4.1-1ubuntu5 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtdeclarative-opensource- src in Ubuntu. https://bugs.launchpad.net/bugs/1530350 Title: package qml-module-qtquick-xmllistmodel 5.4.1-1ubuntu5 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1 Status in qtdeclarative-opensource-src package in Ubuntu: New Bug description: Error while upgrading to ubuntu 15.10 ProblemType: Package DistroRelease: Ubuntu 15.10 Package: qml-module-qtquick-xmllistmodel 5.4.1-1ubuntu5 ProcVersionSignature: Ubuntu 3.19.0-42.48-generic 3.19.8-ckt10 Uname: Linux 3.19.0-42-generic i686 ApportVersion: 2.19.1-0ubuntu5 Architecture: i386 Date: Thu Dec 31 18:05:28 2015 DuplicateSignature: package:qml-module-qtquick-xmllistmodel:5.4.1-1ubuntu5:subprocess installed pre-removal script returned error exit status 1 ErrorMessage: subprocess installed pre-removal script returned error exit status 1 InstallationDate: Installed on 2011-09-18 (1564 days ago) InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1) RelatedPackageVersions: dpkg 1.18.2ubuntu5.1 apt 1.0.10.2ubuntu1 SourcePackage: qtdeclarative-opensource-src Title: package qml-module-qtquick-xmllistmodel 5.4.1-1ubuntu5 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1 UpgradeStatus: Upgraded to wily on 2015-12-31 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1530350/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1720541] [NEW] flock does not lock dpkg lock file properly
Public bug reported: Test: sudo flock /var/lib/dpkg/lock -c \ 'echo 1; apt-get -o Debug::NoLocking=true check; echo 2; apt-get check' Expected behavior: apt-get fails in stage 2. Workaround (needs moreutils package) sudo lckdo /var/lib/dpkg/lock /bin/sh -c \ 'echo 1; apt-get -o Debug::NoLocking=true check; echo 2; apt-get check' Similarly, flock does not recognize lock set by e.g. apt-get. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: util-linux 2.20.1-5.1ubuntu20.9 ProcVersionSignature: Ubuntu 4.4.0-96.119~14.04.1-generic 4.4.83 Uname: Linux 4.4.0-96-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.25 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Sep 30 16:30:50 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2014-09-21 (1105 days ago) InstallationMedia: Ubuntu-Studio 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.1) SourcePackage: util-linux UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.cron.weekly.fstrim: 2014-09-21T13:07:51.420447 ** Affects: util-linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1720541 Title: flock does not lock dpkg lock file properly Status in util-linux package in Ubuntu: New Bug description: Test: sudo flock /var/lib/dpkg/lock -c \ 'echo 1; apt-get -o Debug::NoLocking=true check; echo 2; apt-get check' Expected behavior: apt-get fails in stage 2. Workaround (needs moreutils package) sudo lckdo /var/lib/dpkg/lock /bin/sh -c \ 'echo 1; apt-get -o Debug::NoLocking=true check; echo 2; apt-get check' Similarly, flock does not recognize lock set by e.g. apt-get. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: util-linux 2.20.1-5.1ubuntu20.9 ProcVersionSignature: Ubuntu 4.4.0-96.119~14.04.1-generic 4.4.83 Uname: Linux 4.4.0-96-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.25 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Sep 30 16:30:50 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2014-09-21 (1105 days ago) InstallationMedia: Ubuntu-Studio 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.1) SourcePackage: util-linux UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.cron.weekly.fstrim: 2014-09-21T13:07:51.420447 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1720541/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1667963] Re: QuiteRSS AppArmor profile
I have removed the proposal for merging, as I want to check the profile with KDE 5 on Kubuntu 17.04. I am removing also the patch tag as suggested by the bot, because it is not a patch to anything available already in the repository. ** Tags removed: patch ** Changed in: apparmor (Ubuntu) Assignee: (unassigned) => Raúl Vidal (raulvior-bcn) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1667963 Title: QuiteRSS AppArmor profile Status in apparmor package in Ubuntu: New Bug description: Test plan: 1. Boot application. 2. Add feed 3. Update feeds 4. Read some feed. 5. Open link in external browser. 6. Click to view page inside QuiteRSS. 7. Export feeds. 8. Go to preferences, change something. 9. Hide window (minimize it) 9. Use notification area menu to show update feeds, show window. 10. Close application. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1667963/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1720519] Re: Module "module-switch-on-connect" should be loaded once at most. Refusing to load.
fixed myself by reinstalling pulseaudio ** Changed in: pulseaudio (Ubuntu) Assignee: (unassigned) => ben van 't ende (benvantende) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1720519 Title: Module "module-switch-on-connect" should be loaded once at most. Refusing to load. Status in pulseaudio package in Ubuntu: New Bug description: Pulseaudio daemon does not start after the update to Kubuntu 17.10 beta2, because the module fails to load although it is there. From 'pulseaudio -vv' E: [pulseaudio] module.c: Module "module-switch-on-connect" should be loaded once at most. Refusing to load. E: [pulseaudio] main.c: Module load failed. E: [pulseaudio] main.c: Failed to initialize daemon. PS sorry I am not a seasoned bug reporter. Let me know if I can provide more info. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: pulseaudio 1:10.0-2ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: ben2809 F...m chrome /dev/snd/controlC0: ben2809 F chrome /dev/snd/timer: ben2809 f chrome CurrentDesktop: KDE Date: Sat Sep 30 11:20:55 2017 InstallationDate: Installed on 2017-04-07 (175 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: Upgraded to artful on 2017-09-30 (0 days ago) dmi.bios.date: 10/29/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: B150M-ITX 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.10:bd10/29/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB150M-ITX: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/1720519/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1720519] Re: Module "module-switch-on-connect" should be loaded once at most. Refusing to load.
Heyla, After reading up some more I removed alsa and pulseaudio and reinstalled like this: sudo apt-get remove --purge alsa-base pulseaudio Now install again Alsa and Pulse Audio: sudo apt-get install alsa-base pulseaudio Then, reload Alsa: sudo alsa force-reload That made audio up and running again! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1720519 Title: Module "module-switch-on-connect" should be loaded once at most. Refusing to load. Status in pulseaudio package in Ubuntu: New Bug description: Pulseaudio daemon does not start after the update to Kubuntu 17.10 beta2, because the module fails to load although it is there. From 'pulseaudio -vv' E: [pulseaudio] module.c: Module "module-switch-on-connect" should be loaded once at most. Refusing to load. E: [pulseaudio] main.c: Module load failed. E: [pulseaudio] main.c: Failed to initialize daemon. PS sorry I am not a seasoned bug reporter. Let me know if I can provide more info. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: pulseaudio 1:10.0-2ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: ben2809 F...m chrome /dev/snd/controlC0: ben2809 F chrome /dev/snd/timer: ben2809 f chrome CurrentDesktop: KDE Date: Sat Sep 30 11:20:55 2017 InstallationDate: Installed on 2017-04-07 (175 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: Upgraded to artful on 2017-09-30 (0 days ago) dmi.bios.date: 10/29/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: B150M-ITX 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.10:bd10/29/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB150M-ITX: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/1720519/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1706939] Re: A live session can't be shut down due to "[ *** ] (2 of 2) A start job is running for ... (21s / no limit)"
On 09/30/2017 04:40 AM, JimmyL wrote: > I have this bug too. If it helps I have test a clean Beta 2 install > twice and it doesnt hang on shutdown until the nvidia driver is > installed then the bug occurs on every instance of a shutdown. It > occurs on ubuntu desktop and kubuntu and in both instances only on > nvidia install. Interestingly it did not happen at all on earlier > beta/alpha releases. > Jimmy, this bug is only about a live session, the issue after install concerning nvidia drivers is something else. For those with hybrid (optimus) devices this check this bug https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1715746 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1706939 Title: A live session can't be shut down due to "[ *** ] (2 of 2) A start job is running for ... (21s / no limit)" Status in gdm3 package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: Test case: Boot to live session using current or recent image Attempt to restart, shutdown or even log out. Hangs basically forever with: [ *** ] (2 of 2) A start job is running for Hold until boot process finishes up (21s / no limit) or [ *** ] (2 of 2) A start job is running for Wait for Network to be Configured (21s / no limit) --- ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gdm3 3.24.2-1ubuntu9 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 ApportVersion: 2.20.6-0ubuntu4 Architecture: amd64 CasperVersion: 1.384 CurrentDesktop: GNOME Date: Thu Jul 27 10:15:57 2017 LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170723) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.custom.conf: 2017-07-27T10:13:04.127685 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1706939/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1720133] Re: USB 3.0 displays are black on Ubuntu after x.org update to 1.18.3 or newer
Same result on Ubuntu 17.10 - black screen with cursor on USB monitor running on displaylink driver as mentioned above. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1720133 Title: USB 3.0 displays are black on Ubuntu after x.org update to 1.18.3 or newer Status in xorg package in Ubuntu: Confirmed Bug description: [Impact] * This impacts all Ubuntu releases which received an update of x.org to 1.18.3 or newer, i.e. Ubuntu 16.04, 16.10, 17.04 & 17.10 * End users are unable to use their USB displays unless they workaround the problem which currently involves disabling pageflip for modesetting in x.org.conf file * The fix which has been submitted to x.org extends blacklisting mechanism so the EVDI kernel module which is essential for DisplayLink USB 3.0 devices to work is correctly recognised by x.org. Then the PRIME sync is disabled in such case; The patch can be found here: https://cgit.freedesktop.org/xorg/xserver/commit/?id=fbd80b2c8ebe9fd41229dc5438524d107c071ff1 [Test Case] 1. On a PC device with Ubuntu install DisplayLink SW for Ubuntu v1.3.54 downloaded from http://www.displaylink.com/downloads/ubuntu. Detailed requirements and instructions can be found here: 2. Plug in a DisplayLink USB 3.0 compatible device, e.g. Dell D3100 docking station 3. Plug in an external monitor (HDMI or DisplayPort) to the docking station Expected result: The external monitor should light up and show the desktop Actual result: The monitor remains black or shows frozen desktop. [Regression Potential] * The patchset extends number of modules for which x.org changes its functionality. It checks if "evdi" string is in the syspath so it is quite unlikely there would be any impact on anything else then USB 3.0 displays which use EVDI module. [Other Info] * The patch has been applied to Ubuntu x.org source code built and tested. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1720133/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1720133] Re: USB 3.0 displays are black on Ubuntu after x.org update to 1.18.3 or newer
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xorg (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1720133 Title: USB 3.0 displays are black on Ubuntu after x.org update to 1.18.3 or newer Status in xorg package in Ubuntu: Confirmed Bug description: [Impact] * This impacts all Ubuntu releases which received an update of x.org to 1.18.3 or newer, i.e. Ubuntu 16.04, 16.10, 17.04 & 17.10 * End users are unable to use their USB displays unless they workaround the problem which currently involves disabling pageflip for modesetting in x.org.conf file * The fix which has been submitted to x.org extends blacklisting mechanism so the EVDI kernel module which is essential for DisplayLink USB 3.0 devices to work is correctly recognised by x.org. Then the PRIME sync is disabled in such case; The patch can be found here: https://cgit.freedesktop.org/xorg/xserver/commit/?id=fbd80b2c8ebe9fd41229dc5438524d107c071ff1 [Test Case] 1. On a PC device with Ubuntu install DisplayLink SW for Ubuntu v1.3.54 downloaded from http://www.displaylink.com/downloads/ubuntu. Detailed requirements and instructions can be found here: 2. Plug in a DisplayLink USB 3.0 compatible device, e.g. Dell D3100 docking station 3. Plug in an external monitor (HDMI or DisplayPort) to the docking station Expected result: The external monitor should light up and show the desktop Actual result: The monitor remains black or shows frozen desktop. [Regression Potential] * The patchset extends number of modules for which x.org changes its functionality. It checks if "evdi" string is in the syspath so it is quite unlikely there would be any impact on anything else then USB 3.0 displays which use EVDI module. [Other Info] * The patch has been applied to Ubuntu x.org source code built and tested. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1720133/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1717714] Re: @{pid} variable broken on systems with pid_max more than 6 digits
** Branch linked: lp:~talkless/apparmor/seven_digit_pid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1717714
Title:
@{pid} variable broken on systems with pid_max more than 6 digits
Status in AppArmor:
New
Status in apparmor package in Ubuntu:
New
Bug description:
If your kernel.pid_max sysctl is set higher than the default, say at 7
digits, the @{pid} variable no longer matches all pids, causing some
breakage in any profile using it.
@{pid} is defined in /etc/apparmor.d/tunables:
@{pid}={[1-9],[1-9][0-9],[1-9][0-9][0-9],[1-9][0-9][0-9][0-9],[1-9][0-9][0-9][0-9][0-9],[1-9][0-9][0-9][0-9][0-9][0-9]}
It only covers up to 6 digits.
This Ubuntu 17.04 system has:
kernel.pid_max = 4194303
And is showing
type=1400 audit(1505588857.828:792): apparmor="DENIED" operation="open"
profile="libvirt-55e9e12c-e6dc-4f56-a547-8514cf7d9bf3"
name="/proc/2168180/task/2769256/comm" pid=2168180 comm="qemu-system-x86"
requested_mask="wr" denied_mask="wr" fsuid=111 ouid=111
Which should be matched by
@{PROC}/sys/vm/overcommit_memory r,
in /etc/apparmor.d/abstractions/libvirt-qemu
I'm seeing similar failures on 16.04 (2.10.95-0ubuntu2.7), 17.04
(2.11.0-2ubuntu4) and 17.10 (2.11.0-2ubuntu17)
I am aware this is a non-default configuration, but I think this
should work.
To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1717714/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1717714] Re: @{pid} variable broken on systems with pid_max more than 6 digits
OK, so if http://man7.org/linux/man-pages/man5/proc.5.html says:
```
On 64-bit systems, pid_max can be set to any value up to 2^22 (PID_MAX_LIMIT,
approximately 4 million).
``
Its 4194304, so I will propose adding one more bulk of expressions for
seven-digit PID, stating with [1-4].
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1717714
Title:
@{pid} variable broken on systems with pid_max more than 6 digits
Status in AppArmor:
New
Status in apparmor package in Ubuntu:
New
Bug description:
If your kernel.pid_max sysctl is set higher than the default, say at 7
digits, the @{pid} variable no longer matches all pids, causing some
breakage in any profile using it.
@{pid} is defined in /etc/apparmor.d/tunables:
@{pid}={[1-9],[1-9][0-9],[1-9][0-9][0-9],[1-9][0-9][0-9][0-9],[1-9][0-9][0-9][0-9][0-9],[1-9][0-9][0-9][0-9][0-9][0-9]}
It only covers up to 6 digits.
This Ubuntu 17.04 system has:
kernel.pid_max = 4194303
And is showing
type=1400 audit(1505588857.828:792): apparmor="DENIED" operation="open"
profile="libvirt-55e9e12c-e6dc-4f56-a547-8514cf7d9bf3"
name="/proc/2168180/task/2769256/comm" pid=2168180 comm="qemu-system-x86"
requested_mask="wr" denied_mask="wr" fsuid=111 ouid=111
Which should be matched by
@{PROC}/sys/vm/overcommit_memory r,
in /etc/apparmor.d/abstractions/libvirt-qemu
I'm seeing similar failures on 16.04 (2.10.95-0ubuntu2.7), 17.04
(2.11.0-2ubuntu4) and 17.10 (2.11.0-2ubuntu17)
I am aware this is a non-default configuration, but I think this
should work.
To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1717714/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1720530] Re: gdebi-kde crashed with ModuleNotFoundError in /usr/lib/python3/dist-packages/PyKDE4/__init__.py: No module named 'DLFCN'
*** This bug is a duplicate of bug 1708947 *** https://bugs.launchpad.net/bugs/1708947 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 #1708947, 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. ** Tags removed: need-duplicate-check ** Changed in: gdebi (Ubuntu) Importance: Undecided => Medium ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1720530/+attachment/4959295/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1720530/+attachment/4959296/+files/ProcStatus.txt ** This bug has been marked a duplicate of private bug 1708947 ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdebi in Ubuntu. https://bugs.launchpad.net/bugs/1720530 Title: gdebi-kde crashed with ModuleNotFoundError in /usr/lib/python3/dist- packages/PyKDE4/__init__.py: No module named 'DLFCN' Status in gdebi package in Ubuntu: New Bug description: i can not install program with Gdebi... ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gdebi-kde 0.9.5.7+nmu1ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Sat Sep 30 15:03:24 2017 ExecutablePath: /usr/share/gdebi/gdebi-kde InstallationDate: Installed on 2017-09-30 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) InterpreterPath: /usr/bin/python3.6 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/bin/gdebi-kde Python3Details: /usr/bin/python3.6, Python 3.6.3rc1, python3-minimal, 3.6.2-1ubuntu4 PythonArgs: ['/usr/bin/gdebi-kde'] PythonDetails: /home/bahram/Error: command ['which', 'python'] failed with exit code 1:, Error: [Errno 2] No such file or directory: "/home/bahram/Error: command ['which', 'python'] failed with exit code 1:": "/home/bahram/Error: command ['which', 'python'] failed with exit code 1:", unpackaged SourcePackage: gdebi Title: gdebi-kde crashed with ModuleNotFoundError in /usr/lib/python3/dist-packages/PyKDE4/__init__.py: No module named 'DLFCN' 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/gdebi/+bug/1720530/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1720528] Re: package libglib2.0-dev 2.48.2-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 3
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1720528 Title: package libglib2.0-dev 2.48.2-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 3 Status in glib2.0 package in Ubuntu: New Bug description: It crashed on ubuntu 16.04.03 LTS with Python 2.7 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libglib2.0-dev 2.48.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-35-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Sat Sep 30 18:18:36 2017 DpkgTerminalLog: Setting up libglib2.0-dev (2.48.2-0ubuntu1) ... E: pycompile:233: Requested versions are not installed dpkg: error processing package libglib2.0-dev (--configure): subprocess installed post-installation script returned error exit status 3 DuplicateSignature: package:libglib2.0-dev:2.48.2-0ubuntu1 Setting up libglib2.0-dev (2.48.2-0ubuntu1) ... E: pycompile:233: Requested versions are not installed dpkg: error processing package libglib2.0-dev (--configure): subprocess installed post-installation script returned error exit status 3 ErrorMessage: subprocess installed post-installation script returned error exit status 3 InstallationDate: Installed on 2017-08-26 (35 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.24 SourcePackage: glib2.0 Title: package libglib2.0-dev 2.48.2-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1720528/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1720529] [NEW] ~/dmesg and your /var/log/Xorg.0.log.
Public bug reported: i am unable to use my wireless mouse ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-96.119-generic 4.4.83 Uname: Linux 4.4.0-96-generic x86_64 NonfreeKernelModules: wl .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 BootLog: Scanning for Btrfs filesystems UBUNTU: clean, 275992/60309504 files, 5656499/241220352 blocks CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sat Sep 30 16:46:23 2017 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0792] InstallationDate: Installed on 2017-08-08 (53 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 138a:0010 Validity Sensors, Inc. VFS Fingerprint sensor Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Vostro 14-3468 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-96-generic.efi.signed root=UUID=de326c40-9285-4350-b59e-15e9b09834cb ro acpi_rev_override quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/23/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.08.00 dmi.board.name: 0T1X3V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.08.00:bd03/23/2017:svnDellInc.:pnVostro14-3468:pvr:rvnDellInc.:rn0T1X3V:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Vostro 14-3468 dmi.sys.vendor: Dell Inc. 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.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.4 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: Sat Sep 30 16:33:28 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1767 vendor BOE xserver.version: 2:1.18.4-0ubuntu0.4 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1720529 Title: ~/dmesg and your /var/log/Xorg.0.log. Status in xorg package in Ubuntu: New Bug description: i am unable to use my wireless mouse ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-96.119-generic 4.4.83 Uname: Linux 4.4.0-96-generic x86_64 NonfreeKernelModules: wl .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 BootLog: Scanning for Btrfs filesystems UBUNTU: clean, 275992/60309504 files, 5656499/241220352 blocks CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sat Sep 30 16:46:23 2017 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0792] InstallationDate: Installed on 2017-08-08 (53 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 Lsusb: Bus 002 Device 001:
[Touch-packages] [Bug 1720528] [NEW] package libglib2.0-dev 2.48.2-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 3
Public bug reported: It crashed on ubuntu 16.04.03 LTS with Python 2.7 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libglib2.0-dev 2.48.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-35-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Sat Sep 30 18:18:36 2017 DpkgTerminalLog: Setting up libglib2.0-dev (2.48.2-0ubuntu1) ... E: pycompile:233: Requested versions are not installed dpkg: error processing package libglib2.0-dev (--configure): subprocess installed post-installation script returned error exit status 3 DuplicateSignature: package:libglib2.0-dev:2.48.2-0ubuntu1 Setting up libglib2.0-dev (2.48.2-0ubuntu1) ... E: pycompile:233: Requested versions are not installed dpkg: error processing package libglib2.0-dev (--configure): subprocess installed post-installation script returned error exit status 3 ErrorMessage: subprocess installed post-installation script returned error exit status 3 InstallationDate: Installed on 2017-08-26 (35 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.24 SourcePackage: glib2.0 Title: package libglib2.0-dev 2.48.2-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 3 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: glib2.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package need-duplicate-check xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1720528 Title: package libglib2.0-dev 2.48.2-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 3 Status in glib2.0 package in Ubuntu: New Bug description: It crashed on ubuntu 16.04.03 LTS with Python 2.7 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libglib2.0-dev 2.48.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-35-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Sat Sep 30 18:18:36 2017 DpkgTerminalLog: Setting up libglib2.0-dev (2.48.2-0ubuntu1) ... E: pycompile:233: Requested versions are not installed dpkg: error processing package libglib2.0-dev (--configure): subprocess installed post-installation script returned error exit status 3 DuplicateSignature: package:libglib2.0-dev:2.48.2-0ubuntu1 Setting up libglib2.0-dev (2.48.2-0ubuntu1) ... E: pycompile:233: Requested versions are not installed dpkg: error processing package libglib2.0-dev (--configure): subprocess installed post-installation script returned error exit status 3 ErrorMessage: subprocess installed post-installation script returned error exit status 3 InstallationDate: Installed on 2017-08-26 (35 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.24 SourcePackage: glib2.0 Title: package libglib2.0-dev 2.48.2-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1720528/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1720526] Re: systemd-udevd crashed with SIGABRT in __libc_open64()
*** This bug is a duplicate of bug 1715782 *** https://bugs.launchpad.net/bugs/1715782 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 #1715782, 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/1720526/+attachment/4959237/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1720526/+attachment/4959240/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1720526/+attachment/4959248/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1720526/+attachment/4959250/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1720526/+attachment/4959251/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1720526/+attachment/4959252/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1720526/+attachment/4959253/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1715782 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1720526 Title: systemd-udevd crashed with SIGABRT in __libc_open64() Status in systemd package in Ubuntu: New Bug description: none ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: udev 234-2ubuntu11 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CrashCounter: 1 CustomUdevRuleFiles: ft-rockey.rules Date: Sat Sep 30 12:29:56 2017 ExecutablePath: /lib/systemd/systemd-udevd MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcCmdline: /lib/systemd/systemd-udevd ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-12-generic root=UUID=bdd1754a-b8b4-4d5c-bdad-2275569c1c25 ro rhgb plymouth:debug drm.debug=0xe Signal: 6 SourcePackage: systemd StacktraceTop: __libc_open64 (file=0x55ada1697b20 "/dev/sdj", oflag=657408) at ../sysdeps/unix/sysv/linux/open64.c:46 ?? () ?? () ?? () ?? () Title: systemd-udevd crashed with SIGABRT in __libc_open64() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 12/24/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: F2A88X-D3HP dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x 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.:bvrF2:bd12/24/2015:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A88X-D3HP:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.: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: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1720526/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1717995] Re: extra domains not removed from resolv.conf when VPN disconnects
I'm experiencing this same issue. A workaround that works for me is to remove my vpn domain from /etc/resolv.conf. The last line of this file looks as follows after a successful VPN connection: search Home myvpndomain where the last term is the domain of my vpn (vpn.bla.com). The workaround is to remove it and leave: search Home then restart the network-manager service and the VPN reconnects. Otherwise I have to restart the computer to be able to connect to the VPN after a successful connection. I mean: after a computer restart, VPN always connects, but if I disconnect I cannot reconnect to the VPN unless I restart the computer or do the workaround. I have a big confusion on how /etc/resolv.conf is managed nowadays in Ubuntu. I have at least three different system processes generating a resolv.conf. systemd-resolved: /run/systemd/resolve/resolv.conf network-manager: /run/NetworkManager/resolv.conf and resolvconf: /run/resolvconf/resolv.conf My actual /etc/resolv.conf is a symbolic link to this last one. At some point I tried to have only network-manager manage /etc/resolv.conf. Everything works fine, but when I connect to VPN it can't resolve any DNS outside of the private network. The resolv.conf generated by systemd-resolved has the same problem as the one generated by resolvconf, when the VPN reconnects the VPN domain is not removed from the "search" line. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1717995 Title: extra domains not removed from resolv.conf when VPN disconnects Status in systemd package in Ubuntu: In Progress Bug description: I use a VPN (network manager "vpnc" config) to connect to my work network. The gateway is "webvpn.purestorage.com". When I connect, I get "purestorage.com" added to the "search" line in my /etc/resolv.conf (and /run/resolvconf/interface/systemd-resolved) - which makes perfect sense, the VPN passes this info to me and then I can connect to systems within the work network without having to use a FQDN. The bug (which is a regression from older versions of Ubuntu) is that when I lose my connection to the VPN (either because I disconnect explicitly, or because the network goes down or I suspend my laptop), the "purestorage.com" domain is not removed from those "search" lines. And for some reason this prevents me from resolving webvpn.purestorage.com (which prevents me from reconnecting to the VPN). In particular, if I connect and disconnect my VPN, I get: $ systemd-resolve webvpn.purestorage.com webvpn.purestorage.com: resolve call failed: No appropriate name servers or networks for name found If I then edit /etc/resolv.conf by hand to remove all the purestorage.com entries from the search line - in other words, change $ cat /etc/resolv.conf # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN # 127.0.0.53 is the systemd-resolved stub resolver. # run "systemd-resolve --status" to see details about the actual nameservers. nameserver 127.0.0.53 search home.digitalvampire.org purestorage.com dev.purestorage.com to $ cat /etc/resolv.conf # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN # 127.0.0.53 is the systemd-resolved stub resolver. # run "systemd-resolve --status" to see details about the actual nameservers. nameserver 127.0.0.53 search home.digitalvampire.org and change nothing else, then: $ systemd-resolve webvpn.purestorage.com webvpn.purestorage.com: 192.30.189.1 (vpn.purestorage.com) -- Information acquired via protocol DNS in 25.9ms. -- Data is authenticated: no I'm not sure if the bug is in systemd, network manager, or some other package, but I'm happy to try any debugging that is helpful to resolve this (no pun intended). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: systemd 234-2ubuntu10 ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10 Uname: Linux 4.12.0-13-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Sep 18 11:20:17 2017 InstallationDate: Installed on 2016-09-01 (381 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160901) MachineType: LENOVO 20FRS2FK00 ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-13-generic root=UUID=30d5ada5-835d-4cf7-96cf-3329c0316107 ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to artful on 2017-07-26 (53 days ago) dmi.bios.date: 07/13/2017 dmi.bios.vendor: LENOVO dmi.bios.version: N1FET5
[Touch-packages] [Bug 1720525] [NEW] Update package to newer version
Public bug reported: In Artful (and older releases) the version of the package is 0.4.7 even though 0.7.0 is already out. Debian Buster and Sid has 0.7.0 in the repos. The changes are bug fixes and features (see http://python-evdev.readthedocs.io/en/latest/changelog.html). ** Affects: python-evdev (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-evdev in Ubuntu. https://bugs.launchpad.net/bugs/1720525 Title: Update package to newer version Status in python-evdev package in Ubuntu: New Bug description: In Artful (and older releases) the version of the package is 0.4.7 even though 0.7.0 is already out. Debian Buster and Sid has 0.7.0 in the repos. The changes are bug fixes and features (see http://python-evdev.readthedocs.io/en/latest/changelog.html). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-evdev/+bug/1720525/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1720519] [NEW] Module "module-switch-on-connect" should be loaded once at most. Refusing to load.
Public bug reported: Pulseaudio daemon does not start after the update to Kubuntu 17.10 beta2, because the module fails to load although it is there. >From 'pulseaudio -vv' E: [pulseaudio] module.c: Module "module-switch-on-connect" should be loaded once at most. Refusing to load. E: [pulseaudio] main.c: Module load failed. E: [pulseaudio] main.c: Failed to initialize daemon. PS sorry I am not a seasoned bug reporter. Let me know if I can provide more info. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: pulseaudio 1:10.0-2ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: ben2809 F...m chrome /dev/snd/controlC0: ben2809 F chrome /dev/snd/timer: ben2809 f chrome CurrentDesktop: KDE Date: Sat Sep 30 11:20:55 2017 InstallationDate: Installed on 2017-04-07 (175 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: Upgraded to artful on 2017-09-30 (0 days ago) dmi.bios.date: 10/29/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: B150M-ITX 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.10:bd10/29/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB150M-ITX: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. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1720519 Title: Module "module-switch-on-connect" should be loaded once at most. Refusing to load. Status in pulseaudio package in Ubuntu: New Bug description: Pulseaudio daemon does not start after the update to Kubuntu 17.10 beta2, because the module fails to load although it is there. From 'pulseaudio -vv' E: [pulseaudio] module.c: Module "module-switch-on-connect" should be loaded once at most. Refusing to load. E: [pulseaudio] main.c: Module load failed. E: [pulseaudio] main.c: Failed to initialize daemon. PS sorry I am not a seasoned bug reporter. Let me know if I can provide more info. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: pulseaudio 1:10.0-2ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: ben2809 F...m chrome /dev/snd/controlC0: ben2809 F chrome /dev/snd/timer: ben2809 f chrome CurrentDesktop: KDE Date: Sat Sep 30 11:20:55 2017 InstallationDate: Installed on 2017-04-07 (175 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: Upgraded to artful on 2017-09-30 (0 days ago) dmi.bios.date: 10/29/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: B150M-ITX 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.10:bd10/29/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB150M-ITX: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/1720519/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1720517] [NEW] Software and Updates /Other Software greys out when clicking on "Canonical Partners"
Public bug reported: "Other Software" only works after having clicked on "Ubuntu Software", "Updates", etc and changing some settings on those pages. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: software-properties-gtk 0.96.24.16 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Sep 30 10:44:47 2017 EcryptfsInUse: Yes ExecutablePath: /usr/bin/software-properties-gtk InstallationDate: Installed on 2017-09-29 (0 days ago) InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 (20170919) InterpreterPath: /usr/bin/python3.6 PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash Python3Details: /usr/bin/python3.6, Python 3.6.3rc1, python3-minimal, 3.6.2-1ubuntu4 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1720517 Title: Software and Updates /Other Software greys out when clicking on "Canonical Partners" Status in software-properties package in Ubuntu: New Bug description: "Other Software" only works after having clicked on "Ubuntu Software", "Updates", etc and changing some settings on those pages. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: software-properties-gtk 0.96.24.16 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Sep 30 10:44:47 2017 EcryptfsInUse: Yes ExecutablePath: /usr/bin/software-properties-gtk InstallationDate: Installed on 2017-09-29 (0 days ago) InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 (20170919) InterpreterPath: /usr/bin/python3.6 PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash Python3Details: /usr/bin/python3.6, Python 3.6.3rc1, python3-minimal, 3.6.2-1ubuntu4 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1720517/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1706939] Re: A live session can't be shut down due to "[ *** ] (2 of 2) A start job is running for ... (21s / no limit)"
My bug is only on shutdown "a stop job and relates to 1 of 2 ..network-manager and 2 of 2 ...WPA -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1706939 Title: A live session can't be shut down due to "[ *** ] (2 of 2) A start job is running for ... (21s / no limit)" Status in gdm3 package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: Test case: Boot to live session using current or recent image Attempt to restart, shutdown or even log out. Hangs basically forever with: [ *** ] (2 of 2) A start job is running for Hold until boot process finishes up (21s / no limit) or [ *** ] (2 of 2) A start job is running for Wait for Network to be Configured (21s / no limit) --- ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gdm3 3.24.2-1ubuntu9 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 ApportVersion: 2.20.6-0ubuntu4 Architecture: amd64 CasperVersion: 1.384 CurrentDesktop: GNOME Date: Thu Jul 27 10:15:57 2017 LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170723) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.custom.conf: 2017-07-27T10:13:04.127685 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1706939/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1706939] Re: A live session can't be shut down due to "[ *** ] (2 of 2) A start job is running for ... (21s / no limit)"
I have this bug too. If it helps I have test a clean Beta 2 install twice and it doesnt hang on shutdown until the nvidia driver is installed then the bug occurs on every instance of a shutdown. It occurs on ubuntu desktop and kubuntu and in both instances only on nvidia install. Interestingly it did not happen at all on earlier beta/alpha releases. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1706939 Title: A live session can't be shut down due to "[ *** ] (2 of 2) A start job is running for ... (21s / no limit)" Status in gdm3 package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: Test case: Boot to live session using current or recent image Attempt to restart, shutdown or even log out. Hangs basically forever with: [ *** ] (2 of 2) A start job is running for Hold until boot process finishes up (21s / no limit) or [ *** ] (2 of 2) A start job is running for Wait for Network to be Configured (21s / no limit) --- ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gdm3 3.24.2-1ubuntu9 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 ApportVersion: 2.20.6-0ubuntu4 Architecture: amd64 CasperVersion: 1.384 CurrentDesktop: GNOME Date: Thu Jul 27 10:15:57 2017 LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170723) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.custom.conf: 2017-07-27T10:13:04.127685 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1706939/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1586528] Re: Avahi-daemon withdraws address record
Graham, Unfortunately I'm not an expert with Network Manager, until now it remains a mystery to me how it works, where is the configuration stored and where there heck are the log files?!?. Nevertheless, if the "Network Manager" icon disappeared, you can run that "Network Connections" tool directly from "search your computer" (click on the ubuntu logo on the top left or press the "windows" key) and type "Network Connections". Alternatively you can run nm-connection-editor from the terminal. On ubuntu, it is part of package network-manager-gnome. Nir -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1586528 Title: Avahi-daemon withdraws address record Status in avahi package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: For some reason, if I leave my Ubuntu VM up for a prolonged period of time the machine will lose connection to the network. ip addr shows that the nic port no longer has an address and an examination of the syslog shows this: May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Withdrawing address record for 10.0.2.15 on enp0s3. May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Leaving mDNS multicast group on interface enp0s3.IPv4 with address 10.0.2.15. May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Interface enp0s3.IPv4 no longer relevant for mDNS. for no known reason. The only reliable way to get the network to come back (that I have found) is a full reboot. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: avahi-daemon 0.6.32~rc+dfsg-1ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Fri May 27 15:11:34 2016 InstallationDate: Installed on 2015-10-22 (218 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: avahi UpgradeStatus: Upgraded to xenial on 2016-03-30 (58 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1586528/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1544621] Re: When there is a broken dependency, apt-get is unable to purge/remove any other package than the one(s) that has broken dependency
** Changed in: apt (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1544621 Title: When there is a broken dependency, apt-get is unable to purge/remove any other package than the one(s) that has broken dependency Status in apt package in Ubuntu: Invalid Bug description: An example, when this bug is a problem, is when /boot becomes full during kernel update. A meta kernel package such as linux-image- generic becomes broken, but the suggested command "sudo apt-get -f install" can not fix the problem. Freeing space by removing an older kernel packages by "apt-get purge" does not work either. A workaround is to use "dpkg --purge", but couldn't purging work by apt-get, too? http://askubuntu.com/questions/635798/boot-partition-full-failing-to- delete-old-kernels-broken-packages/731791 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: apt 1.0.1ubuntu2.10 ProcVersionSignature: Ubuntu 3.13.0-77.121-lowlatency 3.13.11-ckt32 Uname: Linux 3.13.0-77-lowlatency x86_64 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Feb 11 11:36:06 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2014-09-21 (508 days ago) InstallationMedia: Ubuntu-Studio 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.1) SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.kernel.postinst.d.apt.auto.removal: 2016-02-03T01:46:24.317010 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1544621/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1678187] Re: Removing a linux-image-extra package fails, if /boot is about full
There is no bug with that number. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1678187 Title: Removing a linux-image-extra package fails, if /boot is about full Status in initramfs-tools: New Status in dpkg package in Ubuntu: Invalid Status in initramfs-tools package in Ubuntu: Confirmed Bug description: System calls /etc/kernel/postinst.d/initramfs-tools when purging/removing a linux-image-extra package. That calls "update- initramfs -c" which needs significant amount of additional disk space in /boot temporarily. But there is no space left, if /boot is full. Likewise /etc/kernel/postinst.d/dkms may call "update-initramfs -u". The fix could be to create the new initrg.img file in different partition before replacing the old one by it in update-initramfs. So the update-initramfs script should be fixed. But there may not be such a partition.. Anyway the likely case when space runs out is when there is a separate /boot partition. Alternatively the init scripts should remove the respective /boot/initrd.img- file when removing/installing the linux-image-extra package. That could also be done by update-initramfs -d -k That may be worse way, as then initrd.img file is missing for longer period of time and system integrity may suffer in case of e.g. power cut. Related question: http://askubuntu.com/q/898499/21005 The output of 'dpkg --purge' presented there shows that corresponding linux-image package may get successfully removed while the linux-image-extra is left broken. If the linux-image-extra package will be removed later, the post-installation script will create an initrd.img file for a non-installed kernel! Same would happen, if removing would be done by apt-get purge. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: initramfs-tools 0.103ubuntu4.7 ProcVersionSignature: Ubuntu 4.4.0-71.92~14.04.1-generic 4.4.49 Uname: Linux 4.4.0-71-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Mar 31 17:42:35 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2014-09-21 (922 days ago) InstallationMedia: Ubuntu-Studio 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.1) PackageArchitecture: all SourcePackage: initramfs-tools UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/initramfs-tools/+bug/1678187/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
