[Touch-packages] [Bug 1432843] Re: Lubuntu failed to boot
I've spent some more time in tracking this down.
If you have a video adapter that is 3D capable and supports KMS, such as
the aforementioned AMD E350 APU, you shouldn't have any issues. IF
you're running some... older hardware, then this might bite you.
Here's the change that made this occur:
http://files.sllabs.com/files/long-term/screenshots/kamikazi/vmware-broken-for-lubuntu-and-this-is-the-culprit-commit.jpg
On march 16th, xserver-xorg-video-all was moved from Depends to
Recommends in the xserver-xorg package.
This bug happens to us for two reasons:
One: lubuntu's seed specifies no-follow-recommends.
Two: We do not have an explicit dependency on xserver-xorg-video-all.
I propose that an explicit dependency is added in either lubuntu's seed,
or in one of the metapackages, to follow suit with the rest of the
crowd. They all have the packages installed, one way or another, and we
are the odd-man-out.
ubuntu-mate seems to have added their explicit dependency in the vivid cycle.
edubuntu had the explicit dependency in utopic, so they never noticed.
Xubuntu does not have no-follow-recommends, so they never noticed.
The others (ubuntu+Unity, kubuntu, etc) are all primarily based on GL
compositors these days, and simply barf on the simple 2D cards that most
of these remaining packages support.
Specifically:
xserver-xorg-video-vmware
xserver-xorg-video-vesa
xserver-xorg-video-mga
xserver-xorg-video-cirrus
xserver-xorg-video-mach64
xserver-xorg-video-trident
MGA is required to support the Matrox G200e-compatible VGA adapter found in
Nuvoton and ASPEED baseboard management controllers on various supermicro X8
and X9 series motherboards.
Mach64 is required to support some older supermicro X7-series on-motherboard
VGA adapter.
cirrus and trident are required for some emulation environments like qemu.
Most of the pieces of actual hardware that these drivers were built for
are no longer used; but they are old enough to be the popular virtual
devices to emulate.
I am not sure if these drivers will ever be updated to support DRM or
KMS, or even if it is worth it for them to be changed, with the progress
on wayland+pixman.
This comment is found in several of the seeds, and no longer seems to apply as
of the march 16th commit to xserver-xorg.
# this includes xserver-xorg-xserver-xorg-{input|video}-* (no need to add
specific drivers manually)
Here is my factual corroboration of the above set of opinions.
[code]
ubuntu@kamikazi-builder:~/seedfinder/seeds$ grep -r xserver-xorg | grep -v
xserver-xorg-input | grep -v dbg | grep -v geode
edubuntu.utopic/desktop-gnome: * (xserver-xorg-video-all)
edubuntu.vivid/desktop-gnome: * (xserver-xorg-video-all)
kubuntu.utopic/active: * xorg # this includes
xserver-xorg-xserver-xorg-{input|video}-* (no need to add specific drivers
manually)
kubuntu-active.utopic/active: * xorg # this includes
xserver-xorg-xserver-xorg-{input|video}-* (no need to add specific drivers
manually)
kubuntu-active.vivid/active: * xorg # this includes
xserver-xorg-xserver-xorg-{input|video}-* (no need to add specific drivers
manually)
platform.utopic/desktop-common: * xorg # this includes
xserver-xorg-xserver-xorg-{input|video}-* (no need to add specific drivers
manually)
platform.utopic/installer-gtk: * xserver-xorg-core-udeb
platform.utopic/installer-gtk: * xserver-xorg-video-fbdev-udeb
platform.vivid/desktop-common: * xorg # this includes
xserver-xorg-xserver-xorg-{input|video}-* (no need to add specific drivers
manually)
platform.vivid/installer-gtk: * xserver-xorg-core-udeb
platform.vivid/installer-gtk: * xserver-xorg-video-fbdev-udeb
ubuntu-mate.vivid/core: * xserver-xorg
ubuntu-mate.vivid/core: * xserver-xorg-video-all
ubuntu@kamikazi-builder:~/seedfinder/seeds$ grep -r no-follow-recommends
lubuntu.utopic/STRUCTURE:feature no-follow-recommends
lubuntu.utopic/core: * Feature: no-follow-recommends
lubuntu.utopic/desktop: * Feature: no-follow-recommends
lubuntu.vivid/STRUCTURE:feature no-follow-recommends
lubuntu.vivid/core: * Feature: no-follow-recommends
lubuntu.vivid/desktop: * Feature: no-follow-recommends
platform.utopic/build-essential: * Feature: no-follow-recommends
platform.utopic/required: * Feature: no-follow-recommends
platform.vivid/build-essential: * Feature: no-follow-recommends
platform.vivid/required: * Feature: no-follow-recommends
ubuntu.utopic/system-image: * Feature: no-follow-recommends
ubuntu.vivid/system-image: * Feature: no-follow-recommends
ubuntu-mate.vivid/STRUCTURE:feature no-follow-recommends
ubuntu-mate.vivid/cloudtop: * Feature: no-follow-recommends
ubuntu-mate.vivid/core: * Feature: no-follow-recommends
ubuntu-mate.vivid/desktop: * Feature: no-follow-recommends
ubuntu-mate.vivid/live: * Feature: no-follow-recommends
ubuntu-mate.vivid/live:# 'no-follow-recommends' is used in the seed to prevent
the following
ubuntu-mate.vivid/live:== no-follow-recommends hacks ==
ubuntu-mate.vivid/live:# software when 'no-follow-recommends' is used.
[Touch-packages] [Bug 1439313] Re: apt-key del keyid is case sensitive
** Changed in: apt (Debian) Status: New = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1439313 Title: apt-key del keyid is case sensitive Status in apt package in Ubuntu: Confirmed Status in apt package in Debian: Fix Released Bug description: Note: Confirmed on Ubuntu utopic with apt 1.0.9.2ubuntu2 Confirmed on Debian jessie apt 1.0.9.7 Behavior NOT seen on Ubuntu precise with apt 0.8.16~exp12ubuntu10.22 Behavior NOT seen on Debian wheezy apt 0.9.7.9+deb7u7 apt-key export is not case-sensitive to the hex keyid specified. Inconsistently, apt-key del is case-sensitive and won't match unless the hex keyid is uppercase. This is highly exacerbated by bug #1256565 which results in OK being printed and success being returned when apt-key del doesn't match anything. The user is reasonably left to conclude that the key has been deleted from the trusted keyring when it has not. Example: # apt-key export 7fac5991 -BEGIN PGP PUBLIC KEY BLOCK- Version: GnuPG v1 mQGiBEXwb0YRBADQva2NLpYXxgjNkbuP0LnPoEXruGmvi3XMIxjEUFuGNCP4Rj/a kv2E5VixBP1vcQFDRJ+p1puh8NU0XERlhpyZrVMzzS/RdWdyXf7E5S8oqNXsoD1z fvmI+i9b2EhHAA19Kgw7ifV8vMa4tkwslEmcTiwiw8lyUl28Wh4Et8SxzwCggDcA feGqtn3PP5YAdD0km4S4XeMEAJjlrqPoPv2Gf//tfznY2UyS9PUqFCPLHgFLe80u QhI2U5jt6jUKN4fHauvR6z3seSAsh1YyzyZCKxJFEKXCCqnrFSoh4WSJsbFNc4PN b0V0SqiTCkWADZyLT5wll8sWuQ5ylTf3z1ENoHf+G3um3/wk/+xmEHvj9HCTBEXP 78X0A/0Tqlhc2RBnEf+AqxWvM8sk8LzJI/XGjwBvKfXe+l3rnSR2kEAvGzj5Sg0X 4XmfTg4Jl8BNjWyvm2Wmjfet41LPmYJKsux3g0b8yzQxeOA4pQKKAU3Z4+rgzGmf HdwCG5MNT2A5XxD/eDd+L4fRx0HbFkIQoAi1J3YWQSiTk15fw7RMR29vZ2xlLCBJ bmMuIExpbnV4IFBhY2thZ2UgU2lnbmluZyBLZXkgPGxpbnV4LXBhY2thZ2VzLWtl eW1hc3RlckBnb29nbGUuY29tPohjBBMRAgAjAhsDBgsJCAcDAgQVAggDBBYCAwEC HgECF4AFAkYVdn8CGQEACgkQoECDD3+sWZHKSgCfdq3HtNYJLv+XZleb6HN4zOcF AJEAniSFbuv8V5FSHxeRimHx25671az+uQINBEXwb0sQCACuA8HT2nr+FM5y/kzI A51ZcC46KFtIDgjQJ31Q3OrkYP8LbxOpKMRIzvOZrsjOlFmDVqitiVc7qj3lYp6U rgNVaFv6Qu4bo2/ctjNHDDBdv6nufmusJUWq/9TwieepM/cwnXd+HMxu1XBKRVk9 XyAZ9SvfcW4EtxVgysI+XlptKFa5JCqFM3qJllVohMmr7lMwO8+sxTWTXqxsptJo pZeKz+UBEEqPyw7CUIVYGC9ENEtIMFvAvPqnhj1GS96REMpry+5s9WKuLEaclWpd K3krttbDlY1NaeQUCRvBYZ8iAG9YSLHUHMTuI2oea07Rh4dtIAqPwAX8xn36JAYG 2vgLAAMFB/wKqaycjWAZwIe98Yt0qHsdkpmIbarD9fGiA6kfkK/UxjL/k7tmS4Vm CljrrDZkPSQ/19mpdRcGXtb0NI9+nyM5trweTvtPw+HPkDiJlTaiCcx+izg79Fj9 KcofuNb3lPdXZb9tzf5oDnmm/B+4vkeTuEZJ//IFty8cmvCpzvY+DAz1Vo9rA+Zn cpWY1n6z6oSS9AsyT/IFlWWBZZ17SpMHu+h4Bxy62+AbPHKGSujEGQhWq8ZRoJAT G0KSObnmZ7FwFWu1e9XFoUCt0bSjiJWTIyaObMrWu/LvJ3e9I87HseSJStfw6fki 5og9qFEkMrIrBCp3QGuQWBq/rTdMuwNFiEkEGBECAAkFAkXwb0sCGwwACgkQoECD D3+sWZF/WACfeNAu1/1hwZtUo1bR+MWiCjpvHtwAnA1R3IHqFLQ2X3xJ40XPuAyY /FJG =Quqp -END PGP PUBLIC KEY BLOCK- # apt-key del 7fac5991 OK # echo $? 0 # apt-key export 7fac5991 -BEGIN PGP PUBLIC KEY BLOCK- Version: GnuPG v1 mQGiBEXwb0YRBADQva2NLpYXxgjNkbuP0LnPoEXruGmvi3XMIxjEUFuGNCP4Rj/a kv2E5VixBP1vcQFDRJ+p1puh8NU0XERlhpyZrVMzzS/RdWdyXf7E5S8oqNXsoD1z fvmI+i9b2EhHAA19Kgw7ifV8vMa4tkwslEmcTiwiw8lyUl28Wh4Et8SxzwCggDcA feGqtn3PP5YAdD0km4S4XeMEAJjlrqPoPv2Gf//tfznY2UyS9PUqFCPLHgFLe80u QhI2U5jt6jUKN4fHauvR6z3seSAsh1YyzyZCKxJFEKXCCqnrFSoh4WSJsbFNc4PN b0V0SqiTCkWADZyLT5wll8sWuQ5ylTf3z1ENoHf+G3um3/wk/+xmEHvj9HCTBEXP 78X0A/0Tqlhc2RBnEf+AqxWvM8sk8LzJI/XGjwBvKfXe+l3rnSR2kEAvGzj5Sg0X 4XmfTg4Jl8BNjWyvm2Wmjfet41LPmYJKsux3g0b8yzQxeOA4pQKKAU3Z4+rgzGmf HdwCG5MNT2A5XxD/eDd+L4fRx0HbFkIQoAi1J3YWQSiTk15fw7RMR29vZ2xlLCBJ bmMuIExpbnV4IFBhY2thZ2UgU2lnbmluZyBLZXkgPGxpbnV4LXBhY2thZ2VzLWtl eW1hc3RlckBnb29nbGUuY29tPohjBBMRAgAjAhsDBgsJCAcDAgQVAggDBBYCAwEC HgECF4AFAkYVdn8CGQEACgkQoECDD3+sWZHKSgCfdq3HtNYJLv+XZleb6HN4zOcF AJEAniSFbuv8V5FSHxeRimHx25671az+uQINBEXwb0sQCACuA8HT2nr+FM5y/kzI A51ZcC46KFtIDgjQJ31Q3OrkYP8LbxOpKMRIzvOZrsjOlFmDVqitiVc7qj3lYp6U rgNVaFv6Qu4bo2/ctjNHDDBdv6nufmusJUWq/9TwieepM/cwnXd+HMxu1XBKRVk9 XyAZ9SvfcW4EtxVgysI+XlptKFa5JCqFM3qJllVohMmr7lMwO8+sxTWTXqxsptJo pZeKz+UBEEqPyw7CUIVYGC9ENEtIMFvAvPqnhj1GS96REMpry+5s9WKuLEaclWpd K3krttbDlY1NaeQUCRvBYZ8iAG9YSLHUHMTuI2oea07Rh4dtIAqPwAX8xn36JAYG 2vgLAAMFB/wKqaycjWAZwIe98Yt0qHsdkpmIbarD9fGiA6kfkK/UxjL/k7tmS4Vm CljrrDZkPSQ/19mpdRcGXtb0NI9+nyM5trweTvtPw+HPkDiJlTaiCcx+izg79Fj9 KcofuNb3lPdXZb9tzf5oDnmm/B+4vkeTuEZJ//IFty8cmvCpzvY+DAz1Vo9rA+Zn cpWY1n6z6oSS9AsyT/IFlWWBZZ17SpMHu+h4Bxy62+AbPHKGSujEGQhWq8ZRoJAT G0KSObnmZ7FwFWu1e9XFoUCt0bSjiJWTIyaObMrWu/LvJ3e9I87HseSJStfw6fki 5og9qFEkMrIrBCp3QGuQWBq/rTdMuwNFiEkEGBECAAkFAkXwb0sCGwwACgkQoECD D3+sWZF/WACfeNAu1/1hwZtUo1bR+MWiCjpvHtwAnA1R3IHqFLQ2X3xJ40XPuAyY /FJG =Quqp -END PGP PUBLIC KEY BLOCK- # apt-key del 7FAC5991 OK # echo $? 0 # apt-key export 7fac5991 gpg: WARNING: nothing exported To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1439313/+subscriptions -- Mailing list:
[Touch-packages] [Bug 1359249] Re: Launching PAVUControl works from Xubuntu, but not from Xfce
same as #1443229. I investigate the source code of indicator-sound, and find that in src/service.vala: var env = Environment.get_variable (DESKTOP_SESSION); string cmd; if (env == xubuntu || env == ubuntustudio) cmd = pavucontrol; else I think you would support more desktop environment such as XFCE by adding || env == xfce -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-sound in Ubuntu. https://bugs.launchpad.net/bugs/1359249 Title: Launching PAVUControl works from Xubuntu, but not from Xfce Status in indicator-sound package in Ubuntu: Confirmed Bug description: In Xubuntu 14.04 when clicking the sound indicator and choosing Sound Settings Pavucontrol is launched, but it does not get launched in the same scenario when the session Xfce is launched instead, with the same settings. In fact I installed the xfce4 package on top of Xubuntu's and launched it. Both xsession files list the same thing to start it, so is indicator only choosing to work on whitelisted sessions? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1359249/+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 1432843] Re: Lubuntu failed to boot
Here's an *UNOFFICIAL* ISO based on beta2 (I built it on march 30th) with the packages corrected. You may use it to test to see if the specific fix I've played with will work on other people's hardware. http://files.sllabs.com/files/long-term/downloads/isos/kamikazi-15.04-beta2-amd64.iso Your milage may very, do not rely on this ISO for production purposes, ONLY TESTING! IF you're gonna install, use the official alternate ISOs instead and add the xserver-xorg-video-all package (and it's dependencies!) before rebooting. If it breaks, you are advised to keep both pieces. -- 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/1432843 Title: Lubuntu failed to boot Status in X.Org X server: Confirmed Status in lubuntu-meta package in Ubuntu: Triaged Status in xorg package in Ubuntu: Triaged Bug description: The daily build of Lubuntu 20150316 failed to boot into the live session, and fails to install. During the boot session, the Lubuntu splash screen appears indicating that Lubuntu was loading. What follows next was a blank screen. Unfortunately, I cannot sumit the exact version of syslinux since the daily build could not boot into an interactive session. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: syslinux 3:6.03~pre18+dfsg-1ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0 Uname: Linux 3.19.0-7-generic i686 ApportVersion: 2.16.2-0ubuntu1 Architecture: i386 Date: Mon Mar 16 17:19:35 2015 Dependencies: gcc-5-base 5-20150228-1ubuntu1 libc6 2.19-15ubuntu2 libgcc1 1:5-20150228-1ubuntu1 mtools 4.0.18-2 multiarch-support 2.19-15ubuntu2 InstallationDate: Installed on 2015-03-05 (11 days ago) InstallationMedia: Lubuntu 15.04 Vivid Vervet - Alpha i386 (20150303) SourcePackage: syslinux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1432843/+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 1432843] Re: Lubuntu failed to boot
Den 2015-04-14 08:06, Kamilion skrev: Here's an *UNOFFICIAL* ISO based on beta2 (I built it on march 30th) with the packages corrected. You may use it to test to see if the specific fix I've played with will work on other people's hardware. http://files.sllabs.com/files/long-term/downloads/isos/kamikazi-15.04-beta2-amd64.iso Your milage may very, do not rely on this ISO for production purposes, ONLY TESTING! IF you're gonna install, use the official alternate ISOs instead and add the xserver-xorg-video-all package (and it's dependencies!) before rebooting. If it breaks, you are advised to keep both pieces. Thanks a lot Kamilion, for this promising contribution to squash a nasty bug. I'll try in my two failing computers. Please post the md5sum of your *UNOFFICIAL* ISO file. Best regards Nio -- 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/1432843 Title: Lubuntu failed to boot Status in X.Org X server: Confirmed Status in lubuntu-meta package in Ubuntu: Triaged Status in xorg package in Ubuntu: Triaged Bug description: The daily build of Lubuntu 20150316 failed to boot into the live session, and fails to install. During the boot session, the Lubuntu splash screen appears indicating that Lubuntu was loading. What follows next was a blank screen. Unfortunately, I cannot sumit the exact version of syslinux since the daily build could not boot into an interactive session. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: syslinux 3:6.03~pre18+dfsg-1ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0 Uname: Linux 3.19.0-7-generic i686 ApportVersion: 2.16.2-0ubuntu1 Architecture: i386 Date: Mon Mar 16 17:19:35 2015 Dependencies: gcc-5-base 5-20150228-1ubuntu1 libc6 2.19-15ubuntu2 libgcc1 1:5-20150228-1ubuntu1 mtools 4.0.18-2 multiarch-support 2.19-15ubuntu2 InstallationDate: Installed on 2015-03-05 (11 days ago) InstallationMedia: Lubuntu 15.04 Vivid Vervet - Alpha i386 (20150303) SourcePackage: syslinux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1432843/+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 1443774] [NEW] Horizontal scrolling is backwards
Public bug reported: Don't know where to report this specifically, sorry. In native gnome applications (file manager, gedit, etc), scrolling horizontally via Trackpoint middle-button scrolling is backwards: * Middle button + trackpoint move up = scroll up (expected) * Middle button + trackpoint move down = scroll down (expected) * Middle button + trackpoint move left = scroll right (backwards) * Middle button + trackpoint move right = scroll left (backwards) Scolling horizontally in Firefox and Chromium work as expected. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity 7.3.2+15.04.20150410.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-13.13-generic 3.19.3 Uname: Linux 3.19.0-13-generic x86_64 ApportVersion: 2.17-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Mon Apr 13 23:36:58 2015 InstallationDate: Installed on 2015-03-07 (38 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) SourcePackage: unity UpgradeStatus: Upgraded to vivid on 2015-03-29 (16 days ago) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages vivid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1443774 Title: Horizontal scrolling is backwards Status in unity package in Ubuntu: New Bug description: Don't know where to report this specifically, sorry. In native gnome applications (file manager, gedit, etc), scrolling horizontally via Trackpoint middle-button scrolling is backwards: * Middle button + trackpoint move up = scroll up (expected) * Middle button + trackpoint move down = scroll down (expected) * Middle button + trackpoint move left = scroll right (backwards) * Middle button + trackpoint move right = scroll left (backwards) Scolling horizontally in Firefox and Chromium work as expected. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity 7.3.2+15.04.20150410.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-13.13-generic 3.19.3 Uname: Linux 3.19.0-13-generic x86_64 ApportVersion: 2.17-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Mon Apr 13 23:36:58 2015 InstallationDate: Installed on 2015-03-07 (38 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) SourcePackage: unity UpgradeStatus: Upgraded to vivid on 2015-03-29 (16 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1443774/+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 1439695] Re: Cannot set ACL from python
This bug was fixed in the package libsignon-glib - 1.12+15.04.20150410.3-0ubuntu1 --- libsignon-glib (1.12+15.04.20150410.3-0ubuntu1) vivid; urgency=medium [ Alberto Mardegan ] * Merge from upstream: - Introspection: mark ACL and realms as string lists (LP: #1439695) -- CI Train Bot ci-train-...@canonical.com Fri, 10 Apr 2015 08:30:16 + ** Changed in: libsignon-glib (Ubuntu) Status: In Progress = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libsignon-glib in Ubuntu. https://bugs.launchpad.net/bugs/1439695 Title: Cannot set ACL from python Status in libsignon-glib package in Ubuntu: Fix Released Bug description: The introspection information for the IdentityInfo.set_access_control_list() method is wrong, making it impossible to set an ACL on the identity. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsignon-glib/+bug/1439695/+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 1425447] Re: pulseaudio crashed with SIGABRT in core_free() at login
Hi Raymond, This bug is about a crash in PulseAudio. In case you're interested in following up on jack detection, could you do so somewhere else, e g by contacting the bug reporter instead? Thanks. -- 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/1425447 Title: pulseaudio crashed with SIGABRT in core_free() at login Status in PulseAudio sound server: Unknown Status in pulseaudio package in Ubuntu: Confirmed Status in pulseaudio package in Fedora: Unknown Bug description: When I login, I get no sound, a Dummy Output device which is not functional, and then an error report about this. ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: pulseaudio 1:6.0-0ubuntu3 ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5 Uname: Linux 3.18.0-13-generic x86_64 ApportVersion: 2.16.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: GNOME Date: Wed Feb 25 03:14:39 2015 ExecutablePath: /usr/bin/pulseaudio InstallationDate: Installed on 2013-09-29 (513 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64+mac (20130424) ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog Signal: 6 SourcePackage: pulseaudio StacktraceTop: ?? () from /usr/lib/libpulsecore-6.0.so main () Title: pulseaudio crashed with SIGABRT in main() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 11/19/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA12:bd11/19/2008:svnDellInc.:pnXPSM1530:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: XPS M1530 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1425447/+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 1060081] Re: aptd crashed with UnicodeDecodeError in _emit_acquire_item(): 'utf-8' codec can't decode byte 0x93 in position 1: invalid start byte
** Changed in: apt (Debian) Status: New = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1060081 Title: aptd crashed with UnicodeDecodeError in _emit_acquire_item(): 'utf-8' codec can't decode byte 0x93 in position 1: invalid start byte Status in apt package in Ubuntu: New Status in aptdaemon package in Ubuntu: Confirmed Status in apt package in Debian: Fix Released Bug description: - ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: aptdaemon 0.45+bzr861-0ubuntu5 ProcVersionSignature: Ubuntu 3.5.0-16.25-generic 3.5.4 Uname: Linux 3.5.0-16-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.6.1-0ubuntu1 Architecture: amd64 Date: Tue Oct 2 06:17:45 2012 ExecutablePath: /usr/sbin/aptd InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427.1) InterpreterPath: /usr/bin/python3.2mu PackageArchitecture: all ProcCmdline: /usr/bin/python3.2 /usr/sbin/aptd ProcEnviron: PythonArgs: ['/usr/sbin/aptd'] SourcePackage: aptdaemon Title: aptd crashed with UnicodeDecodeError in _emit_acquire_item(): 'utf-8' codec can't decode byte 0x93 in position 1: invalid start byte UpgradeStatus: Upgraded to quantal on 2012-09-22 (9 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1060081/+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 1441961] Re: dataChanged signal cannot be used on ARM under certain conditions
The patch you point to was never applied to Ubuntu packages. Even more, we have reverted it in all our releases. The proper fix to this bug on ARM is in binutils: https://sourceware.org/git/gitweb.cgi?p=binutils- gdb.git;a=commitdiff;h=97323ad11305. Dear binutils maintainers: do you think it will be possible to backport the above fix to Trusty? ** Also affects: binutils (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1441961 Title: dataChanged signal cannot be used on ARM under certain conditions Status in binutils package in Ubuntu: New Status in qtbase-opensource-src package in Ubuntu: New Bug description: This is probably the strangest bug I have ever observed, but it is completely reproducible. When running the attached Qt application, I receive the following error: QObject::connect: signal not found in Test This error is 100% reproducible on my Raspberry Pi 2 running Ubuntu 14.04.2 (Trusty). This device has an ARMv7 CPU (Broadcom BCM2836). I cannot reproduce this error on any other hardware (x86 and amd64 have been tested). This does not appear to be a compiler bug since both g++ and Clang produce an executable that prints the above error. Here's the thing that really confuses me: the error disappears (and everything works correctly) if I comment out the dataChanged(...) line in test.cpp. This is completely bizarre because the line is never executed by any code. I've tried digging through Qt's headers and buried myself neck-deep in macros, templates, and MOC-generated files. I can't make any sense out of this. Therefore I am reporting it as a bug. To compile the example, enter the source directory, run qmake, and then run make to build the executable. Remember, the bug only manifests itself on an ARM CPU. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1441961/+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 1443783] Re: unity8 can not run because of ServerPropertySynchroniser
i am sorry,i forget to upgrade -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1443783 Title: unity8 can not run because of ServerPropertySynchroniser Status in unity8 package in Ubuntu: New Bug description: unity8 cannot work because of ServerPropertySynchroniser,there is no a type named ServerPropertySynchroniser To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1443783/+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 1443785] [NEW] unity8 can not run because of ServerPropertySynchroniser
Public bug reported: there is no a type named ServerPropertySynchroniser ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1443785 Title: unity8 can not run because of ServerPropertySynchroniser Status in unity8 package in Ubuntu: New Bug description: there is no a type named ServerPropertySynchroniser To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1443785/+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 1443823] Re: pulseaudio crashed with SIGABRT in pa_object_unref()
*** This bug is a duplicate of bug 1430785 *** https://bugs.launchpad.net/bugs/1430785 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1430785, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: CoreDump.gz https://bugs.launchpad.net/bugs/1443823/+attachment/4374828/+files/CoreDump.gz ** Attachment removed: Disassembly.txt https://bugs.launchpad.net/bugs/1443823/+attachment/4374831/+files/Disassembly.txt ** Attachment removed: ProcMaps.txt https://bugs.launchpad.net/bugs/1443823/+attachment/4374833/+files/ProcMaps.txt ** Attachment removed: ProcStatus.txt https://bugs.launchpad.net/bugs/1443823/+attachment/4374834/+files/ProcStatus.txt ** Attachment removed: Registers.txt https://bugs.launchpad.net/bugs/1443823/+attachment/4374835/+files/Registers.txt ** Attachment removed: Stacktrace.txt https://bugs.launchpad.net/bugs/1443823/+attachment/4374836/+files/Stacktrace.txt ** Attachment removed: ThreadStacktrace.txt https://bugs.launchpad.net/bugs/1443823/+attachment/4374837/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1430785 ** Information type changed from Private to Public ** Tags removed: need-i386-retrace -- 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/1443823 Title: pulseaudio crashed with SIGABRT in pa_object_unref() Status in pulseaudio package in Ubuntu: New Bug description: apport showed up indicating ubuntu had an error ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: pulseaudio 1:6.0-0ubuntu5 Uname: Linux 4.0.0-rc7-custom i686 ApportVersion: 2.17-0ubuntu2 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: dylan 11174 F pulseaudio /dev/snd/controlC1: dylan 11174 F pulseaudio /dev/snd/controlC0: dylan 11174 F pulseaudio Date: Tue Apr 14 10:38:27 2015 ExecutablePath: /usr/bin/pulseaudio InstallationDate: Installed on 2011-11-11 (1249 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release i386 (20111012) ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog ProcEnviron: PATH=(custom, no user) LANGUAGE=en_US:en_GB:mt:en XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/false PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Signal: 6 SourcePackage: pulseaudio StacktraceTop: ?? () from /usr/lib/libpulsecore-6.0.so pa_object_unref () from /usr/lib/libpulsecore-6.0.so main () Title: pulseaudio crashed with SIGABRT in pa_object_unref() UpgradeStatus: Upgraded to vivid on 2015-03-31 (13 days ago) UserGroups: dmi.bios.date: 07/15/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0703 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8H67-M dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0703:bd07/15/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8H67-M:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1443823/+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 1378867] Re: [oobe] wizard should provide option to connect to hidden networks
** Description changed: Users should have an option to connect to hidden networks in the set up wizard. The behaviour should mimic the current implementation in system settings. Design added this functionality on the Wifi screens in the oobe, please see attached images for reference. + + The PC equivalent is bug 833312. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1378867 Title: [oobe] wizard should provide option to connect to hidden networks Status in Ubuntu UX bugs: Fix Committed Status in ubuntu-system-settings package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Confirmed Bug description: Users should have an option to connect to hidden networks in the set up wizard. The behaviour should mimic the current implementation in system settings. Design added this functionality on the Wifi screens in the oobe, please see attached images for reference. The PC equivalent is bug 833312. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1378867/+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 1407907] Re: [phone] Leaving WiFi coverage often leads to the password dialog being displayed indefinitely
Specification updated. https://wiki.ubuntu.com/Networking?action=diffrev2=259rev1=258 ** Changed in: network-manager (Ubuntu) Status: Confirmed = Triaged ** Description changed: Steps: * connect to a password-protected WiFi network * suspend the phone * turn the WiFi off or leave the network's covered area * resume the phone Expected: * phone is connected via a GSM data connection Current: * phone is connected via a GSM data connection * there is a WiFi password dialog displayed for a network that isn't in range any more (and for which the password is known) ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: indicator-network 0.5.1+15.04.20141216-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.15-0ubuntu3 Architecture: armhf Date: Tue Jan 6 10:19:05 2015 InstallationDate: Installed on 2014-12-18 (19 days ago) InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf (20141218-020204) SourcePackage: indicator-network UpgradeStatus: No upgrade log present (probably fresh install) + + https://wiki.ubuntu.com/Networking#wi-fi-authenticating: Regardless + of the dialog variation, if it is still open when the network stops + being available — for example, if the network is no longer in range, or + if you switch into Flight Mode — the commit buttons should be replaced + by the centered text “Network no longer available”, all the dialog’s + controls should become insensitive, and two seconds later, the dialog + should close. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1407907 Title: [phone] Leaving WiFi coverage often leads to the password dialog being displayed indefinitely Status in the base for Ubuntu mobile products: Confirmed Status in indicator-network package in Ubuntu: Invalid Status in network-manager package in Ubuntu: Triaged Status in unity8 package in Ubuntu: Invalid Bug description: Steps: * connect to a password-protected WiFi network * suspend the phone * turn the WiFi off or leave the network's covered area * resume the phone Expected: * phone is connected via a GSM data connection Current: * phone is connected via a GSM data connection * there is a WiFi password dialog displayed for a network that isn't in range any more (and for which the password is known) ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: indicator-network 0.5.1+15.04.20141216-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.15-0ubuntu3 Architecture: armhf Date: Tue Jan 6 10:19:05 2015 InstallationDate: Installed on 2014-12-18 (19 days ago) InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf (20141218-020204) SourcePackage: indicator-network UpgradeStatus: No upgrade log present (probably fresh install) https://wiki.ubuntu.com/Networking#wi-fi-authenticating: Regardless of the dialog variation, if it is still open when the network stops being available — for example, if the network is no longer in range, or if you switch into Flight Mode — the commit buttons should be replaced by the centered text “Network no longer available”, all the dialog’s controls should become insensitive, and two seconds later, the dialog should close. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1407907/+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 1433177] Re: Organic grid renderer not available
This layout is now depreciated and not used in Scopes going forward, so marking as won't fix. ** Changed in: unity8 (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 unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1433177 Title: Organic grid renderer not available Status in unity8 package in Ubuntu: Won't Fix Bug description: In the original design documents for the new scopes framework, there was an organic grid renderer that has not been implemented ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity8 8.00+14.10.20141013.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1 Uname: Linux 3.16.0-28-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Tue Mar 17 12:00:55 2015 InstallationDate: Installed on 2014-10-11 (156 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) SourcePackage: unity8 UpgradeStatus: Upgraded to utopic on 2014-10-20 (148 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1433177/+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 1407907] Re: [phone] Leaving WiFi coverage often leads to the password dialog being displayed indefinitely
Oops, I got that wrong. This doesn't apply to the dialog for connecting to a hidden network, because we don't know whether it's in range until we try connecting to it. Specification updated again. https://wiki.ubuntu.com/Networking?action=diffrev2=260rev1=259 ** Description changed: Steps: * connect to a password-protected WiFi network * suspend the phone * turn the WiFi off or leave the network's covered area * resume the phone Expected: * phone is connected via a GSM data connection Current: * phone is connected via a GSM data connection * there is a WiFi password dialog displayed for a network that isn't in range any more (and for which the password is known) ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: indicator-network 0.5.1+15.04.20141216-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.15-0ubuntu3 Architecture: armhf Date: Tue Jan 6 10:19:05 2015 InstallationDate: Installed on 2014-12-18 (19 days ago) InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf (20141218-020204) SourcePackage: indicator-network UpgradeStatus: No upgrade log present (probably fresh install) - https://wiki.ubuntu.com/Networking#wi-fi-authenticating: Regardless - of the dialog variation, if it is still open when the network stops - being available — for example, if the network is no longer in range, or - if you switch into Flight Mode — the commit buttons should be replaced - by the centered text “Network no longer available”, all the dialog’s - controls should become insensitive, and two seconds later, the dialog - should close. + https://wiki.ubuntu.com/Networking#wi-fi-authenticating: If the + network stops being available while the dialog is still open — for + example, if the network is no longer in range, or if you switch into + Flight Mode — the commit buttons should be replaced by the centered text + “Network no longer available”, all the dialog’s controls should become + insensitive, and two seconds later, the dialog should close. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1407907 Title: [phone] Leaving WiFi coverage often leads to the password dialog being displayed indefinitely Status in the base for Ubuntu mobile products: Confirmed Status in indicator-network package in Ubuntu: Invalid Status in network-manager package in Ubuntu: Triaged Status in unity8 package in Ubuntu: Invalid Bug description: Steps: * connect to a password-protected WiFi network * suspend the phone * turn the WiFi off or leave the network's covered area * resume the phone Expected: * phone is connected via a GSM data connection Current: * phone is connected via a GSM data connection * there is a WiFi password dialog displayed for a network that isn't in range any more (and for which the password is known) ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: indicator-network 0.5.1+15.04.20141216-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.15-0ubuntu3 Architecture: armhf Date: Tue Jan 6 10:19:05 2015 InstallationDate: Installed on 2014-12-18 (19 days ago) InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf (20141218-020204) SourcePackage: indicator-network UpgradeStatus: No upgrade log present (probably fresh install) https://wiki.ubuntu.com/Networking#wi-fi-authenticating: If the network stops being available while the dialog is still open — for example, if the network is no longer in range, or if you switch into Flight Mode — the commit buttons should be replaced by the centered text “Network no longer available”, all the dialog’s controls should become insensitive, and two seconds later, the dialog should close. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1407907/+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 996906]
Both commands produce underruns at large, audible and visible in the output. aplay -D hw:0,0 -v --buffer-time=4000 /tmp/fr025.wav Playing WAVE '/tmp/fr025.wav' : Signed 16 bit Little Endian, Rate 44100 Hz, Stereo Hardware PCM card 0 'HDA Intel PCH' device 0 subdevice 0 Its setup is: stream : PLAYBACK access : RW_INTERLEAVED format : S16_LE subformat: STD channels : 2 rate : 44100 exact rate : 44100 (44100/1) msbits : 16 buffer_size : 192 period_size : 32 period_time : 725 tstamp_mode : NONE period_step : 1 avail_min: 32 period_event : 0 start_threshold : 192 stop_threshold : 192 silence_threshold: 0 silence_size : 0 boundary : 6917529027641081856 appl_ptr : 0 hw_ptr : 0 underrun!!! (at least 4.191 ms long) Status: state : XRUN trigger_time: 3336.7694317 tstamp : 3336.11882117 delay : 0 avail : 200 avail_max : 200 underrun!!! (at least 1.832 ms long) Status: state : XRUN trigger_time: 3336.30152303 tstamp : 3336.31983077 delay : 0 avail : 194 avail_max : 194 underrun!!! (at least 0.312 ms long) Status: state : XRUN trigger_time: 3337.6068547 tstamp : 3337.6379149 delay : 0 avail : 200 avail_max : 200 underrun!!! (at least 4.293 ms long) Status: state : XRUN trigger_time: 3339.4484089 tstamp : 3339.8775797 delay : 0 avail : 200 avail_max : 200 underrun!!! (at least 11.592 ms long) Status: state : XRUN trigger_time: 3343.6272217 tstamp : 3343.17862683 delay : 0 avail : 200 avail_max : 200 underrun!!! (at least 2.310 ms long) Status: state : XRUN trigger_time: 3343.700965780 tstamp : 3343.703274524 delay : 0 avail : 200 avail_max : 200 ^CAborted by signal Interrupt... aplay -D hw:0,0 -v --period-time=2000 --buffer-time=4000 /tmp/fr025.wav Playing WAVE '/tmp/fr025.wav' : Signed 16 bit Little Endian, Rate 44100 Hz, Stereo Hardware PCM card 0 'HDA Intel PCH' device 0 subdevice 0 Its setup is: stream : PLAYBACK access : RW_INTERLEAVED format : S16_LE subformat: STD channels : 2 rate : 44100 exact rate : 44100 (44100/1) msbits : 16 buffer_size : 192 period_size : 96 period_time : 2176 tstamp_mode : NONE period_step : 1 avail_min: 96 period_event : 0 start_threshold : 192 stop_threshold : 192 silence_threshold: 0 silence_size : 0 boundary : 6917529027641081856 appl_ptr : 0 hw_ptr : 0 underrun!!! (at least 8.673 ms long) Status: state : XRUN trigger_time: 3355.4367755 tstamp : 3355.13037189 delay : 0 avail : 200 avail_max : 200 underrun!!! (at least 2.189 ms long) Status: state : XRUN trigger_time: 3356.24657841 tstamp : 3356.26845873 delay : 0 avail : 200 avail_max : 200 underrun!!! (at least 2.160 ms long) Status: state : XRUN trigger_time: 3358.690871062 tstamp : 3358.693029225 delay : 0 avail : 281 avail_max : 281 underrun!!! (at least 3.647 ms long) Status: state : XRUN trigger_time: 3360.9384022 tstamp : 3360.13029349 delay : 0 avail : 200 avail_max : 200 underrun!!! (at least 1.095 ms long) Status: state : XRUN trigger_time: 3361.11945732 tstamp : 3361.13039182 delay : 0 avail : 200 avail_max : 200 underrun!!! (at least 3.016 ms long) Status: state : XRUN trigger_time: 3361.132006217 tstamp : 3361.135020659 delay : 0 avail : 200 avail_max : 200 underrun!!! (at least 0.352 ms long) Status: state : XRUN trigger_time: 3361.465478201 tstamp : 3361.465829023 delay : 0 avail : 200 avail_max : 200 underrun!!! (at least 2.799 ms long) Status: state : XRUN trigger_time: 3361.502227029 tstamp : 3361.505024503 delay : 0 avail : 200 avail_max : 200 underrun!!! (at least 0.019 ms long) Status: state : XRUN trigger_time: 3361.513310022 tstamp : 3361.513327710 delay : 0 avail : 200 avail_max : 200 ^CAborted by signal Interrupt... Also, after I do: echo 1 /proc/asound/card0/pcm0p/xrun_debug I have lots of this in dmesg: [ 3504.140844] ALSA: PCM: [Q] Lost interrupts?: (stream=0, delta=56, new_hw_ptr=809, old_hw_ptr=753) [ 3504.143264] ALSA: PCM: [Q] Lost interrupts?: (stream=0, delta=72, new_hw_ptr=913, old_hw_ptr=841) [ 3504.148353] ALSA: PCM: [Q] Lost interrupts?: (stream=0, delta=72, new_hw_ptr=1137, old_hw_ptr=1065) [ 3504.150102] ALSA: PCM: [Q] Lost interrupts?: (stream=0, delta=80, new_hw_ptr=1217, old_hw_ptr=1137) [ 3504.156337] ALSA: PCM: [Q] Lost interrupts?: (stream=0, delta=72, new_hw_ptr=1489, old_hw_ptr=1417) [ 3504.157990] ALSA: PCM:
[Touch-packages] [Bug 996906]
So I've bought a laptop with VIA sound as well and it also have skips/stutters. I worked around it on both systems with these steps: 1) in /etc/pulse/default.pa added tsched=0: load-module module-udev-detect tsched=0 2) to reduce latency set in /etc/pulse/daemon.conf: default-fragments = 4 default-fragment-size-msec = 1 The final latency is a product of these numbers, 1*4 == 4 ms which is acceptable. The number of fragments should be at least 2 so the least latency possible is 2*1 == 2 ms. I don't know if there's a real difference between 4 fragments of 1 ms each or 2 fragments of 2 ms each. Try some experimenting. At least now I don't have latency increase and sound doesn't skip on pavucontrol launch, though it still skips on LMMS launch. Based on the comments' content and timestamps here, it looks to me that no one in PA team really cares about HDA Intel cards which are the most popular cards. And if PA performs badly with them out of the box it hurts PA's face, no matter who's to blame actually. Plus, pure ALSA works fine or doesn't work at all, usually. -- 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/996906 Title: periodic audio skips with Intel HDA Status in PulseAudio sound server: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: When running PulseAudio, if I'm playing music via any source (Exaile, Totem, Flash in Firefox or Chromium, VLC, etc.) every few minutes the audio will skip once or twice. top doesn't show any process eating CPU any more when it happens. dmesg doesn't show anything. Nothing else seems to be affected. It doesn't seem to happen regularly. I just installed Ubuntu 12.04 from scratch (with pulseaudio 1:1.1-0ubuntu15), but the same thing happened in 10.04 on the same hardware. Uninstalling the PulseAudio packages and going back to ALSA gives me no issues whatsoever, which is how I know the issue is with PulseAudio. I'm using my onboard audio device: $ lspci | grep Audio 00:14.2 Audio device: Advanced Micro Devices [AMD] nee ATI SBx00 Azalia (Intel HDA) Following mailing list instructions, pulseaudio - --log-time shows during a skip: ( 684.030| 5.000) I: [alsa-sink] alsa-sink.c: Underrun! ( 684.030| 0.000) I: [alsa-sink] alsa-sink.c: Increasing minimal latency to 26.00 ms ( 684.030| 0.000) D: [alsa-sink] alsa-sink.c: Latency set to 26.00ms ( 684.030| 0.000) D: [alsa-sink] alsa-sink.c: hwbuf_unused=60952 ( 684.030| 0.000) D: [alsa-sink] alsa-sink.c: setting avail_min=15944 ( 684.030| 0.000) D: [alsa-sink] alsa-sink.c: Latency set to 26.00ms ( 684.030| 0.000) D: [alsa-sink] alsa-sink.c: hwbuf_unused=60952 ( 684.030| 0.000) D: [alsa-sink] alsa-sink.c: setting avail_min=15944 ( 684.031| 0.000) D: [alsa-sink] protocol-native.c: Underrun on 'ALSA Playback', 0 bytes in queue. ( 684.036| 0.004) D: [alsa-sink] protocol-native.c: Requesting rewind due to end of underrun. ( 684.036| 0.000) D: [alsa-sink] alsa-sink.c: Requested to rewind 10940 bytes. ( 684.036| 0.000) D: [alsa-sink] alsa-sink.c: Limited to 3320 bytes. ( 684.036| 0.000) D: [alsa-sink] alsa-sink.c: before: 830 ( 684.036| 0.000) D: [alsa-sink] alsa-sink.c: after: 830 ( 684.036| 0.000) D: [alsa-sink] alsa-sink.c: Rewound 3320 bytes. ( 684.036| 0.000) D: [alsa-sink] sink.c: Processing rewind... ( 684.036| 0.000) D: [alsa-sink] sink.c: latency = 1337 ( 684.036| 0.000) D: [alsa-sink] sink-input.c: Have to rewind 3320 bytes on render memblockq. ( 684.036| 0.000) D: [alsa-sink] source.c: Processing rewind... ( 696.234| 12.197) I: [alsa-sink] alsa-sink.c: Underrun! ( 696.234| 0.000) I: [alsa-sink] alsa-sink.c: Increasing wakeup watermark to 15.99 ms ( 702.033| 5.799) I: [alsa-sink] alsa-sink.c: Underrun! ( 702.033| 0.000) I: [alsa-sink] alsa-sink.c: Increasing minimal latency to 36.00 ms ( 702.033| 0.000) D: [alsa-sink] alsa-sink.c: Latency set to 36.00ms ( 702.033| 0.000) D: [alsa-sink] alsa-sink.c: hwbuf_unused=59188 ( 702.033| 0.000) D: [alsa-sink] alsa-sink.c: setting avail_min=15680 ( 702.033| 0.000) D: [alsa-sink] alsa-sink.c: Latency set to 36.00ms ( 702.034| 0.000) D: [alsa-sink] alsa-sink.c: hwbuf_unused=59188 ( 702.034| 0.000) D: [alsa-sink] alsa-sink.c: setting avail_min=15680 ( 702.034| 0.000) D: [alsa-sink] protocol-native.c: Underrun on 'ALSA Playback', 0 bytes in queue. ...and it goes on. The Underrun! messages alone happened a few times before, but it didn't skip. I'd like to use PulseAudio, but it's pretty annoying having audio skip all the time. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: pulseaudio 1:1.1-0ubuntu15 ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14 Uname: Linux 3.2.0-24-generic x86_64 NonfreeKernelModules: nvidia
[Touch-packages] [Bug 996906]
(In reply to rkfg from comment #26) So I've bought a laptop with VIA sound as well and it also have skips/stutters. I worked around it on both systems with these steps: 1) in /etc/pulse/default.pa added tsched=0: load-module module-udev-detect tsched=0 2) to reduce latency set in /etc/pulse/daemon.conf: default-fragments = 4 default-fragment-size-msec = 1 The final latency is a product of these numbers, 1*4 == 4 ms which is acceptable. The number of fragments should be at least 2 so the least latency possible is 2*1 == 2 ms. I don't know if there's a real difference between 4 fragments of 1 ms each or 2 fragments of 2 ms each. Try some experimenting. At least now I don't have latency increase and sound doesn't skip on pavucontrol launch, though it still skips on LMMS launch. are there any difference when using four periods or two periods ? 1ms at 44100 Hz has 44.1 frames aplay select buffer size nearest to the selected time aplay -D hw:0,0 -v --buffer-time=4000 /tmp/fr025.wav aplay -D hw:0,0 -v --period-time=2000 --buffer-time=4000 /tmp/fr025.wav -- 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/996906 Title: periodic audio skips with Intel HDA Status in PulseAudio sound server: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: When running PulseAudio, if I'm playing music via any source (Exaile, Totem, Flash in Firefox or Chromium, VLC, etc.) every few minutes the audio will skip once or twice. top doesn't show any process eating CPU any more when it happens. dmesg doesn't show anything. Nothing else seems to be affected. It doesn't seem to happen regularly. I just installed Ubuntu 12.04 from scratch (with pulseaudio 1:1.1-0ubuntu15), but the same thing happened in 10.04 on the same hardware. Uninstalling the PulseAudio packages and going back to ALSA gives me no issues whatsoever, which is how I know the issue is with PulseAudio. I'm using my onboard audio device: $ lspci | grep Audio 00:14.2 Audio device: Advanced Micro Devices [AMD] nee ATI SBx00 Azalia (Intel HDA) Following mailing list instructions, pulseaudio - --log-time shows during a skip: ( 684.030| 5.000) I: [alsa-sink] alsa-sink.c: Underrun! ( 684.030| 0.000) I: [alsa-sink] alsa-sink.c: Increasing minimal latency to 26.00 ms ( 684.030| 0.000) D: [alsa-sink] alsa-sink.c: Latency set to 26.00ms ( 684.030| 0.000) D: [alsa-sink] alsa-sink.c: hwbuf_unused=60952 ( 684.030| 0.000) D: [alsa-sink] alsa-sink.c: setting avail_min=15944 ( 684.030| 0.000) D: [alsa-sink] alsa-sink.c: Latency set to 26.00ms ( 684.030| 0.000) D: [alsa-sink] alsa-sink.c: hwbuf_unused=60952 ( 684.030| 0.000) D: [alsa-sink] alsa-sink.c: setting avail_min=15944 ( 684.031| 0.000) D: [alsa-sink] protocol-native.c: Underrun on 'ALSA Playback', 0 bytes in queue. ( 684.036| 0.004) D: [alsa-sink] protocol-native.c: Requesting rewind due to end of underrun. ( 684.036| 0.000) D: [alsa-sink] alsa-sink.c: Requested to rewind 10940 bytes. ( 684.036| 0.000) D: [alsa-sink] alsa-sink.c: Limited to 3320 bytes. ( 684.036| 0.000) D: [alsa-sink] alsa-sink.c: before: 830 ( 684.036| 0.000) D: [alsa-sink] alsa-sink.c: after: 830 ( 684.036| 0.000) D: [alsa-sink] alsa-sink.c: Rewound 3320 bytes. ( 684.036| 0.000) D: [alsa-sink] sink.c: Processing rewind... ( 684.036| 0.000) D: [alsa-sink] sink.c: latency = 1337 ( 684.036| 0.000) D: [alsa-sink] sink-input.c: Have to rewind 3320 bytes on render memblockq. ( 684.036| 0.000) D: [alsa-sink] source.c: Processing rewind... ( 696.234| 12.197) I: [alsa-sink] alsa-sink.c: Underrun! ( 696.234| 0.000) I: [alsa-sink] alsa-sink.c: Increasing wakeup watermark to 15.99 ms ( 702.033| 5.799) I: [alsa-sink] alsa-sink.c: Underrun! ( 702.033| 0.000) I: [alsa-sink] alsa-sink.c: Increasing minimal latency to 36.00 ms ( 702.033| 0.000) D: [alsa-sink] alsa-sink.c: Latency set to 36.00ms ( 702.033| 0.000) D: [alsa-sink] alsa-sink.c: hwbuf_unused=59188 ( 702.033| 0.000) D: [alsa-sink] alsa-sink.c: setting avail_min=15680 ( 702.033| 0.000) D: [alsa-sink] alsa-sink.c: Latency set to 36.00ms ( 702.034| 0.000) D: [alsa-sink] alsa-sink.c: hwbuf_unused=59188 ( 702.034| 0.000) D: [alsa-sink] alsa-sink.c: setting avail_min=15680 ( 702.034| 0.000) D: [alsa-sink] protocol-native.c: Underrun on 'ALSA Playback', 0 bytes in queue. ...and it goes on. The Underrun! messages alone happened a few times before, but it didn't skip. I'd like to use PulseAudio, but it's pretty annoying having audio skip all the time. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: pulseaudio 1:1.1-0ubuntu15 ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14 Uname: Linux 3.2.0-24-generic x86_64 NonfreeKernelModules:
[Touch-packages] [Bug 996906]
Also, when CPU is loaded for any reason I sometimes get this: Apr 09 11:56:10 work pulseaudio[9718]: [alsa-sink-VT1708S Analog] protocol-native.c: Implicit underrun of 'Playback' Apr 09 11:56:10 work pulseaudio[9718]: [alsa-sink-VT1708S Analog] sink.c: Found underrun 1380 bytes ago (1436 bytes ahead in playback buffer) Apr 09 11:56:10 work pulseaudio[9718]: [alsa-sink-VT1708S Analog] protocol-native.c: Requesting rewind due to end of underrun. Apr 09 11:56:10 work pulseaudio[9718]: [alsa-sink-VT1708S Analog] alsa-sink.c: Requested to rewind 2816 bytes. Apr 09 11:56:10 work pulseaudio[9718]: [alsa-sink-VT1708S Analog] alsa-sink.c: Limited to 2560 bytes. Apr 09 11:56:10 work pulseaudio[9718]: [alsa-sink-VT1708S Analog] alsa-sink.c: before: 640 Apr 09 11:56:10 work pulseaudio[9718]: [alsa-sink-VT1708S Analog] alsa-sink.c: after: 640 Apr 09 11:56:10 work pulseaudio[9718]: [alsa-sink-VT1708S Analog] alsa-sink.c: Rewound 2560 bytes. Apr 09 11:56:10 work pulseaudio[9718]: [alsa-sink-VT1708S Analog] sink.c: Processing rewind... Apr 09 11:56:10 work pulseaudio[9718]: [alsa-sink-VT1708S Analog] sink.c: latency = 1302 Apr 09 11:56:10 work pulseaudio[9718]: [alsa-sink-VT1708S Analog] sink-input.c: Have to rewind 2560 bytes on render memblockq. Apr 09 11:56:10 work pulseaudio[9718]: [alsa-sink-VT1708S Analog] source.c: Processing rewind... Apr 09 11:56:10 work pulseaudio[9718]: [alsa-sink-VT1708S Analog] alsa-util.c: snd_pcm_avail() returned a value that is exceptionally large: 32960 bytes (186 ms). Apr 09 11:56:10 work pulseaudio[9718]: [alsa-sink-VT1708S Analog] alsa-util.c: Most likely this is a bug in the ALSA driver 'snd_hda_intel'. Please report this issue to the ALSA developers. Apr 09 11:56:10 work pulseaudio[9718]: [alsa-sink-VT1708S Analog] alsa-util.c: snd_pcm_dump(): Apr 09 11:56:10 work pulseaudio[9718]: [alsa-sink-VT1708S Analog] alsa-util.c: Soft volume PCM Apr 09 11:56:10 work pulseaudio[9718]: [alsa-sink-VT1708S Analog] alsa-util.c: Control: PCM Playback Volume Apr 09 11:56:10 work pulseaudio[9718]: [alsa-sink-VT1708S Analog] alsa-util.c: min_dB: -51 Apr 09 11:56:10 work pulseaudio[9718]: [alsa-sink-VT1708S Analog] alsa-util.c: max_dB: 0 Apr 09 11:56:10 work pulseaudio[9718]: [alsa-sink-VT1708S Analog] alsa-util.c: resolution: 256 Apr 09 11:56:10 work pulseaudio[9718]: [alsa-sink-VT1708S Analog] alsa-util.c: Its setup is: Apr 09 11:56:10 work pulseaudio[9718]: [alsa-sink-VT1708S Analog] alsa-util.c: stream : PLAYBACK Apr 09 11:56:10 work pulseaudio[9718]: [alsa-sink-VT1708S Analog] alsa-util.c: access : MMAP_INTERLEAVED Apr 09 11:56:10 work pulseaudio[9718]: [alsa-sink-VT1708S Analog] alsa-util.c: format : S16_LE Apr 09 11:56:10 work pulseaudio[9718]: [alsa-sink-VT1708S Analog] alsa-util.c: subformat: STD Apr 09 11:56:10 work pulseaudio[9718]: [alsa-sink-VT1708S Analog] alsa-util.c: channels : 2 Apr 09 11:56:10 work pulseaudio[9718]: [alsa-sink-VT1708S Analog] alsa-util.c: rate : 44100 Apr 09 11:56:10 work pulseaudio[9718]: [alsa-sink-VT1708S Analog] alsa-util.c: exact rate : 44100 (44100/1) Apr 09 11:56:10 work pulseaudio[9718]: [alsa-sink-VT1708S Analog] alsa-util.c: msbits : 16 Apr 09 11:56:10 work pulseaudio[9718]: [alsa-sink-VT1708S Analog] alsa-util.c: buffer_size : 704 Apr 09 11:56:10 work pulseaudio[9718]: [alsa-sink-VT1708S Analog] alsa-util.c: period_size : 352 Apr 09 11:56:10 work pulseaudio[9718]: [alsa-sink-VT1708S Analog] alsa-util.c: period_time : 7981 Apr 09 11:56:10 work pulseaudio[9718]: [alsa-sink-VT1708S Analog] alsa-util.c: tstamp_mode : ENABLE Apr 09 11:56:10 work pulseaudio[9718]: [alsa-sink-VT1708S Analog] alsa-util.c: period_step : 1 Apr 09 11:56:10 work pulseaudio[9718]: [alsa-sink-VT1708S Analog] alsa-util.c: avail_min: 352 Apr 09 11:56:10 work pulseaudio[9718]: [alsa-sink-VT1708S Analog] alsa-util.c: period_event : 1 Apr 09 11:56:10 work pulseaudio[9718]: [alsa-sink-VT1708S Analog] alsa-util.c: start_threshold : -1 Apr 09 11:56:10 work pulseaudio[9718]: [alsa-sink-VT1708S Analog] alsa-util.c: stop_threshold : 6341068275337658368 Apr 09 11:56:10 work pulseaudio[9718]: [alsa-sink-VT1708S Analog] alsa-util.c: silence_threshold: 0 Apr 09 11:56:10 work pulseaudio[9718]: [alsa-sink-VT1708S Analog] alsa-util.c: silence_size : 0 Apr 09 11:56:10 work pulseaudio[9718]: [alsa-sink-VT1708S Analog] alsa-util.c: boundary : 6341068275337658368 Apr 09 11:56:10 work pulseaudio[9718]: [alsa-sink-VT1708S Analog] alsa-util.c: Slave: Hardware PCM card 0 'HDA Intel PCH' device 0 subdevice 0 Apr 09 11:56:10 work pulseaudio[9718]: [alsa-sink-VT1708S Analog] alsa-util.c: Its setup is: Apr 09 11:56:10 work pulseaudio[9718]: [alsa-sink-VT1708S Analog] alsa-util.c: stream : PLAYBACK Apr 09 11:56:10 work pulseaudio[9718]: [alsa-sink-VT1708S Analog] alsa-util.c: access : MMAP_INTERLEAVED Apr 09 11:56:10 work pulseaudio[9718]: [alsa-sink-VT1708S
[Touch-packages] [Bug 996906]
I don't know if it's related but there's no error messages in dmesg if I run PA without tsched=0. Though in this case skips are pretty audible and the fragment size and their number aren't respected. Even worse, latency grows over time with each skip and becomes unbearable. With tsched=0 I can at least get it fixed. I also have skips when PC is under load (Java compiling, tabs reloading at the same time etc.). PA says it's working in realtime mode so these userland processes should not interfere. It reports in its log that it's the ALSA underrun, not the application's one. So I don't know who's to blame. -- 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/996906 Title: periodic audio skips with Intel HDA Status in PulseAudio sound server: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: When running PulseAudio, if I'm playing music via any source (Exaile, Totem, Flash in Firefox or Chromium, VLC, etc.) every few minutes the audio will skip once or twice. top doesn't show any process eating CPU any more when it happens. dmesg doesn't show anything. Nothing else seems to be affected. It doesn't seem to happen regularly. I just installed Ubuntu 12.04 from scratch (with pulseaudio 1:1.1-0ubuntu15), but the same thing happened in 10.04 on the same hardware. Uninstalling the PulseAudio packages and going back to ALSA gives me no issues whatsoever, which is how I know the issue is with PulseAudio. I'm using my onboard audio device: $ lspci | grep Audio 00:14.2 Audio device: Advanced Micro Devices [AMD] nee ATI SBx00 Azalia (Intel HDA) Following mailing list instructions, pulseaudio - --log-time shows during a skip: ( 684.030| 5.000) I: [alsa-sink] alsa-sink.c: Underrun! ( 684.030| 0.000) I: [alsa-sink] alsa-sink.c: Increasing minimal latency to 26.00 ms ( 684.030| 0.000) D: [alsa-sink] alsa-sink.c: Latency set to 26.00ms ( 684.030| 0.000) D: [alsa-sink] alsa-sink.c: hwbuf_unused=60952 ( 684.030| 0.000) D: [alsa-sink] alsa-sink.c: setting avail_min=15944 ( 684.030| 0.000) D: [alsa-sink] alsa-sink.c: Latency set to 26.00ms ( 684.030| 0.000) D: [alsa-sink] alsa-sink.c: hwbuf_unused=60952 ( 684.030| 0.000) D: [alsa-sink] alsa-sink.c: setting avail_min=15944 ( 684.031| 0.000) D: [alsa-sink] protocol-native.c: Underrun on 'ALSA Playback', 0 bytes in queue. ( 684.036| 0.004) D: [alsa-sink] protocol-native.c: Requesting rewind due to end of underrun. ( 684.036| 0.000) D: [alsa-sink] alsa-sink.c: Requested to rewind 10940 bytes. ( 684.036| 0.000) D: [alsa-sink] alsa-sink.c: Limited to 3320 bytes. ( 684.036| 0.000) D: [alsa-sink] alsa-sink.c: before: 830 ( 684.036| 0.000) D: [alsa-sink] alsa-sink.c: after: 830 ( 684.036| 0.000) D: [alsa-sink] alsa-sink.c: Rewound 3320 bytes. ( 684.036| 0.000) D: [alsa-sink] sink.c: Processing rewind... ( 684.036| 0.000) D: [alsa-sink] sink.c: latency = 1337 ( 684.036| 0.000) D: [alsa-sink] sink-input.c: Have to rewind 3320 bytes on render memblockq. ( 684.036| 0.000) D: [alsa-sink] source.c: Processing rewind... ( 696.234| 12.197) I: [alsa-sink] alsa-sink.c: Underrun! ( 696.234| 0.000) I: [alsa-sink] alsa-sink.c: Increasing wakeup watermark to 15.99 ms ( 702.033| 5.799) I: [alsa-sink] alsa-sink.c: Underrun! ( 702.033| 0.000) I: [alsa-sink] alsa-sink.c: Increasing minimal latency to 36.00 ms ( 702.033| 0.000) D: [alsa-sink] alsa-sink.c: Latency set to 36.00ms ( 702.033| 0.000) D: [alsa-sink] alsa-sink.c: hwbuf_unused=59188 ( 702.033| 0.000) D: [alsa-sink] alsa-sink.c: setting avail_min=15680 ( 702.033| 0.000) D: [alsa-sink] alsa-sink.c: Latency set to 36.00ms ( 702.034| 0.000) D: [alsa-sink] alsa-sink.c: hwbuf_unused=59188 ( 702.034| 0.000) D: [alsa-sink] alsa-sink.c: setting avail_min=15680 ( 702.034| 0.000) D: [alsa-sink] protocol-native.c: Underrun on 'ALSA Playback', 0 bytes in queue. ...and it goes on. The Underrun! messages alone happened a few times before, but it didn't skip. I'd like to use PulseAudio, but it's pretty annoying having audio skip all the time. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: pulseaudio 1:1.1-0ubuntu15 ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14 Uname: Linux 3.2.0-24-generic x86_64 NonfreeKernelModules: nvidia AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: toxite 2136 F pulseaudio /dev/snd/pcmC0D0p: toxite 2136 F...m pulseaudio Card0.Amixer.info: Card hw:0 'SB'/'HDA ATI SB at 0xfe024000 irq 16' Mixer name : 'Realtek ALC889' Components : 'HDA:10ec0889,1458a102,0014' Controls
[Touch-packages] [Bug 996906]
When I start PA without tsched=0, it's ALSA setup is weird: Apr 10 09:46:52 work pulseaudio[5161]: [pulseaudio] alsa-util.c: Control: PCM Playback Volume Apr 10 09:46:52 work pulseaudio[5161]: [pulseaudio] alsa-util.c: min_dB: -51 Apr 10 09:46:52 work pulseaudio[5161]: [pulseaudio] alsa-util.c: max_dB: 0 Apr 10 09:46:52 work pulseaudio[5161]: [pulseaudio] alsa-util.c: resolution: 256 Apr 10 09:46:52 work pulseaudio[5161]: [pulseaudio] alsa-util.c: Its setup is: Apr 10 09:46:52 work pulseaudio[5161]: [pulseaudio] alsa-util.c: stream : PLAYBACK Apr 10 09:46:52 work pulseaudio[5161]: [pulseaudio] alsa-util.c: access : MMAP_INTERLEAVED Apr 10 09:46:52 work pulseaudio[5161]: [pulseaudio] alsa-util.c: format : S16_LE Apr 10 09:46:52 work pulseaudio[5161]: [pulseaudio] alsa-util.c: subformat : STD Apr 10 09:46:52 work pulseaudio[5161]: [pulseaudio] alsa-util.c: channels : 2 Apr 10 09:46:52 work pulseaudio[5161]: [pulseaudio] alsa-util.c: rate : 44100 Apr 10 09:46:52 work pulseaudio[5161]: [pulseaudio] alsa-util.c: exact rate : 44100 (44100/1) Apr 10 09:46:52 work pulseaudio[5161]: [pulseaudio] alsa-util.c: msbits : 16 Apr 10 09:46:52 work pulseaudio[5161]: [pulseaudio] alsa-util.c: buffer_size : 88192 Apr 10 09:46:52 work pulseaudio[5161]: [pulseaudio] alsa-util.c: period_size : 44096 Apr 10 09:46:52 work pulseaudio[5161]: [pulseaudio] alsa-util.c: period_time : 09 Apr 10 09:46:52 work pulseaudio[5161]: [pulseaudio] alsa-util.c: tstamp_mode : ENABLE Apr 10 09:46:52 work pulseaudio[5161]: [pulseaudio] alsa-util.c: period_step : 1 Apr 10 09:46:52 work pulseaudio[5161]: [pulseaudio] alsa-util.c: avail_min : 87310 Apr 10 09:46:52 work pulseaudio[5161]: [pulseaudio] alsa-util.c: period_event : 0 Apr 10 09:46:52 work pulseaudio[5161]: [pulseaudio] alsa-util.c: start_threshold : -1 Apr 10 09:46:52 work pulseaudio[5161]: [pulseaudio] alsa-util.c: stop_threshold : 6205960286516543488 Apr 10 09:46:52 work pulseaudio[5161]: [pulseaudio] alsa-util.c: silence_threshold: 0 Apr 10 09:46:52 work pulseaudio[5161]: [pulseaudio] alsa-util.c: silence_size : 0 Apr 10 09:46:52 work pulseaudio[5161]: [pulseaudio] alsa-util.c: boundary : 6205960286516543488 Apr 10 09:46:52 work pulseaudio[5161]: [pulseaudio] alsa-util.c: Slave: Hardware PCM card 0 'HDA Intel PCH' device 0 subdevice 0 Apr 10 09:46:52 work pulseaudio[5161]: [pulseaudio] alsa-util.c: Its setup is: Apr 10 09:46:52 work pulseaudio[5161]: [pulseaudio] alsa-util.c: stream : PLAYBACK Apr 10 09:46:52 work pulseaudio[5161]: [pulseaudio] alsa-util.c: access : MMAP_INTERLEAVED Apr 10 09:46:52 work pulseaudio[5161]: [pulseaudio] alsa-util.c: format : S16_LE Apr 10 09:46:52 work pulseaudio[5161]: [pulseaudio] alsa-util.c: subformat : STD Apr 10 09:46:52 work pulseaudio[5161]: [pulseaudio] alsa-util.c: channels : 2 Apr 10 09:46:52 work pulseaudio[5161]: [pulseaudio] alsa-util.c: rate : 44100 Apr 10 09:46:52 work pulseaudio[5161]: [pulseaudio] alsa-util.c: exact rate : 44100 (44100/1) Apr 10 09:46:52 work pulseaudio[5161]: [pulseaudio] alsa-util.c: msbits : 16 Apr 10 09:46:52 work pulseaudio[5161]: [pulseaudio] alsa-util.c: buffer_size : 88192 Apr 10 09:46:52 work pulseaudio[5161]: [pulseaudio] alsa-util.c: period_size : 44096 Apr 10 09:46:52 work pulseaudio[5161]: [pulseaudio] alsa-util.c: period_time : 09 Apr 10 09:46:52 work pulseaudio[5161]: [pulseaudio] alsa-util.c: tstamp_mode : ENABLE Apr 10 09:46:52 work pulseaudio[5161]: [pulseaudio] alsa-util.c: period_step : 1 Apr 10 09:46:52 work pulseaudio[5161]: [pulseaudio] alsa-util.c: avail_min : 87310 Apr 10 09:46:52 work pulseaudio[5161]: [pulseaudio] alsa-util.c: period_event : 0 Apr 10 09:46:52 work pulseaudio[5161]: [pulseaudio] alsa-util.c: start_threshold : -1 Apr 10 09:46:52 work pulseaudio[5161]: [pulseaudio] alsa-util.c: stop_threshold : 6205960286516543488 Apr 10 09:46:52 work pulseaudio[5161]: [pulseaudio] alsa-util.c: silence_threshold: 0 Apr 10 09:46:52 work pulseaudio[5161]: [pulseaudio] alsa-util.c: silence_size : 0 Apr 10 09:46:52 work pulseaudio[5161]: [pulseaudio] alsa-util.c: boundary : 6205960286516543488 Apr 10 09:46:52 work pulseaudio[5161]: [pulseaudio] alsa-util.c: appl_ptr : 0 Apr 10 09:46:52 work pulseaudio[5161]: [pulseaudio] alsa-util.c: hw_ptr : 0 Why does period size lack 4 bytes to be exactly 1 second long? -- 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/996906 Title: periodic audio skips with Intel HDA Status in PulseAudio sound server: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: When running PulseAudio, if I'm playing music via any source (Exaile, Totem, Flash in Firefox or
[Touch-packages] [Bug 996906]
(I Also, after I do: echo 1 /proc/asound/card0/pcm0p/xrun_debug I have lots of this in dmesg: [ 3504.140844] ALSA: PCM: [Q] Lost interrupts?: (stream=0, delta=56, new_hw_ptr=809, old_hw_ptr=753) [ 3504.143264] ALSA: PCM: [Q] Lost interrupts?: (stream=0, delta=72, new_hw_ptr=913, old_hw_ptr=841) [ 3504.148353] ALSA: PCM: [Q] Lost interrupts?: (stream=0, delta=72, new_hw_ptr=1137, old_hw_ptr=1065) [ 3504.150102] ALSA: PCM: [Q] Lost interrupts?: (stream=0, delta=80, new_hw_ptr=1217, old_hw_ptr=1137) [ 3504.156337] ALSA: PCM: [Q] Lost interrupts?: (stream=0, delta=72, new_hw_ptr=1489, old_hw_ptr=1417) [ 3504.157990] ALSA: PCM: [Q] Lost interrupts?: (stream=0, delta=72, new_hw_ptr=1561, old_hw_ptr=1489) [ 3504.169408] ALSA: PCM: [Q] Lost interrupts?: (stream=0, delta=72, new_hw_ptr=2065, old_hw_ptr=1993) [ 3504.170967] ALSA: PCM: [Q] Lost interrupts?: (stream=0, delta=72, new_hw_ptr=2137, old_hw_ptr=2065) [ 3504.179684] ALSA: PCM: [Q] Lost interrupts?: (stream=0, delta=72, new_hw_ptr=2521, old_hw_ptr=2449) [ 3504.194902] ALSA: PCM: [Q] Lost interrupts?: (stream=0, delta=80, new_hw_ptr=121, old_hw_ptr=41) http://www.alsa-project.org/main/index.php/XRUN_Debug you need more debug info to find out what happen Enable basic debugging and dump stack, check hardware pointer on the period update https://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git/tree/Documentation/sound/alsa/HD-Audio.txt how about enable_msi=0 ? if it don't help, you need to file bug report at https://bugzilla.kernel.org/enter_bug.cgi?product=Drivers -- 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/996906 Title: periodic audio skips with Intel HDA Status in PulseAudio sound server: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: When running PulseAudio, if I'm playing music via any source (Exaile, Totem, Flash in Firefox or Chromium, VLC, etc.) every few minutes the audio will skip once or twice. top doesn't show any process eating CPU any more when it happens. dmesg doesn't show anything. Nothing else seems to be affected. It doesn't seem to happen regularly. I just installed Ubuntu 12.04 from scratch (with pulseaudio 1:1.1-0ubuntu15), but the same thing happened in 10.04 on the same hardware. Uninstalling the PulseAudio packages and going back to ALSA gives me no issues whatsoever, which is how I know the issue is with PulseAudio. I'm using my onboard audio device: $ lspci | grep Audio 00:14.2 Audio device: Advanced Micro Devices [AMD] nee ATI SBx00 Azalia (Intel HDA) Following mailing list instructions, pulseaudio - --log-time shows during a skip: ( 684.030| 5.000) I: [alsa-sink] alsa-sink.c: Underrun! ( 684.030| 0.000) I: [alsa-sink] alsa-sink.c: Increasing minimal latency to 26.00 ms ( 684.030| 0.000) D: [alsa-sink] alsa-sink.c: Latency set to 26.00ms ( 684.030| 0.000) D: [alsa-sink] alsa-sink.c: hwbuf_unused=60952 ( 684.030| 0.000) D: [alsa-sink] alsa-sink.c: setting avail_min=15944 ( 684.030| 0.000) D: [alsa-sink] alsa-sink.c: Latency set to 26.00ms ( 684.030| 0.000) D: [alsa-sink] alsa-sink.c: hwbuf_unused=60952 ( 684.030| 0.000) D: [alsa-sink] alsa-sink.c: setting avail_min=15944 ( 684.031| 0.000) D: [alsa-sink] protocol-native.c: Underrun on 'ALSA Playback', 0 bytes in queue. ( 684.036| 0.004) D: [alsa-sink] protocol-native.c: Requesting rewind due to end of underrun. ( 684.036| 0.000) D: [alsa-sink] alsa-sink.c: Requested to rewind 10940 bytes. ( 684.036| 0.000) D: [alsa-sink] alsa-sink.c: Limited to 3320 bytes. ( 684.036| 0.000) D: [alsa-sink] alsa-sink.c: before: 830 ( 684.036| 0.000) D: [alsa-sink] alsa-sink.c: after: 830 ( 684.036| 0.000) D: [alsa-sink] alsa-sink.c: Rewound 3320 bytes. ( 684.036| 0.000) D: [alsa-sink] sink.c: Processing rewind... ( 684.036| 0.000) D: [alsa-sink] sink.c: latency = 1337 ( 684.036| 0.000) D: [alsa-sink] sink-input.c: Have to rewind 3320 bytes on render memblockq. ( 684.036| 0.000) D: [alsa-sink] source.c: Processing rewind... ( 696.234| 12.197) I: [alsa-sink] alsa-sink.c: Underrun! ( 696.234| 0.000) I: [alsa-sink] alsa-sink.c: Increasing wakeup watermark to 15.99 ms ( 702.033| 5.799) I: [alsa-sink] alsa-sink.c: Underrun! ( 702.033| 0.000) I: [alsa-sink] alsa-sink.c: Increasing minimal latency to 36.00 ms ( 702.033| 0.000) D: [alsa-sink] alsa-sink.c: Latency set to 36.00ms ( 702.033| 0.000) D: [alsa-sink] alsa-sink.c: hwbuf_unused=59188 ( 702.033| 0.000) D: [alsa-sink] alsa-sink.c: setting avail_min=15680 ( 702.033| 0.000) D: [alsa-sink] alsa-sink.c: Latency set to 36.00ms ( 702.034| 0.000) D: [alsa-sink] alsa-sink.c: hwbuf_unused=59188 ( 702.034| 0.000) D: [alsa-sink] alsa-sink.c: setting avail_min=15680 ( 702.034|
[Touch-packages] [Bug 996906]
enable_msi=0 doesn't change anything, still the same errors in the log. -- 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/996906 Title: periodic audio skips with Intel HDA Status in PulseAudio sound server: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: When running PulseAudio, if I'm playing music via any source (Exaile, Totem, Flash in Firefox or Chromium, VLC, etc.) every few minutes the audio will skip once or twice. top doesn't show any process eating CPU any more when it happens. dmesg doesn't show anything. Nothing else seems to be affected. It doesn't seem to happen regularly. I just installed Ubuntu 12.04 from scratch (with pulseaudio 1:1.1-0ubuntu15), but the same thing happened in 10.04 on the same hardware. Uninstalling the PulseAudio packages and going back to ALSA gives me no issues whatsoever, which is how I know the issue is with PulseAudio. I'm using my onboard audio device: $ lspci | grep Audio 00:14.2 Audio device: Advanced Micro Devices [AMD] nee ATI SBx00 Azalia (Intel HDA) Following mailing list instructions, pulseaudio - --log-time shows during a skip: ( 684.030| 5.000) I: [alsa-sink] alsa-sink.c: Underrun! ( 684.030| 0.000) I: [alsa-sink] alsa-sink.c: Increasing minimal latency to 26.00 ms ( 684.030| 0.000) D: [alsa-sink] alsa-sink.c: Latency set to 26.00ms ( 684.030| 0.000) D: [alsa-sink] alsa-sink.c: hwbuf_unused=60952 ( 684.030| 0.000) D: [alsa-sink] alsa-sink.c: setting avail_min=15944 ( 684.030| 0.000) D: [alsa-sink] alsa-sink.c: Latency set to 26.00ms ( 684.030| 0.000) D: [alsa-sink] alsa-sink.c: hwbuf_unused=60952 ( 684.030| 0.000) D: [alsa-sink] alsa-sink.c: setting avail_min=15944 ( 684.031| 0.000) D: [alsa-sink] protocol-native.c: Underrun on 'ALSA Playback', 0 bytes in queue. ( 684.036| 0.004) D: [alsa-sink] protocol-native.c: Requesting rewind due to end of underrun. ( 684.036| 0.000) D: [alsa-sink] alsa-sink.c: Requested to rewind 10940 bytes. ( 684.036| 0.000) D: [alsa-sink] alsa-sink.c: Limited to 3320 bytes. ( 684.036| 0.000) D: [alsa-sink] alsa-sink.c: before: 830 ( 684.036| 0.000) D: [alsa-sink] alsa-sink.c: after: 830 ( 684.036| 0.000) D: [alsa-sink] alsa-sink.c: Rewound 3320 bytes. ( 684.036| 0.000) D: [alsa-sink] sink.c: Processing rewind... ( 684.036| 0.000) D: [alsa-sink] sink.c: latency = 1337 ( 684.036| 0.000) D: [alsa-sink] sink-input.c: Have to rewind 3320 bytes on render memblockq. ( 684.036| 0.000) D: [alsa-sink] source.c: Processing rewind... ( 696.234| 12.197) I: [alsa-sink] alsa-sink.c: Underrun! ( 696.234| 0.000) I: [alsa-sink] alsa-sink.c: Increasing wakeup watermark to 15.99 ms ( 702.033| 5.799) I: [alsa-sink] alsa-sink.c: Underrun! ( 702.033| 0.000) I: [alsa-sink] alsa-sink.c: Increasing minimal latency to 36.00 ms ( 702.033| 0.000) D: [alsa-sink] alsa-sink.c: Latency set to 36.00ms ( 702.033| 0.000) D: [alsa-sink] alsa-sink.c: hwbuf_unused=59188 ( 702.033| 0.000) D: [alsa-sink] alsa-sink.c: setting avail_min=15680 ( 702.033| 0.000) D: [alsa-sink] alsa-sink.c: Latency set to 36.00ms ( 702.034| 0.000) D: [alsa-sink] alsa-sink.c: hwbuf_unused=59188 ( 702.034| 0.000) D: [alsa-sink] alsa-sink.c: setting avail_min=15680 ( 702.034| 0.000) D: [alsa-sink] protocol-native.c: Underrun on 'ALSA Playback', 0 bytes in queue. ...and it goes on. The Underrun! messages alone happened a few times before, but it didn't skip. I'd like to use PulseAudio, but it's pretty annoying having audio skip all the time. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: pulseaudio 1:1.1-0ubuntu15 ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14 Uname: Linux 3.2.0-24-generic x86_64 NonfreeKernelModules: nvidia AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: toxite 2136 F pulseaudio /dev/snd/pcmC0D0p: toxite 2136 F...m pulseaudio Card0.Amixer.info: Card hw:0 'SB'/'HDA ATI SB at 0xfe024000 irq 16' Mixer name : 'Realtek ALC889' Components : 'HDA:10ec0889,1458a102,0014' Controls : 48 Simple ctrls : 22 Date: Tue May 8 21:45:17 2012 InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) ProcEnviron: TERM=xterm PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/03/2009 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F2 dmi.board.name: GA-790FXTA-UD5 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version:
[Touch-packages] [Bug 996906]
I've found that 16000 buffer time with 4000 period time doesn't underrun while if I change the period time to 1000 or 2000 it underruns pretty quickly. Lower buffer times underrun regardless of the period time it seems. 16000/4000 shows these params: aplay -D hw:0,0 -v --buffer-time=16000 --period-time=4000 /tmp/fr025.wav Playing WAVE '/tmp/fr025.wav' : Signed 16 bit Little Endian, Rate 44100 Hz, Stereo Hardware PCM card 0 'HDA Intel PCH' device 0 subdevice 0 Its setup is: stream : PLAYBACK access : RW_INTERLEAVED format : S16_LE subformat: STD channels : 2 rate : 44100 exact rate : 44100 (44100/1) msbits : 16 buffer_size : 768 period_size : 192 period_time : 4353 tstamp_mode : NONE period_step : 1 avail_min: 192 period_event : 0 start_threshold : 768 stop_threshold : 768 silence_threshold: 0 silence_size : 0 boundary : 6917529027641081856 appl_ptr : 0 hw_ptr : 0 16000/2000 is like this: aplay -D hw:0,0 -v --buffer-time=16000 --period-time=2000 /tmp/fr025.wav Playing WAVE '/tmp/fr025.wav' : Signed 16 bit Little Endian, Rate 44100 Hz, Stereo Hardware PCM card 0 'HDA Intel PCH' device 0 subdevice 0 Its setup is: stream : PLAYBACK access : RW_INTERLEAVED format : S16_LE subformat: STD channels : 2 rate : 44100 exact rate : 44100 (44100/1) msbits : 16 buffer_size : 672 period_size : 96 period_time : 2176 tstamp_mode : NONE period_step : 1 avail_min: 96 period_event : 0 start_threshold : 672 stop_threshold : 672 silence_threshold: 0 silence_size : 0 boundary : 6052837899185946624 appl_ptr : 0 hw_ptr : 0 underrun!!! (at least 2.587 ms long) Status: state : XRUN trigger_time: 4380.16449247 tstamp : 4380.19033473 delay : 0 avail : 761 avail_max : 761 ^CAborted by signal Interrupt... -- 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/996906 Title: periodic audio skips with Intel HDA Status in PulseAudio sound server: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: When running PulseAudio, if I'm playing music via any source (Exaile, Totem, Flash in Firefox or Chromium, VLC, etc.) every few minutes the audio will skip once or twice. top doesn't show any process eating CPU any more when it happens. dmesg doesn't show anything. Nothing else seems to be affected. It doesn't seem to happen regularly. I just installed Ubuntu 12.04 from scratch (with pulseaudio 1:1.1-0ubuntu15), but the same thing happened in 10.04 on the same hardware. Uninstalling the PulseAudio packages and going back to ALSA gives me no issues whatsoever, which is how I know the issue is with PulseAudio. I'm using my onboard audio device: $ lspci | grep Audio 00:14.2 Audio device: Advanced Micro Devices [AMD] nee ATI SBx00 Azalia (Intel HDA) Following mailing list instructions, pulseaudio - --log-time shows during a skip: ( 684.030| 5.000) I: [alsa-sink] alsa-sink.c: Underrun! ( 684.030| 0.000) I: [alsa-sink] alsa-sink.c: Increasing minimal latency to 26.00 ms ( 684.030| 0.000) D: [alsa-sink] alsa-sink.c: Latency set to 26.00ms ( 684.030| 0.000) D: [alsa-sink] alsa-sink.c: hwbuf_unused=60952 ( 684.030| 0.000) D: [alsa-sink] alsa-sink.c: setting avail_min=15944 ( 684.030| 0.000) D: [alsa-sink] alsa-sink.c: Latency set to 26.00ms ( 684.030| 0.000) D: [alsa-sink] alsa-sink.c: hwbuf_unused=60952 ( 684.030| 0.000) D: [alsa-sink] alsa-sink.c: setting avail_min=15944 ( 684.031| 0.000) D: [alsa-sink] protocol-native.c: Underrun on 'ALSA Playback', 0 bytes in queue. ( 684.036| 0.004) D: [alsa-sink] protocol-native.c: Requesting rewind due to end of underrun. ( 684.036| 0.000) D: [alsa-sink] alsa-sink.c: Requested to rewind 10940 bytes. ( 684.036| 0.000) D: [alsa-sink] alsa-sink.c: Limited to 3320 bytes. ( 684.036| 0.000) D: [alsa-sink] alsa-sink.c: before: 830 ( 684.036| 0.000) D: [alsa-sink] alsa-sink.c: after: 830 ( 684.036| 0.000) D: [alsa-sink] alsa-sink.c: Rewound 3320 bytes. ( 684.036| 0.000) D: [alsa-sink] sink.c: Processing rewind... ( 684.036| 0.000) D: [alsa-sink] sink.c: latency = 1337 ( 684.036| 0.000) D: [alsa-sink] sink-input.c: Have to rewind 3320 bytes on render memblockq. ( 684.036| 0.000) D: [alsa-sink] source.c: Processing rewind... ( 696.234| 12.197) I: [alsa-sink] alsa-sink.c: Underrun! ( 696.234| 0.000) I: [alsa-sink] alsa-sink.c: Increasing wakeup watermark to 15.99 ms ( 702.033| 5.799) I: [alsa-sink] alsa-sink.c: Underrun! ( 702.033| 0.000) I: [alsa-sink] alsa-sink.c: Increasing minimal latency to 36.00 ms ( 702.033| 0.000) D: [alsa-sink] alsa-sink.c: Latency
[Touch-packages] [Bug 1443791] [NEW] When running systemd the system sometimes logs out rather than locking the scrren
Public bug reported: I am using Ubuntu 15.04 and booting with systemd. In most cases locking the screen works as expected but in certain cases the machine logs out instead. Can this be fixed? ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- 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/1443791 Title: When running systemd the system sometimes logs out rather than locking the scrren Status in systemd package in Ubuntu: New Bug description: I am using Ubuntu 15.04 and booting with systemd. In most cases locking the screen works as expected but in certain cases the machine logs out instead. Can this be fixed? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1443791/+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 996906]
Created attachment 115003 Syslog with debug info Here's my full syslog. First I started PA with: default-fragments = 9 default-fragment-size-msec = 2 So the buffer was 800 frames, I couldn't get it to be 768 to have exactly 16 ms latency. So it was 18 ms. I had no errors in dmesg while using value of 11 for xrun_debug. Then I set params to 4 fragments of 1 ms each and had errors. enable_msi=0 didn't help IIRC, neither did position_fix. But I'll try again. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/996906 Title: periodic audio skips with Intel HDA Status in PulseAudio sound server: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: When running PulseAudio, if I'm playing music via any source (Exaile, Totem, Flash in Firefox or Chromium, VLC, etc.) every few minutes the audio will skip once or twice. top doesn't show any process eating CPU any more when it happens. dmesg doesn't show anything. Nothing else seems to be affected. It doesn't seem to happen regularly. I just installed Ubuntu 12.04 from scratch (with pulseaudio 1:1.1-0ubuntu15), but the same thing happened in 10.04 on the same hardware. Uninstalling the PulseAudio packages and going back to ALSA gives me no issues whatsoever, which is how I know the issue is with PulseAudio. I'm using my onboard audio device: $ lspci | grep Audio 00:14.2 Audio device: Advanced Micro Devices [AMD] nee ATI SBx00 Azalia (Intel HDA) Following mailing list instructions, pulseaudio - --log-time shows during a skip: ( 684.030| 5.000) I: [alsa-sink] alsa-sink.c: Underrun! ( 684.030| 0.000) I: [alsa-sink] alsa-sink.c: Increasing minimal latency to 26.00 ms ( 684.030| 0.000) D: [alsa-sink] alsa-sink.c: Latency set to 26.00ms ( 684.030| 0.000) D: [alsa-sink] alsa-sink.c: hwbuf_unused=60952 ( 684.030| 0.000) D: [alsa-sink] alsa-sink.c: setting avail_min=15944 ( 684.030| 0.000) D: [alsa-sink] alsa-sink.c: Latency set to 26.00ms ( 684.030| 0.000) D: [alsa-sink] alsa-sink.c: hwbuf_unused=60952 ( 684.030| 0.000) D: [alsa-sink] alsa-sink.c: setting avail_min=15944 ( 684.031| 0.000) D: [alsa-sink] protocol-native.c: Underrun on 'ALSA Playback', 0 bytes in queue. ( 684.036| 0.004) D: [alsa-sink] protocol-native.c: Requesting rewind due to end of underrun. ( 684.036| 0.000) D: [alsa-sink] alsa-sink.c: Requested to rewind 10940 bytes. ( 684.036| 0.000) D: [alsa-sink] alsa-sink.c: Limited to 3320 bytes. ( 684.036| 0.000) D: [alsa-sink] alsa-sink.c: before: 830 ( 684.036| 0.000) D: [alsa-sink] alsa-sink.c: after: 830 ( 684.036| 0.000) D: [alsa-sink] alsa-sink.c: Rewound 3320 bytes. ( 684.036| 0.000) D: [alsa-sink] sink.c: Processing rewind... ( 684.036| 0.000) D: [alsa-sink] sink.c: latency = 1337 ( 684.036| 0.000) D: [alsa-sink] sink-input.c: Have to rewind 3320 bytes on render memblockq. ( 684.036| 0.000) D: [alsa-sink] source.c: Processing rewind... ( 696.234| 12.197) I: [alsa-sink] alsa-sink.c: Underrun! ( 696.234| 0.000) I: [alsa-sink] alsa-sink.c: Increasing wakeup watermark to 15.99 ms ( 702.033| 5.799) I: [alsa-sink] alsa-sink.c: Underrun! ( 702.033| 0.000) I: [alsa-sink] alsa-sink.c: Increasing minimal latency to 36.00 ms ( 702.033| 0.000) D: [alsa-sink] alsa-sink.c: Latency set to 36.00ms ( 702.033| 0.000) D: [alsa-sink] alsa-sink.c: hwbuf_unused=59188 ( 702.033| 0.000) D: [alsa-sink] alsa-sink.c: setting avail_min=15680 ( 702.033| 0.000) D: [alsa-sink] alsa-sink.c: Latency set to 36.00ms ( 702.034| 0.000) D: [alsa-sink] alsa-sink.c: hwbuf_unused=59188 ( 702.034| 0.000) D: [alsa-sink] alsa-sink.c: setting avail_min=15680 ( 702.034| 0.000) D: [alsa-sink] protocol-native.c: Underrun on 'ALSA Playback', 0 bytes in queue. ...and it goes on. The Underrun! messages alone happened a few times before, but it didn't skip. I'd like to use PulseAudio, but it's pretty annoying having audio skip all the time. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: pulseaudio 1:1.1-0ubuntu15 ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14 Uname: Linux 3.2.0-24-generic x86_64 NonfreeKernelModules: nvidia AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: toxite 2136 F pulseaudio /dev/snd/pcmC0D0p: toxite 2136 F...m pulseaudio Card0.Amixer.info: Card hw:0 'SB'/'HDA ATI SB at 0xfe024000 irq 16' Mixer name : 'Realtek ALC889' Components : 'HDA:10ec0889,1458a102,0014' Controls : 48 Simple ctrls : 22 Date: Tue May 8 21:45:17 2012 InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425)
[Touch-packages] [Bug 1366014] Re: [indicators] In a Dual SIM phone, There is no way to know which of the two SIMs is being used for cellular data.
movement applied. ** Changed in: indicator-network (Ubuntu Vivid) Assignee: Pete Woods (pete-woods) = Antti Kaijanmäki (kaijanmaki) ** Changed in: indicator-network (Ubuntu RTM) Assignee: Pete Woods (pete-woods) = Antti Kaijanmäki (kaijanmaki) ** Changed in: ubuntu-ux Status: Triaged = Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1366014 Title: [indicators] In a Dual SIM phone, There is no way to know which of the two SIMs is being used for cellular data. Status in the base for Ubuntu mobile products: Confirmed Status in Ubuntu UX bugs: Fix Committed Status in indicator-network package in Ubuntu: In Progress Status in indicator-network source package in Utopic: In Progress Status in indicator-network source package in Vivid: In Progress Status in indicator-network package in Ubuntu RTM: In Progress Bug description: Pulled as separate task from bug #1350739, per comment #6: * There is no way to know which of the two SIMs is being used for cellular data. Also, it looks like the displayed indicator mixes data from different slots: when I have a connection on the secondary slot using EDGE, I see an icon with an H some times, and with an E (the right one) some times. The H is probably taking from the technology in the primary slot, which is not attached. Also, related to this one: mobile broadband data connection speed is right now always coming from SIM 1, even if SIM 2 is the one used for mobile broadband. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1366014/+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 1432843] Re: Lubuntu failed to boot
'Kamikaze-15-04' contains Lubuntu with the 64-bit kernel 3.19.0-10-generic #10-Ubuntu SMP Mon Mar 23. The live session works nicely in http://www.toshiba.se/laptops/satellite-pro/c850/satellite-pro-c850-19w/ -o- 'Kamikaze-15-04' works also in a desktop computer with AMD Athlon processor and on-board (old) nvidia graphics - Lubuntu used to work in the following computer, where the current Vivid i386 desktop iso does not work, http://www.asus.com/Motherboards/M2NVM_DVI/ It needs SysRq REISUO to shut down both computers. I should check if the xserver-xorg-video-all package helps in the i386 version (I should be able to test that myself). -- 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/1432843 Title: Lubuntu failed to boot Status in X.Org X server: Confirmed Status in lubuntu-meta package in Ubuntu: Triaged Status in xorg package in Ubuntu: Triaged Bug description: The daily build of Lubuntu 20150316 failed to boot into the live session, and fails to install. During the boot session, the Lubuntu splash screen appears indicating that Lubuntu was loading. What follows next was a blank screen. Unfortunately, I cannot sumit the exact version of syslinux since the daily build could not boot into an interactive session. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: syslinux 3:6.03~pre18+dfsg-1ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0 Uname: Linux 3.19.0-7-generic i686 ApportVersion: 2.16.2-0ubuntu1 Architecture: i386 Date: Mon Mar 16 17:19:35 2015 Dependencies: gcc-5-base 5-20150228-1ubuntu1 libc6 2.19-15ubuntu2 libgcc1 1:5-20150228-1ubuntu1 mtools 4.0.18-2 multiarch-support 2.19-15ubuntu2 InstallationDate: Installed on 2015-03-05 (11 days ago) InstallationMedia: Lubuntu 15.04 Vivid Vervet - Alpha i386 (20150303) SourcePackage: syslinux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1432843/+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 1443846] [NEW] 'Advance by one frame' no longer works at beginning of video
Public bug reported: This might be a totem issue, not a gstreamer one; the ubuntu-bug program asked what was happening and I selected video not playing correctly. After I upgraded from Ubuntu 12.04 to Ubuntu 14.10, with whatever gstreamer or totem changes were involved with that, 'advance by one frame' (the '.' key) didn't work as well. It will almost always not work at the very start of a video. Sometimes instead of one frame, it will advance around half a second. Other times, maybe related to seeking in the video after using it without first starting normal playback again, it will not work properly or will send you back to where you were in the video before you seeked to a different time. Occasionally, it will work at the start of a video, but very rarely if ever can you do this by pausing, seeking to the start of a video, and then pressing '.' . You used to be able to do this though. Right now, trying to seek near the start of a video, if it doesn't just send you back to wherever you were, usually skips several frames, like 6 frames or so, then starts normal behaviour of advancing 1 frame at a time. On a related note, the 'one frame back' key (the ',' key) is either broken by design or partly by accident. Pressing it usually either freezes the video, so you have to seek to a different location in order for the video to start playing normally, or it causes the video to seek to a totally separate time, and subsequently pressing '.' causes a frame to be shown which is at a completely separate time than what ',' was returning. When ',' works instead of freezing the video (possibly only before I upgraded to 14.10 several months ago), it seemed to usually seek to near the start of the video before returning frames, though the '.' key would sort of let you reset playback to where it was before. As a quick test, I just tried it on a webm/VP9 video, though I think the same thing happens with other videos: 1) Played for a few seconds, then pressed and held '.' . Result, video advances at the rate of keyboard sending '.' events. 2) Pressed and held ','. Result, video went back maybe a second, but then actually played backwards. 3) Pressed and held '.' again. Result, video played backwards instead of advancing forwards like the key should do. 4) With video paused, seeked forward by 15 sec, and pressed '.' again. Result, progress bar moved back to video start where it was before seeking, and video didn't advance as probably still trying to go backwards. 5) With video paused, seek forward by clicking. Unpause video. Result, it goes back to start and doesn't play. 6) With video on play but not playing, seeked forward again. Result, starts playing from beginning. 7) With video on play and playing, seeked to a different location. Result, video still on play but not playing. 8) Paused and then unpaused, video starts playing again. 9) Pressed and held '.' again, video slowly moves forward. 10) Pressed ',' , totem crashes. (don't remember this happening before) ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: libgstreamer1.0-0 1.4.3-1 ProcVersionSignature: Ubuntu 3.16.0-30.40-generic 3.16.7-ckt3 Uname: Linux 3.16.0-30-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu8.2 Architecture: amd64 CurrentDesktop: Unity Date: Tue Apr 14 02:12:17 2015 SourcePackage: gstreamer1.0 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gstreamer1.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug utopic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1443846 Title: 'Advance by one frame' no longer works at beginning of video Status in gstreamer1.0 package in Ubuntu: New Bug description: This might be a totem issue, not a gstreamer one; the ubuntu-bug program asked what was happening and I selected video not playing correctly. After I upgraded from Ubuntu 12.04 to Ubuntu 14.10, with whatever gstreamer or totem changes were involved with that, 'advance by one frame' (the '.' key) didn't work as well. It will almost always not work at the very start of a video. Sometimes instead of one frame, it will advance around half a second. Other times, maybe related to seeking in the video after using it without first starting normal playback again, it will not work properly or will send you back to where you were in the video before you seeked to a different time. Occasionally, it will work at the start of a video, but very rarely if ever can you do this by pausing, seeking to the start of a video, and then pressing '.' . You used to be able to do this though. Right now, trying to seek near the start of a video, if it doesn't just send you back to wherever you were, usually skips several frames, like 6 frames or so, then starts normal behaviour of advancing 1 frame at a
[Touch-packages] [Bug 1443882] Re: Rotation stops working
Can you clarify what you mean by pages? You mention scopes, but they never rotate? ** Changed in: unity8 (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1443882 Title: Rotation stops working Status in qtubuntu-sensors package in Ubuntu RTM: New Status in unity8 package in Ubuntu RTM: Incomplete Bug description: On the ubuntu phone, update to the latest release (r20), rotation sometimes stops working. ( the rotation lock is not set ofc ) Some pages are landscape, some are portrait, and none of them rotate anymore. Switching the rotation lock on and off does not change anything. Closing the scopes and opening them again does not help. Restarting the phone restores the functionality, at least for a while. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-rtm/+source/qtubuntu-sensors/+bug/1443882/+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 1443882] Re: Rotation stops working
Can you please have a look into ~/.cache/upstart/unity8.log an see whether these messages are printed when you rotate the phone: qtmir.sensor: Screen::customEvent - new orientation 1 handled qtmir.surfaces: MirSurfaceItem::setOrientation - orientation= 1 qtmir.sensor: Screen::onOrientationReadingChanged qtmir.sensor: Screen::customEvent - new orientation 2 handled qtmir.surfaces: MirSurfaceItem::setOrientation - orientation= 2 ** Also affects: qtubuntu-sensors (Ubuntu) Importance: Undecided Status: New ** Package changed: qtubuntu-sensors (Ubuntu) = qtubuntu-sensors (Ubuntu RTM) ** Package changed: unity8 (Ubuntu) = unity8 (Ubuntu RTM) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1443882 Title: Rotation stops working Status in qtubuntu-sensors package in Ubuntu RTM: New Status in unity8 package in Ubuntu RTM: Incomplete Bug description: On the ubuntu phone, update to the latest release (r20), rotation sometimes stops working. ( the rotation lock is not set ofc ) Some pages are landscape, some are portrait, and none of them rotate anymore. Switching the rotation lock on and off does not change anything. Closing the scopes and opening them again does not help. Restarting the phone restores the functionality, at least for a while. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-rtm/+source/qtubuntu-sensors/+bug/1443882/+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 1436982] Re: Unity freezes for a few seconds when 'clear all' is tapped in Notifications
** Tags added: qa-sanity -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1436982 Title: Unity freezes for a few seconds when 'clear all' is tapped in Notifications Status in unity8 package in Ubuntu: Triaged Bug description: 1. Create a missed call or sms. 2. Open Notification from top. 3. press the 'clear all' label 4. try to close the Notification menu by dragging it from bottom What happens: Nothing happens, unity seem to freeze for 2 seconds. This issue does not exist in RTM branch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1436982/+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 1436448] Re: Error messages while installing apport package
I try to install from mini.iso and similar errors. ** Attachment added: sysderr.png https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1436448/+attachment/4375069/+files/sysderr.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1436448 Title: Error messages while installing apport package Status in apport package in Ubuntu: Confirmed Bug description: ---Problem Description--- Error messages while installing apport package ---uname output--- 3.19.0-9-generic Machine Type = POWER8 ---Steps to Reproduce--- 1) Install Ubuntu 15.04 as a PowerKVM guest. 2) Install apport package using following command apt-get install apport Error messages are displayed during the installation. The installation eventually succeeds. root@ub1504:~# apt-get install apport Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: linux-headers-3.18.0-13 linux-headers-3.18.0-13-generic linux-image-3.18.0-13-generic linux-image-extra-3.18.0-13-generic python-support Use 'apt-get autoremove' to remove them. The following extra packages will be installed: apport-symptoms libpolkit-agent-1-0 libpolkit-backend-1-0 policykit-1 python3-apport python3-problem-report Suggested packages: apport-gtk apport-kde python3-launchpadlib The following NEW packages will be installed: apport apport-symptoms libpolkit-agent-1-0 libpolkit-backend-1-0 policykit-1 python3-apport python3-problem-report 0 upgraded, 7 newly installed, 0 to remove and 0 not upgraded. Need to get 312 kB of archives. After this operation, 2,296 kB of additional disk space will be used. Do you want to continue? [Y/n] y Get:1 http://ports.ubuntu.com/ubuntu-ports/ vivid/main libpolkit-agent-1-0 ppc64el 0.105-8ubuntu2 [14.6 kB] Get:2 http://ports.ubuntu.com/ubuntu-ports/ vivid/main libpolkit-backend-1-0 ppc64el 0.105-8ubuntu2 [33.5 kB] Get:3 http://ports.ubuntu.com/ubuntu-ports/ vivid/main python3-problem-report all 2.16.2-0ubuntu4 [10.1 kB] Get:4 http://ports.ubuntu.com/ubuntu-ports/ vivid/main python3-apport all 2.16.2-0ubuntu4 [75.9 kB] Get:5 http://ports.ubuntu.com/ubuntu-ports/ vivid/main apport all 2.16.2-0ubuntu4 [113 kB] Get:6 http://ports.ubuntu.com/ubuntu-ports/ vivid/main apport-symptoms all 0.20 [14.2 kB] Get:7 http://ports.ubuntu.com/ubuntu-ports/ vivid/main policykit-1 ppc64el 0.105-8ubuntu2 [50.7 kB] Fetched 312 kB in 1s (217 kB/s) Selecting previously unselected package libpolkit-agent-1-0:ppc64el. (Reading database ... 114319 files and directories currently installed.) Preparing to unpack .../libpolkit-agent-1-0_0.105-8ubuntu2_ppc64el.deb ... Unpacking libpolkit-agent-1-0:ppc64el (0.105-8ubuntu2) ... Selecting previously unselected package libpolkit-backend-1-0:ppc64el. Preparing to unpack .../libpolkit-backend-1-0_0.105-8ubuntu2_ppc64el.deb ... Unpacking libpolkit-backend-1-0:ppc64el (0.105-8ubuntu2) ... Selecting previously unselected package python3-problem-report. Preparing to unpack .../python3-problem-report_2.16.2-0ubuntu4_all.deb ... Unpacking python3-problem-report (2.16.2-0ubuntu4) ... Selecting previously unselected package python3-apport. Preparing to unpack .../python3-apport_2.16.2-0ubuntu4_all.deb ... Unpacking python3-apport (2.16.2-0ubuntu4) ... Selecting previously unselected package apport. Preparing to unpack .../apport_2.16.2-0ubuntu4_all.deb ... Unpacking apport (2.16.2-0ubuntu4) ... Selecting previously unselected package apport-symptoms. Preparing to unpack .../apport-symptoms_0.20_all.deb ... Unpacking apport-symptoms (0.20) ... Selecting previously unselected package policykit-1. Preparing to unpack .../policykit-1_0.105-8ubuntu2_ppc64el.deb ... Unpacking policykit-1 (0.105-8ubuntu2) ... Processing triggers for man-db (2.7.0.2-5) ... Processing triggers for shared-mime-info (1.3-1) ... Processing triggers for ureadahead (0.100.0-19) ... Processing triggers for dbus (1.8.12-1ubuntu3) ... Setting up libpolkit-agent-1-0:ppc64el (0.105-8ubuntu2) ... Setting up libpolkit-backend-1-0:ppc64el (0.105-8ubuntu2) ... Setting up python3-problem-report (2.16.2-0ubuntu4) ... Setting up python3-apport (2.16.2-0ubuntu4) ... Setting up apport (2.16.2-0ubuntu4) ... Error getting authority: Error initializing authority: Error calling StartServiceByName for org.freedesktop.PolicyKit1: Timeout was reached (g-io-error-quark, 24) Failed to execute operation: Connection timed out invoke-rc.d: apport.service doesn't exist but the upstart job does. Nothing to start or stop until a systemd or init job is present. Setting up apport-symptoms (0.20) ... Setting up policykit-1 (0.105-8ubuntu2) ... Processing
[Touch-packages] [Bug 1443906] [NEW] Xorg freeze
Public bug reported: [I reported with ubuntu-bug, seems ok, and provides same info as ubuntu-bug xorg (as I then chose xorg)?] I locked the screen (yes, I have dual screen setup) and when coming back seconds/minutes later the pointer was frozen and I could not type in a password. Note, I see the password prompt [e.g. not (fully) similar to a bug (#1311316]) I've reported previously, that is supposed to be fixed, but I get e-mails saying it isn't..]. Here, at work in 14.04, all details are clear in memory still except for (and see about 15.04 below): [From memory I tried and failed to go to a virtual terminal, in case I misremember, I think I at least confirmed CAPS LOCK light not working.] After restart I got a (apport) dialog box about X failed. Note, I tried (after opening chrome) to use it to finish using that dialog box to send the error but didn't get the web-report I expected (like I'm filling out now) or any confirmation, so I used ubuntu-bug manually as I wasn't sure you get the info otherwise. I wouldn't know for sure that this freeze is because of Xorg and still do not know for sure, just seems so based on the auto dialog and report as such. What I can speculate about, if this is a new bug it may even come from vivid/15.04 (what has been backported recently?) as I've gotten a freeze (same or possibly only similar symptoms) at home with it. Note there, I do not have dual screens as it is a laptop. There the computer may have suspended. I do not recall if this only happened there when closing lid/suspend or even without. The screen may have been black can't remember all details at least it was frozen and required a reboot.. At home I have Intel, here Nvidia Quadro graphics. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.13.0-49.81-generic 3.13.11-ckt17 Uname: Linux 3.13.0-49-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Apr 14 10:48:29 2015 DistUpgraded: 2015-03-19 11:34:13,727 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Once a week GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Since before I upgraded GraphicsCard: NVIDIA Corporation GF108GL [Quadro 600] [10de:0df8] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation Device [10de:0835] InstallationDate: Installed on 2014-08-26 (230 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: Dell Inc. Precision T1650 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-49-generic root=UUID=b342558f-2de5-4795-857d-67d51db3a726 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to trusty on 2015-03-19 (25 days ago) dmi.bios.date: 01/31/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 0X9M3X dmi.board.vendor: Dell Inc. dmi.board.version: A04 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA12:bd01/31/2013:svnDellInc.:pnPrecisionT1650:pvr01:rvnDellInc.:rn0X9M3X:rvrA04:cvnDellInc.:ct6:cvr: dmi.product.name: Precision T1650 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1~ubuntu2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.4 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Tue Apr 14 10:44:57 2015 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputPixArt USB Optical Mouse MOUSE, id 8 inputAT Translated Set 2 keyboard KEYBOARD, id 9 xserver.errors: Failed to load module nvidia (module does not exist, 0) Failed to load module nvidia (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.15.1-0ubuntu2.7 xserver.video_driver: nouveau ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 freeze trusty ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed
[Touch-packages] [Bug 1443791] Re: When running systemd the system sometimes logs out rather than locking the scrren
It's very unlikely that this is related to systemd, as it's got nothing at all to do with handling the user session and screen locking. This is handled by unity. The most probable reason is that unity crashes when it's trying to lock the screen. When this happens, do you get a crash notification? Do you have anything in /var/crash/ ? Please also attach ~/.cache/upstart/unity7.log right after this happens. Thanks! ** Package changed: systemd (Ubuntu) = unity (Ubuntu) ** Changed in: unity (Ubuntu) Status: New = Incomplete ** Summary changed: - When running systemd the system sometimes logs out rather than locking the scrren + the system sometimes logs out rather than locking the scrren ** Summary changed: - the system sometimes logs out rather than locking the scrren + the system sometimes logs out rather than locking the screen -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1443791 Title: the system sometimes logs out rather than locking the screen Status in unity package in Ubuntu: Incomplete Bug description: I am using Ubuntu 15.04 and booting with systemd. In most cases locking the screen works as expected but in certain cases the machine logs out instead. Can this be fixed? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1443791/+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 1437510] Re: Screen dim is not following the lock screen timeout (always dimming after 50 seconds)
USC implements the com.canonical.Unity.Screen.setInactivityTimeouts(poweroff_timeout, dim_timeout) interface. It's up to the components calling this interface to implement the policy by properly setting both timeouts. ** Changed in: unity-system-compositor (Ubuntu) Status: Confirmed = Invalid ** Changed in: unity-system-compositor (Ubuntu RTM) Status: Confirmed = Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-system-compositor in Ubuntu. https://bugs.launchpad.net/bugs/1437510 Title: Screen dim is not following the lock screen timeout (always dimming after 50 seconds) Status in the base for Ubuntu mobile products: Confirmed Status in unity-system-compositor package in Ubuntu: Invalid Status in unity-system-compositor package in Ubuntu RTM: Invalid Bug description: current build number: 258 device name: krillin channel: ubuntu-touch/ubuntu-rtm/14.09-proposed last update: 2015-03-26 16:39:52 version version: 258 version ubuntu: 20150326 version device: 20150310-3201c0a version custom: 20150216-561-29-186 Go to system settings, security, lock when idle, and change to any value higher than 1 minute. Now wait and you will see that the screen will dim after 50 seconds, no matter what value you set. The screen should only dim 10 seconds before reaching the screen lock value. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1437510/+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 1432843] Re: Lubuntu failed to boot
I got one single core machine with a 1 GB Geforce GT 210 (nvidia) and one dual core machine also with a 1GB Geforce GT 210. These are cards of only a few months old. Both fail to load Lubuntu vivid beta i386 20150413. -- 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/1432843 Title: Lubuntu failed to boot Status in X.Org X server: Confirmed Status in lubuntu-meta package in Ubuntu: Triaged Status in xorg package in Ubuntu: Triaged Bug description: The daily build of Lubuntu 20150316 failed to boot into the live session, and fails to install. During the boot session, the Lubuntu splash screen appears indicating that Lubuntu was loading. What follows next was a blank screen. Unfortunately, I cannot sumit the exact version of syslinux since the daily build could not boot into an interactive session. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: syslinux 3:6.03~pre18+dfsg-1ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0 Uname: Linux 3.19.0-7-generic i686 ApportVersion: 2.16.2-0ubuntu1 Architecture: i386 Date: Mon Mar 16 17:19:35 2015 Dependencies: gcc-5-base 5-20150228-1ubuntu1 libc6 2.19-15ubuntu2 libgcc1 1:5-20150228-1ubuntu1 mtools 4.0.18-2 multiarch-support 2.19-15ubuntu2 InstallationDate: Installed on 2015-03-05 (11 days ago) InstallationMedia: Lubuntu 15.04 Vivid Vervet - Alpha i386 (20150303) SourcePackage: syslinux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1432843/+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 1414930]
kernel 4.0 has been released it contains all required fixes. closing. -- 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/1414930 Title: [Lenovo ThinkPad 2015 models] Buttons of Synaptics trackpad doesn't work Status in HWE Next Project: In Progress Status in The Linux Kernel: Fix Released Status in libinput package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in linux source package in Trusty: Confirmed Status in systemd source package in Trusty: Confirmed Status in linux source package in Utopic: Confirmed Status in systemd source package in Utopic: Confirmed Bug description: Lenovo X1 3rd Carbon (201411-16196) Steps to reproduce the bug: 1, Log in to system 2, Click left/right/middle buttons of the touchpad Actual result: No response after clicking the buttons Expected results: Buttons work as expected behavirour ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-45-generic 3.13.0-45.74 [modified: boot/vmlinuz-3.13.0-45-generic] ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13 Uname: Linux 3.13.0-45-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: u 1598 F pulseaudio /dev/snd/controlC0: u 1598 F pulseaudio CurrentDesktop: Unity Date: Tue Jan 27 02:48:23 2015 HibernationDevice: RESUME=UUID=c553e9ba-b74b-43ad-8cf2-496531261e0f InstallationDate: Installed on 2015-01-27 (0 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20150126) MachineType: LENOVO 20BTZ09ZUS ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-45-generic root=UUID=1d34e685-c98b-41f3-b649-87770517b194 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-45-generic N/A linux-backports-modules-3.13.0-45-generic N/A linux-firmware 1.127.11 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/27/2014 dmi.bios.vendor: LENOVO dmi.bios.version: N14ET24W (1.02 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BTZ09ZUS dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN14ET24W(1.02):bd10/27/2014:svnLENOVO:pn20BTZ09ZUS:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BTZ09ZUS:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20BTZ09ZUS dmi.product.version: ThinkPad X1 Carbon 3rd dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1414930/+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 1414930] Re: [Lenovo ThinkPad 2015 models] Buttons of Synaptics trackpad doesn't work
** Changed in: linux Status: In Progress = Fix Released -- 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/1414930 Title: [Lenovo ThinkPad 2015 models] Buttons of Synaptics trackpad doesn't work Status in HWE Next Project: In Progress Status in The Linux Kernel: Fix Released Status in libinput package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in linux source package in Trusty: Confirmed Status in systemd source package in Trusty: Confirmed Status in linux source package in Utopic: Confirmed Status in systemd source package in Utopic: Confirmed Bug description: Lenovo X1 3rd Carbon (201411-16196) Steps to reproduce the bug: 1, Log in to system 2, Click left/right/middle buttons of the touchpad Actual result: No response after clicking the buttons Expected results: Buttons work as expected behavirour ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-45-generic 3.13.0-45.74 [modified: boot/vmlinuz-3.13.0-45-generic] ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13 Uname: Linux 3.13.0-45-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: u 1598 F pulseaudio /dev/snd/controlC0: u 1598 F pulseaudio CurrentDesktop: Unity Date: Tue Jan 27 02:48:23 2015 HibernationDevice: RESUME=UUID=c553e9ba-b74b-43ad-8cf2-496531261e0f InstallationDate: Installed on 2015-01-27 (0 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20150126) MachineType: LENOVO 20BTZ09ZUS ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-45-generic root=UUID=1d34e685-c98b-41f3-b649-87770517b194 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-45-generic N/A linux-backports-modules-3.13.0-45-generic N/A linux-firmware 1.127.11 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/27/2014 dmi.bios.vendor: LENOVO dmi.bios.version: N14ET24W (1.02 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BTZ09ZUS dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN14ET24W(1.02):bd10/27/2014:svnLENOVO:pn20BTZ09ZUS:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BTZ09ZUS:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20BTZ09ZUS dmi.product.version: ThinkPad X1 Carbon 3rd dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1414930/+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 1443869] [NEW] [Wizard] New wizard in Vivid doesn't excercise indicator gesture
Public bug reported: Test case. - Flash the device with a recent Vivid image. - Complete the wizard. - Go through edges demo. Expected result. - Edges demo exercises the indicator gesture. Actual result. - Indicators aren't opened. current build number: 184 device name: krillin channel: ubuntu-touch/devel-proposed ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New ** Tags: qa-regression -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1443869 Title: [Wizard] New wizard in Vivid doesn't excercise indicator gesture Status in unity8 package in Ubuntu: New Bug description: Test case. - Flash the device with a recent Vivid image. - Complete the wizard. - Go through edges demo. Expected result. - Edges demo exercises the indicator gesture. Actual result. - Indicators aren't opened. current build number: 184 device name: krillin channel: ubuntu-touch/devel-proposed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1443869/+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 1432696] Re: [SDK] Bottom edge header improvement
** Changed in: ubuntu-docviewer-app Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to messaging-app in Ubuntu. https://bugs.launchpad.net/bugs/1432696 Title: [SDK] Bottom edge header improvement Status in Dekko: Fix Released Status in Calendar application for Ubuntu devices: New Status in Clock application for Ubuntu devices: Triaged Status in Document Viewer application for Ubuntu devices: Fix Released Status in Ubuntu UX bugs: Fix Committed Status in address-book-app package in Ubuntu: Confirmed Status in dialer-app package in Ubuntu: Confirmed Status in messaging-app package in Ubuntu: Confirmed Status in ubuntu-clock-app package in Ubuntu: Confirmed Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Bug description: When user does a bottom edge gesture to show a new view (Address Book, Dialer, Clock, etc) the new header should never have a chevron pointing left, as it seems to suggest the wrong direction for the movement. The header of the new View should always have a chevron pointing down. Also, it should allow people using a gesture and dismiss the new screen by dragging or swiping the [chevron title area of the header] downward UX here: https://www.dropbox.com/s/ypmhej7ie2hrc9a/down_chevron_for_manage_dash_01%28wireframe%29.tiff?dl=0 VD: https://www.dropbox.com/s/1wuihy8tf7no7iw/Music_Down_Chevron.jpg?dl=0 To manage notifications about this bug go to: https://bugs.launchpad.net/dekko/+bug/1432696/+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 1361864] Re: add Tag property to ConnectionContext interface
This bug was fixed in the package ofono - 1.12.bzr6892+15.04.20150407-0ubuntu1 --- ofono (1.12.bzr6892+15.04.20150407-0ubuntu1) vivid; urgency=medium [ Alfonso Sanchez-Beato ] * ubuntu-apndb.c, src/common.c, test-common.c: provision IA APNs LTE modems may require a new IA APN for non-GPRS operation, this change allows a new IA APN type to be provisioned along with Internet and MMS APNs. * gril/grilunsol.c: LTE signal strength fix (LP: #1433867) * ubuntu-apndb.c: load APNS w/out explict type (LP: #1437200) * mtkodem, plugins/mtk.c, unit/tesk-mtkunsol.c: Dynamic MTK firwmare switching This change causes the firmware on specific MTK-based phone to be dynamically switched/reset based on SIM type and roaming conditions. * include, plugins/mtk.c, src/modem.c, gprs.c: set data for just one slot (LP: #1413672) Make sure ConnectionManager.Powered property is set for only one slot in case the modem is of type dual SIM stand-by. * doc, gprs: add 'Preferred' property to GPRS contexts (LP: #1361864) -- CI Train Bot ci-train-...@canonical.com Tue, 07 Apr 2015 06:50:28 + ** Changed in: ofono (Ubuntu) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1361864 Title: add Tag property to ConnectionContext interface Status in the base for Ubuntu mobile products: New Status in network-manager package in Ubuntu: Confirmed Status in nuntium package in Ubuntu: Confirmed Status in ofono package in Ubuntu: Fix Released Status in ubuntu-system-settings package in Ubuntu: Confirmed Bug description: To implement system-settings APN editor reliably there has to be a Tag field with is an arbitrary non user-visible string that can be set for any Context. We also need org.ofono.ConnectionManager.AddContext which takes a variant map with prepopulated values for the context to be created, so we can have a function in QOfono QOfonoConnectionManager::addContextWithTag(QString tag). To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1361864/+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 1432696] Re: [SDK] Bottom edge header improvement
It seems that the design assets attached to this bug report can no longer be accessed as the dropbox links are invalid. Can you please fix them? ** Changed in: ubuntu-clock-app Status: Triaged = In Progress ** Changed in: ubuntu-clock-app Assignee: (unassigned) = Nekhelesh Ramananthan (nik90) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to messaging-app in Ubuntu. https://bugs.launchpad.net/bugs/1432696 Title: [SDK] Bottom edge header improvement Status in Dekko: Fix Released Status in Calendar application for Ubuntu devices: New Status in Clock application for Ubuntu devices: In Progress Status in Document Viewer application for Ubuntu devices: Fix Released Status in Ubuntu UX bugs: Fix Committed Status in address-book-app package in Ubuntu: Confirmed Status in dialer-app package in Ubuntu: Confirmed Status in messaging-app package in Ubuntu: Confirmed Status in ubuntu-clock-app package in Ubuntu: Confirmed Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Bug description: When user does a bottom edge gesture to show a new view (Address Book, Dialer, Clock, etc) the new header should never have a chevron pointing left, as it seems to suggest the wrong direction for the movement. The header of the new View should always have a chevron pointing down. Also, it should allow people using a gesture and dismiss the new screen by dragging or swiping the [chevron title area of the header] downward UX here: https://www.dropbox.com/s/ypmhej7ie2hrc9a/down_chevron_for_manage_dash_01%28wireframe%29.tiff?dl=0 VD: https://www.dropbox.com/s/1wuihy8tf7no7iw/Music_Down_Chevron.jpg?dl=0 To manage notifications about this bug go to: https://bugs.launchpad.net/dekko/+bug/1432696/+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 1443853] Re: Ubuntu 14.10 ISO live boot in Oracle VirtualBox ends up with a corrupted display
Please see comment 1[1] and 14[2] on that ticket. We believe that this is a problem in setfont, not in VirtualBox (or Ubuntu for that matter). [1] https://www.virtualbox.org/ticket/13615#comment:1 [2] https://www.virtualbox.org/ticket/13615#comment:14 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1443853 Title: Ubuntu 14.10 ISO live boot in Oracle VirtualBox ends up with a corrupted display Status in Virtualbox: New Status in console-setup package in Ubuntu: New Status in virtualbox package in Ubuntu: New Bug description: (Content copied from Ubuntu 14.10 ISO live boot ends up with a corrupted display #13615 VirtualBox bug ticket, by piotrjurkiewicz) Booting up live session of Ubuntu MATE 14.10 and Ubuntu Gnome 14.10 from ISO ends up with a corrupted screen. See the screenshot: https://launchpadlibrarian.net/186864347/ubu.png Switching back and forth to the tty7 (ctrl+alt+F1 and then alt+F7) fixes the display. I think that this might be a problem with resolution setting: ``` 00:00:31.226379 Display::handleDisplayResize(): uScreenId = 0, pvVRAM= w=1152 h=400 bpp=0 cbLine=0x0, flags=0x1 00:00:31.226399 UIFrameBuffer::RequestResize: Screen=0, Format=0, BitsPerPixel=0, BytesPerLine=0, Size=1152x400, Sending to async-handler.. 00:00:31.226457 UIFrameBufferQImage::resizeEvent: Format=0, BitsPerPixel=0, BytesPerLine=0, Size=1152x400 00:00:31.226467 UIFrameBufferQImage::resizeEvent: Resizing to FALLBACK buffer due to format is invalid.. ``` After switching back and forth to the tty7 (what fixes the display) the log says: ``` 00:00:31.226379 Display::handleDisplayResize(): uScreenId = 0, pvVRAM= w=1152 h=400 bpp=0 cbLine=0x0, flags=0x1 00:00:31.226399 UIFrameBuffer::RequestResize: Screen=0, Format=0, BitsPerPixel=0, BytesPerLine=0, Size=1152x400, Sending to async-handler.. 00:00:31.226457 UIFrameBufferQImage::resizeEvent: Format=0, BitsPerPixel=0, BytesPerLine=0, Size=1152x400 00:00:31.226467 UIFrameBufferQImage::resizeEvent: Resizing to FALLBACK buffer due to format is invalid.. 00:01:37.584616 Display::handleDisplayResize(): uScreenId = 0, pvVRAM= w=720 h=400 bpp=0 cbLine=0x0, flags=0x1 00:01:37.584634 UIFrameBuffer::RequestResize: Screen=0, Format=0, BitsPerPixel=0, BytesPerLine=0, Size=720x400, Sending to async-handler.. 00:01:37.584680 UIFrameBufferQImage::resizeEvent: Format=0, BitsPerPixel=0, BytesPerLine=0, Size=720x400 00:01:37.584692 UIFrameBufferQImage::resizeEvent: Resizing to FALLBACK buffer due to format is invalid.. 00:01:39.055475 Display::handleDisplayResize(): uScreenId = 0, pvVRAM=0a7f w=1024 h=768 bpp=32 cbLine=0x1000, flags=0x1 00:01:39.055495 UIFrameBuffer::RequestResize: Screen=0, Format=843204434, BitsPerPixel=32, BytesPerLine=4096, Size=1024x768, Sending to async-handler.. 00:01:39.09 UIFrameBufferQImage::resizeEvent: Format=843204434, BitsPerPixel=32, BytesPerLine=4096, Size=1024x768 00:01:39.055568 UIFrameBufferQImage::resizeEvent: Resizing to directly use VGA device content.. ``` I have tested 4.3.18 and also the testbuild 4.3.19 r96825, it happens on both of them. You can download the ISO images of these two systems here: https://ubuntu-mate.r.worldssl.net/download/ubuntu-mate-14.10 -desktop-amd64.iso http://cdimage.ubuntu.com/ubuntu-gnome/releases/14.10/release/ubuntu- gnome-14.10-desktop-amd64.iso To manage notifications about this bug go to: https://bugs.launchpad.net/virtualbox/+bug/1443853/+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 1435778] Re: can not set applicationName property from variable
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1435778 Title: can not set applicationName property from variable Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Bug description: trying to use an external config for some global settings in an app framework it turns out that you can not set the applicationName property of a MainView from an external variable ... it seems like the qml/js imports are only processed after the empty APP_ID was handed to the lifecycle management. using either an imported .js file or a singleton imported from a qml file like in http://paste.ubuntu.com/10667313/ and http://paste.ubuntu.com/10667782/ always results in the following errors in the application log: [0323/175358:ERROR:cache_util.cc(132)] Unable to move cache folder /home/phablet/.cache/QtProject/foo-bar.ogra/Cache to /home/phablet/.cache/QtProject/foo-bar.ogra/old_Cache_000 [0323/175358:ERROR:cache_creator.cc(133)] Unable to create cache [0323/175358:ERROR:cache_util.cc(132)] Unable to move cache folder /home/phablet/.local/share/QtProject/foo-bar.ogra/GPUCache to /home/phablet/.local/share/QtProject/foo-bar.ogra/old_GPUCache_000 [0323/175358:ERROR:cache_creator.cc(133)] Unable to create cache [0323/175358:ERROR:shader_disk_cache.cc(614)] Shader Cache Creation failed: -2 additionally apparmor denials can be seen for the same path (as expected, an app should not try to create something out of its namespace) in /var/log/syslog To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1435778/+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 1443869] Re: [Wizard] New wizard in Vivid doesn't excercise indicator gesture
** Also affects: ubuntu-ux Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1443869 Title: [Wizard] New wizard in Vivid doesn't excercise indicator gesture Status in Ubuntu UX bugs: New Status in unity8 package in Ubuntu: New Bug description: Test case. - Flash the device with a recent Vivid image. - Complete the wizard. - Go through edges demo. Expected result. - Edges demo exercises the indicator gesture. Actual result. - Indicators aren't opened. current build number: 184 device name: krillin channel: ubuntu-touch/devel-proposed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1443869/+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 803627] Re: empathy crashed with signal 5 in gtk_box_size_allocate()
Some widget (probably a custom one from empathy) reported a negative minimum size, resulting in gtk to abort on an assertion. So this is not really a gtk issue. Since it is quite old and I cannot reproduce it in newer versions, I'll close it. If this is still a problem for anyone, feel free to reopen this bug and add empathy as being affected. ** Changed in: gtk+3.0 (Ubuntu) Status: Triaged = Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/803627 Title: empathy crashed with signal 5 in gtk_box_size_allocate() Status in GTK+ GUI Toolkit: New Status in gtk+3.0 package in Ubuntu: Invalid Bug description: Open empathy and click in link contacts... (Facebook) and crash. My acount is Gabble, butterfly and IRC. ProblemType: Crash DistroRelease: Ubuntu 11.10 Package: empathy 3.1.2.1-1ubuntu1 Uname: Linux 3.0.0-0300rc5-generic x86_64 Architecture: amd64 Date: Wed Jun 29 16:02:32 2011 ExecutablePath: /usr/bin/empathy InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Alpha amd64 (20110531.1) ProcCmdline: empathy ProcEnviron: LANGUAGE=es_ES:en PATH=(custom, no user) LANG=es_CL.UTF-8 LC_MESSAGES=es_ES.UTF-8 SHELL=/bin/bash Signal: 5 SourcePackage: empathy StacktraceTop: gtk_box_size_allocate (widget=value optimized out, allocation=value optimized out) at /build/buildd/gtk+3.0-3.1.6/./gtk/gtkbox.c:480 g_closure_invoke (closure=0x27815b0, return_value=0x0, n_param_values=2, param_values=0x7f19e4066760, invocation_hint=value optimized out) at /build/buildd/glib2.0-2.29.8/./gobject/gclosure.c:771 signal_emit_unlocked_R (node=value optimized out, detail=0, instance=0x301dcb0, emission_return=0x0, instance_and_params=0x7f19e4066760) at /build/buildd/glib2.0-2.29.8/./gobject/gsignal.c:3186 g_signal_emit_valist (instance=value optimized out, signal_id=value optimized out, detail=value optimized out, var_args=0x7fff9337b688) at /build/buildd/glib2.0-2.29.8/./gobject/gsignal.c:2987 g_signal_emit (instance=value optimized out, signal_id=value optimized out, detail=value optimized out) at /build/buildd/glib2.0-2.29.8/./gobject/gsignal.c:3044 Title: empathy crashed with signal 5 in gtk_box_size_allocate() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/803627/+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 1443853] Re: Ubuntu 14.10 ISO live boot in VirtualBox ends up with a corrupted display
** Changed in: virtualbox Status: Unknown = New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1443853 Title: Ubuntu 14.10 ISO live boot in VirtualBox ends up with a corrupted display Status in Virtualbox: New Status in console-setup package in Ubuntu: New Status in virtualbox package in Ubuntu: New Bug description: (Content copied from Ubuntu 14.10 ISO live boot ends up with a corrupted display #13615 VirtualBox bug ticket, by piotrjurkiewicz) Booting up live session of Ubuntu MATE 14.10 and Ubuntu Gnome 14.10 from ISO ends up with a corrupted screen. See the screenshot: https://launchpadlibrarian.net/186864347/ubu.png Switching back and forth to the tty7 (ctrl+alt+F1 and then alt+F7) fixes the display. I think that this might be a problem with resolution setting: ``` 00:00:31.226379 Display::handleDisplayResize(): uScreenId = 0, pvVRAM= w=1152 h=400 bpp=0 cbLine=0x0, flags=0x1 00:00:31.226399 UIFrameBuffer::RequestResize: Screen=0, Format=0, BitsPerPixel=0, BytesPerLine=0, Size=1152x400, Sending to async-handler.. 00:00:31.226457 UIFrameBufferQImage::resizeEvent: Format=0, BitsPerPixel=0, BytesPerLine=0, Size=1152x400 00:00:31.226467 UIFrameBufferQImage::resizeEvent: Resizing to FALLBACK buffer due to format is invalid.. ``` After switching back and forth to the tty7 (what fixes the display) the log says: ``` 00:00:31.226379 Display::handleDisplayResize(): uScreenId = 0, pvVRAM= w=1152 h=400 bpp=0 cbLine=0x0, flags=0x1 00:00:31.226399 UIFrameBuffer::RequestResize: Screen=0, Format=0, BitsPerPixel=0, BytesPerLine=0, Size=1152x400, Sending to async-handler.. 00:00:31.226457 UIFrameBufferQImage::resizeEvent: Format=0, BitsPerPixel=0, BytesPerLine=0, Size=1152x400 00:00:31.226467 UIFrameBufferQImage::resizeEvent: Resizing to FALLBACK buffer due to format is invalid.. 00:01:37.584616 Display::handleDisplayResize(): uScreenId = 0, pvVRAM= w=720 h=400 bpp=0 cbLine=0x0, flags=0x1 00:01:37.584634 UIFrameBuffer::RequestResize: Screen=0, Format=0, BitsPerPixel=0, BytesPerLine=0, Size=720x400, Sending to async-handler.. 00:01:37.584680 UIFrameBufferQImage::resizeEvent: Format=0, BitsPerPixel=0, BytesPerLine=0, Size=720x400 00:01:37.584692 UIFrameBufferQImage::resizeEvent: Resizing to FALLBACK buffer due to format is invalid.. 00:01:39.055475 Display::handleDisplayResize(): uScreenId = 0, pvVRAM=0a7f w=1024 h=768 bpp=32 cbLine=0x1000, flags=0x1 00:01:39.055495 UIFrameBuffer::RequestResize: Screen=0, Format=843204434, BitsPerPixel=32, BytesPerLine=4096, Size=1024x768, Sending to async-handler.. 00:01:39.09 UIFrameBufferQImage::resizeEvent: Format=843204434, BitsPerPixel=32, BytesPerLine=4096, Size=1024x768 00:01:39.055568 UIFrameBufferQImage::resizeEvent: Resizing to directly use VGA device content.. ``` I have tested 4.3.18 and also the testbuild 4.3.19 r96825, it happens on both of them. You can download the ISO images of these two systems here: https://ubuntu-mate.r.worldssl.net/download/ubuntu-mate-14.10 -desktop-amd64.iso http://cdimage.ubuntu.com/ubuntu-gnome/releases/14.10/release/ubuntu- gnome-14.10-desktop-amd64.iso To manage notifications about this bug go to: https://bugs.launchpad.net/virtualbox/+bug/1443853/+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 813653] Re: gedit crashed with SIGSEGV in g_type_check_instance_is_a()
This was fixed upstream: https://bugzilla.gnome.org/show_bug.cgi?id=664137 The upstream bug linked here is a duplicate of the above. ** Bug watch added: GNOME Bug Tracker #664137 https://bugzilla.gnome.org/show_bug.cgi?id=664137 ** Changed in: gtk+3.0 (Ubuntu) Status: Triaged = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/813653 Title: gedit crashed with SIGSEGV in g_type_check_instance_is_a() Status in GTK+ GUI Toolkit: Invalid Status in gtk+3.0 package in Ubuntu: Fix Released Bug description: trying to open a second file in gedit on a Flaky oneiric install ProblemType: Crash DistroRelease: Ubuntu 11.10 Package: gedit 3.1.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-5.6-generic 3.0.0-rc7 Uname: Linux 3.0.0-5-generic x86_64 Architecture: amd64 Date: Wed Jul 20 18:33:05 2011 ExecutablePath: /usr/bin/gedit InstallationMedia: Ubuntu 11.04 Natty Narwhal - Beta amd64 (20110417) ProcCmdline: gedit ProcEnviron: SHELL=/bin/bash PATH=(custom, no user) LANGUAGE=en_GB:en LANG=en_GB.UTF-8 SegvAnalysis: Segfault happened at: 0x7fa91b173ff0 g_type_check_instance_is_a+112: testb $0x4,0x16(%rdi) PC (0x7fa91b173ff0) ok source $0x4 ok destination 0x16(%rdi) (0x7fa900100016) not located in a known VMA region (needed writable region)! SegvReason: writing unknown VMA Signal: 11 SourcePackage: gedit StacktraceTop: g_type_check_instance_is_a () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_file_equal () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/libgtk-3.so.0 ?? () from /usr/lib/libgtk-3.so.0 ?? () from /usr/lib/libgtk-3.so.0 Title: gedit crashed with SIGSEGV in g_type_check_instance_is_a() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm admin cdrom dialout lpadmin netdev plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/813653/+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 1423542] Re: regresion: buttons styled differently
This bug was fixed in the package unity-greeter - 15.04.4-0ubuntu1 --- unity-greeter (15.04.4-0ubuntu1) vivid; urgency=medium * New upstream release: - Update unity-greeter so it is possible to style buttons in greeter with css (LP: #1423542) * debian/control: - Use standards version 3.9.6 -- Robert Ancell robert.anc...@canonical.com Tue, 14 Apr 2015 13:06:52 +1200 ** Changed in: unity-greeter (Ubuntu) Status: In Progress = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1423542 Title: regresion: buttons styled differently Status in ubuntu-themes package in Ubuntu: Fix Released Status in unity-greeter package in Ubuntu: Fix Released Bug description: Unity greeter buttons are styled differently compared to previus ubuntu version: 1) Session option button has background-color and border. 2) All buttons look similar in session chooser. It is not possible to see currently selected session. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1423542/+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 1443853] [NEW] Ubuntu 14.10 ISO live boot ends up with a corrupted display
Public bug reported: (Content copied from Ubuntu 14.10 ISO live boot ends up with a corrupted display #13615 VirtualBox bug ticket, by piotrjurkiewicz) Booting up live session of Ubuntu MATE 14.10 and Ubuntu Gnome 14.10 from ISO ends up with a corrupted screen. See the screenshot: https://launchpadlibrarian.net/186864347/ubu.png Switching back and forth to the tty7 (ctrl+alt+F1 and then alt+F7) fixes the display. I think that this might be a problem with resolution setting: ``` 00:00:31.226379 Display::handleDisplayResize(): uScreenId = 0, pvVRAM= w=1152 h=400 bpp=0 cbLine=0x0, flags=0x1 00:00:31.226399 UIFrameBuffer::RequestResize: Screen=0, Format=0, BitsPerPixel=0, BytesPerLine=0, Size=1152x400, Sending to async-handler.. 00:00:31.226457 UIFrameBufferQImage::resizeEvent: Format=0, BitsPerPixel=0, BytesPerLine=0, Size=1152x400 00:00:31.226467 UIFrameBufferQImage::resizeEvent: Resizing to FALLBACK buffer due to format is invalid.. ``` After switching back and forth to the tty7 (what fixes the display) the log says: ``` 00:00:31.226379 Display::handleDisplayResize(): uScreenId = 0, pvVRAM= w=1152 h=400 bpp=0 cbLine=0x0, flags=0x1 00:00:31.226399 UIFrameBuffer::RequestResize: Screen=0, Format=0, BitsPerPixel=0, BytesPerLine=0, Size=1152x400, Sending to async-handler.. 00:00:31.226457 UIFrameBufferQImage::resizeEvent: Format=0, BitsPerPixel=0, BytesPerLine=0, Size=1152x400 00:00:31.226467 UIFrameBufferQImage::resizeEvent: Resizing to FALLBACK buffer due to format is invalid.. 00:01:37.584616 Display::handleDisplayResize(): uScreenId = 0, pvVRAM= w=720 h=400 bpp=0 cbLine=0x0, flags=0x1 00:01:37.584634 UIFrameBuffer::RequestResize: Screen=0, Format=0, BitsPerPixel=0, BytesPerLine=0, Size=720x400, Sending to async-handler.. 00:01:37.584680 UIFrameBufferQImage::resizeEvent: Format=0, BitsPerPixel=0, BytesPerLine=0, Size=720x400 00:01:37.584692 UIFrameBufferQImage::resizeEvent: Resizing to FALLBACK buffer due to format is invalid.. 00:01:39.055475 Display::handleDisplayResize(): uScreenId = 0, pvVRAM=0a7f w=1024 h=768 bpp=32 cbLine=0x1000, flags=0x1 00:01:39.055495 UIFrameBuffer::RequestResize: Screen=0, Format=843204434, BitsPerPixel=32, BytesPerLine=4096, Size=1024x768, Sending to async-handler.. 00:01:39.09 UIFrameBufferQImage::resizeEvent: Format=843204434, BitsPerPixel=32, BytesPerLine=4096, Size=1024x768 00:01:39.055568 UIFrameBufferQImage::resizeEvent: Resizing to directly use VGA device content.. ``` I have tested 4.3.18 and also the testbuild 4.3.19 r96825, it happens on both of them. You can download the ISO images of these two systems here: https://ubuntu-mate.r.worldssl.net/download/ubuntu-mate-14.10-desktop- amd64.iso http://cdimage.ubuntu.com/ubuntu-gnome/releases/14.10/release/ubuntu- gnome-14.10-desktop-amd64.iso ** Affects: console-setup (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1443853 Title: Ubuntu 14.10 ISO live boot ends up with a corrupted display Status in console-setup package in Ubuntu: New Bug description: (Content copied from Ubuntu 14.10 ISO live boot ends up with a corrupted display #13615 VirtualBox bug ticket, by piotrjurkiewicz) Booting up live session of Ubuntu MATE 14.10 and Ubuntu Gnome 14.10 from ISO ends up with a corrupted screen. See the screenshot: https://launchpadlibrarian.net/186864347/ubu.png Switching back and forth to the tty7 (ctrl+alt+F1 and then alt+F7) fixes the display. I think that this might be a problem with resolution setting: ``` 00:00:31.226379 Display::handleDisplayResize(): uScreenId = 0, pvVRAM= w=1152 h=400 bpp=0 cbLine=0x0, flags=0x1 00:00:31.226399 UIFrameBuffer::RequestResize: Screen=0, Format=0, BitsPerPixel=0, BytesPerLine=0, Size=1152x400, Sending to async-handler.. 00:00:31.226457 UIFrameBufferQImage::resizeEvent: Format=0, BitsPerPixel=0, BytesPerLine=0, Size=1152x400 00:00:31.226467 UIFrameBufferQImage::resizeEvent: Resizing to FALLBACK buffer due to format is invalid.. ``` After switching back and forth to the tty7 (what fixes the display) the log says: ``` 00:00:31.226379 Display::handleDisplayResize(): uScreenId = 0, pvVRAM= w=1152 h=400 bpp=0 cbLine=0x0, flags=0x1 00:00:31.226399 UIFrameBuffer::RequestResize: Screen=0, Format=0, BitsPerPixel=0, BytesPerLine=0, Size=1152x400, Sending to async-handler.. 00:00:31.226457 UIFrameBufferQImage::resizeEvent: Format=0, BitsPerPixel=0, BytesPerLine=0, Size=1152x400 00:00:31.226467 UIFrameBufferQImage::resizeEvent: Resizing to FALLBACK buffer due to format is invalid.. 00:01:37.584616 Display::handleDisplayResize(): uScreenId = 0, pvVRAM= w=720 h=400 bpp=0 cbLine=0x0, flags=0x1 00:01:37.584634
[Touch-packages] [Bug 1443853] Re: Ubuntu 14.10 ISO live boot in VirtualBox ends up with a corrupted display
** Summary changed: - Ubuntu 14.10 ISO live boot ends up with a corrupted display + Ubuntu 14.10 ISO live boot in VirtualBox ends up with a corrupted display ** Also affects: virtualbox (Ubuntu) Importance: Undecided Status: New ** Bug watch added: Virtualbox Trac #13615 http://www.virtualbox.org/ticket/13615 ** Also affects: virtualbox via http://www.virtualbox.org/ticket/13615 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1443853 Title: Ubuntu 14.10 ISO live boot in VirtualBox ends up with a corrupted display Status in Virtualbox: Unknown Status in console-setup package in Ubuntu: New Status in virtualbox package in Ubuntu: New Bug description: (Content copied from Ubuntu 14.10 ISO live boot ends up with a corrupted display #13615 VirtualBox bug ticket, by piotrjurkiewicz) Booting up live session of Ubuntu MATE 14.10 and Ubuntu Gnome 14.10 from ISO ends up with a corrupted screen. See the screenshot: https://launchpadlibrarian.net/186864347/ubu.png Switching back and forth to the tty7 (ctrl+alt+F1 and then alt+F7) fixes the display. I think that this might be a problem with resolution setting: ``` 00:00:31.226379 Display::handleDisplayResize(): uScreenId = 0, pvVRAM= w=1152 h=400 bpp=0 cbLine=0x0, flags=0x1 00:00:31.226399 UIFrameBuffer::RequestResize: Screen=0, Format=0, BitsPerPixel=0, BytesPerLine=0, Size=1152x400, Sending to async-handler.. 00:00:31.226457 UIFrameBufferQImage::resizeEvent: Format=0, BitsPerPixel=0, BytesPerLine=0, Size=1152x400 00:00:31.226467 UIFrameBufferQImage::resizeEvent: Resizing to FALLBACK buffer due to format is invalid.. ``` After switching back and forth to the tty7 (what fixes the display) the log says: ``` 00:00:31.226379 Display::handleDisplayResize(): uScreenId = 0, pvVRAM= w=1152 h=400 bpp=0 cbLine=0x0, flags=0x1 00:00:31.226399 UIFrameBuffer::RequestResize: Screen=0, Format=0, BitsPerPixel=0, BytesPerLine=0, Size=1152x400, Sending to async-handler.. 00:00:31.226457 UIFrameBufferQImage::resizeEvent: Format=0, BitsPerPixel=0, BytesPerLine=0, Size=1152x400 00:00:31.226467 UIFrameBufferQImage::resizeEvent: Resizing to FALLBACK buffer due to format is invalid.. 00:01:37.584616 Display::handleDisplayResize(): uScreenId = 0, pvVRAM= w=720 h=400 bpp=0 cbLine=0x0, flags=0x1 00:01:37.584634 UIFrameBuffer::RequestResize: Screen=0, Format=0, BitsPerPixel=0, BytesPerLine=0, Size=720x400, Sending to async-handler.. 00:01:37.584680 UIFrameBufferQImage::resizeEvent: Format=0, BitsPerPixel=0, BytesPerLine=0, Size=720x400 00:01:37.584692 UIFrameBufferQImage::resizeEvent: Resizing to FALLBACK buffer due to format is invalid.. 00:01:39.055475 Display::handleDisplayResize(): uScreenId = 0, pvVRAM=0a7f w=1024 h=768 bpp=32 cbLine=0x1000, flags=0x1 00:01:39.055495 UIFrameBuffer::RequestResize: Screen=0, Format=843204434, BitsPerPixel=32, BytesPerLine=4096, Size=1024x768, Sending to async-handler.. 00:01:39.09 UIFrameBufferQImage::resizeEvent: Format=843204434, BitsPerPixel=32, BytesPerLine=4096, Size=1024x768 00:01:39.055568 UIFrameBufferQImage::resizeEvent: Resizing to directly use VGA device content.. ``` I have tested 4.3.18 and also the testbuild 4.3.19 r96825, it happens on both of them. You can download the ISO images of these two systems here: https://ubuntu-mate.r.worldssl.net/download/ubuntu-mate-14.10 -desktop-amd64.iso http://cdimage.ubuntu.com/ubuntu-gnome/releases/14.10/release/ubuntu- gnome-14.10-desktop-amd64.iso To manage notifications about this bug go to: https://bugs.launchpad.net/virtualbox/+bug/1443853/+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 1443861] [NEW] [Phone call] When accepting a call, call panel takes at least 10s to appear
Public bug reported: I have a BQ phone with the devel-proposed channel. When someone calls you and you accept the call, there is 10s where nothing happens. Call panel is loading and no sounds comes. Should be great to reduce this time ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: bq call devel-proposed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1443861 Title: [Phone call] When accepting a call, call panel takes at least 10s to appear Status in network-manager package in Ubuntu: New Bug description: I have a BQ phone with the devel-proposed channel. When someone calls you and you accept the call, there is 10s where nothing happens. Call panel is loading and no sounds comes. Should be great to reduce this time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1443861/+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 1443853] Re: Ubuntu 14.10 ISO live boot in Oracle VirtualBox ends up with a corrupted display
** Summary changed: - Ubuntu 14.10 ISO live boot in VirtualBox ends up with a corrupted display + Ubuntu 14.10 ISO live boot in Oracle VirtualBox ends up with a corrupted display -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1443853 Title: Ubuntu 14.10 ISO live boot in Oracle VirtualBox ends up with a corrupted display Status in Virtualbox: New Status in console-setup package in Ubuntu: New Status in virtualbox package in Ubuntu: New Bug description: (Content copied from Ubuntu 14.10 ISO live boot ends up with a corrupted display #13615 VirtualBox bug ticket, by piotrjurkiewicz) Booting up live session of Ubuntu MATE 14.10 and Ubuntu Gnome 14.10 from ISO ends up with a corrupted screen. See the screenshot: https://launchpadlibrarian.net/186864347/ubu.png Switching back and forth to the tty7 (ctrl+alt+F1 and then alt+F7) fixes the display. I think that this might be a problem with resolution setting: ``` 00:00:31.226379 Display::handleDisplayResize(): uScreenId = 0, pvVRAM= w=1152 h=400 bpp=0 cbLine=0x0, flags=0x1 00:00:31.226399 UIFrameBuffer::RequestResize: Screen=0, Format=0, BitsPerPixel=0, BytesPerLine=0, Size=1152x400, Sending to async-handler.. 00:00:31.226457 UIFrameBufferQImage::resizeEvent: Format=0, BitsPerPixel=0, BytesPerLine=0, Size=1152x400 00:00:31.226467 UIFrameBufferQImage::resizeEvent: Resizing to FALLBACK buffer due to format is invalid.. ``` After switching back and forth to the tty7 (what fixes the display) the log says: ``` 00:00:31.226379 Display::handleDisplayResize(): uScreenId = 0, pvVRAM= w=1152 h=400 bpp=0 cbLine=0x0, flags=0x1 00:00:31.226399 UIFrameBuffer::RequestResize: Screen=0, Format=0, BitsPerPixel=0, BytesPerLine=0, Size=1152x400, Sending to async-handler.. 00:00:31.226457 UIFrameBufferQImage::resizeEvent: Format=0, BitsPerPixel=0, BytesPerLine=0, Size=1152x400 00:00:31.226467 UIFrameBufferQImage::resizeEvent: Resizing to FALLBACK buffer due to format is invalid.. 00:01:37.584616 Display::handleDisplayResize(): uScreenId = 0, pvVRAM= w=720 h=400 bpp=0 cbLine=0x0, flags=0x1 00:01:37.584634 UIFrameBuffer::RequestResize: Screen=0, Format=0, BitsPerPixel=0, BytesPerLine=0, Size=720x400, Sending to async-handler.. 00:01:37.584680 UIFrameBufferQImage::resizeEvent: Format=0, BitsPerPixel=0, BytesPerLine=0, Size=720x400 00:01:37.584692 UIFrameBufferQImage::resizeEvent: Resizing to FALLBACK buffer due to format is invalid.. 00:01:39.055475 Display::handleDisplayResize(): uScreenId = 0, pvVRAM=0a7f w=1024 h=768 bpp=32 cbLine=0x1000, flags=0x1 00:01:39.055495 UIFrameBuffer::RequestResize: Screen=0, Format=843204434, BitsPerPixel=32, BytesPerLine=4096, Size=1024x768, Sending to async-handler.. 00:01:39.09 UIFrameBufferQImage::resizeEvent: Format=843204434, BitsPerPixel=32, BytesPerLine=4096, Size=1024x768 00:01:39.055568 UIFrameBufferQImage::resizeEvent: Resizing to directly use VGA device content.. ``` I have tested 4.3.18 and also the testbuild 4.3.19 r96825, it happens on both of them. You can download the ISO images of these two systems here: https://ubuntu-mate.r.worldssl.net/download/ubuntu-mate-14.10 -desktop-amd64.iso http://cdimage.ubuntu.com/ubuntu-gnome/releases/14.10/release/ubuntu- gnome-14.10-desktop-amd64.iso To manage notifications about this bug go to: https://bugs.launchpad.net/virtualbox/+bug/1443853/+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 1443882] [NEW] Rotation stops working
Public bug reported: On the ubuntu phone, update to the latest release (r20), rotation sometimes stops working. ( the rotation lock is not set ofc ) Some pages are landscape, some are portrait, and none of them rotate anymore. Switching the rotation lock on and off does not change anything. Closing the scopes and opening them again does not help. Restarting the phone restores the functionality, at least for a while. ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1443882 Title: Rotation stops working Status in unity8 package in Ubuntu: New Bug description: On the ubuntu phone, update to the latest release (r20), rotation sometimes stops working. ( the rotation lock is not set ofc ) Some pages are landscape, some are portrait, and none of them rotate anymore. Switching the rotation lock on and off does not change anything. Closing the scopes and opening them again does not help. Restarting the phone restores the functionality, at least for a while. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1443882/+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 1443843] Re: text too small on New alarm screen.
Hi Mike, Thanks for the detailed description on the issue. It seems during our user testing, testers found the font size to be too small in some areas of the clock app. We are tracking that at https://bugs.launchpad.net/ubuntu-clock-app/+bug/1432736. You also seem to be pointing at the scroll wheel (time picker) being small as well. Let's use this bug to track that issue. The time picker is a standard upstream SDK widget and so the fix should come from them. I will let the SDK team know and get this in their radar. ** Changed in: ubuntu-clock-app Status: Incomplete = Confirmed ** Also affects: ubuntu-ux Importance: Undecided Status: New ** Summary changed: - text too small on New alarm screen. + Time picker width too small leading to accidental changes in other columns ** Also affects: ubuntu-ui-toolkit (Ubuntu) Importance: Undecided Status: New ** Description changed: Ubuntu Touch 14.10 (r20) running on BQ Ubuntu Edition. + + Issue: The time picker occupies the entire width of the alarm page and + yet the actual dials occupy only a fraction of that width resulting in + users accidentally changing other column values. + + May be we should increase the width of the dials? ** Tags added: needs-design -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1443843 Title: Time picker width too small leading to accidental changes in other columns Status in Clock application for Ubuntu devices: Confirmed Status in Ubuntu UX bugs: New Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: Ubuntu Touch 14.10 (r20) running on BQ Ubuntu Edition. Issue: The time picker occupies the entire width of the alarm page and yet the actual dials occupy only a fraction of that width resulting in users accidentally changing other column values. May be we should increase the width of the dials? Screenshot: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui- toolkit/+bug/1443843/+attachment/4375026/+files/timepicker.png To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-clock-app/+bug/1443843/+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 1443843] Re: Time picker width too small leading to accidental changes in other columns
** Attachment added: timepicker.png https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1443843/+attachment/4375026/+files/timepicker.png ** Description changed: Ubuntu Touch 14.10 (r20) running on BQ Ubuntu Edition. Issue: The time picker occupies the entire width of the alarm page and yet the actual dials occupy only a fraction of that width resulting in users accidentally changing other column values. May be we should increase the width of the dials? + + Screenshot: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui- + toolkit/+bug/1443843/+attachment/4375026/+files/timepicker.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1443843 Title: Time picker width too small leading to accidental changes in other columns Status in Clock application for Ubuntu devices: Confirmed Status in Ubuntu UX bugs: New Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: Ubuntu Touch 14.10 (r20) running on BQ Ubuntu Edition. Issue: The time picker occupies the entire width of the alarm page and yet the actual dials occupy only a fraction of that width resulting in users accidentally changing other column values. May be we should increase the width of the dials? Screenshot: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui- toolkit/+bug/1443843/+attachment/4375026/+files/timepicker.png To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-clock-app/+bug/1443843/+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 1416424] Re: Wifi list is empty
** Changed in: indicator-network (Ubuntu) Assignee: (unassigned) = Antti Kaijanmäki (kaijanmaki) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1416424 Title: Wifi list is empty Status in indicator-network package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Invalid Bug description: On recent vivid-proposed builds for mako (e.g. r83), the Wifi list in the network indicator as well as in the system settings is empty, even when the phone has automatically connected to a saved network. phablet@ubuntu-phablet:~$ system-image-cli -i current build number: 84 device name: mako channel: ubuntu-touch/devel-proposed alias: ubuntu-touch/vivid-proposed last update: 2015-01-30 14:45:36 version version: 84 version ubuntu: 20150130 version device: 20150129 version custom: 20150130 Systems Effected: Mako Flo Manta To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1416424/+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 1432843] Re: Lubuntu failed to boot
I installed a system into a USB 3 pendrive from the current Lubuntu Vivid i386 desktop iso in the Toshiba. It works there but not in the desktop computer with the ASUS mobo. Then I installed the xserver-xorg- video-all package. The kernel is kernel 3.19.0-13-generic #13-Ubuntu SMP Mon Mar 23 ... i686 in this case and I updated/upgraded it to the bleeding edge. This installed system reboots nicely in the Toshiba. And now, tadaa, it boots nicely and works with the ASUS mobo too. http://www.asus.com/Motherboards/M2NVM_DVI/ @ Kamilion, You found the solution :-) @ gilir, I hope you can squeeze this new package into the desktop iso without making it oversized for CD. There should be some package with lower priority. What a happy feeling that this works again in typical target computers for Lubuntu 32-bit systems :-) -- 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/1432843 Title: Lubuntu failed to boot Status in X.Org X server: Confirmed Status in lubuntu-meta package in Ubuntu: Triaged Status in xorg package in Ubuntu: Triaged Bug description: The daily build of Lubuntu 20150316 failed to boot into the live session, and fails to install. During the boot session, the Lubuntu splash screen appears indicating that Lubuntu was loading. What follows next was a blank screen. Unfortunately, I cannot sumit the exact version of syslinux since the daily build could not boot into an interactive session. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: syslinux 3:6.03~pre18+dfsg-1ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0 Uname: Linux 3.19.0-7-generic i686 ApportVersion: 2.16.2-0ubuntu1 Architecture: i386 Date: Mon Mar 16 17:19:35 2015 Dependencies: gcc-5-base 5-20150228-1ubuntu1 libc6 2.19-15ubuntu2 libgcc1 1:5-20150228-1ubuntu1 mtools 4.0.18-2 multiarch-support 2.19-15ubuntu2 InstallationDate: Installed on 2015-03-05 (11 days ago) InstallationMedia: Lubuntu 15.04 Vivid Vervet - Alpha i386 (20150303) SourcePackage: syslinux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1432843/+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 1366661] Re: Xorg freeze
Luiz, just to advise, this report is only scoped to the hardware (GTX 580M) and problem noted in the Bug Description. If you are having an issue with a different card/HW combination, please file a new report that. Just to clarify, did you test 12.04.0? -- 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/131 Title: Xorg freeze Status in xorg package in Ubuntu: Incomplete Bug description: My system freezes always while i am playing cs source dust2 map. The system shutdown and a see a message in logs: nvidia has fallen off bus. I search for another relevant information without success. I am using kernel 3.10.54 with nvidia 331.89 proprietary driver. WORKAROUND: Use Nouveau. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 Uname: Linux 3.10.54 x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 331.89 Tue Jul 1 13:30:18 PDT 2014 GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Sep 8 00:37:22 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Since before I upgraded GraphicsCard: NVIDIA Corporation GF114M [GeForce GTX 580M] [10de:1211] (rev a1) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Device [1558:5102] InstallationDate: Installed on 2014-06-14 (85 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) MachineType: CLEVO P150HMx ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.10.54 root=UUID=727896fd-6717-4299-ad41-e259af78a16f ro quiet debug intel_pstate=disable pcie_aspm=default pcie_pme=nomsi acpi.debug_layer=0x2 acpi.debug_level=0x pci=nocrs SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/09/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.4 dmi.board.asset.tag: Not Applicable dmi.board.name: P150HMx dmi.board.vendor: CLEVO dmi.board.version: Not Applicable dmi.chassis.asset.tag: Not Applicable dmi.chassis.type: 10 dmi.chassis.vendor: CLEVO dmi.chassis.version: Not Applicable dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.4:bd08/09/2011:svnCLEVO:pnP150HMx:pvrNotApplicable:rvnCLEVO:rnP150HMx:rvrNotApplicable:cvnCLEVO:ct10:cvrNotApplicable: dmi.product.name: P150HMx dmi.product.version: Not Applicable dmi.sys.vendor: CLEVO version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Mon Sep 8 00:30:25 2014 xserver.configfile: /etc/X11/xorg.conf xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.15.1-0ubuntu2.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/131/+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 1285783] Re: Right panel has a transparent background
** Changed in: gtk+3.0 (Ubuntu) Status: Triaged = Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1285783 Title: Right panel has a transparent background Status in gtk+3.0 package in Ubuntu: Invalid Status in ubuntu-themes package in Ubuntu: Fix Released Bug description: Launching gnome-tweak-tool and choosing a category on the left panel makes the right panel transparent. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1285783/+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 797775] Re: gedit crashed with SIGSEGV in g_file_equal()
** Changed in: gtk+3.0 (Ubuntu) Status: Triaged = Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/797775 Title: gedit crashed with SIGSEGV in g_file_equal() Status in GTK+ GUI Toolkit: Expired Status in gtk+3.0 package in Ubuntu: Invalid Bug description: Binary package hint: gedit Not easily reproducible. I was trying to reproduce bug 797443 and playing with the folder buttons of the Save As... dialog, 2 buttons where highlighted at the same time (I haven't found a way to reproduce how yet) and then this crash. --- Ubuntu Bug Squad volunteer triager http://wiki.ubuntu.com/BugSquad ProblemType: Crash DistroRelease: Ubuntu 11.10 Package: gedit 3.0.4-0ubuntu2 ProcVersionSignature: Ubuntu 3.0-0.1-generic 3.0.0-rc2 Uname: Linux 3.0-0-generic i686 Architecture: i386 Date: Wed Jun 15 17:18:26 2011 EcryptfsInUse: Yes ExecutablePath: /usr/bin/gedit ProcCmdline: gedit ProcEnviron: SHELL=/bin/bash PATH=(custom, no user) LC_MESSAGES=en_US.utf8 LANG=en_US.utf8 LANGUAGE=en_US:en SegvAnalysis: Segfault happened at: 0x784182 g_file_equal+146: mov(%edx),%ecx PC (0x00784182) ok source (%edx) (0x0001) not located in a known VMA region (needed readable region)! destination %ecx ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gedit StacktraceTop: g_file_equal (file1=0x9a850b0, file2=0xb09e0d40) at /build/buildd/glib2.0-2.29.8/./gio/gfile.c:585 ?? () from /usr/lib/libgtk-3.so.0 ?? () from /usr/lib/libgtk-3.so.0 ?? () from /usr/lib/libgtk-3.so.0 g_simple_async_result_complete (simple=0x9af1d00) at /build/buildd/glib2.0-2.29.8/./gio/gsimpleasyncresult.c:749 Title: gedit crashed with SIGSEGV in g_file_equal() UpgradeStatus: Upgraded to oneiric on 2011-05-16 (29 days ago) UserGroups: adm admin audio cdrom dialout dip floppy fuse libvirtd lpadmin netdev plugdev scanner sudo video To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/797775/+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 1423542] Re: regresion: buttons styled differently
** Branch linked: lp:ubuntu/vivid-proposed/unity-greeter -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1423542 Title: regresion: buttons styled differently Status in ubuntu-themes package in Ubuntu: Fix Released Status in unity-greeter package in Ubuntu: In Progress Bug description: Unity greeter buttons are styled differently compared to previus ubuntu version: 1) Session option button has background-color and border. 2) All buttons look similar in session chooser. It is not possible to see currently selected session. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1423542/+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 440527] Re: evolution crashed with SIGSEGV in g_closure_invoke()
** Changed in: gtk+3.0 (Ubuntu) Status: Triaged = Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/440527 Title: evolution crashed with SIGSEGV in g_closure_invoke() Status in The Evolution Mail Calendaring Tool: Invalid Status in GTK+ GUI Toolkit: Expired Status in gtk+3.0 package in Ubuntu: Invalid Bug description: Binary package hint: evolution I was not actively using evolution when it crashed, no idea how to reproduce. ProblemType: Crash Architecture: amd64 Date: Fri Oct 2 14:39:29 2009 DistroRelease: Ubuntu 9.10 ExecutablePath: /usr/bin/evolution Package: evolution 2.28.0-0ubuntu2 ProcCmdline: evolution --component=mail ProcEnviron: PATH=(custom, user) LANG=fi_FI.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-11.36-generic SegvAnalysis: Segfault happened at: 0x7ffeb442faa8:mov(%rax),%edx PC (0x7ffeb442faa8) ok source (%rax) (0x) not located in a known VMA region (needed readable region)! destination %edx ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: evolution StacktraceTop: ?? () from /usr/lib/libgtk-x11-2.0.so.0 ?? () from /usr/lib/libgtk-x11-2.0.so.0 g_closure_invoke () ?? () from /usr/lib/libgobject-2.0.so.0 g_signal_emit_valist () Title: evolution crashed with SIGSEGV in g_closure_invoke() Uname: Linux 2.6.31-11-generic x86_64 UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/evolution/+bug/440527/+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 1432843] Re: Lubuntu failed to boot
Now Lubuntu Vivid i386 desktop iso works in my old Dell with P4 and nvidia Riva too, http://support.dell.com/support/edocs/systems/dim4600/en/4600i/sm/specs.htm The installed system with this extra video package boots and runs 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/1432843 Title: Lubuntu failed to boot Status in X.Org X server: Confirmed Status in lubuntu-meta package in Ubuntu: Triaged Status in xorg package in Ubuntu: Triaged Bug description: The daily build of Lubuntu 20150316 failed to boot into the live session, and fails to install. During the boot session, the Lubuntu splash screen appears indicating that Lubuntu was loading. What follows next was a blank screen. Unfortunately, I cannot sumit the exact version of syslinux since the daily build could not boot into an interactive session. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: syslinux 3:6.03~pre18+dfsg-1ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0 Uname: Linux 3.19.0-7-generic i686 ApportVersion: 2.16.2-0ubuntu1 Architecture: i386 Date: Mon Mar 16 17:19:35 2015 Dependencies: gcc-5-base 5-20150228-1ubuntu1 libc6 2.19-15ubuntu2 libgcc1 1:5-20150228-1ubuntu1 mtools 4.0.18-2 multiarch-support 2.19-15ubuntu2 InstallationDate: Installed on 2015-03-05 (11 days ago) InstallationMedia: Lubuntu 15.04 Vivid Vervet - Alpha i386 (20150303) SourcePackage: syslinux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1432843/+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 1442508] Re: /usr/sbin/unity-system-compositor:11:Add:add_surface_pixel_format:mir::frontend::SessionMediator::connect:mir::frontend::detail::invoke:mir::frontend::detail::Protob
** Also affects: mir Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-system-compositor in Ubuntu. https://bugs.launchpad.net/bugs/1442508 Title: /usr/sbin/unity-system- compositor:11:Add:add_surface_pixel_format:mir::frontend::SessionMediator::connect:mir::frontend::detail::invoke:mir::frontend::detail::ProtobufMessageProcessor::dispatch Status in Mir: New Status in unity-system-compositor package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding unity-system-compositor. This problem was most recently seen with version 0.0.5+15.04.20150227-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/009ff218f16e78b57614e9a3a0e4ddae9cb0750a contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1442508/+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 1443872] Re: qmlplugindump crashed with SIGABRT in oxide::qt::WebViewAdapter::context()
*** This bug is a duplicate of bug 1419616 *** https://bugs.launchpad.net/bugs/1419616 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1419616, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: CoreDump.gz https://bugs.launchpad.net/bugs/1443872/+attachment/4374938/+files/CoreDump.gz ** Attachment removed: Disassembly.txt https://bugs.launchpad.net/bugs/1443872/+attachment/4374940/+files/Disassembly.txt ** Attachment removed: ProcMaps.txt https://bugs.launchpad.net/bugs/1443872/+attachment/4374942/+files/ProcMaps.txt ** Attachment removed: ProcStatus.txt https://bugs.launchpad.net/bugs/1443872/+attachment/4374943/+files/ProcStatus.txt ** Attachment removed: Registers.txt https://bugs.launchpad.net/bugs/1443872/+attachment/4374944/+files/Registers.txt ** Attachment removed: Stacktrace.txt https://bugs.launchpad.net/bugs/1443872/+attachment/4374945/+files/Stacktrace.txt ** Attachment removed: ThreadStacktrace.txt https://bugs.launchpad.net/bugs/1443872/+attachment/4374946/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1419616 qmlplugindump crashed with SIGABRT in oxide::WebView::GetBrowserContext() ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtdeclarative-opensource- src in Ubuntu. https://bugs.launchpad.net/bugs/1443872 Title: qmlplugindump crashed with SIGABRT in oxide::qt::WebViewAdapter::context() Status in qtdeclarative-opensource-src package in Ubuntu: New Bug description: ubuntu sdk on ubuntu linux 15.04 amd64 ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: qtdeclarative5-dev-tools 5.4.1-1ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3 Uname: Linux 3.19.0-12-generic x86_64 ApportVersion: 2.17-0ubuntu2 Architecture: amd64 CrashCounter: 1 CurrentDesktop: Unity Date: Tue Apr 14 12:21:54 2015 ExecutablePath: /usr/lib/x86_64-linux-gnu/qt5/bin/qmlplugindump InstallationDate: Installed on 2015-04-07 (6 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Beta amd64 (20150326) ProcCmdline: /usr/lib/x86_64-linux-gnu/qt5/bin/qmlplugindump -relocatable com.canonical.Oxide 1.3 /usr/lib/x86_64-linux-gnu/qt5/qml ProcEnviron: XDG_RUNTIME_DIR=set SHELL=/bin/bash LANG=de_DE.UTF-8 PATH=(custom, no user) LANGUAGE=de_DE Signal: 6 SourcePackage: qtdeclarative-opensource-src StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libOxideQtCore.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libOxideQtCore.so.0 oxide::qt::WebViewAdapter::context() const () from /usr/lib/x86_64-linux-gnu/libOxideQtCore.so.0 OxideQQuickWebView::~OxideQQuickWebView() () from /usr/lib/x86_64-linux-gnu/libOxideQtQuick.so.0 QQmlPrivate::QQmlElementOxideQQuickWebView::~QQmlElement() () from /usr/lib/x86_64-linux-gnu/qt5/qml/com/canonical/Oxide/libqmloxideplugin.so Title: qmlplugindump crashed with SIGABRT in oxide::qt::WebViewAdapter::context() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm autopilot cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1443872/+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 1426347] Re: [browser] In landscape mode (phone), the app should go full screen
uh, pretty please make this optional i definitely want to be able to see my panel in landscape ... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1426347 Title: [browser] In landscape mode (phone), the app should go full screen Status in Ubuntu UX bugs: Fix Committed Status in Web Browser App: In Progress Status in webbrowser-app package in Ubuntu: New Bug description: In landscape mode (on the phone form factor) there is a limited real estate available, therefore it is beneficial to go full screen and free up valuable space for the content. On tablet FFs this is not an issue and the behaviour should be the default (i.e. indicators are shown) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1426347/+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 998285] Re: Tapping alt-tab switches between windows of the same application sometimes
** Changed in: unity Status: In Progress = Fix Committed ** Also affects: unity/7.2 Importance: Undecided Status: New ** Changed in: unity/7.2 Importance: Undecided = Medium ** Changed in: unity/7.2 Status: New = Triaged ** Changed in: unity/7.2 Milestone: None = 7.2.5 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/998285 Title: Tapping alt-tab switches between windows of the same application sometimes Status in Unity: Fix Committed Status in Unity 7.2 series: Triaged Status in unity package in Ubuntu: Fix Released Bug description: Normally, tapping alt-tab switches between applications, and tapping alt-` switches between windows of the front-most application. However, if the two front-most windows are from the same application, then alt- tab will switch between these windows instead, instead of moving to the second-front-most application. Hence, in this case, alt-tab duplicates the action of alt-`. Here is an example: 1) create the stack with two nautilus windows at the top, e.g. Nautilus window 1 (N1), Nautilus window 2 (N2), and Firefox window (F1) (but you can use any applications). Create the stack either by [clicking F1, N2, N1] or [switching to Nautilus with alt-tab, then alt-` to the other Nautilus window]. 2) Tap alt-tab. What happens: I switch to the other nautilus window. What I expected: to switch to the other application (i.e. Firefox). ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: unity 5.12-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14 Uname: Linux 3.2.0-24-generic x86_64 ApportVersion: 2.0.1-0ubuntu7 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] Date: Sat May 12 10:17:21 2012 InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) SourcePackage: unity UpgradeStatus: Upgraded to precise on 2012-04-29 (12 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/998285/+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 1443944] Re: indicator-sound-service crashed with signal 5 in indicator_sound_service_construct()
*** This bug is a duplicate of bug 1432446 *** https://bugs.launchpad.net/bugs/1432446 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1432446, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: CoreDump.gz https://bugs.launchpad.net/bugs/1443944/+attachment/4375180/+files/CoreDump.gz ** Attachment removed: Disassembly.txt https://bugs.launchpad.net/bugs/1443944/+attachment/4375182/+files/Disassembly.txt ** Attachment removed: ProcMaps.txt https://bugs.launchpad.net/bugs/1443944/+attachment/4375184/+files/ProcMaps.txt ** Attachment removed: ProcStatus.txt https://bugs.launchpad.net/bugs/1443944/+attachment/4375185/+files/ProcStatus.txt ** Attachment removed: Registers.txt https://bugs.launchpad.net/bugs/1443944/+attachment/4375186/+files/Registers.txt ** Attachment removed: Stacktrace.txt https://bugs.launchpad.net/bugs/1443944/+attachment/4375187/+files/Stacktrace.txt ** Attachment removed: ThreadStacktrace.txt https://bugs.launchpad.net/bugs/1443944/+attachment/4375188/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1432446 indicator-sound-service crashed with signal 5 in indicator_sound_service_construct() ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-sound in Ubuntu. https://bugs.launchpad.net/bugs/1443944 Title: indicator-sound-service crashed with signal 5 in indicator_sound_service_construct() Status in indicator-sound package in Ubuntu: New Bug description: not in the list, constant crash on restart. Does not seem to affect anything, except the annoying message of a crash on startup. Using audio over HDMI with Amd HD Crossfire motherboard. ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: indicator-sound 12.10.2+15.04.20150413-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-13.13-generic 3.19.3 Uname: Linux 3.19.0-13-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17-0ubuntu2 Architecture: amd64 CrashCounter: 1 Date: Tue Apr 14 08:10:44 2015 ExecutablePath: /usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service InstallationDate: Installed on 2015-04-01 (12 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140731) ProcCmdline: /usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/false Signal: 5 SourcePackage: indicator-sound StacktraceTop: indicator_sound_service_construct () ?? () ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 g_simple_async_result_complete () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: indicator-sound-service crashed with signal 5 in indicator_sound_service_construct() UpgradeStatus: Upgraded to vivid on 2015-04-01 (12 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1443944/+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 1436043] Re: contacts can not be imported from sd card
*** This bug is a duplicate of bug 1331346 *** https://bugs.launchpad.net/bugs/1331346 ** This bug has been marked a duplicate of bug 1331346 [address book] No access to contacts on SIM -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to address-book-app in Ubuntu. https://bugs.launchpad.net/bugs/1436043 Title: contacts can not be imported from sd card Status in Usability Bugs in Ubuntu Phone: New Status in address-book-app package in Ubuntu: Confirmed Bug description: There is no way to import a *.vcf File into Contacts from a SD-Card. If you email the *.vcf to Dekko and open the Attachment you will be asked to import the *.vcf to contacts. There should be a easy way to import vcf-Files from a SD-Card. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntuphone/+bug/1436043/+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 1437538] Re: Battery Applet appears in English with Gnome in Ubuntu 12.04
Please try with newer ubuntu version and report if this is still problem. Sorry, this won't be fixed in 12.04... ** Changed in: indicator-power (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1437538 Title: Battery Applet appears in English with Gnome in Ubuntu 12.04 Status in indicator-power package in Ubuntu: Incomplete Bug description: Use Ubuntu 12.04 on a Toshiba NB500. I use the Gnome desktop environment, but I found a bug: The battery applet appears in English, but with Unity appears in Spanish, but I still use Gnome !. So I ask you traduzcais battery applet to Spanish. If you ask me I missing some information. a greeting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1437538/+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 1330770] Re: click packages rely upon tls for integrity and authenticity
** Changed in: canonical-devices-system-image Assignee: Ricardo Salveti (rsalveti) = Canonical Phone Foundations (canonical-phonedations-team) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to click in Ubuntu. https://bugs.launchpad.net/bugs/1330770 Title: click packages rely upon tls for integrity and authenticity Status in the base for Ubuntu mobile products: In Progress Status in Click Package metadata search service: Fix Released Status in Online service used by software center: Fix Released Status in click package in Ubuntu: Fix Released Status in ubuntu-download-manager package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: In Progress Status in unity-scope-click package in Ubuntu: Fix Released Bug description: Hello, I just completed a quick review of the click source and the unity-scope-click source and behaviours, and found some opportunities for improvement. Debian, and Ubuntu, rely upon signed repository files with cryptographic hashes of packages to provide both integrity and authenticity checks for the packages hosted on that repository. The click framework and the unity-scope-click discovery and installation tool do not use signed repository files, nor do they have signatures of any sort on downloaded packages. The only integrity and authenticity checks are provided by the use of HTTPS. The click verify command will check files within the archive against MD5sums stored inside the archive but the click verify command is not used during package installation. (This is suitable for validating integrity against accidental changes only.) While it appears that unity-scope-click properly uses HTTPS to download package metadata and packages, HTTPS alone is insufficient for our needs: - Someone in a position to create new certificates at any of several hundred certificate authorities could create certificates purporting to be our update servers. This actual problem has been discovered in the wild with several certificate authorities issuing wild-card certificates or even certificates with signing authority. - X.509 is extremely complicated; TLS is extremely complicated. Flaws in both are inevitable. - HTTPS prevents the use of caching. - HTTPS only 'works' for data-in-motion; it is useless for data-at- rest integrity and authenticity checks. I have not yet reviewed the tools that application authors will use to upload their packages to our distribution servers but note in passing that most of these issues are also issues for adding packages to our update servers -- packages in flight within our network can be corrupted for many reasons, packages on disk can be corrupted for many reasons. A signature mechanism can protect against internal network faults, storage faults, and provide assurance months or years later that an uploaded package was uploaded by someone in control of a corresponding private key. Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1330770/+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 1438758] Re: User to root privilege escalation (ab)using the crash forwarding feature of apport
** Information type changed from Private Security to Public Security -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1438758 Title: User to root privilege escalation (ab)using the crash forwarding feature of apport Status in Apport crash detection/reporting: In Progress Status in apport package in Ubuntu: Triaged Status in apport source package in Trusty: Triaged Status in apport source package in Utopic: Triaged Status in apport source package in Vivid: Triaged Status in apport package in Debian: New Bug description: Back in Ubuntu 14.04, I introduced an apport feature that will have it forward any crash to another apport running in the task's namespace (in the case where the pid of the task in its namespace isn't equal to that in the host namespace). This feature simply checks for the presence of /usr/share/apport/apport in the task's root directory. If it exists, it will chroot and exec the script. The problem is that as apport is a coredump handler triggered by the kernel, it'll always run as real root, regardless of the crashed task's owner and namespace. This therefore allows an unprivileged user to craft a specific filesystem structure, pivot_root to it, then crash a process inside it, causing apport outside of the namespace to execute a script as real root. By bind-mounting /proc from the host into that namespace, the unprivileged user can then access any file on the host as real root, causing the privilege escalation. An exploit is attached to this bug. It's been confirmed to be runnable as a nobody user on a regular Ubuntu system and to successfully read any file on the host. To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1438758/+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 1410582] Re: [Trusty / Unity] Desktop got unlocked on its own.
** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1410582 Title: [Trusty / Unity] Desktop got unlocked on its own. Status in Unity: Fix Released Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Fix Released Status in unity source package in Trusty: Fix Committed Bug description: [Impact] Certain code paths may cause the Unity lockscreen to crash, which can allow the screen to be unlocked without a password entry. [Test Case] Unfortunately this bug only appears under certain race conditions and is not reliably reproduce able. [Regression Potential] The change in the code simply assumes that if a screen is already locked, then it is lockable this avoiding certain operations that are inherently racy. It is possible that this fix does not avoid all possible crash conditions in the lockscreen and there may still be unaccounted-for crashes in the lockscreen. [Other Info] This fix was cherry picked for Ubuntu 14.04 LTS from the Ubuntu Vivid Vervet dev release where it has been in testing for some time. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1410582/+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 1444054] [NEW] Symbolic links are never removed from /tmp with TMPTIME0
Public bug reported:
With TMPTIME set to anything other than 0 in /etc/default/rcS the init
script has to find files to remove rather than simply wiping /tmp. This
fails to remove symbolic links.
lrwxrwxrwx 1 1001 1001 12 Mar 20 02:01 test2.jpg - download.jpg
lrwxrwxrwx 1 1001 10013 Mar 20 02:04 beh - meh
$ file beh
beh: broken symbolic link to `meh'
$ file test2.jpg
test2.jpg: broken symbolic link to `download.jpg'
My TMPTIME is set to 3 but these two files are well over a month old.
The script uses find but this seems to find the files no problem:
$ find . ! -type d 2- | egrep beh|test2
./beh
./test2.jpg
Tests using find . ! -type d -delete show find removing symbolic
links both working and broken.
My syslog does show this during boot:
kernel: [ 723.500519] type=1302 audit(1429024710.712:73): item=0
name=/tmp/beh inode=221577 dev=08:05 mode=0120777 ouid=1001 ogid=1001
rdev=00:00 nametype=NORMAL
This seems to be updating the atime, and the atime is used in the
expression:
TEXPR=-mtime +${TMPTIME} -ctime +${TMPTIME} -atime +${TMPTIME}
The result being that symbolic links will, apparently, never be removed.
I have no idea what is updating the atime for these symbolic links or
why it is being audited. It's nothing I have intentionally set up on
this system. It may be that the script is not at fault here but whatever
package is updating the atime on these files.
A temporary solution would be to have a separate expression just for
symbolic links ignoring the atime, but this may not be what a user
wants. However: I can think of no good reason why anyone would need a
symbolic link hanging around /tmp for longer than the TMPTIME.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: initscripts 2.88dsf-13.10ubuntu11.1
ProcVersionSignature: Ubuntu 3.11.0-26.45~precise1-generic 3.11.10.12
Uname: Linux 3.11.0-26-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 2.0.1-0ubuntu17.8
Architecture: i386
Date: Tue Apr 14 16:46:52 2015
MarkForUpload: True
ProcEnviron:
LANGUAGE=en_GB:en
TERM=xterm
PATH=(custom, no user)
LANG=en_GB.UTF-8
SHELL=/bin/bash
SourcePackage: sysvinit
UpgradeStatus: Upgraded to precise on 2014-12-07 (128 days ago)
** Affects: sysvinit (Ubuntu)
Importance: Undecided
Status: New
** Tags: apport-bug i386 precise
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sysvinit in Ubuntu.
https://bugs.launchpad.net/bugs/1444054
Title:
Symbolic links are never removed from /tmp with TMPTIME0
Status in sysvinit package in Ubuntu:
New
Bug description:
With TMPTIME set to anything other than 0 in /etc/default/rcS the init
script has to find files to remove rather than simply wiping /tmp.
This fails to remove symbolic links.
lrwxrwxrwx 1 1001 1001 12 Mar 20 02:01 test2.jpg - download.jpg
lrwxrwxrwx 1 1001 10013 Mar 20 02:04 beh - meh
$ file beh
beh: broken symbolic link to `meh'
$ file test2.jpg
test2.jpg: broken symbolic link to `download.jpg'
My TMPTIME is set to 3 but these two files are well over a month old.
The script uses find but this seems to find the files no problem:
$ find . ! -type d 2- | egrep beh|test2
./beh
./test2.jpg
Tests using find . ! -type d -delete show find removing symbolic
links both working and broken.
My syslog does show this during boot:
kernel: [ 723.500519] type=1302 audit(1429024710.712:73): item=0
name=/tmp/beh inode=221577 dev=08:05 mode=0120777 ouid=1001
ogid=1001 rdev=00:00 nametype=NORMAL
This seems to be updating the atime, and the atime is used in the
expression:
TEXPR=-mtime +${TMPTIME} -ctime +${TMPTIME} -atime +${TMPTIME}
The result being that symbolic links will, apparently, never be
removed.
I have no idea what is updating the atime for these symbolic links or
why it is being audited. It's nothing I have intentionally set up on
this system. It may be that the script is not at fault here but
whatever package is updating the atime on these files.
A temporary solution would be to have a separate expression just for
symbolic links ignoring the atime, but this may not be what a user
wants. However: I can think of no good reason why anyone would need a
symbolic link hanging around /tmp for longer than the TMPTIME.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: initscripts 2.88dsf-13.10ubuntu11.1
ProcVersionSignature: Ubuntu 3.11.0-26.45~precise1-generic 3.11.10.12
Uname: Linux 3.11.0-26-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 2.0.1-0ubuntu17.8
Architecture: i386
Date: Tue Apr 14 16:46:52 2015
MarkForUpload: True
ProcEnviron:
LANGUAGE=en_GB:en
TERM=xterm
PATH=(custom, no user)
LANG=en_GB.UTF-8
SHELL=/bin/bash
SourcePackage: sysvinit
UpgradeStatus: Upgraded to precise on 2014-12-07 (128 days ago)
To manage notifications about this bug go to:
[Touch-packages] [Bug 1443853] Re: Ubuntu 14.10 ISO live boot in Oracle VirtualBox ends up with a corrupted display
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: console-setup (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kbd in Ubuntu. https://bugs.launchpad.net/bugs/1443853 Title: Ubuntu 14.10 ISO live boot in Oracle VirtualBox ends up with a corrupted display Status in Virtualbox: New Status in console-setup package in Ubuntu: Confirmed Status in kbd package in Ubuntu: Confirmed Status in virtualbox package in Ubuntu: Confirmed Bug description: (Content copied from Ubuntu 14.10 ISO live boot ends up with a corrupted display #13615 VirtualBox bug ticket, by piotrjurkiewicz) Booting up live session of Ubuntu MATE 14.10 and Ubuntu Gnome 14.10 from ISO ends up with a corrupted screen. See the screenshot: https://launchpadlibrarian.net/186864347/ubu.png Switching back and forth to the tty7 (ctrl+alt+F1 and then alt+F7) fixes the display. I think that this might be a problem with resolution setting: ``` 00:00:31.226379 Display::handleDisplayResize(): uScreenId = 0, pvVRAM= w=1152 h=400 bpp=0 cbLine=0x0, flags=0x1 00:00:31.226399 UIFrameBuffer::RequestResize: Screen=0, Format=0, BitsPerPixel=0, BytesPerLine=0, Size=1152x400, Sending to async-handler.. 00:00:31.226457 UIFrameBufferQImage::resizeEvent: Format=0, BitsPerPixel=0, BytesPerLine=0, Size=1152x400 00:00:31.226467 UIFrameBufferQImage::resizeEvent: Resizing to FALLBACK buffer due to format is invalid.. ``` After switching back and forth to the tty7 (what fixes the display) the log says: ``` 00:00:31.226379 Display::handleDisplayResize(): uScreenId = 0, pvVRAM= w=1152 h=400 bpp=0 cbLine=0x0, flags=0x1 00:00:31.226399 UIFrameBuffer::RequestResize: Screen=0, Format=0, BitsPerPixel=0, BytesPerLine=0, Size=1152x400, Sending to async-handler.. 00:00:31.226457 UIFrameBufferQImage::resizeEvent: Format=0, BitsPerPixel=0, BytesPerLine=0, Size=1152x400 00:00:31.226467 UIFrameBufferQImage::resizeEvent: Resizing to FALLBACK buffer due to format is invalid.. 00:01:37.584616 Display::handleDisplayResize(): uScreenId = 0, pvVRAM= w=720 h=400 bpp=0 cbLine=0x0, flags=0x1 00:01:37.584634 UIFrameBuffer::RequestResize: Screen=0, Format=0, BitsPerPixel=0, BytesPerLine=0, Size=720x400, Sending to async-handler.. 00:01:37.584680 UIFrameBufferQImage::resizeEvent: Format=0, BitsPerPixel=0, BytesPerLine=0, Size=720x400 00:01:37.584692 UIFrameBufferQImage::resizeEvent: Resizing to FALLBACK buffer due to format is invalid.. 00:01:39.055475 Display::handleDisplayResize(): uScreenId = 0, pvVRAM=0a7f w=1024 h=768 bpp=32 cbLine=0x1000, flags=0x1 00:01:39.055495 UIFrameBuffer::RequestResize: Screen=0, Format=843204434, BitsPerPixel=32, BytesPerLine=4096, Size=1024x768, Sending to async-handler.. 00:01:39.09 UIFrameBufferQImage::resizeEvent: Format=843204434, BitsPerPixel=32, BytesPerLine=4096, Size=1024x768 00:01:39.055568 UIFrameBufferQImage::resizeEvent: Resizing to directly use VGA device content.. ``` I have tested 4.3.18 and also the testbuild 4.3.19 r96825, it happens on both of them. You can download the ISO images of these two systems here: https://ubuntu-mate.r.worldssl.net/download/ubuntu-mate-14.10 -desktop-amd64.iso http://cdimage.ubuntu.com/ubuntu-gnome/releases/14.10/release/ubuntu- gnome-14.10-desktop-amd64.iso To manage notifications about this bug go to: https://bugs.launchpad.net/virtualbox/+bug/1443853/+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 1443853] Re: Ubuntu 14.10 ISO live boot in Oracle VirtualBox ends up with a corrupted display
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: kbd (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kbd in Ubuntu. https://bugs.launchpad.net/bugs/1443853 Title: Ubuntu 14.10 ISO live boot in Oracle VirtualBox ends up with a corrupted display Status in Virtualbox: New Status in console-setup package in Ubuntu: Confirmed Status in kbd package in Ubuntu: Confirmed Status in virtualbox package in Ubuntu: Confirmed Bug description: (Content copied from Ubuntu 14.10 ISO live boot ends up with a corrupted display #13615 VirtualBox bug ticket, by piotrjurkiewicz) Booting up live session of Ubuntu MATE 14.10 and Ubuntu Gnome 14.10 from ISO ends up with a corrupted screen. See the screenshot: https://launchpadlibrarian.net/186864347/ubu.png Switching back and forth to the tty7 (ctrl+alt+F1 and then alt+F7) fixes the display. I think that this might be a problem with resolution setting: ``` 00:00:31.226379 Display::handleDisplayResize(): uScreenId = 0, pvVRAM= w=1152 h=400 bpp=0 cbLine=0x0, flags=0x1 00:00:31.226399 UIFrameBuffer::RequestResize: Screen=0, Format=0, BitsPerPixel=0, BytesPerLine=0, Size=1152x400, Sending to async-handler.. 00:00:31.226457 UIFrameBufferQImage::resizeEvent: Format=0, BitsPerPixel=0, BytesPerLine=0, Size=1152x400 00:00:31.226467 UIFrameBufferQImage::resizeEvent: Resizing to FALLBACK buffer due to format is invalid.. ``` After switching back and forth to the tty7 (what fixes the display) the log says: ``` 00:00:31.226379 Display::handleDisplayResize(): uScreenId = 0, pvVRAM= w=1152 h=400 bpp=0 cbLine=0x0, flags=0x1 00:00:31.226399 UIFrameBuffer::RequestResize: Screen=0, Format=0, BitsPerPixel=0, BytesPerLine=0, Size=1152x400, Sending to async-handler.. 00:00:31.226457 UIFrameBufferQImage::resizeEvent: Format=0, BitsPerPixel=0, BytesPerLine=0, Size=1152x400 00:00:31.226467 UIFrameBufferQImage::resizeEvent: Resizing to FALLBACK buffer due to format is invalid.. 00:01:37.584616 Display::handleDisplayResize(): uScreenId = 0, pvVRAM= w=720 h=400 bpp=0 cbLine=0x0, flags=0x1 00:01:37.584634 UIFrameBuffer::RequestResize: Screen=0, Format=0, BitsPerPixel=0, BytesPerLine=0, Size=720x400, Sending to async-handler.. 00:01:37.584680 UIFrameBufferQImage::resizeEvent: Format=0, BitsPerPixel=0, BytesPerLine=0, Size=720x400 00:01:37.584692 UIFrameBufferQImage::resizeEvent: Resizing to FALLBACK buffer due to format is invalid.. 00:01:39.055475 Display::handleDisplayResize(): uScreenId = 0, pvVRAM=0a7f w=1024 h=768 bpp=32 cbLine=0x1000, flags=0x1 00:01:39.055495 UIFrameBuffer::RequestResize: Screen=0, Format=843204434, BitsPerPixel=32, BytesPerLine=4096, Size=1024x768, Sending to async-handler.. 00:01:39.09 UIFrameBufferQImage::resizeEvent: Format=843204434, BitsPerPixel=32, BytesPerLine=4096, Size=1024x768 00:01:39.055568 UIFrameBufferQImage::resizeEvent: Resizing to directly use VGA device content.. ``` I have tested 4.3.18 and also the testbuild 4.3.19 r96825, it happens on both of them. You can download the ISO images of these two systems here: https://ubuntu-mate.r.worldssl.net/download/ubuntu-mate-14.10 -desktop-amd64.iso http://cdimage.ubuntu.com/ubuntu-gnome/releases/14.10/release/ubuntu- gnome-14.10-desktop-amd64.iso To manage notifications about this bug go to: https://bugs.launchpad.net/virtualbox/+bug/1443853/+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 1444002] Re: [launcher] visual feedback from tap/click on app icon is inconsistent between app scope and launcher
** No longer affects: ubuntu-ux ** Changed in: unity8 (Ubuntu) Status: New = Triaged ** Changed in: unity8 (Ubuntu) Importance: Undecided = Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1444002 Title: [launcher] visual feedback from tap/click on app icon is inconsistent between app scope and launcher Status in unity8 package in Ubuntu: Triaged Bug description: Clicking/tapping an app icon is not the same in the launcher and in the app scope. This is confusing. $ system-image-cli -i current build number: 127 device name: m75 channel: ubuntu-touch/vivid-proposed last update: 2015-03-10 16:26:39 version version: 127 Steps to reproduce: 1. Open launcher 2. Click or tap an open or closed application. What happens: There's no visual feedback on the button (app icon) What should happen instead: There should be a feedback on the button (app icon) as there is in the app scope. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1444002/+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 1415974] Re: Cleaning a directory in /tmp during boot updates the directory's modification time
Indeed the script shows that the directory's mtime is checked after the
files have been removed:
DEXPR=-mtime +${TMPTIME} -ctime +${TMPTIME}
find . -depth -xdev $DEXPR $EXCEPT -type d -empty -delete
** Package changed: sysvinit (Ubuntu) = mountall (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sysvinit in Ubuntu.
https://bugs.launchpad.net/bugs/1415974
Title:
Cleaning a directory in /tmp during boot updates the directory's
modification time
Status in mountall package in Ubuntu:
New
Bug description:
When TMPTIME is set to anything other than 0 (clean all of /tmp) in
/etc/default/rcS, /tmp is cleaned of old files, but in doing so it
updates the modification times of all the directories, so that they
remain until they themselves become old.
I hope this makes sense, an example:
During boot files in /tmp older than three days will be cleaned.
Files in /tmp/olddir will be cleaned.
/tmp/olddir will have its modification time updated, it is no longer an old
directory.
/tmp/olddir is left behind because it is not recognised as an old directory.
It's minor and may be impossible to fix, but is there any magic that
can be done to remove the old directories at boot rather than waiting
for the directory to expire again? Is it possible to avoid the
modification time being updated?
Simply removing the whole directory based on its creation or
modification times, without first checking its contents for newer
files, would probably not be preferable.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: initscripts 2.88dsf-13.10ubuntu11.1
ProcVersionSignature: Ubuntu 3.11.0-26.45~precise1-generic 3.11.10.12
Uname: Linux 3.11.0-26-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 2.0.1-0ubuntu17.8
Architecture: i386
Date: Thu Jan 29 15:13:27 2015
MarkForUpload: True
ProcEnviron:
LANGUAGE=en_GB:en
TERM=xterm
PATH=(custom, no user)
LANG=en_GB.UTF-8
SHELL=/bin/bash
SourcePackage: sysvinit
UpgradeStatus: Upgraded to precise on 2014-12-07 (53 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1415974/+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 1443778] Re: [Inspiron 3420, Intel PantherPoint HDMI, Digital Out, HDMI] No sound at all
** Changed in: alsa-driver (Ubuntu) Status: New = Incomplete -- 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/1443778 Title: [Inspiron 3420, Intel PantherPoint HDMI, Digital Out, HDMI] No sound at all Status in alsa-driver package in Ubuntu: Incomplete Bug description: there are no sound in the external speakers and ye HDMI out is shut down ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-49.81-generic 3.13.11-ckt17 Uname: Linux 3.13.0-49-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: cabelo 2034 F pulseaudio CurrentDesktop: Unity Date: Tue Apr 14 03:49:47 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2015-02-04 (68 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Áudio interno - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: cabelo 2034 F pulseaudio Symptom_Jack: Digital Out, HDMI Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: No sound at all Title: [Inspiron 3420, Intel PantherPoint HDMI, Digital Out, HDMI] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/28/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 04XGDT dmi.board.vendor: Dell Inc. dmi.board.version: A05 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA05:bd09/28/2012:svnDellInc.:pnInspiron3420:pvrNotSpecified:rvnDellInc.:rn04XGDT:rvrA05:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 3420 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1443778/+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 1438758] Re: User to root privilege escalation (ab)using the crash forwarding feature of apport
** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1438758 Title: User to root privilege escalation (ab)using the crash forwarding feature of apport Status in Apport crash detection/reporting: Fix Released Status in apport package in Ubuntu: Fix Committed Status in apport source package in Trusty: Fix Released Status in apport source package in Utopic: Fix Released Status in apport source package in Vivid: Fix Committed Status in apport package in Debian: New Bug description: Back in Ubuntu 14.04, I introduced an apport feature that will have it forward any crash to another apport running in the task's namespace (in the case where the pid of the task in its namespace isn't equal to that in the host namespace). This feature simply checks for the presence of /usr/share/apport/apport in the task's root directory. If it exists, it will chroot and exec the script. The problem is that as apport is a coredump handler triggered by the kernel, it'll always run as real root, regardless of the crashed task's owner and namespace. This therefore allows an unprivileged user to craft a specific filesystem structure, pivot_root to it, then crash a process inside it, causing apport outside of the namespace to execute a script as real root. By bind-mounting /proc from the host into that namespace, the unprivileged user can then access any file on the host as real root, causing the privilege escalation. An exploit is attached to this bug. It's been confirmed to be runnable as a nobody user on a regular Ubuntu system and to successfully read any file on the host. To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1438758/+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 1432843] Re: Lubuntu failed to boot
*** This bug is a duplicate of bug 1441843 *** https://bugs.launchpad.net/bugs/1441843 Confirmed this is a bug in the seed. Julien is on it and it should be resolved in time for release. This doesn't affect X but I can't remove that it seems. Alberto? I'm going to dupe this against the other bug and change the description a bit. ** No longer affects: xorg (Ubuntu) ** Changed in: lubuntu-meta (Ubuntu) Assignee: (unassigned) = Julien Lavergne (gilir) ** This bug has been marked a duplicate of bug 1441843 X server fails to start on post-final Beta Lubuntu Vivid desktop images in virtual machines -- 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/1432843 Title: Lubuntu failed to boot Status in X.Org X server: Confirmed Status in lubuntu-meta package in Ubuntu: Triaged Bug description: The daily build of Lubuntu 20150316 failed to boot into the live session, and fails to install. During the boot session, the Lubuntu splash screen appears indicating that Lubuntu was loading. What follows next was a blank screen. Unfortunately, I cannot sumit the exact version of syslinux since the daily build could not boot into an interactive session. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: syslinux 3:6.03~pre18+dfsg-1ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0 Uname: Linux 3.19.0-7-generic i686 ApportVersion: 2.16.2-0ubuntu1 Architecture: i386 Date: Mon Mar 16 17:19:35 2015 Dependencies: gcc-5-base 5-20150228-1ubuntu1 libc6 2.19-15ubuntu2 libgcc1 1:5-20150228-1ubuntu1 mtools 4.0.18-2 multiarch-support 2.19-15ubuntu2 InstallationDate: Installed on 2015-03-05 (11 days ago) InstallationMedia: Lubuntu 15.04 Vivid Vervet - Alpha i386 (20150303) SourcePackage: syslinux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1432843/+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 1443019] Re: browser crashes on image-heavy pages
I can reproduce on krillin, with the latest vivid-proposed image (#184). Relevant output from /var/log/syslog: Apr 14 19:01:49 ubuntu-phablet kernel: [ 6435.958540]select 'unity8-dash' (2512), adj 50, size 14703, to kill Apr 14 19:01:49 ubuntu-phablet kernel: [ 6435.958570]select 'webbrowser-app' (9421), adj 110, size 16248, to kill Apr 14 19:01:49 ubuntu-phablet kernel: [ 6435.958590]select 'oxide-renderer' (16584), adj 300, size 150274, to kill Apr 14 19:01:49 ubuntu-phablet kernel: [ 6435.958613]Killing 'oxide-renderer' (16584), adj 300, Apr 14 19:01:49 ubuntu-phablet kernel: [ 6435.958617] to free 601096kB on behalf of 'CompositorTileW' (16593) because Apr 14 19:01:49 ubuntu-phablet kernel: [ 6435.958622] cache 65364kB is below limit 65536kB for oom_score_adj 12 Apr 14 19:01:49 ubuntu-phablet kernel: [ 6435.958627] Free memory is -3272kB above reserved [gfp(0x200da)] So technically, the browser doesn’t crash, but the renderer process is being killed by the system to free up memory. The browser should certainly display a user-friendly message when that happens, instead of just a blank page (tracked by bug #1375272). However I doubt you’ll ever be able to view that page in its entirety on this device, given the memory constraints. ** Changed in: webbrowser-app (Ubuntu) Status: New = Confirmed ** Summary changed: - browser crashes on image-heavy pages + renderer process is killed on image-heavy pages on krillin ** Also affects: webbrowser-app Importance: Undecided Status: New ** Changed in: webbrowser-app Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1443019 Title: renderer process is killed on image-heavy pages on krillin Status in Web Browser App: Confirmed Status in webbrowser-app package in Ubuntu: Confirmed Bug description: On the BQ ubuntu phone, while browsing image-heavy pages, the browser suddenly turns completely white and unresponsive. Closing the app and restarting it fixes the problem. example: I can't watch this page to the end, because the browser crashes in the middle... https://imgur.com/gallery/NnGyq I have this on a lot of websites, after browsing for 30 minutes, the browser crashes... To manage notifications about this bug go to: https://bugs.launchpad.net/webbrowser-app/+bug/1443019/+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 1214352] Re: [SRU] GUINT32/64_SWAP_LE_BE macros do not enclose val argument in parentheses
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gvfs (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1214352 Title: [SRU] GUINT32/64_SWAP_LE_BE macros do not enclose val argument in parentheses Status in LibreOffice Productivity Suite: Fix Released Status in The G Library - GLib: Fix Released Status in glib2.0 package in Ubuntu: Fix Released Status in gvfs package in Ubuntu: Confirmed Status in libreoffice package in Ubuntu: Confirmed Bug description: [Impact] * This bug affects Glib-dependent packages, one of them is modern version of LibreOffice 4.x from PPA (https://launchpad.net/~libreoffice/+archive/ubuntu/ppa). * LibreOffice is very important software. Modern versions are more functional. Without them Ubuntu is nothing, it is a toy. [Test Case] 1. Place OpenDocument file (for example 'test.odt') on SMB/CIFS server (Samba on GNU/Linux, or from Windows). Make this share available for read-write. 2a.1. Open Nautilus, navigate it to 'smb://server_name/share_name/', wait the share to be mounted with GVFS. 2a.2. Double click on 'test.odt' 2b. Launch terminal and send 'libreoffice smb://server_name/share_name/test.odt' command. 3. Get error message from LibreOffice: The file 'test.odt' is corrupt and therefore cannot be opened. LibreOffice can try to repair the file. The corruption could be the result of document manipulation or of structural document damage due to data transmission. We recommend that you do not trust the content of the repaired document. Execution of macros is disabled for this document. Should LibreOffice repair the file? Yes No 4a. If I click 'Yes', the file is opened, but the title of the document is Untitled 1 (repaired document), not original name. 4b. If I click 'No', the dialog 'LibreOffice 4.4' is opened with text: The file 'test.odt' could not be repaired and therefore cannot be opened. OK I click 'OK' here, the next window LibreOffice 4.4.1.2 is opened with text: General Error. General input/output error. OK If I click OK here - no files are opened. While step 3 gvfsd-smb process eats CPU then terminates with error. This error is caused by bug in Glib (wrong type conversion in macros). [Regression Potential] * This functionality is essential. Please fix this bug. I (and you) can't tell Windows users, that they should not open office files from network shares in GNU/Linux. * The patch has two lines (https://git.gnome.org/browse/glib/commit/?id=255c65f83c1515a7e3fc4609b36e72acc08a79e4) and well-tested at upstream. * This bug may cause potential loss of data. [Other Info] * Corresponding links to LibO bugs are: https://bugs.freedesktop.org/show_bug.cgi?id=67527 https://bugs.documentfoundation.org/show_bug.cgi?id=72337 [Original description] On 12.04 LTS precise GUINT32/64_SWAP_LE_BE macros do not enclose val argument in parentheses, causing trouble down the stack in gvfs and LibreOffice (and possibly in lots of obscure bugs elsewhere). There is a patch available, but as this touches the header, it needs a full recompile of rdepends. see: https://lists.fedoraproject.org/pipermail/devel/2013-March/180302.html ff. for details To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1214352/+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 1214352] Re: [SRU] GUINT32/64_SWAP_LE_BE macros do not enclose val argument in parentheses
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: libreoffice (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1214352 Title: [SRU] GUINT32/64_SWAP_LE_BE macros do not enclose val argument in parentheses Status in LibreOffice Productivity Suite: Fix Released Status in The G Library - GLib: Fix Released Status in glib2.0 package in Ubuntu: Fix Released Status in gvfs package in Ubuntu: Confirmed Status in libreoffice package in Ubuntu: Confirmed Bug description: [Impact] * This bug affects Glib-dependent packages, one of them is modern version of LibreOffice 4.x from PPA (https://launchpad.net/~libreoffice/+archive/ubuntu/ppa). * LibreOffice is very important software. Modern versions are more functional. Without them Ubuntu is nothing, it is a toy. [Test Case] 1. Place OpenDocument file (for example 'test.odt') on SMB/CIFS server (Samba on GNU/Linux, or from Windows). Make this share available for read-write. 2a.1. Open Nautilus, navigate it to 'smb://server_name/share_name/', wait the share to be mounted with GVFS. 2a.2. Double click on 'test.odt' 2b. Launch terminal and send 'libreoffice smb://server_name/share_name/test.odt' command. 3. Get error message from LibreOffice: The file 'test.odt' is corrupt and therefore cannot be opened. LibreOffice can try to repair the file. The corruption could be the result of document manipulation or of structural document damage due to data transmission. We recommend that you do not trust the content of the repaired document. Execution of macros is disabled for this document. Should LibreOffice repair the file? Yes No 4a. If I click 'Yes', the file is opened, but the title of the document is Untitled 1 (repaired document), not original name. 4b. If I click 'No', the dialog 'LibreOffice 4.4' is opened with text: The file 'test.odt' could not be repaired and therefore cannot be opened. OK I click 'OK' here, the next window LibreOffice 4.4.1.2 is opened with text: General Error. General input/output error. OK If I click OK here - no files are opened. While step 3 gvfsd-smb process eats CPU then terminates with error. This error is caused by bug in Glib (wrong type conversion in macros). [Regression Potential] * This functionality is essential. Please fix this bug. I (and you) can't tell Windows users, that they should not open office files from network shares in GNU/Linux. * The patch has two lines (https://git.gnome.org/browse/glib/commit/?id=255c65f83c1515a7e3fc4609b36e72acc08a79e4) and well-tested at upstream. * This bug may cause potential loss of data. [Other Info] * Corresponding links to LibO bugs are: https://bugs.freedesktop.org/show_bug.cgi?id=67527 https://bugs.documentfoundation.org/show_bug.cgi?id=72337 [Original description] On 12.04 LTS precise GUINT32/64_SWAP_LE_BE macros do not enclose val argument in parentheses, causing trouble down the stack in gvfs and LibreOffice (and possibly in lots of obscure bugs elsewhere). There is a patch available, but as this touches the header, it needs a full recompile of rdepends. see: https://lists.fedoraproject.org/pipermail/devel/2013-March/180302.html ff. for details To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1214352/+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 1432843] Re: Lubuntu failed to boot
** Tags added: lubuntu -- 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/1432843 Title: Lubuntu failed to boot Status in X.Org X server: Confirmed Status in lubuntu-meta package in Ubuntu: Triaged Status in xorg package in Ubuntu: Triaged Bug description: The daily build of Lubuntu 20150316 failed to boot into the live session, and fails to install. During the boot session, the Lubuntu splash screen appears indicating that Lubuntu was loading. What follows next was a blank screen. Unfortunately, I cannot sumit the exact version of syslinux since the daily build could not boot into an interactive session. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: syslinux 3:6.03~pre18+dfsg-1ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0 Uname: Linux 3.19.0-7-generic i686 ApportVersion: 2.16.2-0ubuntu1 Architecture: i386 Date: Mon Mar 16 17:19:35 2015 Dependencies: gcc-5-base 5-20150228-1ubuntu1 libc6 2.19-15ubuntu2 libgcc1 1:5-20150228-1ubuntu1 mtools 4.0.18-2 multiarch-support 2.19-15ubuntu2 InstallationDate: Installed on 2015-03-05 (11 days ago) InstallationMedia: Lubuntu 15.04 Vivid Vervet - Alpha i386 (20150303) SourcePackage: syslinux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1432843/+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 1432788] Re: Race in vivid means sometimes bluetooth is no available
** Also affects: canonical-devices-system-image Importance: Undecided Status: New ** Changed in: canonical-devices-system-image Assignee: (unassigned) = Canonical Phone Foundations (canonical-phonedations-team) -- 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/1432788 Title: Race in vivid means sometimes bluetooth is no available Status in the base for Ubuntu mobile products: New Status in bluez package in Ubuntu: New Bug description: STEPS: 1. Flash a fresh image of vivid on a krillin device 2. Check if bluetooth is on 3. Reboot EXPECTED: I always expect bluetooth to be on ACTUAL: Bluetooth was turned off, I couldn't tur it on, when I rebooted it was on how ever it wouldn't connect to anything. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1432788/+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 1444002] [NEW] [launcher] visual feedback on tap is too subtle
Public bug reported: Reproduce: Always $ system-image-cli -i current build number: 127 device name: m75 channel: ubuntu-touch/vivid-proposed last update: 2015-03-10 16:26:39 version version: 127 Steps to reproduce: 1. Open launcher 2. Click or tap an open or closed application. What happens: There's a time between a click/tap, when the system spawns a spinner (and closes the launcher), where nothing happens. What should happen instead: You should immediately get feedback that the button was clicked/tapped. ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New ** Description changed: Reproduce: Always $ system-image-cli -i current build number: 127 device name: m75 channel: ubuntu-touch/vivid-proposed last update: 2015-03-10 16:26:39 version version: 127 Steps to reproduce: 1. Open launcher 2. Click or tap an open or closed application. What happens: There's a time between a click/tap, when the system spawns a spinner (and closes the launcher), where nothing happens. What should happen instead: - You should get feedback that the button was clicked/tapped immediately. + You should immediately get feedback that the button was clicked/tapped. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1444002 Title: [launcher] visual feedback on tap is too subtle Status in unity8 package in Ubuntu: New Bug description: Reproduce: Always $ system-image-cli -i current build number: 127 device name: m75 channel: ubuntu-touch/vivid-proposed last update: 2015-03-10 16:26:39 version version: 127 Steps to reproduce: 1. Open launcher 2. Click or tap an open or closed application. What happens: There's a time between a click/tap, when the system spawns a spinner (and closes the launcher), where nothing happens. What should happen instead: You should immediately get feedback that the button was clicked/tapped. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1444002/+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 1441241] Re: Ubuntu Nexus 4 does not detect location
This does appear to work for me, but after soem experimentation with another Nexus 4 user, it seems that it's very weak... the phone fails to get a GPS lock when in a case, but can when it's not in the case... I don't know how much of the GPS system is implemented in Software vs how much is in hardware... I'm told the GPS on the Nexus 4 is good under Android although I have not tested this... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1441241 Title: Ubuntu Nexus 4 does not detect location Status in location-service package in Ubuntu: Confirmed Bug description: Whenever I try to locate myself, the app/scope/whatever I am using does not manage to locate me even if location detection and GPS are on. The only way I manage to locate myself is through being connected to a wireless network. I have tried using different apps and scopes that all use location data and none of them receive any GPS information unless I am on a wireless network. I never turn GPS off and I live in central London so there is no way it cannot find a GPS fix (I also have spend a lot of time outside and still no luck). I am using the OSMTouch app and it spends 20 seconds trying to locate me and comes back with Geolocation failed. This is using a Nexus 4. I have tried the current stable and devel- proposed channels. I asked on IRC this morning to find other people having issues with Nexus 4 GPS including one person who said: 'on the N4 i actually have to leave the device outside on the window shelf for 20-30 min to get GPS at all.' Is this a known issue with the Nexus 4? Is there a fix for this? Can anybody help fix this? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/location-service/+bug/1441241/+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 1427275] Re: clean cloud images of python2
point of reference: $ sudo apt-get remove python Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED: landscape-client landscape-common python python-apt python-characteristic python-chardet python-configobj python-debian python-gdbm python-idna python-openssl python-pam python-pkg-resources python-pyasn1 python-pyasn1-modules python-pycurl python-serial python-service-identity python-six python-twisted-bin python-twisted-core python-twisted-web python-zope.interface update-notifier-common 0 upgraded, 0 newly installed, 24 to remove and 0 not upgraded. After this operation, 17.0 MB disk space will be freed. Do you want to continue? [Y/n] n $ cat /etc/cloud/build.info build_name: server serial: 20150413.1 ** No longer affects: vim (Ubuntu Vivid) ** No longer affects: landscape-client (Ubuntu Vivid) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1427275 Title: clean cloud images of python2 Status in cloud-utils package in Ubuntu: Confirmed Status in landscape-client package in Ubuntu: Confirmed Status in vim package in Ubuntu: Confirmed Status in cloud-utils source package in Vivid: Confirmed Bug description: cloud-init is now running in python3 in the cloud images in vivid. We'd like to remove the remaining few python2 packages. P From a 20150228 image, that looks like: $ sudo apt-get remove python Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED: cloud-guest-utils cloud-init landscape-client landscape-common python python-apt python-characteristic python-chardet python-configobj python-debian python-gdbm python-idna python-openssl python-pam python-pkg-resources python-pyasn1 python-pyasn1-modules python-pycurl python-serial python-service-identity python-six python-twisted-bin python-twisted-core python-twisted-web python-zope.interface update-notifier-common 0 upgraded, 0 newly installed, 26 to remove and 17 not upgraded. After this operation, 18.1 MB disk space will be freed. Do you want to continue? [Y/n] ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: landscape-client 14.12-0ubuntu1 ProcVersionSignature: User Name 3.18.0-13.14-generic 3.18.5 Uname: Linux 3.18.0-13-generic x86_64 ApportVersion: 2.16.1-0ubuntu2 Architecture: amd64 Date: Mon Mar 2 15:56:05 2015 Ec2AMI: ami-01cc Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.small Ec2Kernel: aki-0002 Ec2Ramdisk: ari-0002 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: landscape-client UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-utils/+bug/1427275/+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 1300235] Re: init (chromium-browser) crashed with SIGSEGV
This bug was fixed in the package apport - 2.17.1-0ubuntu1 --- apport (2.17.1-0ubuntu1) vivid; urgency=medium * New upstream bug fix release: - SECURITY UPDATE: Fix root privilege escalation through crash forwarding to containers. Version 2.13 introduced forwarding a crash to a container's apport. By crafting a specific file system structure, entering it as a namespace (container), and crashing something in it, a local user could access arbitrary files on the host system with root privileges. Thanks to Stéphane Graber for discovering and fixing this! (CVE-2015-1318, LP: #1438758) - apport-kde tests: Fix imports to make tests work again. - Fix UnicodeDecodeError on parsing non-ASCII environment variables. - apport: use the proper pid when calling apport in another PID namespace. Thanks Brian Murray. (LP: #1300235) -- Martin Pitt martin.p...@ubuntu.com Tue, 14 Apr 2015 09:10:17 -0500 ** Changed in: apport (Ubuntu) Status: Fix Committed = Fix Released ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2015-1318 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1300235 Title: init (chromium-browser) crashed with SIGSEGV Status in apport package in Ubuntu: Fix Released Status in chromium-browser package in Ubuntu: Triaged Bug description: Test Case - 1) Set your default browser to Chromium. 2) Launch synaptic 3) Click on the home page url for a package. 4) Observe chromium-browser not launch 5) Receive apport crash dialog 5) Also notice the apport crash dialog refers to upstart / systemd none ProblemType: CrashDistroRelease: Ubuntu 14.04 Package: upstart 1.12.1-0ubuntu1 Uname: Linux 3.14.0-031400rc8-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 Date: Mon Mar 31 09:53:16 2014 Disassembly: = 0x7fa2b65e94d7: Cannot access memory at address 0x7fa2b65e94d7 ExecutablePath: /sbin/init InstallationDate: Installed on 2014-03-05 (25 days ago) InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140305) ProcCmdline: /sbin/init ProcEnviron: TERM=linux PATH=(custom, no user) ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.14.0-031400rc8-generic root=UUID=bef08855-3273-4d41-ac06-bad06bdd08a4 ro quiet splash SegvAnalysis: Segfault happened at: 0x7fa2b65e94d7:Cannot access memory at address 0x7fa2b65e94d7 PC (0x7fa2b65e94d7) not located in a known VMA region (needed executable region)! Stack pointer not within stack segment SegvReason: executing unknown VMA Signal: 11SourcePackage: upstart StacktraceTop: ?? () ?? () ?? () Title: init crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UpstartBugCategory: System UpstartRunningSystemVersion: init (upstart 1.12.1) UserGroups: modified.conffile..etc.default.cups: [modified] mtime.conffile..etc.default.cups: 2014-03-11T13:23:34.740893 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1300235/+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 1438758] Re: User to root privilege escalation (ab)using the crash forwarding feature of apport
This bug was fixed in the package apport - 2.17.1-0ubuntu1 --- apport (2.17.1-0ubuntu1) vivid; urgency=medium * New upstream bug fix release: - SECURITY UPDATE: Fix root privilege escalation through crash forwarding to containers. Version 2.13 introduced forwarding a crash to a container's apport. By crafting a specific file system structure, entering it as a namespace (container), and crashing something in it, a local user could access arbitrary files on the host system with root privileges. Thanks to Stéphane Graber for discovering and fixing this! (CVE-2015-1318, LP: #1438758) - apport-kde tests: Fix imports to make tests work again. - Fix UnicodeDecodeError on parsing non-ASCII environment variables. - apport: use the proper pid when calling apport in another PID namespace. Thanks Brian Murray. (LP: #1300235) -- Martin Pitt martin.p...@ubuntu.com Tue, 14 Apr 2015 09:10:17 -0500 ** Changed in: apport (Ubuntu Vivid) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1438758 Title: User to root privilege escalation (ab)using the crash forwarding feature of apport Status in Apport crash detection/reporting: Fix Released Status in apport package in Ubuntu: Fix Released Status in apport source package in Trusty: Fix Released Status in apport source package in Utopic: Fix Released Status in apport source package in Vivid: Fix Released Status in apport package in Debian: New Bug description: Back in Ubuntu 14.04, I introduced an apport feature that will have it forward any crash to another apport running in the task's namespace (in the case where the pid of the task in its namespace isn't equal to that in the host namespace). This feature simply checks for the presence of /usr/share/apport/apport in the task's root directory. If it exists, it will chroot and exec the script. The problem is that as apport is a coredump handler triggered by the kernel, it'll always run as real root, regardless of the crashed task's owner and namespace. This therefore allows an unprivileged user to craft a specific filesystem structure, pivot_root to it, then crash a process inside it, causing apport outside of the namespace to execute a script as real root. By bind-mounting /proc from the host into that namespace, the unprivileged user can then access any file on the host as real root, causing the privilege escalation. An exploit is attached to this bug. It's been confirmed to be runnable as a nobody user on a regular Ubuntu system and to successfully read any file on the host. To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1438758/+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 1436406] Re: The Browser has no privacy options!
Now marking fixed as an initial cut of the privacy settings has been implemented in vivid (although not complete, it already allows clearing the cache and the browsing history). Let’s track the addition of more privacy settings in separate bug reports. ** Changed in: webbrowser-app Status: In Progress = Fix Released ** Changed in: webbrowser-app (Ubuntu) Status: In Progress = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1436406 Title: The Browser has no privacy options! Status in Usability Bugs in Ubuntu Phone: Confirmed Status in Web Browser App: Fix Released Status in webbrowser-app package in Ubuntu: Fix Released Bug description: The Browser has no privacy options! There should be a option to: - forbid third party cookies - tell Websites do not track me - delete chronicle - delete list of visited websites - to install a adblocker - to modify the user agent To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntuphone/+bug/1436406/+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 1318144] Re: Can't edit reviews
** Changed in: unity-scope-click (Ubuntu) Assignee: (unassigned) = Pawel Stolowski (stolowski) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scope-click in Ubuntu. https://bugs.launchpad.net/bugs/1318144 Title: Can't edit reviews Status in Ratings and Reviews server: Fix Released Status in unity-scope-click package in Ubuntu: Confirmed Bug description: It seems impossible to edit reviews at the moment. I get the review entry even though I reviewed already and I'm allowed to send another review, which actually gets lost somewhere. I imagine we want to limit the number of reviews to 1 per U1 account, but it should be possible to send a new/modified one. Maybe the review entry should be pre-filled with the previous review so it's obvious you can edit? To manage notifications about this bug go to: https://bugs.launchpad.net/rnr-server/+bug/1318144/+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 513644] Re: Does not log fsck invocations in /var/log/fsck/
** Tags added: amd64 i386 jaunty karmic trusty
** Tags added: precise
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mountall in Ubuntu.
https://bugs.launchpad.net/bugs/513644
Title:
Does not log fsck invocations in /var/log/fsck/
Status in mountall package in Ubuntu:
Triaged
Bug description:
Binary package hint: mountall
This concerns mountall 1.0 in Karmic.
After fsck is invoked at boot time, the two log files in
/var/log/fsck/ remain empty. In Jaunty, the
/etc/init.d/check{fs,root}.sh scripts saved the output of the commands
to that directory (A log is being saved in ${FSCK_LOGFILE} if that
location is writable) but mountall has yet to do this.
As this would have to be newly implemented, I'd like to request a
slight change from the Jaunty behavior, and have entries be appended
to the log files rather than the files being overwritten each time
with the latest (single) entry. Log rotation on these files may be
good, too, although I'm not sure which package would/should be
responsible for that.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/513644/+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 1371248] Re: [Browser] No home button to take you back to the default home page
** Tags added: newtab -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1371248 Title: [Browser] No home button to take you back to the default home page Status in Ubuntu UX bugs: Fix Committed Status in Web Browser App: In Progress Status in webbrowser-app package in Ubuntu: In Progress Bug description: STEPS: 1. Open the browser on a fresh flash 2. Note the home page 3. Browse to planet.ubuntu.com 4. Close the browser 5. Open the browser 6. Try and get back to the original home page. EXPECTATION: Every browser has a home button, it may or may not be used on mobiles but at some point you might want to go back to that page. ACTUAL: Once you close the browser the history registers the home page but after a while that would disappear then you would be left with no reference of it. -- SOLUTION -- Add a default bookmark in the New Tab screen http://start.ubuntu.com/current/?sourceid=hp Title=Ubuntu Start page To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1371248/+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 1436427] Re: Turning off WiFi doesn't set a route after the modem connects data
@Sebastien
We have a proposed ofono fix that definitely improves the situation,
however nobody else with Canonical besides yourself an Michael have been
able to reproduce on RTM. See bug #1435328 for an update on the
analysis so far.
Could you install the version ( 1.12.bzr6894+15.04.20150413.2~rtm-
0ubuntu1~awe1 ) of ofono from my personal PPA:
https://launchpad.net/~awe/+archive/ubuntu/ppa
...and also make sure you have network-manager version
0.9.10.0-4ubuntu14 installed. It's currently in silo 009, but should
be landing in the archive shortly.
I'm trying to determine if we need a fix to network-manager in RTM as
well, per Alfonso's comments in the other bug.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1436427
Title:
Turning off WiFi doesn't set a route after the modem connects data
Status in the base for Ubuntu mobile products:
Confirmed
Status in network-manager package in Ubuntu:
Confirmed
Status in network-manager package in Ubuntu RTM:
Confirmed
Bug description:
I just switched off WiFi in order to test if the device switches
successfully to a mobile data connection. After disabling WiFi the
indicator showed H in no time. So it would seem all is fine. I
opened the browser and no data went through.
Here's the output of ip route and list-contexts:
phablet@ubuntu-phablet:~$ sudo ip route
[sudo] password for phablet:
phablet@ubuntu-phablet:~$ /usr/share/ofono/scripts/list-contexts
[ /ril_1 ]
[ /ril_0 ]
[ /ril_0/context1 ]
Name = E-Plus Web GPRS
Settings = { Netmask=255.255.255.0 Address=10.121.30.213
Interface=ccmni0 Method=static DomainNameServers=212.23.103.8,212.23.103.9,
Gateway=10.121.30.213 }
Username = eplus
IPv6.Settings = { }
Protocol = ip
Active = 1
Password = internet
Type = internet
AccessPointName = internet.eplus.de
[ /ril_0/context2 ]
IPv6.Settings = { }
Name = E-Plus MMS
MessageProxy = 212.23.97.153:5080
MessageCenter = http://mms/eplus/
Username = mms
Settings = { }
Protocol = ip
Active = 0
Password = eplus
Type = mms
AccessPointName = mms.eplus.de
[ /ril_0/context3 ]
Name = ___ubuntu_custom_apn_internet
Settings = { }
Username =
IPv6.Settings = { }
Protocol = ip
Active = 0
Password =
Type = internet
AccessPointName =
phablet@ubuntu-phablet:~$ system-image-cli -i
current build number: 21
device name: krillin
channel: ubuntu-touch/rc/bq-aquaris.en
last update: 2015-03-13 17:11:07
version version: 21
version ubuntu: 20150312
version device: 20150310-3201c0a
version custom: 20150216-561-29-186
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1436427/+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
