[Touch-packages] [Bug 1383486] Re: menu to select zoom doesn't drop down
This bug was fixed in the package gtk+3.0 - 3.12.2-0ubuntu16 --- gtk+3.0 (3.12.2-0ubuntu16) vivid; urgency=medium * debian/patches/git_popover_position.patch, debian/patches/git_popover_display.patch: - correctly display gtkpopover widgets, thanks Ryan Lorties for backporting the fixes (lp: #1383486) -- Sebastien BacherTue, 28 Oct 2014 18:23:29 +0100 ** Changed in: gtk+3.0 (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 gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1383486 Title: menu to select zoom doesn't drop down Status in “gtk+3.0” package in Ubuntu: Fix Released Bug description: To reproduce open a pdf file in evince from pcmanfm or another file manager. Then move the mouse to the upper right corner of the window along the top bar. Then try to click on the arrow pointing down to drop down the menu. The mouse pointer will click but no menu will drop down. I can still edit the zoom by clickin in this bar but I cannoy select fit page or fit width like I used to be able to in 14.04. I am using lxde as my desktop environment with openbox as my window manager. evince: Installed: 3.14.1-0ubuntu1 Candidate: 3.14.1-0ubuntu1 Version table: *** 3.14.1-0ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages 100 /var/lib/dpkg/status Description: Ubuntu 14.10 Release: 14.10 I expected a menu to be able to choose zoom instead I can only change zoom by typing in the box. Work around is to manually set a zoom by typing it in. This could lead to some accessibility problems for people with low vision if they need to zoom in on a pdf and don't know the workaround. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: evince 3.14.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-22.29-generic 3.16.4 Uname: Linux 3.16.0-22-generic x86_64 ApportVersion: 2.14.7-0ubuntu7 Architecture: amd64 CurrentDesktop: LXDE Date: Mon Oct 20 14:08:31 2014 InstallationDate: Installed on 2014-09-30 (19 days ago) InstallationMedia: Lubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140930) SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1383486/+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 1376644] Re: Some qtpim tests start failing when built against Qt 5.3.2
Vivid packages now at https://launchpad.net/~ci-train-ppa- service/+archive/ubuntu/landing-002 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtpim-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1376644 Title: Some qtpim tests start failing when built against Qt 5.3.2 Status in “qtpim-opensource-src” package in Ubuntu: New Bug description: Some qtpim tests start failing when built against Qt 5.3.2: https://launchpad.net/~ci-train-ppa- service/+archive/ubuntu/landing-015/+sourcepub/4451482/+listing- archive-extra I've also updated to the latest git snapshot but unfortunately it doesn't fix the problems: https://launchpad.net/~ci-train-ppa- service/+archive/ubuntu/landing-015/+sourcepub/4451510/+listing- archive-extra We shouldn't be disabling additional tests, so the root causes should be found. You can test the Qt 5.3.2 yourself by following the instructions at https://wiki.ubuntu.com/Touch/QtTesting And to get the sources + current packaging: dget https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-015/+files/qtpim-opensource-src_5.0%7Egit20141002%7E4c0b26cf-0ubuntu1%7Eutopic1%7Etest1.dsc dpkg-source -x *.dsc # and for example 'pdebuild' to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtpim-opensource-src/+bug/1376644/+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 1386992] Re: package libqtcore4 (not installed) failed to install/upgrade: intentando sobreescribir el compartido `/etc/xdg/Trolltech.conf', que es distinto de otras instancias d
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qt4-x11 in Ubuntu. https://bugs.launchpad.net/bugs/1386992 Title: package libqtcore4 (not installed) failed to install/upgrade: intentando sobreescribir el compartido `/etc/xdg/Trolltech.conf', que es distinto de otras instancias del paquetes libqtcore4:i386 Status in “qt4-x11” package in Ubuntu: New Bug description: package libqtcore4 (not installed) failed to install/upgrade: intentando sobreescribir el compartido `/etc/xdg/Trolltech.conf', que es distinto de otras instancias del paquetes libqtcore4:i386 ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libqtcore4 (not installed) ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 Date: Wed Oct 29 00:50:28 2014 DuplicateSignature: package:libqtcore4:(not installed):intentando sobreescribir el compartido `/etc/xdg/Trolltech.conf', que es distinto de otras instancias del paquetes libqtcore4:i386 ErrorMessage: intentando sobreescribir el compartido `/etc/xdg/Trolltech.conf', que es distinto de otras instancias del paquetes libqtcore4:i386 InstallationDate: Installed on 2014-10-29 (0 days ago) InstallationMedia: Xubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140723) SourcePackage: qt4-x11 Title: package libqtcore4 (not installed) failed to install/upgrade: intentando sobreescribir el compartido `/etc/xdg/Trolltech.conf', que es distinto de otras instancias del paquetes libqtcore4:i386 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qt4-x11/+bug/1386992/+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 1386872] Re: Incorrect termination Firefox when shutdown Ubuntu
The same problem. does Google-chrome, ubuntu 12.04. -- 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/1386872 Title: Incorrect termination Firefox when shutdown Ubuntu Status in “unity” package in Ubuntu: Confirmed Bug description: 1. In Firefox go to Preference -> General tab, choose Show my windows and tabs from last time in When Firefox starts field. 2. Shutdown Ubuntu 3. Start Ubuntu 4. Open Firefox Actual result: Firefox opens with message "Firefox was not closed properly" ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20141016-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4 Uname: Linux 3.16.0-23-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Oct 28 22:20:52 2014 InstallationDate: Installed on 2014-10-25 (3 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1386872/+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 1386992] [NEW] package libqtcore4 (not installed) failed to install/upgrade: intentando sobreescribir el compartido `/etc/xdg/Trolltech.conf', que es distinto de otras instancias
Public bug reported: package libqtcore4 (not installed) failed to install/upgrade: intentando sobreescribir el compartido `/etc/xdg/Trolltech.conf', que es distinto de otras instancias del paquetes libqtcore4:i386 ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libqtcore4 (not installed) ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 Date: Wed Oct 29 00:50:28 2014 DuplicateSignature: package:libqtcore4:(not installed):intentando sobreescribir el compartido `/etc/xdg/Trolltech.conf', que es distinto de otras instancias del paquetes libqtcore4:i386 ErrorMessage: intentando sobreescribir el compartido `/etc/xdg/Trolltech.conf', que es distinto de otras instancias del paquetes libqtcore4:i386 InstallationDate: Installed on 2014-10-29 (0 days ago) InstallationMedia: Xubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140723) SourcePackage: qt4-x11 Title: package libqtcore4 (not installed) failed to install/upgrade: intentando sobreescribir el compartido `/etc/xdg/Trolltech.conf', que es distinto de otras instancias del paquetes libqtcore4:i386 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: qt4-x11 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qt4-x11 in Ubuntu. https://bugs.launchpad.net/bugs/1386992 Title: package libqtcore4 (not installed) failed to install/upgrade: intentando sobreescribir el compartido `/etc/xdg/Trolltech.conf', que es distinto de otras instancias del paquetes libqtcore4:i386 Status in “qt4-x11” package in Ubuntu: New Bug description: package libqtcore4 (not installed) failed to install/upgrade: intentando sobreescribir el compartido `/etc/xdg/Trolltech.conf', que es distinto de otras instancias del paquetes libqtcore4:i386 ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libqtcore4 (not installed) ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 Date: Wed Oct 29 00:50:28 2014 DuplicateSignature: package:libqtcore4:(not installed):intentando sobreescribir el compartido `/etc/xdg/Trolltech.conf', que es distinto de otras instancias del paquetes libqtcore4:i386 ErrorMessage: intentando sobreescribir el compartido `/etc/xdg/Trolltech.conf', que es distinto de otras instancias del paquetes libqtcore4:i386 InstallationDate: Installed on 2014-10-29 (0 days ago) InstallationMedia: Xubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140723) SourcePackage: qt4-x11 Title: package libqtcore4 (not installed) failed to install/upgrade: intentando sobreescribir el compartido `/etc/xdg/Trolltech.conf', que es distinto de otras instancias del paquetes libqtcore4:i386 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qt4-x11/+bug/1386992/+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 1357321] Re: QNetworkAccessManager doesn't support roaming on Ubuntu
I've just pushed updated build ~test4, refreshing/rebasing from the 5.4 patches and adding Reset-QNAM-s-NetworkConfiguration-when-state- changes.patch. The patches included currently are: disable-generic-plugin-when-others-available.patch Add-better-mobile-connections-to-QtBearer-NetworkMan.patch update-QtBearer-NetworkManager-backend-API.patch Reset-QNAM-s-NetworkConfiguration-when-state-changes.patch Please tell if eg any of the following not yet mentioned here would be needed to be added too (from codereview): Fix bogus error report when disconnect/stop actually works Do not add invalid configurations to bearermonitor QtBearer corewlan add list of remembered networks ...although I understand there's still work to be done. -- 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/1357321 Title: QNetworkAccessManager doesn't support roaming on Ubuntu Status in Platform API: Incomplete Status in The Savilerow project: New Status in “qtbase-opensource-src” package in Ubuntu: In Progress Bug description: scope images load fine in wifi, but not on hsdpa even when there is good connectivity and browsing works well. Results are return, but images do not load. To manage notifications about this bug go to: https://bugs.launchpad.net/platform-api/+bug/1357321/+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 1386872] Re: Incorrect termination Firefox when shutdown Ubuntu
This is not a bug of Unity, because I confirm thim bug is observed on Xubuntu too. -- 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/1386872 Title: Incorrect termination Firefox when shutdown Ubuntu Status in “unity” package in Ubuntu: Confirmed Bug description: 1. In Firefox go to Preference -> General tab, choose Show my windows and tabs from last time in When Firefox starts field. 2. Shutdown Ubuntu 3. Start Ubuntu 4. Open Firefox Actual result: Firefox opens with message "Firefox was not closed properly" ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20141016-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4 Uname: Linux 3.16.0-23-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Oct 28 22:20:52 2014 InstallationDate: Installed on 2014-10-25 (3 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1386872/+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 1380683] Re: Web app requiring account, and "Online Accounts" account screen, disappear without explanation
QNAM does indeed block at startup. Unfortunately, the QtBearer backend needs to perform synchronously in order for QNAM to perform correctly. Under heavy cpu load, I have seen dbus get quite sluggish. There is room for optimization in the NetworkManager backend so it uses property cache with one blocking call per interface (that need it) instead of the current method. -- 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/1380683 Title: Web app requiring account, and "Online Accounts" account screen, disappear without explanation Status in “qtbase-opensource-src” package in Ubuntu: Incomplete Status in “ubuntu-system-settings-online-accounts” package in Ubuntu: Confirmed Bug description: Ubuntu 14.10 r279 1. Launch a Web app that requires an online account, e.g. Twitter or Facebook. 2. Launch System Settings, and choose an account type. What happens: 1. The app opens, shows an Online Accounts prompt with a spinner for a few seconds, then disappears. 2. An account screen appears for a few seconds, then you're returned to Online Accounts. What should happen: 1. You see the sign-in page. 2. You see the sign-in page. [Originally reported by Patricia Davila.] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1380683/+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 1357321] Re: QNetworkAccessManager doesn't support roaming on Ubuntu
Unfortunately, QtBearer cannot be totally asynchronous, as QNAM is a synchronous API. It does need optimization in regards to amount of blocking calls it does. -- 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/1357321 Title: QNetworkAccessManager doesn't support roaming on Ubuntu Status in Platform API: Incomplete Status in The Savilerow project: New Status in “qtbase-opensource-src” package in Ubuntu: In Progress Bug description: scope images load fine in wifi, but not on hsdpa even when there is good connectivity and browsing works well. Results are return, but images do not load. To manage notifications about this bug go to: https://bugs.launchpad.net/platform-api/+bug/1357321/+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 1288777] Re: Qt bearer thread requires otherwise unneeded internet access
I get his log when running it with Qt 5.3: type=AVC msg=audit(1414555047.145:83): apparmor="DENIED" operation="create" profile="com.ubuntu.developer.jdstrand.permy_permy_0.7" pid=3682 comm="qmlscene" family="netlink" sock_type="raw" protocol=0 type=AVC msg=audit(1414555047.155:84): apparmor="DENIED" operation="create" profile="com.ubuntu.developer.jdstrand.permy_permy_0.7" pid=3727 comm=517420626561726572207468726561 family="netlink" sock_type="raw" protocol=0 I don't think this comes from QtBearer which certainly does need internet access, but from something to do with something in qmlscene needing a socket. Only QNAM and QtNetworkConfiguration stuff uses QtBearer. Qt's Sockets doesn't use that. -- 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/1288777 Title: Qt bearer thread requires otherwise unneeded internet access Status in “qtbase-opensource-src” package in Ubuntu: New Bug description: When comparing Qt5.0 denials with Qt5.2 denials on test runs that popey did, it looks like Qt5.2 changed its behavior such that the Qt bearer thread requires otherwise unneeded internet access. Eg, 'permy' from the appstore does not (and should not) use the "networking" policy group. On 5.0, launching it causes no apparmor denials. On 5.2, it does: Feb 25 REDACT ubuntu-phablet kernel [REDACT] type=1400 audit(REDACT) apparmor="DENIED" operation="create" parent= profile="com.ubuntu.developer.jdstrand.permy_permy_0.5" pid= comm=517420626561726572207468726561 family="inet" sock_type="dgram" protocol=0 Permy's source is at lp:permy. Note, one other application besides permy had similar denials: Feb 25 REDACT ubuntu-phablet kernel [REDACT] type=1400 audit(REDACT) apparmor="DENIED" operation="create" parent= profile="org.sambull.eo-dict_eo-dict_0.2" pid= comm=517420626561726572207468726561 family="inet" sock_type="dgram" protocol=0 This may seem like it isn't important-- the apparmor policy doesn't say it is allowed to connect to the network and apparmor correctly blocks it. I don't know if the app is adversely affected though (these aren't my logs). It might be, and even if it isn't, the noisy denial will lead to confusion (we can't explicitly deny networking in its policy to silence the denial due to how apparmor policy works). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1288777/+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 1386964] Re: package gcc-4.8 4.8.1-10ubuntu8 failed to install/upgrade: não pode copiar dados extráidos para './usr/lib/gcc/x86_64-linux-gnu/4.8/lto1' para '/usr/lib/gcc/x86_64-l
Thank you for taking the time to report this bug and helping to make Ubuntu better. Reviewing your dmesg attachment in this bug report it seems that there is a problem with your hardware. I recommend performing a back up and then investigating the situation. Measures you might take include checking cable connections and using software tools to investigate the health of your hardware. In the event that is is not in fact an error with your hardware please set the bug's status back to New. Thanks and good luck! [This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.] ** Tags added: hardware-error ** Changed in: gcc-4.8 (Ubuntu) Importance: Undecided => Low ** Changed in: gcc-4.8 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gcc-4.8 in Ubuntu. https://bugs.launchpad.net/bugs/1386964 Title: package gcc-4.8 4.8.1-10ubuntu8 failed to install/upgrade: não pode copiar dados extráidos para './usr/lib/gcc/x86_64-linux-gnu/4.8/lto1' para '/usr/lib/gcc/x86_64-linux-gnu/4.8/lto1.dpkg-new': fim de ficheiro ou stream inesperado Status in “gcc-4.8” package in Ubuntu: Invalid Bug description: I'm installing plex package and samba as well. But the program took priority installation and the update started giving error. ProblemType: Package DistroRelease: Ubuntu 13.10 Package: gcc-4.8 4.8.1-10ubuntu8 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 Date: Wed Oct 29 00:16:19 2014 DuplicateSignature: package:gcc-4.8:4.8.1-10ubuntu8:não pode copiar dados extráidos para './usr/lib/gcc/x86_64-linux-gnu/4.8/lto1' para '/usr/lib/gcc/x86_64-linux-gnu/4.8/lto1.dpkg-new': fim de ficheiro ou stream inesperado ErrorMessage: não pode copiar dados extráidos para './usr/lib/gcc/x86_64-linux-gnu/4.8/lto1' para '/usr/lib/gcc/x86_64-linux-gnu/4.8/lto1.dpkg-new': fim de ficheiro ou stream inesperado InstallationDate: Installed on 2014-10-28 (0 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MarkForUpload: True SourcePackage: gcc-4.8 Title: package gcc-4.8 4.8.1-10ubuntu8 failed to install/upgrade: não pode copiar dados extráidos para './usr/lib/gcc/x86_64-linux-gnu/4.8/lto1' para '/usr/lib/gcc/x86_64-linux-gnu/4.8/lto1.dpkg-new': fim de ficheiro ou stream inesperado UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-4.8/+bug/1386964/+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 1362379] Re: Unable discover or play any audio from any hardware device. Bluetooth audio also affected.
[Expired for pulseaudio (Ubuntu) because there has been no activity for 60 days.] ** Changed in: pulseaudio (Ubuntu) Status: Incomplete => Expired -- 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/1362379 Title: Unable discover or play any audio from any hardware device. Bluetooth audio also affected. Status in “pulseaudio” package in Ubuntu: Expired Bug description: Not sure if this is directly related to PulseAudio. PulseAudio equalizer is installed & was working recently. Reinstalled pulseaudio & alsa-base. Still no go. Many thanks! ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: pulseaudio 1:4.0-0ubuntu11 ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4 Uname: Linux 3.13.0-34-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D8p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Wed Aug 27 18:53:42 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-07-26 (33 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/03/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A02 dmi.board.name: 0YX2X3 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA02:bd09/03/2013:svnDellInc.:pnLatitudeE6440:pvr01:rvnDellInc.:rn0YX2X3:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6440 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1362379/+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 1279298] Re: Header title sometimes disappears
[Expired for unity8 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: unity8 (Ubuntu) Status: Incomplete => Expired -- 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/1279298 Title: Header title sometimes disappears Status in “unity8” package in Ubuntu: Expired Bug description: Had this on mako #174 and #176 a couple of times now. When swiping between one applications scope and home scope the new animated title in the header sometimes doesn't appear. It comes back if you swipe around a bit, and it's hard to reproduce. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity8 7.84+14.04.20140207.1-0ubuntu1 Uname: Linux 3.4.0-3-mako armv7l ApportVersion: 2.13.2-0ubuntu2 Architecture: armhf Date: Wed Feb 12 11:22:46 2014 InstallationDate: Installed on 2014-02-12 (0 days ago) InstallationMedia: Ubuntu Trusty Tahr (development branch) - armhf (20140212) ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= SHELL=/bin/bash SourcePackage: unity8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1279298/+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 1329056] Re: lightdm does not start under systemd
[Expired for lightdm (Ubuntu) because there has been no activity for 60 days.] ** Changed in: lightdm (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1329056 Title: lightdm does not start under systemd Status in “lightdm” package in Ubuntu: Expired Bug description: Lightdm does not start under ssytemd. Starting it by hand works. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: lightdm 1.11.3-0ubuntu1 ProcVersionSignature: Ubuntu 3.15.0-5.10-generic 3.15.0-rc8 Uname: Linux 3.15.0-5-generic x86_64 ApportVersion: 2.14.3-0ubuntu1 Architecture: amd64 Date: Wed Jun 11 21:08:35 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2013-06-20 (356 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130618) LightdmConfig: [SeatDefaults] user-session=ubuntu greeter-session=unity-greeter SourcePackage: lightdm UpgradeStatus: Upgraded to utopic on 2013-11-10 (213 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1329056/+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 1362633] Re: 1002:68f2 [Dell Precision T3600] Corrupted Mouse Cursor on primary monitor in dual-monitor KDE
[Expired for xorg (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg (Ubuntu) Status: Incomplete => Expired -- 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/1362633 Title: 1002:68f2 [Dell Precision T3600] Corrupted Mouse Cursor on primary monitor in dual-monitor KDE Status in “xorg” package in Ubuntu: Expired Bug description: When moving the mouse from the secondary (right) monitor to primary (left) monitor, the cursor often becomes corrupted on the primary monitor, as seen in https://bugs.launchpad.net/ubuntu/+source/xserver- xorg-video-ati/+bug/360724 The cursor appears corrupted thereafter, but only on the primary monitor - it appears normal on the secondary. This does not always happen the first time the boundary is crossed from secondary to primary, but once it does occur, it persists until X.Org is restarted. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4 Uname: Linux 3.13.0-34-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: kwin CurrentDesktop: KDE Date: Thu Aug 28 09:05:05 2014 DistUpgraded: 2014-04-21 09:55:42,938 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: kubuntu ExtraDebuggingInterest: No GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Cedar GL [FirePro 2270] [1002:68f2] (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0126] MachineType: Dell Inc. Precision T3600 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-34-generic root=UUID=dce226de-16b4-4a7d-9232-c11bc0c5d9f7 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to trusty on 2014-04-21 (128 days ago) dmi.bios.date: 05/11/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A13 dmi.board.name: 0PTTT9 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA13:bd05/11/2014:svnDellInc.:pnPrecisionT3600:pvr01:rvnDellInc.:rn0PTTT9:rvrA01:cvnDellInc.:ct7:cvr: dmi.product.name: Precision T3600 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A 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.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 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 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Thu Aug 21 16:56:20 2014 xserver.configfile: /etc/X11/xorg.conf xserver.errors: fglrx(0): atiddxDriScreenInit failed. Probably kernel module missing or incompatible. xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.15.1-0ubuntu2 xserver.video_driver: fglrx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1362633/+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 1362647] Re: [CA0106 - CA0106, playback] No sound at all unstable DMA pointer
[Expired for alsa-driver (Ubuntu) because there has been no activity for 60 days.] ** Changed in: alsa-driver (Ubuntu) Status: Incomplete => Expired -- 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/1362647 Title: [CA0106 - CA0106, playback] No sound at all unstable DMA pointer Status in “alsa-driver” package in Ubuntu: Expired Bug description: Trying to get my xTreme Audio (CA1006) to work. Sometimes it works for a short while, and then only front/back left channel and front center. Right channel (front and back) and sub doesn't work at all. After a while no sound whatsoever, but when running ubuntu-bug left channel sunds correct, and with the alternating signals right channel works but quite lower in volume. Only front spekars sounds during test. In Windows (XP, 7, 8, 8.1) the card works fine. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: tomas 7403 F pulseaudio /dev/snd/controlC0: tomas 7403 F pulseaudio /dev/snd/controlC1: tomas 7403 F pulseaudio CurrentDesktop: Unity Date: Thu Aug 28 16:28:02 2014 InstallationDate: Installed on 2014-08-22 (6 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:CA0106 successful Symptom_Card: GF104 High Definition Audio Controller - HDA NVidia Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: tomas 7313 F pulseaudio /dev/snd/controlC0: tomas 7313 F pulseaudio /dev/snd/controlC1: tomas 7313 F pulseaudio Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_SpeakerTestPulseStderr: W r i t e e r r o r : - 5 , I n p u t / o u t p u t e r r o r x r u n _ r e c o v e r y f a i l e d : - 5 , I n p u t / o u t p u t e r r o r T r a n s f e r f a i l e d : I n p u t / o u t p u t e r r o r Symptom_Type: No sound at all Title: [CA0106 - CA0106, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2501 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M5A97 R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2501:bd04/07/2014:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97R2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1362647/+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 1275398] Re: i915 driver/i945 hardware: Mir GL clients are rendered as black (or transparent or crash) windows when using i945 graphics
Andreas' fix is mentioned officially as part of Mesa 10.3.1. I'm yet to test it on an i945 system though... http://lists.freedesktop.org/archives/mesa-dev/2014-October/069253.html -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1275398 Title: i915 driver/i945 hardware: Mir GL clients are rendered as black (or transparent or crash) windows when using i945 graphics Status in Mir: Confirmed Status in “linux” package in Ubuntu: Invalid Status in “mesa” package in Ubuntu: In Progress Bug description: Running Mir on a Pentium D system with integrated i945 graphics, appears to work at first. The server starts and software clients are rendered correctly. However hardware (GL) clients are rendered as all black or transparent windows, despite logging to stdout that they think they are rendering: $ sudo bin/mir_demo_client_egltriangle Current active output is 1920x1200 +0+0 Server supports 2 of 6 surface pixel formats. Using format: 4 libEGL warning: unsupported platform (null) 1 FPS 33 FPS 60 FPS 60 FPS 60 FPS 60 FPS To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1275398/+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 1386964] Re: package gcc-4.8 4.8.1-10ubuntu8 failed to install/upgrade: não pode copiar dados extráidos para './usr/lib/gcc/x86_64-linux-gnu/4.8/lto1' para '/usr/lib/gcc/x86_64-l
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gcc-4.8 in Ubuntu. https://bugs.launchpad.net/bugs/1386964 Title: package gcc-4.8 4.8.1-10ubuntu8 failed to install/upgrade: não pode copiar dados extráidos para './usr/lib/gcc/x86_64-linux-gnu/4.8/lto1' para '/usr/lib/gcc/x86_64-linux-gnu/4.8/lto1.dpkg-new': fim de ficheiro ou stream inesperado Status in “gcc-4.8” package in Ubuntu: New Bug description: I'm installing plex package and samba as well. But the program took priority installation and the update started giving error. ProblemType: Package DistroRelease: Ubuntu 13.10 Package: gcc-4.8 4.8.1-10ubuntu8 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 Date: Wed Oct 29 00:16:19 2014 DuplicateSignature: package:gcc-4.8:4.8.1-10ubuntu8:não pode copiar dados extráidos para './usr/lib/gcc/x86_64-linux-gnu/4.8/lto1' para '/usr/lib/gcc/x86_64-linux-gnu/4.8/lto1.dpkg-new': fim de ficheiro ou stream inesperado ErrorMessage: não pode copiar dados extráidos para './usr/lib/gcc/x86_64-linux-gnu/4.8/lto1' para '/usr/lib/gcc/x86_64-linux-gnu/4.8/lto1.dpkg-new': fim de ficheiro ou stream inesperado InstallationDate: Installed on 2014-10-28 (0 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MarkForUpload: True SourcePackage: gcc-4.8 Title: package gcc-4.8 4.8.1-10ubuntu8 failed to install/upgrade: não pode copiar dados extráidos para './usr/lib/gcc/x86_64-linux-gnu/4.8/lto1' para '/usr/lib/gcc/x86_64-linux-gnu/4.8/lto1.dpkg-new': fim de ficheiro ou stream inesperado UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-4.8/+bug/1386964/+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 1386964] [NEW] package gcc-4.8 4.8.1-10ubuntu8 failed to install/upgrade: não pode copiar dados extráidos para './usr/lib/gcc/x86_64-linux-gnu/4.8/lto1' para '/usr/lib/gcc/x86_64
Public bug reported: I'm installing plex package and samba as well. But the program took priority installation and the update started giving error. ProblemType: Package DistroRelease: Ubuntu 13.10 Package: gcc-4.8 4.8.1-10ubuntu8 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 Date: Wed Oct 29 00:16:19 2014 DuplicateSignature: package:gcc-4.8:4.8.1-10ubuntu8:não pode copiar dados extráidos para './usr/lib/gcc/x86_64-linux-gnu/4.8/lto1' para '/usr/lib/gcc/x86_64-linux-gnu/4.8/lto1.dpkg-new': fim de ficheiro ou stream inesperado ErrorMessage: não pode copiar dados extráidos para './usr/lib/gcc/x86_64-linux-gnu/4.8/lto1' para '/usr/lib/gcc/x86_64-linux-gnu/4.8/lto1.dpkg-new': fim de ficheiro ou stream inesperado InstallationDate: Installed on 2014-10-28 (0 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MarkForUpload: True SourcePackage: gcc-4.8 Title: package gcc-4.8 4.8.1-10ubuntu8 failed to install/upgrade: não pode copiar dados extráidos para './usr/lib/gcc/x86_64-linux-gnu/4.8/lto1' para '/usr/lib/gcc/x86_64-linux-gnu/4.8/lto1.dpkg-new': fim de ficheiro ou stream inesperado UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gcc-4.8 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package need-duplicate-check saucy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gcc-4.8 in Ubuntu. https://bugs.launchpad.net/bugs/1386964 Title: package gcc-4.8 4.8.1-10ubuntu8 failed to install/upgrade: não pode copiar dados extráidos para './usr/lib/gcc/x86_64-linux-gnu/4.8/lto1' para '/usr/lib/gcc/x86_64-linux-gnu/4.8/lto1.dpkg-new': fim de ficheiro ou stream inesperado Status in “gcc-4.8” package in Ubuntu: New Bug description: I'm installing plex package and samba as well. But the program took priority installation and the update started giving error. ProblemType: Package DistroRelease: Ubuntu 13.10 Package: gcc-4.8 4.8.1-10ubuntu8 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 Date: Wed Oct 29 00:16:19 2014 DuplicateSignature: package:gcc-4.8:4.8.1-10ubuntu8:não pode copiar dados extráidos para './usr/lib/gcc/x86_64-linux-gnu/4.8/lto1' para '/usr/lib/gcc/x86_64-linux-gnu/4.8/lto1.dpkg-new': fim de ficheiro ou stream inesperado ErrorMessage: não pode copiar dados extráidos para './usr/lib/gcc/x86_64-linux-gnu/4.8/lto1' para '/usr/lib/gcc/x86_64-linux-gnu/4.8/lto1.dpkg-new': fim de ficheiro ou stream inesperado InstallationDate: Installed on 2014-10-28 (0 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MarkForUpload: True SourcePackage: gcc-4.8 Title: package gcc-4.8 4.8.1-10ubuntu8 failed to install/upgrade: não pode copiar dados extráidos para './usr/lib/gcc/x86_64-linux-gnu/4.8/lto1' para '/usr/lib/gcc/x86_64-linux-gnu/4.8/lto1.dpkg-new': fim de ficheiro ou stream inesperado UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-4.8/+bug/1386964/+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 1372847] Re: [SRU] New stable release 2.40.1
I rebooted shortly after this update and it seems to have broken our IPv4 firewalls. The IPv6 tunnel through sixxs.net still seems to work. Connectivity for the fiewall itself was fine, but most everything on the LAN ground to a halt. One machine is Ubuntu 14.04 64 bit with ufw and the other is Ubuntu 14.04 32 bit using shorewall. I downgraded the libglib2.0-0_2.40.0-2_i386.deb and libglib2.0-data_2.40.0-2_all.deb on the 32 bit machine and reconfigured dhcpd to change the gateway and we are back on the net. I'll try some other tests on the 64 bit machine later or tonight, or more likely tomorrow. I should note that it is possible some other odd networking issue from our local cable company is causing this, but if it is the library, it is going to be ugly for a lot of people using Ubuntu firewalls if this isn't fixed soon. -- 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/1372847 Title: [SRU] New stable release 2.40.1 Status in “glib2.0” package in Ubuntu: Fix Released Status in “glib2.0” source package in Trusty: Fix Released Bug description: We'd like to update glib2.0 using the GNOME MRE. [ Description ] Upstream have released a new stable, fixing some bugs. glib2.0 (2.40.2-0ubuntu1) UNRELEASED; urgency=medium * New upstream stable release, fixing bugs + gobject: try to link with -Wl,-z,nodelete to prevent unloading + g_file_copy: Don't set GError when we intend to ignore errors + gapplication-tool: ensure object paths are valid + gtlscertificate: fix certificate list parsing with trailing comments + g_str_has_prefix: improve efficiency with long strings + Added type check to GPermission public functions. + GApplication: Don't decrease use_count below 0 + networkmonitornetlink: fix IPv6 issues on Android + gresolver: Ensure GThreadedResolver always sets an error if resolution fails + gmacros.h: add G_GNUC_*_IGNORE_DEPRECATIONS macros for clang + networkaddress: fix parsing of uri with @ after authority + gvariant tests: workaround libc/compiler "issue" -- Iain Lane Tue, 23 Sep 2014 10:27:17 +0100 [ QA ] Under the terms of the MRE, you can assume the bugs are fixed. I suggest installing the update and then using your system as normal for the 10 day verification time. [ Regression potential ] One of the fixes could be bad. This is the first stable in this series and is a new release, so hasn't had much testing on its own, even if all of the fixes are in the unstable release. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1372847/+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 1381333] Re: [regression] platform-api fails to build with Mir 0.9: mir/client/private.h: No such file or directory
** Changed in: platform-api Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to platform-api in Ubuntu. https://bugs.launchpad.net/bugs/1381333 Title: [regression] platform-api fails to build with Mir 0.9: mir/client/private.h: No such file or directory Status in Mir: Won't Fix Status in Platform API: Fix Released Status in “platform-api” package in Ubuntu: Fix Released Bug description: [regression] platform-api fails to build with Mir 0.9: /home/dan/bzr/platform-api/trunk/src/ubuntu/application/common/mirclient/ubuntu_application_api_mirclient.cpp:37:32: fatal error: mir/client/private.h: No such file or directory #include ^ compilation terminated. I recall approving the offending change recently on the assumption no one was using this header. But that's obviously not true. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1381333/+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 1383858] Re: expr-simplify optimization slows click policy compilation
** Description changed: AppArmor has several optimization options that can be used to help speed up policy compiles for certain types of policy. Currently, we are using expr tree simplification option by default, which has dramatic affects on policy compiles for the evince profile. However, with click profiles not using expr tree simplification (ie, adding the '-O no-expr-simplify' option) can improve click policy generation by 44% (375 vs 210 seconds). On Krillin, the difference is even more substantial: 636 vs 233 seconds (63%). Short term for rtm is to to use '-O no-expr-simplify' when compiling policy in /var/lib/apparmor/profiles but leave /etc/apparmor.d alone. We - can do the same with click-apparmor. + can do the same with click-apparmor. Note: the fix for bug #1385947 must + be included with this fix. The long term fix is to adjust expr tree simplification to be more efficient (at least as fast as without) and drop the '-O no-expr- simplify' option. Justification: apparmor policy recompilation is not expected to happen as part of the normal user experience (see bug #1350598 for a lot of detail) and it is expected to only happen on upgrades from 14.10 to 15.04 or to fix very serious apparmor or apparmor policy bugs. None of these bugs are currently scheduled for OTA. However, *if* we ever need to fix one of these, policy will have to be recompiled. Choices: 1. do nothing for RTM since policy recompiles are expected to be rare, but do apply this change to 15.04. Policy is expected to be recompiled on upgrades to 15.04 and upgrades would use the new option 2. apply this change in OTA. This is problematic because this change alone will trigger a policy recompilation that would not otherwise be needed. Optionally, this change could accompany a severe bug fix Risk: The change consists of a small modification to the apparmor upstart job and a change to the arguments click-apparmor gives to apparmor_parser. The risk assessment is considered low because of the size of the change and the simple test case will immediately indicate if either were applied incorrectly. Test case: 1. run aa-status | wc -l and note the result 2. install the new apparmor and click-apparmor packages and verify there are no errors during installation 3. reboot 4. run aa-status | wc -l and compare to '1' 5. run 'sudo start apparmor' and make sure it finishes in a few seconds If they are the same, it indicates the upstart job is properly loading the profiles generated by click apparmor. While these changes may occur separately, landing them at the same time along with a regenerated custom tarball (for preinstalled policy) will reduce policy recompiles. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to click-apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1383858 Title: expr-simplify optimization slows click policy compilation Status in AppArmor Linux application security framework: Triaged Status in “apparmor” package in Ubuntu: Fix Released Status in “click-apparmor” package in Ubuntu: Fix Released Status in “apparmor” package in Ubuntu RTM: In Progress Status in “click-apparmor” package in Ubuntu RTM: In Progress Bug description: AppArmor has several optimization options that can be used to help speed up policy compiles for certain types of policy. Currently, we are using expr tree simplification option by default, which has dramatic affects on policy compiles for the evince profile. However, with click profiles not using expr tree simplification (ie, adding the '-O no-expr-simplify' option) can improve click policy generation by 44% (375 vs 210 seconds). On Krillin, the difference is even more substantial: 636 vs 233 seconds (63%). Short term for rtm is to to use '-O no-expr-simplify' when compiling policy in /var/lib/apparmor/profiles but leave /etc/apparmor.d alone. We can do the same with click-apparmor. Note: the fix for bug #1385947 must be included with this fix. The long term fix is to adjust expr tree simplification to be more efficient (at least as fast as without) and drop the '-O no-expr- simplify' option. Justification: apparmor policy recompilation is not expected to happen as part of the normal user experience (see bug #1350598 for a lot of detail) and it is expected to only happen on upgrades from 14.10 to 15.04 or to fix very serious apparmor or apparmor policy bugs. None of these bugs are currently scheduled for OTA. However, *if* we ever need to fix one of these, policy will have to be recompiled. Choices: 1. do nothing for RTM since policy recompiles are expected to be rare, but do apply this change to 15.04. Policy is expected to be recompiled on upgrades to 15.04 and upgrades would use the new option 2. apply this change in OTA. This is problematic because this c
[Touch-packages] [Bug 1385947] Re: specifying -O to parser causes the parser to not consider cache files
** Tags added: rtm14 touch-2014-10-28 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1385947 Title: specifying -O to parser causes the parser to not consider cache files Status in AppArmor Linux application security framework: Confirmed Status in “apparmor” package in Ubuntu: Fix Released Status in “apparmor” package in Ubuntu RTM: In Progress Bug description: If the cache files are up to date and I specify: /sbin/apparmor_parser --write-cache --replace --cache-loc=/var/cache/apparmor -- profile1 profile2 ... then the cache files in /var/cache/apparmor are used (good). However, if the cache files are up to date and I specify: /sbin/apparmor_parser --write-cache --replace --cache-loc=/var/cache/apparmor -O no-expr-simplify -- profile1 profile2 ... then the cache files in /var/cache/apparmor are all regenerated (not good). This needs to be fixed in order to use '-O no-expr-simplify' to fix bug #1383858. To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1385947/+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 1314367] Re: Flickering with Ubuntu 14.04 and nvidia card reappeared
Compiz works for me: Ubuntu 14.04 with updated Nvidia GeForce GTX 560/PCIe/SSE2 $ nvidia-smi Wed Oct 29 09:09:59 2014 +--+ | NVIDIA-SMI 340.29 Driver Version: 340.29 | |---+--+--+ | GPU NamePersistence-M| Bus-IdDisp.A | Volatile Uncorr. ECC | | Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. | |===+==+==| | 0 GeForce GTX 560 Off | :01:00.0 N/A | N/A | | 20% 38C P12N/A / N/A |336MiB / 1023MiB | N/A Default | +---+--+--+ +-+ | Compute processes: GPU Memory | | GPU PID Process name Usage | |=| |0Not Supported | +-+ -- 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/1314367 Title: Flickering with Ubuntu 14.04 and nvidia card reappeared Status in “xorg” package in Ubuntu: Confirmed Bug description: As requested in Bug #1310633 I'm opening a new bug. With a previous version of Ubuntu I already had this flickering. With additional options for the kernel module I was able to fix the flickering. options nvidia NVreg_RegistryDwords="PerfLevelSrc=0x" NVreg_Mobile=3 NVreg_ModifyDeviceFiles=0 With version 14.04 and the nvidia-331 (331.38-0ubuntu7) driver the flickering reappeared although the line is still present in options.conf. Using modprobe --resolve-alias nvidia I found the correct driver module name which in my case is nvidia_331. Changing the module name in options.conf to nvidia_331 X doesn't start anymore. Removing the NVreg_ModifyDeviceFiles option X is starting again, but does not solve the issue. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic 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.38 Wed Jan 8 19:32:30 PST 2014 GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: Unity Date: Tue Apr 29 21:09:41 2014 DistUpgraded: 2014-04-17 23:47:50,572 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.13.0-24-generic, x86_64: installed nvidia-331, 331.38, 3.13.0-24-generic, x86_64: installed vboxhost, 4.3.10, 3.13.0-24-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GT215GLM [Quadro FX 1800M] [10de:0cbc] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:1521] InstallationDate: Installed on 2012-11-17 (528 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MachineType: Hewlett-Packard HP EliteBook 8540w PccardctlStatus: Socket 0: 3.3V 16-bit PC Card Subdevice 0 (function 0) bound to driver "pata_pcmcia" ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=c6af930a-63f1-4015-9c42-bdde793e3e5a ro quiet splash SourcePackage: xorg UpgradeStatus: Upgraded to trusty on 2014-04-17 (11 days ago) dmi.bios.date: 09/13/2013 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68CVD Ver. F.24 dmi.board.name: 1521 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 32.35 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68CVDVer.F.24:bd09/13/2013:svnHewlett-Packard:pnHPEliteBook8540w:pvr:rvnHewlett-Packard:rn1521:rvrKBCVersion32.35:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 8540w dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1 version.ia32-libs: ia32-libs 20090808ubuntu36 version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dr
[Touch-packages] [Bug 1385261] Re: package initramfs-tools 0.103ubuntu8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: initramfs-tools (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1385261 Title: package initramfs-tools 0.103ubuntu8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in “initramfs-tools” package in Ubuntu: Confirmed Bug description: apt-cache policy initramfs-tools initramfs-tools: Installed: 0.103ubuntu8 Candidate: 0.103ubuntu8 Version table: *** 0.103ubuntu8 0 500 http://archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Package DistroRelease: Ubuntu 14.10 Package: initramfs-tools 0.103ubuntu8 ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4 Uname: Linux 3.16.0-23-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 Date: Fri Oct 24 12:46:37 2014 DuplicateSignature: package:initramfs-tools:0.103ubuntu8:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2014-10-21 (2 days ago) InstallationMedia: PackageArchitecture: all SourcePackage: initramfs-tools Title: package initramfs-tools 0.103ubuntu8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1385261/+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 873167] Re: Cannot drag emails between Thunderbird windows[regression]
** Tags removed: regression ** Tags added: regression-release -- 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/873167 Title: Cannot drag emails between Thunderbird windows[regression] Status in Unity: Triaged Status in “unity” package in Ubuntu: Triaged Status in “unity” source package in Precise: Triaged Bug description: When I drag an email from the inbox in Thunderbird to the Unity launcher, it no longer highlights Thunderbird. I used to be able to drag an email from the inbox to a composition window, to attach that email to the message being composed. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/873167/+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 1359439] Re: [ 7.287663] systemd-logind[1057]: Failed to start unit user@126.service: Unknown unit: user@126.service
Same issue here. Just upgrade from Ubuntu GNOME 14.04 to Ubuntu GNOME 14.10 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd-shim in Ubuntu. https://bugs.launchpad.net/bugs/1359439 Title: [7.287663] systemd-logind[1057]: Failed to start unit user@126.service: Unknown unit: user@126.service Status in “systemd-shim” package in Ubuntu: Triaged Status in “systemd-shim” package in Debian: Incomplete Bug description: [7.287663] systemd-logind[1057]: Failed to start unit user@126.service: Unknown unit: user@126.service [7.287677] systemd-logind[1057]: Failed to start user service: Unknown unit: user@126.service [7.293871] systemd-logind[1057]: New session c1 of user lightdm. [7.293902] systemd-logind[1057]: Linked /tmp/.X11-unix/X0 to /run/user/126/X11-display. [7.363706] ip_tables: (C) 2000-2006 Netfilter Core Team [7.421846] nf_conntrack version 0.5.0 (16384 buckets, 65536 max) [7.484529] IPv6: ADDRCONF(NETDEV_UP): virbr0: link is not ready [9.903052] wlan0: authenticate with c8:d7:19:22:21:ec [9.912429] wlan0: send auth to c8:d7:19:22:21:ec (try 1/3) [9.920181] wlan0: authenticated [9.924352] wlan0: associate with c8:d7:19:22:21:ec (try 1/3) [9.925709] wlan0: RX AssocResp from c8:d7:19:22:21:ec (capab=0x11 status=0 aid=2) [9.927753] wlan0: associated [9.927800] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 12.677104] systemd-logind[1057]: Failed to abandon scope session-c1.scope [ 12.677122] systemd-logind[1057]: Failed to abandon session scope: No such interface 'org.freedesktop.systemd1.Scope' on object at path /org/freedesktop/systemd1/unit/session_2dc1_2escope [ 12.683902] systemd-logind[1057]: Failed to start unit user@1000.service: Unknown unit: user@1000.service [ 12.683912] systemd-logind[1057]: Failed to start user service: Unknown unit: user@1000.service [ 12.685157] systemd-logind[1057]: New session c2 of user caravena. [ 12.685190] systemd-logind[1057]: Linked /tmp/.X11-unix/X0 to /run/user/1000/X11-display. [ 234.494462] systemd-logind[1057]: Failed to abandon scope session-c2.scope [ 234.494478] systemd-logind[1057]: Failed to abandon session scope: No such interface 'org.freedesktop.systemd1.Scope' on object at path /org/freedesktop/systemd1/unit/session_2dc2_2escope [ 235.514349] systemd-logind[1057]: New session c3 of user lightdm. [ 244.245908] systemd-logind[1057]: Failed to abandon scope session-c3.scope [ 244.245923] systemd-logind[1057]: Failed to abandon session scope: No such interface 'org.freedesktop.systemd1.Scope' on object at path /org/freedesktop/systemd1/unit/session_2dc3_2escope ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: systemd 208-7ubuntu4 [modified: usr/share/dbus-1/system-services/org.freedesktop.systemd1.service] ProcVersionSignature: Ubuntu 3.16.0-9.14-generic 3.16.1 Uname: Linux 3.16.0-9-generic x86_64 ApportVersion: 2.14.6-0ubuntu2 Architecture: amd64 CurrentDesktop: LXDE Date: Wed Aug 20 18:26:06 2014 InstallationDate: Installed on 2014-04-27 (115 days ago) InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1359439/+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 1059872] Re: Error formatting disk using disk utility
** Bug watch removed: Debian Bug tracker #732068 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=732068 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1059872 Title: Error formatting disk using disk utility Status in “udisks2” package in Ubuntu: Invalid Status in “util-linux” package in Ubuntu: Fix Released Status in “udisks2” source package in Trusty: Invalid Status in “util-linux” source package in Trusty: Triaged Status in “util-linux” package in Debian: Fix Released Bug description: Formatting a SD card using the disk utility fails with an error message "Error formatting disk - Error synchronizing after initial wipe: Timed out waiting for object (udisks-error-quark, 0)" Steps to repro: Launch the disk utility Plug a SD card into the computer Select the SD card and click on the gears icon at the top right of the application From the drop down menu, select "Format Disk" maintain the default setting and select Format Acknowledge warnings After format process has been going for a while, the error message shown above pops up Workaround: After selecting the SD card, instead of clicking the gear icon to format, click the partition in the "Volumes" section. Delete the partition ("minus" icon) Create a new partition - The underlying problem is that the "wipefs" tool from util-linux does not work any more. === TEST CASE === $ sudo modprobe scsi_debug dev_size_mb=200 # this creates a new /dev/sdX, usually /dev/sdb; check dmesg! # now create a partition table $ cat
[Touch-packages] [Bug 1313446] Re: window disappears on toggle shade
** Tags added: trusty utopic -- 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/1313446 Title: window disappears on toggle shade Status in Unity: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: I used Unity Tweak Tool to enable Toggle Shade using middle click. When I click to top of the window, it rolls up and disappears. A "ghost" outline of the window appears and the only way to get the window back is by using Alt-tab. Sometimes, when reselecting the window using Alt-tab, Ubuntu freezes (crashes) and an internal error is generated. It seems to be related to Compiz but I'm not sure. An error report was generated and sent. Description: Ubuntu 14.04 LTS (64-bit) Release: 14.04 unity-tweak-tool 0.0.6ubuntu1 I expected the window would "roll up" and I'd be left with the window's top bar like with previous versions of Ubuntu. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1313446/+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 974480] Re: Notification area whitelist is obsolete
There is systray whitelist patch and other patches for arch here https://github.com/chenxiaolong/Unity-for-Arch/tree/master/unity, right now i am compiling for utopic with this patch -- 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/974480 Title: Notification area whitelist is obsolete Status in Ayatana Design: Fix Released Status in Unity: Fix Released Status in “unity” package in Ubuntu: Fix Released Bug description: Mark has asked us to consider retiring the notification area whitelist for 12.10. The application indicator system has been in place for two years now, which should be long enough for applications to adopt it. If the whitelist was retired, Java and Wine would be hard-coded as the only software still able to use the menu bar as if it was a notification area, because their developers don't necessarily know that Ubuntu even exists. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/974480/+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 1383858] Re: expr-simplify optimization slows click policy compilation
This bug was fixed in the package apparmor - 2.8.98-0ubuntu3 --- apparmor (2.8.98-0ubuntu3) vivid; urgency=medium * debian/lib/apparmor/functions: disable expr tree simplification for /var/lib/apparmor/profiles (LP: #1383858) * parser-dont-skip-read-cache-with-optimizations.patch: don't skip read cache when specifying '-O' (LP: #1385947) -- Jamie StrandbogeTue, 28 Oct 2014 17:41:08 -0500 ** Changed in: apparmor (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 click-apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1383858 Title: expr-simplify optimization slows click policy compilation Status in AppArmor Linux application security framework: Triaged Status in “apparmor” package in Ubuntu: Fix Released Status in “click-apparmor” package in Ubuntu: Fix Released Status in “apparmor” package in Ubuntu RTM: In Progress Status in “click-apparmor” package in Ubuntu RTM: In Progress Bug description: AppArmor has several optimization options that can be used to help speed up policy compiles for certain types of policy. Currently, we are using expr tree simplification option by default, which has dramatic affects on policy compiles for the evince profile. However, with click profiles not using expr tree simplification (ie, adding the '-O no-expr-simplify' option) can improve click policy generation by 44% (375 vs 210 seconds). On Krillin, the difference is even more substantial: 636 vs 233 seconds (63%). Short term for rtm is to to use '-O no-expr-simplify' when compiling policy in /var/lib/apparmor/profiles but leave /etc/apparmor.d alone. We can do the same with click-apparmor. The long term fix is to adjust expr tree simplification to be more efficient (at least as fast as without) and drop the '-O no-expr- simplify' option. Justification: apparmor policy recompilation is not expected to happen as part of the normal user experience (see bug #1350598 for a lot of detail) and it is expected to only happen on upgrades from 14.10 to 15.04 or to fix very serious apparmor or apparmor policy bugs. None of these bugs are currently scheduled for OTA. However, *if* we ever need to fix one of these, policy will have to be recompiled. Choices: 1. do nothing for RTM since policy recompiles are expected to be rare, but do apply this change to 15.04. Policy is expected to be recompiled on upgrades to 15.04 and upgrades would use the new option 2. apply this change in OTA. This is problematic because this change alone will trigger a policy recompilation that would not otherwise be needed. Optionally, this change could accompany a severe bug fix Risk: The change consists of a small modification to the apparmor upstart job and a change to the arguments click-apparmor gives to apparmor_parser. The risk assessment is considered low because of the size of the change and the simple test case will immediately indicate if either were applied incorrectly. Test case: 1. run aa-status | wc -l and note the result 2. install the new apparmor and click-apparmor packages and verify there are no errors during installation 3. reboot 4. run aa-status | wc -l and compare to '1' 5. run 'sudo start apparmor' and make sure it finishes in a few seconds If they are the same, it indicates the upstart job is properly loading the profiles generated by click apparmor. While these changes may occur separately, landing them at the same time along with a regenerated custom tarball (for preinstalled policy) will reduce policy recompiles. To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1383858/+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 1385947] Re: specifying -O to parser causes the parser to not consider cache files
This bug was fixed in the package apparmor - 2.8.98-0ubuntu3 --- apparmor (2.8.98-0ubuntu3) vivid; urgency=medium * debian/lib/apparmor/functions: disable expr tree simplification for /var/lib/apparmor/profiles (LP: #1383858) * parser-dont-skip-read-cache-with-optimizations.patch: don't skip read cache when specifying '-O' (LP: #1385947) -- Jamie StrandbogeTue, 28 Oct 2014 17:41:08 -0500 ** Changed in: apparmor (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 apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1385947 Title: specifying -O to parser causes the parser to not consider cache files Status in AppArmor Linux application security framework: Confirmed Status in “apparmor” package in Ubuntu: Fix Released Status in “apparmor” package in Ubuntu RTM: In Progress Bug description: If the cache files are up to date and I specify: /sbin/apparmor_parser --write-cache --replace --cache-loc=/var/cache/apparmor -- profile1 profile2 ... then the cache files in /var/cache/apparmor are used (good). However, if the cache files are up to date and I specify: /sbin/apparmor_parser --write-cache --replace --cache-loc=/var/cache/apparmor -O no-expr-simplify -- profile1 profile2 ... then the cache files in /var/cache/apparmor are all regenerated (not good). This needs to be fixed in order to use '-O no-expr-simplify' to fix bug #1383858. To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1385947/+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 1383858] Re: expr-simplify optimization slows click policy compilation
** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to click-apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1383858 Title: expr-simplify optimization slows click policy compilation Status in AppArmor Linux application security framework: Triaged Status in “apparmor” package in Ubuntu: Fix Committed Status in “click-apparmor” package in Ubuntu: Fix Released Status in “apparmor” package in Ubuntu RTM: In Progress Status in “click-apparmor” package in Ubuntu RTM: In Progress Bug description: AppArmor has several optimization options that can be used to help speed up policy compiles for certain types of policy. Currently, we are using expr tree simplification option by default, which has dramatic affects on policy compiles for the evince profile. However, with click profiles not using expr tree simplification (ie, adding the '-O no-expr-simplify' option) can improve click policy generation by 44% (375 vs 210 seconds). On Krillin, the difference is even more substantial: 636 vs 233 seconds (63%). Short term for rtm is to to use '-O no-expr-simplify' when compiling policy in /var/lib/apparmor/profiles but leave /etc/apparmor.d alone. We can do the same with click-apparmor. The long term fix is to adjust expr tree simplification to be more efficient (at least as fast as without) and drop the '-O no-expr- simplify' option. Justification: apparmor policy recompilation is not expected to happen as part of the normal user experience (see bug #1350598 for a lot of detail) and it is expected to only happen on upgrades from 14.10 to 15.04 or to fix very serious apparmor or apparmor policy bugs. None of these bugs are currently scheduled for OTA. However, *if* we ever need to fix one of these, policy will have to be recompiled. Choices: 1. do nothing for RTM since policy recompiles are expected to be rare, but do apply this change to 15.04. Policy is expected to be recompiled on upgrades to 15.04 and upgrades would use the new option 2. apply this change in OTA. This is problematic because this change alone will trigger a policy recompilation that would not otherwise be needed. Optionally, this change could accompany a severe bug fix Risk: The change consists of a small modification to the apparmor upstart job and a change to the arguments click-apparmor gives to apparmor_parser. The risk assessment is considered low because of the size of the change and the simple test case will immediately indicate if either were applied incorrectly. Test case: 1. run aa-status | wc -l and note the result 2. install the new apparmor and click-apparmor packages and verify there are no errors during installation 3. reboot 4. run aa-status | wc -l and compare to '1' 5. run 'sudo start apparmor' and make sure it finishes in a few seconds If they are the same, it indicates the upstart job is properly loading the profiles generated by click apparmor. While these changes may occur separately, landing them at the same time along with a regenerated custom tarball (for preinstalled policy) will reduce policy recompiles. To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1383858/+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 1335289] Re: Shutdown timer regression
I would love to have the 60 second "countdown" feature back (for logging out, shutting down or restarting). This has saved me on several occasions (e.g. when my KVM switch became unresponsive, the video display became corrupted, or a wireless keyboard/mouse lost the connection, etc - just push the power button and you knew the system would automatically shutdown in a minute's time). This feature is available in other desktops still (e.g. KDE, Cinnamon), so it would be great to have it back in Unity too. Even if it was a "tick box" option somewhere in System Settings to turn it on (i.e. optional). Many thanks. Kind regards, Adam. -- 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/1335289 Title: Shutdown timer regression Status in Unity: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: Description: Ubuntu 14.04 LTS Release: 14.04 In older (12.*) versions of Ubuntu, pressing the physical power button on a computer would popup a dialog box asking the user what to do, along with a timer counting down from 60 seconds. After the time elapsed, the computer would shutdown. This feature is now missing in 14.*. As a user who absolutely loved this feature, I consider this a regression. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1335289/+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 1355813] Re: LXC containers reset bridge MTU on start/restart
i've seen reference to you can't really set a bridge mtu, you have to set it for all the containers on the bridge, ie. bridges take the lowest mtu of their interfaces. so instead we have to set all the containers mtu. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1355813 Title: LXC containers reset bridge MTU on start/restart Status in juju-core: Incomplete Status in MAAS: Incomplete Status in “lxc” package in Ubuntu: Incomplete Bug description: Context: juju + MAAS deployed OpenStack environment, misc services deployed under LXC on the bootstrap node, interfaces configured for jumbo frames - note that I had to manually set the LXC container interfaces to mtu 9000 before the bridge would do the same. Action: Reboot one of the containers; MTU on br0 resets from 9000 -> 1500. This feels like more of a 'we need a better way to orchestrate MTU configuration across different services' so raising tasks for MAAS and Juju as well. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lxc 1.0.5-0ubuntu0.1 ProcVersionSignature: User Name 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 Date: Tue Aug 12 13:26:00 2014 KernLog: SourcePackage: lxc UpgradeStatus: No upgrade log present (probably fresh install) defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up lxc.network.hwaddr = 00:16:3e:xx:xx:xx lxcsyslog: To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1355813/+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 1386934] [NEW] cpu scaling frequency limited when on ac power
Public bug reported: When I installed Utopic it changed the default driver to intel pstate. Ever since then my cpu speed has been locked to 800MHz while on AC power. My cpu is rated for 1.8GHz. Manually setting scaling_max_freq only has an effect when my laptop is unplugged. This is a duplicate of https://bugs.launchpad.net/ubuntu/+source/powermgmt-base/+bug/744429 His reason for closing it makes no sense. He (and I) had higher clock speeds OFF of AC power, so power limitations cannot be the explanation. Ubuntu 14.10 ** Affects: powermgmt-base (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to powermgmt-base in Ubuntu. https://bugs.launchpad.net/bugs/1386934 Title: cpu scaling frequency limited when on ac power Status in “powermgmt-base” package in Ubuntu: New Bug description: When I installed Utopic it changed the default driver to intel pstate. Ever since then my cpu speed has been locked to 800MHz while on AC power. My cpu is rated for 1.8GHz. Manually setting scaling_max_freq only has an effect when my laptop is unplugged. This is a duplicate of https://bugs.launchpad.net/ubuntu/+source/powermgmt-base/+bug/744429 His reason for closing it makes no sense. He (and I) had higher clock speeds OFF of AC power, so power limitations cannot be the explanation. Ubuntu 14.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/powermgmt-base/+bug/1386934/+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 1385947] Re: specifying -O to parser causes the parser to not consider cache files
** Changed in: apparmor (Ubuntu) Status: Confirmed => Fix Committed ** Changed in: apparmor (Ubuntu RTM) Status: Confirmed => In Progress ** Changed in: apparmor (Ubuntu RTM) Assignee: (unassigned) => Jamie Strandboge (jdstrand) ** Changed in: apparmor (Ubuntu) Importance: Undecided => Medium ** Changed in: apparmor (Ubuntu) Assignee: (unassigned) => Jamie Strandboge (jdstrand) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1385947 Title: specifying -O to parser causes the parser to not consider cache files Status in AppArmor Linux application security framework: Confirmed Status in “apparmor” package in Ubuntu: Fix Committed Status in “apparmor” package in Ubuntu RTM: In Progress Bug description: If the cache files are up to date and I specify: /sbin/apparmor_parser --write-cache --replace --cache-loc=/var/cache/apparmor -- profile1 profile2 ... then the cache files in /var/cache/apparmor are used (good). However, if the cache files are up to date and I specify: /sbin/apparmor_parser --write-cache --replace --cache-loc=/var/cache/apparmor -O no-expr-simplify -- profile1 profile2 ... then the cache files in /var/cache/apparmor are all regenerated (not good). This needs to be fixed in order to use '-O no-expr-simplify' to fix bug #1383858. To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1385947/+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 1383858] Re: expr-simplify optimization slows click policy compilation
** Changed in: apparmor (Ubuntu) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1383858 Title: expr-simplify optimization slows click policy compilation Status in AppArmor Linux application security framework: Triaged Status in “apparmor” package in Ubuntu: Fix Committed Status in “click-apparmor” package in Ubuntu: Fix Released Status in “apparmor” package in Ubuntu RTM: In Progress Status in “click-apparmor” package in Ubuntu RTM: In Progress Bug description: AppArmor has several optimization options that can be used to help speed up policy compiles for certain types of policy. Currently, we are using expr tree simplification option by default, which has dramatic affects on policy compiles for the evince profile. However, with click profiles not using expr tree simplification (ie, adding the '-O no-expr-simplify' option) can improve click policy generation by 44% (375 vs 210 seconds). On Krillin, the difference is even more substantial: 636 vs 233 seconds (63%). Short term for rtm is to to use '-O no-expr-simplify' when compiling policy in /var/lib/apparmor/profiles but leave /etc/apparmor.d alone. We can do the same with click-apparmor. The long term fix is to adjust expr tree simplification to be more efficient (at least as fast as without) and drop the '-O no-expr- simplify' option. Justification: apparmor policy recompilation is not expected to happen as part of the normal user experience (see bug #1350598 for a lot of detail) and it is expected to only happen on upgrades from 14.10 to 15.04 or to fix very serious apparmor or apparmor policy bugs. None of these bugs are currently scheduled for OTA. However, *if* we ever need to fix one of these, policy will have to be recompiled. Choices: 1. do nothing for RTM since policy recompiles are expected to be rare, but do apply this change to 15.04. Policy is expected to be recompiled on upgrades to 15.04 and upgrades would use the new option 2. apply this change in OTA. This is problematic because this change alone will trigger a policy recompilation that would not otherwise be needed. Optionally, this change could accompany a severe bug fix Risk: The change consists of a small modification to the apparmor upstart job and a change to the arguments click-apparmor gives to apparmor_parser. The risk assessment is considered low because of the size of the change and the simple test case will immediately indicate if either were applied incorrectly. Test case: 1. run aa-status | wc -l and note the result 2. install the new apparmor and click-apparmor packages and verify there are no errors during installation 3. reboot 4. run aa-status | wc -l and compare to '1' 5. run 'sudo start apparmor' and make sure it finishes in a few seconds If they are the same, it indicates the upstart job is properly loading the profiles generated by click apparmor. While these changes may occur separately, landing them at the same time along with a regenerated custom tarball (for preinstalled policy) will reduce policy recompiles. To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1383858/+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 1348039] Re: shim does not implement 'Subscribe' method called by logind
4th and 5th freeze, the later after connecting to ethernet, so that didn't help. gpgv sez package signature DSA FBB75451 kthanxbye -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd-shim in Ubuntu. https://bugs.launchpad.net/bugs/1348039 Title: shim does not implement 'Subscribe' method called by logind Status in “systemd-shim” package in Ubuntu: Fix Released Bug description: Get that error logged at the end of the dmesg file. That error seems to have no sad effect on the system: [ 30.793181] systemd-logind[1006]: Failed to enable subscription: No such method 'Subscribe' ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: systemd 208-6ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-4.9-generic 3.16.0-rc5 Uname: Linux 3.16.0-4-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.14.4-0ubuntu2 Architecture: i386 CurrentDesktop: GNOME Date: Thu Jul 24 07:25:46 2014 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1348039/+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 1348039] Re: shim does not implement 'Subscribe' method called by logind
other details: booting with splash disabled so as to see process, on desktop with no ethernet connection (would the later make a difference? too noob to know) dunno what else to share that would be of any help, or unusual. 4 monitors. A rather oldish processor, AMD Phenom II X4 940 3 GHz third freeze achieved. I wanted to have a clean install. I guess I'll go back to upgrading from 12.04 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd-shim in Ubuntu. https://bugs.launchpad.net/bugs/1348039 Title: shim does not implement 'Subscribe' method called by logind Status in “systemd-shim” package in Ubuntu: Fix Released Bug description: Get that error logged at the end of the dmesg file. That error seems to have no sad effect on the system: [ 30.793181] systemd-logind[1006]: Failed to enable subscription: No such method 'Subscribe' ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: systemd 208-6ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-4.9-generic 3.16.0-rc5 Uname: Linux 3.16.0-4-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.14.4-0ubuntu2 Architecture: i386 CurrentDesktop: GNOME Date: Thu Jul 24 07:25:46 2014 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1348039/+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 1348039] Re: shim does not implement 'Subscribe' method called by logind
During install of Kubuntu Utopic Unicorn Release AMD64 20141022.1 from DVD confirm bug sighted. Computer froze twice on "Failed to start... user@999.service let's go for a third freeze? :-) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd-shim in Ubuntu. https://bugs.launchpad.net/bugs/1348039 Title: shim does not implement 'Subscribe' method called by logind Status in “systemd-shim” package in Ubuntu: Fix Released Bug description: Get that error logged at the end of the dmesg file. That error seems to have no sad effect on the system: [ 30.793181] systemd-logind[1006]: Failed to enable subscription: No such method 'Subscribe' ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: systemd 208-6ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-4.9-generic 3.16.0-rc5 Uname: Linux 3.16.0-4-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.14.4-0ubuntu2 Architecture: i386 CurrentDesktop: GNOME Date: Thu Jul 24 07:25:46 2014 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1348039/+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 1365079] Re: apport should gather package information about click packages
Ah, I'd forgotten that all hooks in /usr/share/apport/general-hooks/ are run. -- 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/1365079 Title: apport should gather package information about click packages Status in “apport” package in Ubuntu: Triaged Bug description: Bug 1324853 was about there being a click command line switch for gathering information about a click package. This now exists and works: click info /opt/click.ubuntu.com/com.ubuntu.developer.jdstrand.blabble/current/blabble.qml { "architecture": "all", "description": "Word search game", "framework": "ubuntu-sdk-14.10-qml-dev3", "hooks": { "blabble": { "apparmor": "blabble.json", "desktop": "blabble.desktop" } }, "installed-size": "21615", "maintainer": "Jamie Strandboge ", "name": "com.ubuntu.developer.jdstrand.blabble", "title": "Blabble", "version": "0.5" } While the error tracker retracers will not be able to retrace these crashes, it would still be good if we could assign them to a package and include the package version. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1365079/+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 1386872] Re: Incorrect termination Firefox when shutdown Ubuntu
Same on Ubuntu 14.04 64bit -- 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/1386872 Title: Incorrect termination Firefox when shutdown Ubuntu Status in “unity” package in Ubuntu: Confirmed Bug description: 1. In Firefox go to Preference -> General tab, choose Show my windows and tabs from last time in When Firefox starts field. 2. Shutdown Ubuntu 3. Start Ubuntu 4. Open Firefox Actual result: Firefox opens with message "Firefox was not closed properly" ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20141016-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4 Uname: Linux 3.16.0-23-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Oct 28 22:20:52 2014 InstallationDate: Installed on 2014-10-25 (3 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1386872/+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 1382039] Re: [TOPBLOCKER] Apps scope empty on boot
It's in rtm silo 15. Saviq will land tomorrow. -- 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/1382039 Title: [TOPBLOCKER] Apps scope empty on boot Status in “qtmir” package in Ubuntu: Triaged Status in “unity-scope-click” package in Ubuntu: Invalid Status in “unity-scopes-api” package in Ubuntu: Invalid Status in “unity-scopes-shell” package in Ubuntu: Invalid Status in “unity8” package in Ubuntu: Invalid Bug description: Several people reported today that the apps scope came up empty on boot. A pull-to-refresh makes results come in again. Note: it seems the problem is more likely to happen if you wait for at least 1 minute after reboot, and then unlock your device. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtmir/+bug/1382039/+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 1170647] Re: After minimizing an external media, clicking on the "Files" icon on the Launcher doesn't restore the minimized window, but opens a new one
If you change mount folder from /media/username to /mnt folder it works as expected. I tested it only on Ubuntu 14.10 Unicorn For trash, though, I found no solution -- 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/1170647 Title: After minimizing an external media, clicking on the "Files" icon on the Launcher doesn't restore the minimized window, but opens a new one Status in One Hundred Papercuts: Triaged Status in Unity: Triaged Status in “unity” package in Ubuntu: Triaged Bug description: *** ISSUE *** HOW TO REPRODUCE 1. Connect a removable media to the computer. 2. On the launcher, click on the "Files" icon. 3. On the left sidebar, click on the removable media icon or the trash. 4. Minimize the window. 5. Click on the "Files" icon. EXPECTED BEHAVIOUR - The Files window to be maximized. REAL BEHAVIOUR - A new window is opened. RELEVANT DETAILS - The only way to navigate between windows at this moment is to use the "control + tabulation" key combination, or to click again on the "Files" icon so windows are exposed. ** SOLUTION ** WORK-AROUND - On the launcher, left click on the "Files" icon and select the "unlock from Launcher" option. FIX - The launcher icon for "Files" to be treated the same way as if it was unlocked. REGRESSION POTENTIAL - Clicking on the "Files" icon won't send the user to its home folder, but to the latest opened Files window. TECHNICAL INFO ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: nautilus 1:3.6.3-0ubuntu16 ProcVersionSignature: Ubuntu 3.8.0-18.28-generic 3.8.6 Uname: Linux 3.8.0-18-generic i686 ApportVersion: 2.9.2-0ubuntu8 Architecture: i386 Date: Fri Apr 19 11:33:13 2013 EcryptfsInUse: Yes GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b"'814x493+136+38'" b'org.gnome.nautilus.window-state' b'sidebar-width' b'182' InstallationDate: Installed on 2011-07-23 (635 days ago) InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110426) MarkForUpload: True SourcePackage: nautilus UpgradeStatus: Upgraded to raring on 2013-04-14 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1170647/+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 1382039] Re: [TOPBLOCKER] Apps scope empty on boot
There is a fix in qtmir already, but I suspect it hasn't made it into the image yet? -- 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/1382039 Title: [TOPBLOCKER] Apps scope empty on boot Status in “qtmir” package in Ubuntu: Triaged Status in “unity-scope-click” package in Ubuntu: Invalid Status in “unity-scopes-api” package in Ubuntu: Invalid Status in “unity-scopes-shell” package in Ubuntu: Invalid Status in “unity8” package in Ubuntu: Invalid Bug description: Several people reported today that the apps scope came up empty on boot. A pull-to-refresh makes results come in again. Note: it seems the problem is more likely to happen if you wait for at least 1 minute after reboot, and then unlock your device. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtmir/+bug/1382039/+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 1382595] Re: [TOPBLOCKER] /usr/lib/arm-linux-gnueabihf/indicator-network/indicator-network-service:indicator-network-service: pthread_mutex_lock.c:80: __pthread_mutex_lock: Asser
Added missing date tag ** Tags removed: rtm-14.09 ** Tags added: touch-2014-10-30 ** Changed in: location-service (Ubuntu) Status: Confirmed => In Progress ** Changed in: dbus-cpp (Ubuntu RTM) Status: Confirmed => In Progress ** Changed in: indicator-network (Ubuntu) Status: Triaged => In Progress -- 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/1382595 Title: [TOPBLOCKER] /usr/lib/arm-linux-gnueabihf/indicator-network/indicator- network-service:indicator-network-service: pthread_mutex_lock.c:80: __pthread_mutex_lock: Assertion `mutex->__data.__owner == 0' failed. Status in DBus C++: Confirmed Status in “dbus-cpp” package in Ubuntu: Confirmed Status in “indicator-network” package in Ubuntu: In Progress Status in “location-service” package in Ubuntu: In Progress Status in “dbus-cpp” package in Ubuntu RTM: In Progress Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding indicator-network. This problem was most recently seen with version 0.5.1+14.10.20141015-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/ecc14b5d54f3e0a0f1720cad0c623f81c8a16988 contains more details. steps to reproduce: (need to trigger race condition) 1. pull down network indicator 2. toggle flight mode on and off quickly a few times 3. click sim card 1 and 2 4. toggle flight mode 5. swipe up close indicators 6. repeat steps 1-5 until crash occurs expected results: no crash happens actual results: Bluetooth indicator blinks (appear and disappear) in indicator bar at top of screen, and network indicator crashes. additional info: eventually the bluetooth indicator appears stable in the indicators at the top of the screen. To manage notifications about this bug go to: https://bugs.launchpad.net/dbus-cpp/+bug/1382595/+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 1369573] Re: camera_app.tests.test_flash.TestCameraFlash.test_cycle_video_flash fails sometimes due to wrong geometry of the flash icon
** Changed in: camera-app Status: New => Confirmed ** Changed in: camera-app (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to camera-app in Ubuntu. https://bugs.launchpad.net/bugs/1369573 Title: camera_app.tests.test_flash.TestCameraFlash.test_cycle_video_flash fails sometimes due to wrong geometry of the flash icon Status in Camera App: Confirmed Status in “camera-app” package in Ubuntu: Confirmed Bug description: test failure: camera_app.tests.test_flash.TestCameraFlash.test_cycle_video_flash The above test fails because the settingsProperty property is not reliable enough. Sometimes the test ends up clicking 'location' icon which results in the test failure. We need to find a better way to select this icon. test-log: {{{ 13:17:04.391 WARNING testcase:115 - No tracing available - install the python-autopilot-trace package! 13:17:04.406 WARNING testcase:162 - Process manager backend unavailable, application snapshot support disabled. 13:17:05.915 INFO _launcher:280 - Attempting to launch click application '(default)' from click package 'com.ubuntu.camera' and URIs '' 13:17:06.878 INFO _launcher:120 - Attempting to launch application 'com.ubuntu.camera_camera_3.0.0.389' with URIs '' via upstart-app-launch 13:17:11.270 DEBUG _common:45 - Moving to object's globalRect coordinates. 13:17:11.271 DEBUG _uinput:470 - Tapping at: 45,45 13:17:11.419 INFO logging:45 - Panel: Open the panel if it's not already opened. Arguments (). Keyword arguments: {}. 13:17:11.769 DEBUG _uinput:541 - Dragging from 384,1279 to 384,1118 13:17:14.027 DEBUG _common:45 - Moving to object's globalRect coordinates. 13:17:14.028 DEBUG _uinput:470 - Tapping at: 123,1163 13:17:14.726 DEBUG dbus:352 - Selecting objects of type OptionValueButton with attributes: {} 13:17:14.926 DEBUG _common:45 - Moving to object's globalRect coordinates. 13:17:14.927 DEBUG _uinput:470 - Tapping at: 186,947 }}} Traceback (most recent call last): File "/home/phablet/autopilot/camera_app/tests/test_flash.py", line 86, in test_cycle_video_flash self.assertThat(flash_button.iconName, Equals("torch-on")) File "/usr/lib/python3/dist-packages/testtools/testcase.py", line 423, in assertThat raise mismatch_error testtools.matchers._impl.MismatchError: 'torch-on' != 'torch-off' ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: camera-app 3.0.0+14.10.20140908-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-14.20-generic 3.16.2 Uname: Linux 3.16.0-14-generic x86_64 ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Mon Sep 15 19:00:25 2014 InstallationDate: Installed on 2014-06-14 (92 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140610.1) SourcePackage: camera-app UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/camera-app/+bug/1369573/+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 1355173] Re: Switching windows with a Trusted Prompt Session active loses the trusted prompt session
** Changed in: unity8 (Ubuntu) Importance: Critical => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-system-settings- online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1355173 Title: Switching windows with a Trusted Prompt Session active loses the trusted prompt session Status in Qt integration with the Mir display server: In Progress Status in Online Accounts setup for Ubuntu Touch: Confirmed Status in “pay-service” package in Ubuntu: New Status in “trust-store” package in Ubuntu: New Status in “ubuntu-system-settings-online-accounts” package in Ubuntu: Confirmed Status in “unity8” package in Ubuntu: Triaged Status in “unity8” package in Ubuntu RTM: Triaged Bug description: When we create a trusted prompt session over an application, let's say a small dialog, and then switch applications, when we switch back to the original application the dialog is not overlayed on top of the original application. The program providing the dialog seems happy, and is still running, but visually it is not there. We notice this when using the payments UI which overlays ontop of the dash. In some cases we need to show Online Accounts which runs as an independent application and causes a switching behavior. When returning back to the dash the Payment UI is not visible. It also happens if the Payment UI is visible and you switch applications using the right swipe. To manage notifications about this bug go to: https://bugs.launchpad.net/qtmir/+bug/1355173/+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 1368748] Re: The screen disappears after lock/unlock
*** This bug is a duplicate of bug 1355173 *** https://bugs.launchpad.net/bugs/1355173 ** Tags removed: rtm14 touch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-system-settings- online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1368748 Title: The screen disappears after lock/unlock Status in “ubuntu-system-settings-online-accounts” package in Ubuntu: New Bug description: Credential screen is gone after locking/unlocking the phone. Test case - Go to System Settings > Accounts. - Click on Add account. - Click on Ubuntu One. - With the credentials screen in foreground, lock the phone. - Unlock. Expected result - Credential screen appears. Actual result - Ubuntu One Credential screen is gone. - Accounts screen appears instead, and the Ubuntu One option is disabled. - Going back to System Settings and returning to Accounts doesn't show again the window. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings-online-accounts/+bug/1368748/+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 1386456] Re: Unable to install fglrx or fglrx-updates in software-properties
*** This bug is a duplicate of bug 1382563 *** https://bugs.launchpad.net/bugs/1382563 ** This bug has been marked a duplicate of bug 1382563 Cant install proprietary drivers/fglrx -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1386456 Title: Unable to install fglrx or fglrx-updates in software-properties Status in “software-properties” package in Ubuntu: New Bug description: I am unable to select the fglrx or fglrx-updates package under additional drivers. The output from software-properties-gtk --debug is: Warning: install transaction not completed successfully: Transaction failed: Package dependencies cannot be resolved The following packages have unmet dependencies: fglrx: Depends: libqtcore4 (>= 4:4.8.4) but 4:4.8.6+git49-gbc62005+dfsg-1ubuntu1 is to be installed Depends: xorg-video-abi-18 but it is a virtual package Warning: install transaction not completed successfully: Transaction failed: Package dependencies cannot be resolved The following packages have unmet dependencies: fglrx-updates: Depends: libqtcore4 (>= 4:4.8.4) but 4:4.8.6+git49-gbc62005+dfsg-1ubuntu1 is to be installed Depends: xorg-video-abi-18 but it is a virtual package ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: software-properties-gtk 0.94 ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4 Uname: Linux 3.16.0-23-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Oct 28 01:19:41 2014 InstallationDate: Installed on 2014-03-10 (231 days ago) InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Release amd64 (20131017) PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: Upgraded to utopic on 2014-09-17 (40 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1386456/+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 1386898] [NEW] Intempestive wifi disconnections
Public bug reported: I can see intempestive network disconnection when using the wireless interface. I don't know how to attach my dmesg with this interface tough. ** Affects: cordova-ubuntu (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cordova-ubuntu in Ubuntu. https://bugs.launchpad.net/bugs/1386898 Title: Intempestive wifi disconnections Status in “cordova-ubuntu” package in Ubuntu: New Bug description: I can see intempestive network disconnection when using the wireless interface. I don't know how to attach my dmesg with this interface tough. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cordova-ubuntu/+bug/1386898/+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 1376416] Re: apparmor denial for yelp
** Changed in: unity-scopes-api (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 unity-scopes-api in Ubuntu. https://bugs.launchpad.net/bugs/1376416 Title: apparmor denial for yelp Status in “unity-scopes-api” package in Ubuntu: Fix Released Bug description: In a recent test run, the following denial was observed: Oct 1 18:13:05 ubuntu-phablet kernel: [ 130.968843] (3)[6618:com.ubuntu.yelp]type=1400 audit(1412187185.260:127): apparmor="DENIED" operation="mkdir" profile="com.ubuntu.yelp_yelp_1.0.26" name="/home/phablet/.local/share/unity-scopes/com.ubuntu.yelp_yelp/" pid=6618 comm="com.ubuntu.yelp" requested_mask="c" denied_mask="c" fsuid=32011 ouid=32011 Yelp is using the wrong directory. It is using: @{HOME}/.local/share/unity-scopes/@{APP_PKGNAME}_@{APP_APPNAME} but apparmor policy says to use: @{HOME}/.local/share/unity-scopes/leaf-net/@{APP_PKGNAME} Note: this is a different bug than the one dealing with XDG_RUNTIME_DIR paths, where we do use @{APP_APPNAME}. Adding rtm14 tag with High priority since this seems to affect scopes in the store. Please readjust as necessary. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1376416/+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 1386898] Re: Intempestive wifi disconnections
** Attachment added: "oops.txt" https://bugs.launchpad.net/ubuntu/+source/cordova-ubuntu/+bug/1386898/+attachment/4247587/+files/oops.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cordova-ubuntu in Ubuntu. https://bugs.launchpad.net/bugs/1386898 Title: Intempestive wifi disconnections Status in “cordova-ubuntu” package in Ubuntu: New Bug description: I can see intempestive network disconnection when using the wireless interface. I don't know how to attach my dmesg with this interface tough. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cordova-ubuntu/+bug/1386898/+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 1386872] Re: Incorrect termination Firefox when shutdown Ubuntu
This happens not only with FF, but with Chrome too. But not always. It seems that the system shuts doen too fast and does not wait for applications to terminate. -- 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/1386872 Title: Incorrect termination Firefox when shutdown Ubuntu Status in “unity” package in Ubuntu: Confirmed Bug description: 1. In Firefox go to Preference -> General tab, choose Show my windows and tabs from last time in When Firefox starts field. 2. Shutdown Ubuntu 3. Start Ubuntu 4. Open Firefox Actual result: Firefox opens with message "Firefox was not closed properly" ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20141016-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4 Uname: Linux 3.16.0-23-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Oct 28 22:20:52 2014 InstallationDate: Installed on 2014-10-25 (3 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1386872/+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 1361688] Re: settings: string's defaultValue not displayed
*** This bug is a duplicate of bug 1381010 *** https://bugs.launchpad.net/bugs/1381010 ** Changed in: unity-scopes-api (Ubuntu) Importance: Undecided => High ** Changed in: unity-scopes-api (Ubuntu) Assignee: (unassigned) => Michi Henning (michihenning) ** Also affects: unity-scopes-shell (Ubuntu) Importance: Undecided Status: New ** Changed in: unity-scopes-api (Ubuntu) Status: New => Invalid ** This bug has been marked a duplicate of bug 1381010 Cannot get Chinese string in the scope setting -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scopes-api in Ubuntu. https://bugs.launchpad.net/bugs/1361688 Title: settings: string's defaultValue not displayed Status in The Savilerow project: New Status in “unity-scopes-api” package in Ubuntu: Invalid Status in “unity-scopes-shell” package in Ubuntu: New Bug description: I have a localized settings.ini file with only a string. The displayName is displayed localized, as expected. The defaultValue is NOT displayed in the input box, neither localized nor not localized. Here's the contents of the settings ini: [sample] type=string defaultValue=Value defaultValue[es]=Significando displayName=Display name displayName[es]=Nombre para mostrar Please see screenshot attachment. Note also the input box is not sized correctly to fit the default text it displays. To manage notifications about this bug go to: https://bugs.launchpad.net/savilerow/+bug/1361688/+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 1386872] Re: Incorrect termination Firefox when shutdown Ubuntu
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: unity (Ubuntu) Status: New => Confirmed -- 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/1386872 Title: Incorrect termination Firefox when shutdown Ubuntu Status in “unity” package in Ubuntu: Confirmed Bug description: 1. In Firefox go to Preference -> General tab, choose Show my windows and tabs from last time in When Firefox starts field. 2. Shutdown Ubuntu 3. Start Ubuntu 4. Open Firefox Actual result: Firefox opens with message "Firefox was not closed properly" ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20141016-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4 Uname: Linux 3.16.0-23-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Oct 28 22:20:52 2014 InstallationDate: Installed on 2014-10-25 (3 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1386872/+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 1386767] Re: single tap causes many letters
Just noting that this could be a mir bug or the touch driver being too sensitive sometimes. I have seen these symptoms and more without changing any settings. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu. https://bugs.launchpad.net/bugs/1386767 Title: single tap causes many letters Status in “ubuntu-keyboard” package in Ubuntu: New Bug description: Sometimes, a single key press in OSK causes multiple keys to appear. It is hard to reproduce, but here is what I just did that caused it: * I installed with --wipe brand new rtm krillin image 133. * In Welcome Wizard, I selected English as my language and completed to normal shell. * in System Settings > Languages, I selected Spanish as display language, which caused a reboot * On reboot, I entered the scopes "dashboard" (not the "dashboard" scope, but the place where you see Favorites v All and a search field) * I tapped the search field, which display the OSK. (Note, the keyboard layout is still English.) * In OSK, I tapped the globe key to switch layouts and chose Spanish Now, I got weird double keys on single presses. Bad enough to be unusable. However, after switch OSK back to English and back to spanish I don't get them, so I wonder whether it has to do with switching the system's runtime locale. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyboard/+bug/1386767/+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 1370215] Re: unity menu scrolls itself up from time to time
** No longer affects: unity (Ubuntu) ** Changed in: unity Status: New => Invalid ** Converted to question: https://answers.launchpad.net/unity/+question/256326 ** Also affects: ubuntu Importance: Undecided Status: New -- 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/1370215 Title: unity menu scrolls itself up from time to time Status in Unity: Invalid Status in Ubuntu: New Bug description: I had big trouble to describe it, and the problem bothers me so much that guided by the motto "a picture is worth thousand words" I decided to record a video that shows it: https://www.youtube.com/watch?v=UkWYYbYu2FY In other words sometimes when I hover an icon, then menu instead of stopping on this icon scrolls itself up instead. Note that I do not have two monitors so my cursor does not go beyond the edge of the monitor. moreover, this happens only sometimes. Description: Ubuntu 14.04.1 LTS Release: 14.04 unity 7.2.2+14.04.20140714-0ubuntu1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1370215/+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 1372665] Re: apport reports suspend/resume failure twice on boot (apportcheckresume)
I've uploaded an SRU for this to the trusty queue. ** Description changed: - Something has regressed to cause my laptop to not resume from suspend. - But in addition, this has exposed a bug in apportcheckresume, which is - reporting the resume failure twice in a row. + Test Case + - + 1) sudo touch /var/lib/pm-utils/status + 2) reboot + 3) observe two susres named crash reports in /var/crash/ + + With the version of apport from trusty-proposed you will only have one + crash report in /var/crash. + + + Something has regressed to cause my laptop to not resume from suspend. But in addition, this has exposed a bug in apportcheckresume, which is reporting the resume failure twice in a row. $ ls -l /var/crash/susres.2014-09-22_15\:00\:53.7*.crash -rw-r- 1 root whoopsie 1314658 Sep 22 15:02 /var/crash/susres.2014-09-22_15:00:53.767701.crash -rw-r- 1 root whoopsie 1314630 Sep 22 15:01 /var/crash/susres.2014-09-22_15:00:53.780433.crash $ As I certainly did not have two resume failures within a second of one another, I think this is an apportcheckresume bug. - ProblemType: Bug - DistroRelease: Ubuntu 14.10 + ProblemType: BugDistroRelease: Ubuntu 14.10 Package: apport 2.14.7-0ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-16.22-generic 3.16.2 Uname: Linux 3.16.0-16-generic x86_64 ApportLog: - + ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Mon Sep 22 15:15:14 2014 - InstallationDate: Installed on 2010-09-24 (1459 days ago) - InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1) - PackageArchitecture: all - SourcePackage: apport + InstallationDate: Installed on 2010-09-24 (1459 days ago)InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1) + PackageArchitecture: allSourcePackage: apport UpgradeStatus: Upgraded to utopic on 2014-05-23 (122 days ago) ** Changed in: apport (Ubuntu Trusty) Status: Triaged => In Progress -- 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/1372665 Title: apport reports suspend/resume failure twice on boot (apportcheckresume) Status in “apport” package in Ubuntu: Fix Released Status in “apport” source package in Trusty: In Progress Bug description: Test Case - 1) sudo touch /var/lib/pm-utils/status 2) reboot 3) observe two susres named crash reports in /var/crash/ With the version of apport from trusty-proposed you will only have one crash report in /var/crash. Something has regressed to cause my laptop to not resume from suspend. But in addition, this has exposed a bug in apportcheckresume, which is reporting the resume failure twice in a row. $ ls -l /var/crash/susres.2014-09-22_15\:00\:53.7*.crash -rw-r- 1 root whoopsie 1314658 Sep 22 15:02 /var/crash/susres.2014-09-22_15:00:53.767701.crash -rw-r- 1 root whoopsie 1314630 Sep 22 15:01 /var/crash/susres.2014-09-22_15:00:53.780433.crash $ As I certainly did not have two resume failures within a second of one another, I think this is an apportcheckresume bug. ProblemType: BugDistroRelease: Ubuntu 14.10 Package: apport 2.14.7-0ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-16.22-generic 3.16.2 Uname: Linux 3.16.0-16-generic x86_64 ApportLog: ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Mon Sep 22 15:15:14 2014 InstallationDate: Installed on 2010-09-24 (1459 days ago)InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1) PackageArchitecture: allSourcePackage: apport UpgradeStatus: Upgraded to utopic on 2014-05-23 (122 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1372665/+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 1385360] Re: Change include guards to use #pragma once
** Changed in: unity-scopes-api (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scopes-api in Ubuntu. https://bugs.launchpad.net/bugs/1385360 Title: Change include guards to use #pragma once Status in “unity-scopes-api” package in Ubuntu: New Bug description: We should do a pass over the code base and get rid of the old-style include guards, replacing them with #pragma once. That's a lot simpler and less error prone than having to remember to update the guard identifier every time copies a header to create a new one. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1385360/+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 1385460] Re: Activation handling should be re-visited
** Changed in: unity-scopes-api (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scopes-api in Ubuntu. https://bugs.launchpad.net/bugs/1385460 Title: Activation handling should be re-visited Status in “unity-scopes-api” package in Ubuntu: New Bug description: We should re-visit result activation API. There's currently no way for scope to handle result activation (not be confused with preview action activation) except for a few hardcoded cases in the UI (namely - Apps), because all clicks / taps display a mandatory preview. Also, the ShowDash/HideDash activation responses should be re- considered. We should consider what to do about activate() handler in the ScopeBaseAPI. At the very least we should probably update the documentation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1385460/+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 1381891] Re: Setting invalid widget attribute does not raise exception
** Changed in: unity-scopes-api (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scopes-api in Ubuntu. https://bugs.launchpad.net/bugs/1381891 Title: Setting invalid widget attribute does not raise exception Status in “unity-scopes-api” package in Ubuntu: New Bug description: Suppose I do: PreviewWidget desc("summary_col", "text"); desc.add_attribute_value("test", Variant("This is the text for the widget")); Did you spot the error? The attribute being set is "test", but it should be "text". There is no indication that I'm doing something impossible, and I'm left scratching my head why nothing renders. It might be better to raise InvalidArgumentException here? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1381891/+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 1386891] [NEW] curser
Public bug reported: curser jumps allover the place some graphics on the screen do not go when they should ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4 Uname: Linux 3.16.0-23-generic x86_64 NonfreeKernelModules: wl .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Tue Oct 28 21:12:20 2014 DistUpgraded: 2014-10-26 09:34:21,462 DEBUG enabling apt cron job DistroCodename: utopic DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.16.0-23-generic, x86_64: installed bcmwl, 6.30.223.248+bdcom, 3.13.0-38-generic, x86_64: installed bcmwl, 6.30.223.248+bdcom, 3.16.0-23-generic, x86_64: installed ndiswrapper, 1.59, 3.13.0-38-generic, x86_64: installed ndiswrapper, 1.59, 3.16.0-23-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0465] NVIDIA Corporation GT215M [GeForce GT 335M] [10de:0caf] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0465] InstallationDate: Installed on 2014-10-11 (17 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Alienware M11x R2 ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-23-generic root=/dev/mapper/ubuntu--vg-root ro splash quiet vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to utopic on 2014-10-26 (2 days ago) dmi.bios.date: 08/09/2010 dmi.bios.vendor: Alienware dmi.bios.version: A03 dmi.board.name: M11x R2 dmi.board.vendor: Alienware dmi.board.version: A03 dmi.chassis.type: 8 dmi.chassis.vendor: Alienware dmi.chassis.version: A03 dmi.modalias: dmi:bvnAlienware:bvrA03:bd08/09/2010:svnAlienware:pnM11xR2:pvrA03:rvnAlienware:rnM11xR2:rvrA03:cvnAlienware:ct8:cvrA03: dmi.product.name: M11x R2 dmi.product.version: A03 dmi.sys.vendor: Alienware version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Tue Oct 28 20:02:39 2014 xserver.configfile: default xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) NOUVEAU(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 21569 vendor SEC xserver.version: 2:1.16.0-1ubuntu1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu utopic -- 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/1386891 Title: curser Status in “xorg” package in Ubuntu: New Bug description: curser jumps allover the place some graphics on the screen do not go when they should ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4 Uname: Linux 3.16.0-23-generic x86_64 NonfreeKernelModules: wl .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Tue Oct 28 21:12:20 2014 DistUpgraded: 2014-10-26 09:34:21,462 DEBUG enabling apt cron job DistroCodename: utopic DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.16.0-23-generic, x86_64: installed bcmwl, 6.30.223.248+bdcom, 3.13.0-38-generic, x86_64: installed bcmwl, 6.30.223.248+bdcom, 3.16.0-23-generic, x86_64: installed ndiswrapper, 1.59, 3.13.0-38-generic, x86_64: installed ndiswrapper, 1.59, 3.16.0-23-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if
[Touch-packages] [Bug 988072] Re: Can't remove user if they're not in /etc/passwd
That work-around doesn't work for me, because my lightdm.conf already has those entries in it. [SeatDefaults] greeter-session=unity-greeter user-session=ubuntu greeter-hide-users=true greeter-show-manual-login=true allow-guest=false -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/988072 Title: Can't remove user if they're not in /etc/passwd Status in “accountsservice” package in Ubuntu: Confirmed Bug description: Thanks to nss, there are many ways for a user account to exist. If you have user accounts authenticated with LDAP (say), and use nss tables other than passwd to store user information, then you find that the system automatically creates an entry in the user account database on login. This is handy: it means the user gets listed by lightdm in the greeter, for example, and things like background and keyboard prefs can be known to the greeter. It's all good. However, these users cannot be deleted. If you use the accounts-daemon from the control center to remove them, you get this error: Failed to delete user GDBus.Error:org.freedesktop.Accounts.Error.Failed: running '/usr/sbin/userdel' failed: /usr/sbin/userdel returned an error (1): userdel: cannot remove entry 'tbushnell' from /etc/passwd And alas, the user then stays in the system database. Please make it possible to remove users from the system database even if deluser and userdel don't work on them. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/988072/+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 1382039] Re: [TOPBLOCKER] Apps scope empty on boot
Hello, Hello, seems this is stuck'ish again? Who needs doing what here to get us to a good app scope back asap? Thanks! - Alexander -- 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/1382039 Title: [TOPBLOCKER] Apps scope empty on boot Status in “qtmir” package in Ubuntu: Triaged Status in “unity-scope-click” package in Ubuntu: Invalid Status in “unity-scopes-api” package in Ubuntu: Invalid Status in “unity-scopes-shell” package in Ubuntu: Invalid Status in “unity8” package in Ubuntu: Invalid Bug description: Several people reported today that the apps scope came up empty on boot. A pull-to-refresh makes results come in again. Note: it seems the problem is more likely to happen if you wait for at least 1 minute after reboot, and then unlock your device. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtmir/+bug/1382039/+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 1386840] Re: failure to start a container
** Changed in: lxc (Ubuntu) Importance: Undecided => High ** Changed in: lxc (Ubuntu) Status: New => Triaged ** Also affects: lxc (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: lxc (Ubuntu Utopic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1386840 Title: failure to start a container Status in “lxc” package in Ubuntu: Triaged Status in “lxc” source package in Trusty: New Status in “lxc” source package in Utopic: New Bug description: On utopic using lxc version 1.1.0~alpha2-0ubuntu3, I was unable to start a container. $ sudo lxc-start -F -n lxc-errors lxc-start: lsm/apparmor.c: mount_feature_enabled: 61 Permission denied - Error mounting securityfs lxc-start: lsm/apparmor.c: apparmor_process_label_set: 186 If you really want to start this container, set lxc-start: lsm/apparmor.c: apparmor_process_label_set: 187 lxc.aa_allow_incomplete = 1 lxc-start: lsm/apparmor.c: apparmor_process_label_set: 188 in your container configuration file lxc-start: sync.c: __sync_wait: 51 invalid sequence number 1. expected 4 lxc-start: start.c: __lxc_start: 1087 failed to spawn 'lxc-errors' lxc-start: cgmanager.c: cgm_remove_cgroup: 503 call to cgmanager_remove_sync failed: invalid request lxc-start: cgmanager.c: cgm_remove_cgroup: 505 Error removing name=systemd:lxc/lxc-errors-2 Switching to the version of lxc in http://ppa.launchpad.net/ubuntu- lxc/daily/ resolved the failure to start for me. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1386840/+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 1372665] Re: apport reports suspend/resume failure twice on boot (apportcheckresume)
** Also affects: apport (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: apport (Ubuntu Trusty) Status: New => Triaged ** Changed in: apport (Ubuntu Trusty) Importance: Undecided => High ** Changed in: apport (Ubuntu Trusty) Assignee: (unassigned) => Brian Murray (brian-murray) -- 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/1372665 Title: apport reports suspend/resume failure twice on boot (apportcheckresume) Status in “apport” package in Ubuntu: Fix Released Status in “apport” source package in Trusty: Triaged Bug description: Something has regressed to cause my laptop to not resume from suspend. But in addition, this has exposed a bug in apportcheckresume, which is reporting the resume failure twice in a row. $ ls -l /var/crash/susres.2014-09-22_15\:00\:53.7*.crash -rw-r- 1 root whoopsie 1314658 Sep 22 15:02 /var/crash/susres.2014-09-22_15:00:53.767701.crash -rw-r- 1 root whoopsie 1314630 Sep 22 15:01 /var/crash/susres.2014-09-22_15:00:53.780433.crash $ As I certainly did not have two resume failures within a second of one another, I think this is an apportcheckresume bug. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: apport 2.14.7-0ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-16.22-generic 3.16.2 Uname: Linux 3.16.0-16-generic x86_64 ApportLog: ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Mon Sep 22 15:15:14 2014 InstallationDate: Installed on 2010-09-24 (1459 days ago) InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1) PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to utopic on 2014-05-23 (122 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1372665/+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 1386882] [NEW] evolution does not start due to missing symbol in /usr/lib/x86_64-linux-gnu/libhogweed.so.2
Public bug reported: evolution does not start after update to 14.10: $ evolution (evolution:17843): libebackend-WARNING **: module_load: /usr/lib/x86_64-linux-gnu/libhogweed.so.2: undefined symbol: __gmpn_cnd_sub_n Failed to load module: /usr/lib/evolution/3.12/modules/module-cal-config-google.so (evolution:17843): libebackend-WARNING **: module_load: /usr/lib/x86_64-linux-gnu/libhogweed.so.2: undefined symbol: __gmpn_cnd_sub_n Failed to load module: /usr/lib/evolution/3.12/modules/module-book-config-ldap.so (evolution:17843): camel-WARNING **: Failed to initialize NSS SQL database in sql:/etc/pki/nssdb: NSS error -8126 evolution: symbol lookup error: /usr/lib/x86_64-linux-gnu/libhogweed.so.2: undefined symbol: __gmpn_cnd_add_n lsb_release -rd Description:Ubuntu 14.10 Release:14.10 apt-cache policy evolution evolution: Installiert: 3.12.7-0ubuntu1 Installationskandidat: 3.12.7-0ubuntu1 Versionstabelle: *** 3.12.7-0ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages 100 /var/lib/dpkg/status ** Affects: nettle (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nettle in Ubuntu. https://bugs.launchpad.net/bugs/1386882 Title: evolution does not start due to missing symbol in /usr/lib/x86_64 -linux-gnu/libhogweed.so.2 Status in “nettle” package in Ubuntu: New Bug description: evolution does not start after update to 14.10: $ evolution (evolution:17843): libebackend-WARNING **: module_load: /usr/lib/x86_64-linux-gnu/libhogweed.so.2: undefined symbol: __gmpn_cnd_sub_n Failed to load module: /usr/lib/evolution/3.12/modules/module-cal-config-google.so (evolution:17843): libebackend-WARNING **: module_load: /usr/lib/x86_64-linux-gnu/libhogweed.so.2: undefined symbol: __gmpn_cnd_sub_n Failed to load module: /usr/lib/evolution/3.12/modules/module-book-config-ldap.so (evolution:17843): camel-WARNING **: Failed to initialize NSS SQL database in sql:/etc/pki/nssdb: NSS error -8126 evolution: symbol lookup error: /usr/lib/x86_64-linux-gnu/libhogweed.so.2: undefined symbol: __gmpn_cnd_add_n lsb_release -rd Description: Ubuntu 14.10 Release: 14.10 apt-cache policy evolution evolution: Installiert: 3.12.7-0ubuntu1 Installationskandidat: 3.12.7-0ubuntu1 Versionstabelle: *** 3.12.7-0ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nettle/+bug/1386882/+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 1386534] Re: kernel dependent deterministic view crash on X startup
WARNING: the apport above is with the kernel 3.13.0-36-generic, where there is no problem (see the origonal post), hence it is useful only for getting the configuration of my machine. In case of 3.16.0-23-generic I am not able to get a non-blank X neither a readable console, hence I can not provide an apport-collect result for that kernel. However, if someone could provide me a shell script for BLIND use, then I can login blindly into a character console and run that shell script, but I have NO CHANCE to answer any question or to make any selection, since I sen NOTHING useful: the character console is broken in a different way: the usual left edge is vibrating somewhere at the 80% of the width, an only every second scan row is visible, and what is beyond the rigth edge, that appears really fuzzy on the left side. Many thanks in advance, Péter. -- 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/1386534 Title: kernel dependent deterministic view crash on X startup Status in “xorg” package in Ubuntu: New Bug description: kernel 3.13.0-37 and 3.16.0-23, but not kernel 3.13.0-36 The phenomenon: just when the user interface starts at the end of the Ununtu startup, the screen reamins in one solid color (very light grey, this is the everage of my colors), except for the topmost 3-4 scan lines, where one can see some sort of vibrating content. Sometimes there is a 1-3 seconds of normal operation just at the start, when Ctrl-Alt-F2 works, and swithing there one can work in the character terminal forever. But as soon as the disorder in the X view appears, even the Ctrl-Alt-F2 console change does not work visually, however a blindly stroken Ctr-Alt-Del is correctly executed. What I know: (1) on the core i3 based laptop there is no trace of this kind of view crash, while in case of the Phenom x6 1100t and Radeon HD 6570 based desktop machine the problem is fully deterministic. (2) the problem is distro independet, i.e.: I have it with Ubuntu 14.04 + kernel 3.13.0-37-generic, and also with Ubuntu 14.10 + 3.16.0-23-generic, and I do NOT have it with Ubuntu 14.04 + kernel 3.13.0-36-generic, and also with Ubuntu 14.10 + 3.13.0-36-generic. (3) In case of Ubuntu 14.04 in average every second or third boot gave a 1-3 seconds of grace period when I could escape to Ctrl-Alt-F2, while in case of Ubuntu 14.10 there is no such a short time slot when I could escape. (4) my configuration is set to fall into my only user account directly, I will do experiments, whether the problem is there, if the startup is without falling into an account. If I can, I will apport log files with produced with the 3.16.0-23-generic kernel as well, not only with the 3.13.0-36-generic. I try to send the remaining information after my work day, now I have to leave, sorry. --- .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8 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 CurrentDmesg: [ 11.299825] init: plymouth-upstart-bridge main process ended, respawning [ 11.329699] systemd-logind[1615]: Failed to start unit user@1000.service: Unknown unit: user@1000.service [ 11.329706] systemd-logind[1615]: Failed to start user service: Unknown unit: user@1000.service [ 11.332093] systemd-logind[1615]: New session c1 of user prohlep. [ 11.332112] systemd-logind[1615]: Linked /tmp/.X11-unix/X0 to /run/user/1000/X11-display. DistUpgraded: 2014-10-27 10:17:33,100 DEBUG enabling apt cron job DistroCodename: utopic DistroRelease: Ubuntu 14.10 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Turks PRO [Radeon HD 6570/7570/8550] [1002:6759] (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Device [1682:3195] InstallationDate: Installed on 2014-06-26 (124 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: System manufacturer System Product Name Package: xorg 1:7.7+7ubuntu2 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-36-generic root=UUID=db97e979-6d3b-43cb-9159-341be03e6c9e ro ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Tags: utopic ubuntu compiz-0.9 Uname: Linux 3.13.0-36-generic x86_64 UpgradeStatus: Upgraded to utopic on 2014-10-27 (1 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 07/18/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2301 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A89GTD-PRO/USB3 dmi.board.vendor: ASUSTeK Computer
[Touch-packages] [Bug 1363257] Re: string matching for dpkg I/O errors in dpkgpm.cc is out of date
Hello Brian, or anyone else affected, Accepted apt into trusty-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/apt/1.0.1ubuntu2.6 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: apt (Ubuntu Trusty) Status: Triaged => Fix Committed ** Tags added: verification-needed -- 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/1363257 Title: string matching for dpkg I/O errors in dpkgpm.cc is out of date Status in “apt” package in Ubuntu: Fix Released Status in “apt” source package in Trusty: Fix Committed Bug description: The following error strings are no longer returned by dpkg: io_errors.push_back(string("failed to read on buffer copy for %s")); io_errors.push_back(string("failed in write on buffer copy for %s")); io_errors.push_back(string("short read on buffer copy for %s")); Subsequently, apport package installation failures are being created for these types of crashes and they should not be. Additionally, there is a new error returned by dpkg ("unexpected end of file or stream" as seen in bug 1361489) which should also be blocked. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1363257/+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 1353171] Re: Misparses dpkg status line, fails to write apport reports
Hello Anders, or anyone else affected, Accepted apt into trusty-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/apt/1.0.1ubuntu2.6 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: apt (Ubuntu Trusty) Status: Triaged => Fix Committed ** Tags added: verification-needed -- 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/1353171 Title: Misparses dpkg status line, fails to write apport reports Status in “apt” package in Ubuntu: Fix Released Status in “apt” source package in Trusty: Fix Committed Bug description: Test Case - 1) sudo apt-add-repository ppa:daisy-pluckers/daisy-seeds 2) sudo apt-get update 3) sudo apt-get install crash-in-postinst 4) observe a package installation failure dialog With the version of apt in the archive you will *not* receive a crash file in /var/crash. If you install the version of apt from -proposed you should receive a crash file in /var/crash and an apport dialog should appear. For a while apt has not been writing apport reports for dpkg maintainer script errors. Here’s why: • pkgDPkgPM::ProcessDpkgStatusLine sees a line like "status: cyrus-clients : error : subprocess installed post-installation script returned error exit status 1". • StringSplit splits it into list == {"status", "cyrus-clients ", "error ", "subprocess installed post-installation script returned error exit status 1"}. • pkgname is set to Strip(list[1]) == "cyrus-clients". • However, the original list[1] == "cyrus-clients " (with a trailing space) is passed to WriteApportReport. • WriteApport fails to find "cyrus-clients " in the cache, and bails out. Patch attached. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: libapt-pkg4.12 1.0.4ubuntu6 ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7 Uname: Linux 3.16.0-6-generic x86_64 NonfreeKernelModules: openafs ApportVersion: 2.14.5-0ubuntu3 Architecture: amd64 Date: Tue Aug 5 19:19:39 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2010-12-05 (1339 days ago) InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20101202) SourcePackage: apt UpgradeStatus: Upgraded to utopic on 2013-10-31 (278 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1353171/+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 1383858] Re: expr-simplify optimization slows click policy compilation
Here is the debdiff for apparmor, in case anyone needs it: ** Patch added: "apparmor_2.8.96~2652-0ubuntu5.3.debdiff" https://bugs.launchpad.net/ubuntu-rtm/+source/apparmor/+bug/1383858/+attachment/4247539/+files/apparmor_2.8.96%7E2652-0ubuntu5.3.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1383858 Title: expr-simplify optimization slows click policy compilation Status in AppArmor Linux application security framework: Triaged Status in “apparmor” package in Ubuntu: Triaged Status in “click-apparmor” package in Ubuntu: Fix Released Status in “apparmor” package in Ubuntu RTM: In Progress Status in “click-apparmor” package in Ubuntu RTM: In Progress Bug description: AppArmor has several optimization options that can be used to help speed up policy compiles for certain types of policy. Currently, we are using expr tree simplification option by default, which has dramatic affects on policy compiles for the evince profile. However, with click profiles not using expr tree simplification (ie, adding the '-O no-expr-simplify' option) can improve click policy generation by 44% (375 vs 210 seconds). On Krillin, the difference is even more substantial: 636 vs 233 seconds (63%). Short term for rtm is to to use '-O no-expr-simplify' when compiling policy in /var/lib/apparmor/profiles but leave /etc/apparmor.d alone. We can do the same with click-apparmor. The long term fix is to adjust expr tree simplification to be more efficient (at least as fast as without) and drop the '-O no-expr- simplify' option. Justification: apparmor policy recompilation is not expected to happen as part of the normal user experience (see bug #1350598 for a lot of detail) and it is expected to only happen on upgrades from 14.10 to 15.04 or to fix very serious apparmor or apparmor policy bugs. None of these bugs are currently scheduled for OTA. However, *if* we ever need to fix one of these, policy will have to be recompiled. Choices: 1. do nothing for RTM since policy recompiles are expected to be rare, but do apply this change to 15.04. Policy is expected to be recompiled on upgrades to 15.04 and upgrades would use the new option 2. apply this change in OTA. This is problematic because this change alone will trigger a policy recompilation that would not otherwise be needed. Optionally, this change could accompany a severe bug fix Risk: The change consists of a small modification to the apparmor upstart job and a change to the arguments click-apparmor gives to apparmor_parser. The risk assessment is considered low because of the size of the change and the simple test case will immediately indicate if either were applied incorrectly. Test case: 1. run aa-status | wc -l and note the result 2. install the new apparmor and click-apparmor packages and verify there are no errors during installation 3. reboot 4. run aa-status | wc -l and compare to '1' 5. run 'sudo start apparmor' and make sure it finishes in a few seconds If they are the same, it indicates the upstart job is properly loading the profiles generated by click apparmor. While these changes may occur separately, landing them at the same time along with a regenerated custom tarball (for preinstalled policy) will reduce policy recompiles. To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1383858/+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 1386534] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1386534/+attachment/4247525/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1386534 Title: kernel dependent deterministic view crash on X startup Status in “xorg” package in Ubuntu: New Bug description: kernel 3.13.0-37 and 3.16.0-23, but not kernel 3.13.0-36 The phenomenon: just when the user interface starts at the end of the Ununtu startup, the screen reamins in one solid color (very light grey, this is the everage of my colors), except for the topmost 3-4 scan lines, where one can see some sort of vibrating content. Sometimes there is a 1-3 seconds of normal operation just at the start, when Ctrl-Alt-F2 works, and swithing there one can work in the character terminal forever. But as soon as the disorder in the X view appears, even the Ctrl-Alt-F2 console change does not work visually, however a blindly stroken Ctr-Alt-Del is correctly executed. What I know: (1) on the core i3 based laptop there is no trace of this kind of view crash, while in case of the Phenom x6 1100t and Radeon HD 6570 based desktop machine the problem is fully deterministic. (2) the problem is distro independet, i.e.: I have it with Ubuntu 14.04 + kernel 3.13.0-37-generic, and also with Ubuntu 14.10 + 3.16.0-23-generic, and I do NOT have it with Ubuntu 14.04 + kernel 3.13.0-36-generic, and also with Ubuntu 14.10 + 3.13.0-36-generic. (3) In case of Ubuntu 14.04 in average every second or third boot gave a 1-3 seconds of grace period when I could escape to Ctrl-Alt-F2, while in case of Ubuntu 14.10 there is no such a short time slot when I could escape. (4) my configuration is set to fall into my only user account directly, I will do experiments, whether the problem is there, if the startup is without falling into an account. If I can, I will apport log files with produced with the 3.16.0-23-generic kernel as well, not only with the 3.13.0-36-generic. I try to send the remaining information after my work day, now I have to leave, sorry. --- .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8 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 CurrentDmesg: [ 11.299825] init: plymouth-upstart-bridge main process ended, respawning [ 11.329699] systemd-logind[1615]: Failed to start unit user@1000.service: Unknown unit: user@1000.service [ 11.329706] systemd-logind[1615]: Failed to start user service: Unknown unit: user@1000.service [ 11.332093] systemd-logind[1615]: New session c1 of user prohlep. [ 11.332112] systemd-logind[1615]: Linked /tmp/.X11-unix/X0 to /run/user/1000/X11-display. DistUpgraded: 2014-10-27 10:17:33,100 DEBUG enabling apt cron job DistroCodename: utopic DistroRelease: Ubuntu 14.10 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Turks PRO [Radeon HD 6570/7570/8550] [1002:6759] (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Device [1682:3195] InstallationDate: Installed on 2014-06-26 (124 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: System manufacturer System Product Name Package: xorg 1:7.7+7ubuntu2 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-36-generic root=UUID=db97e979-6d3b-43cb-9159-341be03e6c9e ro ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Tags: utopic ubuntu compiz-0.9 Uname: Linux 3.13.0-36-generic x86_64 UpgradeStatus: Upgraded to utopic on 2014-10-27 (1 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 07/18/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2301 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A89GTD-PRO/USB3 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.:bvr2301:bd07/18/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A89GTD-PRO/USB3:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3 version.libgl1-mesa-d
[Touch-packages] [Bug 1386534] LightdmGreeterLog.txt
apport information ** Attachment added: "LightdmGreeterLog.txt" https://bugs.launchpad.net/bugs/1386534/+attachment/4247522/+files/LightdmGreeterLog.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1386534 Title: kernel dependent deterministic view crash on X startup Status in “xorg” package in Ubuntu: New Bug description: kernel 3.13.0-37 and 3.16.0-23, but not kernel 3.13.0-36 The phenomenon: just when the user interface starts at the end of the Ununtu startup, the screen reamins in one solid color (very light grey, this is the everage of my colors), except for the topmost 3-4 scan lines, where one can see some sort of vibrating content. Sometimes there is a 1-3 seconds of normal operation just at the start, when Ctrl-Alt-F2 works, and swithing there one can work in the character terminal forever. But as soon as the disorder in the X view appears, even the Ctrl-Alt-F2 console change does not work visually, however a blindly stroken Ctr-Alt-Del is correctly executed. What I know: (1) on the core i3 based laptop there is no trace of this kind of view crash, while in case of the Phenom x6 1100t and Radeon HD 6570 based desktop machine the problem is fully deterministic. (2) the problem is distro independet, i.e.: I have it with Ubuntu 14.04 + kernel 3.13.0-37-generic, and also with Ubuntu 14.10 + 3.16.0-23-generic, and I do NOT have it with Ubuntu 14.04 + kernel 3.13.0-36-generic, and also with Ubuntu 14.10 + 3.13.0-36-generic. (3) In case of Ubuntu 14.04 in average every second or third boot gave a 1-3 seconds of grace period when I could escape to Ctrl-Alt-F2, while in case of Ubuntu 14.10 there is no such a short time slot when I could escape. (4) my configuration is set to fall into my only user account directly, I will do experiments, whether the problem is there, if the startup is without falling into an account. If I can, I will apport log files with produced with the 3.16.0-23-generic kernel as well, not only with the 3.13.0-36-generic. I try to send the remaining information after my work day, now I have to leave, sorry. --- .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8 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 CurrentDmesg: [ 11.299825] init: plymouth-upstart-bridge main process ended, respawning [ 11.329699] systemd-logind[1615]: Failed to start unit user@1000.service: Unknown unit: user@1000.service [ 11.329706] systemd-logind[1615]: Failed to start user service: Unknown unit: user@1000.service [ 11.332093] systemd-logind[1615]: New session c1 of user prohlep. [ 11.332112] systemd-logind[1615]: Linked /tmp/.X11-unix/X0 to /run/user/1000/X11-display. DistUpgraded: 2014-10-27 10:17:33,100 DEBUG enabling apt cron job DistroCodename: utopic DistroRelease: Ubuntu 14.10 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Turks PRO [Radeon HD 6570/7570/8550] [1002:6759] (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Device [1682:3195] InstallationDate: Installed on 2014-06-26 (124 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: System manufacturer System Product Name Package: xorg 1:7.7+7ubuntu2 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-36-generic root=UUID=db97e979-6d3b-43cb-9159-341be03e6c9e ro ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Tags: utopic ubuntu compiz-0.9 Uname: Linux 3.13.0-36-generic x86_64 UpgradeStatus: Upgraded to utopic on 2014-10-27 (1 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 07/18/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2301 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A89GTD-PRO/USB3 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.:bvr2301:bd07/18/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A89GTD-PRO/USB3:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu
[Touch-packages] [Bug 1386534] LightdmGreeterLogOld.txt
apport information ** Attachment added: "LightdmGreeterLogOld.txt" https://bugs.launchpad.net/bugs/1386534/+attachment/4247523/+files/LightdmGreeterLogOld.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1386534 Title: kernel dependent deterministic view crash on X startup Status in “xorg” package in Ubuntu: New Bug description: kernel 3.13.0-37 and 3.16.0-23, but not kernel 3.13.0-36 The phenomenon: just when the user interface starts at the end of the Ununtu startup, the screen reamins in one solid color (very light grey, this is the everage of my colors), except for the topmost 3-4 scan lines, where one can see some sort of vibrating content. Sometimes there is a 1-3 seconds of normal operation just at the start, when Ctrl-Alt-F2 works, and swithing there one can work in the character terminal forever. But as soon as the disorder in the X view appears, even the Ctrl-Alt-F2 console change does not work visually, however a blindly stroken Ctr-Alt-Del is correctly executed. What I know: (1) on the core i3 based laptop there is no trace of this kind of view crash, while in case of the Phenom x6 1100t and Radeon HD 6570 based desktop machine the problem is fully deterministic. (2) the problem is distro independet, i.e.: I have it with Ubuntu 14.04 + kernel 3.13.0-37-generic, and also with Ubuntu 14.10 + 3.16.0-23-generic, and I do NOT have it with Ubuntu 14.04 + kernel 3.13.0-36-generic, and also with Ubuntu 14.10 + 3.13.0-36-generic. (3) In case of Ubuntu 14.04 in average every second or third boot gave a 1-3 seconds of grace period when I could escape to Ctrl-Alt-F2, while in case of Ubuntu 14.10 there is no such a short time slot when I could escape. (4) my configuration is set to fall into my only user account directly, I will do experiments, whether the problem is there, if the startup is without falling into an account. If I can, I will apport log files with produced with the 3.16.0-23-generic kernel as well, not only with the 3.13.0-36-generic. I try to send the remaining information after my work day, now I have to leave, sorry. --- .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8 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 CurrentDmesg: [ 11.299825] init: plymouth-upstart-bridge main process ended, respawning [ 11.329699] systemd-logind[1615]: Failed to start unit user@1000.service: Unknown unit: user@1000.service [ 11.329706] systemd-logind[1615]: Failed to start user service: Unknown unit: user@1000.service [ 11.332093] systemd-logind[1615]: New session c1 of user prohlep. [ 11.332112] systemd-logind[1615]: Linked /tmp/.X11-unix/X0 to /run/user/1000/X11-display. DistUpgraded: 2014-10-27 10:17:33,100 DEBUG enabling apt cron job DistroCodename: utopic DistroRelease: Ubuntu 14.10 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Turks PRO [Radeon HD 6570/7570/8550] [1002:6759] (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Device [1682:3195] InstallationDate: Installed on 2014-06-26 (124 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: System manufacturer System Product Name Package: xorg 1:7.7+7ubuntu2 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-36-generic root=UUID=db97e979-6d3b-43cb-9159-341be03e6c9e ro ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Tags: utopic ubuntu compiz-0.9 Uname: Linux 3.13.0-36-generic x86_64 UpgradeStatus: Upgraded to utopic on 2014-10-27 (1 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 07/18/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2301 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A89GTD-PRO/USB3 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.:bvr2301:bd07/18/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A89GTD-PRO/USB3:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0
[Touch-packages] [Bug 1386534] XorgLog.txt
apport information ** Attachment added: "XorgLog.txt" https://bugs.launchpad.net/bugs/1386534/+attachment/4247534/+files/XorgLog.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1386534 Title: kernel dependent deterministic view crash on X startup Status in “xorg” package in Ubuntu: New Bug description: kernel 3.13.0-37 and 3.16.0-23, but not kernel 3.13.0-36 The phenomenon: just when the user interface starts at the end of the Ununtu startup, the screen reamins in one solid color (very light grey, this is the everage of my colors), except for the topmost 3-4 scan lines, where one can see some sort of vibrating content. Sometimes there is a 1-3 seconds of normal operation just at the start, when Ctrl-Alt-F2 works, and swithing there one can work in the character terminal forever. But as soon as the disorder in the X view appears, even the Ctrl-Alt-F2 console change does not work visually, however a blindly stroken Ctr-Alt-Del is correctly executed. What I know: (1) on the core i3 based laptop there is no trace of this kind of view crash, while in case of the Phenom x6 1100t and Radeon HD 6570 based desktop machine the problem is fully deterministic. (2) the problem is distro independet, i.e.: I have it with Ubuntu 14.04 + kernel 3.13.0-37-generic, and also with Ubuntu 14.10 + 3.16.0-23-generic, and I do NOT have it with Ubuntu 14.04 + kernel 3.13.0-36-generic, and also with Ubuntu 14.10 + 3.13.0-36-generic. (3) In case of Ubuntu 14.04 in average every second or third boot gave a 1-3 seconds of grace period when I could escape to Ctrl-Alt-F2, while in case of Ubuntu 14.10 there is no such a short time slot when I could escape. (4) my configuration is set to fall into my only user account directly, I will do experiments, whether the problem is there, if the startup is without falling into an account. If I can, I will apport log files with produced with the 3.16.0-23-generic kernel as well, not only with the 3.13.0-36-generic. I try to send the remaining information after my work day, now I have to leave, sorry. --- .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8 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 CurrentDmesg: [ 11.299825] init: plymouth-upstart-bridge main process ended, respawning [ 11.329699] systemd-logind[1615]: Failed to start unit user@1000.service: Unknown unit: user@1000.service [ 11.329706] systemd-logind[1615]: Failed to start user service: Unknown unit: user@1000.service [ 11.332093] systemd-logind[1615]: New session c1 of user prohlep. [ 11.332112] systemd-logind[1615]: Linked /tmp/.X11-unix/X0 to /run/user/1000/X11-display. DistUpgraded: 2014-10-27 10:17:33,100 DEBUG enabling apt cron job DistroCodename: utopic DistroRelease: Ubuntu 14.10 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Turks PRO [Radeon HD 6570/7570/8550] [1002:6759] (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Device [1682:3195] InstallationDate: Installed on 2014-06-26 (124 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: System manufacturer System Product Name Package: xorg 1:7.7+7ubuntu2 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-36-generic root=UUID=db97e979-6d3b-43cb-9159-341be03e6c9e ro ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Tags: utopic ubuntu compiz-0.9 Uname: Linux 3.13.0-36-generic x86_64 UpgradeStatus: Upgraded to utopic on 2014-10-27 (1 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 07/18/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2301 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A89GTD-PRO/USB3 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.:bvr2301:bd07/18/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A89GTD-PRO/USB3:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3 version.libgl1-m
[Touch-packages] [Bug 1386534] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1386534/+attachment/4247526/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1386534 Title: kernel dependent deterministic view crash on X startup Status in “xorg” package in Ubuntu: New Bug description: kernel 3.13.0-37 and 3.16.0-23, but not kernel 3.13.0-36 The phenomenon: just when the user interface starts at the end of the Ununtu startup, the screen reamins in one solid color (very light grey, this is the everage of my colors), except for the topmost 3-4 scan lines, where one can see some sort of vibrating content. Sometimes there is a 1-3 seconds of normal operation just at the start, when Ctrl-Alt-F2 works, and swithing there one can work in the character terminal forever. But as soon as the disorder in the X view appears, even the Ctrl-Alt-F2 console change does not work visually, however a blindly stroken Ctr-Alt-Del is correctly executed. What I know: (1) on the core i3 based laptop there is no trace of this kind of view crash, while in case of the Phenom x6 1100t and Radeon HD 6570 based desktop machine the problem is fully deterministic. (2) the problem is distro independet, i.e.: I have it with Ubuntu 14.04 + kernel 3.13.0-37-generic, and also with Ubuntu 14.10 + 3.16.0-23-generic, and I do NOT have it with Ubuntu 14.04 + kernel 3.13.0-36-generic, and also with Ubuntu 14.10 + 3.13.0-36-generic. (3) In case of Ubuntu 14.04 in average every second or third boot gave a 1-3 seconds of grace period when I could escape to Ctrl-Alt-F2, while in case of Ubuntu 14.10 there is no such a short time slot when I could escape. (4) my configuration is set to fall into my only user account directly, I will do experiments, whether the problem is there, if the startup is without falling into an account. If I can, I will apport log files with produced with the 3.16.0-23-generic kernel as well, not only with the 3.13.0-36-generic. I try to send the remaining information after my work day, now I have to leave, sorry. --- .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8 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 CurrentDmesg: [ 11.299825] init: plymouth-upstart-bridge main process ended, respawning [ 11.329699] systemd-logind[1615]: Failed to start unit user@1000.service: Unknown unit: user@1000.service [ 11.329706] systemd-logind[1615]: Failed to start user service: Unknown unit: user@1000.service [ 11.332093] systemd-logind[1615]: New session c1 of user prohlep. [ 11.332112] systemd-logind[1615]: Linked /tmp/.X11-unix/X0 to /run/user/1000/X11-display. DistUpgraded: 2014-10-27 10:17:33,100 DEBUG enabling apt cron job DistroCodename: utopic DistroRelease: Ubuntu 14.10 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Turks PRO [Radeon HD 6570/7570/8550] [1002:6759] (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Device [1682:3195] InstallationDate: Installed on 2014-06-26 (124 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: System manufacturer System Product Name Package: xorg 1:7.7+7ubuntu2 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-36-generic root=UUID=db97e979-6d3b-43cb-9159-341be03e6c9e ro ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Tags: utopic ubuntu compiz-0.9 Uname: Linux 3.13.0-36-generic x86_64 UpgradeStatus: Upgraded to utopic on 2014-10-27 (1 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 07/18/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2301 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A89GTD-PRO/USB3 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.:bvr2301:bd07/18/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A89GTD-PRO/USB3:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3 version.libgl1-mesa-d
[Touch-packages] [Bug 1386534] LightdmLog.txt
apport information ** Attachment added: "LightdmLog.txt" https://bugs.launchpad.net/bugs/1386534/+attachment/4247524/+files/LightdmLog.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1386534 Title: kernel dependent deterministic view crash on X startup Status in “xorg” package in Ubuntu: New Bug description: kernel 3.13.0-37 and 3.16.0-23, but not kernel 3.13.0-36 The phenomenon: just when the user interface starts at the end of the Ununtu startup, the screen reamins in one solid color (very light grey, this is the everage of my colors), except for the topmost 3-4 scan lines, where one can see some sort of vibrating content. Sometimes there is a 1-3 seconds of normal operation just at the start, when Ctrl-Alt-F2 works, and swithing there one can work in the character terminal forever. But as soon as the disorder in the X view appears, even the Ctrl-Alt-F2 console change does not work visually, however a blindly stroken Ctr-Alt-Del is correctly executed. What I know: (1) on the core i3 based laptop there is no trace of this kind of view crash, while in case of the Phenom x6 1100t and Radeon HD 6570 based desktop machine the problem is fully deterministic. (2) the problem is distro independet, i.e.: I have it with Ubuntu 14.04 + kernel 3.13.0-37-generic, and also with Ubuntu 14.10 + 3.16.0-23-generic, and I do NOT have it with Ubuntu 14.04 + kernel 3.13.0-36-generic, and also with Ubuntu 14.10 + 3.13.0-36-generic. (3) In case of Ubuntu 14.04 in average every second or third boot gave a 1-3 seconds of grace period when I could escape to Ctrl-Alt-F2, while in case of Ubuntu 14.10 there is no such a short time slot when I could escape. (4) my configuration is set to fall into my only user account directly, I will do experiments, whether the problem is there, if the startup is without falling into an account. If I can, I will apport log files with produced with the 3.16.0-23-generic kernel as well, not only with the 3.13.0-36-generic. I try to send the remaining information after my work day, now I have to leave, sorry. --- .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8 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 CurrentDmesg: [ 11.299825] init: plymouth-upstart-bridge main process ended, respawning [ 11.329699] systemd-logind[1615]: Failed to start unit user@1000.service: Unknown unit: user@1000.service [ 11.329706] systemd-logind[1615]: Failed to start user service: Unknown unit: user@1000.service [ 11.332093] systemd-logind[1615]: New session c1 of user prohlep. [ 11.332112] systemd-logind[1615]: Linked /tmp/.X11-unix/X0 to /run/user/1000/X11-display. DistUpgraded: 2014-10-27 10:17:33,100 DEBUG enabling apt cron job DistroCodename: utopic DistroRelease: Ubuntu 14.10 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Turks PRO [Radeon HD 6570/7570/8550] [1002:6759] (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Device [1682:3195] InstallationDate: Installed on 2014-06-26 (124 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: System manufacturer System Product Name Package: xorg 1:7.7+7ubuntu2 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-36-generic root=UUID=db97e979-6d3b-43cb-9159-341be03e6c9e ro ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Tags: utopic ubuntu compiz-0.9 Uname: Linux 3.13.0-36-generic x86_64 UpgradeStatus: Upgraded to utopic on 2014-10-27 (1 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 07/18/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2301 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A89GTD-PRO/USB3 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.:bvr2301:bd07/18/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A89GTD-PRO/USB3:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3 version.li
[Touch-packages] [Bug 1386534] XorgLogOld.txt
apport information ** Attachment added: "XorgLogOld.txt" https://bugs.launchpad.net/bugs/1386534/+attachment/4247535/+files/XorgLogOld.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1386534 Title: kernel dependent deterministic view crash on X startup Status in “xorg” package in Ubuntu: New Bug description: kernel 3.13.0-37 and 3.16.0-23, but not kernel 3.13.0-36 The phenomenon: just when the user interface starts at the end of the Ununtu startup, the screen reamins in one solid color (very light grey, this is the everage of my colors), except for the topmost 3-4 scan lines, where one can see some sort of vibrating content. Sometimes there is a 1-3 seconds of normal operation just at the start, when Ctrl-Alt-F2 works, and swithing there one can work in the character terminal forever. But as soon as the disorder in the X view appears, even the Ctrl-Alt-F2 console change does not work visually, however a blindly stroken Ctr-Alt-Del is correctly executed. What I know: (1) on the core i3 based laptop there is no trace of this kind of view crash, while in case of the Phenom x6 1100t and Radeon HD 6570 based desktop machine the problem is fully deterministic. (2) the problem is distro independet, i.e.: I have it with Ubuntu 14.04 + kernel 3.13.0-37-generic, and also with Ubuntu 14.10 + 3.16.0-23-generic, and I do NOT have it with Ubuntu 14.04 + kernel 3.13.0-36-generic, and also with Ubuntu 14.10 + 3.13.0-36-generic. (3) In case of Ubuntu 14.04 in average every second or third boot gave a 1-3 seconds of grace period when I could escape to Ctrl-Alt-F2, while in case of Ubuntu 14.10 there is no such a short time slot when I could escape. (4) my configuration is set to fall into my only user account directly, I will do experiments, whether the problem is there, if the startup is without falling into an account. If I can, I will apport log files with produced with the 3.16.0-23-generic kernel as well, not only with the 3.13.0-36-generic. I try to send the remaining information after my work day, now I have to leave, sorry. --- .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8 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 CurrentDmesg: [ 11.299825] init: plymouth-upstart-bridge main process ended, respawning [ 11.329699] systemd-logind[1615]: Failed to start unit user@1000.service: Unknown unit: user@1000.service [ 11.329706] systemd-logind[1615]: Failed to start user service: Unknown unit: user@1000.service [ 11.332093] systemd-logind[1615]: New session c1 of user prohlep. [ 11.332112] systemd-logind[1615]: Linked /tmp/.X11-unix/X0 to /run/user/1000/X11-display. DistUpgraded: 2014-10-27 10:17:33,100 DEBUG enabling apt cron job DistroCodename: utopic DistroRelease: Ubuntu 14.10 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Turks PRO [Radeon HD 6570/7570/8550] [1002:6759] (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Device [1682:3195] InstallationDate: Installed on 2014-06-26 (124 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: System manufacturer System Product Name Package: xorg 1:7.7+7ubuntu2 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-36-generic root=UUID=db97e979-6d3b-43cb-9159-341be03e6c9e ro ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Tags: utopic ubuntu compiz-0.9 Uname: Linux 3.13.0-36-generic x86_64 UpgradeStatus: Upgraded to utopic on 2014-10-27 (1 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 07/18/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2301 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A89GTD-PRO/USB3 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.:bvr2301:bd07/18/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A89GTD-PRO/USB3:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3 version.li
[Touch-packages] [Bug 1386534] UdevLog.txt
apport information ** Attachment added: "UdevLog.txt" https://bugs.launchpad.net/bugs/1386534/+attachment/4247532/+files/UdevLog.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1386534 Title: kernel dependent deterministic view crash on X startup Status in “xorg” package in Ubuntu: New Bug description: kernel 3.13.0-37 and 3.16.0-23, but not kernel 3.13.0-36 The phenomenon: just when the user interface starts at the end of the Ununtu startup, the screen reamins in one solid color (very light grey, this is the everage of my colors), except for the topmost 3-4 scan lines, where one can see some sort of vibrating content. Sometimes there is a 1-3 seconds of normal operation just at the start, when Ctrl-Alt-F2 works, and swithing there one can work in the character terminal forever. But as soon as the disorder in the X view appears, even the Ctrl-Alt-F2 console change does not work visually, however a blindly stroken Ctr-Alt-Del is correctly executed. What I know: (1) on the core i3 based laptop there is no trace of this kind of view crash, while in case of the Phenom x6 1100t and Radeon HD 6570 based desktop machine the problem is fully deterministic. (2) the problem is distro independet, i.e.: I have it with Ubuntu 14.04 + kernel 3.13.0-37-generic, and also with Ubuntu 14.10 + 3.16.0-23-generic, and I do NOT have it with Ubuntu 14.04 + kernel 3.13.0-36-generic, and also with Ubuntu 14.10 + 3.13.0-36-generic. (3) In case of Ubuntu 14.04 in average every second or third boot gave a 1-3 seconds of grace period when I could escape to Ctrl-Alt-F2, while in case of Ubuntu 14.10 there is no such a short time slot when I could escape. (4) my configuration is set to fall into my only user account directly, I will do experiments, whether the problem is there, if the startup is without falling into an account. If I can, I will apport log files with produced with the 3.16.0-23-generic kernel as well, not only with the 3.13.0-36-generic. I try to send the remaining information after my work day, now I have to leave, sorry. --- .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8 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 CurrentDmesg: [ 11.299825] init: plymouth-upstart-bridge main process ended, respawning [ 11.329699] systemd-logind[1615]: Failed to start unit user@1000.service: Unknown unit: user@1000.service [ 11.329706] systemd-logind[1615]: Failed to start user service: Unknown unit: user@1000.service [ 11.332093] systemd-logind[1615]: New session c1 of user prohlep. [ 11.332112] systemd-logind[1615]: Linked /tmp/.X11-unix/X0 to /run/user/1000/X11-display. DistUpgraded: 2014-10-27 10:17:33,100 DEBUG enabling apt cron job DistroCodename: utopic DistroRelease: Ubuntu 14.10 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Turks PRO [Radeon HD 6570/7570/8550] [1002:6759] (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Device [1682:3195] InstallationDate: Installed on 2014-06-26 (124 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: System manufacturer System Product Name Package: xorg 1:7.7+7ubuntu2 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-36-generic root=UUID=db97e979-6d3b-43cb-9159-341be03e6c9e ro ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Tags: utopic ubuntu compiz-0.9 Uname: Linux 3.13.0-36-generic x86_64 UpgradeStatus: Upgraded to utopic on 2014-10-27 (1 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 07/18/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2301 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A89GTD-PRO/USB3 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.:bvr2301:bd07/18/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A89GTD-PRO/USB3:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3 version.libgl1-m
[Touch-packages] [Bug 1386534] xserver.outputs.txt
apport information ** Attachment added: "xserver.outputs.txt" https://bugs.launchpad.net/bugs/1386534/+attachment/4247538/+files/xserver.outputs.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1386534 Title: kernel dependent deterministic view crash on X startup Status in “xorg” package in Ubuntu: New Bug description: kernel 3.13.0-37 and 3.16.0-23, but not kernel 3.13.0-36 The phenomenon: just when the user interface starts at the end of the Ununtu startup, the screen reamins in one solid color (very light grey, this is the everage of my colors), except for the topmost 3-4 scan lines, where one can see some sort of vibrating content. Sometimes there is a 1-3 seconds of normal operation just at the start, when Ctrl-Alt-F2 works, and swithing there one can work in the character terminal forever. But as soon as the disorder in the X view appears, even the Ctrl-Alt-F2 console change does not work visually, however a blindly stroken Ctr-Alt-Del is correctly executed. What I know: (1) on the core i3 based laptop there is no trace of this kind of view crash, while in case of the Phenom x6 1100t and Radeon HD 6570 based desktop machine the problem is fully deterministic. (2) the problem is distro independet, i.e.: I have it with Ubuntu 14.04 + kernel 3.13.0-37-generic, and also with Ubuntu 14.10 + 3.16.0-23-generic, and I do NOT have it with Ubuntu 14.04 + kernel 3.13.0-36-generic, and also with Ubuntu 14.10 + 3.13.0-36-generic. (3) In case of Ubuntu 14.04 in average every second or third boot gave a 1-3 seconds of grace period when I could escape to Ctrl-Alt-F2, while in case of Ubuntu 14.10 there is no such a short time slot when I could escape. (4) my configuration is set to fall into my only user account directly, I will do experiments, whether the problem is there, if the startup is without falling into an account. If I can, I will apport log files with produced with the 3.16.0-23-generic kernel as well, not only with the 3.13.0-36-generic. I try to send the remaining information after my work day, now I have to leave, sorry. --- .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8 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 CurrentDmesg: [ 11.299825] init: plymouth-upstart-bridge main process ended, respawning [ 11.329699] systemd-logind[1615]: Failed to start unit user@1000.service: Unknown unit: user@1000.service [ 11.329706] systemd-logind[1615]: Failed to start user service: Unknown unit: user@1000.service [ 11.332093] systemd-logind[1615]: New session c1 of user prohlep. [ 11.332112] systemd-logind[1615]: Linked /tmp/.X11-unix/X0 to /run/user/1000/X11-display. DistUpgraded: 2014-10-27 10:17:33,100 DEBUG enabling apt cron job DistroCodename: utopic DistroRelease: Ubuntu 14.10 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Turks PRO [Radeon HD 6570/7570/8550] [1002:6759] (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Device [1682:3195] InstallationDate: Installed on 2014-06-26 (124 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: System manufacturer System Product Name Package: xorg 1:7.7+7ubuntu2 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-36-generic root=UUID=db97e979-6d3b-43cb-9159-341be03e6c9e ro ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Tags: utopic ubuntu compiz-0.9 Uname: Linux 3.13.0-36-generic x86_64 UpgradeStatus: Upgraded to utopic on 2014-10-27 (1 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 07/18/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2301 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A89GTD-PRO/USB3 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.:bvr2301:bd07/18/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A89GTD-PRO/USB3:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3
[Touch-packages] [Bug 1386534] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1386534/+attachment/4247530/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1386534 Title: kernel dependent deterministic view crash on X startup Status in “xorg” package in Ubuntu: New Bug description: kernel 3.13.0-37 and 3.16.0-23, but not kernel 3.13.0-36 The phenomenon: just when the user interface starts at the end of the Ununtu startup, the screen reamins in one solid color (very light grey, this is the everage of my colors), except for the topmost 3-4 scan lines, where one can see some sort of vibrating content. Sometimes there is a 1-3 seconds of normal operation just at the start, when Ctrl-Alt-F2 works, and swithing there one can work in the character terminal forever. But as soon as the disorder in the X view appears, even the Ctrl-Alt-F2 console change does not work visually, however a blindly stroken Ctr-Alt-Del is correctly executed. What I know: (1) on the core i3 based laptop there is no trace of this kind of view crash, while in case of the Phenom x6 1100t and Radeon HD 6570 based desktop machine the problem is fully deterministic. (2) the problem is distro independet, i.e.: I have it with Ubuntu 14.04 + kernel 3.13.0-37-generic, and also with Ubuntu 14.10 + 3.16.0-23-generic, and I do NOT have it with Ubuntu 14.04 + kernel 3.13.0-36-generic, and also with Ubuntu 14.10 + 3.13.0-36-generic. (3) In case of Ubuntu 14.04 in average every second or third boot gave a 1-3 seconds of grace period when I could escape to Ctrl-Alt-F2, while in case of Ubuntu 14.10 there is no such a short time slot when I could escape. (4) my configuration is set to fall into my only user account directly, I will do experiments, whether the problem is there, if the startup is without falling into an account. If I can, I will apport log files with produced with the 3.16.0-23-generic kernel as well, not only with the 3.13.0-36-generic. I try to send the remaining information after my work day, now I have to leave, sorry. --- .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8 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 CurrentDmesg: [ 11.299825] init: plymouth-upstart-bridge main process ended, respawning [ 11.329699] systemd-logind[1615]: Failed to start unit user@1000.service: Unknown unit: user@1000.service [ 11.329706] systemd-logind[1615]: Failed to start user service: Unknown unit: user@1000.service [ 11.332093] systemd-logind[1615]: New session c1 of user prohlep. [ 11.332112] systemd-logind[1615]: Linked /tmp/.X11-unix/X0 to /run/user/1000/X11-display. DistUpgraded: 2014-10-27 10:17:33,100 DEBUG enabling apt cron job DistroCodename: utopic DistroRelease: Ubuntu 14.10 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Turks PRO [Radeon HD 6570/7570/8550] [1002:6759] (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Device [1682:3195] InstallationDate: Installed on 2014-06-26 (124 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: System manufacturer System Product Name Package: xorg 1:7.7+7ubuntu2 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-36-generic root=UUID=db97e979-6d3b-43cb-9159-341be03e6c9e ro ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Tags: utopic ubuntu compiz-0.9 Uname: Linux 3.13.0-36-generic x86_64 UpgradeStatus: Upgraded to utopic on 2014-10-27 (1 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 07/18/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2301 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A89GTD-PRO/USB3 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.:bvr2301:bd07/18/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A89GTD-PRO/USB3:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3 version.
[Touch-packages] [Bug 1386534] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1386534/+attachment/4247527/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1386534 Title: kernel dependent deterministic view crash on X startup Status in “xorg” package in Ubuntu: New Bug description: kernel 3.13.0-37 and 3.16.0-23, but not kernel 3.13.0-36 The phenomenon: just when the user interface starts at the end of the Ununtu startup, the screen reamins in one solid color (very light grey, this is the everage of my colors), except for the topmost 3-4 scan lines, where one can see some sort of vibrating content. Sometimes there is a 1-3 seconds of normal operation just at the start, when Ctrl-Alt-F2 works, and swithing there one can work in the character terminal forever. But as soon as the disorder in the X view appears, even the Ctrl-Alt-F2 console change does not work visually, however a blindly stroken Ctr-Alt-Del is correctly executed. What I know: (1) on the core i3 based laptop there is no trace of this kind of view crash, while in case of the Phenom x6 1100t and Radeon HD 6570 based desktop machine the problem is fully deterministic. (2) the problem is distro independet, i.e.: I have it with Ubuntu 14.04 + kernel 3.13.0-37-generic, and also with Ubuntu 14.10 + 3.16.0-23-generic, and I do NOT have it with Ubuntu 14.04 + kernel 3.13.0-36-generic, and also with Ubuntu 14.10 + 3.13.0-36-generic. (3) In case of Ubuntu 14.04 in average every second or third boot gave a 1-3 seconds of grace period when I could escape to Ctrl-Alt-F2, while in case of Ubuntu 14.10 there is no such a short time slot when I could escape. (4) my configuration is set to fall into my only user account directly, I will do experiments, whether the problem is there, if the startup is without falling into an account. If I can, I will apport log files with produced with the 3.16.0-23-generic kernel as well, not only with the 3.13.0-36-generic. I try to send the remaining information after my work day, now I have to leave, sorry. --- .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8 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 CurrentDmesg: [ 11.299825] init: plymouth-upstart-bridge main process ended, respawning [ 11.329699] systemd-logind[1615]: Failed to start unit user@1000.service: Unknown unit: user@1000.service [ 11.329706] systemd-logind[1615]: Failed to start user service: Unknown unit: user@1000.service [ 11.332093] systemd-logind[1615]: New session c1 of user prohlep. [ 11.332112] systemd-logind[1615]: Linked /tmp/.X11-unix/X0 to /run/user/1000/X11-display. DistUpgraded: 2014-10-27 10:17:33,100 DEBUG enabling apt cron job DistroCodename: utopic DistroRelease: Ubuntu 14.10 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Turks PRO [Radeon HD 6570/7570/8550] [1002:6759] (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Device [1682:3195] InstallationDate: Installed on 2014-06-26 (124 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: System manufacturer System Product Name Package: xorg 1:7.7+7ubuntu2 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-36-generic root=UUID=db97e979-6d3b-43cb-9159-341be03e6c9e ro ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Tags: utopic ubuntu compiz-0.9 Uname: Linux 3.13.0-36-generic x86_64 UpgradeStatus: Upgraded to utopic on 2014-10-27 (1 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 07/18/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2301 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A89GTD-PRO/USB3 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.:bvr2301:bd07/18/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A89GTD-PRO/USB3:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3 version.
[Touch-packages] [Bug 1386534] xdpyinfo.txt
apport information ** Attachment added: "xdpyinfo.txt" https://bugs.launchpad.net/bugs/1386534/+attachment/4247537/+files/xdpyinfo.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1386534 Title: kernel dependent deterministic view crash on X startup Status in “xorg” package in Ubuntu: New Bug description: kernel 3.13.0-37 and 3.16.0-23, but not kernel 3.13.0-36 The phenomenon: just when the user interface starts at the end of the Ununtu startup, the screen reamins in one solid color (very light grey, this is the everage of my colors), except for the topmost 3-4 scan lines, where one can see some sort of vibrating content. Sometimes there is a 1-3 seconds of normal operation just at the start, when Ctrl-Alt-F2 works, and swithing there one can work in the character terminal forever. But as soon as the disorder in the X view appears, even the Ctrl-Alt-F2 console change does not work visually, however a blindly stroken Ctr-Alt-Del is correctly executed. What I know: (1) on the core i3 based laptop there is no trace of this kind of view crash, while in case of the Phenom x6 1100t and Radeon HD 6570 based desktop machine the problem is fully deterministic. (2) the problem is distro independet, i.e.: I have it with Ubuntu 14.04 + kernel 3.13.0-37-generic, and also with Ubuntu 14.10 + 3.16.0-23-generic, and I do NOT have it with Ubuntu 14.04 + kernel 3.13.0-36-generic, and also with Ubuntu 14.10 + 3.13.0-36-generic. (3) In case of Ubuntu 14.04 in average every second or third boot gave a 1-3 seconds of grace period when I could escape to Ctrl-Alt-F2, while in case of Ubuntu 14.10 there is no such a short time slot when I could escape. (4) my configuration is set to fall into my only user account directly, I will do experiments, whether the problem is there, if the startup is without falling into an account. If I can, I will apport log files with produced with the 3.16.0-23-generic kernel as well, not only with the 3.13.0-36-generic. I try to send the remaining information after my work day, now I have to leave, sorry. --- .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8 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 CurrentDmesg: [ 11.299825] init: plymouth-upstart-bridge main process ended, respawning [ 11.329699] systemd-logind[1615]: Failed to start unit user@1000.service: Unknown unit: user@1000.service [ 11.329706] systemd-logind[1615]: Failed to start user service: Unknown unit: user@1000.service [ 11.332093] systemd-logind[1615]: New session c1 of user prohlep. [ 11.332112] systemd-logind[1615]: Linked /tmp/.X11-unix/X0 to /run/user/1000/X11-display. DistUpgraded: 2014-10-27 10:17:33,100 DEBUG enabling apt cron job DistroCodename: utopic DistroRelease: Ubuntu 14.10 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Turks PRO [Radeon HD 6570/7570/8550] [1002:6759] (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Device [1682:3195] InstallationDate: Installed on 2014-06-26 (124 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: System manufacturer System Product Name Package: xorg 1:7.7+7ubuntu2 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-36-generic root=UUID=db97e979-6d3b-43cb-9159-341be03e6c9e ro ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Tags: utopic ubuntu compiz-0.9 Uname: Linux 3.13.0-36-generic x86_64 UpgradeStatus: Upgraded to utopic on 2014-10-27 (1 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 07/18/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2301 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A89GTD-PRO/USB3 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.:bvr2301:bd07/18/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A89GTD-PRO/USB3:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3 version.libgl1
[Touch-packages] [Bug 1386534] UnitySupportTest.txt
apport information ** Attachment added: "UnitySupportTest.txt" https://bugs.launchpad.net/bugs/1386534/+attachment/4247533/+files/UnitySupportTest.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1386534 Title: kernel dependent deterministic view crash on X startup Status in “xorg” package in Ubuntu: New Bug description: kernel 3.13.0-37 and 3.16.0-23, but not kernel 3.13.0-36 The phenomenon: just when the user interface starts at the end of the Ununtu startup, the screen reamins in one solid color (very light grey, this is the everage of my colors), except for the topmost 3-4 scan lines, where one can see some sort of vibrating content. Sometimes there is a 1-3 seconds of normal operation just at the start, when Ctrl-Alt-F2 works, and swithing there one can work in the character terminal forever. But as soon as the disorder in the X view appears, even the Ctrl-Alt-F2 console change does not work visually, however a blindly stroken Ctr-Alt-Del is correctly executed. What I know: (1) on the core i3 based laptop there is no trace of this kind of view crash, while in case of the Phenom x6 1100t and Radeon HD 6570 based desktop machine the problem is fully deterministic. (2) the problem is distro independet, i.e.: I have it with Ubuntu 14.04 + kernel 3.13.0-37-generic, and also with Ubuntu 14.10 + 3.16.0-23-generic, and I do NOT have it with Ubuntu 14.04 + kernel 3.13.0-36-generic, and also with Ubuntu 14.10 + 3.13.0-36-generic. (3) In case of Ubuntu 14.04 in average every second or third boot gave a 1-3 seconds of grace period when I could escape to Ctrl-Alt-F2, while in case of Ubuntu 14.10 there is no such a short time slot when I could escape. (4) my configuration is set to fall into my only user account directly, I will do experiments, whether the problem is there, if the startup is without falling into an account. If I can, I will apport log files with produced with the 3.16.0-23-generic kernel as well, not only with the 3.13.0-36-generic. I try to send the remaining information after my work day, now I have to leave, sorry. --- .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8 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 CurrentDmesg: [ 11.299825] init: plymouth-upstart-bridge main process ended, respawning [ 11.329699] systemd-logind[1615]: Failed to start unit user@1000.service: Unknown unit: user@1000.service [ 11.329706] systemd-logind[1615]: Failed to start user service: Unknown unit: user@1000.service [ 11.332093] systemd-logind[1615]: New session c1 of user prohlep. [ 11.332112] systemd-logind[1615]: Linked /tmp/.X11-unix/X0 to /run/user/1000/X11-display. DistUpgraded: 2014-10-27 10:17:33,100 DEBUG enabling apt cron job DistroCodename: utopic DistroRelease: Ubuntu 14.10 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Turks PRO [Radeon HD 6570/7570/8550] [1002:6759] (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Device [1682:3195] InstallationDate: Installed on 2014-06-26 (124 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: System manufacturer System Product Name Package: xorg 1:7.7+7ubuntu2 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-36-generic root=UUID=db97e979-6d3b-43cb-9159-341be03e6c9e ro ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Tags: utopic ubuntu compiz-0.9 Uname: Linux 3.13.0-36-generic x86_64 UpgradeStatus: Upgraded to utopic on 2014-10-27 (1 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 07/18/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2301 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A89GTD-PRO/USB3 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.:bvr2301:bd07/18/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A89GTD-PRO/USB3:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3
[Touch-packages] [Bug 1386534] GconfCompiz.txt
apport information ** Attachment added: "GconfCompiz.txt" https://bugs.launchpad.net/bugs/1386534/+attachment/4247520/+files/GconfCompiz.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1386534 Title: kernel dependent deterministic view crash on X startup Status in “xorg” package in Ubuntu: New Bug description: kernel 3.13.0-37 and 3.16.0-23, but not kernel 3.13.0-36 The phenomenon: just when the user interface starts at the end of the Ununtu startup, the screen reamins in one solid color (very light grey, this is the everage of my colors), except for the topmost 3-4 scan lines, where one can see some sort of vibrating content. Sometimes there is a 1-3 seconds of normal operation just at the start, when Ctrl-Alt-F2 works, and swithing there one can work in the character terminal forever. But as soon as the disorder in the X view appears, even the Ctrl-Alt-F2 console change does not work visually, however a blindly stroken Ctr-Alt-Del is correctly executed. What I know: (1) on the core i3 based laptop there is no trace of this kind of view crash, while in case of the Phenom x6 1100t and Radeon HD 6570 based desktop machine the problem is fully deterministic. (2) the problem is distro independet, i.e.: I have it with Ubuntu 14.04 + kernel 3.13.0-37-generic, and also with Ubuntu 14.10 + 3.16.0-23-generic, and I do NOT have it with Ubuntu 14.04 + kernel 3.13.0-36-generic, and also with Ubuntu 14.10 + 3.13.0-36-generic. (3) In case of Ubuntu 14.04 in average every second or third boot gave a 1-3 seconds of grace period when I could escape to Ctrl-Alt-F2, while in case of Ubuntu 14.10 there is no such a short time slot when I could escape. (4) my configuration is set to fall into my only user account directly, I will do experiments, whether the problem is there, if the startup is without falling into an account. If I can, I will apport log files with produced with the 3.16.0-23-generic kernel as well, not only with the 3.13.0-36-generic. I try to send the remaining information after my work day, now I have to leave, sorry. --- .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8 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 CurrentDmesg: [ 11.299825] init: plymouth-upstart-bridge main process ended, respawning [ 11.329699] systemd-logind[1615]: Failed to start unit user@1000.service: Unknown unit: user@1000.service [ 11.329706] systemd-logind[1615]: Failed to start user service: Unknown unit: user@1000.service [ 11.332093] systemd-logind[1615]: New session c1 of user prohlep. [ 11.332112] systemd-logind[1615]: Linked /tmp/.X11-unix/X0 to /run/user/1000/X11-display. DistUpgraded: 2014-10-27 10:17:33,100 DEBUG enabling apt cron job DistroCodename: utopic DistroRelease: Ubuntu 14.10 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Turks PRO [Radeon HD 6570/7570/8550] [1002:6759] (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Device [1682:3195] InstallationDate: Installed on 2014-06-26 (124 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: System manufacturer System Product Name Package: xorg 1:7.7+7ubuntu2 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-36-generic root=UUID=db97e979-6d3b-43cb-9159-341be03e6c9e ro ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Tags: utopic ubuntu compiz-0.9 Uname: Linux 3.13.0-36-generic x86_64 UpgradeStatus: Upgraded to utopic on 2014-10-27 (1 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 07/18/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2301 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A89GTD-PRO/USB3 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.:bvr2301:bd07/18/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A89GTD-PRO/USB3:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3 version.
[Touch-packages] [Bug 1386534] Xrandr.txt
apport information ** Attachment added: "Xrandr.txt" https://bugs.launchpad.net/bugs/1386534/+attachment/4247536/+files/Xrandr.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1386534 Title: kernel dependent deterministic view crash on X startup Status in “xorg” package in Ubuntu: New Bug description: kernel 3.13.0-37 and 3.16.0-23, but not kernel 3.13.0-36 The phenomenon: just when the user interface starts at the end of the Ununtu startup, the screen reamins in one solid color (very light grey, this is the everage of my colors), except for the topmost 3-4 scan lines, where one can see some sort of vibrating content. Sometimes there is a 1-3 seconds of normal operation just at the start, when Ctrl-Alt-F2 works, and swithing there one can work in the character terminal forever. But as soon as the disorder in the X view appears, even the Ctrl-Alt-F2 console change does not work visually, however a blindly stroken Ctr-Alt-Del is correctly executed. What I know: (1) on the core i3 based laptop there is no trace of this kind of view crash, while in case of the Phenom x6 1100t and Radeon HD 6570 based desktop machine the problem is fully deterministic. (2) the problem is distro independet, i.e.: I have it with Ubuntu 14.04 + kernel 3.13.0-37-generic, and also with Ubuntu 14.10 + 3.16.0-23-generic, and I do NOT have it with Ubuntu 14.04 + kernel 3.13.0-36-generic, and also with Ubuntu 14.10 + 3.13.0-36-generic. (3) In case of Ubuntu 14.04 in average every second or third boot gave a 1-3 seconds of grace period when I could escape to Ctrl-Alt-F2, while in case of Ubuntu 14.10 there is no such a short time slot when I could escape. (4) my configuration is set to fall into my only user account directly, I will do experiments, whether the problem is there, if the startup is without falling into an account. If I can, I will apport log files with produced with the 3.16.0-23-generic kernel as well, not only with the 3.13.0-36-generic. I try to send the remaining information after my work day, now I have to leave, sorry. --- .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8 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 CurrentDmesg: [ 11.299825] init: plymouth-upstart-bridge main process ended, respawning [ 11.329699] systemd-logind[1615]: Failed to start unit user@1000.service: Unknown unit: user@1000.service [ 11.329706] systemd-logind[1615]: Failed to start user service: Unknown unit: user@1000.service [ 11.332093] systemd-logind[1615]: New session c1 of user prohlep. [ 11.332112] systemd-logind[1615]: Linked /tmp/.X11-unix/X0 to /run/user/1000/X11-display. DistUpgraded: 2014-10-27 10:17:33,100 DEBUG enabling apt cron job DistroCodename: utopic DistroRelease: Ubuntu 14.10 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Turks PRO [Radeon HD 6570/7570/8550] [1002:6759] (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Device [1682:3195] InstallationDate: Installed on 2014-06-26 (124 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: System manufacturer System Product Name Package: xorg 1:7.7+7ubuntu2 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-36-generic root=UUID=db97e979-6d3b-43cb-9159-341be03e6c9e ro ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Tags: utopic ubuntu compiz-0.9 Uname: Linux 3.13.0-36-generic x86_64 UpgradeStatus: Upgraded to utopic on 2014-10-27 (1 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 07/18/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2301 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A89GTD-PRO/USB3 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.:bvr2301:bd07/18/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A89GTD-PRO/USB3:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3 version.libgl1-mesa
[Touch-packages] [Bug 1386534] LightdmDisplayLog.txt
apport information ** Attachment added: "LightdmDisplayLog.txt" https://bugs.launchpad.net/bugs/1386534/+attachment/4247521/+files/LightdmDisplayLog.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1386534 Title: kernel dependent deterministic view crash on X startup Status in “xorg” package in Ubuntu: New Bug description: kernel 3.13.0-37 and 3.16.0-23, but not kernel 3.13.0-36 The phenomenon: just when the user interface starts at the end of the Ununtu startup, the screen reamins in one solid color (very light grey, this is the everage of my colors), except for the topmost 3-4 scan lines, where one can see some sort of vibrating content. Sometimes there is a 1-3 seconds of normal operation just at the start, when Ctrl-Alt-F2 works, and swithing there one can work in the character terminal forever. But as soon as the disorder in the X view appears, even the Ctrl-Alt-F2 console change does not work visually, however a blindly stroken Ctr-Alt-Del is correctly executed. What I know: (1) on the core i3 based laptop there is no trace of this kind of view crash, while in case of the Phenom x6 1100t and Radeon HD 6570 based desktop machine the problem is fully deterministic. (2) the problem is distro independet, i.e.: I have it with Ubuntu 14.04 + kernel 3.13.0-37-generic, and also with Ubuntu 14.10 + 3.16.0-23-generic, and I do NOT have it with Ubuntu 14.04 + kernel 3.13.0-36-generic, and also with Ubuntu 14.10 + 3.13.0-36-generic. (3) In case of Ubuntu 14.04 in average every second or third boot gave a 1-3 seconds of grace period when I could escape to Ctrl-Alt-F2, while in case of Ubuntu 14.10 there is no such a short time slot when I could escape. (4) my configuration is set to fall into my only user account directly, I will do experiments, whether the problem is there, if the startup is without falling into an account. If I can, I will apport log files with produced with the 3.16.0-23-generic kernel as well, not only with the 3.13.0-36-generic. I try to send the remaining information after my work day, now I have to leave, sorry. --- .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8 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 CurrentDmesg: [ 11.299825] init: plymouth-upstart-bridge main process ended, respawning [ 11.329699] systemd-logind[1615]: Failed to start unit user@1000.service: Unknown unit: user@1000.service [ 11.329706] systemd-logind[1615]: Failed to start user service: Unknown unit: user@1000.service [ 11.332093] systemd-logind[1615]: New session c1 of user prohlep. [ 11.332112] systemd-logind[1615]: Linked /tmp/.X11-unix/X0 to /run/user/1000/X11-display. DistUpgraded: 2014-10-27 10:17:33,100 DEBUG enabling apt cron job DistroCodename: utopic DistroRelease: Ubuntu 14.10 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Turks PRO [Radeon HD 6570/7570/8550] [1002:6759] (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Device [1682:3195] InstallationDate: Installed on 2014-06-26 (124 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: System manufacturer System Product Name Package: xorg 1:7.7+7ubuntu2 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-36-generic root=UUID=db97e979-6d3b-43cb-9159-341be03e6c9e ro ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Tags: utopic ubuntu compiz-0.9 Uname: Linux 3.13.0-36-generic x86_64 UpgradeStatus: Upgraded to utopic on 2014-10-27 (1 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 07/18/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2301 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A89GTD-PRO/USB3 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.:bvr2301:bd07/18/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A89GTD-PRO/USB3:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu
[Touch-packages] [Bug 1386534] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1386534/+attachment/4247529/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1386534 Title: kernel dependent deterministic view crash on X startup Status in “xorg” package in Ubuntu: New Bug description: kernel 3.13.0-37 and 3.16.0-23, but not kernel 3.13.0-36 The phenomenon: just when the user interface starts at the end of the Ununtu startup, the screen reamins in one solid color (very light grey, this is the everage of my colors), except for the topmost 3-4 scan lines, where one can see some sort of vibrating content. Sometimes there is a 1-3 seconds of normal operation just at the start, when Ctrl-Alt-F2 works, and swithing there one can work in the character terminal forever. But as soon as the disorder in the X view appears, even the Ctrl-Alt-F2 console change does not work visually, however a blindly stroken Ctr-Alt-Del is correctly executed. What I know: (1) on the core i3 based laptop there is no trace of this kind of view crash, while in case of the Phenom x6 1100t and Radeon HD 6570 based desktop machine the problem is fully deterministic. (2) the problem is distro independet, i.e.: I have it with Ubuntu 14.04 + kernel 3.13.0-37-generic, and also with Ubuntu 14.10 + 3.16.0-23-generic, and I do NOT have it with Ubuntu 14.04 + kernel 3.13.0-36-generic, and also with Ubuntu 14.10 + 3.13.0-36-generic. (3) In case of Ubuntu 14.04 in average every second or third boot gave a 1-3 seconds of grace period when I could escape to Ctrl-Alt-F2, while in case of Ubuntu 14.10 there is no such a short time slot when I could escape. (4) my configuration is set to fall into my only user account directly, I will do experiments, whether the problem is there, if the startup is without falling into an account. If I can, I will apport log files with produced with the 3.16.0-23-generic kernel as well, not only with the 3.13.0-36-generic. I try to send the remaining information after my work day, now I have to leave, sorry. --- .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8 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 CurrentDmesg: [ 11.299825] init: plymouth-upstart-bridge main process ended, respawning [ 11.329699] systemd-logind[1615]: Failed to start unit user@1000.service: Unknown unit: user@1000.service [ 11.329706] systemd-logind[1615]: Failed to start user service: Unknown unit: user@1000.service [ 11.332093] systemd-logind[1615]: New session c1 of user prohlep. [ 11.332112] systemd-logind[1615]: Linked /tmp/.X11-unix/X0 to /run/user/1000/X11-display. DistUpgraded: 2014-10-27 10:17:33,100 DEBUG enabling apt cron job DistroCodename: utopic DistroRelease: Ubuntu 14.10 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Turks PRO [Radeon HD 6570/7570/8550] [1002:6759] (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Device [1682:3195] InstallationDate: Installed on 2014-06-26 (124 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: System manufacturer System Product Name Package: xorg 1:7.7+7ubuntu2 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-36-generic root=UUID=db97e979-6d3b-43cb-9159-341be03e6c9e ro ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Tags: utopic ubuntu compiz-0.9 Uname: Linux 3.13.0-36-generic x86_64 UpgradeStatus: Upgraded to utopic on 2014-10-27 (1 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 07/18/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2301 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A89GTD-PRO/USB3 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.:bvr2301:bd07/18/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A89GTD-PRO/USB3:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3 ve
[Touch-packages] [Bug 1386534] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1386534/+attachment/4247531/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1386534 Title: kernel dependent deterministic view crash on X startup Status in “xorg” package in Ubuntu: New Bug description: kernel 3.13.0-37 and 3.16.0-23, but not kernel 3.13.0-36 The phenomenon: just when the user interface starts at the end of the Ununtu startup, the screen reamins in one solid color (very light grey, this is the everage of my colors), except for the topmost 3-4 scan lines, where one can see some sort of vibrating content. Sometimes there is a 1-3 seconds of normal operation just at the start, when Ctrl-Alt-F2 works, and swithing there one can work in the character terminal forever. But as soon as the disorder in the X view appears, even the Ctrl-Alt-F2 console change does not work visually, however a blindly stroken Ctr-Alt-Del is correctly executed. What I know: (1) on the core i3 based laptop there is no trace of this kind of view crash, while in case of the Phenom x6 1100t and Radeon HD 6570 based desktop machine the problem is fully deterministic. (2) the problem is distro independet, i.e.: I have it with Ubuntu 14.04 + kernel 3.13.0-37-generic, and also with Ubuntu 14.10 + 3.16.0-23-generic, and I do NOT have it with Ubuntu 14.04 + kernel 3.13.0-36-generic, and also with Ubuntu 14.10 + 3.13.0-36-generic. (3) In case of Ubuntu 14.04 in average every second or third boot gave a 1-3 seconds of grace period when I could escape to Ctrl-Alt-F2, while in case of Ubuntu 14.10 there is no such a short time slot when I could escape. (4) my configuration is set to fall into my only user account directly, I will do experiments, whether the problem is there, if the startup is without falling into an account. If I can, I will apport log files with produced with the 3.16.0-23-generic kernel as well, not only with the 3.13.0-36-generic. I try to send the remaining information after my work day, now I have to leave, sorry. --- .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8 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 CurrentDmesg: [ 11.299825] init: plymouth-upstart-bridge main process ended, respawning [ 11.329699] systemd-logind[1615]: Failed to start unit user@1000.service: Unknown unit: user@1000.service [ 11.329706] systemd-logind[1615]: Failed to start user service: Unknown unit: user@1000.service [ 11.332093] systemd-logind[1615]: New session c1 of user prohlep. [ 11.332112] systemd-logind[1615]: Linked /tmp/.X11-unix/X0 to /run/user/1000/X11-display. DistUpgraded: 2014-10-27 10:17:33,100 DEBUG enabling apt cron job DistroCodename: utopic DistroRelease: Ubuntu 14.10 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Turks PRO [Radeon HD 6570/7570/8550] [1002:6759] (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Device [1682:3195] InstallationDate: Installed on 2014-06-26 (124 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: System manufacturer System Product Name Package: xorg 1:7.7+7ubuntu2 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-36-generic root=UUID=db97e979-6d3b-43cb-9159-341be03e6c9e ro ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Tags: utopic ubuntu compiz-0.9 Uname: Linux 3.13.0-36-generic x86_64 UpgradeStatus: Upgraded to utopic on 2014-10-27 (1 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 07/18/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2301 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A89GTD-PRO/USB3 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.:bvr2301:bd07/18/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A89GTD-PRO/USB3:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3 version.libgl1-mesa
[Touch-packages] [Bug 1386534] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1386534/+attachment/4247528/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1386534 Title: kernel dependent deterministic view crash on X startup Status in “xorg” package in Ubuntu: New Bug description: kernel 3.13.0-37 and 3.16.0-23, but not kernel 3.13.0-36 The phenomenon: just when the user interface starts at the end of the Ununtu startup, the screen reamins in one solid color (very light grey, this is the everage of my colors), except for the topmost 3-4 scan lines, where one can see some sort of vibrating content. Sometimes there is a 1-3 seconds of normal operation just at the start, when Ctrl-Alt-F2 works, and swithing there one can work in the character terminal forever. But as soon as the disorder in the X view appears, even the Ctrl-Alt-F2 console change does not work visually, however a blindly stroken Ctr-Alt-Del is correctly executed. What I know: (1) on the core i3 based laptop there is no trace of this kind of view crash, while in case of the Phenom x6 1100t and Radeon HD 6570 based desktop machine the problem is fully deterministic. (2) the problem is distro independet, i.e.: I have it with Ubuntu 14.04 + kernel 3.13.0-37-generic, and also with Ubuntu 14.10 + 3.16.0-23-generic, and I do NOT have it with Ubuntu 14.04 + kernel 3.13.0-36-generic, and also with Ubuntu 14.10 + 3.13.0-36-generic. (3) In case of Ubuntu 14.04 in average every second or third boot gave a 1-3 seconds of grace period when I could escape to Ctrl-Alt-F2, while in case of Ubuntu 14.10 there is no such a short time slot when I could escape. (4) my configuration is set to fall into my only user account directly, I will do experiments, whether the problem is there, if the startup is without falling into an account. If I can, I will apport log files with produced with the 3.16.0-23-generic kernel as well, not only with the 3.13.0-36-generic. I try to send the remaining information after my work day, now I have to leave, sorry. --- .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8 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 CurrentDmesg: [ 11.299825] init: plymouth-upstart-bridge main process ended, respawning [ 11.329699] systemd-logind[1615]: Failed to start unit user@1000.service: Unknown unit: user@1000.service [ 11.329706] systemd-logind[1615]: Failed to start user service: Unknown unit: user@1000.service [ 11.332093] systemd-logind[1615]: New session c1 of user prohlep. [ 11.332112] systemd-logind[1615]: Linked /tmp/.X11-unix/X0 to /run/user/1000/X11-display. DistUpgraded: 2014-10-27 10:17:33,100 DEBUG enabling apt cron job DistroCodename: utopic DistroRelease: Ubuntu 14.10 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Turks PRO [Radeon HD 6570/7570/8550] [1002:6759] (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Device [1682:3195] InstallationDate: Installed on 2014-06-26 (124 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: System manufacturer System Product Name Package: xorg 1:7.7+7ubuntu2 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-36-generic root=UUID=db97e979-6d3b-43cb-9159-341be03e6c9e ro ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Tags: utopic ubuntu compiz-0.9 Uname: Linux 3.13.0-36-generic x86_64 UpgradeStatus: Upgraded to utopic on 2014-10-27 (1 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 07/18/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2301 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A89GTD-PRO/USB3 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.:bvr2301:bd07/18/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A89GTD-PRO/USB3:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3 version.
[Touch-packages] [Bug 1386534] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1386534/+attachment/4247518/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1386534 Title: kernel dependent deterministic view crash on X startup Status in “xorg” package in Ubuntu: New Bug description: kernel 3.13.0-37 and 3.16.0-23, but not kernel 3.13.0-36 The phenomenon: just when the user interface starts at the end of the Ununtu startup, the screen reamins in one solid color (very light grey, this is the everage of my colors), except for the topmost 3-4 scan lines, where one can see some sort of vibrating content. Sometimes there is a 1-3 seconds of normal operation just at the start, when Ctrl-Alt-F2 works, and swithing there one can work in the character terminal forever. But as soon as the disorder in the X view appears, even the Ctrl-Alt-F2 console change does not work visually, however a blindly stroken Ctr-Alt-Del is correctly executed. What I know: (1) on the core i3 based laptop there is no trace of this kind of view crash, while in case of the Phenom x6 1100t and Radeon HD 6570 based desktop machine the problem is fully deterministic. (2) the problem is distro independet, i.e.: I have it with Ubuntu 14.04 + kernel 3.13.0-37-generic, and also with Ubuntu 14.10 + 3.16.0-23-generic, and I do NOT have it with Ubuntu 14.04 + kernel 3.13.0-36-generic, and also with Ubuntu 14.10 + 3.13.0-36-generic. (3) In case of Ubuntu 14.04 in average every second or third boot gave a 1-3 seconds of grace period when I could escape to Ctrl-Alt-F2, while in case of Ubuntu 14.10 there is no such a short time slot when I could escape. (4) my configuration is set to fall into my only user account directly, I will do experiments, whether the problem is there, if the startup is without falling into an account. If I can, I will apport log files with produced with the 3.16.0-23-generic kernel as well, not only with the 3.13.0-36-generic. I try to send the remaining information after my work day, now I have to leave, sorry. --- .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8 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 CurrentDmesg: [ 11.299825] init: plymouth-upstart-bridge main process ended, respawning [ 11.329699] systemd-logind[1615]: Failed to start unit user@1000.service: Unknown unit: user@1000.service [ 11.329706] systemd-logind[1615]: Failed to start user service: Unknown unit: user@1000.service [ 11.332093] systemd-logind[1615]: New session c1 of user prohlep. [ 11.332112] systemd-logind[1615]: Linked /tmp/.X11-unix/X0 to /run/user/1000/X11-display. DistUpgraded: 2014-10-27 10:17:33,100 DEBUG enabling apt cron job DistroCodename: utopic DistroRelease: Ubuntu 14.10 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Turks PRO [Radeon HD 6570/7570/8550] [1002:6759] (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Device [1682:3195] InstallationDate: Installed on 2014-06-26 (124 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: System manufacturer System Product Name Package: xorg 1:7.7+7ubuntu2 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-36-generic root=UUID=db97e979-6d3b-43cb-9159-341be03e6c9e ro ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Tags: utopic ubuntu compiz-0.9 Uname: Linux 3.13.0-36-generic x86_64 UpgradeStatus: Upgraded to utopic on 2014-10-27 (1 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 07/18/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2301 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A89GTD-PRO/USB3 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.:bvr2301:bd07/18/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A89GTD-PRO/USB3:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3 versio
[Touch-packages] [Bug 1386534] DpkgLog.txt
apport information ** Attachment added: "DpkgLog.txt" https://bugs.launchpad.net/bugs/1386534/+attachment/4247519/+files/DpkgLog.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1386534 Title: kernel dependent deterministic view crash on X startup Status in “xorg” package in Ubuntu: New Bug description: kernel 3.13.0-37 and 3.16.0-23, but not kernel 3.13.0-36 The phenomenon: just when the user interface starts at the end of the Ununtu startup, the screen reamins in one solid color (very light grey, this is the everage of my colors), except for the topmost 3-4 scan lines, where one can see some sort of vibrating content. Sometimes there is a 1-3 seconds of normal operation just at the start, when Ctrl-Alt-F2 works, and swithing there one can work in the character terminal forever. But as soon as the disorder in the X view appears, even the Ctrl-Alt-F2 console change does not work visually, however a blindly stroken Ctr-Alt-Del is correctly executed. What I know: (1) on the core i3 based laptop there is no trace of this kind of view crash, while in case of the Phenom x6 1100t and Radeon HD 6570 based desktop machine the problem is fully deterministic. (2) the problem is distro independet, i.e.: I have it with Ubuntu 14.04 + kernel 3.13.0-37-generic, and also with Ubuntu 14.10 + 3.16.0-23-generic, and I do NOT have it with Ubuntu 14.04 + kernel 3.13.0-36-generic, and also with Ubuntu 14.10 + 3.13.0-36-generic. (3) In case of Ubuntu 14.04 in average every second or third boot gave a 1-3 seconds of grace period when I could escape to Ctrl-Alt-F2, while in case of Ubuntu 14.10 there is no such a short time slot when I could escape. (4) my configuration is set to fall into my only user account directly, I will do experiments, whether the problem is there, if the startup is without falling into an account. If I can, I will apport log files with produced with the 3.16.0-23-generic kernel as well, not only with the 3.13.0-36-generic. I try to send the remaining information after my work day, now I have to leave, sorry. --- .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8 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 CurrentDmesg: [ 11.299825] init: plymouth-upstart-bridge main process ended, respawning [ 11.329699] systemd-logind[1615]: Failed to start unit user@1000.service: Unknown unit: user@1000.service [ 11.329706] systemd-logind[1615]: Failed to start user service: Unknown unit: user@1000.service [ 11.332093] systemd-logind[1615]: New session c1 of user prohlep. [ 11.332112] systemd-logind[1615]: Linked /tmp/.X11-unix/X0 to /run/user/1000/X11-display. DistUpgraded: 2014-10-27 10:17:33,100 DEBUG enabling apt cron job DistroCodename: utopic DistroRelease: Ubuntu 14.10 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Turks PRO [Radeon HD 6570/7570/8550] [1002:6759] (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Device [1682:3195] InstallationDate: Installed on 2014-06-26 (124 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: System manufacturer System Product Name Package: xorg 1:7.7+7ubuntu2 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-36-generic root=UUID=db97e979-6d3b-43cb-9159-341be03e6c9e ro ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Tags: utopic ubuntu compiz-0.9 Uname: Linux 3.13.0-36-generic x86_64 UpgradeStatus: Upgraded to utopic on 2014-10-27 (1 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 07/18/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2301 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A89GTD-PRO/USB3 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.:bvr2301:bd07/18/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A89GTD-PRO/USB3:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3 version.libgl1-m
[Touch-packages] [Bug 1386534] BootLog.txt
apport information ** Attachment added: "BootLog.txt" https://bugs.launchpad.net/bugs/1386534/+attachment/4247517/+files/BootLog.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1386534 Title: kernel dependent deterministic view crash on X startup Status in “xorg” package in Ubuntu: New Bug description: kernel 3.13.0-37 and 3.16.0-23, but not kernel 3.13.0-36 The phenomenon: just when the user interface starts at the end of the Ununtu startup, the screen reamins in one solid color (very light grey, this is the everage of my colors), except for the topmost 3-4 scan lines, where one can see some sort of vibrating content. Sometimes there is a 1-3 seconds of normal operation just at the start, when Ctrl-Alt-F2 works, and swithing there one can work in the character terminal forever. But as soon as the disorder in the X view appears, even the Ctrl-Alt-F2 console change does not work visually, however a blindly stroken Ctr-Alt-Del is correctly executed. What I know: (1) on the core i3 based laptop there is no trace of this kind of view crash, while in case of the Phenom x6 1100t and Radeon HD 6570 based desktop machine the problem is fully deterministic. (2) the problem is distro independet, i.e.: I have it with Ubuntu 14.04 + kernel 3.13.0-37-generic, and also with Ubuntu 14.10 + 3.16.0-23-generic, and I do NOT have it with Ubuntu 14.04 + kernel 3.13.0-36-generic, and also with Ubuntu 14.10 + 3.13.0-36-generic. (3) In case of Ubuntu 14.04 in average every second or third boot gave a 1-3 seconds of grace period when I could escape to Ctrl-Alt-F2, while in case of Ubuntu 14.10 there is no such a short time slot when I could escape. (4) my configuration is set to fall into my only user account directly, I will do experiments, whether the problem is there, if the startup is without falling into an account. If I can, I will apport log files with produced with the 3.16.0-23-generic kernel as well, not only with the 3.13.0-36-generic. I try to send the remaining information after my work day, now I have to leave, sorry. --- .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8 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 CurrentDmesg: [ 11.299825] init: plymouth-upstart-bridge main process ended, respawning [ 11.329699] systemd-logind[1615]: Failed to start unit user@1000.service: Unknown unit: user@1000.service [ 11.329706] systemd-logind[1615]: Failed to start user service: Unknown unit: user@1000.service [ 11.332093] systemd-logind[1615]: New session c1 of user prohlep. [ 11.332112] systemd-logind[1615]: Linked /tmp/.X11-unix/X0 to /run/user/1000/X11-display. DistUpgraded: 2014-10-27 10:17:33,100 DEBUG enabling apt cron job DistroCodename: utopic DistroRelease: Ubuntu 14.10 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Turks PRO [Radeon HD 6570/7570/8550] [1002:6759] (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Device [1682:3195] InstallationDate: Installed on 2014-06-26 (124 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: System manufacturer System Product Name Package: xorg 1:7.7+7ubuntu2 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-36-generic root=UUID=db97e979-6d3b-43cb-9159-341be03e6c9e ro ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Tags: utopic ubuntu compiz-0.9 Uname: Linux 3.13.0-36-generic x86_64 UpgradeStatus: Upgraded to utopic on 2014-10-27 (1 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 07/18/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2301 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A89GTD-PRO/USB3 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.:bvr2301:bd07/18/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A89GTD-PRO/USB3:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3 version.libgl1-m
[Touch-packages] [Bug 1386534] Re: kernel dependent deterministic view crash on X startup
apport information ** Tags added: apport-collected compiz-0.9 ubuntu utopic ** Description changed: kernel 3.13.0-37 and 3.16.0-23, but not kernel 3.13.0-36 The phenomenon: just when the user interface starts at the end of the Ununtu startup, the screen reamins in one solid color (very light grey, this is the everage of my colors), except for the topmost 3-4 scan lines, where one can see some sort of vibrating content. Sometimes there is a 1-3 seconds of normal operation just at the start, when Ctrl-Alt-F2 works, and swithing there one can work in the character terminal forever. But as soon as the disorder in the X view appears, even the Ctrl-Alt-F2 console change does not work visually, however a blindly stroken Ctr-Alt-Del is correctly executed. What I know: (1) on the core i3 based laptop there is no trace of this kind of view crash, while in case of the Phenom x6 1100t and Radeon HD 6570 based desktop machine the problem is fully deterministic. (2) the problem is distro independet, i.e.: I have it with Ubuntu 14.04 + kernel 3.13.0-37-generic, and also with Ubuntu 14.10 + 3.16.0-23-generic, and I do NOT have it with Ubuntu 14.04 + kernel 3.13.0-36-generic, and also with Ubuntu 14.10 + 3.13.0-36-generic. (3) In case of Ubuntu 14.04 in average every second or third boot gave a 1-3 seconds of grace period when I could escape to Ctrl-Alt-F2, while in case of Ubuntu 14.10 there is no such a short time slot when I could escape. (4) my configuration is set to fall into my only user account directly, I will do experiments, whether the problem is there, if the startup is without falling into an account. If I can, I will apport log files with produced with the 3.16.0-23-generic kernel as well, not only with the 3.13.0-36-generic. - I try to send the remaining information after my work day, now I have to - leave, sorry. + I try to send the remaining information after my work day, now I have to leave, sorry. + --- + .tmp.unity.support.test.0: + + ApportVersion: 2.14.7-0ubuntu8 + 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 + CurrentDmesg: + [ 11.299825] init: plymouth-upstart-bridge main process ended, respawning + [ 11.329699] systemd-logind[1615]: Failed to start unit user@1000.service: Unknown unit: user@1000.service + [ 11.329706] systemd-logind[1615]: Failed to start user service: Unknown unit: user@1000.service + [ 11.332093] systemd-logind[1615]: New session c1 of user prohlep. + [ 11.332112] systemd-logind[1615]: Linked /tmp/.X11-unix/X0 to /run/user/1000/X11-display. + DistUpgraded: 2014-10-27 10:17:33,100 DEBUG enabling apt cron job + DistroCodename: utopic + DistroRelease: Ubuntu 14.10 + DistroVariant: ubuntu + ExtraDebuggingInterest: Yes, including running git bisection searches + GraphicsCard: + Advanced Micro Devices, Inc. [AMD/ATI] Turks PRO [Radeon HD 6570/7570/8550] [1002:6759] (prog-if 00 [VGA controller]) +Subsystem: XFX Pine Group Inc. Device [1682:3195] + InstallationDate: Installed on 2014-06-26 (124 days ago) + InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) + MachineType: System manufacturer System Product Name + Package: xorg 1:7.7+7ubuntu2 + PackageArchitecture: amd64 + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-36-generic root=UUID=db97e979-6d3b-43cb-9159-341be03e6c9e ro + ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 + Tags: utopic ubuntu compiz-0.9 + Uname: Linux 3.13.0-36-generic x86_64 + UpgradeStatus: Upgraded to utopic on 2014-10-27 (1 days ago) + UserGroups: + + _MarkForUpload: True + dmi.bios.date: 07/18/2011 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: 2301 + dmi.board.asset.tag: To Be Filled By O.E.M. + dmi.board.name: M4A89GTD-PRO/USB3 + 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.:bvr2301:bd07/18/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A89GTD-PRO/USB3:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: + dmi.product.name: System Product Name + dmi.product.version: System Version + dmi.sys.vendor: System manufacturer + version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 + version.ia32-libs: ia32-libs N/A + version.libdrm2: libdrm2 2.4.56-1 + version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3 + version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A + version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3 + version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1 + version.xserver-xorg-input-evdev: xserver-xorg-input-evde
[Touch-packages] [Bug 1246981] Re: Bluetooth mouse failes to re-connect after sleep.
This problem was not happening on 14.04, but now is happening again on 14.10. -- 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/1246981 Title: Bluetooth mouse failes to re-connect after sleep. Status in “bluez” package in Ubuntu: Confirmed Bug description: This exact harware was working faultlessly in 13.04. Since re- installing at 13.10 the mouse consistently failes to reconnect after the device either hybernates or ever goes to screen saver sleep. I have to remove the dive and re-add it each time (which works well). There are other issues with the bluetooth stack as well in that I have not found any way to use bluetooth tethering to my mobile which again worked well and was easy to configure in 13.04 Peter. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: bluetooth 4.101-0ubuntu8b1 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Fri Nov 1 16:44:37 2013 InstallationDate: Installed on 2013-10-19 (13 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) InterestingModules: bnep rfcomm btusb bluetooth MachineType: Dell Inc. Latitude E6530 MarkForUpload: True PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=8283de78-9264-42bf-a8b4-25643fa1475f ro quiet splash SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/13/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 07Y85M dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA09:bd12/13/2012:svnDellInc.:pnLatitudeE6530:pvr01:rvnDellInc.:rn07Y85M:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6530 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: 20:16:D8:9C:38:E5 ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING PSCAN ISCAN RX bytes:1817731 acl:117432 sco:0 events:5271 errors:0 TX bytes:37955 acl:131 sco:0 commands:5096 errors:0 syslog: Nov 1 14:50:19 pnunn-Latitude-E6530 bluetoothd[1015]: Discovery session 0x7f6489f7b450 with :1.582 activated Nov 1 14:50:25 pnunn-Latitude-E6530 bluetoothd[1015]: Unknown command complete for opcode 37 Nov 1 14:50:28 pnunn-Latitude-E6530 bluetoothd[1015]: Stopping discovery Nov 1 14:50:36 pnunn-Latitude-E6530 kernel: [60934.211132] input: Microsoft Bluetooth Notebook Mouse 5000 as /devices/pci:00/:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.0/bluetooth/hci0/hci0:11/input29 Nov 1 14:50:36 pnunn-Latitude-E6530 kernel: [60934.211646] hid-generic 0005:045E:0700.000C: input,hidraw3: BLUETOOTH HID v1.00 Mouse [Microsoft Bluetooth Notebook Mouse 5000] on 20:16:d8:9c:38:e5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1246981/+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 1386872] [NEW] Incorrect termination Firefox when shutdown Ubuntu
Public bug reported: 1. In Firefox go to Preference -> General tab, choose Show my windows and tabs from last time in When Firefox starts field. 2. Shutdown Ubuntu 3. Start Ubuntu 4. Open Firefox Actual result: Firefox opens with message "Firefox was not closed properly" ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20141016-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4 Uname: Linux 3.16.0-23-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Oct 28 22:20:52 2014 InstallationDate: Installed on 2014-10-25 (3 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: unity (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 unity in Ubuntu. https://bugs.launchpad.net/bugs/1386872 Title: Incorrect termination Firefox when shutdown Ubuntu Status in “unity” package in Ubuntu: New Bug description: 1. In Firefox go to Preference -> General tab, choose Show my windows and tabs from last time in When Firefox starts field. 2. Shutdown Ubuntu 3. Start Ubuntu 4. Open Firefox Actual result: Firefox opens with message "Firefox was not closed properly" ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20141016-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4 Uname: Linux 3.16.0-23-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Oct 28 22:20:52 2014 InstallationDate: Installed on 2014-10-25 (3 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1386872/+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 1240198] Re: Wrong keyboard layout active after booting into desktop
The attachment "use-system-keyboard-layout.patch" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1240198 Title: Wrong keyboard layout active after booting into desktop Status in “ibus” package in Ubuntu: Triaged Status in “indicator-keyboard” package in Ubuntu: Triaged Bug description: I upgraded from raring to saucy. After booting into the desktop (unity), the english keyboard layout is active, although everything on the system is set to be german (keyboard layout, language...) Switching to a virtual terminal (ctrl+alt+f1) fixes the problem and changes the layout to the german layout. all the time, the new input settings indicator says the german layout is active. locale says: LANG=de_DE.UTF-8 LANGUAGE=de_DE LC_CTYPE="de_DE.UTF-8" LC_NUMERIC="de_DE.UTF-8" LC_TIME="de_DE.UTF-8" LC_COLLATE="de_DE.UTF-8" LC_MONETARY="de_DE.UTF-8" LC_MESSAGES="de_DE.UTF-8" LC_PAPER="de_DE.UTF-8" LC_NAME="de_DE.UTF-8" LC_ADDRESS="de_DE.UTF-8" LC_TELEPHONE="de_DE.UTF-8" LC_MEASUREMENT="de_DE.UTF-8" LC_IDENTIFICATION="de_DE.UTF-8" LC_ALL= /etc/default/keyboard says: # Check /usr/share/doc/keyboard-configuration/README.Debian for # documentation on what to do after having modified this file. # The following variables describe your keyboard and can have the same # values as the XkbModel, XkbLayout, XkbVariant and XkbOptions options # in /etc/X11/xorg.conf. XKBMODEL="pc105" XKBLAYOUT="de" XKBVARIANT="" XKBOPTIONS="" # If you don't want to use the XKB layout on the console, you can # specify an alternative keymap. Make sure it will be accessible # before /usr is mounted. # KMAP=/etc/console-setup/defkeymap.kmap.gz ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: indicator-keyboard 0.0.0+13.10.20131010.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 Date: Tue Oct 15 20:49:03 2013 InstallationDate: Installed on 2013-04-26 (171 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True SourcePackage: indicator-keyboard UpgradeStatus: Upgraded to saucy on 2013-10-13 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1240198/+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 1297234] Re: Live session set wrong keyboard layout and time zone
This issue does exist in Trusty (probably in Utopic as well). It didn't exist a few versions ago (I don't remember which one introduced the bug). If I boot from the Live USB (created using "dd"), select another language (Portuguese, for example) then "Try Ubuntu", the live session has English keyboard layout, UTC time and almost all text in English (some things in Portuguese). The text being in English is OK, but the keyboard layout and timezone not being what I selected is not OK. And, as mentioned in comment #7, when the boot process reaches the "purple screen with some icons at the bottom" (like this: http://pix .toile-libre.org/upload/original/1347445119.png), if I press some key and then select Portuguese from there and "Try Ubuntu", the live session will have the correct keyboard layout (not sure about the timezone). So, there's a bug somewhere. ** Changed in: ubiquity (Ubuntu) Status: Incomplete => Confirmed -- 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/1297234 Title: Live session set wrong keyboard layout and time zone Status in “console-setup” package in Ubuntu: Expired Status in “ibus” package in Ubuntu: Expired Status in “ubiquity” package in Ubuntu: Confirmed Status in “console-setup” source package in Trusty: Invalid Status in “ibus” source package in Trusty: Invalid Status in “ubiquity” source package in Trusty: Invalid Bug description: When I boot the Ubuntu Studio 14.04 beta 2 testing it will start with keyboard set to English US and time zone as UTC. Usually I believe this would be localized to my Swedish keyboard and CET. ubuntu-studio@ubuntu-studio:~$ lsb_release -rd Description: Ubuntu Trusty Tahr (development branch) Release: 14.04 ubuntu-studio@ubuntu-studio:~$ apt-cache policy keyboard-configuration keyboard-configuration: Installed: 1.70ubuntu8 Candidate: 1.70ubuntu8 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: keyboard-configuration 1.70ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-19.40-lowlatency 3.13.6 Uname: Linux 3.13.0-19-lowlatency i686 ApportVersion: 2.13.3-0ubuntu1 Architecture: i386 CasperVersion: 1.339 CurrentDesktop: XFCE Date: Tue Mar 25 11:33:44 2014 LiveMediaBuild: Ubuntu-Studio 14.04 LTS "Trusty Tahr" - Beta i386 (20140325) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: console-setup UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1297234/+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