[Touch-packages] [Bug 1392317] Re: Incorrect order of messages with RepeatedMsgReduction on
** Tags added: canonical-is -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/1392317 Title: Incorrect order of messages with RepeatedMsgReduction on Status in rsyslog package in Ubuntu: Confirmed Bug description: In rsyslog Version 7.4.4-1ubuntu2.3 there is a bug which mixes up the order of some messages when $RepeatedMsgReduction is enabled. This can sometimes result in a message missing in the current syslog and being printed even days later. Using Ubuntu 14.04.1 LTS. […] Nov 12 16:32:01 ws-api3 CRON[5572]: pam_unix(cron:session): session closed for user www-data Nov 12 16:33:01 ws-api3 CRON[5582]: pam_unix(cron:session): session opened for user www-data by (uid=0) Nov 10 11:56:01 ws-api3 CRON[5583]: (www-data) CMD (nice -n10 php /var/www/api/scripts/import/php/import.php all^I>> $CL/import.log 2>> $PL/api_cli_er rlog) Nov 12 16:33:01 ws-api3 CRON[5583]: (www-data) CMD (nice -n10 php /var/www/api/scripts/import/php/import.php all^I>> $CL/dev_import.log 2>> $PL/dev_ap i_cli_errlog) Nov 12 16:33:01 ws-api3 CRON[5582]: pam_unix(cron:session): session closed for user www-data […] To reproduce this error, turn on $RepeatedMsgReduction in the rsyslog.conf and generate a whole bunch of syslog message, e.g. with the following php script: $k'"); } } Result will be (after a short while): Nov 12 11:17:08 syslogTest vm[21410]: log > 0 Nov 12 11:18:05 syslogTest vm[21410]: log > 1 Nov 12 11:17:08 syslogTest vm[21412]: log > 0 Nov 12 11:18:05 syslogTest vm[21412]: log > 1 Nov 12 11:17:08 syslogTest vm[21414]: log > 0 Nov 12 11:18:05 syslogTest vm[21414]: log > 1 What's pretty suspicious is that after the pool of process IDs is exhausted and resettet, old messages are from the same process ID but from the previous iteration. Is RepeatedMsgReduction somehow grouping by process ID? In the first example is a cron process using the same process ID like one before, therefore printing the old message from Nov, 10. The old message was not at the position inside the syslog where it should have been. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1392317/+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 1625667] Update Released
The verification of the Stable Release Update for apt has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/1625667 Title: Trusty: apt does not try next mirror if index file download fails with mirror:// source Status in apt package in Ubuntu: Fix Released Status in apt source package in Trusty: Fix Released Bug description: [SRU justification] This fix is needed to allow correct archive mirroring functionality. [Impact] Without this fix, apt-get update and other apt commands requiring Package file access may fail when there are remote transient errors due to archive availability. [Fix] Use std::npos instead of 0 to test presence of "Translation" in ShortDesc. [Test Case] 1) Setup three containers (archive1, archive2, archive3) with a reprepro configuration mirroring the ubuntu restricted archive (to save on space and time to replicate). 2) Add an apache webserver serving the reprepro archive over http on each container 3) Add the following mirrors.txt file to one of the webserver (archive1): $ cat /var/www/html/mirrors.txt http://archive1/ubuntu/ http://archive2/ubuntu/ http://archive3/ubuntu/ 4) Add a client container. Add the IP adresses of the archive[1-3] containers to /etc/hosts. Alias the archive1 address to archive.ubuntu.com similar to the following : $ cat /etc/hosts 127.0.0.1 localhost 10.0.4.182 archive1mirrors.ubuntu.com 10.0.4.127 archive2 10.0.4.193 archive3 5) Add the following line to the /etc/apt/sources.list, commenting all other entries : $ cat /etc/apt/sources.list #deb http://archive.ubuntu.com/ubuntu trusty main #deb http://archive.ubuntu.com/ubuntu trusty-updates main #deb http://archive.ubuntu.com/ubuntu trusty universe #deb http://archive.ubuntu.com/ubuntu trusty-updates universe deb mirror://mirrors.ubuntu.com/mirrors.txt trusty restricted 6) Run $ apt-get -oDebug::Acquire::mirror=true update The log should display for the Packages file : MirrorMethod::Fetch() Failure to get http://10.0.4.193/ubuntu//dists/trusty/restricted/binary-amd64/Packages Err http://10.0.4.193/ubuntu/ trusty/restricted amd64 Packages With the fix you will see : MirrorMethod::Fetch() Failure to get http://10.0.4.193/ubuntu//dists/trusty/restricted/binary-amd64/Packages.gz TryNextMirror: http://10.0.4.127/ubuntu//dists/trusty/restricted/binary-amd64/Packages.gz [Regression] None expected. Worse that can happen is a retry when none was done previously. [Original description of the problem] When using the mirror://mirrors.ubuntu.com/mirrors.txt functionality on Trusty, if the download of the index file fails, apt will not retry on another archive listed in mirrors.txt and will fail. Running the following on Trusty leads to the following result : sudo apt-get update -qq W: Failed to fetch mirror://mirrors.ubuntu.com/mirrors.txt/dists/trusty-security/universe/binary-amd64/Packages 404 Not Found [Mirror: http://ftp.availo.se/ubuntu/] W: Failed to fetch mirror://mirrors.ubuntu.com/mirrors.txt/dists/trusty-security/main/binary-i386/Packages 404 Not Found [Mirror: http://ftp.availo.se/ubuntu/] W: Failed to fetch mirror://mirrors.ubuntu.com/mirrors.txt/dists/trusty-security/restricted/binary-i386/Packages 404 Not Found [Mirror: http://ftp.availo.se/ubuntu/] W: Failed to fetch mirror://mirrors.ubuntu.com/mirrors.txt/dists/trusty-security/universe/binary-i386/Packages 404 Not Found [Mirror: http://ftp.availo.se/ubuntu/] W: Failed to fetch mirror://mirrors.ubuntu.com/mirrors.txt/dists/trusty-updates/main/binary-amd64/Packages 404 Not Found [Mirror: http://ftp.availo.se/ubuntu/] W: Failed to fetch mirror://mirrors.ubuntu.com/mirrors.txt/dists/trusty-updates/restricted/binary-amd64/Packages 404 Not Found [Mirror: http://ftp.availo.se/ubuntu/] W: Failed to fetch mirror://mirrors.ubuntu.com/mirrors.txt/dists/trusty-updates/universe/binary-amd64/Packages 404 Not Found [Mirror: http://ftp.availo.se/ubuntu/] W: Failed to fetch mirror://mirrors.ubuntu.com/mirrors.txt/dists/trusty-updates/main/binary-i386/Packages 404 Not Found [Mirror: http://ftp.availo.se/ubuntu/] W: Failed to fetch mirror://mirrors.ubuntu.com/mirrors.txt/dists/trusty-updates/restricted/binary-i386/Packages 404 Not Found [Mirror: http://ftp.availo.se/ubuntu/] W: Failed to fetch mirror://mirrors.ubuntu.com/mirrors.txt/dists/trusty-updates/universe/binary-i386/Packages
[Touch-packages] [Bug 1625667] Re: Trusty: apt does not try next mirror if index file download fails with mirror:// source
This bug was fixed in the package apt - 1.0.1ubuntu2.15 --- apt (1.0.1ubuntu2.15) trusty; urgency=medium * Fixes failure to download the Package index file when using mirror:// URL in sources.list and the archive fails to profile a file. APT would try the next archive in the list for .deb packages but did not retry when the index file failed to download. (LP: #1625667) -- Louis BouchardTue, 20 Sep 2016 17:02:03 +0200 ** Changed in: apt (Ubuntu Trusty) Status: Fix Committed => Fix Released -- 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/1625667 Title: Trusty: apt does not try next mirror if index file download fails with mirror:// source Status in apt package in Ubuntu: Fix Released Status in apt source package in Trusty: Fix Released Bug description: [SRU justification] This fix is needed to allow correct archive mirroring functionality. [Impact] Without this fix, apt-get update and other apt commands requiring Package file access may fail when there are remote transient errors due to archive availability. [Fix] Use std::npos instead of 0 to test presence of "Translation" in ShortDesc. [Test Case] 1) Setup three containers (archive1, archive2, archive3) with a reprepro configuration mirroring the ubuntu restricted archive (to save on space and time to replicate). 2) Add an apache webserver serving the reprepro archive over http on each container 3) Add the following mirrors.txt file to one of the webserver (archive1): $ cat /var/www/html/mirrors.txt http://archive1/ubuntu/ http://archive2/ubuntu/ http://archive3/ubuntu/ 4) Add a client container. Add the IP adresses of the archive[1-3] containers to /etc/hosts. Alias the archive1 address to archive.ubuntu.com similar to the following : $ cat /etc/hosts 127.0.0.1 localhost 10.0.4.182 archive1mirrors.ubuntu.com 10.0.4.127 archive2 10.0.4.193 archive3 5) Add the following line to the /etc/apt/sources.list, commenting all other entries : $ cat /etc/apt/sources.list #deb http://archive.ubuntu.com/ubuntu trusty main #deb http://archive.ubuntu.com/ubuntu trusty-updates main #deb http://archive.ubuntu.com/ubuntu trusty universe #deb http://archive.ubuntu.com/ubuntu trusty-updates universe deb mirror://mirrors.ubuntu.com/mirrors.txt trusty restricted 6) Run $ apt-get -oDebug::Acquire::mirror=true update The log should display for the Packages file : MirrorMethod::Fetch() Failure to get http://10.0.4.193/ubuntu//dists/trusty/restricted/binary-amd64/Packages Err http://10.0.4.193/ubuntu/ trusty/restricted amd64 Packages With the fix you will see : MirrorMethod::Fetch() Failure to get http://10.0.4.193/ubuntu//dists/trusty/restricted/binary-amd64/Packages.gz TryNextMirror: http://10.0.4.127/ubuntu//dists/trusty/restricted/binary-amd64/Packages.gz [Regression] None expected. Worse that can happen is a retry when none was done previously. [Original description of the problem] When using the mirror://mirrors.ubuntu.com/mirrors.txt functionality on Trusty, if the download of the index file fails, apt will not retry on another archive listed in mirrors.txt and will fail. Running the following on Trusty leads to the following result : sudo apt-get update -qq W: Failed to fetch mirror://mirrors.ubuntu.com/mirrors.txt/dists/trusty-security/universe/binary-amd64/Packages 404 Not Found [Mirror: http://ftp.availo.se/ubuntu/] W: Failed to fetch mirror://mirrors.ubuntu.com/mirrors.txt/dists/trusty-security/main/binary-i386/Packages 404 Not Found [Mirror: http://ftp.availo.se/ubuntu/] W: Failed to fetch mirror://mirrors.ubuntu.com/mirrors.txt/dists/trusty-security/restricted/binary-i386/Packages 404 Not Found [Mirror: http://ftp.availo.se/ubuntu/] W: Failed to fetch mirror://mirrors.ubuntu.com/mirrors.txt/dists/trusty-security/universe/binary-i386/Packages 404 Not Found [Mirror: http://ftp.availo.se/ubuntu/] W: Failed to fetch mirror://mirrors.ubuntu.com/mirrors.txt/dists/trusty-updates/main/binary-amd64/Packages 404 Not Found [Mirror: http://ftp.availo.se/ubuntu/] W: Failed to fetch mirror://mirrors.ubuntu.com/mirrors.txt/dists/trusty-updates/restricted/binary-amd64/Packages 404 Not Found [Mirror: http://ftp.availo.se/ubuntu/] W: Failed to fetch mirror://mirrors.ubuntu.com/mirrors.txt/dists/trusty-updates/universe/binary-amd64/Packages 404 Not Found [Mirror: http://ftp.availo.se/ubuntu/] W: Failed to fetch mirror://mirrors.ubuntu.com/mirrors.txt/dists/trusty-updates/main/binary-i386/Packages 404 Not Found [Mirror: http://ftp.availo.se/ubuntu/] W: Failed to fetch mirror://mirrors.ubuntu.com/mirrors.txt/dists/trusty-updates/restricted/binary-i386/Packages 404 Not Found [Mirror: http://ftp.availo.se/ubuntu/] W:
[Touch-packages] [Bug 1499879] Re: [Day Scope] [German] Moonphase could not be read
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: unity8 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1499879 Title: [Day Scope] [German] Moonphase could not be read Status in Day Scope: Confirmed Status in Today Scope: Invalid Status in Ubuntu Translations: New Status in Ubuntu UX: Triaged Status in unity8 package in Ubuntu: Confirmed Bug description: Hello guys! I want to read information for the moon phase in TodayScope. Problem is that the displayed text is to long, so I can see first word but not the rest. I think it is really a good think with this information, thank you for this :-) I use a BQ Aquaris E4.5 with Ubuntu 15.04 r25 dashboard 1.9.2 I sent a screenshot To manage notifications about this bug go to: https://bugs.launchpad.net/day-scope/+bug/1499879/+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 1499879] Re: [Day Scope] [German] Moonphase could not be read
** Summary changed: - [Today Scope] Moonphase could not be read + [Day Scope] [German] Moonphase could not be read -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1499879 Title: [Day Scope] [German] Moonphase could not be read Status in Day Scope: Confirmed Status in Today Scope: Invalid Status in Ubuntu Translations: New Status in Ubuntu UX: Triaged Status in unity8 package in Ubuntu: Confirmed Bug description: Hello guys! I want to read information for the moon phase in TodayScope. Problem is that the displayed text is to long, so I can see first word but not the rest. I think it is really a good think with this information, thank you for this :-) I use a BQ Aquaris E4.5 with Ubuntu 15.04 r25 dashboard 1.9.2 I sent a screenshot To manage notifications about this bug go to: https://bugs.launchpad.net/day-scope/+bug/1499879/+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 541595] Re: [Master] package failed to install/upgrade: package is already installed and configured
Wtf is this? Huh? On May 24, 2013 9:12 AM, "Magdalena Shneider"wrote: > ** Changed in: apt-dpkg-ref (Ubuntu) > Assignee: dr arya s (aryakutabali) => Magdalena Shneider (magdash) > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1033719). > https://bugs.launchpad.net/bugs/541595 > > Title: > [Master] package failed to install/upgrade: package is already > installed and configured > > Status in dpkg: > New > Status in “apt-dpkg-ref” package in Ubuntu: > Fix Released > > Bug description: > Binary package hint: dpkg > > For yet unknown reasons packages fail to install with an error like: > > dpkg: error processing flashplugin-installer (--configure): >package flashplugin-installer is already installed and configured > > without further error. > This is a "one time" failure. Another run of the installation doesn't > produce any error. > > Users reporting this error are also experiencing bug 545790 and bug > 545738 . > > ProblemType: Bug > Architecture: i386 > Date: Fri Mar 19 00:09:06 2010 > DistroRelease: Ubuntu 10.04 > EcryptfsInUse: Yes > Package: dpkg 1.15.5.6ubuntu3 > ProcEnviron: >PATH=(custom, user) >LANG=en_US.utf8 >SHELL=/bin/bash > ProcVersionSignature: Ubuntu 2.6.32-16.25-generic > SourcePackage: dpkg > Uname: Linux 2.6.32-16-generic i686 > > To manage notifications about this bug go to: > https://bugs.launchpad.net/dpkg/+bug/541595/+subscriptions > -- 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/541595 Title: [Master] package failed to install/upgrade: package is already installed and configured Status in dpkg: New Status in apt package in Ubuntu: New Status in dpkg package in Ubuntu: Fix Released Bug description: Binary package hint: dpkg For yet unknown reasons packages fail to install with an error like: dpkg: error processing flashplugin-installer (--configure): package flashplugin-installer is already installed and configured without further error. This is a "one time" failure. Another run of the installation doesn't produce any error. Users reporting this error are also experiencing bug 545790 and bug 545738 . ProblemType: Bug Architecture: i386 Date: Fri Mar 19 00:09:06 2010 DistroRelease: Ubuntu 10.04 EcryptfsInUse: Yes Package: dpkg 1.15.5.6ubuntu3 ProcEnviron: PATH=(custom, user) LANG=en_US.utf8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.32-16.25-generic SourcePackage: dpkg Uname: Linux 2.6.32-16-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/dpkg/+bug/541595/+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 1499879] Re: [Today Scope] Moonphase could not be read
I suggested some new German translations for the lunar phases, avoiding very long terms, and using only terms from common speech (i.e. no astronomical terms). Additionally, I suggested to replace "Mondphase" with "Mond", to gain additional space for the lunar phases. BQ Aquaris E4.5 Ubuntu Edition Ubuntu 15.04 (OTA-13) ** Attachment added: "insufficient space on Aquaris E4.5 in landscape mode" https://bugs.launchpad.net/day-scope/+bug/1499879/+attachment/4762238/+files/screenshot20161017_033230993.png ** Also affects: ubuntu-translations Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1499879 Title: [Today Scope] Moonphase could not be read Status in Day Scope: Confirmed Status in Today Scope: Invalid Status in Ubuntu Translations: New Status in Ubuntu UX: Triaged Status in unity8 package in Ubuntu: New Bug description: Hello guys! I want to read information for the moon phase in TodayScope. Problem is that the displayed text is to long, so I can see first word but not the rest. I think it is really a good think with this information, thank you for this :-) I use a BQ Aquaris E4.5 with Ubuntu 15.04 r25 dashboard 1.9.2 I sent a screenshot To manage notifications about this bug go to: https://bugs.launchpad.net/day-scope/+bug/1499879/+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 1633954] Re: package click 0.4.43+16.04.20160203-0ubuntu2 failed to install/upgrade: subprocess new 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 click in Ubuntu. https://bugs.launchpad.net/bugs/1633954 Title: package click 0.4.43+16.04.20160203-0ubuntu2 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 Status in click package in Ubuntu: New Bug description: I was doing the distro upgrade from 16.04 to 16.10 and I encountered this error. ProblemType: Package DistroRelease: Ubuntu 16.10 Package: click 0.4.43+16.04.20160203-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-43.63-generic 4.4.21 Uname: Linux 4.4.0-43-generic x86_64 NonfreeKernelModules: vboxpci vboxnetadp vboxnetflt vboxdrv ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 Date: Sun Oct 16 19:37:22 2016 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2013-07-10 (1195 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3.1 SourcePackage: click Title: package click 0.4.43+16.04.20160203-0ubuntu2 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: Upgraded to yakkety on 2016-10-17 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/click/+bug/1633954/+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 541595] Re: [Master] package failed to install/upgrade: package is already installed and configured
** Changed in: dpkg (Ubuntu) Assignee: Magdalena Shneider (magdash) => (unassigned) -- 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/541595 Title: [Master] package failed to install/upgrade: package is already installed and configured Status in dpkg: New Status in apt package in Ubuntu: New Status in dpkg package in Ubuntu: Fix Released Bug description: Binary package hint: dpkg For yet unknown reasons packages fail to install with an error like: dpkg: error processing flashplugin-installer (--configure): package flashplugin-installer is already installed and configured without further error. This is a "one time" failure. Another run of the installation doesn't produce any error. Users reporting this error are also experiencing bug 545790 and bug 545738 . ProblemType: Bug Architecture: i386 Date: Fri Mar 19 00:09:06 2010 DistroRelease: Ubuntu 10.04 EcryptfsInUse: Yes Package: dpkg 1.15.5.6ubuntu3 ProcEnviron: PATH=(custom, user) LANG=en_US.utf8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.32-16.25-generic SourcePackage: dpkg Uname: Linux 2.6.32-16-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/dpkg/+bug/541595/+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 1629620] Re: DNS resolver stops accepting queries
this seems to be less of a problem after switching /etc/resolv.conf to point to the systemd-resolved managed file instead of the resolvconf managed file. not sure exactly which package should be changed to have this work automatically? -- 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/1629620 Title: DNS resolver stops accepting queries Status in network-manager package in Ubuntu: New Bug description: After a while / after resume from suspend, the system becomes unable to respond to DNS queries, with the following output for example: $ nslookup google.com 127.0.1.1 Server: 127.0.1.1 Address: 127.0.1.1#53 ** server can't find google.com: REFUSED This is on an up to date yakkety install. Changing resolv.conf to use 8.8.8.8, or restarting network-manager appears to fix this, at least until it recurs again. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: network-manager 1.2.4-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7 Uname: Linux 4.8.0-17-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Oct 1 21:28:51 2016 EcryptfsInUse: Yes IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2015-08-21 (407 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150819) IpRoute: default via 192.168.1.1 dev wlp3s0 proto static metric 600 169.254.0.0/16 dev docker0 scope link metric 1000 linkdown 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 192.168.1.0/24 dev wlp3s0 proto kernel scope link src 192.168.1.5 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to yakkety on 2016-09-29 (2 days ago) nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH docker0bridgeconnected /org/freedesktop/NetworkManager/Devices/1 docker0 63f0b05b-f699-4a68-81ce-f62d2c1a247d /org/freedesktop/NetworkManager/ActiveConnection/0 wlp3s0 wifi connected /org/freedesktop/NetworkManager/Devices/4 HOME-1622-5 6df3f2f0-fb86-43b5-802a-d59bc5734be3 /org/freedesktop/NetworkManager/ActiveConnection/2 24:DA:9B:B9:09:0E btdisconnected /org/freedesktop/NetworkManager/Devices/3 -- -- -- lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/2 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.4connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1629620/+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 1633954] [NEW] package click 0.4.43+16.04.20160203-0ubuntu2 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1
Public bug reported: I was doing the distro upgrade from 16.04 to 16.10 and I encountered this error. ProblemType: Package DistroRelease: Ubuntu 16.10 Package: click 0.4.43+16.04.20160203-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-43.63-generic 4.4.21 Uname: Linux 4.4.0-43-generic x86_64 NonfreeKernelModules: vboxpci vboxnetadp vboxnetflt vboxdrv ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 Date: Sun Oct 16 19:37:22 2016 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2013-07-10 (1195 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3.1 SourcePackage: click Title: package click 0.4.43+16.04.20160203-0ubuntu2 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: Upgraded to yakkety on 2016-10-17 (0 days ago) ** Affects: click (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package need-duplicate-check yakkety -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to click in Ubuntu. https://bugs.launchpad.net/bugs/1633954 Title: package click 0.4.43+16.04.20160203-0ubuntu2 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 Status in click package in Ubuntu: New Bug description: I was doing the distro upgrade from 16.04 to 16.10 and I encountered this error. ProblemType: Package DistroRelease: Ubuntu 16.10 Package: click 0.4.43+16.04.20160203-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-43.63-generic 4.4.21 Uname: Linux 4.4.0-43-generic x86_64 NonfreeKernelModules: vboxpci vboxnetadp vboxnetflt vboxdrv ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 Date: Sun Oct 16 19:37:22 2016 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2013-07-10 (1195 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3.1 SourcePackage: click Title: package click 0.4.43+16.04.20160203-0ubuntu2 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: Upgraded to yakkety on 2016-10-17 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/click/+bug/1633954/+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 1630156] Re: No password needed to Log in after cancel the password and then reset again
Output of command "groups" u adm cdrom sudo dip plugdev nopasswdlogin lpadmin sambashare and lightdm.log as attached ** Attachment added: "lightdm.log" https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1630156/+attachment/4762229/+files/lightdm.log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1630156 Title: No password needed to Log in after cancel the password and then reset again Status in Light Display Manager: New Status in OEM Priority Project: Confirmed Status in OEM Priority Project trusty series: Confirmed Status in lightdm package in Ubuntu: Confirmed Bug description: OS: 14.04 trusty Tested with 16.10 lightdm version is 1.19.5 issue still exist 1. Go to path "System Setting --> User Accounts--> Unlock" to unlock system setting. 2. Click "Password --> Action --> Log in without password -->Change to clear Log in password. 3. Reboot and log to desktop without password. 4. Then do the similar action "Set a password now" as the same way to set Log in password. 5. Reboot but still no password needed at Log in interface. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1630156/+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 1633319] Re: memory leak in indicator-datetime
I've been able to narrow down on my system that enabling "Evolution Data Server" for Access to the Google Calendar is the trigger for this memory issue. See the three screenshots. I even removed and reauthorized the Google account access with no change. First screenshot shows the Evolution Data Service disabled and memory function is normal. Second is toggling the Evolution Data Service from off to on. After ~10-5 seconds memory consumption appears at a rapid rate. Third is after switching Evolution Data Service from on to off and killing the indicator-datetime-service process showing the memory issue no longer exists. If Evolution Data Server is not switched to off killing the indicator- datetime-service process only restarts memory levels at the initial value and consumption growth appears nearly immediately following its automatic resume. ** Attachment added: "Three screenshots before during and after" https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1633319/+attachment/4762228/+files/screenshots.tar.gz -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1633319 Title: memory leak in indicator-datetime Status in indicator-datetime package in Ubuntu: Confirmed Bug description: After upgrading from 16.04 to 16.10 on the System76 Serval WS indicator-datetime-service is consuming all the system memory from 3.7GB up to 32 GB in 30 seconds. The system kills the indicator- datetime-service process and indicator-datetime-service restarts and memory consumption repeats until killed again. All swap memory is consumed in this pattern. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: indicator-datetime 15.10+16.10.20160820.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Uname: Linux 4.8.0-22-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Fri Oct 14 00:12:00 2016 EcryptfsInUse: Yes SourcePackage: indicator-datetime UpgradeStatus: Upgraded to yakkety on 2016-10-14 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1633319/+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 1522316] Re: Icons are too big
Still present in Yakkety. I know that the desktop and Nautilus icon sizes are interconnected, but I end up with tiny icons in Nautilus and oversized (but a bit smaller) icons on the desktop. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1522316 Title: Icons are too big Status in Nautilus: Incomplete Status in nautilus package in Ubuntu: Triaged Status in ubuntu-settings package in Ubuntu: Fix Released Bug description: On xenial the icons in nautilus (also on the Desktop) are too big. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nautilus 1:3.18.2-1ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6 Uname: Linux 4.2.0-19-generic x86_64 ApportVersion: 2.19.2-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Thu Dec 3 09:37:55 2015 GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-visible-columns' b"['name', 'size', 'type', 'date_modified']" b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'owner', 'group', 'permissions', 'mime_type', 'where']" InstallationDate: Installed on 2015-04-30 (216 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: nautilus SystemImageInfo: Error: command ['system-image-cli', '-i'] failed with exit code 2: UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1522316/+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 1513275]
Tem como eu localizar meu notebook.?e um satux, com sistema Linux. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1513275 Title: package libdevmapper1.02.1:amd64 2:1.02.90-2ubuntu1 failed to install/upgrade: dependency problems - leaving unconfigured Status in lvm2 package in Ubuntu: Confirmed Bug description: nao consigo atualizar? ProblemType: Package DistroRelease: Ubuntu 15.04 Package: libdevmapper1.02.1:amd64 2:1.02.90-2ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-67.110-generic 3.13.11-ckt27 Uname: Linux 3.13.0-67-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.18 Architecture: amd64 Date: Wed Nov 4 23:16:54 2015 DpkgHistoryLog: DpkgTerminalLog: ErrorMessage: dependency problems - leaving unconfigured InstallationDate: Installed on 2015-10-20 (15 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) RelatedPackageVersions: dpkg 1.17.25ubuntu1 apt 1.0.1ubuntu2.10 SourcePackage: lvm2 Title: package libdevmapper1.02.1:amd64 2:1.02.90-2ubuntu1 failed to install/upgrade: dependency problems - leaving unconfigured UpgradeStatus: Upgraded to vivid on 2015-11-05 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1513275/+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 1408963] Re: [Xbuntu 14.04, 14.10 and 15.04] Network manager stops working: iwl3945 0000:03:00.0: BSM uCode verification failed at addr ...; wlan0: deauthenticating from... by lo
I had never heard of this problem until upgrading to 16.10 yesterday. Now my HP DV6000 is suffering from this exact problem, about 5 times in less than 24 hours since the upgrade. -- 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/1408963 Title: [Xbuntu 14.04, 14.10 and 15.04] Network manager stops working: iwl3945 :03:00.0: BSM uCode verification failed at addr ...; wlan0: deauthenticating from... by local choice (Reason: 3=DEAUTH_LEAVING), Status in network-manager package in Ubuntu: Incomplete Bug description: From time to time, the system loses all wireles networks and kubuntu network manager applet goes blank - not even one network is shown. All wifi connections are broken. Rebooting fixes the issue, switching to WICD on-the-fly enables to continue browsing without rebooting, so it seems to be no hardware issue or iwl3945 issue. What to expect: stable connections and flawless network managing. What happens: so above. Further informations about the system, the network configuration, the package version can be found in the attachment, also parts of rsyslog and dmesg. Interesting, according to some helpers, are the following lines: dmesg: wlan0: deauthenticating from 02:26:4d:ac:8f:45 by local choice (Reason: 3=DEAUTH_LEAVING) lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 14.10 Release:14.10 Codename: utopic apt-cache policy network-manager network-manager: Installiert: 0.9.8.8-0ubuntu28 Installationskandidat: 0.9.8.8-0ubuntu28 Versionstabelle: *** 0.9.8.8-0ubuntu28 0 500 http://de.archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1408963/+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 1578810] Re: Insensitive (disabled) toolbar icons in GTK3 are not dimmed
I tested the proposed fix for Yakkety and it also works well, thanks! -- 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/1578810 Title: Insensitive (disabled) toolbar icons in GTK3 are not dimmed Status in remmina: Invalid Status in Ubuntu theme: In Progress Status in Wireshark: Invalid Status in ubuntu-themes package in Ubuntu: In Progress Bug description: [ Impact ] Disabled (GTK 3.20) and Insensitive (GTK <= 3.18) icons are not dimmed, therefore there is no visual indication that an icon in the toolbar is inactionable. [ Test Case ] This issue can be observed in Xenial and Yakkety. Install `gtk-3-examples` and run `gtk3-widget-factory`, look at the toolbar on Page 2, the last icon (tooltip 'Insert something') is disabled/insensitive and should be dimmed, but is not. After applying the relevant merge proposal (see below), the disabled/insensitive icon in the toolbar on Page 2 of gtk3-widgets- factory will now be dimmed. [ Regression Potential ] None. [ Other Info ] This issue can also be reproduced on Xenial and Yakkety using: * Remmina (from the archive) * Wireshark (from the archive) * Eclipse (downloaded) To reproduce with Eclipse, Eclipse has to be downloaded since the version in the archive uses GTK2+ for styling, and dims insensitive icons correctly. * Download a recent Eclipse https://www.eclipse.org/downloads/download.php?file=/eclipse/downloads/drops4/R-4.5.2-201602121500/eclipse-SDK-4.5.2-linux-gtk-x86_64.tar.gz * Extract and execute the "eclipse" executable * In the toolbar, several icons look enabled even though they are not. For example the Save icon (Floppy). To manage notifications about this bug go to: https://bugs.launchpad.net/remmina/+bug/1578810/+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 1629150] Re: background process apport routinely using 100% CPU
since mediascanner doesn't seem to crash so much in 16.10 ...this might be way harder to reproduce / isn't as much of a problem. -- 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/1629150 Title: background process apport routinely using 100% CPU Status in apport package in Ubuntu: New Bug description: Seems to be when mediascanner-2.0 is not running when *it's* usually the process that takes up 100% cpu ( https://bugs.launchpad.net/ubuntu/+source/mediascanner2/+bug/1398614 )...that apport begins to run at 100% cpu for an indeterminate time(after awhile of heating up my computer, I typically kill -9 it). #0 __memcpy_sse2_unaligned () at ../sysdeps/x86_64/multiarch/memcpy-sse2-unaligned.S:81 #1 0x005b6d18 in ?? () #2 0x0051bdbe in PyEval_EvalFrameEx () #3 0x00523de7 in ?? () #4 0x0051f992 in PyEval_EvalFrameEx () #5 0x0051f294 in PyEval_EvalFrameEx () #6 0x00523de7 in ?? () #7 0x00524b0f in PyEval_EvalCode () #8 0x005fd5f2 in ?? () #9 0x005ffb2a in PyRun_FileExFlags () #10 0x005ffd1c in PyRun_SimpleFileExFlags () #11 0x0063f886 in Py_Main () #12 0x004d00e1 in main () cpu: 4 cores: example: vendor_id : GenuineIntel cpu family: 6 model : 58 model name: Intel(R) Core(TM) i5-3230M CPU @ 2.60GHz stepping : 9 microcode : 0x15 cpu MHz : 1581.125 cache size: 3072 KB physical id : 0 siblings : 4 core id : 1 cpu cores : 2 apicid: 3 initial apicid: 3 fpu : yes fpu_exception : yes cpuid level : 13 wp: yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm epb tpr_shadow vnmi flexpriority ept vpid fsgsbase smep erms xsaveopt dtherm ida arat pln pts bugs : bogomips : 5188.25 clflush size : 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management: Ubuntu: 16.04.1 LTS xenial apport: apport: Installed: 2.20.1-0ubuntu2.1 Candidate: 2.20.1-0ubuntu2.1 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: apport 2.20.1-0ubuntu2.1 ProcVersionSignature: Ubuntu 4.4.0-40.60-generic 4.4.21 Uname: Linux 4.4.0-40-generic x86_64 ApportLog: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Sep 29 20:28:43 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2014-07-09 (813 days ago) InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 (20140708) PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to xenial on 2016-08-16 (44 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1629150/+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 1513275] Re: package libdevmapper1.02.1:amd64 2:1.02.90-2ubuntu1 failed to install/upgrade: dependency problems - leaving unconfigured
this issue doesn't seem to exist for me in yakkety / 16.10 ? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1513275 Title: package libdevmapper1.02.1:amd64 2:1.02.90-2ubuntu1 failed to install/upgrade: dependency problems - leaving unconfigured Status in lvm2 package in Ubuntu: Confirmed Bug description: nao consigo atualizar? ProblemType: Package DistroRelease: Ubuntu 15.04 Package: libdevmapper1.02.1:amd64 2:1.02.90-2ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-67.110-generic 3.13.11-ckt27 Uname: Linux 3.13.0-67-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.18 Architecture: amd64 Date: Wed Nov 4 23:16:54 2015 DpkgHistoryLog: DpkgTerminalLog: ErrorMessage: dependency problems - leaving unconfigured InstallationDate: Installed on 2015-10-20 (15 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) RelatedPackageVersions: dpkg 1.17.25ubuntu1 apt 1.0.1ubuntu2.10 SourcePackage: lvm2 Title: package libdevmapper1.02.1:amd64 2:1.02.90-2ubuntu1 failed to install/upgrade: dependency problems - leaving unconfigured UpgradeStatus: Upgraded to vivid on 2015-11-05 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1513275/+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 1629598] Re: Apps failing to load on M10 (OTA13)
UPDATE: Depsite a full wipe (which led to partition issues, and then to a full reflash to Android and back to UT!), the issues with my apps persist and now the Music app has stopped working too. It just hangs on the initial screen, not even loading any tracks or artwork. ** Also affects: music-app Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to camera-app in Ubuntu. https://bugs.launchpad.net/bugs/1629598 Title: Apps failing to load on M10 (OTA13) Status in Canonical System Image: New Status in Ubuntu Music App: New Status in Ubuntu Document Viewer App: New Status in camera-app package in Ubuntu: New Status in gallery-app package in Ubuntu: New Bug description: Over the last few months, apps have started failing to start on my M10. Apps affected currently: - camera (stops at 'Loading...' screen), - gallery (stops at 'Gallery' splash screen), - document viewer (stops with white screen and 'Documents' header) I have had issues with Telegram too, which now just goes to a white screen, but that may stem from setup problems I have with the app on my M10 and E4.5 (see https://bugs.launchpad.net/unity-webapps- telegram/+bug/1626728) I had hoped OTA13 would fix it, but sadly not. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1629598/+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 1633274] Re: Systemd-networkd crashes with core dump
This is auto uploaded by "ubuntu-bug", i've ran the systemd-networkd in debug mode, didn't give any more output. -- 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/1633274 Title: Systemd-networkd crashes with core dump Status in systemd package in Ubuntu: Incomplete Bug description: Systemd-networkd crashes with core dump, this happends in Yakkety and Xenial. The latest patch that was commited to Xenial-updates and Yakkety is the one that broke this. Everything works just fine with Xenial without latest update or Yakkety Beta 2. The log entries i see is: Oct 14 02:37:42 Router01 systemd-networkd[3402]: Assertion 't' failed at ../src/network/networkd-netdev-tunnel.c:210, function netdev_vti_fill_message_key(). Aborting. Oct 14 02:37:42 Router01 systemd[1]: systemd-networkd.service: Main process exited, code=dumped, status=6/ABRT Oct 14 02:37:42 Router01 systemd[1]: systemd-networkd.service: Unit entered failed state. Oct 14 02:37:42 Router01 systemd[1]: systemd-networkd.service: Failed with result 'core-dump'. Oct 14 02:37:42 Router01 systemd[1]: systemd-networkd.service: Service has no hold-off time, scheduling restart. Oct 14 02:37:42 Router01 systemd[1]: Stopped Network Service. Oct 14 02:37:42 Router01 systemd[1]: systemd-networkd.service: Start request repeated too quickly. Oct 14 02:37:42 Router01 systemd[1]: Failed to start Network Service. Oct 14 02:37:42 Router01 systemd[1]: Dependency failed for Wait for Network to be Configured. Oct 14 02:37:42 Router01 systemd[1]: systemd-networkd-wait-online.service: Job systemd-networkd-wait-online.service/start failed with result 'dependency'. Oct 14 02:37:42 Router01 systemd[1]: systemd-networkd.service: Unit entered failed state. Oct 14 02:37:42 Router01 systemd[1]: systemd-networkd.service: Failed with result 'start-limit-hit'. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: systemd 231-9git1 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Uname: Linux 4.8.0-22-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 Date: Fri Oct 14 02:39:05 2016 InstallationDate: Installed on 2016-10-13 (0 days ago) InstallationMedia: Ubuntu-Server 16.10 "Yakkety Yak" - Release amd64 (20161012.1) MachineType: Dell Inc. OptiPlex 755 ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-22-generic root=/dev/mapper/hostname--vg-root ro SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/11/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A22 dmi.board.name: 0PU052 dmi.board.vendor: Dell Inc. dmi.chassis.type: 15 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA22:bd06/11/2012:svnDellInc.:pnOptiPlex755:pvr:rvnDellInc.:rn0PU052:rvr:cvnDellInc.:ct15:cvr: dmi.product.name: OptiPlex 755 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1633274/+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 1633751] Re: No login prompt when waking up the computer from suspend
That's fine to me, Gunnar. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1633751 Title: No login prompt when waking up the computer from suspend Status in lightdm package in Ubuntu: Incomplete Bug description: Ubuntu 16.10 x64. * I let my computer go to sleep. * Several hours later I wake it up. Expected result: the lock screen is displayed, waiting for me to input my password. Actual result: I am directly back to my desktop. I verified that the option to ask for my password at wake up is correctly checked. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: lightdm 1.19.5-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Uname: Linux 4.8.0-22-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Sat Oct 15 18:34:14 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-10-14 (0 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1633751/+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 1410012] Re: Does not detect hotplugged storage device
lsblk /dev/sdb1 NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sdb1 8:17 0 3.7T 0 part /mnt/disk fstab: UUID=885e04f0-bd26-4885-aa1c-f134c674b8ff / ext4 errors=remount-ro 0 1 /swap noneswapdefaults (ie only my other hard disk and swap) ls -l /var/run/systemd/generator/ total 8 drwxr-xr-x 2 root root 60 Oct 16 13:54 local-fs.target.requires drwxr-xr-x 2 root root 60 Oct 16 13:54 local-fs.target.wants -rw-r--r-- 1 root root 277 Oct 16 13:54 -.mount drwxr-xr-x 2 root root 60 Oct 16 13:54 multi-user.target.wants -rw-r--r-- 1 root root 0 Oct 16 13:54 netplan.stamp drwxr-xr-x 2 root root 40 Oct 16 13:54 openvpn.service.wants drwxr-xr-x 2 root root 40 Oct 16 13:54 postfix.service.wants -rw-r--r-- 1 root root 160 Oct 16 13:54 swap.swap drwxr-xr-x 2 root root 60 Oct 16 13:54 swap.target.requires drwxr-xr-x 2 root root 60 Oct 16 13:54 tor.service.wants ** Tags added: yakkety -- 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/1410012 Title: Does not detect hotplugged storage device Status in systemd package in Ubuntu: New Bug description: I plug it in, it doesn't automatically mount, is not visible in nautilus. Mounts fine on system start up. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: udev 218-3ubuntu1 ProcVersionSignature: Ubuntu 3.18.0-8.9-generic 3.18.1 Uname: Linux 3.18.0-8-generic x86_64 ApportVersion: 2.15.1-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Jan 12 22:07:54 2015 EcryptfsInUse: Yes HotplugNewDevices: /dev/sda /dev/sda1 HotplugNewMounts: InstallationDate: Installed on 2014-07-09 (187 days ago) InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 (20140708) MachineType: Acer TravelMate P273-MG ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.18.0-8-generic root=UUID=885e04f0-bd26-4885-aa1c-f134c674b8ff ro quiet splash vt.handoff=7 SourcePackage: systemd Symptom: storage Title: Does not detect hotplugged storage device UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/27/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.11 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: BA70_HC dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.11:bd11/27/2013:svnAcer:pnTravelMateP273-MG:pvrV2.11:rvnAcer:rnBA70_HC:rvrType2-BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: TravelMate P273-MG dmi.product.version: V2.11 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1410012/+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 1632772] Re: GNOME on Wayland does not start from LightDM
Requested log file attached. ** Attachment added: "lightdm.log" https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1632772/+attachment/4762171/+files/lightdm.log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1632772 Title: GNOME on Wayland does not start from LightDM Status in gnome-session package in Ubuntu: New Status in lightdm package in Ubuntu: Incomplete Bug description: When picking GNOME on Wayland as session and attempting to login from LightDM then it fails, all you see is a black screen with a blinking cursor. However, manually running: $ dbus-run-session gnome-shell --display-server --wayland from the console/vt1 (Ctrl+Alt+F1) seems to work. But from LightDM it does not work. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: gnome-session-wayland 3.20.2-1ubuntu7 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Uname: Linux 4.8.0-22-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 Date: Wed Oct 12 18:06:13 2016 InstallationDate: Installed on 2013-12-26 (1020 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1632772/+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 19353] Re: Tools relying on /etc/debian_version get confused
** Tags added: yakkety -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/19353 Title: Tools relying on /etc/debian_version get confused Status in base-files package in Ubuntu: Confirmed Bug description: /etc/debian_version appears to be carried unmodified from Debian on Ubuntu systems. This means that things like reportbug that use the information there to identify the version of Debian that they are running on will identify Unbuntu systems as a Debian version. Another approach would be to modify all the tools like reportbug to add their own information or read /etc/ubuntu_version and prefer that. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/19353/+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 1630750] Re: package dbus 1.10.10-1ubuntu1 failed to install/upgrade: triggers looping, abandoned
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: dbus (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1630750 Title: package dbus 1.10.10-1ubuntu1 failed to install/upgrade: triggers looping, abandoned Status in dbus package in Ubuntu: Confirmed Bug description: Was trying to upgrade from 16.04 to 16.10 beta ProblemType: Package DistroRelease: Ubuntu 16.10 Package: dbus 1.10.10-1ubuntu1 Uname: Linux 4.7.3-040703-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Wed Oct 5 22:31:26 2016 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2016-09-13 (22 days ago) InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160720) RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3 SourcePackage: dbus Title: package dbus 1.10.10-1ubuntu1 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to yakkety on 2016-10-05 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1630750/+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 1633912] Re: Problem with DNS resolution after suspend
▶ sudo killall dnsmasq Works as well, afterwards things work again. -- 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/1633912 Title: Problem with DNS resolution after suspend Status in network-manager package in Ubuntu: New Bug description: I upgraded my laptop to 16.10 yesterday. Sometimes after suspend I have network issues, one time I was not able to connect to a wifi network (might report another bug if this occurees again, but maybe it is related, as in network-manager is in some broken state after suspend). Here is whats happening pretty often: After resume from suspend I have a solid network connection, no problem to ping machines in LAN or on the internet. But DNS resolution is broken until I restart the network-manager service. I ran ubuntu-bug while DNS was broken, so if anything gets log-ed it should be in there. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: network-manager 1.2.4-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Uname: Linux 4.8.0-22-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Sun Oct 16 21:01:09 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-09-28 (18 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IpRoute: default via 192.168.0.1 dev wlp58s0 proto static metric 600 169.254.0.0/16 dev br-541a0f9bec93 scope link metric 1000 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 172.18.0.0/16 dev br-541a0f9bec93 proto kernel scope link src 172.18.0.1 192.168.0.0/24 dev wlp58s0 proto kernel scope link src 192.168.0.118 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to yakkety on 2016-10-15 (1 days ago) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.4connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1633912/+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 1632964] Re: Regression: systemd does not send all queued DBus Signals when a unit gets inactive
I have been able to reproduce those missing signals most reliably within a systemd user session (for the system session it works most of the time): Steps to reproduce missing dbus signals with Ubuntu 16.10 Desktop: Create a ~/.config/systemd/user/terminal.service with this content: [Unit] Description=example unit to open a terminal [Service] Environment=DISPLAY=:0 ExecStart=/usr/bin/xterm SuccessExitStatus=0 15 [Install] WantedBy=default.target Open two terminals. In the first one execute the attached test_systemd_signals.py (which looks for PropertiesChanged Signals): $ python test_systemd_signals.py To see all dbus messages during the test you can run "dbus-monitor --session" in another terminal. In a second terminal start/stop the systemd unit: $ systemctl --user daemon-reload $ systemctl --user start terminal.service $ systemctl --user stop terminal.service With the current systemd package 231-9git1 the test script only shows two status changes (PropertiesChanged signals) sent by systemd: ActiveState: active SubState: running ActiveState: deactivating SubState: stop-sigterm With the patched systemd package the test script should show the last change of the unit status (being set to inactive), too: ActiveState: active SubState: running ActiveState: deactivating SubState: stop-sigterm ActiveState: inactive SubState: dead Ubuntu 16.04 Desktop does not start a systemd user session by default - I created a package (based on https://github.com/joukewitteveen/xlogin) to simplify the process: $ sudo add-apt-repository ppa:seahawk1986-hotmail/xlogin $ sudo apt-get update $ sudo apt-get install xlogin openbox Create a ~/.xinitrc with this content (and make it executable): #!/bin/bash exec openbox-session Then change to a tty console (or use a remote login via ssh): $ sudo systemctl stop lightdm $ sudo systemctl start xlogin@user # replace "user" with an existing user name Now you can open two terminals (a right click on the desktop opens the openbox menu) and follow the steps for Ubuntu 16.10 above. ** Attachment added: "test_systemd_signals.py" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1632964/+attachment/4762145/+files/test_systemd_signals.py -- 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/1632964 Title: Regression: systemd does not send all queued DBus Signals when a unit gets inactive Status in systemd package in Ubuntu: In Progress Status in systemd source package in Xenial: Incomplete Status in systemd source package in Yakkety: In Progress Status in systemd source package in z-series: Fix Committed Bug description: Since the penultimate systemd package update in september (229-4ubuntu8) systemd does not send the remaining queued DBus signals (e.g. PropertiesChanged) when a unit's state changes to inactive. Sending those signals has been working since the release of Ubuntu 16.04 and it is quite unfortunate for my use case this got broken while fixing another bug. Adding this upstream change to the package restores the old functionality (a patch for the current systemd package (systemd 229-4ubuntu10) for xenial is attached): https://github.com/systemd/systemd/commit/0dd99f86addd1f81e24e89807b6bc4aab57d5793 $ lsb_release -rd Description:Ubuntu 16.04.1 LTS Release:16.04 package version: systemd 229-4ubuntu10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1632964/+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 1633751] Re: No login prompt when waking up the computer from suspend
Thanks for that info. If the issue isn't reproducible it's hard to deal with.. I let the status of this bug report remain "Incomplete". It means that it will be automatically closed in a couple of months if there is no further activity. Would you be able to reproduce the issue after that, please file a new bug. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1633751 Title: No login prompt when waking up the computer from suspend Status in lightdm package in Ubuntu: Incomplete Bug description: Ubuntu 16.10 x64. * I let my computer go to sleep. * Several hours later I wake it up. Expected result: the lock screen is displayed, waiting for me to input my password. Actual result: I am directly back to my desktop. I verified that the option to ask for my password at wake up is correctly checked. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: lightdm 1.19.5-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Uname: Linux 4.8.0-22-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Sat Oct 15 18:34:14 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-10-14 (0 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1633751/+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 1633912] [NEW] Problem with DNS resolution after suspend
Public bug reported: I upgraded my laptop to 16.10 yesterday. Sometimes after suspend I have network issues, one time I was not able to connect to a wifi network (might report another bug if this occurees again, but maybe it is related, as in network-manager is in some broken state after suspend). Here is whats happening pretty often: After resume from suspend I have a solid network connection, no problem to ping machines in LAN or on the internet. But DNS resolution is broken until I restart the network- manager service. I ran ubuntu-bug while DNS was broken, so if anything gets log-ed it should be in there. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: network-manager 1.2.4-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Uname: Linux 4.8.0-22-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Sun Oct 16 21:01:09 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-09-28 (18 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IpRoute: default via 192.168.0.1 dev wlp58s0 proto static metric 600 169.254.0.0/16 dev br-541a0f9bec93 scope link metric 1000 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 172.18.0.0/16 dev br-541a0f9bec93 proto kernel scope link src 172.18.0.1 192.168.0.0/24 dev wlp58s0 proto kernel scope link src 192.168.0.118 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to yakkety on 2016-10-15 (1 days ago) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.4connected started full enabled enabled enabled enabled enabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug yakkety -- 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/1633912 Title: Problem with DNS resolution after suspend Status in network-manager package in Ubuntu: New Bug description: I upgraded my laptop to 16.10 yesterday. Sometimes after suspend I have network issues, one time I was not able to connect to a wifi network (might report another bug if this occurees again, but maybe it is related, as in network-manager is in some broken state after suspend). Here is whats happening pretty often: After resume from suspend I have a solid network connection, no problem to ping machines in LAN or on the internet. But DNS resolution is broken until I restart the network-manager service. I ran ubuntu-bug while DNS was broken, so if anything gets log-ed it should be in there. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: network-manager 1.2.4-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Uname: Linux 4.8.0-22-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Sun Oct 16 21:01:09 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-09-28 (18 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IpRoute: default via 192.168.0.1 dev wlp58s0 proto static metric 600 169.254.0.0/16 dev br-541a0f9bec93 scope link metric 1000 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 172.18.0.0/16 dev br-541a0f9bec93 proto kernel scope link src 172.18.0.1 192.168.0.0/24 dev wlp58s0 proto kernel scope link src 192.168.0.118 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to yakkety on 2016-10-15 (1 days ago) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.4connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1633912/+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 1633873] Re: package tzdata 2016g-0ubuntu0.16.04 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 1
*** This bug is a duplicate of bug 1633791 *** https://bugs.launchpad.net/bugs/1633791 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1633791, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1633791 package tzdata 2016g-0ubuntu0.16.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1633873 Title: package tzdata 2016g-0ubuntu0.16.04 failed to install/upgrade: sub- processo script post-installation instalado retornou estado de saída de erro 1 Status in tzdata package in Ubuntu: New Bug description: after SO updates from ubuntu software every system start up i have a bug report problem. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: tzdata 2016g-0ubuntu0.16.04 ProcVersionSignature: Ubuntu 4.4.0-43.63-generic 4.4.21 Uname: Linux 4.4.0-43-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 AptOrdering: tzdata: Install tzdata: Configure NULL: ConfigurePending Architecture: amd64 Date: Sat Oct 15 21:03:20 2016 ErrorMessage: sub-processo script post-installation instalado retornou estado de saída de erro 1 InstallationDate: Installed on 2016-10-12 (3 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: tzdata Title: package tzdata 2016g-0ubuntu0.16.04 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1633873/+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 1610534] Re: Open tabs keep getting forgotten
Back to the original bug. It's been 2-3 weeks, and now it has forgotten my tabs yet again. Friday night, I closed the browser with 7 tabs, afterwards I shutdown the phone. Saturday morning, I turned my phone on, opened a twitter link, the browser app opened with only this tab, having forgotten my other 7 tabs. ** Summary changed: - Restore previous session doesn't work + Open tabs keep getting forgotten ** Changed in: webbrowser-app (Ubuntu) Status: Invalid => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1610534 Title: Open tabs keep getting forgotten Status in webbrowser-app package in Ubuntu: New Bug description: The browser app keeps forgetting my open tabs on a semi-regular basis. It seems to happen to me every couple of weeks or so, I will open the app and all my tabs are gone. This is very frustrating, as there is no easy way to recover them. I think it may actually happen more frequently when there are around 7/8 tabs or more open. OTA-12 (and previous versions), mako. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1610534/+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 1573470] Re: GLX apps (including Libreoffice Impress presentation mode) on ARM devices display wrong colors
I use Citix receiver to connect to my desktop at the office (Windows 7 / Office 2013) in libertine. Same problem as in Impress presentation mode. Colors are mixed up. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1573470 Title: GLX apps (including Libreoffice Impress presentation mode) on ARM devices display wrong colors Status in Canonical System Image: Confirmed Status in Mir: Opinion Status in Puritine: Invalid Status in mesa package in Ubuntu: Confirmed Status in mir package in Ubuntu: Opinion Status in xorg-server package in Ubuntu: Invalid Bug description: GLX apps (including Libreoffice Impress presentation mode) on ARM devices display wrong colors --- On the new BQ M10 tablet. 1- switch to desktop mode (manual, no external peripheral attached) 2- launch libreoffice 3- open impress file 4- colours in images are all messed up on the BQ M10 screen when toggle to presentation view. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1573470/+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 1633751] Re: No login prompt when waking up the computer from suspend
'sudo systemctl suspend' works fine and I m prompted for my password on wake-up. When I voluntarily ask the computer, it's ok too. I tried to reproduce the same conditions than when the bug occurred: I was watching a flash video in my web browser, and flash does not disable screen power off nor sleep mode when a video is playing. Unfortunately I did not reproduce the bug. If I encounter the bug again I will add more information here, hopefully I will find the conditions that led to the bug (I only saw it once but my Ubuntu 16.10 installation is fresh). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1633751 Title: No login prompt when waking up the computer from suspend Status in lightdm package in Ubuntu: Incomplete Bug description: Ubuntu 16.10 x64. * I let my computer go to sleep. * Several hours later I wake it up. Expected result: the lock screen is displayed, waiting for me to input my password. Actual result: I am directly back to my desktop. I verified that the option to ask for my password at wake up is correctly checked. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: lightdm 1.19.5-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Uname: Linux 4.8.0-22-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Sat Oct 15 18:34:14 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-10-14 (0 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1633751/+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 1398614] Re: mediascanner-service-2.0 using large amounts of CPU
Upgrading to 16.10 (yakkety) seems to have resolved this(?). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mediascanner2 in Ubuntu. https://bugs.launchpad.net/bugs/1398614 Title: mediascanner-service-2.0 using large amounts of CPU Status in mediascanner2 package in Ubuntu: Confirmed Bug description: Each time I plug my external USB hard disk the mediascanner-service process is activ and is using large amount of CPU for long minutes without interruption. I have the same problem in utopic and vivid ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: mediascanner2.0 0.105+15.04.20141030.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic x86_64 ApportVersion: 2.14.7-0ubuntu10 Architecture: amd64 CurrentDesktop: Unity Date: Wed Dec 3 00:29:43 2014 InstallationDate: Installed on 2011-05-26 (1286 days ago) InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1) SourcePackage: mediascanner2 UpgradeStatus: Upgraded to vivid on 2013-11-26 (371 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mediascanner2/+bug/1398614/+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 1542374] Re: bluez hung upgrade from 14.04 to 15.10
just upgraded from 16.04 to 16.10 and this did not occur. At the very least, it appears that it's only affecting 14.04 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1542374 Title: bluez hung upgrade from 14.04 to 15.10 Status in bluez package in Ubuntu: Confirmed Bug description: upgrade process to ubuntu wily got stuck for > 24 hours on : Setting up bluez (5.35-0ubuntu2) ... Installing new version of config file /etc/bluetooth/input.conf ... Installing new version of config file /etc/bluetooth/main.conf ... Installing new version of config file /etc/dbus-1/system.d/bluetooth.conf ... Installing new version of config file /etc/init.d/bluetooth ... Installing new version of config file /etc/init/bluetooth.conf ... ended it with a ^C and kill -9 dpkg (there was a dpkg process left after the ^C but gdb did not glean any information from it), and then dpkg --configure -a successfully appeared to finish the install off. claims to be installed and working, now: bluez: Installed: 5.35-0ubuntu2 Candidate: 5.35-0ubuntu2 ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: bluez 5.35-0ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-37.51~14.04.1-lowlatency 3.16.7-ckt9 Uname: Linux 3.16.0-37-lowlatency x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 Date: Fri Feb 5 10:33:26 2016 InstallationDate: Installed on 2015-05-07 (273 days ago) InstallationMedia: Ubuntu-Studio 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) InterestingModules: bluetooth MachineType: Acer Veriton M480 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-37-lowlatency root=UUID=febd52dc-833f-4df7-a355-6aab2c0f8c00 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to wily on 2016-02-05 (0 days ago) dmi.bios.date: 05/26/2009 dmi.bios.vendor: Acer dmi.bios.version: P01-A2 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: Veriton M480 dmi.board.vendor: Acer dmi.chassis.type: 3 dmi.chassis.vendor: Acer dmi.modalias: dmi:bvnAcer:bvrP01-A2:bd05/26/2009:svnAcer:pnVeritonM480:pvr:rvnAcer:rnVeritonM480:rvr:cvnAcer:ct3:cvr: dmi.product.name: Veriton M480 dmi.sys.vendor: Acer hciconfig: rfkill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no syslog: Feb 05 10:32:07 tbpl-makerspace2 NetworkManager[646]: Loaded device plugin: NMBluezManager (/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-bluetooth.so) Feb 05 10:32:57 tbpl-makerspace2 ureadahead[229]: ureadahead:bluetooth: Ignored relative path Feb 05 10:32:57 tbpl-makerspace2 ureadahead[229]: ureadahead:bluetooth.target.wants: Ignored relative path To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1542374/+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 1633905] Re: xenial to yakkety upgrade : "Activated service 'ca.desrt.dconf' failed"
I can trigger individual instances of these errors via gnome-control- center, by going to settings -> background -> pictures -> selecting my jpeg wallpaper -> hitting 'select'. result: a single line of Oct 16 14:16:30 localhost gnome-control-c[8352]: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ExecFailed: Failed to execute program ca.desrt.dconf: No such file or directory -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to d-conf in Ubuntu. https://bugs.launchpad.net/bugs/1633905 Title: xenial to yakkety upgrade : "Activated service 'ca.desrt.dconf' failed" Status in d-conf package in Ubuntu: New Status in gnome-shell package in Ubuntu: New Bug description: 1) Upgraded from ubuntu 16.04 (xenial) to 16.10 (yakkety) Result: My /var/log/kern.log file was very quickly filling with MB and MB of messages of the form Oct 16 12:45:23 localhost gnome-shell[2655]: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ExecFailed: Failed to execute program ca.desrt.dconf: No such file or directory and my /var/log/syslog file was very quickly filling with MB and MB of messages of the form Oct 16 12:44:30 localhost gnome-shell[2655]: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ExecFailed: Failed to execute program ca.desrt.dconf: No such file or directory Oct 16 12:44:30 localhost dbus-daemon[2284]: Activating service name='ca.desrt.dconf' Oct 16 12:44:30 localhost dbus-daemon[2284]: Activated service 'ca.desrt.dconf' failed: Failed to execute program ca.desrt.dconf: No such file or directory Workaround: moved .config/dconf to a backup directory (contents attached), and restarted: while at least the kern.log logs keep coming, at least they are coming like one at a time over a long period of time rather than a million at a time, also gnome-shell seems much more stable now (it hasn't crashed since I did this). gnome-shell: Installed: 3.20.4-0ubuntu1 Candidate: 3.20.4-0ubuntu1 Version table: *** 3.20.4-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu yakkety/universe amd64 Packages 100 /var/lib/dpkg/status dconf-service: Installed: 0.26.0-2 Candidate: 0.26.0-2 Version table: *** 0.26.0-2 500 500 http://archive.ubuntu.com/ubuntu yakkety/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: dconf-service 0.26.0-2 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Uname: Linux 4.8.0-22-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Oct 16 13:56:22 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2014-07-09 (829 days ago) InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 (20140708) SourcePackage: d-conf UpgradeStatus: Upgraded to yakkety on 2016-10-16 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/d-conf/+bug/1633905/+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 1633905] [NEW] xenial to yakkety upgrade : "Activated service 'ca.desrt.dconf' failed"
Public bug reported: 1) Upgraded from ubuntu 16.04 (xenial) to 16.10 (yakkety) Result: My /var/log/kern.log file was very quickly filling with MB and MB of messages of the form Oct 16 12:45:23 localhost gnome-shell[2655]: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ExecFailed: Failed to execute program ca.desrt.dconf: No such file or directory and my /var/log/syslog file was very quickly filling with MB and MB of messages of the form Oct 16 12:44:30 localhost gnome-shell[2655]: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ExecFailed: Failed to execute program ca.desrt.dconf: No such file or directory Oct 16 12:44:30 localhost dbus-daemon[2284]: Activating service name='ca.desrt.dconf' Oct 16 12:44:30 localhost dbus-daemon[2284]: Activated service 'ca.desrt.dconf' failed: Failed to execute program ca.desrt.dconf: No such file or directory Workaround: moved .config/dconf to a backup directory (contents attached), and restarted: while at least the kern.log logs keep coming, at least they are coming like one at a time over a long period of time rather than a million at a time, also gnome-shell seems much more stable now (it hasn't crashed since I did this). gnome-shell: Installed: 3.20.4-0ubuntu1 Candidate: 3.20.4-0ubuntu1 Version table: *** 3.20.4-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu yakkety/universe amd64 Packages 100 /var/lib/dpkg/status dconf-service: Installed: 0.26.0-2 Candidate: 0.26.0-2 Version table: *** 0.26.0-2 500 500 http://archive.ubuntu.com/ubuntu yakkety/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: dconf-service 0.26.0-2 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Uname: Linux 4.8.0-22-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Oct 16 13:56:22 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2014-07-09 (829 days ago) InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 (20140708) SourcePackage: d-conf UpgradeStatus: Upgraded to yakkety on 2016-10-16 (0 days ago) ** Affects: d-conf (Ubuntu) Importance: Undecided Status: New ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug yakkety ** Attachment added: ".config/dconf/user the only file in .config/dconf" https://bugs.launchpad.net/bugs/1633905/+attachment/4762088/+files/user ** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to d-conf in Ubuntu. https://bugs.launchpad.net/bugs/1633905 Title: xenial to yakkety upgrade : "Activated service 'ca.desrt.dconf' failed" Status in d-conf package in Ubuntu: New Status in gnome-shell package in Ubuntu: New Bug description: 1) Upgraded from ubuntu 16.04 (xenial) to 16.10 (yakkety) Result: My /var/log/kern.log file was very quickly filling with MB and MB of messages of the form Oct 16 12:45:23 localhost gnome-shell[2655]: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ExecFailed: Failed to execute program ca.desrt.dconf: No such file or directory and my /var/log/syslog file was very quickly filling with MB and MB of messages of the form Oct 16 12:44:30 localhost gnome-shell[2655]: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ExecFailed: Failed to execute program ca.desrt.dconf: No such file or directory Oct 16 12:44:30 localhost dbus-daemon[2284]: Activating service name='ca.desrt.dconf' Oct 16 12:44:30 localhost dbus-daemon[2284]: Activated service 'ca.desrt.dconf' failed: Failed to execute program ca.desrt.dconf: No such file or directory Workaround: moved .config/dconf to a backup directory (contents attached), and restarted: while at least the kern.log logs keep coming, at least they are coming like one at a time over a long period of time rather than a million at a time, also gnome-shell seems much more stable now (it hasn't crashed since I did this). gnome-shell: Installed: 3.20.4-0ubuntu1 Candidate: 3.20.4-0ubuntu1 Version table: *** 3.20.4-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu yakkety/universe amd64 Packages 100 /var/lib/dpkg/status dconf-service: Installed: 0.26.0-2 Candidate: 0.26.0-2 Version table: *** 0.26.0-2 500 500 http://archive.ubuntu.com/ubuntu yakkety/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: dconf-service 0.26.0-2 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Uname: Linux 4.8.0-22-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Oct 16
[Touch-packages] [Bug 1633825] Re: System goes to emergency mode as /boot/efi could not be mounted
Booted into Windows 8 once and came back. Now audio and wifi starts automatically. Don't know if it is a coincidence. -- 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/1633825 Title: System goes to emergency mode as /boot/efi could not be mounted Status in systemd package in Ubuntu: New Bug description: System was booting normally with 16.04. Upgraded to 16.10, system goes to emergency console on every boot. This happened due to timeout in mounting /boot/efi. Commented out /boot/efi entry in /etc/fstab. System boots after that. But wifi, bluetooth and sound does not start automatically now. I have to load iwlwifi module to start wifi, snd_hda_intel to get sound working. I am using a Lenovo G50-80 laptop. Everything was working fine in 16.04. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: systemd 231-9git1 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Uname: Linux 4.8.0-22-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 Date: Sun Oct 16 15:22:05 2016 InstallationDate: Installed on 2015-11-20 (330 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:07dc Intel Corp. Bus 001 Device 003: ID 0c45:6513 Microdia Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80E5 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-22-generic.efi.signed root=UUID=e3865c00-93d9-4ed7-a9a4-35f9a0d1b16f ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to yakkety on 2016-10-15 (0 days ago) dmi.bios.date: 07/23/2015 dmi.bios.vendor: LENOVO dmi.bios.version: B0CN93WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lenovo G50-80 dmi.board.vendor: LENOVO dmi.board.version: 31900059 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G50-80 dmi.modalias: dmi:bvnLENOVO:bvrB0CN93WW:bd07/23/2015:svnLENOVO:pn80E5:pvrLenovoG50-80:rvnLENOVO:rnLenovoG50-80:rvr31900059WIN:cvnLENOVO:ct10:cvrLenovoG50-80: dmi.product.name: 80E5 dmi.product.version: Lenovo G50-80 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1633825/+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 1633900] [NEW] Wrong name displayed when 1 of 2 similar numbers selected
Public bug reported: I have stored 2 different contacts in my address book with similar numbers: Name 1 -> +43 1 9663*** (a landline number) Name 2 -> +43 699 19663*** (a cell phone number) The last 8 digits are the same in both numbers. What happens: If I select the 2nd number, the messaging app shows the name belonging to the 1st number (in both the compose view and in the history view). Because the number is not shown in the compose view, I don't see if I selected the correct contact. (BTW, the dialer app shows the wrong (1st) name as well if I select the 2nd contact. But I can check it because the number is shown as well.) What I expect to happen: If I select the 2nd number, the name belonging to the 2nd number should be displayed. Info: BQ Aquaris E4.5 Ubuntu Edition Ubuntu 15.04 (OTA-13) messaging-app 0.1+15.04.20160831-0ubuntu1 ** Affects: messaging-app (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to messaging-app in Ubuntu. https://bugs.launchpad.net/bugs/1633900 Title: Wrong name displayed when 1 of 2 similar numbers selected Status in messaging-app package in Ubuntu: New Bug description: I have stored 2 different contacts in my address book with similar numbers: Name 1 -> +43 1 9663*** (a landline number) Name 2 -> +43 699 19663*** (a cell phone number) The last 8 digits are the same in both numbers. What happens: If I select the 2nd number, the messaging app shows the name belonging to the 1st number (in both the compose view and in the history view). Because the number is not shown in the compose view, I don't see if I selected the correct contact. (BTW, the dialer app shows the wrong (1st) name as well if I select the 2nd contact. But I can check it because the number is shown as well.) What I expect to happen: If I select the 2nd number, the name belonging to the 2nd number should be displayed. Info: BQ Aquaris E4.5 Ubuntu Edition Ubuntu 15.04 (OTA-13) messaging-app 0.1+15.04.20160831-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/messaging-app/+bug/1633900/+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 1633890] [NEW] sudo password field allows other applications to steal focus
Public bug reported: When apport asks for the sudo passwords, other applications or dialogs can steal focus. This is inacceptable because it leads to leaked passwords. Moreover, it is inconvenient because the apport sudo dialog contains possibly a part of the password and the other application the other part, requiring to retype it. observed behavior: 1. apport asks for sudo rights. 2. I start typing the password. 3. network manager has disconnected from wifi and asks for wifi password, with the wifi password dialog getting focussed. 4. The remaining characters that I type go into the second application (network manager) with the enter key causing an unintended action. expected behavior: When typing a password, no other application can be focussed automatically (i.e. not by user action) until I have finished typing the password. This can be implemented as: - in all UI toolkits, if a password input field is focussed and the user is currently typing (timeout after last keys stroke), the application locks focus. - make sudo dialog system-modal, and the window manager does not allow anything else being focussed by non-user action. Ubuntu 16.04 apport-gtk 2.20.1-0ubuntu2.1 ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Description changed: When apport asks for the sudo passwords, other applications or dialogs can steal focus. This is inacceptable because it leads to leaked passwords. Moreover, it is inconvenient because the apport sudo dialog contains possibly a part of the password and the other application the other part, requiring to retype it. observed behavior: 1. apport asks for sudo rights. 2. I start typing the password. 3. network manager has disconnected from wifi and asks for wifi password, with the wifi password dialog getting focussed. 4. The remaining characters that I type go into the second application (network manager) with the enter key causing an unintended action. expected behavior: When typing a password, no other application can be focussed automatically (i.e. not by user action) until I have finished typing the password. This can be implemented as: - in all UI toolkits, if a password input field is focussed and the user is currently typing (timeout after last keys stroke), the application locks focus. - make sudo dialog system-modal, and the window manager does not allow anything else being focussed by non-user action. + + Ubuntu 16.04 + apport-gtk 2.20.1-0ubuntu2.1 -- 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/1633890 Title: sudo password field allows other applications to steal focus Status in apport package in Ubuntu: New Bug description: When apport asks for the sudo passwords, other applications or dialogs can steal focus. This is inacceptable because it leads to leaked passwords. Moreover, it is inconvenient because the apport sudo dialog contains possibly a part of the password and the other application the other part, requiring to retype it. observed behavior: 1. apport asks for sudo rights. 2. I start typing the password. 3. network manager has disconnected from wifi and asks for wifi password, with the wifi password dialog getting focussed. 4. The remaining characters that I type go into the second application (network manager) with the enter key causing an unintended action. expected behavior: When typing a password, no other application can be focussed automatically (i.e. not by user action) until I have finished typing the password. This can be implemented as: - in all UI toolkits, if a password input field is focussed and the user is currently typing (timeout after last keys stroke), the application locks focus. - make sudo dialog system-modal, and the window manager does not allow anything else being focussed by non-user action. Ubuntu 16.04 apport-gtk 2.20.1-0ubuntu2.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1633890/+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 1593924] Re: systemd-shim was not installed in 16.10 and now cannot purge or remove
To me this seems to be the problem : dpkg-divert: error: rename involves overwriting '/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service' with different file '/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd', not allowed Why does the package try to do this if it is not allowed? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libjpeg-turbo in Ubuntu. https://bugs.launchpad.net/bugs/1593924 Title: systemd-shim was not installed in 16.10 and now cannot purge or remove Status in libjpeg-turbo package in Ubuntu: Invalid Bug description: spsanchez@spsanchez-OEM:~$ sudo apt upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages will be REMOVED: systemd-shim 0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded. 1 not fully installed or removed. After this operation, 71.7 kB disk space will be freed. Do you want to continue? [Y/n] y (Reading database ... 63 files and directories currently installed.) Removing systemd-shim (9-1bzr4ubuntu1) ... Removing 'diversion of /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd by systemd-shim' dpkg-divert: error: rename involves overwriting '/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service' with different file '/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd', not allowed dpkg: error processing package systemd-shim (--remove): subprocess installed post-removal script returned error exit status 2 Errors were encountered while processing: systemd-shim E: Sub-process /usr/bin/dpkg returned an error code (1) spsanchez@spsanchez-OEM:~$ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libjpeg-turbo/+bug/1593924/+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 1633877] [NEW] VPN - "Additional Search Domains" Settings are being Ignored
Public bug reported: During configuring of a VPN, Network Manager normally allows you to specify "additional Search Domains" that are located on the virtual private network: http://neartalk.com/ss/2016-10-16_001_601x625.png However, in Ubuntu 16.10 the network manager is ignoring the "additional Search Domains" that I've specified at the dialog I've linked above. Normally, after connecting to a VPN (where additional Search Domains are specified), the command (below) will show (in addition to your local Search Domains) the remote Search Domains (located on the VPN): nmcli dev show | grep DOMAIN Unfortunately, in Ubuntu 16.10, this is not working. Consequently, I cannot resolve remote computers by their computer-name because the "Search Domains" I've specified are not getting appended to the computer-names I'm pinging. I've confirm this issue on both OpenVPN and Cisco vpnc connections. The additional Search Domains are not making it here: nmcli dev show | grep DOMAIN ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: network-manager 1.2.4-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Uname: Linux 4.8.0-22-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Sun Oct 16 10:16:04 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-10-13 (2 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.4connected started full enabled disabled disabled enabled enabled ** Affects: network-manager-applet Importance: Undecided Status: New ** Affects: network-manager-openvpn Importance: Undecided Status: New ** Affects: network-manager-vpnc Importance: Undecided Status: New ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug yakkety ** Also affects: network-manager-vpnc Importance: Undecided Status: New ** Also affects: network-manager-openvpn Importance: Undecided Status: New ** Also affects: network-manager-applet Importance: Undecided Status: New -- 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/1633877 Title: VPN - "Additional Search Domains" Settings are being Ignored Status in Network Manager Applet: New Status in NetworkManager-OpenVPN: New Status in network-manager-vpnc: New Status in network-manager package in Ubuntu: New Bug description: During configuring of a VPN, Network Manager normally allows you to specify "additional Search Domains" that are located on the virtual private network: http://neartalk.com/ss/2016-10-16_001_601x625.png However, in Ubuntu 16.10 the network manager is ignoring the "additional Search Domains" that I've specified at the dialog I've linked above. Normally, after connecting to a VPN (where additional Search Domains are specified), the command (below) will show (in addition to your local Search Domains) the remote Search Domains (located on the VPN): nmcli dev show | grep DOMAIN Unfortunately, in Ubuntu 16.10, this is not working. Consequently, I cannot resolve remote computers by their computer-name because the "Search Domains" I've specified are not getting appended to the computer-names I'm pinging. I've confirm this issue on both OpenVPN and Cisco vpnc connections. The additional Search Domains are not making it here: nmcli dev show | grep DOMAIN ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: network-manager 1.2.4-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Uname: Linux 4.8.0-22-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Sun Oct 16 10:16:04 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-10-13 (2 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.4connected started full enabled disabled disabled enabled enabled To manage notifications about this bug go to:
[Touch-packages] [Bug 1633852] Re: Blank screen on boot when using nvidia
** Description changed: The problem always happens when I try to use the nvidia graphics card using the command prime-select nvidia. When using prime-select intel it works fine. The baffling part is that I dual boot 2 Ubuntu installs... And the other one works fine. I can help try and figure out what seems to be wrong, I just don't know which files to diff. + - ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-43.63-generic 4.4.21 Uname: Linux 4.4.0-43-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: - NVRM version: NVIDIA UNIX x86_64 Kernel Module 361.42 Tue Mar 22 18:10:58 PDT 2016 - GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.2) + NVRM version: NVIDIA UNIX x86_64 Kernel Module 361.42 Tue Mar 22 18:10:58 PDT 2016 + GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.2) ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Sun Oct 16 13:48:35 2016 DistUpgraded: 2016-05-13 01:31:31,411 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (Failed to execute child process "./xorg_fix_proprietary.py" (No such file or directory)) DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: - Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) -Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics Controller [17aa:397d] - NVIDIA Corporation GF108M [GeForce GT 540M] [10de:0df4] (rev a1) (prog-if 00 [VGA controller]) -Subsystem: Lenovo GF108M [GeForce GT 540M] [17aa:397d] + Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) + Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics Controller [17aa:397d] + NVIDIA Corporation GF108M [GeForce GT 540M] [10de:0df4] (rev a1) (prog-if 00 [VGA controller]) + Subsystem: Lenovo GF108M [GeForce GT 540M] [17aa:397d] InstallationDate: Installed on 2014-12-31 (654 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: LENOVO HuronRiver Platform ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-43-generic.efi.signed root=UUID=dddc1c5f-ac3e-48b9-90c3-cd0effbf6a55 ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to xenial on 2016-05-13 (156 days ago) dmi.bios.date: 10/21/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 45CN38WW dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Emerald Lake dmi.board.vendor: LENOVO dmi.board.version: FAB1 dmi.chassis.asset.tag: Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnLENOVO:bvr45CN38WW:bd10/21/2011:svnLENOVO:pnHuronRiverPlatform:pvrIdeapadZ570:rvnLENOVO:rnEmeraldLake:rvrFAB1:cvnLENOVO:ct10:cvr0.1: dmi.product.name: HuronRiver Platform dmi.product.version: Ideapad Z570 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.1 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.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Sun Oct 16 13:45:12 2016 xserver.configfile: /etc/X11/xorg.conf xserver.errors: Screen 1 deleted because of no matching config section. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: - + xserver.version: 2:1.18.4-0ubuntu0.1 ** Also affects: nvidia-graphics-drivers-361 (Ubuntu) Importance: Undecided Status: New -- 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/1633852 Title: Blank screen on boot when using nvidia Status in nvidia-graphics-drivers-361 package in Ubuntu: New Status in xorg package in Ubuntu: New Bug description: The problem always happens when I try to use the nvidia
[Touch-packages] [Bug 1633874] [NEW] VPN - "Additional DNS servers" Settings are being Ignored
Public bug reported: During configuring of a VPN, Network Manager normally allows you to specify additional DNS servers that are located on the virtual private network: http://neartalk.com/ss/2016-10-16_001_601x625.png However, in Ubuntu 16.10 the network manager is ignoring the additional DNS that I've specified at the dialog I've linked above. Normally, after connecting to a VPN (where additional DNS servers are specified), the command (below) will show (in addition to your local DNS servers) the remote DNS servers (located on the VPN): nmcli dev show | grep DNS Unfortunately, in Ubuntu 16.10, this is not working. Consequently, I cannot resolve remote computers by their computer-name, which is very inconvenient considering that I have over 100 Remmina connections set to resolve by name. Right now, I have to manually discover the IP addresses of the remote computer-names before connecting to the computers with Remmina. I've confirm this issue on both OpenVPN and Cisco vpnc connections. The additional DNS server are not making it here: nmcli dev show | grep DNS ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: network-manager 1.2.4-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Uname: Linux 4.8.0-22-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Sun Oct 16 09:31:31 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-10-13 (2 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.4connected started full enabled enabled enabled enabled enabled ** Affects: network-manager-applet Importance: Undecided Status: New ** Affects: network-manager-openvpn Importance: Undecided Status: New ** Affects: network-manager-vpnc Importance: Undecided Status: New ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug yakkety ** Also affects: network-manager-openvpn Importance: Undecided Status: New ** Also affects: network-manager-vpnc Importance: Undecided Status: New ** Also affects: network-manager-applet Importance: Undecided Status: New ** Description changed: During configuring of a VPN, Network Manager normally allows you to specify additional DNS servers that are located on the virtual private network: http://neartalk.com/ss/2016-10-16_001_601x625.png However, in Ubuntu 16.10 the network manager is ignoring the additional DNS that I've specified at the dialog I've linked above. Normally, after connecting to a VPN (where additional DNS servers are specified), the command (below) will show (in addition to your local DNS - servers) the remote DNS servers located on the VPN: + servers) the remote DNS servers (located on the VPN): nmcli dev show | grep DNS Unfortunately, in Ubuntu 16.10, this is not working. Consequently, I cannot resolve remote computers by their computer-name, which is very inconvenient considering that I have over 100 Remmina connections set to resolve by name. Right now, I have to manually discover the IP addresses of the remote computer-names before connecting to the computers with Remmina. I've confirm this issue on both OpenVPN and Cisco vpnc connections. The additional DNS server are not making it here: nmcli dev show | grep DNS ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: network-manager 1.2.4-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Uname: Linux 4.8.0-22-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Sun Oct 16 09:31:31 2016 IfupdownConfig: - # interfaces(5) file used by ifup(8) and ifdown(8) - auto lo - iface lo inet loopback + # interfaces(5) file used by ifup(8) and ifdown(8) + auto lo + iface lo inet loopback InstallationDate: Installed on 2016-10-13 (2 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) NetworkManager.state: - [main] - NetworkingEnabled=true - WirelessEnabled=true - WWANEnabled=true + [main] + NetworkingEnabled=true + WirelessEnabled=true + WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: - RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN - running 1.2.4connected started full enabled enabled enabled enabled enabled + RUNNING VERSION STATE STARTUP
[Touch-packages] [Bug 1633873] [NEW] package tzdata 2016g-0ubuntu0.16.04 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 1
Public bug reported: after SO updates from ubuntu software every system start up i have a bug report problem. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: tzdata 2016g-0ubuntu0.16.04 ProcVersionSignature: Ubuntu 4.4.0-43.63-generic 4.4.21 Uname: Linux 4.4.0-43-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 AptOrdering: tzdata: Install tzdata: Configure NULL: ConfigurePending Architecture: amd64 Date: Sat Oct 15 21:03:20 2016 ErrorMessage: sub-processo script post-installation instalado retornou estado de saída de erro 1 InstallationDate: Installed on 2016-10-12 (3 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: tzdata Title: package tzdata 2016g-0ubuntu0.16.04 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: tzdata (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1633873 Title: package tzdata 2016g-0ubuntu0.16.04 failed to install/upgrade: sub- processo script post-installation instalado retornou estado de saída de erro 1 Status in tzdata package in Ubuntu: New Bug description: after SO updates from ubuntu software every system start up i have a bug report problem. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: tzdata 2016g-0ubuntu0.16.04 ProcVersionSignature: Ubuntu 4.4.0-43.63-generic 4.4.21 Uname: Linux 4.4.0-43-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 AptOrdering: tzdata: Install tzdata: Configure NULL: ConfigurePending Architecture: amd64 Date: Sat Oct 15 21:03:20 2016 ErrorMessage: sub-processo script post-installation instalado retornou estado de saída de erro 1 InstallationDate: Installed on 2016-10-12 (3 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: tzdata Title: package tzdata 2016g-0ubuntu0.16.04 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1633873/+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 1171435] Re: [AV200 - Xonar STX, recording] Microphone is not working on frontpanel
** Tags removed: wily ** Tags added: yakkety -- 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/1171435 Title: [AV200 - Xonar STX, recording] Microphone is not working on frontpanel Status in pulseaudio package in Ubuntu: Confirmed Bug description: Microphone is not working on frontpanel of my soundcard Asus Xonar Essence STX. In Windows it works normally. Workaround: 1. Start alsamixer from a terminal. 2. Press F6 to select the Xonar sound card 3. Press F4 to see recording controls. 4. Use arrow keys to find a control named "Mic Source" and change it from "Mic Jack" to "Front Panel". Still actual for: Ubuntu 16.04 x64 4.3.0-2-generic ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 Uname: Linux 3.9.0-030900rc8-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: simplehuman 2394 F pulseaudio /dev/snd/pcmC0D0c: simplehuman 2394 F...m pulseaudio /dev/snd/controlC1: simplehuman 2394 F pulseaudio Date: Mon Apr 22 15:06:32 2013 InstallationDate: Installed on 2013-02-14 (67 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MarkForUpload: True PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:STX failed Symptom_Card: GF110 High Definition Audio Controller - HDA NVidia Symptom_Type: None of the above Title: [AV200 - Xonar STX, recording] Recording problem UpgradeStatus: Upgraded to raring on 2013-02-14 (67 days ago) dmi.bios.date: 08/09/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1402 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: SABERTOOTH X58 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1402:bd08/09/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnSABERTOOTHX58:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1171435/+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 1288182] Re: Cyrillic not displayed in the input field
Yakkety is also affected, adding tag "yakkety" ** Tags removed: wily -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1288182 Title: Cyrillic not displayed in the input field Status in Evince: Unknown Status in Poppler: Confirmed Status in evince package in Ubuntu: Triaged Status in poppler package in Ubuntu: Invalid Bug description: Ubuntu 14.04 x64 Evince 3.10.3 Cyrillic not displayed in the input field. In attach screenshot: input field with text 'This сyrillic: "Кириллица"' Upd. Still actual for Ubuntu 16.04 x64 Evince 3.18.2 To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/1288182/+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 1633858] [NEW] package python2.7 2.7.12-1~16.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: update error ProblemType: Package DistroRelease: Ubuntu 16.04 Package: python2.7 2.7.12-1~16.04 ProcVersionSignature: Ubuntu 4.4.0-43.63-generic 4.4.21 Uname: Linux 4.4.0-43-generic i686 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: i386 Date: Sun Oct 16 07:47:38 2016 DpkgHistoryLog: Start-Date: 2016-10-16 07:22:42 Requested-By: marcos (1000) Install: linux-headers-4.4.0-43-generic:i386 (4.4.0-43.63, automatic) Upgrade: linux-headers-generic:i386 (4.4.0.38.40, 4.4.0.43.45), xserver-common:i386 (2:1.18.3-1ubuntu2.3, 2:1.18.4-0ubuntu0.1), xserver-xorg-core:i386 (2:1.18.3-1ubuntu2.3, 2:1.18.4-0ubuntu0.1), libsystemd0:i386 (229-4ubuntu10, 229-4ubuntu11), udev:i386 (229-4ubuntu10, 229-4ubuntu11), network-manager:i386 (1.2.2-0ubuntu0.16.04.1, 1.2.2-0ubuntu0.16.04.3), libudev1:i386 (229-4ubuntu10, 229-4ubuntu11), linux-headers-4.4.0-43:i386 (4.4.0-43.63, 4.4.0-43.63), systemd-sysv:i386 (229-4ubuntu10, 229-4ubuntu11), libpam-systemd:i386 (229-4ubuntu10, 229-4ubuntu11), systemd:i386 (229-4ubuntu10, 229-4ubuntu11) ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2016-10-05 (11 days ago) InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: python2.7 Title: package python2.7 2.7.12-1~16.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: python2.7 (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/1633858 Title: package python2.7 2.7.12-1~16.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in python2.7 package in Ubuntu: New Bug description: update error ProblemType: Package DistroRelease: Ubuntu 16.04 Package: python2.7 2.7.12-1~16.04 ProcVersionSignature: Ubuntu 4.4.0-43.63-generic 4.4.21 Uname: Linux 4.4.0-43-generic i686 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: i386 Date: Sun Oct 16 07:47:38 2016 DpkgHistoryLog: Start-Date: 2016-10-16 07:22:42 Requested-By: marcos (1000) Install: linux-headers-4.4.0-43-generic:i386 (4.4.0-43.63, automatic) Upgrade: linux-headers-generic:i386 (4.4.0.38.40, 4.4.0.43.45), xserver-common:i386 (2:1.18.3-1ubuntu2.3, 2:1.18.4-0ubuntu0.1), xserver-xorg-core:i386 (2:1.18.3-1ubuntu2.3, 2:1.18.4-0ubuntu0.1), libsystemd0:i386 (229-4ubuntu10, 229-4ubuntu11), udev:i386 (229-4ubuntu10, 229-4ubuntu11), network-manager:i386 (1.2.2-0ubuntu0.16.04.1, 1.2.2-0ubuntu0.16.04.3), libudev1:i386 (229-4ubuntu10, 229-4ubuntu11), linux-headers-4.4.0-43:i386 (4.4.0-43.63, 4.4.0-43.63), systemd-sysv:i386 (229-4ubuntu10, 229-4ubuntu11), libpam-systemd:i386 (229-4ubuntu10, 229-4ubuntu11), systemd:i386 (229-4ubuntu10, 229-4ubuntu11) ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2016-10-05 (11 days ago) InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: python2.7 Title: package python2.7 2.7.12-1~16.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1633858/+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 1633749] Re: Double login to switch back to my session after closing the guest session
The log shows LightDM doing the correct thing - it unlocks the logind session when you get to the greeter. I suspect that Unity has regressed and is not removing its lock screen when this occurs. ** Also affects: unity (Ubuntu) Importance: Undecided Status: New ** Changed in: unity (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1633749 Title: Double login to switch back to my session after closing the guest session Status in lightdm package in Ubuntu: Triaged Status in unity package in Ubuntu: New Bug description: Ubuntu 16.10 x64 * I have my session open and want to temporarily switch to the guest session. I click on the appropriate item (top right menu of Unity). * I am now on the guest session. After I'm done, I close the guest session. * I am now in front of a screen where I can input my password to go back to my session. The wallpaper is the default Ubuntu wallpaper as when I am not logged in. * After I validate my password, another screen is displayed that asks my again to enter my password. That time, the wallpaper is my personnal wallpaper I have in my session. * I enter my password again and I am back to my session. I did not have to enter my password twice in previous versions of Ubuntu when switching of sessions. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: lightdm 1.19.5-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Uname: Linux 4.8.0-22-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Sat Oct 15 18:26:17 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-10-14 (0 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1633749/+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 1632772] Re: GNOME on Wayland does not start from LightDM
Can you attach the contents of /var/log/lightdm/lightdm.log after attempting to start the session? Thanks. ** Changed in: lightdm (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1632772 Title: GNOME on Wayland does not start from LightDM Status in gnome-session package in Ubuntu: New Status in lightdm package in Ubuntu: Incomplete Bug description: When picking GNOME on Wayland as session and attempting to login from LightDM then it fails, all you see is a black screen with a blinking cursor. However, manually running: $ dbus-run-session gnome-shell --display-server --wayland from the console/vt1 (Ctrl+Alt+F1) seems to work. But from LightDM it does not work. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: gnome-session-wayland 3.20.2-1ubuntu7 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Uname: Linux 4.8.0-22-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 Date: Wed Oct 12 18:06:13 2016 InstallationDate: Installed on 2013-12-26 (1020 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1632772/+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 1633852] [NEW] Blank screen on boot when using nvidia
Public bug reported: The problem always happens when I try to use the nvidia graphics card using the command prime-select nvidia. When using prime-select intel it works fine. The baffling part is that I dual boot 2 Ubuntu installs... And the other one works fine. I can help try and figure out what seems to be wrong, I just don't know which files to diff. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-43.63-generic 4.4.21 Uname: Linux 4.4.0-43-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 361.42 Tue Mar 22 18:10:58 PDT 2016 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.2) ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Sun Oct 16 13:48:35 2016 DistUpgraded: 2016-05-13 01:31:31,411 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (Failed to execute child process "./xorg_fix_proprietary.py" (No such file or directory)) DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics Controller [17aa:397d] NVIDIA Corporation GF108M [GeForce GT 540M] [10de:0df4] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo GF108M [GeForce GT 540M] [17aa:397d] InstallationDate: Installed on 2014-12-31 (654 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: LENOVO HuronRiver Platform ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-43-generic.efi.signed root=UUID=dddc1c5f-ac3e-48b9-90c3-cd0effbf6a55 ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to xenial on 2016-05-13 (156 days ago) dmi.bios.date: 10/21/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 45CN38WW dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Emerald Lake dmi.board.vendor: LENOVO dmi.board.version: FAB1 dmi.chassis.asset.tag: Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnLENOVO:bvr45CN38WW:bd10/21/2011:svnLENOVO:pnHuronRiverPlatform:pvrIdeapadZ570:rvnLENOVO:rnEmeraldLake:rvrFAB1:cvnLENOVO:ct10:cvr0.1: dmi.product.name: HuronRiver Platform dmi.product.version: Ideapad Z570 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.1 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.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Sun Oct 16 13:45:12 2016 xserver.configfile: /etc/X11/xorg.conf xserver.errors: Screen 1 deleted because of no matching config section. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.4-0ubuntu0.1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug possible-manual-nvidia-install 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/1633852 Title: Blank screen on boot when using nvidia Status in xorg package in Ubuntu: New Bug description: The problem always happens when I try to use the nvidia graphics card using the command prime-select nvidia. When using prime-select intel it works fine. The baffling part is that I dual boot 2 Ubuntu installs... And the other one works fine. I can help try and figure out what seems to be wrong, I just don't know which files to diff. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-43.63-generic 4.4.21 Uname: Linux 4.4.0-43-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX
[Touch-packages] [Bug 1171435] Re: [AV200 - Xonar STX, recording] Microphone is not working on frontpanel
** Tags removed: vivid -- 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/1171435 Title: [AV200 - Xonar STX, recording] Microphone is not working on frontpanel Status in pulseaudio package in Ubuntu: Confirmed Bug description: Microphone is not working on frontpanel of my soundcard Asus Xonar Essence STX. In Windows it works normally. Workaround: 1. Start alsamixer from a terminal. 2. Press F6 to select the Xonar sound card 3. Press F4 to see recording controls. 4. Use arrow keys to find a control named "Mic Source" and change it from "Mic Jack" to "Front Panel". Still actual for: Ubuntu 16.04 x64 4.3.0-2-generic ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 Uname: Linux 3.9.0-030900rc8-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: simplehuman 2394 F pulseaudio /dev/snd/pcmC0D0c: simplehuman 2394 F...m pulseaudio /dev/snd/controlC1: simplehuman 2394 F pulseaudio Date: Mon Apr 22 15:06:32 2013 InstallationDate: Installed on 2013-02-14 (67 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MarkForUpload: True PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:STX failed Symptom_Card: GF110 High Definition Audio Controller - HDA NVidia Symptom_Type: None of the above Title: [AV200 - Xonar STX, recording] Recording problem UpgradeStatus: Upgraded to raring on 2013-02-14 (67 days ago) dmi.bios.date: 08/09/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1402 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: SABERTOOTH X58 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1402:bd08/09/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnSABERTOOTHX58:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1171435/+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 1288182] Re: Cyrillic not displayed in the input field
** Tags removed: vivid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1288182 Title: Cyrillic not displayed in the input field Status in Evince: Unknown Status in Poppler: Confirmed Status in evince package in Ubuntu: Triaged Status in poppler package in Ubuntu: Invalid Bug description: Ubuntu 14.04 x64 Evince 3.10.3 Cyrillic not displayed in the input field. In attach screenshot: input field with text 'This сyrillic: "Кириллица"' Upd. Still actual for Ubuntu 16.04 x64 Evince 3.18.2 To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/1288182/+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 1620806] Re: gedit edit window is transparent when using Ambiance and Radiance themes
** Changed in: ubuntu-themes (Ubuntu) Status: Incomplete => New -- 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/1620806 Title: gedit edit window is transparent when using Ambiance and Radiance themes Status in gedit package in Ubuntu: New Status in ubuntu-themes package in Ubuntu: New Bug description: In a freshly booted and fully updated Ubuntu 16.10 the edit window of gedit is transparent using the *Classic* colour scheme. Other colour schemes seem to work as intended. The text of loaded files shows against the desktop wallpaper but when no files are loaded gedit displays its edit window or pane as it should do. To clarify this bug is only apparent when a file is loaded. I don't know when this started as I don't normally used gedit to edit files. I haven't found any other application affected by this problem. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: gedit 3.20.2-2ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16 Uname: Linux 4.4.0-9136-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: Unity Date: Tue Sep 6 21:01:35 2016 InstallationDate: Installed on 2016-03-11 (179 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160311) SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1620806/+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 1620806] Re: gedit edit window is transparent when using Ambiance and Radiance themes
I see this bug after upgrading 16.04 to 16.10 just now. ** Changed in: gedit (Ubuntu) Status: Incomplete => New -- 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/1620806 Title: gedit edit window is transparent when using Ambiance and Radiance themes Status in gedit package in Ubuntu: New Status in ubuntu-themes package in Ubuntu: Incomplete Bug description: In a freshly booted and fully updated Ubuntu 16.10 the edit window of gedit is transparent using the *Classic* colour scheme. Other colour schemes seem to work as intended. The text of loaded files shows against the desktop wallpaper but when no files are loaded gedit displays its edit window or pane as it should do. To clarify this bug is only apparent when a file is loaded. I don't know when this started as I don't normally used gedit to edit files. I haven't found any other application affected by this problem. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: gedit 3.20.2-2ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16 Uname: Linux 4.4.0-9136-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: Unity Date: Tue Sep 6 21:01:35 2016 InstallationDate: Installed on 2016-03-11 (179 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160311) SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1620806/+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 1633845] [NEW] network-manager does not connect to wifi
Public bug reported: When trying to connect to wifi network, network-manager remains blocked in waiting for authentification state then fails after cca 1min. This started to happen after I updated to kubuntu 16.10. Stopping network manager from service and trying to manually connect with wpa_supplicant works fine. The only way to fix this for me was to stop network manager and/or networking and restart the services sometimes more than once. os: Kubuntu 16.10 network-manager: 1.2.4 hardware: dell xps 9550 network controller: BCM43602 ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- 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/1633845 Title: network-manager does not connect to wifi Status in network-manager package in Ubuntu: New Bug description: When trying to connect to wifi network, network-manager remains blocked in waiting for authentification state then fails after cca 1min. This started to happen after I updated to kubuntu 16.10. Stopping network manager from service and trying to manually connect with wpa_supplicant works fine. The only way to fix this for me was to stop network manager and/or networking and restart the services sometimes more than once. os: Kubuntu 16.10 network-manager: 1.2.4 hardware: dell xps 9550 network controller: BCM43602 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1633845/+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 1633791] Re: package tzdata 2016g-0ubuntu0.16.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: tzdata (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1633791 Title: package tzdata 2016g-0ubuntu0.16.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in tzdata package in Ubuntu: Confirmed Bug description: package tzdata 2016g-0ubuntu0.16.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: tzdata 2016g-0ubuntu0.16.04 ProcVersionSignature: Ubuntu 4.4.0-42.62-generic 4.4.21 Uname: Linux 4.4.0-42-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Sat Oct 15 21:22:58 2016 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2016-06-30 (107 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: tzdata Title: package tzdata 2016g-0ubuntu0.16.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1633791/+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 1633792] Re: package tzdata 2016g-0ubuntu0.16.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
*** This bug is a duplicate of bug 1633791 *** https://bugs.launchpad.net/bugs/1633791 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1633791, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1633791 package tzdata 2016g-0ubuntu0.16.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1633792 Title: package tzdata 2016g-0ubuntu0.16.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in tzdata package in Ubuntu: New Bug description: Fault when I was updating the system ProblemType: Package DistroRelease: Ubuntu 16.04 Package: tzdata 2016g-0ubuntu0.16.04 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 Uname: Linux 4.4.0-34-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Sat Oct 15 21:23:45 2016 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2016-07-10 (97 days ago) InstallationMedia: PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: tzdata Title: package tzdata 2016g-0ubuntu0.16.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1633792/+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 1633827] Re: Screen goes black on NVidia card
The workaround seems to produce side effects (in dconf the color spec is entered with double digits. See screenshot) Should that be the aspired behaviour? ** Attachment added: "Screenshot from 2016-10-16 12-32-30.png" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1633827/+attachment/4761864/+files/Screenshot%20from%202016-10-16%2012-32-30.png -- 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/1633827 Title: Screen goes black on NVidia card Status in xorg package in Ubuntu: New Bug description: I've set my desktop to show a gradient blue (standard dark blue to middle blue from the selection box). After resume from suspend the screen was black. This happened before when running an application that covered 70% of the screen (a black banner on the bottom of the screen 50% of screen hight). Workaround: System Settings -> Appearance -> Colors & Gradients choose single color (will switch to blue) choose gradient again (will show two previously selected colors) Screen changes accordingly The graphics card works fine. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Uname: Linux 4.8.0-22-generic x86_64 NonfreeKernelModules: nvidia_uvm wl nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 367.57 Mon Oct 3 20:37:01 PDT 2016 GCC version: gcc version 6.2.0 20161005 (Ubuntu 6.2.0-5ubuntu12) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sun Oct 16 11:56:55 2016 DistUpgraded: 2016-10-15 12:59:20,764 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process "./xorg_fix_proprietary.py" (No such file or directory) (8)) DistroCodename: yakkety DistroVariant: ubuntu GconfCompiz: /apps/compiz-1/general: /apps/compiz-1/general/screen0: /apps/compiz-1/general/screen0/options: active_plugins = [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus] GraphicsCard: NVIDIA Corporation GK107M [GeForce GT 650M Mac Edition] [10de:0fd5] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. GK107M [GeForce GT 650M Mac Edition] [106b:00f2] InstallationDate: Installed on 2013-05-17 (1247 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64+mac (20130424) MachineType: Apple Inc. MacBookPro10,1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-22-generic root=UUID=3679e976-6405-4981-aa99-8c79d15e6aa3 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to yakkety on 2016-10-15 (0 days ago) dmi.bios.date: 12/21/2012 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP101.88Z.00EE.B03.1212211437 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-C3EC7CD22292981F dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro10,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-C3EC7CD22292981F dmi.modalias: dmi:bvnAppleInc.:bvrMBP101.88Z.00EE.B03.1212211437:bd12/21/2012:svnAppleInc.:pnMacBookPro10,1:pvr1.0:rvnAppleInc.:rnMac-C3EC7CD22292981F:rvrMacBookPro10,1:cvnAppleInc.:ct10:cvrMac-C3EC7CD22292981F: dmi.product.name: MacBookPro10,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6
[Touch-packages] [Bug 1633830] [NEW] No sound from the front headphone jack. Shows "unplugged" always. Able to fix by fiddling with pulseaudio profiles somehow
Public bug reported: Will update later ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-42.62-generic 4.4.21 Uname: Linux 4.4.0-42-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: GNOME-Classic:GNOME Date: Sun Oct 16 13:18:00 2016 InstallationDate: Installed on 2016-09-22 (24 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Green Headphone Out, Front Symptom_Type: No sound at all Title: [MS-7918, Realtek ALC1150, Green Headphone Out, Front] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/28/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V2.9 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97 GAMING 3 (MS-7918) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV2.9:bd08/28/2015:svnMSI:pnMS-7918:pvr1.0:rvnMSI:rnZ97GAMING3(MS-7918):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.name: MS-7918 dmi.product.version: 1.0 dmi.sys.vendor: MSI mtime.conffile..etc.modprobe.d.alsa-base.conf: 2016-09-24T08:49:07.298623 ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1633830 Title: No sound from the front headphone jack. Shows "unplugged" always. Able to fix by fiddling with pulseaudio profiles somehow Status in alsa-driver package in Ubuntu: New Bug description: Will update later ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-42.62-generic 4.4.21 Uname: Linux 4.4.0-42-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: GNOME-Classic:GNOME Date: Sun Oct 16 13:18:00 2016 InstallationDate: Installed on 2016-09-22 (24 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Green Headphone Out, Front Symptom_Type: No sound at all Title: [MS-7918, Realtek ALC1150, Green Headphone Out, Front] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/28/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V2.9 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97 GAMING 3 (MS-7918) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV2.9:bd08/28/2015:svnMSI:pnMS-7918:pvr1.0:rvnMSI:rnZ97GAMING3(MS-7918):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.name: MS-7918 dmi.product.version: 1.0 dmi.sys.vendor: MSI mtime.conffile..etc.modprobe.d.alsa-base.conf: 2016-09-24T08:49:07.298623 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1633830/+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 1606159] Re: Battery not recognized on HP Pavilion Detachable X2 10-N123NF
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: upower (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1606159 Title: Battery not recognized on HP Pavilion Detachable X2 10-N123NF Status in upower package in Ubuntu: Confirmed Bug description: After a clean install of xenial on HP Pavilion Detachable X2 10-N123NF, the battery is not "seen" at all. It doesn't appear in Ubuntu's "energy" tab. # acpi No support for device type: power_supply However...: # lshw -class power USB *-battery description: Lithium Ion Battery product: O02033X vendor: 333-42-D7 physical id: 1 version: 02/07/2026 serial: 01794 02/07/2026 slot: Primary capacity: 33060mWh configuration: voltage=3.8V *-power UNCLAIMED description: OEM Define 1 product: OEM Define 5 vendor: OEM Define 2 physical id: 2 version: OEM Define 6 serial: OEM Define 3 capacity: 42mWh ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: acpi-support 0.142 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Mon Jul 25 10:55:19 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-07-22 (3 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: acpi-support UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1606159/+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 1633827] Re: Screen goes black on NVidia card
When screen blanks partially, the workaround described above does not work. -- 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/1633827 Title: Screen goes black on NVidia card Status in xorg package in Ubuntu: New Bug description: I've set my desktop to show a gradient blue (standard dark blue to middle blue from the selection box). After resume from suspend the screen was black. This happened before when running an application that covered 70% of the screen (a black banner on the bottom of the screen 50% of screen hight). Workaround: System Settings -> Appearance -> Colors & Gradients choose single color (will switch to blue) choose gradient again (will show two previously selected colors) Screen changes accordingly The graphics card works fine. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Uname: Linux 4.8.0-22-generic x86_64 NonfreeKernelModules: nvidia_uvm wl nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 367.57 Mon Oct 3 20:37:01 PDT 2016 GCC version: gcc version 6.2.0 20161005 (Ubuntu 6.2.0-5ubuntu12) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sun Oct 16 11:56:55 2016 DistUpgraded: 2016-10-15 12:59:20,764 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process "./xorg_fix_proprietary.py" (No such file or directory) (8)) DistroCodename: yakkety DistroVariant: ubuntu GconfCompiz: /apps/compiz-1/general: /apps/compiz-1/general/screen0: /apps/compiz-1/general/screen0/options: active_plugins = [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus] GraphicsCard: NVIDIA Corporation GK107M [GeForce GT 650M Mac Edition] [10de:0fd5] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. GK107M [GeForce GT 650M Mac Edition] [106b:00f2] InstallationDate: Installed on 2013-05-17 (1247 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64+mac (20130424) MachineType: Apple Inc. MacBookPro10,1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-22-generic root=UUID=3679e976-6405-4981-aa99-8c79d15e6aa3 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to yakkety on 2016-10-15 (0 days ago) dmi.bios.date: 12/21/2012 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP101.88Z.00EE.B03.1212211437 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-C3EC7CD22292981F dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro10,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-C3EC7CD22292981F dmi.modalias: dmi:bvnAppleInc.:bvrMBP101.88Z.00EE.B03.1212211437:bd12/21/2012:svnAppleInc.:pnMacBookPro10,1:pvr1.0:rvnAppleInc.:rnMac-C3EC7CD22292981F:rvrMacBookPro10,1:cvnAppleInc.:ct10:cvrMac-C3EC7CD22292981F: dmi.product.name: MacBookPro10,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 version.xserver-xorg-video-nouveau:
[Touch-packages] [Bug 1633827] Re: Screen goes black on NVidia card
** Attachment added: "Blanked portion of screen" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1633827/+attachment/4761854/+files/Screenshot%20from%202016-10-16%2012-17-39.png -- 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/1633827 Title: Screen goes black on NVidia card Status in xorg package in Ubuntu: New Bug description: I've set my desktop to show a gradient blue (standard dark blue to middle blue from the selection box). After resume from suspend the screen was black. This happened before when running an application that covered 70% of the screen (a black banner on the bottom of the screen 50% of screen hight). Workaround: System Settings -> Appearance -> Colors & Gradients choose single color (will switch to blue) choose gradient again (will show two previously selected colors) Screen changes accordingly The graphics card works fine. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Uname: Linux 4.8.0-22-generic x86_64 NonfreeKernelModules: nvidia_uvm wl nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 367.57 Mon Oct 3 20:37:01 PDT 2016 GCC version: gcc version 6.2.0 20161005 (Ubuntu 6.2.0-5ubuntu12) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sun Oct 16 11:56:55 2016 DistUpgraded: 2016-10-15 12:59:20,764 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process "./xorg_fix_proprietary.py" (No such file or directory) (8)) DistroCodename: yakkety DistroVariant: ubuntu GconfCompiz: /apps/compiz-1/general: /apps/compiz-1/general/screen0: /apps/compiz-1/general/screen0/options: active_plugins = [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus] GraphicsCard: NVIDIA Corporation GK107M [GeForce GT 650M Mac Edition] [10de:0fd5] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. GK107M [GeForce GT 650M Mac Edition] [106b:00f2] InstallationDate: Installed on 2013-05-17 (1247 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64+mac (20130424) MachineType: Apple Inc. MacBookPro10,1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-22-generic root=UUID=3679e976-6405-4981-aa99-8c79d15e6aa3 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to yakkety on 2016-10-15 (0 days ago) dmi.bios.date: 12/21/2012 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP101.88Z.00EE.B03.1212211437 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-C3EC7CD22292981F dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro10,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-C3EC7CD22292981F dmi.modalias: dmi:bvnAppleInc.:bvrMBP101.88Z.00EE.B03.1212211437:bd12/21/2012:svnAppleInc.:pnMacBookPro10,1:pvr1.0:rvnAppleInc.:rnMac-C3EC7CD22292981F:rvrMacBookPro10,1:cvnAppleInc.:ct10:cvrMac-C3EC7CD22292981F: dmi.product.name: MacBookPro10,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1
[Touch-packages] [Bug 1633825] [NEW] System goes to emergency mode as /boot/efi could not be mounted
Public bug reported: System was booting normally with 16.04. Upgraded to 16.10, system goes to emergency console on every boot. This happened due to timeout in mounting /boot/efi. Commented out /boot/efi entry in /etc/fstab. System boots after that. But wifi, bluetooth and sound does not start automatically now. I have to load iwlwifi module to start wifi, snd_hda_intel to get sound working. I am using a Lenovo G50-80 laptop. Everything was working fine in 16.04. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: systemd 231-9git1 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Uname: Linux 4.8.0-22-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 Date: Sun Oct 16 15:22:05 2016 InstallationDate: Installed on 2015-11-20 (330 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:07dc Intel Corp. Bus 001 Device 003: ID 0c45:6513 Microdia Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80E5 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-22-generic.efi.signed root=UUID=e3865c00-93d9-4ed7-a9a4-35f9a0d1b16f ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to yakkety on 2016-10-15 (0 days ago) dmi.bios.date: 07/23/2015 dmi.bios.vendor: LENOVO dmi.bios.version: B0CN93WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lenovo G50-80 dmi.board.vendor: LENOVO dmi.board.version: 31900059 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G50-80 dmi.modalias: dmi:bvnLENOVO:bvrB0CN93WW:bd07/23/2015:svnLENOVO:pn80E5:pvrLenovoG50-80:rvnLENOVO:rnLenovoG50-80:rvr31900059WIN:cvnLENOVO:ct10:cvrLenovoG50-80: dmi.product.name: 80E5 dmi.product.version: Lenovo G50-80 dmi.sys.vendor: LENOVO ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug yakkety -- 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/1633825 Title: System goes to emergency mode as /boot/efi could not be mounted Status in systemd package in Ubuntu: New Bug description: System was booting normally with 16.04. Upgraded to 16.10, system goes to emergency console on every boot. This happened due to timeout in mounting /boot/efi. Commented out /boot/efi entry in /etc/fstab. System boots after that. But wifi, bluetooth and sound does not start automatically now. I have to load iwlwifi module to start wifi, snd_hda_intel to get sound working. I am using a Lenovo G50-80 laptop. Everything was working fine in 16.04. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: systemd 231-9git1 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Uname: Linux 4.8.0-22-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 Date: Sun Oct 16 15:22:05 2016 InstallationDate: Installed on 2015-11-20 (330 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:07dc Intel Corp. Bus 001 Device 003: ID 0c45:6513 Microdia Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80E5 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-22-generic.efi.signed root=UUID=e3865c00-93d9-4ed7-a9a4-35f9a0d1b16f ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to yakkety on 2016-10-15 (0 days ago) dmi.bios.date: 07/23/2015 dmi.bios.vendor: LENOVO dmi.bios.version: B0CN93WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lenovo G50-80 dmi.board.vendor: LENOVO dmi.board.version: 31900059 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G50-80 dmi.modalias: dmi:bvnLENOVO:bvrB0CN93WW:bd07/23/2015:svnLENOVO:pn80E5:pvrLenovoG50-80:rvnLENOVO:rnLenovoG50-80:rvr31900059WIN:cvnLENOVO:ct10:cvrLenovoG50-80: dmi.product.name: 80E5 dmi.product.version: Lenovo G50-80 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1633825/+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 1633827] [NEW] Screen goes black on NVidia card
Public bug reported: I've set my desktop to show a gradient blue (standard dark blue to middle blue from the selection box). After resume from suspend the screen was black. This happened before when running an application that covered 70% of the screen (a black banner on the bottom of the screen 50% of screen hight). Workaround: System Settings -> Appearance -> Colors & Gradients choose single color (will switch to blue) choose gradient again (will show two previously selected colors) Screen changes accordingly The graphics card works fine. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Uname: Linux 4.8.0-22-generic x86_64 NonfreeKernelModules: nvidia_uvm wl nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 367.57 Mon Oct 3 20:37:01 PDT 2016 GCC version: gcc version 6.2.0 20161005 (Ubuntu 6.2.0-5ubuntu12) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sun Oct 16 11:56:55 2016 DistUpgraded: 2016-10-15 12:59:20,764 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process "./xorg_fix_proprietary.py" (No such file or directory) (8)) DistroCodename: yakkety DistroVariant: ubuntu GconfCompiz: /apps/compiz-1/general: /apps/compiz-1/general/screen0: /apps/compiz-1/general/screen0/options: active_plugins = [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus] GraphicsCard: NVIDIA Corporation GK107M [GeForce GT 650M Mac Edition] [10de:0fd5] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. GK107M [GeForce GT 650M Mac Edition] [106b:00f2] InstallationDate: Installed on 2013-05-17 (1247 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64+mac (20130424) MachineType: Apple Inc. MacBookPro10,1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-22-generic root=UUID=3679e976-6405-4981-aa99-8c79d15e6aa3 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to yakkety on 2016-10-15 (0 days ago) dmi.bios.date: 12/21/2012 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP101.88Z.00EE.B03.1212211437 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-C3EC7CD22292981F dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro10,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-C3EC7CD22292981F dmi.modalias: dmi:bvnAppleInc.:bvrMBP101.88Z.00EE.B03.1212211437:bd12/21/2012:svnAppleInc.:pnMacBookPro10,1:pvr1.0:rvnAppleInc.:rnMac-C3EC7CD22292981F:rvrMacBookPro10,1:cvnAppleInc.:ct10:cvrMac-C3EC7CD22292981F: dmi.product.name: MacBookPro10,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2 xserver.bootTime: Sun Oct 16 11:21:42 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.4-1ubuntu6 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 corruption ubuntu yakkety -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu.
[Touch-packages] [Bug 1633828] [NEW] Mounting /boot/efi fails always after updating to 16.10
Public bug reported: System does not boot properly as mounting /boot/efi fails. Commented out /boot/efi entry in /etc/fstab to boot system normally. This started happening after update to 16.10. Everything was working fine in 15.10, 16.04. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: mount 2.28.2-1ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Uname: Linux 4.8.0-22-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 Date: Sun Oct 16 15:23:19 2016 InstallationDate: Installed on 2015-11-20 (330 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: util-linux UpgradeStatus: Upgraded to yakkety on 2016-10-15 (0 days ago) ** Affects: util-linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug yakkety -- 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/1633828 Title: Mounting /boot/efi fails always after updating to 16.10 Status in util-linux package in Ubuntu: New Bug description: System does not boot properly as mounting /boot/efi fails. Commented out /boot/efi entry in /etc/fstab to boot system normally. This started happening after update to 16.10. Everything was working fine in 15.10, 16.04. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: mount 2.28.2-1ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Uname: Linux 4.8.0-22-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 Date: Sun Oct 16 15:23:19 2016 InstallationDate: Installed on 2015-11-20 (330 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: util-linux UpgradeStatus: Upgraded to yakkety on 2016-10-15 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1633828/+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 1518483] Re: problem with PIE binaries and kernels <= 3.19
sbeattie: Any chance of building bash with pie in the future? 16.10 has 4.8 as default kernel, so disabling pie should not be necessary anymore!? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1518483 Title: problem with PIE binaries and kernels <= 3.19 Status in bash package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in bash source package in Vivid: Won't Fix Status in linux source package in Vivid: Fix Released Bug description: When bash is built as a Position Independent Executable (PIE), it very sporadically crashes due to some issue with memory layout in kernels before 4.2. I'm currently testing enabling PIE by default in gcc on amd64 for xenial, and some of my builds (e.g. cpio) are failing in the buildds with the following message emitted: bash: xmalloc: .././locale.c:81: cannot allocate 2 bytes (0 bytes allocated) when the bash that is used is built as PIE. I have seen these failures on buildds where the host is running 3.13 and 3.19. I am also able to reproduce this locally on a machine running trusty with the stock trusty kernel. However, when I boot that same machine with the linux- lts-wily (4.2) kernel and retry the build with everything else exactly the same, the failure disappears. I discussed this a bit with Kees Cook, and he noted that some cleanups to the kernel's ASLR code happened in 4.1. Specifically, he noted: commit a87938b2e246b81b4fb713edb371a9fa3c5c3c86 Author: Michael Davidsonfs/binfmt_elf.c: fix bug in loading of PIE binaries However, that landed in stable and has been picked up in our kernels as 668965be56ea0b2c45ed6bec84dc2088490ae6b1, landing in Ubuntu-3.13.0-56.93 and b51621abbcb4694b8d2842ce3a66006a60bba6e5 / Ubuntu-3.19.0-19.19. Kees also pointed out that he landed a series of patches from 204db6ed17743000691d930368a5abd6ea541c58 until Michael Davidson's patch (i.e. a87938b2e246b81b4fb713edb371a9fa3c5c3c86..204db6ed17743000691d930368a5abd6ea541c58 ), and in particular, there's: commit d1fd836dcf00d2028c700c7e44d2c23404062c90 Author: Kees Cook mm: split ET_DYN ASLR from mmap ASLR Other fixes that I see to fs/binfmt_elf.c and arch/x86/mm/mmap.c look like they either occurred only in 4.3 or have already been backported via the stable kernels. I should also point out that these cleanups may address some of the ASLR failed tests that occur on non-x86 architectures for pre 4.2 kernels. I am happy to test out kernels to try to address this. Thanks. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-68-generic 3.13.0-68.111 ProcVersionSignature: Ubuntu 3.13.0-68.111-generic 3.13.11-ckt27 Uname: Linux 3.13.0-68-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.18 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/hwC0D1', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Fri Nov 20 13:58:40 2015 HibernationDevice: RESUME=UUID=dc63f523-507a-4f9d-aa30-a2e880199150 IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: Shuttle Inc SG33 ProcEnviron: SHELL=/bin/bash TERM=screen PATH=(custom, user) LANG=en_US.UTF-8 XDG_RUNTIME_DIR= ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-68-generic root=UUID=d30e91cf-3c43-41a9-a72d-c07d1be1d53e ro loop.max_loop=64 rootflags=data=ordered nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw RelatedPackageVersions: linux-restricted-modules-3.13.0-68-generic N/A linux-backports-modules-3.13.0-68-generic N/A linux-firmware 1.127.18 RfKill: SourcePackage: linux StagingDrivers: zram UpgradeStatus: Upgraded to trusty on 2014-04-16 (583 days ago) WpaSupplicantLog: dmi.bios.date: 11/28/2007 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.board.name: FG33 dmi.board.vendor: Shuttle Inc dmi.board.version: V10 dmi.chassis.type: 3 dmi.chassis.vendor: Shuttle Inc dmi.chassis.version: G5 dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd11/28/2007:svnShuttleInc:pnSG33:pvrV10:rvnShuttleInc:rnFG33:rvrV10:cvnShuttleInc:ct3:cvrG5: dmi.product.name: SG33 dmi.product.version: V10 dmi.sys.vendor: Shuttle Inc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1518483/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to :
[Touch-packages] [Bug 1633823] Re: current tab jumps to top of the tab list, background tabs opened are placed to end of the list
** Attachment added: "tab_jumped_to_top.png" https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1633823/+attachment/4761808/+files/tab_jumped_to_top.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1633823 Title: current tab jumps to top of the tab list, background tabs opened are placed to end of the list Status in webbrowser-app package in Ubuntu: New Bug description: When I open a link in the background it goes to the end of tab list instead of next to the currently used tab. To reproduce the problem: Open ~5 tabs in the browser. And go to the 3rd tab now load a website there and do these: -The behaviour I see with "open link in new tab": long click on link with "open link in new tab", a new tab is created that goes to the top of the tabs list and the next tab (the one below) is the original page I opened the link from. It is a bit strange that the original tab changed its location in the list. I think it would be better if it kept its original location and the new tab was inserted between the 3rd and 4th (or 2nd and 3rd, dont know where the indexing starts) tab. But at least the two tabs are next to each other. -The behaviour at "open link in new background tab": when clicked, the new tab will be the last in the list (bottom) while the current tab will be the top which is really annoying when I have multiple tabs open! So, firstly I would recommend that the current tab should stay where it is in the list. When there is a long swipe from below it should show tabs list focused at the current tab (but the current tab is not taken to the top of the list). Secondly, the tab opened with "open link in new background tab" from the current tab should be next to the original tab. I am on mako rc-proposed r550, but this bug is there since quite some time. webbrowser-app: Installed: 0.23+15.04.20160928-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1633823/+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 1633823] [NEW] current tab jumps to top of the tab list, background tabs opened are placed to end of the list
Public bug reported: When I open a link in the background it goes to the end of tab list instead of next to the currently used tab. To reproduce the problem: Open ~5 tabs in the browser. And go to the 3rd tab now load a website there and do these: -The behaviour I see with "open link in new tab": long click on link with "open link in new tab", a new tab is created that goes to the top of the tabs list and the next tab (the one below) is the original page I opened the link from. It is a bit strange that the original tab changed its location in the list. I think it would be better if it kept its original location and the new tab was inserted between the 3rd and 4th (or 2nd and 3rd, dont know where the indexing starts) tab. But at least the two tabs are next to each other. -The behaviour at "open link in new background tab": when clicked, the new tab will be the last in the list (bottom) while the current tab will be the top which is really annoying when I have multiple tabs open! So, firstly I would recommend that the current tab should stay where it is in the list. When there is a long swipe from below it should show tabs list focused at the current tab (but the current tab is not taken to the top of the list). Secondly, the tab opened with "open link in new background tab" from the current tab should be next to the original tab. I am on mako rc-proposed r550, but this bug is there since quite some time. webbrowser-app: Installed: 0.23+15.04.20160928-0ubuntu1 ** Affects: webbrowser-app (Ubuntu) Importance: Undecided Status: New ** Tags: annoying management tab ** Attachment added: "tab_middle.png" https://bugs.launchpad.net/bugs/1633823/+attachment/4761807/+files/tab_middle.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1633823 Title: current tab jumps to top of the tab list, background tabs opened are placed to end of the list Status in webbrowser-app package in Ubuntu: New Bug description: When I open a link in the background it goes to the end of tab list instead of next to the currently used tab. To reproduce the problem: Open ~5 tabs in the browser. And go to the 3rd tab now load a website there and do these: -The behaviour I see with "open link in new tab": long click on link with "open link in new tab", a new tab is created that goes to the top of the tabs list and the next tab (the one below) is the original page I opened the link from. It is a bit strange that the original tab changed its location in the list. I think it would be better if it kept its original location and the new tab was inserted between the 3rd and 4th (or 2nd and 3rd, dont know where the indexing starts) tab. But at least the two tabs are next to each other. -The behaviour at "open link in new background tab": when clicked, the new tab will be the last in the list (bottom) while the current tab will be the top which is really annoying when I have multiple tabs open! So, firstly I would recommend that the current tab should stay where it is in the list. When there is a long swipe from below it should show tabs list focused at the current tab (but the current tab is not taken to the top of the list). Secondly, the tab opened with "open link in new background tab" from the current tab should be next to the original tab. I am on mako rc-proposed r550, but this bug is there since quite some time. webbrowser-app: Installed: 0.23+15.04.20160928-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1633823/+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