[Touch-packages] [Bug 1687354] Re: package python-crypto 2.6.1-6ubuntu0.16.04.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
** Attachment added: "unzip and install this" https://bugs.launchpad.net/ubuntu/+source/python-crypto/+bug/1687354/+attachment/4870177/+files/python-crypto_2.6.1.orig.tar.gz -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-crypto in Ubuntu. https://bugs.launchpad.net/bugs/1687354 Title: package python-crypto 2.6.1-6ubuntu0.16.04.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in python-crypto package in Ubuntu: New Bug description: Please fix this issue as soon as possible... ProblemType: Package DistroRelease: Ubuntu 16.04 Package: python-crypto 2.6.1-6ubuntu0.16.04.2 ProcVersionSignature: Ubuntu 4.8.0-49.52~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-49-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Mon May 1 00:07:48 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2017-04-18 (13 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: python-crypto Title: package python-crypto 2.6.1-6ubuntu0.16.04.2 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/python-crypto/+bug/1687354/+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 1687354] Re: package python-crypto 2.6.1-6ubuntu0.16.04.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
https://launchpad.net/ubuntu/xenial/+source/python-crypto This might help ** Changed in: python-crypto (Ubuntu) Assignee: (unassigned) => Srushti Patil (srushtipatil.p9) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-crypto in Ubuntu. https://bugs.launchpad.net/bugs/1687354 Title: package python-crypto 2.6.1-6ubuntu0.16.04.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in python-crypto package in Ubuntu: New Bug description: Please fix this issue as soon as possible... ProblemType: Package DistroRelease: Ubuntu 16.04 Package: python-crypto 2.6.1-6ubuntu0.16.04.2 ProcVersionSignature: Ubuntu 4.8.0-49.52~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-49-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Mon May 1 00:07:48 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2017-04-18 (13 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: python-crypto Title: package python-crypto 2.6.1-6ubuntu0.16.04.2 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/python-crypto/+bug/1687354/+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 1177318] Re: Unattended Upgrades fail to parse "${distro_id}:${distro_codename}-security"
[Expired for unattended-upgrades (Ubuntu) because there has been no
activity for 60 days.]
** Changed in: unattended-upgrades (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1177318
Title:
Unattended Upgrades fail to parse
"${distro_id}:${distro_codename}-security"
Status in unattended-upgrades package in Ubuntu:
Expired
Bug description:
Beginning with Ubuntu 13.04 Raring Ringtail, unattended-upgrades seems
not to be able to parse /etc/apt/apt.conf.d/50unattended-upgrades
anymore. The logfile tells:
cat /var/log/unattended-upgrades/unattended-upgrades.log
2013-05-06 14:57:05,724 INFO Pakete, die anfangs auf die schwarzen Liste
standen:
2013-05-06 14:57:05,724 INFO Skript für unbeaufsichtigte Upgrades wird
gestartet.
2013-05-06 14:57:05,725 INFO erlaubte Ursprünge sind:
['o=Ubuntu,a=raring-security', 'o=Ubuntu,a=raring-updates']
2013-05-06 14:57:09,114 INFO Es wurden keine Pakete gefunden, von denen ein
unbeaufsichtigtes Upgrade durchgeführt werden kann.
2013-05-07 11:33:04,944 INFO Pakete, die anfangs auf die schwarzen Liste
standen:
2013-05-07 11:33:04,944 INFO Skript für unbeaufsichtigte Upgrades wird
gestartet.
2013-05-07 11:33:04,944 INFO erlaubte Ursprünge sind:
['o=Ubuntu,a=raring-security', 'o=Ubuntu,a=raring-updates']
2013-05-07 11:33:08,398 INFO Es wurden keine Pakete gefunden, von denen ein
unbeaufsichtigtes Upgrade durchgeführt werden kann.
which means two times, that allowed sources are ['o=Ubuntu,a=raring-
security', 'o=Ubuntu,a=raring-updates'].
I do suspect it is because of the automatic distribution setting in
/etc/apt/apt.conf.d/50unattended-upgrades or the setting of the
corresponding variables:
"${distro_id}:${distro_codename}-updates"
When this line is set manually to "Ubuntu:raring-updates", it will
work.
System: Ubuntu Gnome 13.04, all up-to-date
$ lsb_release -rd
Description: Ubuntu 13.04
Release: 13.04
$ cat /etc/apt/apt.conf.d/10periodic
APT::Periodic::Update-Package-Lists "1";
APT::Periodic::Download-Upgradeable-Packages "1";
APT::Periodic::AutocleanInterval "1";
APT::Periodic::Unattended-Upgrade "1";
$ cat /etc/apt/apt.conf.d/50unattended-upgrades
// Automatically upgrade packages from these (origin:archive) pairs
Unattended-Upgrade::Allowed-Origins {
"${distro_id}:${distro_codename}-security";
"${distro_id}:${distro_codename}-updates";
//"${distro_id}:${distro_codename}-proposed";
//"${distro_id}:${distro_codename}-backports";
};
// List of packages to not update
Unattended-Upgrade::Package-Blacklist {
//"vim";
//"libc6";
//"libc6-dev";
//"libc6-i686";
};
...
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1177318/+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 1655804] Re: Under Unity8, mir_demo_client_target is distorted and input in the wrong place on start-up
Hmm, actually doesn't work in Unity8 even with both fixes... In fact it's now worse - nothing ever appears even after resizing the window. ** Changed in: mir/0.27 Milestone: 0.27.0 => None ** Changed in: mir Milestone: 0.28.0 => None ** Changed in: mir Status: Fix Committed => Won't Fix ** Changed in: mir/0.27 Status: Fix Committed => Won't Fix ** Changed in: mir (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1655804 Title: Under Unity8, mir_demo_client_target is distorted and input in the wrong place on start-up Status in Mir: Won't Fix Status in Mir 0.27 series: Won't Fix Status in mir package in Ubuntu: Won't Fix Status in unity8 package in Ubuntu: Won't Fix Bug description: Under Unity8, mir_demo_client_target is distorted and input in the wrong place on start-up. Test case: 1. $ sudo apt install mir-demos 2. $ mir_demo_client_target -- --desktop_file_hint=unity8 3. Wiggle the mouse around over the window The problem goes away after you manually resize the window. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1655804/+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 1651735] Re: $ mir_demo_server --help fails with an exception
Also occurs on Zesty installations that have been upgraded from Yakkety. Unity8 fails to launch (classic black screen) and unity8.log shows the error: "character conversion failed" This is due to incorrect multiple versions of boost being present on the system because they aren't removed when upgrading. Counted 6(six) different boost versions installed in Zesty because of taking the upgrade route through multiple Ubuntu versions. 'apt-get remove --auto-remove --purge' does not remove them so looks like a genuine dependency resolution problem when upgrading. Manually removing all the old boost versions works around the problem and allows Unity8 to work again. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1651735 Title: $ mir_demo_server --help fails with an exception Status in Mir: Invalid Status in mir package in Ubuntu: Invalid Bug description: $ mir_demo_server --help [2016-12-21 11:49:00.068655] mirplatform: Found graphics driver: mir:mesa-kms (version 0.25.0) [2016-12-21 11:49:00.069710] mirplatform: Found graphics driver: mir:mesa-x11 (version 0.25.0) [2016-12-21 11:49:00.069935] mirplatform: Found graphics driver: mir:stub-graphics (version 0.25.0) [2016-12-21 11:49:00.069954] mirplatform: Found graphics driver: throw-on-creation (version 0.25.0) ERROR: Throw location unknown (consider using BOOST_THROW_EXCEPTION) Dynamic exception type: boost::exception_detail::clone_impl > std::exception::what: character conversion failed To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1651735/+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 1655804] Re: Under Unity8, mir_demo_client_target is distorted and input in the wrong place on start-up
Fix committed to lp:mir/0.27 at revision 4157, scheduled for release in Mir 0.27.0 ** Changed in: mir/0.27 Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1655804 Title: Under Unity8, mir_demo_client_target is distorted and input in the wrong place on start-up Status in Mir: Fix Committed Status in Mir 0.27 series: Fix Committed Status in mir package in Ubuntu: New Status in unity8 package in Ubuntu: Won't Fix Bug description: Under Unity8, mir_demo_client_target is distorted and input in the wrong place on start-up. Test case: 1. $ sudo apt install mir-demos 2. $ mir_demo_client_target -- --desktop_file_hint=unity8 3. Wiggle the mouse around over the window The problem goes away after you manually resize the window. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1655804/+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 1655804] Re: Under Unity8, mir_demo_client_target is distorted and input in the wrong place on start-up
** Also affects: mir/0.27 Importance: Undecided Status: New ** Changed in: mir/0.27 Milestone: None => 0.27.0 ** Changed in: mir/0.27 Importance: Undecided => Medium ** Changed in: mir/0.27 Assignee: (unassigned) => Daniel van Vugt (vanvugt) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1655804 Title: Under Unity8, mir_demo_client_target is distorted and input in the wrong place on start-up Status in Mir: Fix Committed Status in Mir 0.27 series: New Status in mir package in Ubuntu: New Status in unity8 package in Ubuntu: Won't Fix Bug description: Under Unity8, mir_demo_client_target is distorted and input in the wrong place on start-up. Test case: 1. $ sudo apt install mir-demos 2. $ mir_demo_client_target -- --desktop_file_hint=unity8 3. Wiggle the mouse around over the window The problem goes away after you manually resize the window. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1655804/+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 1687354] [NEW] package python-crypto 2.6.1-6ubuntu0.16.04.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: Please fix this issue as soon as possible... ProblemType: Package DistroRelease: Ubuntu 16.04 Package: python-crypto 2.6.1-6ubuntu0.16.04.2 ProcVersionSignature: Ubuntu 4.8.0-49.52~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-49-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Mon May 1 00:07:48 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2017-04-18 (13 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: python-crypto Title: package python-crypto 2.6.1-6ubuntu0.16.04.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: python-crypto (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package need-duplicate-check xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-crypto in Ubuntu. https://bugs.launchpad.net/bugs/1687354 Title: package python-crypto 2.6.1-6ubuntu0.16.04.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in python-crypto package in Ubuntu: New Bug description: Please fix this issue as soon as possible... ProblemType: Package DistroRelease: Ubuntu 16.04 Package: python-crypto 2.6.1-6ubuntu0.16.04.2 ProcVersionSignature: Ubuntu 4.8.0-49.52~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-49-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Mon May 1 00:07:48 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2017-04-18 (13 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: python-crypto Title: package python-crypto 2.6.1-6ubuntu0.16.04.2 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/python-crypto/+bug/1687354/+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 1687353] Re: System freezes due to ALSA error and recovers after significant time
** Description changed: Hello I have a Lenovo Ideapad 310. I was having issues with power management, and was using upstream kernels. I noticed they had frequent freezes, so I decided to use the standard from Ubuntu 16.04 (today, 4.4.0-75). But now it has this freezes too, so something which was bugged on the newer kernel was inserted on 4.4.0-75, as previous version (4.4.0-72) hadn't this issue. What is happening is: the system freezes. The sound that was being played loops endlessly. Everything freezes, Ctrl+Alt+Fnumber don't work. The system completely stops. Normally, I would just power the computer off keeping the power button pressed. But this time I tried to recover it, as the syslog ended always corrupted. I needed to gets the logs at least once. So I started to disconnect hardware parts: battery charger, external USB HDD (it was not being accessed), USB mouse, USB keyboard. When I disconnected the sound jack, I noticed the mouse moved, so it was recoverable. I waited for 100 seconds until the system recovered. When it recovered, looked like nothing had happened, and now I'm writing this report from the computer, without restarting. Steps to reproduce: 1) open Audacious or VLC; 2) play a music/video on Audacious or VLC; 3) open another program with sound (Steam, a browser (I use Opera), etc); 4) use the computer until a freeze happens. Observations: -Audacious + Steam + Starbound is nearly 100% chance of triggering it (SDL?). -VLC + Opera + Firefox (on start page) was enough for trigger it once, even with the only program with media opened being VLC. The freeze I was able to recover had: Opera Developer (YouTube video playing) + Audacious (playing) + Steam with audio streams opened on pavucontrol. Additionally, Thunderbird and Evince were opened, and intel-gpu-overlay was opened inside a Xnest window. The syslog says to report to alsa, so I'm writing the report here. However, it should be noted that there is a i915 error too, maybe it was a consequence, maybe it was the cause. $ lsb_release -rd Description: Ubuntu 16.04.2 LTS Release: 16.04 $ uname -a Linux usuario-Lenovo-ideapad-310-14ISK 4.4.0-75-generic #96-Ubuntu SMP Thu Apr 20 09:56:33 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux Thank you. + Edit: one thing I noticed with indicator-multiload, the internal HDD + activity completely stopped while this problem was happening and soon + after it started to function. It was like the computer was recovering + with the internal HDD turned off. The HDD usage ramped up and the system + returned to normal. May this be related with the power management + issues? + ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libasound2 1.1.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-75.96-generic 4.4.59 Uname: Linux 4.4.0-75-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: XFCE Date: Sun Apr 30 23:43:29 2017 Dependencies: - gcc-6-base 6.0.1-0ubuntu1 - libasound2-data 1.1.0-0ubuntu1 - libc6 2.23-0ubuntu7 - libgcc1 1:6.0.1-0ubuntu1 + gcc-6-base 6.0.1-0ubuntu1 + libasound2-data 1.1.0-0ubuntu1 + libc6 2.23-0ubuntu7 + libgcc1 1:6.0.1-0ubuntu1 InstallationDate: Installed on 2016-12-31 (121 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: alsa-lib UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1687353 Title: System freezes due to ALSA error and recovers after significant time Status in alsa-lib package in Ubuntu: New Bug description: Hello I have a Lenovo Ideapad 310. I was having issues with power management, and was using upstream kernels. I noticed they had frequent freezes, so I decided to use the standard from Ubuntu 16.04 (today, 4.4.0-75). But now it has this freezes too, so something which was bugged on the newer kernel was inserted on 4.4.0-75, as previous version (4.4.0-72) hadn't this issue. What is happening is: the system freezes. The sound that was being played loops endlessly. Everything freezes, Ctrl+Alt+Fnumber don't work. The system completely stops. Normally, I would just power the computer off keeping the power button pressed. But this time I tried to recover it, as the syslog ended always corrupted. I needed to gets the logs at least once. So I started to disconnect hardware parts: battery charger, external USB HDD (it was not being accessed), USB mouse, USB keyboard. When I disconnected the sound jack, I noticed the mouse moved, so it was recoverable. I waited for 100 seconds until the system recovered. When it recovered, looked like nothing had happened, and now I'm writing this report from the computer, without rest
[Touch-packages] [Bug 1687353] [NEW] System freezes due to ALSA error and recovers after significant time
Public bug reported: Hello I have a Lenovo Ideapad 310. I was having issues with power management, and was using upstream kernels. I noticed they had frequent freezes, so I decided to use the standard from Ubuntu 16.04 (today, 4.4.0-75). But now it has this freezes too, so something which was bugged on the newer kernel was inserted on 4.4.0-75, as previous version (4.4.0-72) hadn't this issue. What is happening is: the system freezes. The sound that was being played loops endlessly. Everything freezes, Ctrl+Alt+Fnumber don't work. The system completely stops. Normally, I would just power the computer off keeping the power button pressed. But this time I tried to recover it, as the syslog ended always corrupted. I needed to gets the logs at least once. So I started to disconnect hardware parts: battery charger, external USB HDD (it was not being accessed), USB mouse, USB keyboard. When I disconnected the sound jack, I noticed the mouse moved, so it was recoverable. I waited for 100 seconds until the system recovered. When it recovered, looked like nothing had happened, and now I'm writing this report from the computer, without restarting. Steps to reproduce: 1) open Audacious or VLC; 2) play a music/video on Audacious or VLC; 3) open another program with sound (Steam, a browser (I use Opera), etc); 4) use the computer until a freeze happens. Observations: -Audacious + Steam + Starbound is nearly 100% chance of triggering it (SDL?). -VLC + Opera + Firefox (on start page) was enough for trigger it once, even with the only program with media opened being VLC. The freeze I was able to recover had: Opera Developer (YouTube video playing) + Audacious (playing) + Steam with audio streams opened on pavucontrol. Additionally, Thunderbird and Evince were opened, and intel-gpu-overlay was opened inside a Xnest window. The syslog says to report to alsa, so I'm writing the report here. However, it should be noted that there is a i915 error too, maybe it was a consequence, maybe it was the cause. $ lsb_release -rd Description:Ubuntu 16.04.2 LTS Release:16.04 $ uname -a Linux usuario-Lenovo-ideapad-310-14ISK 4.4.0-75-generic #96-Ubuntu SMP Thu Apr 20 09:56:33 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux Thank you. Edit: one thing I noticed with indicator-multiload, the internal HDD activity completely stopped while this problem was happening and soon after it started to function. It was like the computer was recovering with the internal HDD turned off. The HDD usage ramped up and the system returned to normal. May this be related with the power management issues? ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libasound2 1.1.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-75.96-generic 4.4.59 Uname: Linux 4.4.0-75-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: XFCE Date: Sun Apr 30 23:43:29 2017 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libasound2-data 1.1.0-0ubuntu1 libc6 2.23-0ubuntu7 libgcc1 1:6.0.1-0ubuntu1 InstallationDate: Installed on 2016-12-31 (121 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: alsa-lib UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: alsa-lib (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial ** Attachment added: "syslog when the freeze occurred" https://bugs.launchpad.net/bugs/1687353/+attachment/4870156/+files/PULSEKERNELALSA -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1687353 Title: System freezes due to ALSA error and recovers after significant time Status in alsa-lib package in Ubuntu: New Bug description: Hello I have a Lenovo Ideapad 310. I was having issues with power management, and was using upstream kernels. I noticed they had frequent freezes, so I decided to use the standard from Ubuntu 16.04 (today, 4.4.0-75). But now it has this freezes too, so something which was bugged on the newer kernel was inserted on 4.4.0-75, as previous version (4.4.0-72) hadn't this issue. What is happening is: the system freezes. The sound that was being played loops endlessly. Everything freezes, Ctrl+Alt+Fnumber don't work. The system completely stops. Normally, I would just power the computer off keeping the power button pressed. But this time I tried to recover it, as the syslog ended always corrupted. I needed to gets the logs at least once. So I started to disconnect hardware parts: battery charger, external USB HDD (it was not being accessed), USB mouse, USB keyboard. When I disconnected the sound jack, I noticed the mouse moved, so it was recoverable. I waited for 100 seconds until the system recovered. When it recovered, looked like nothing had happened, and now I'm writing this report from the computer, without restarting.
[Touch-packages] [Bug 1687352] [NEW] Graphics Corruption on Hardware Accelerated Softwares
Public bug reported: Applications like Blender (native) and SimCity 4 (running through Wine with Hardware Acceleration enabled) have their windows graphics corrupted as saw in the attachment's print screen image (Blender). Maybe this problem is OpenGL related, it's just a guess. It didn't occur on Ubuntu 16.10 Yakkety Yak. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: xorg 1:7.7+16ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE Date: Sun Apr 30 23:43:40 2017 DistUpgraded: Fresh install DistroCodename: zesty DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 6290] [1002:9807] (prog-if 00 [VGA controller]) Subsystem: Elitegroup Computer Systems Wrestler [Radeon HD 6290] [1019:3141] InstallationDate: Installed on 2017-01-14 (106 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20-generic root=UUID=2db4e4b3-e99a-4d11-96af-5d10de0134c4 ro rootflags=sync splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/09/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.4 dmi.board.name: HDC-M dmi.board.version: 1.0 dmi.chassis.type: 3 dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.4:bd04/09/2012:svn:pnHDC-M:pvr1.0:rvn:rnHDC-M:rvr1.0:cvn:ct3:cvr1.0: dmi.product.name: HDC-M dmi.product.version: 1.0 version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.3-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.3-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.14-0ubuntu1 xserver.bootTime: Sun Apr 30 23:33:33 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.3-1ubuntu1 xserver.video_driver: radeon ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug corruption ubuntu zesty ** Attachment added: "Blender with corrupted graphics" https://bugs.launchpad.net/bugs/1687352/+attachment/4870132/+files/Captura%20de%20tela%20de%202017-04-30%2023-45-43.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/1687352 Title: Graphics Corruption on Hardware Accelerated Softwares Status in xorg package in Ubuntu: New Bug description: Applications like Blender (native) and SimCity 4 (running through Wine with Hardware Acceleration enabled) have their windows graphics corrupted as saw in the attachment's print screen image (Blender). Maybe this problem is OpenGL related, it's just a guess. It didn't occur on Ubuntu 16.10 Yakkety Yak. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: xorg 1:7.7+16ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE Date: Sun Apr 30 23:43:40 2017 DistUpgraded: Fresh install DistroCodename: zesty DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 6290] [1002:9807] (prog-if 00 [VGA controller]) Subsystem: Elitegroup Computer Systems Wrestler [Radeon HD 6290] [1019:3141] InstallationDate: Installed on 2017-01-14 (106 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20-generic root=UUID=2db4e4b3-e99a-4d11-96af-5d10de0134c4 ro rootflags=sync splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/09/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.4 dmi.board.name: HDC-M dmi.board.version: 1.0 dmi.chassis.type: 3 dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.4:bd04/09/2012:svn:pnHDC-M:pvr1.0:rvn:rnHD
[Touch-packages] [Bug 1687349] [NEW] Can't seem to connect to network printer, despite getting a ping response, etc
Private bug reported: For instance, when printing a test page, it just stops in the queue. gsawaya@gsawaya-workstation:~$ nmap -Pn 172.27.115.54 Starting Nmap 7.01 ( https://nmap.org ) at 2017-04-30 19:17 PDT Nmap scan report for RED-Hal_2000.DHCP.thefacebook.com (172.27.115.54) Host is up (0.00092s latency). Not shown: 999 filtered ports PORT STATE SERVICE 9100/tcp open jetdirect Nmap done: 1 IP address (1 host up) scanned in 25.89 seconds gsawaya@gsawaya-workstation:~$ /usr/lib/cups/backend/snmp gsawaya@gsawaya-workstation:~$ /usr/lib/cups/backend/snmp gsawaya@gsawaya-workstation:~$ sudo /usr/lib/cups/backend/dnssd DEBUG: sent=0, count=0 DEBUG: sent=0, count=0 DEBUG: sent=0, count=0 gsawaya@gsawaya-workstation:~$ /usr/lib/cups/backend/snmp 172.27.115.54 gsawaya@gsawaya-workstation:~$ lpinfo -v network https network ipps network socket network beh network http network ipp network ipp14 network lpd direct hp gsawaya@gsawaya-workstation:~$ avahi-browse -a -v -t -r Server version: avahi 0.6.32-rc; Host name: gsawaya-workstation.local E Ifce Prot Name Type Domain : Cache exhausted + enp11s0 IPv6 FFC26777FFC2 iPod Touch Music Library local + enp11s0 IPv4 FFC26777FFC2 iPod Touch Music Library local = enp11s0 IPv6 FFC26777FFC2 iPod Touch Music Library local = enp11s0 IPv4 FFC26777FFC2 iPod Touch Music Library local : All for now gsawaya@gsawaya-workstation:~$ avahi-browse -a -v -c -r Server version: avahi 0.6.32-rc; Host name: gsawaya-workstation.local E Ifce Prot Name Type Domain + enp11s0 IPv6 FFC26777FFC2 iPod Touch Music Library local + enp11s0 IPv4 FFC26777FFC2 iPod Touch Music Library local : Cache exhausted ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: cups 2.1.3-4 ProcVersionSignature: Ubuntu 4.8.0-49.52~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-49-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia wl ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Sun Apr 30 19:25:34 2017 InstallationDate: Installed on 2017-03-31 (30 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) Lpstat: device for hal_2000: socket://172.27.115.54:9100 MachineType: Falcon Northwest All Series Papersize: letter PpdFiles: hal_2000: HP LaserJet 700 color MFP M775 Postscript (recommended) ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-49-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/09/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1401 dmi.board.asset.tag: Default string dmi.board.name: X99-DELUXE II dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1401:bd11/09/2016:svnFalconNorthwest:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnX99-DELUXEII:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: Falcon Northwest ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apparmor apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1687349 Title: Can't seem to connect to network printer, despite getting a ping response, etc Status in cups package in Ubuntu: New Bug description: For instance, when printing a test page, it just stops in the queue. gsawaya@gsawaya-workstation:~$ nmap -Pn 172.27.115.54 Starting Nmap 7.01 ( https://nmap.org ) at 2017-04-30 19:17 PDT Nmap scan report for RED-Hal_2000.DHCP.thefacebook.com (172.27.115.54) Host is up (0.00092s latency). Not shown: 999 filtered ports PORT STATE SERVICE 9100/tcp open jetdirect Nmap done: 1 IP address (1 host up) scanned in 25.89 seconds gsawaya@gsawaya-workstation:~$ /usr/lib/cups/backend/snmp gsawaya@gsawaya-workstation:~$ /usr/lib/cups/backend/snmp gsawaya@gsawaya-workstation:~$ sudo /usr/lib/cups/backend/dnssd DEBUG: sent=0, count=0 DEBUG: sent=0, count=0 DEBUG: sent=0, count=0 gsawaya@gsawaya-workstation:~$ /usr/lib/cups/backend/snmp 172.27.115.54 gsawaya@gsawaya-workstation:~$ lpinfo -v network https network ipps network socket network beh network http network ipp network ipp14 network lpd direct hp gsawaya@gsa
[Touch-packages] [Bug 1682386] Re: systemd-resolved can not resolve .coop domain names
I just ran the updater and the issue appears solved (for the moment anyway) -- 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/1682386 Title: systemd-resolved can not resolve .coop domain names Status in systemd package in Ubuntu: Confirmed Bug description: I am using Ubuntu Gnome 17.04, systemd version 232-21ubuntu2. I found that .coop domain nomes are not being resolved. If I switch to another DNS server (instead of 127.0.0.53, which is the current default in 17.04), then .coop domains are resolved: $ nslookup > www.somenergia.coop Server: 127.0.0.53 Address: 127.0.0.53#53 ** server can't find www.somenergia.coop: SERVFAIL > server 8.8.8.8 Default server: 8.8.8.8 Address: 8.8.8.8#53 > www.somenergia.coop Server: 8.8.8.8 Address: 8.8.8.8#53 Non-authoritative answer: Name: www.somenergia.coop Address: 164.132.200.9 > To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1682386/+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 1682386] Re: systemd-resolved can not resolve .coop domain names
Most places, including BWI airport, I can not access sites with the coop domain. -- 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/1682386 Title: systemd-resolved can not resolve .coop domain names Status in systemd package in Ubuntu: Confirmed Bug description: I am using Ubuntu Gnome 17.04, systemd version 232-21ubuntu2. I found that .coop domain nomes are not being resolved. If I switch to another DNS server (instead of 127.0.0.53, which is the current default in 17.04), then .coop domains are resolved: $ nslookup > www.somenergia.coop Server: 127.0.0.53 Address: 127.0.0.53#53 ** server can't find www.somenergia.coop: SERVFAIL > server 8.8.8.8 Default server: 8.8.8.8 Address: 8.8.8.8#53 > www.somenergia.coop Server: 8.8.8.8 Address: 8.8.8.8#53 Non-authoritative answer: Name: www.somenergia.coop Address: 164.132.200.9 > To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1682386/+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 1682386] Re: systemd-resolved can not resolve .coop domain names
I was just traveling and could access the coop domain, then got back home and used our house internet and no longer had access. Strange. I thought there had been a fix. -- 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/1682386 Title: systemd-resolved can not resolve .coop domain names Status in systemd package in Ubuntu: Confirmed Bug description: I am using Ubuntu Gnome 17.04, systemd version 232-21ubuntu2. I found that .coop domain nomes are not being resolved. If I switch to another DNS server (instead of 127.0.0.53, which is the current default in 17.04), then .coop domains are resolved: $ nslookup > www.somenergia.coop Server: 127.0.0.53 Address: 127.0.0.53#53 ** server can't find www.somenergia.coop: SERVFAIL > server 8.8.8.8 Default server: 8.8.8.8 Address: 8.8.8.8#53 > www.somenergia.coop Server: 8.8.8.8 Address: 8.8.8.8#53 Non-authoritative answer: Name: www.somenergia.coop Address: 164.132.200.9 > To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1682386/+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 1645631] Re: Sending files fails because obex not loaded
Happens in Zesty too. Updated from previous distribution versions 16.04->16.10->17.04. Manually starting the service fixes the problem until reboot. -- 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/1645631 Title: Sending files fails because obex not loaded Status in bluez package in Ubuntu: Confirmed Status in gnome-bluetooth package in Ubuntu: Confirmed Bug description: If I run bluetooth-sendto from command line and try to send the file, it quits after selecting the target device with following command line output: "Acquiring proxy failed: Error calling StartServiceByName for org.bluez.obex: GDBus.Error:org.freedesktop.systemd1.NoSuchUnit: Unit dbus-org.bluez.obex.service not found." After I run "systemctl --user start obex", it proceeds to send the file. Even then it for some reason gets stuck, but I do not know what causes it and it is probably a different problem. This system is upgraded from xenial. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: gnome-bluetooth 3.20.0-1ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1 Uname: Linux 4.8.0-27-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 Date: Tue Nov 29 11:04:11 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-09-12 (77 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: LANGUAGE=fi TERM=xterm PATH=(custom, no user) LANG=C SHELL=/bin/bash SourcePackage: gnome-bluetooth UpgradeStatus: Upgraded to yakkety on 2016-11-01 (27 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1645631/+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 1675892] Re: pulseaudio crashed with SIGABRT
I got so sick and tired of these frequent crashes and not being able to listen to music or adjust the volume that I ended up downgrading the pulseaudio packages using their Yakkety version (the rest of the system is Zesty). Everything's been fine since then. -- 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/1675892 Title: pulseaudio crashed with SIGABRT Status in pulseaudio package in Ubuntu: Confirmed Bug description: A random pulseaudio crash ProblemType: Crash DistroRelease: Ubuntu 17.04 Package: pulseaudio 1:10.0-1ubuntu1 Uname: Linux 4.10.4-041004-lowlatency x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bonnaudl 1902 F pulseaudio CurrentDesktop: MATE Date: Thu Mar 23 07:51:00 2017 ExecutablePath: /usr/bin/pulseaudio ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: pulseaudio Stacktrace: #0 No locals. #1 0x in ?? () No symbol table info available. Backtrace stopped: Cannot access memory at address 0x0 StacktraceTop: ?? () Title: pulseaudio crashed with SIGABRT UpgradeStatus: Upgraded to zesty on 2017-03-12 (12 days ago) UserGroups: adm admin cdrom dialout lpadmin lxd plugdev sambashare staff dmi.bios.date: 03/25/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.50 dmi.board.name: HM77-HT dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.50:bd03/25/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnHM77-HT:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1675892/+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 1645631] Re: Sending files fails because obex not loaded
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-bluetooth (Ubuntu) Status: New => Confirmed -- 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/1645631 Title: Sending files fails because obex not loaded Status in bluez package in Ubuntu: Confirmed Status in gnome-bluetooth package in Ubuntu: Confirmed Bug description: If I run bluetooth-sendto from command line and try to send the file, it quits after selecting the target device with following command line output: "Acquiring proxy failed: Error calling StartServiceByName for org.bluez.obex: GDBus.Error:org.freedesktop.systemd1.NoSuchUnit: Unit dbus-org.bluez.obex.service not found." After I run "systemctl --user start obex", it proceeds to send the file. Even then it for some reason gets stuck, but I do not know what causes it and it is probably a different problem. This system is upgraded from xenial. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: gnome-bluetooth 3.20.0-1ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1 Uname: Linux 4.8.0-27-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 Date: Tue Nov 29 11:04:11 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-09-12 (77 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: LANGUAGE=fi TERM=xterm PATH=(custom, no user) LANG=C SHELL=/bin/bash SourcePackage: gnome-bluetooth UpgradeStatus: Upgraded to yakkety on 2016-11-01 (27 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1645631/+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 1645631] Re: Sending files fails because obex not loaded
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: bluez (Ubuntu) Status: New => Confirmed -- 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/1645631 Title: Sending files fails because obex not loaded Status in bluez package in Ubuntu: Confirmed Status in gnome-bluetooth package in Ubuntu: Confirmed Bug description: If I run bluetooth-sendto from command line and try to send the file, it quits after selecting the target device with following command line output: "Acquiring proxy failed: Error calling StartServiceByName for org.bluez.obex: GDBus.Error:org.freedesktop.systemd1.NoSuchUnit: Unit dbus-org.bluez.obex.service not found." After I run "systemctl --user start obex", it proceeds to send the file. Even then it for some reason gets stuck, but I do not know what causes it and it is probably a different problem. This system is upgraded from xenial. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: gnome-bluetooth 3.20.0-1ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1 Uname: Linux 4.8.0-27-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 Date: Tue Nov 29 11:04:11 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-09-12 (77 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: LANGUAGE=fi TERM=xterm PATH=(custom, no user) LANG=C SHELL=/bin/bash SourcePackage: gnome-bluetooth UpgradeStatus: Upgraded to yakkety on 2016-11-01 (27 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1645631/+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 1681062] Re: Bluetooth doesn't work after update to 17.04
Some additional info: Bluetooth stop wokring after hibernation, but not always. Only way to get it work again is to completly power off computer and turn it on, reboot doesn't help. -- 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/1681062 Title: Bluetooth doesn't work after update to 17.04 Status in bluez package in Ubuntu: New Bug description: After update to 17.04 bluetooth stopped to work. some logs that could be useful: asudak@asudak-Inspiron-One-2330:~$ hciconfig hci0: Type: Primary Bus: USB BD Address: 80:56:F2:09:92:30 ACL MTU: 1022:8 SCO MTU: 183:5 DOWN RX bytes:580 acl:0 sco:0 events:31 errors:0 TX bytes:371 acl:0 sco:0 commands:38 errors:7 asudak@asudak-Inspiron-One-2330:~$ sudo hciconfig hci0 up Can't init device hci0: Connection timed out (110) ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu3 Architecture: amd64 Date: Sat Apr 8 13:04:36 2017 InstallationDate: Installed on 2013-12-27 (1197 days ago) InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Release amd64 (20131017) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. Inspiron One 2330 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic root=UUID=13b39ae0-892a-4b5a-ab81-62dba9463c1a ro quiet splash radeon.dpm=1 radeon.runpm=0 vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to zesty on 2017-02-25 (41 days ago) dmi.bios.date: 05/13/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A13 dmi.board.name: 09JR1D dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 13 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 27147636_1 dmi.modalias: dmi:bvnDellInc.:bvrA13:bd05/13/2013:svnDellInc.:pnInspironOne2330:pvr00:rvnDellInc.:rn09JR1D:rvrA00:cvnDellInc.:ct13:cvr27147636_1: dmi.product.name: Inspiron One 2330 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: 80:56:F2:09:92:30 ACL MTU: 1022:8 SCO MTU: 183:5 DOWN RX bytes:580 acl:0 sco:0 events:31 errors:0 TX bytes:371 acl:0 sco:0 commands:40 errors:9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1681062/+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 1682193] Re: Mouse acceleration significantly reduced after upgrade to 17.04
@POP Ok, I only have the speed slider. Will try to remove libinput and use evdev now as well. -- 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/1682193 Title: Mouse acceleration significantly reduced after upgrade to 17.04 Status in xorg package in Ubuntu: Confirmed Bug description: My external Logitech USB mouse was behaving nicely under 16.10 but after upgrade to 17.04 it has slowed down to a crawl. Settings slidebars are set at the maximum acceleration, but it only affects the touch pad, the mouse is extremely slow. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1682193/+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 1687312] [NEW] package binutils 2.26.1-1ubuntu1~16.04.3 failed to install/upgrade: package binutils is not ready for configuration cannot configure (current status 'half-installe
Public bug reported: It is failed to install. The Computer is lattitude d430 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: binutils 2.26.1-1ubuntu1~16.04.3 ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44 Uname: Linux 4.4.0-64-generic i686 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: i386 Date: Sun Apr 30 20:45:54 2017 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu7 libgcc1 1:6.0.1-0ubuntu1 zlib1g 1:1.2.8.dfsg-2ubuntu4 DuplicateSignature: package:binutils:2.26.1-1ubuntu1~16.04.3 Setting up libc6-dev:i386 (2.23-0ubuntu7) ... dpkg: error processing package binutils (--configure): package binutils is not ready for configuration ErrorMessage: package binutils is not ready for configuration cannot configure (current status 'half-installed') InstallationDate: Installed on 2016-03-08 (417 days ago) InstallationMedia: Lubuntu 15.10 "Wily Werewolf" - Release i386 (20151021) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: binutils Title: package binutils 2.26.1-1ubuntu1~16.04.3 failed to install/upgrade: package binutils is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: Upgraded to xenial on 2017-01-02 (118 days ago) ** Affects: binutils (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 need-duplicate-check xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1687312 Title: package binutils 2.26.1-1ubuntu1~16.04.3 failed to install/upgrade: package binutils is not ready for configuration cannot configure (current status 'half-installed') Status in binutils package in Ubuntu: New Bug description: It is failed to install. The Computer is lattitude d430 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: binutils 2.26.1-1ubuntu1~16.04.3 ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44 Uname: Linux 4.4.0-64-generic i686 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: i386 Date: Sun Apr 30 20:45:54 2017 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu7 libgcc1 1:6.0.1-0ubuntu1 zlib1g 1:1.2.8.dfsg-2ubuntu4 DuplicateSignature: package:binutils:2.26.1-1ubuntu1~16.04.3 Setting up libc6-dev:i386 (2.23-0ubuntu7) ... dpkg: error processing package binutils (--configure): package binutils is not ready for configuration ErrorMessage: package binutils is not ready for configuration cannot configure (current status 'half-installed') InstallationDate: Installed on 2016-03-08 (417 days ago) InstallationMedia: Lubuntu 15.10 "Wily Werewolf" - Release i386 (20151021) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: binutils Title: package binutils 2.26.1-1ubuntu1~16.04.3 failed to install/upgrade: package binutils is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: Upgraded to xenial on 2017-01-02 (118 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1687312/+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 1186662] Re: isc-dhcp-server fails to renew lease file
Yes, I share your frustration. However, the workaround to change the permissions of the /var/lib/dhcp directory to dhcpd:dhcpd is working for me. We shouldn't need a workaround, but at least there is one available. On 2017-04-30 06:54, Emmanuel Proust wrote: > Hi all, > > Soon 4 years and still no fix for this issue ! > > I would like to know any suggestion to make this fixed : > > - any Canonical contact to explain that the linux community is used to > say that Microsoft is very slow to fix bugs... > > - any famous community site to inform ubuntu users that such an issue > still affects 3 LTS versions (12.04 / 14.04 / 16.04) and it is just a > shame. > > - ? > > I regret a lot to write such comments but I noticed that nothing > happens. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1186662 > > Title: > isc-dhcp-server fails to renew lease file > > Status in isc-dhcp package in Ubuntu: > Fix Released > Status in isc-dhcp source package in Trusty: > Triaged > > Bug description: > After raring upgrade, the dhcp server fails to renew lease file when > it tries to (about every hour). > > The syslog says: > dhcpd: Can't create new lease file: Permission denied > > It looks like a permission problem, because > > # chown -R dhcpd:dhcpd /var/lib/dhcp > > the above command temporarily solves the issue, until dhcpd is > restarted: at that time, the ownership of the directory and the lease > file is set back to root:root. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1186662/+subscriptions -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1186662 Title: isc-dhcp-server fails to renew lease file Status in isc-dhcp package in Ubuntu: Fix Released Status in isc-dhcp source package in Trusty: Triaged Bug description: After raring upgrade, the dhcp server fails to renew lease file when it tries to (about every hour). The syslog says: dhcpd: Can't create new lease file: Permission denied It looks like a permission problem, because # chown -R dhcpd:dhcpd /var/lib/dhcp the above command temporarily solves the issue, until dhcpd is restarted: at that time, the ownership of the directory and the lease file is set back to root:root. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1186662/+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 1687019] Re: Cannot add a Google account using Online Accounts in Ubuntu Gnome
I reported this upstream (here: https://bugzilla.gnome.org/show_bug.cgi?id=781990 ) ** Bug watch added: GNOME Bug Tracker #781990 https://bugzilla.gnome.org/show_bug.cgi?id=781990 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1687019 Title: Cannot add a Google account using Online Accounts in Ubuntu Gnome Status in gnome-online-accounts package in Ubuntu: Confirmed Status in gnome-online-accounts package in Arch Linux: New Bug description: With Ubuntu Gnome 17.04 (brand new 64bit install on a Dell XPS13 laptop), I cannot add a Google account using Online-Accounts. If I choose to add a new Google account in Online Accounts, a window appears where I can enter my Google email. After entering my email and pressing the Next button, a window appears where I can enter my Google password. After entering the password and pressing the Next button, an empty window appears and nothing else happens. I expected this to show something useful, and actually add the Google account to my Gnome environment. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1687019/+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 1576864] Re: Unable to extend to second display
Note that according to https://help.ubuntu.com/community/RadeonDriver Radeon HD 6410D should be supported. $ lspci -nn | grep -E "VGA|Display" 00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Sumo [Radeon HD 6410D] [1002:9644] $ -- 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/1576864 Title: Unable to extend to second display Status in xorg package in Ubuntu: New Bug description: Upgrading from UbuntuStudio 15.10 to 16.04, my 2nd display is a no more a 1st display extension and only a clone. xrand detects only one display. $ xrandr xrandr: Failed to get size of gamma for output default Screen 0: minimum 1400 x 1050, current 1400 x 1050, maximum 1400 x 1050 default connected 1400x1050+0+0 0mm x 0mm 1400x1050 77.00* $ lspci -nn | grep VGA 00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Sumo [Radeon HD 6410D] [1002:9644] $ dmesg | egrep 'drm|radeon' [1.293303] [drm] Initialized drm 1.1.0 20060810 [1.328085] [drm] VGACON disable radeon kernel modesetting. [1.328109] [drm:radeon_init [radeon]] *ERROR* No UMS support in radeon module! [ 12.801460] [drm] VGACON disable radeon kernel modesetting. [ 12.801484] [drm:radeon_init [radeon]] *ERROR* No UMS support in radeon module! $ uname -r 4.4.0-21-lowlatency $ Seems same than bug 1407505, but apport-bug failed, so I created a new bug. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-21.37-lowlatency 4.4.6 Uname: Linux 4.4.0-21-lowlatency x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Apr 29 23:19:49 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2015-08-21 (252 days ago) InstallationMedia: Ubuntu-Studio 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to xenial on 2016-04-24 (5 days ago) --- ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 CasperVersion: 1.380 CurrentDesktop: XFCE DistroRelease: Ubuntu 17.04 LiveMediaBuild: Ubuntu-Studio 17.04 "Zesty Zapus" - Release amd64 (20170412) Package: xorg 1:7.7+16ubuntu3 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.10.0-19.21-lowlatency 4.10.8 Tags: zesty Uname: Linux 4.10.0-19-lowlatency x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1576864/+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 1626345] Re: After rebooting for updates, reboot is still required.
*** This bug is a duplicate of bug 1458204 *** https://bugs.launchpad.net/bugs/1458204 ** This bug has been marked a duplicate of bug 1458204 removing kernels should not require a restart afterward -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1626345 Title: After rebooting for updates, reboot is still required. Status in One Hundred Papercuts: Confirmed Status in unattended-upgrades package in Ubuntu: Incomplete Bug description: Yesterday unattended-upgrades required a reboot for kernel updates as expected. But today unattended-upgrades required a reboot even though there were no updates. 2016-09-20 05:20:10,409 INFO Initial blacklisted packages: 2016-09-20 05:20:10,410 INFO Initial whitelisted packages: 2016-09-20 05:20:10,411 INFO Starting unattended upgrades script 2016-09-20 05:20:10,411 INFO Allowed origins are: ['o=Ubuntu,a=xenial-security', 'o=Ubuntu,a=xenial-updates'] 2016-09-20 05:21:13,118 INFO Packages that will be upgraded: linux-generic linux-headers-generic linux-image-generic linux-libc-dev 2016-09-20 05:21:13,119 INFO Writing dpkg log to '/var/log/unattended-upgrades/unattended-upgrades-dpkg.log' 2016-09-20 05:24:17,405 INFO All upgrades installed 2016-09-20 05:24:24,959 WARNING Found /var/run/reboot-required, rebooting 2016-09-21 05:10:54,080 INFO Initial blacklisted packages: 2016-09-21 05:10:54,088 INFO Initial whitelisted packages: 2016-09-21 05:10:54,089 INFO Starting unattended upgrades script 2016-09-21 05:10:54,089 INFO Allowed origins are: ['o=Ubuntu,a=xenial-security', 'o=Ubuntu,a=xenial-updates'] 2016-09-21 05:11:02,624 INFO No packages found that can be upgraded unattended and no pending auto-removals 2016-09-21 05:11:02,624 WARNING Found /var/run/reboot-required, rebooting On this machine (16.04 server) unattended-upgrades is configured to reboot automatically. This also happened on another 16.04 server with default unattended- upgrades configuration. It displayed the ***System restart required*** message. The same on a 14.04 server and a 14.04 desktop. Expected behaviour: Not to do an unnecessary reboot. Let me know what other information I can provide. To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1626345/+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 1654448] Re: XPS 13 9360, Realtek ALC3246, Headphone audio hiss
** Attachment removed: "hwinfo" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1654448/+attachment/4869156/+files/hwinfo -- 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/1654448 Title: XPS 13 9360, Realtek ALC3246, Headphone audio hiss Status in alsa-driver package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: Pertaining to 16.04 on a dell XPS 13 9360 ii alsa-base 1.0.25+dfsg-0ubuntu5 Advanced Linux Sound Architecture Driver Version k4.4.0-57-generic. When headphones are plugged in, there is a clearly audible hiss (white noise). This is present as soon as the headphones are plugged in, whether 'headphones' or 'headset' are selected from the pop-up box. Using alsamixer to debug the issue reveals that it is related to "Headphone Mic Boost" - the default setting is: dB gain 0.00, 0.00. If this is changed to: 10.00, 10.00 (one notch up) the hiss disappears. 20.00, 20.00 cause a louder hiss and 30.00, 30.00 causes an even louder hiss with high frequency audio artifacts. When the headphones are removed and plugged back in the Headphone Mic Boost setting returns to dB gain 0 and the problem also returns. This (problem and workaround) has been reported in the wild: https://news.ycombinator.com/item?id=13050843 and https://www.reddit.com/r/Dell/comments/4j1zz4/headphones_have_static_noise_with_ubuntu_1604_on/ for example To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1654448/+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 1576864] Re: Unable to extend to second display
This bug still alive within Linux version 4.10.0-19-lowlatency (booting UbuntuStudio 17.04 from USB stick). $ egrep 'drm|radeon' /media/cyril/SanDiskBlanc/dmesg170430.log [7.414065] [drm] Initialized [7.451216] [drm] VGACON disable radeon kernel modesetting. [7.451282] [drm:radeon_init [radeon]] *ERROR* No UMS support in radeon module! [ 17.166670] [drm] VGACON disable radeon kernel modesetting. [ 17.166728] [drm:radeon_init [radeon]] *ERROR* No UMS support in radeon module! [ 29.316284] [drm] VGACON disable radeon kernel modesetting. [ 29.316343] [drm:radeon_init [radeon]] *ERROR* No UMS support in radeon module! $ (see apport information just before this post). Quite annoying because AMD proprietary driver unavailable for new kernels. Status moved from Expired to New. ** Changed in: xorg (Ubuntu) Status: Expired => 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/1576864 Title: Unable to extend to second display Status in xorg package in Ubuntu: New Bug description: Upgrading from UbuntuStudio 15.10 to 16.04, my 2nd display is a no more a 1st display extension and only a clone. xrand detects only one display. $ xrandr xrandr: Failed to get size of gamma for output default Screen 0: minimum 1400 x 1050, current 1400 x 1050, maximum 1400 x 1050 default connected 1400x1050+0+0 0mm x 0mm 1400x1050 77.00* $ lspci -nn | grep VGA 00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Sumo [Radeon HD 6410D] [1002:9644] $ dmesg | egrep 'drm|radeon' [1.293303] [drm] Initialized drm 1.1.0 20060810 [1.328085] [drm] VGACON disable radeon kernel modesetting. [1.328109] [drm:radeon_init [radeon]] *ERROR* No UMS support in radeon module! [ 12.801460] [drm] VGACON disable radeon kernel modesetting. [ 12.801484] [drm:radeon_init [radeon]] *ERROR* No UMS support in radeon module! $ uname -r 4.4.0-21-lowlatency $ Seems same than bug 1407505, but apport-bug failed, so I created a new bug. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-21.37-lowlatency 4.4.6 Uname: Linux 4.4.0-21-lowlatency x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Apr 29 23:19:49 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2015-08-21 (252 days ago) InstallationMedia: Ubuntu-Studio 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to xenial on 2016-04-24 (5 days ago) --- ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 CasperVersion: 1.380 CurrentDesktop: XFCE DistroRelease: Ubuntu 17.04 LiveMediaBuild: Ubuntu-Studio 17.04 "Zesty Zapus" - Release amd64 (20170412) Package: xorg 1:7.7+16ubuntu3 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.10.0-19.21-lowlatency 4.10.8 Tags: zesty Uname: Linux 4.10.0-19-lowlatency x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1576864/+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 1576864] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1576864/+attachment/4870019/+files/ProcCpuinfoMinimal.txt -- 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/1576864 Title: Unable to extend to second display Status in xorg package in Ubuntu: Expired Bug description: Upgrading from UbuntuStudio 15.10 to 16.04, my 2nd display is a no more a 1st display extension and only a clone. xrand detects only one display. $ xrandr xrandr: Failed to get size of gamma for output default Screen 0: minimum 1400 x 1050, current 1400 x 1050, maximum 1400 x 1050 default connected 1400x1050+0+0 0mm x 0mm 1400x1050 77.00* $ lspci -nn | grep VGA 00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Sumo [Radeon HD 6410D] [1002:9644] $ dmesg | egrep 'drm|radeon' [1.293303] [drm] Initialized drm 1.1.0 20060810 [1.328085] [drm] VGACON disable radeon kernel modesetting. [1.328109] [drm:radeon_init [radeon]] *ERROR* No UMS support in radeon module! [ 12.801460] [drm] VGACON disable radeon kernel modesetting. [ 12.801484] [drm:radeon_init [radeon]] *ERROR* No UMS support in radeon module! $ uname -r 4.4.0-21-lowlatency $ Seems same than bug 1407505, but apport-bug failed, so I created a new bug. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-21.37-lowlatency 4.4.6 Uname: Linux 4.4.0-21-lowlatency x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Apr 29 23:19:49 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2015-08-21 (252 days ago) InstallationMedia: Ubuntu-Studio 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to xenial on 2016-04-24 (5 days ago) --- ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 CasperVersion: 1.380 CurrentDesktop: XFCE DistroRelease: Ubuntu 17.04 LiveMediaBuild: Ubuntu-Studio 17.04 "Zesty Zapus" - Release amd64 (20170412) Package: xorg 1:7.7+16ubuntu3 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.10.0-19.21-lowlatency 4.10.8 Tags: zesty Uname: Linux 4.10.0-19-lowlatency x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1576864/+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 1576864] Re: Unable to extend to second display
apport information ** Tags added: apport-collected zesty ** Description changed: Upgrading from UbuntuStudio 15.10 to 16.04, my 2nd display is a no more a 1st display extension and only a clone. xrand detects only one display. $ xrandr xrandr: Failed to get size of gamma for output default Screen 0: minimum 1400 x 1050, current 1400 x 1050, maximum 1400 x 1050 default connected 1400x1050+0+0 0mm x 0mm 1400x1050 77.00* $ lspci -nn | grep VGA 00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Sumo [Radeon HD 6410D] [1002:9644] $ dmesg | egrep 'drm|radeon' [1.293303] [drm] Initialized drm 1.1.0 20060810 [1.328085] [drm] VGACON disable radeon kernel modesetting. [1.328109] [drm:radeon_init [radeon]] *ERROR* No UMS support in radeon module! [ 12.801460] [drm] VGACON disable radeon kernel modesetting. [ 12.801484] [drm:radeon_init [radeon]] *ERROR* No UMS support in radeon module! $ uname -r 4.4.0-21-lowlatency $ Seems same than bug 1407505, but apport-bug failed, so I created a new bug. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-21.37-lowlatency 4.4.6 Uname: Linux 4.4.0-21-lowlatency x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Apr 29 23:19:49 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2015-08-21 (252 days ago) InstallationMedia: Ubuntu-Studio 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to xenial on 2016-04-24 (5 days ago) + --- + ApportVersion: 2.20.4-0ubuntu4 + Architecture: amd64 + CasperVersion: 1.380 + CurrentDesktop: XFCE + DistroRelease: Ubuntu 17.04 + LiveMediaBuild: Ubuntu-Studio 17.04 "Zesty Zapus" - Release amd64 (20170412) + Package: xorg 1:7.7+16ubuntu3 + PackageArchitecture: amd64 + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=fr_FR.UTF-8 + SHELL=/bin/bash + ProcVersionSignature: Ubuntu 4.10.0-19.21-lowlatency 4.10.8 + Tags: zesty + Uname: Linux 4.10.0-19-lowlatency x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1576864/+attachment/4870017/+files/Dependencies.txt -- 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/1576864 Title: Unable to extend to second display Status in xorg package in Ubuntu: Expired Bug description: Upgrading from UbuntuStudio 15.10 to 16.04, my 2nd display is a no more a 1st display extension and only a clone. xrand detects only one display. $ xrandr xrandr: Failed to get size of gamma for output default Screen 0: minimum 1400 x 1050, current 1400 x 1050, maximum 1400 x 1050 default connected 1400x1050+0+0 0mm x 0mm 1400x1050 77.00* $ lspci -nn | grep VGA 00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Sumo [Radeon HD 6410D] [1002:9644] $ dmesg | egrep 'drm|radeon' [1.293303] [drm] Initialized drm 1.1.0 20060810 [1.328085] [drm] VGACON disable radeon kernel modesetting. [1.328109] [drm:radeon_init [radeon]] *ERROR* No UMS support in radeon module! [ 12.801460] [drm] VGACON disable radeon kernel modesetting. [ 12.801484] [drm:radeon_init [radeon]] *ERROR* No UMS support in radeon module! $ uname -r 4.4.0-21-lowlatency $ Seems same than bug 1407505, but apport-bug failed, so I created a new bug. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-21.37-lowlatency 4.4.6 Uname: Linux 4.4.0-21-lowlatency x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Apr 29 23:19:49 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2015-08-21 (252 days ago) InstallationMedia: Ubuntu-Studio 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to xenial on 2016-04-24 (5 days ago) --- ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 CasperVersion: 1.380 CurrentDesktop: XFCE DistroRelease: Ubuntu 17.04 LiveMediaBuild: Ubuntu-Studio 17.04 "Zesty Zapus" - Release amd64 (20170412) Package: xorg 1:7.7+16ubuntu3 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.10.0-19.21-lowlatency 4.10.8 Tags: zesty Uname: Linux 4.10.0-19-lowlatency x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo _M
[Touch-packages] [Bug 1576864] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1576864/+attachment/4870018/+files/JournalErrors.txt -- 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/1576864 Title: Unable to extend to second display Status in xorg package in Ubuntu: Expired Bug description: Upgrading from UbuntuStudio 15.10 to 16.04, my 2nd display is a no more a 1st display extension and only a clone. xrand detects only one display. $ xrandr xrandr: Failed to get size of gamma for output default Screen 0: minimum 1400 x 1050, current 1400 x 1050, maximum 1400 x 1050 default connected 1400x1050+0+0 0mm x 0mm 1400x1050 77.00* $ lspci -nn | grep VGA 00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Sumo [Radeon HD 6410D] [1002:9644] $ dmesg | egrep 'drm|radeon' [1.293303] [drm] Initialized drm 1.1.0 20060810 [1.328085] [drm] VGACON disable radeon kernel modesetting. [1.328109] [drm:radeon_init [radeon]] *ERROR* No UMS support in radeon module! [ 12.801460] [drm] VGACON disable radeon kernel modesetting. [ 12.801484] [drm:radeon_init [radeon]] *ERROR* No UMS support in radeon module! $ uname -r 4.4.0-21-lowlatency $ Seems same than bug 1407505, but apport-bug failed, so I created a new bug. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-21.37-lowlatency 4.4.6 Uname: Linux 4.4.0-21-lowlatency x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Apr 29 23:19:49 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2015-08-21 (252 days ago) InstallationMedia: Ubuntu-Studio 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to xenial on 2016-04-24 (5 days ago) --- ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 CasperVersion: 1.380 CurrentDesktop: XFCE DistroRelease: Ubuntu 17.04 LiveMediaBuild: Ubuntu-Studio 17.04 "Zesty Zapus" - Release amd64 (20170412) Package: xorg 1:7.7+16ubuntu3 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.10.0-19.21-lowlatency 4.10.8 Tags: zesty Uname: Linux 4.10.0-19-lowlatency x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1576864/+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 1687019] Re: Cannot add a Google account using Online Accounts in Ubuntu Gnome
** Also affects: gnome-online-accounts (Arch Linux) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1687019 Title: Cannot add a Google account using Online Accounts in Ubuntu Gnome Status in gnome-online-accounts package in Ubuntu: Confirmed Status in gnome-online-accounts package in Arch Linux: New Bug description: With Ubuntu Gnome 17.04 (brand new 64bit install on a Dell XPS13 laptop), I cannot add a Google account using Online-Accounts. If I choose to add a new Google account in Online Accounts, a window appears where I can enter my Google email. After entering my email and pressing the Next button, a window appears where I can enter my Google password. After entering the password and pressing the Next button, an empty window appears and nothing else happens. I expected this to show something useful, and actually add the Google account to my Gnome environment. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1687019/+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 1685900] Re: On artful, no working dns after upgrading to systemd 233-5ubuntu1
This bug report is being closed due to your last comment regarding this being fixed. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find. There simply isn't enough information here to tell whether there was a bug here or not, especially because you are running a custom "minimal setup" with -proposed enabled in a development release. A better bug report would include the specific steps someone else could take to reproduce the issue. ** Changed in: systemd (Ubuntu) Status: Incomplete => Invalid -- 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/1685900 Title: On artful, no working dns after upgrading to systemd 233-5ubuntu1 Status in systemd package in Ubuntu: Invalid Bug description: After upgrading to the newest systemd 233-5ubuntu1 (in artful proposed) I got no nameserver (dns). This is very likely a DNS issue. As a workaround downgrading back to systemd 232-21ubuntu3 the network and DNS work fine. Or instead, I must manually start systemd-resolved: ~$ sudo service systemd-resolved restart So something odd has happened between these versions. Systemd-resolved is not starting automatically at boot anymore. My setup is a fully upgraded artful with proposed repo turned on. I use only Gnome DE with GDM. Everything else works fine, but not systemd 233-5ubuntu1. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1685900/+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 1685193] Re: [17.04] systemd-udevd. Scripts started by a rule won't write to /var/log
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
--
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/1685193
Title:
[17.04] systemd-udevd. Scripts started by a rule won't write to
/var/log
Status in systemd package in Ubuntu:
Confirmed
Bug description:
this is rather weird problem but after upgrading to the 17.04 the pm-
powersave script I start by a udev rule stopped working. After
debuggin a bit I found a place that causes the error. In the /usr/lib
/pm-utils/pm-functions there's the init_logfile function that called
exec to redirect script's output to the /var/log/pm-powersave.log. And
it fails to do so because root (under which the script is started) has
no permission to write to anything under the /var/log/
Inside of that functions I added additional logging to prove that
1. the script is started under root
2. the file /var/log/pm-powersave.log exist and it has 644 permissions
3. the root can read from /var/log/*
4. /var permissions are 755, /var/log permissions are 775
If the script is started with 'sudo /usr/sbin/pm-powersave true' then
it works!
So what could this be? Could the apparmor prevent udevd to write to
/var/log ?
Temporary solution is to write to /tmp/pm-powersave.log
How to reproduce:
1. add the following rule to /etc/udev/rules.d/test.rules
SUBSYSTEM=="power_supply", ATTR{online}=="0", RUN+="/usr/sbin/testudev true"
SUBSYSTEM=="power_supply", ATTR{online}=="1", RUN+="/usr/sbin/testudev false"
2. create /usr/sbin/testudev script and make it executable
#!/usr/bin/env bash
logger "testudev: I'm: $(whoami)"
echo test >> /var/log/testudev.log
3. Plug and unplug the power plug. Check the syslog:
Apr 21 13:17:06 chrome root: testudev: I'm: root
Apr 21 13:17:06 chrome systemd-udevd[2]: Process '/usr/sbin/testudev
false' failed with exit code 1.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1685193/+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 1687019] Re: Cannot add a Google account using Online Accounts in Ubuntu Gnome
Confirmed with a new machine. I tried this with ubuntu 16.04 and 17.04, kept getting the same result, a blank modal dialogue after typing the password. See the attached screenshot. ** Attachment added: "Empty modal dialog after entering the password." https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1687019/+attachment/4870005/+files/gnome-online-account-bug.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1687019 Title: Cannot add a Google account using Online Accounts in Ubuntu Gnome Status in gnome-online-accounts package in Ubuntu: Confirmed Bug description: With Ubuntu Gnome 17.04 (brand new 64bit install on a Dell XPS13 laptop), I cannot add a Google account using Online-Accounts. If I choose to add a new Google account in Online Accounts, a window appears where I can enter my Google email. After entering my email and pressing the Next button, a window appears where I can enter my Google password. After entering the password and pressing the Next button, an empty window appears and nothing else happens. I expected this to show something useful, and actually add the Google account to my Gnome environment. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1687019/+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 1682193] Re: Mouse acceleration significantly reduced after upgrade to 17.04
@clel oh in case you decided to remove libinput and install evdev you need to reboot for the driver change to take effect. -- 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/1682193 Title: Mouse acceleration significantly reduced after upgrade to 17.04 Status in xorg package in Ubuntu: Confirmed Bug description: My external Logitech USB mouse was behaving nicely under 16.10 but after upgrade to 17.04 it has slowed down to a crawl. Settings slidebars are set at the maximum acceleration, but it only affects the touch pad, the mouse is extremely slow. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1682193/+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 1682193] Re: Mouse acceleration significantly reduced after upgrade to 17.04
@clel yes under pointer speed I have two sliders Acceleration and Sensitivity. Neither has any effect. BUT I was able to fix it today by removing libinput and installing evdev! Now both sliders work like before and I can increase acceleration. I don't see any problems with the system so you can try that if your system is used for educational purposes non critical daily use. I heard that they are going to switch to Wayland in the next release so this is probably all that we needed to do until the next release. Problem solved! -- 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/1682193 Title: Mouse acceleration significantly reduced after upgrade to 17.04 Status in xorg package in Ubuntu: Confirmed Bug description: My external Logitech USB mouse was behaving nicely under 16.10 but after upgrade to 17.04 it has slowed down to a crawl. Settings slidebars are set at the maximum acceleration, but it only affects the touch pad, the mouse is extremely slow. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1682193/+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 1670813] Re: package python-setuptools 20.7.0-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
This is another one where the default python is to blame sudo update-alternatives --config python is the fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-setuptools in Ubuntu. https://bugs.launchpad.net/bugs/1670813 Title: package python-setuptools 20.7.0-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in python-setuptools package in Ubuntu: New Bug description: attempting to install pip $ sudo apt-get install python-pip Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: libpython-all-dev python-all python-all-dev python-pip-whl python-setuptools python-wheel Suggested packages: python-setuptools-doc The following NEW packages will be installed libpython-all-dev python-all python-all-dev python-pip python-pip-whl python-setuptools python-wheel 0 to upgrade, 7 to newly install, 0 to remove and 5 not to upgrade. 1 not fully installed or removed. Need to get 1,475 kB of archives. After this operation, 2,614 kB of additional disk space will be used. Do you want to continue? [Y/n] y Get:1 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64 libpython-all-dev amd64 2.7.11-1 [992 B] Get:2 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64 python-all amd64 2.7.11-1 [978 B] Get:3 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64 python-all-dev amd64 2.7.11-1 [1,000 B] Get:4 http://gb.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 python-pip-whl all 8.1.1-2ubuntu0.4 [1,110 kB] Get:5 http://gb.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 python-pip all 8.1.1-2ubuntu0.4 [144 kB] Get:6 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64 python-setuptools all 20.7.0-1 [169 kB] Get:7 http://gb.archive.ubuntu.com/ubuntu xenial/universe amd64 python-wheel all 0.29.0-1 [48.0 kB] Fetched 1,475 kB in 0s (4,260 kB/s) Selecting previously unselected package libpython-all-dev:amd64. (Reading database ... 227429 files and directories currently installed.) Preparing to unpack .../libpython-all-dev_2.7.11-1_amd64.deb ... Unpacking libpython-all-dev:amd64 (2.7.11-1) ... Selecting previously unselected package python-all. Preparing to unpack .../python-all_2.7.11-1_amd64.deb ... Unpacking python-all (2.7.11-1) ... Selecting previously unselected package python-all-dev. Preparing to unpack .../python-all-dev_2.7.11-1_amd64.deb ... Unpacking python-all-dev (2.7.11-1) ... Selecting previously unselected package python-pip-whl. Preparing to unpack .../python-pip-whl_8.1.1-2ubuntu0.4_all.deb ... Unpacking python-pip-whl (8.1.1-2ubuntu0.4) ... Selecting previously unselected package python-pip. Preparing to unpack .../python-pip_8.1.1-2ubuntu0.4_all.deb ... Unpacking python-pip (8.1.1-2ubuntu0.4) ... Selecting previously unselected package python-setuptools. Preparing to unpack .../python-setuptools_20.7.0-1_all.deb ... Unpacking python-setuptools (20.7.0-1) ... Selecting previously unselected package python-wheel. Preparing to unpack .../python-wheel_0.29.0-1_all.deb ... Unpacking python-wheel (0.29.0-1) ... Processing triggers for man-db (2.7.5-1) ... Setting up python-coverage (3.7.1+dfsg.1-1ubuntu7) ... Traceback (most recent call last): File "/usr/bin/pycompile", line 35, in from debpython.version import SUPPORTED, debsorted, vrepr, \ File "/usr/share/python/debpython/version.py", line 24, in from ConfigParser import SafeConfigParser ImportError: No module named 'ConfigParser' dpkg: error processing package python-coverage (--configure): subprocess installed post-installation script returned error exit status 1 Setting up libpython-all-dev:amd64 (2.7.11-1) ... Setting up python-all (2.7.11-1) ... Setting up python-all-dev (2.7.11-1) ... Setting up python-pip-whl (8.1.1-2ubuntu0.4) ... Setting up python-pip (8.1.1-2ubuntu0.4) ... Traceback (most recent call last): File "/usr/bin/pycompile", line 35, in from debpython.version import SUPPORTED, debsorted, vrepr, \ File "/usr/share/python/debpython/version.py", line 24, in from ConfigParser import SafeConfigParser ImportError: No module named 'ConfigParser' dpkg: error processing package python-pip (--configure): subprocess installed post-installation script returned error exit status 1 Setting up python-setuptools (20.7.0-1) ... Traceback (most recent call last): File "/usr/bin/pycompile", line 35, in from debpython.version import SUPPORTED, debsorted, vrepr, \ File "/usr/share/python/debpython/version.py", line 24, in from ConfigParser import SafeConfigParser ImportError: No module named 'ConfigParser' dpkg: error processing package python-setuptools (--configure): subprocess instal
[Touch-packages] [Bug 1687019] Re: Cannot add a Google account using Online Accounts in Ubuntu Gnome
Here are two new observations on this issue: (1) After my brand new install of 17.04, I wiped the entire hard drive of my computer and re-installed 16.10 / Gnome. Online Accounts worked as expected for a while, then the bug came back as described in my initial post. So it seems this is not related to 17.04 only, as described above by others. (29 I have three different Google accounts. I can get one of these accounts working with Online Accounts, but not the other two. The difference of the working account to the others is that when I choose to add a new Google account in Online Accounts, this particular account is shown as the default in the login window. Online Accounts seems to remember this account somehow (or is it Google that remembers?): - If I accept to proceed with this default account, I am not prompted to enter my Google password for this account, and I immediately get the window telling me what kind of information will be accessed from Google. Then I can add the account to Online Accounts, and it syncs fine in Gnome. - If I choose a different account, I am prompted to enter the account name and password. Then I get the blank window as described above. It seems to me that either Online Accounts is not able to display the Google stuff following the login / password entries, which might be different to what is displayed with that "default account". This might be in line with the idea of an issue with Google's new login window. Also post 2 at https://ubuntuforums.org/showthread.php?t=282 mentions some WebKit / GTK issues; could this be related? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1687019 Title: Cannot add a Google account using Online Accounts in Ubuntu Gnome Status in gnome-online-accounts package in Ubuntu: Confirmed Bug description: With Ubuntu Gnome 17.04 (brand new 64bit install on a Dell XPS13 laptop), I cannot add a Google account using Online-Accounts. If I choose to add a new Google account in Online Accounts, a window appears where I can enter my Google email. After entering my email and pressing the Next button, a window appears where I can enter my Google password. After entering the password and pressing the Next button, an empty window appears and nothing else happens. I expected this to show something useful, and actually add the Google account to my Gnome environment. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1687019/+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 1687019] Re: Cannot add a Google account using Online Accounts in Ubuntu Gnome
Confirm here. Also similar experience to @speediedan - It was working until recently, something has changed recently (I was setting up a new machine and hit this bug, so double checked if I could add a second account to a Dell XPS 13 which is already syncing with one account). I suspect it's something to do with Google's new login page which is currently rolling out. Let me know if I can add any relevant reports. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1687019 Title: Cannot add a Google account using Online Accounts in Ubuntu Gnome Status in gnome-online-accounts package in Ubuntu: Confirmed Bug description: With Ubuntu Gnome 17.04 (brand new 64bit install on a Dell XPS13 laptop), I cannot add a Google account using Online-Accounts. If I choose to add a new Google account in Online Accounts, a window appears where I can enter my Google email. After entering my email and pressing the Next button, a window appears where I can enter my Google password. After entering the password and pressing the Next button, an empty window appears and nothing else happens. I expected this to show something useful, and actually add the Google account to my Gnome environment. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1687019/+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 1666676] Re: Install tracker by default
On Sat, Apr 29, 2017 at 5:58 PM, Khurshid Alam wrote: > @Carlos Garnacho > > I have tested this on a low-end laptops first with no tracker and then > with tracker installed with default configuration (and there our problem > lies.) The default configuration is just unacceptable. https://developer.gnome.org/gio/unstable/GSettings.html#id-1.4.19.2.9.25 > > 1. Why does tracker index bzr, vendor, pycache folders by default? I put Because nobody provided patches. I will welcome yours at https://bugzilla.gnome.org/enter_bug.cgi?product=tracker What are 'vendor' folders at all? > my git projects inside documents. You can literally see that with > tracker daemon -f. Also, It should ignore any directory starting with > "." by default It does ignore hidden files/folders, both unix and msdos style on vfat mounts > > 2. There are many other configuration available in Gsettings which > aren't exposed in GUI. As far as Tracker is concerned, UI is part of the integrator. The tracker-preferences executable is a relic and will be eventually discontinued. > > 3. I configure following things: > -- enable-writeback false > -- index-optical-discs false > -- index-on-battery false > -- index-removable-devices false > -- ignored-directories ['core-dumps', 'CVS', 'lost+found', 'po', > 'vendor', '.git'] > -- ignore-stop-words true > -- ignore-numbers true > -- max-words-to-index 1000 > -- removable-days-threshold 3 ? (I don't not understand this) - You seem to reset a bunch of those settings to their default: index-optical-discs, index-removable-devices, ignore-stop-words, ignore-numbers and removable-days-threshold - You added 'vendor' to ignored-directories, good. Adding '.git' is both useless and needless though, the hidden directory will be ignored by default anyway, what you want (and the default) is having '.git' on ignored-directories-with-content, so the parent directory is ignored (and thus the whole cloned repo). - The remaining settings (enable-writeback, index-on-battery, max-words-to-index), how did you measure the impact of these modifications? Did you reindex from scratch after every modification? What were you aiming to measure, system responsivity, indexing responsitivity, cpu usage, ... ? > > After this the system is somewhat working well. There are no aggressive > indexing. All files can still be searched from shell. Documents, Bijiben > etc works without any problems. Perhaps you've just left initial indexing to happen? Tracker is obviously smart enough to avoid reindexing stuff for the sake of it, after initial indexing happened it will sit idle most of the time unless there's file monitor events to attend to. Also, checking an unmodified, up-to-date directory tree (as it usually happens on miner startup) is orders of magnitude faster than indexing it from scratch. > > There are many options which can be disabled during compilation. For > example extractor metadata for ps.gz, gif, iso, xps, abw seems pretty > useless to me (who use it and why?). These can be disabled during > compilation. I have the feeling here and other places above that you are extrapolating personal usecases to entire user bases. Not indexing .iso files will eg. limit functionality of gnome-boxes. As for the other document/image formats, how can you tell at all they are useless? Would you think it's fair not to index the content of these documents for users that actually possess those? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/176 Title: Install tracker by default Status in nautilus package in Ubuntu: New Status in ubuntu-meta package in Ubuntu: New Bug description: For Nautilus' built-in search to not be very slow, Nautilus needs to use tracker for search. This is especially important since it's being seriously proposed for Ubuntu 17.10 that we drop the "type-ahead search" patch that reverted the removal of that feature by Nautilus years ago. (LP: #181) To not cripple Ubuntu GNOME, it was previously decided to let Nautilus build against tracker but not use that functionality on Unity. See this patch: https://bazaar.launchpad.net/~ubuntu- desktop/nautilus/ubuntu/view/head:/debian/patches/ubuntu_tracker_only_on_GNOME.patch This bug is requesting that patch be dropped and the extra tracker components be allowed into main and installed by default in Unity. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/176/+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 1186662] Re: isc-dhcp-server fails to renew lease file
Hi, Not seen your message on the launchpad topic. I would prefer reply on the topic so that the whole subscribers will be able to read it. As a summary : Slackware is not an option for me. I would choose a more professional distro like Opensuse if I had to replace *buntu. But my first choice would be that *buntu evolve to be become a professional and reliable distro. Cheers Le 7 sept. 2016 9:26 AM, "Emsi" a écrit : > I got the same on 16.04 after upgrading from 15.10. > It really sucks nobody can fix it for so many years. > Use Slackware guys. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1186662 > > Title: > isc-dhcp-server fails to renew lease file > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/ > 1186662/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1186662 Title: isc-dhcp-server fails to renew lease file Status in isc-dhcp package in Ubuntu: Fix Released Status in isc-dhcp source package in Trusty: Triaged Bug description: After raring upgrade, the dhcp server fails to renew lease file when it tries to (about every hour). The syslog says: dhcpd: Can't create new lease file: Permission denied It looks like a permission problem, because # chown -R dhcpd:dhcpd /var/lib/dhcp the above command temporarily solves the issue, until dhcpd is restarted: at that time, the ownership of the directory and the lease file is set back to root:root. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1186662/+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 1186662] Re: isc-dhcp-server fails to renew lease file
Hi all, Soon 4 years and still no fix for this issue ! I would like to know any suggestion to make this fixed : - any Canonical contact to explain that the linux community is used to say that Microsoft is very slow to fix bugs... - any famous community site to inform ubuntu users that such an issue still affects 3 LTS versions (12.04 / 14.04 / 16.04) and it is just a shame. - ? I regret a lot to write such comments but I noticed that nothing happens. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1186662 Title: isc-dhcp-server fails to renew lease file Status in isc-dhcp package in Ubuntu: Fix Released Status in isc-dhcp source package in Trusty: Triaged Bug description: After raring upgrade, the dhcp server fails to renew lease file when it tries to (about every hour). The syslog says: dhcpd: Can't create new lease file: Permission denied It looks like a permission problem, because # chown -R dhcpd:dhcpd /var/lib/dhcp the above command temporarily solves the issue, until dhcpd is restarted: at that time, the ownership of the directory and the lease file is set back to root:root. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1186662/+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 1687019] Re: Cannot add a Google account using Online Accounts in Ubuntu Gnome
Looking at the Arch Linux bug reports for gnome-online-accounts https://bugs.archlinux.org/?project=1&cat%5B%5D=2&string=gnome-online- accounts I could not see which report would correspond to this one. I Arch really does have the same bug, we should probably report this upstream. In the meantime, does anyone know how to add Google accounts for syncing? Will Unity really allow me to configure syncing in GNOME? The missing sync is a real show stopper for me! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1687019 Title: Cannot add a Google account using Online Accounts in Ubuntu Gnome Status in gnome-online-accounts package in Ubuntu: Confirmed Bug description: With Ubuntu Gnome 17.04 (brand new 64bit install on a Dell XPS13 laptop), I cannot add a Google account using Online-Accounts. If I choose to add a new Google account in Online Accounts, a window appears where I can enter my Google email. After entering my email and pressing the Next button, a window appears where I can enter my Google password. After entering the password and pressing the Next button, an empty window appears and nothing else happens. I expected this to show something useful, and actually add the Google account to my Gnome environment. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1687019/+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 1682193] Re: Mouse acceleration significantly reduced after upgrade to 17.04
@POP So acceleration is not working for you either? Because for me changing of speed or sensitivity (amount of pointer movement for a constant mouse movement) is not working and I think that is even worse. In system settings there is a slider called "pointer speed" which does not work. It used to change the sensitivity of the mouse so apparently speed and sensitivity are used interchangeable in this case. -- 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/1682193 Title: Mouse acceleration significantly reduced after upgrade to 17.04 Status in xorg package in Ubuntu: Confirmed Bug description: My external Logitech USB mouse was behaving nicely under 16.10 but after upgrade to 17.04 it has slowed down to a crawl. Settings slidebars are set at the maximum acceleration, but it only affects the touch pad, the mouse is extremely slow. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1682193/+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 1623418] Re: gcc-as-needed.diff patch broke mpx support in GCC
the binutils part was checked by looking at gold to accept the new options. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1623418 Title: gcc-as-needed.diff patch broke mpx support in GCC Status in gcc: Unknown Status in binutils package in Ubuntu: Fix Released Status in gcc-5 package in Ubuntu: Fix Released Status in gcc-6 package in Ubuntu: Fix Released Status in binutils source package in Xenial: Fix Committed Status in gcc-5 source package in Xenial: New Status in binutils source package in Yakkety: Fix Committed Status in gcc-5 source package in Yakkety: New Status in gcc-6 source package in Yakkety: New Bug description: [SRU Justification] gcc-5 from Ubuntu is configured with MPX support, but it is broken due to always-added linker option "-as-needed". [Test case] 1. Pass -mmpx to gcc when building an arbitrary project on x86. 2. Verify with ldd that the resulting executable is not linked against libmpx.so because the -as-needed flag has discarded the mpx library from being linked in. 3. Install binutils and gcc-5 from -proposed. 4. Rebuild the target, again with -mmpx. 5. Verify with ldd that the new executable is linked against libmpx.so. 6. Verify that there are no regressions in the binutils testsuite on any architectures, by manually checking the results in the build log. [Regression potential] This binutils patch implements new --push-state / --pop-state options which will not be used in the common case, only when -mmpx is passed. When these flags are not in use, which is the default, it should have no effect on the behavior of the toolchain, so risk of regression is minimal. Here is the GCC upstream bug & fix https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77267 https://gcc.gnu.org/viewcvs/gcc?view=revision&revision=240057 Would it be possible to backport this fix to Ubuntu gcc-5 build? To manage notifications about this bug go to: https://bugs.launchpad.net/gcc/+bug/1623418/+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 1687266] [NEW] After suspend shadow crash
Public bug reported: After suspend window shadows crash by ramdomize pixel colors. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-49.52~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-49-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Je adresár: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 375.39 Tue Jan 31 20:47:00 PST 2017 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4) .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.1-0ubuntu2.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sun Apr 30 10:15:54 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.8.0-36-generic, x86_64: installed bbswitch, 0.8, 4.8.0-49-generic, x86_64: installed nvidia-375, 375.39, 4.4.0-75-generic, x86_64: installed nvidia-375, 375.39, 4.8.0-36-generic, x86_64: installed nvidia-375, 375.39, 4.8.0-49-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GK104 [GeForce GTX 760] [10de:1187] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GK104 [GeForce GTX 760] [1462:2847] InstallationDate: Installed on 2017-04-29 (0 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) MachineType: MSI MS-7851 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-49-generic root=UUID=1db40f01-76fc-4cdd-8c68-1a0479920129 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/30/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V3.7 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B85I (MS-7851) 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.:bvrV3.7:bd03/30/2015:svnMSI:pnMS-7851:pvr1.0:rvnMSI:rnB85I(MS-7851):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.name: MS-7851 dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Sat Apr 29 19:37:14 2017 xserver.configfile: /etc/X11/xorg.conf xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.4-1ubuntu6.1~16.04.1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial ** Attachment added: "Kazam_screencast_0.mp4" https://bugs.launchpad.net/bugs/1687266/+attachment/4869884/+files/Kazam_screencast_0.mp4 -- 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/1687266 Title: After suspend shadow crash Status in xorg package in Ubuntu: New Bug description: After suspend window shadows crash by ramdomize pixel colors. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-49.52~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-49-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Je adresár: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 375.39 Tue Jan 31 20:47:00 PST 2017 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4) .proc.driver.nvidia
[Touch-packages] [Bug 1595695] Re: bluetooth indicator disappears every time bluetooth is being turned off
Likely same or very similar bug on Ubuntu 17.04 with Intel 7260 bluetooth hardware [8087:07dc]. Disabling Bluetooth causes indicator icon to disappear. I can make it reappear again, albeit usually in a disabled state, by enabling Bluetooth in control centre. Then to actually enable, I must enable via indicator as the last step. (Alternatively switch on->off->on in Control centre, which also finally enables Bluetooth again.) RF-kill and device states: 0. Bluetooth enabled and indicator icon visiable (normal): - "hcitool dev" shows 1 device - 3: dell-bluetooth: Bluetooth Soft blocked: no Hard blocked: no 1. After disabling Bluetooth via indicator icon (causing icon to disappear) - "hcitool dev" shows no devices - 3: dell-bluetooth: Bluetooth Soft blocked: yes Hard blocked: no 2. Enable Bluetooth in control centre Most often goes to state where a device is present, but still soft blocked, and indicator icon reappears in a disabled state. Sometimes it works as expected the first time and fully enables Bluetooth radio. This is what my system logs tell me when I disable Bluetooth: april 30 09:52:55 lhs systemd[1]: Starting Load/Save RF Kill Switch Status... april 30 09:52:55 lhs systemd[1]: Started Load/Save RF Kill Switch Status. april 30 09:52:55 lhs kernel: usb 1-1.3: USB disconnect, device number 10 april 30 09:52:55 lhs bluetoothd[883]: Endpoint unregistered: sender=:1.3932 path=/MediaEndpoint/A2DPSource april 30 09:52:55 lhs kernel: Bluetooth: hci0: turning off Intel device LED failed (-19) april 30 09:52:55 lhs systemd-rfkill[17256]: Failed to open device: No such device april 30 09:52:55 lhs bluetoothd[883]: Endpoint unregistered: sender=:1.3932 path=/MediaEndpoint/A2DPSink april 30 09:52:55 lhs dbus[865]: [system] Rejected send message, 3 matched rules; type="error", sender=":1.3932" (uid=1000 pid=12977 comm="/usr/bin/pulseaudio --start --log-target=syslog ") interface="(unset)" member="(unset)" error name="org.bluez.MediaEndpoint1.Error.NotImplemented" requested_reply="0" destination=":1.17" (uid=0 pid=883 comm="/usr/lib/bluetooth/bluetoothd ") april 30 09:52:55 lhs dbus[865]: [system] Rejected send message, 3 matched rules; type="error", sender=":1.3932" (uid=1000 pid=12977 comm="/usr/bin/pulseaudio --start --log-target=syslog ") interface="(unset)" member="(unset)" error name="org.bluez.MediaEndpoint1.Error.NotImplemented" requested_reply="0" destination=":1.17" (uid=0 pid=883 comm="/usr/lib/bluetooth/bluetoothd ") april 30 09:52:55 lhs dbus[865]: [system] Rejected send message, 3 matched rules; type="error", sender=":1.3932" (uid=1000 pid=12977 comm="/usr/bin/pulseaudio --start --log-target=syslog ") interface="(unset)" member="(unset)" error name="org.bluez.MediaEndpoint1.Error.NotImplemented" requested_reply="0" destination=":1.17" (uid=0 pid=883 comm="/usr/lib/bluetooth/bluetoothd ") april 30 09:52:55 lhs systemd[1]: bluetooth.target: Unit not needed anymore. Stopping. april 30 09:52:55 lhs dbus[865]: [system] Rejected send message, 3 matched rules; type="error", sender=":1.3932" (uid=1000 pid=12977 comm="/usr/bin/pulseaudio --start --log-target=syslog ") interface="(unset)" member="(unset)" error name="org.bluez.MediaEndpoint1.Error.NotImplemented" requested_reply="0" destination=":1.17" (uid=0 pid=883 comm="/usr/lib/bluetooth/bluetoothd ") april 30 09:52:55 lhs systemd[1]: Stopped target Bluetooth. Not too pretty, even though most complaining seems to come from Bluetooth audio integration. And here's when I enable: april 30 09:55:32 lhs systemd[1]: Starting Load/Save RF Kill Switch Status... april 30 09:55:32 lhs systemd[1]: Started Load/Save RF Kill Switch Status. april 30 09:55:32 lhs kernel: usb 1-1.3: new full-speed USB device number 11 using ehci-pci april 30 09:55:32 lhs kernel: usb 1-1.3: New USB device found, idVendor=8087, idProduct=07dc april 30 09:55:32 lhs kernel: usb 1-1.3: New USB device strings: Mfr=0, Product=0, SerialNumber=0 april 30 09:55:32 lhs systemd[1]: Reached target Bluetooth. april 30 09:55:32 lhs kernel: Bluetooth: hci0: read Intel version: 370710018002030d00 april 30 09:55:32 lhs kernel: Bluetooth: hci0: Intel Bluetooth firmware file: intel/ibt-hw-37.7.10-fw-1.80.2.3.d.bseq april 30 09:55:33 lhs kernel: Bluetooth: hci0: Intel Bluetooth firmware patch completed and activated april 30 09:55:33 lhs bluetoothd[883]: Failed to obtain handles for "Service Changed" characteristic april 30 09:55:33 lhs bluetoothd[883]: Sap driver initialization failed. april 30 09:55:33 lhs bluetoothd[883]: sap-server: Operation not permitted (1) april 30 09:55:33 lhs bluetoothd[883]: Endpoint registered: sender=:1.3932 path=/MediaEndpoint/A2DPSource april 30 09:55:33 lhs bluetoothd[883]: Endpoint registered: sender=:1.3932 path=/MediaEndpoint/A2DPSink (In the above log examples, Bluetooth enabling worked as expected. I do not yet know what conditions are required for it to not fully enable the first time, wh
[Touch-packages] [Bug 1685900] Re: On artful, no working dns after upgrading to systemd 233-5ubuntu1
Just to be clear and let those interested know, my setup is working fine now with the latest systemd (in proposed now) 233-5ubuntu1. I installed and reinstalled several packages related to systemd and the command "systemd-resolve --status" is OK now. Systemd-resolved is working well now. So this bug is self-fixed. ** Attachment removed: "Sosreport" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1685900/+attachment/4868196/+files/sosreport-HarryKaasinen.systemd-20170426130934.tar.xz -- 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/1685900 Title: On artful, no working dns after upgrading to systemd 233-5ubuntu1 Status in systemd package in Ubuntu: Incomplete Bug description: After upgrading to the newest systemd 233-5ubuntu1 (in artful proposed) I got no nameserver (dns). This is very likely a DNS issue. As a workaround downgrading back to systemd 232-21ubuntu3 the network and DNS work fine. Or instead, I must manually start systemd-resolved: ~$ sudo service systemd-resolved restart So something odd has happened between these versions. Systemd-resolved is not starting automatically at boot anymore. My setup is a fully upgraded artful with proposed repo turned on. I use only Gnome DE with GDM. Everything else works fine, but not systemd 233-5ubuntu1. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1685900/+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
