[Touch-packages] [Bug 1508260] Re: un-starring a scope jumps several scopes to the right
Adding unity8 to affected packages. This sounds like a UI bug ** Also affects: unity8 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scopes-shell in Ubuntu. https://bugs.launchpad.net/bugs/1508260 Title: un-starring a scope jumps several scopes to the right Status in unity-scopes-shell package in Ubuntu: New Status in unity8 package in Ubuntu: New Bug description: When I tap the star in a scope to un-favorite it, the view spontaneously shifts several scopes to the right. For example, if I flash a completely fresh image (such as arale rc-proposed 143), boot the first time, and tap the Today scope's star, the view shifts to the News scope instead of the Nearby scope. In older images, the view would shift only to the nearest neighbor, preferring right-most when one existed. Could we revert this back to the older behavior? Skipping multiple scopes seems like a bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scopes-shell/+bug/1508260/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1506907] Re: No way to install pip for Python 3.4 in 15.10 Wily
There seems to be some broader wierdness w/r/t what calls python3 and what calls python3.5. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3.4 in Ubuntu. https://bugs.launchpad.net/bugs/1506907 Title: No way to install pip for Python 3.4 in 15.10 Wily Status in Python: New Status in python3.4 package in Ubuntu: Confirmed Bug description: Related to this bug: https://bugs.launchpad.net/ubuntu/+source/python3.4/+bug/1290847 It looks like 15.10 uses a mixture of Python 3.4 and 3.5 (hopefully that's temporary?). Pip, the python package manager, is available from "python-pip" for Python 2.7, and "python3-pip" for Python 3.5, however, there is no python3.4-pip, and because of the weird state of Python in debian/ubuntu, there's no way to use "ensurepip" to get it either. One fix would be to just ship a complete version of python/python3.4/python3.5, including pip, as part of the base package, if there's any appetite for revisiting the historical decision to unbundle python... To manage notifications about this bug go to: https://bugs.launchpad.net/python/+bug/1506907/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1514701] [NEW] QmlTests::BrowserTab::test_load_unload() fails on xenial armhf
Public bug reported: I’ve seen the following unit test fail twice in silo builds (xenial armhf): FAIL! : QmlTests::BrowserTab::test_load_unload() property webviewPresent Actual (): false Expected (): true Loc: [/«BUILDDIR»/webbrowser-app-0.23+16.04.20151109.1/tests/unittests/qml/tst_BrowserTab.qml(81)] See e.g. a full build log here: https://launchpadlibrarian.net/225643181 /buildlog_ubuntu-xenial-armhf.webbrowser- app_0.23%2B16.04.20151109.1-0ubuntu1_BUILDING.txt.gz. The same test passes on other architectures (amd64, i386), and also on vivid armhf. ** Affects: webbrowser-app (Ubuntu) Importance: High Assignee: Olivier Tilloy (osomon) Status: Triaged ** Changed in: webbrowser-app (Ubuntu) Assignee: (unassigned) => Olivier Tilloy (osomon) ** Changed in: webbrowser-app (Ubuntu) Status: New => Triaged ** Changed in: webbrowser-app (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1514701 Title: QmlTests::BrowserTab::test_load_unload() fails on xenial armhf Status in webbrowser-app package in Ubuntu: Triaged Bug description: I’ve seen the following unit test fail twice in silo builds (xenial armhf): FAIL! : QmlTests::BrowserTab::test_load_unload() property webviewPresent Actual (): false Expected (): true Loc: [/«BUILDDIR»/webbrowser-app-0.23+16.04.20151109.1/tests/unittests/qml/tst_BrowserTab.qml(81)] See e.g. a full build log here: https://launchpadlibrarian.net/225643181/buildlog_ubuntu-xenial-armhf .webbrowser-app_0.23%2B16.04.20151109.1-0ubuntu1_BUILDING.txt.gz. The same test passes on other architectures (amd64, i386), and also on vivid armhf. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1514701/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1477130] Re: timedatectl fails inside container
Presumably you don't have dbus installed in your container. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1477130 Title: timedatectl fails inside container Status in systemd package in Ubuntu: Fix Released Bug description: lxc-attach -n mycont -- timedatectl Failed to create bus connection: No such file or directory while on the host timedatectl works just fine. lxc Version: 1.1.2-0ubuntu3 on ubuntu 15.04 x86_64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1477130/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1514141] Re: unprivileged user can freeze journald
Thanks for your report! Let's discuss/fix that on the upstream side to get the relevant developers. ** Changed in: systemd (Ubuntu) Importance: Undecided => Medium ** Changed in: systemd (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1514141 Title: unprivileged user can freeze journald Status in systemd package in Ubuntu: Triaged Bug description: On default installs of Ubuntu 15.10, both server and desktop, an unprivileged user can freeze journald using the attached program. (Journald is then eventually killed and restarted by systemd after a 1 min timeout is detected - but nothing prevent the unprivileged user to DOS in a loop if he feels so inclined.) The reason is that journald uses inappropriate rules to decide if a file descriptor sent by a user is safe to read. [ IMO that such a "feature" (passing messages to log to journald by fd to regular files) exists at all should be questioned anyway, given the kind of impacts it can have on various aspects of the whole system (e.g.: the fd is completely read in a malloc'ed area, up to 750 MB) ] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1514141/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1514690] Re: rebooting container with systemd >= 226 fails to create /lxc/adt-xenial/init.scope control group
FTR, same behaviour with Serge's lxcfs "testing" branch with cgfs. -- 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/1514690 Title: rebooting container with systemd >= 226 fails to create /lxc/adt- xenial/init.scope control group Status in lxc package in Ubuntu: New Bug description: Even after fixing bug 1497420 rebooting containers with systemd >= 226 (i. e. with supporting unified cgroups) does not work. Build a standard xenial container (using the ubuntu template; e. g. "adt- build-lxc ubuntu xenial"), start it: sudo lxc-start -n adt-xenial -F then log in and run "sudo reboot". It shuts down, but reboot fails with Rebooting. systemd 227 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID -ELFUTILS +KMOD -IDN) Detected virtualization lxc. Detected architecture x86-64. Welcome to Ubuntu 16.04! Set hostname to . Failed to install release agent, ignoring: No such file or directory Failed to create /lxc/adt-xenial/init.scope control group: No such file or directory Failed to allocate manager object: No such file or directory [!!] Failed to allocate manager object, freezing. Freezing execution. During that time, I get the following errors: Nov 09 08:42:31 donald cgmanager[864]: cgmanager: Invalid path /run/cgmanager/fs/none,name=systemd///lxc/adt-xenial/init.scope (No such file or directory) Nov 09 08:42:31 donald cgmanager[864]: cgmanager:list_children_main: Could not determine the requested cgroup (name=systemd:lxc/adt-xenial/init.scope) Nov 09 08:42:31 donald cgmanager[864]: cgmanager: Invalid path /run/cgmanager/fs/none,name=systemd///lxc/adt-xenial/init.scope (No such file or directory) Nov 09 08:42:31 donald cgmanager[864]: cgmanager:list_keys_main: Could not determine the requested cgroup (name=systemd:lxc/adt-xenial/init.scope) Nov 09 08:42:31 donald lxcfs[882]: ** (process:882): WARNING **: cgmanager method call org.linuxcontainers.cgmanager0_0.ListChildren failed: GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: invalid request. Use G_DBUS_DEBUG=message for more info. Nov 09 08:42:31 donald lxcfs[882]: ** (process:882): WARNING **: cgmanager method call org.linuxcontainers.cgmanager0_0.ListKeys failed: GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: invalid request. Use G_DBUS_DEBUG=message for more info.h ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: lxc 1.1.5-0ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.2-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Tue Nov 10 06:30:28 2015 EcryptfsInUse: Yes 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 lxc.conf: lxc.lxcpath = /srv/lxc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1514690/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1497420] Re: systemd 226 (moving pid 1 into /init.scope cgroup) breaks lxc-attach
That did not fix reboot yet. I filed bug 1514690 as it's a different root cause apparenlty. @Serge: there's nothing that should "stick around", it's a reboot after all and everything including pid 1 gets restarted. It just seems that the second boot can't create the init.scope cgroup as the "outside" host still has some state from the first boot? -- 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/1497420 Title: systemd 226 (moving pid 1 into /init.scope cgroup) breaks lxc-attach Status in cgmanager package in Ubuntu: Fix Released Status in lxc package in Ubuntu: Fix Released Status in lxcfs package in Ubuntu: Fix Released Status in docker package in Debian: Fix Released Bug description: Once systemd 226 is installed in an unprivileged Debian Sid container, lxc-attach no-longer functions: % lxc-attach -n siddy lxc-attach: cgmanager.c: lxc_cgmanager_enter: 698 call to cgmanager_move_pid_abs_sync failed: invalid request lxc-attach: cgmanager.c: cgm_attach: 1460 Failed to enter group /user.slice/user-1000.slice/session-1.scope/lxc/siddy/init.scope lxc-attach: attach.c: lxc_attach: 909 error communicating with child process % journalctl -u cgmanager | tail -n 1 Sep 18 20:20:44 astoria cgmanager[1169]: cgmanager:per_ctrl_move_pid_main: pid 21918 (uid 1000 gid 1000) may not write to /run/cgmanager/fs/none,name=systemd//user.slice/user-1000.slice/session-1.scope/lxc/siddy/init.scope/tasks Full walkthrough: % lxc-create -n siddy -t download -- -d debian -r sid -a amd64 Using image from local cache Unpacking the rootfs ... % lxc-start -n siddy % lxc-attach -n siddy root@siddy:/# apt-get update Get:1 http://http.debian.net sid InRelease [253 kB] ... Get:7 http://http.debian.net sid/non-free amd64 Packages [91.3 kB] Fetched 13.2 MB in 3s (3789 kB/s) Reading package lists... Done root@siddy:/# apt-get install systemd Reading package lists... Done Building dependency tree Reading state information... Done The following extra packages will be installed: libsystemd0 Suggested packages: systemd-ui systemd-container Recommended packages: libpam-systemd dbus The following packages will be upgraded: libsystemd0 systemd 2 upgraded, 0 newly installed, 0 to remove and 47 not upgraded. Need to get 3668 kB of archives. After this operation, 1100 kB disk space will be freed. Do you want to continue? [Y/n] Get:1 http://http.debian.net/debian/ sid/main libsystemd0 amd64 226-2 [242 kB] Get:2 http://http.debian.net/debian/ sid/main systemd amd64 226-2 [3426 kB] ... Setting up systemd (226-2) ... Installing new version of config file /etc/X11/xinit/xinitrc.d/50-systemd-user.sh ... Installing new version of config file /etc/dbus-1/system.d/org.freedesktop.login1.conf ... addgroup: The group `systemd-journal' already exists as a system group. Exiting. Failed to set capabilities on file `/usr/bin/systemd-detect-virt' (Invalid argument) The value of the capability argument is not permitted for a file. Or the file is not a regular (non-symlink) file Failed to execute operation: File exists Removing obsolete conffile /etc/dbus-1/system.d/org.freedesktop.machine1.conf ... root@siddy:/# exit % lxc-attach -n siddy lxc-attach: cgmanager.c: lxc_cgmanager_enter: 698 call to cgmanager_move_pid_abs_sync failed: invalid request lxc-attach: cgmanager.c: cgm_attach: 1460 Failed to enter group /user.slice/user-1000.slice/session-1.scope/lxc/siddy/init.scope lxc-attach: attach.c: lxc_attach: 909 error communicating with child process ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: lxc 1.1.3-0ubuntu1 [modified: usr/lib/x86_64-linux-gnu/lxc/lxc-net] ProcVersionSignature: Ubuntu 4.2.0-10.11-generic 4.2.0 Uname: Linux 4.2.0-10-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.18.1-0ubuntu1 Architecture: amd64 Date: Fri Sep 18 20:19:58 2015 SourcePackage: lxc UpgradeStatus: Upgraded to wily on 2015-08-28 (20 days ago) defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up lxc.network.hwaddr = 00:16:3e:xx:xx:xx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cgmanager/+bug/1497420/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1505705] Re: [sound] Subwoofer slider works in mysterious ways
** Changed in: hwe-next Importance: Undecided => Low ** Changed in: hwe-next Status: New => Triaged ** Changed in: hwe-next Assignee: (unassigned) => David Henningsson (diwic) -- 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/1505705 Title: [sound] Subwoofer slider works in mysterious ways Status in HWE Next: Triaged Status in pulseaudio package in Ubuntu: Fix Committed Status in unity-control-center package in Ubuntu: Triaged Bug description: Sometimes it follows master volume and sometimes it doesn't. Same as: https://bugzilla.gnome.org/show_bug.cgi?id=753847 Also raised by OEM team. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1505705/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1514519] Re: Font in Terminal is incorrectly massive since recent update
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: unity8 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1514519 Title: Font in Terminal is incorrectly massive since recent update Status in Canonical System Image: Confirmed Status in logviewer: New Status in Ubuntu Terminal App: New Status in unity8 package in Ubuntu: Confirmed Bug description: Last know good image: 166 Changes on 167: http://people.canonical.com/~lzemczak/landing-team/ubuntu-touch/rc-proposed/167.commitlog Landing request for Unity8/Mir: https://requests.ci-train.ubuntu.com/#/ticket/564 After updating my Nexus 4 and Krillin over the weekend I notice the terminal now has really huge text. Even dialling down the font size in the app to 8pt results in huge unusable text. Before:- http://people.canonical.com/~alan/screenshots/device-2015-11-09-165137.png After:- http://people.canonical.com/~alan/screenshots/device-2015-11-09-165130.png With the same font size setting on both. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1514519/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1514690] Re: rebooting container with systemd >= 226 fails to create /lxc/adt-xenial/init.scope control group
I'm setting this to high as this breaks autopkgtesting on armhf quite badly. ** Changed in: lxc (Ubuntu) Importance: Undecided => High -- 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/1514690 Title: rebooting container with systemd >= 226 fails to create /lxc/adt- xenial/init.scope control group Status in lxc package in Ubuntu: New Bug description: Even after fixing bug 1497420 rebooting containers with systemd >= 226 (i. e. with supporting unified cgroups) does not work. Build a standard xenial container (using the ubuntu template; e. g. "adt- build-lxc ubuntu xenial"), start it: sudo lxc-start -n adt-xenial -F then log in and run "sudo reboot". It shuts down, but reboot fails with Rebooting. systemd 227 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID -ELFUTILS +KMOD -IDN) Detected virtualization lxc. Detected architecture x86-64. Welcome to Ubuntu 16.04! Set hostname to . Failed to install release agent, ignoring: No such file or directory Failed to create /lxc/adt-xenial/init.scope control group: No such file or directory Failed to allocate manager object: No such file or directory [!!] Failed to allocate manager object, freezing. Freezing execution. During that time, I get the following errors: Nov 09 08:42:31 donald cgmanager[864]: cgmanager: Invalid path /run/cgmanager/fs/none,name=systemd///lxc/adt-xenial/init.scope (No such file or directory) Nov 09 08:42:31 donald cgmanager[864]: cgmanager:list_children_main: Could not determine the requested cgroup (name=systemd:lxc/adt-xenial/init.scope) Nov 09 08:42:31 donald cgmanager[864]: cgmanager: Invalid path /run/cgmanager/fs/none,name=systemd///lxc/adt-xenial/init.scope (No such file or directory) Nov 09 08:42:31 donald cgmanager[864]: cgmanager:list_keys_main: Could not determine the requested cgroup (name=systemd:lxc/adt-xenial/init.scope) Nov 09 08:42:31 donald lxcfs[882]: ** (process:882): WARNING **: cgmanager method call org.linuxcontainers.cgmanager0_0.ListChildren failed: GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: invalid request. Use G_DBUS_DEBUG=message for more info. Nov 09 08:42:31 donald lxcfs[882]: ** (process:882): WARNING **: cgmanager method call org.linuxcontainers.cgmanager0_0.ListKeys failed: GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: invalid request. Use G_DBUS_DEBUG=message for more info.h ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: lxc 1.1.5-0ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.2-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Tue Nov 10 06:30:28 2015 EcryptfsInUse: Yes 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 lxc.conf: lxc.lxcpath = /srv/lxc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1514690/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1514519] Re: Font in Terminal is incorrectly massive since recent update
** Also affects: logviewer Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1514519 Title: Font in Terminal is incorrectly massive since recent update Status in Canonical System Image: Confirmed Status in logviewer: New Status in Ubuntu Terminal App: New Status in unity8 package in Ubuntu: Confirmed Bug description: Last know good image: 166 Changes on 167: http://people.canonical.com/~lzemczak/landing-team/ubuntu-touch/rc-proposed/167.commitlog Landing request for Unity8/Mir: https://requests.ci-train.ubuntu.com/#/ticket/564 After updating my Nexus 4 and Krillin over the weekend I notice the terminal now has really huge text. Even dialling down the font size in the app to 8pt results in huge unusable text. Before:- http://people.canonical.com/~alan/screenshots/device-2015-11-09-165137.png After:- http://people.canonical.com/~alan/screenshots/device-2015-11-09-165130.png With the same font size setting on both. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1514519/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1514690] [NEW] rebooting container with systemd >= 226 fails to create /lxc/adt-xenial/init.scope control group
Public bug reported: Even after fixing bug 1497420 rebooting containers with systemd >= 226 (i. e. with supporting unified cgroups) does not work. Build a standard xenial container (using the ubuntu template; e. g. "adt-build-lxc ubuntu xenial"), start it: sudo lxc-start -n adt-xenial -F then log in and run "sudo reboot". It shuts down, but reboot fails with Rebooting. systemd 227 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID -ELFUTILS +KMOD -IDN) Detected virtualization lxc. Detected architecture x86-64. Welcome to Ubuntu 16.04! Set hostname to . Failed to install release agent, ignoring: No such file or directory Failed to create /lxc/adt-xenial/init.scope control group: No such file or directory Failed to allocate manager object: No such file or directory [!!] Failed to allocate manager object, freezing. Freezing execution. During that time, I get the following errors: Nov 09 08:42:31 donald cgmanager[864]: cgmanager: Invalid path /run/cgmanager/fs/none,name=systemd///lxc/adt-xenial/init.scope (No such file or directory) Nov 09 08:42:31 donald cgmanager[864]: cgmanager:list_children_main: Could not determine the requested cgroup (name=systemd:lxc/adt-xenial/init.scope) Nov 09 08:42:31 donald cgmanager[864]: cgmanager: Invalid path /run/cgmanager/fs/none,name=systemd///lxc/adt-xenial/init.scope (No such file or directory) Nov 09 08:42:31 donald cgmanager[864]: cgmanager:list_keys_main: Could not determine the requested cgroup (name=systemd:lxc/adt-xenial/init.scope) Nov 09 08:42:31 donald lxcfs[882]: ** (process:882): WARNING **: cgmanager method call org.linuxcontainers.cgmanager0_0.ListChildren failed: GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: invalid request. Use G_DBUS_DEBUG=message for more info. Nov 09 08:42:31 donald lxcfs[882]: ** (process:882): WARNING **: cgmanager method call org.linuxcontainers.cgmanager0_0.ListKeys failed: GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: invalid request. Use G_DBUS_DEBUG=message for more info.h ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: lxc 1.1.5-0ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.2-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Tue Nov 10 06:30:28 2015 EcryptfsInUse: Yes 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 lxc.conf: lxc.lxcpath = /srv/lxc ** Affects: lxc (Ubuntu) Importance: High Status: New ** Tags: amd64 apparmor apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1514690 Title: rebooting container with systemd >= 226 fails to create /lxc/adt- xenial/init.scope control group Status in lxc package in Ubuntu: New Bug description: Even after fixing bug 1497420 rebooting containers with systemd >= 226 (i. e. with supporting unified cgroups) does not work. Build a standard xenial container (using the ubuntu template; e. g. "adt- build-lxc ubuntu xenial"), start it: sudo lxc-start -n adt-xenial -F then log in and run "sudo reboot". It shuts down, but reboot fails with Rebooting. systemd 227 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID -ELFUTILS +KMOD -IDN) Detected virtualization lxc. Detected architecture x86-64. Welcome to Ubuntu 16.04! Set hostname to . Failed to install release agent, ignoring: No such file or directory Failed to create /lxc/adt-xenial/init.scope control group: No such file or directory Failed to allocate manager object: No such file or directory [!!] Failed to allocate manager object, freezing. Freezing execution. During that time, I get the following errors: Nov 09 08:42:31 donald cgmanager[864]: cgmanager: Invalid path /run/cgmanager/fs/none,name=systemd///lxc/adt-xenial/init.scope (No such file or directory) Nov 09 08:42:31 donald cgmanager[864]: cgmanager:list_children_main: Could not determine the requested cgroup (name=systemd:lxc/adt-xenial/init.scope) Nov 09 08:42:31 donald cgmanager[864]: cgmanager: Invalid path /run/cgmanager/fs/none,name=systemd///lxc/adt-xenial/init.scope (No such file or directory) Nov 09 08:42:31 donald cgmanager[864]: cgmanager:list_keys_main: Could not determine the requested cgroup (name=systemd:lxc/adt-xenial/init.scope) Nov 09 08:42:31 donald lxcfs[882]: ** (process:882): WARNING **: cgmanager method call org.linuxcontainers.cgmanager0_0.ListChildren failed: GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: invalid request. Use G_DBUS_DEBUG=message for more
[Touch-packages] [Bug 1128207] Re: [AO756, Realtek ALC271X, Mic, Internal] External Microphone doesn't work
[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/1128207 Title: [AO756, Realtek ALC271X, Mic, Internal] External Microphone doesn't work Status in alsa-driver package in Ubuntu: Expired Bug description: When I connect my headphones with built-in microphone using single mini-jack port sound is ok, but microphone doesn't work. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: alsa-base 1.0.25+dfsg-0ubuntu3 ProcVersionSignature: Ubuntu 3.5.0-23.35-generic 3.5.7.2 Uname: Linux 3.5.0-23-generic x86_64 ApportVersion: 2.6.1-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: necrordian 2249 F pulseaudio Date: Sun Feb 17 17:23:24 2013 EcryptfsInUse: Yes InstallationDate: Installed on 2013-02-09 (8 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MarkForUpload: True PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Wbudowany dźwięk - HDA Intel PCH Symptom_Jack: Mic, Internal Symptom_Type: Only some of inputs are working Title: [AO756, Realtek ALC271X, Mic, Internal] Recording problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/19/2012 dmi.bios.vendor: Acer dmi.bios.version: V1.05 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Mimic dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.05 dmi.modalias: dmi:bvnAcer:bvrV1.05:bd07/19/2012:svnAcer:pnAO756:pvrV1.05:rvnAcer:rnMimic:rvrType2-BoardVersion:cvnAcer:ct10:cvrV1.05: dmi.product.name: AO756 dmi.product.version: V1.05 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1128207/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1387187] Re: [HP Pavilion dv7 Notebook PC, IDT 92HD81B1X5, Black Headphone Out, Front] No sound at all
[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/1387187 Title: [HP Pavilion dv7 Notebook PC, IDT 92HD81B1X5, Black Headphone Out, Front] No sound at all Status in alsa-driver package in Ubuntu: Expired Bug description: I suspended my dv7, when I tried to resume it crashed, I rebooted it. Since then, audio is not working, everything seems fine visually, I have tried many tutorials to no avail, everything seems to be in working order, but no sound comes out of speakers or headphone. I have also tried an external usb audio driver, no sound comes out of it either. It seems to be recognized, there is no indication that it should not be working. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: marcelosalgado 2139 F pulseaudio CurrentDesktop: Unity Date: Wed Oct 29 10:38:09 2014 InstallationDate: Installed on 2014-09-10 (49 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: marcelosalgado 2139 F pulseaudio Symptom_Jack: Black Headphone Out, Front Symptom_Type: No sound at all Title: [HP Pavilion dv7 Notebook PC, IDT 92HD81B1X5, Black Headphone Out, Front] No sound at all UpgradeStatus: Upgraded to trusty on 2014-10-28 (0 days ago) dmi.bios.date: 07/20/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.1A dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 165A dmi.board.vendor: Hewlett-Packard dmi.board.version: 10.31 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnHewlett-Packard:bvrF.1A:bd07/20/2011:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvr058D11244620001620100:rvnHewlett-Packard:rn165A:rvr10.31:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion dv7 Notebook PC dmi.product.version: 058D11244620001620100 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1387187/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1494170] Re: [System Product Name, VIA VT1828S, Green Line Out, Rear] No sound at all
[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/1494170 Title: [System Product Name, VIA VT1828S, Green Line Out, Rear] No sound at all Status in pulseaudio package in Ubuntu: Expired Bug description: I upgraded to 15.04, and my sound stopped working; both output and input. There are no devices shown in the panels when I go to Sound settings, either. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: pulseaudio 1:6.0-0ubuntu6 ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5 Uname: Linux 3.19.0-28-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: aqui1a11457 F pulseaudio /dev/snd/controlC0: aqui1a11457 F pulseaudio CurrentDesktop: GNOME Date: Thu Sep 10 09:01:08 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2014-03-17 (541 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID successful Symptom_Card: Built-in Audio - HDA Intel MID Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: aqui1a11457 F pulseaudio /dev/snd/controlC0: aqui1a11457 F pulseaudio Symptom_Jack: Green Line Out, Rear Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: No sound at all Title: [System Product Name, VIA VT1828S, Green Line Out, Rear] No sound at all UpgradeStatus: Upgraded to vivid on 2015-09-10 (0 days ago) dmi.bios.date: 05/21/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1002 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P7P55D-E 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.:bvr1002:bd05/21/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP7P55D-E:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1494170/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1484829] Re: the words"Add Photo to Album" was hided after rotate the device to landscape mode
I found a new issue in this part :"Add photo to album" dialog doesn't change bigger when turn your phone to portrait mode Step: 1.Open gallery app in landscape mode 2.Long press a picture then press "+", the "Add photo to album" pops up 3.Turn your phone to portrait mode Notes:When you add picture in portrait mode directly after entering into gallery app , the normal size of the dialog is bigger than it in the landscape mode current build number: 168 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2015-11-10 02:13:53 version version: 168 version ubuntu: 20151109 version device: 20150821-736d127 version custom: 20150925-901-35-40-vivid ** Attachment added: "screenshot20151110_040700647.png" https://bugs.launchpad.net/ubuntu/+source/gallery-app/+bug/1484829/+attachment/4515882/+files/screenshot20151110_040700647.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gallery-app in Ubuntu. https://bugs.launchpad.net/bugs/1484829 Title: the words"Add Photo to Album" was hided after rotate the device to landscape mode Status in gallery-app package in Ubuntu: Confirmed Bug description: system-image-cli -i current build number: 96 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2015-08-13 11:47:07 version version: 96 version ubuntu: 20150813 version device: 20150804-7bba081 version custom: 20150717-820-30-25-vivid reproduce steps: 1.launch gallery app 2.tap drop down menu and select photos 3.tap the select icon at the top right corner 4.select a few photos and tap the "+" icon 5.rotate the device to landscape mode the"Add Photo to Album" disappear after rotate the device" expect result: the word "Add Photo to Album" should be still appear after rotate the device to landscape mode actual result: the"Add Photo to Album" disappear after rotate the device" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gallery-app/+bug/1484829/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1484829] Re: the words"Add Photo to Album" was hided after rotate the device to landscape mode
** Attachment added: "screenshot20151110_040710240.png" https://bugs.launchpad.net/ubuntu/+source/gallery-app/+bug/1484829/+attachment/4515883/+files/screenshot20151110_040710240.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gallery-app in Ubuntu. https://bugs.launchpad.net/bugs/1484829 Title: the words"Add Photo to Album" was hided after rotate the device to landscape mode Status in gallery-app package in Ubuntu: Confirmed Bug description: system-image-cli -i current build number: 96 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2015-08-13 11:47:07 version version: 96 version ubuntu: 20150813 version device: 20150804-7bba081 version custom: 20150717-820-30-25-vivid reproduce steps: 1.launch gallery app 2.tap drop down menu and select photos 3.tap the select icon at the top right corner 4.select a few photos and tap the "+" icon 5.rotate the device to landscape mode the"Add Photo to Album" disappear after rotate the device" expect result: the word "Add Photo to Album" should be still appear after rotate the device to landscape mode actual result: the"Add Photo to Album" disappear after rotate the device" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gallery-app/+bug/1484829/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1513909] Re: unity8 crash on unplug of monitor
OK, on an updated PD image with silo 18 I am seeing this very consistently now. Mainly on plugging in the monitor now. Greater than 50% of the time. Attaching crash file i'm seeing consistently. ** Attachment added: "_usr_bin_unity8.32011.crash" https://bugs.launchpad.net/canonical-pocket-desktop/+bug/1513909/+attachment/4515871/+files/_usr_bin_unity8.32011.crash ** Changed in: canonical-pocket-desktop Importance: High => Critical ** Changed in: mir (Ubuntu) Importance: High => Critical ** Changed in: qtmir (Ubuntu) Importance: High => Critical ** Changed in: unity8 (Ubuntu) Importance: High => Critical -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1513909 Title: unity8 crash on unplug of monitor Status in canonical-pocket-desktop: New Status in mir package in Ubuntu: New Status in qtmir package in Ubuntu: New Status in unity8 package in Ubuntu: New Bug description: Stability of hotplug is much better - so this is not a duplicate of bug 1488863 Maybe every 1/4 unplug event will see unity8 crashstrangely, didn't capture a crash log until now. This configuration is latest PD image + silo 18 (with point release fixes for Mir0.17) also libertine/puritine installed xmir is from libertine devel ppa To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-pocket-desktop/+bug/1513909/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1474035] Re: Missing docs in ubuntu website
Sorry, the media.getArtUri() method doesn't apply to QML. It is provided by the mediascanner API. But that raises another question: we also have a Qt API. The doc for that is provided by the thumbnailer-qt-doc package. Would it be worth mentioning this somewhere? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to thumbnailer in Ubuntu. https://bugs.launchpad.net/bugs/1474035 Title: Missing docs in ubuntu website Status in Ubuntu Developer Portal: New Status in thumbnailer package in Ubuntu: Triaged Bug description: There are no docs for the thumbnailer's QML plugin in https://developer.ubuntu.com/api/qml/current/ To manage notifications about this bug go to: https://bugs.launchpad.net/developer-ubuntu-com/+bug/1474035/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1002952] Re: [meta-bug] Invalid extra "Digital output S/PDIF" device for USB cards
Same issue was encountered with this headset: "Jabra UC VOICE 550a MS" http://www.alsa- project.org/db/?f=864bc9d63da66650232a42d9747a239cd2a205d7 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1002952 Title: [meta-bug] Invalid extra "Digital output S/PDIF" device for USB cards Status in alsa-lib package in Ubuntu: Confirmed Bug description: === Read me first === = Symptom = If you have a USB headset, or other USB device that does not have any S/PDIF output, but yet sometimes there is an extra device called "Digital Output (S/PDIF)" for that device, you're suffering from this bug. This bug is only for USB devices - if you have an invalid digital output for some other type of device, please file a separate bug instead. = Workaround = If you're affected, please try this workaround: first check the output of "aplay -l" (lowercase L), or "arecord -l" if it's an input device, and grab the first of two name in brackets: Example: card 3: Headset [Sennheiser USB Headset], device 0: USB Audio [USB Audio] here grab the name "Sennheiser USB Headset". Now edit the file /usr/share/alsa/cards/USB-Audio.conf (requires root permissions) Around line 40, you will find a line saying "Logitech USB Headset" 999 Add a new line after this line, so that there is now a new line called "Sennheiser USB Headset" 999 (including quotes, and replace "Sennheiser USB Headset" with whatever your particular card was named.) Save the file and reboot your computer for the changes to take effect. = Already known devices = These card names are already in 12.04: "Blue Snowball" "Logitech USB Headset" "Logitech Web Camera" These card names are on their way into 12.04: "Logitech Speaker Lapdesk N700" "Logitech Wireless Headset" "Plantronics USB Headset" "Sennheiser USB headset" If you have one of the above four, please help out by testing the proposed repository and report back in bug 987163. If your name is not listed above, please add a comment to this bug, including your alsa-info: https://wiki.ubuntu.com/Audio/AlsaInfo - they will be collected for a SRU later on, or at least make it into the next release of Ubuntu. Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1002952/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1509622] Re: Xorg crash
I've encountered this issue twice today. I had done a clean 15.10 install perhaps ~2 weeks ago and this is the first day such an event occurred. I too use Chrome, HOWEVER, I found it happened first when I was using Kodi 16. I do see an update from my ASRock H97M-ITX/ac 1.70 in May to an August 1.80 which I'll try, but considering I had not had the issue in 15.04, I have my doubts. There is no consistency I can see in each occurrence. -- 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/1509622 Title: Xorg crash Status in xorg package in Ubuntu: Incomplete Bug description: This is the full apport data from the crash reported as bug #1507461. It occurred whilst watching a full-screen Flash video in Google Chrome. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.19.1-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sat Oct 24 18:04:11 2015 DistUpgraded: Fresh install DistroCodename: wily DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:21fa] MachineType: LENOVO CTO ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-16-generic root=/dev/mapper/peleg0-lv01 ro splash quiet nomdmonddf nomdmonisw vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/24/2012 dmi.bios.vendor: LENOVO dmi.bios.version: G2ET33WW (1.13 ) dmi.board.asset.tag: Not Available dmi.board.name: CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG2ET33WW(1.13):bd07/24/2012:svnLENOVO:pnCTO:pvrThinkPadX230:rvnLENOVO:rnCTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: CTO dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.2+15.10.20151015-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4 version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0+git20150819-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3 xserver.bootTime: Sat Oct 24 17:58:31 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 728 vendor LGD xserver.version: 2:1.17.2-1ubuntu9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1509622/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1511553] Re: Crash in queueRequest
** Changed in: thumbnailer (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to thumbnailer in Ubuntu. https://bugs.launchpad.net/bugs/1511553 Title: Crash in queueRequest Status in thumbnailer package in Ubuntu: Fix Committed Bug description: https://errors.ubuntu.com/problem/fa22f0b18ff6dc949c4cdf768f32121d64a83b8d We hit this occasionally, but not very often. I suspect it is because of the way we shut down: we destroy the thumbnailer instance before the dbus interface so we don't hit the race condition where one instance of the service still has the database lock while a second instance of the service is activated by a new incoming request. But, destroying the thumbnailer first means that, if a request arrives at just the right time, the dbu sinterface fires the request at the already-destroyed thumbnailer. I recently hit a whole slew of issues in a test that destroyed the thumbnailer and dbus interface (in that order) while there were still requests sitting in the scheduler and thread pools, and fixed a bunch of these issues (see the request-cancellation branch.) In effect, via the handler class that calls back into the thumbnailer and the closures that sit in the thread pools, we have created a circular dependency between the dbus interface and thumbnailer, which makes it impossible to shut down either without causing problems. I think the best solution would be to add a shutdown() method to the dbus interface that prevents new requests from firing. We also need some way to wait for all *received* (not just scheduled) requests to finish executing before physically shutting down. Does DBus have a way to say "I'm in the process of shutting down. Send the request that just arrived and that I can't process anymore to a new instance of the service"? Ideally, I would like to "close the gate" on incoming requests such that they are transparently re-sent, and then wait for all currently executing requests to finish processing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thumbnailer/+bug/1511553/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1514141] Re: unprivileged user can freeze journald
OpenSUSE 42.1 bug: https://bugzilla.opensuse.org/show_bug.cgi?id=954374 upstream bug: https://github.com/systemd/systemd/issues/1822 ** Bug watch added: bugzilla.opensuse.org/ #954374 http://bugzilla.opensuse.org/show_bug.cgi?id=954374 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1514141 Title: unprivileged user can freeze journald Status in systemd package in Ubuntu: New Bug description: On default installs of Ubuntu 15.10, both server and desktop, an unprivileged user can freeze journald using the attached program. (Journald is then eventually killed and restarted by systemd after a 1 min timeout is detected - but nothing prevent the unprivileged user to DOS in a loop if he feels so inclined.) The reason is that journald uses inappropriate rules to decide if a file descriptor sent by a user is safe to read. [ IMO that such a "feature" (passing messages to log to journald by fd to regular files) exists at all should be questioned anyway, given the kind of impacts it can have on various aspects of the whole system (e.g.: the fd is completely read in a malloc'ed area, up to 750 MB) ] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1514141/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1125726] Re: boot-time race between /etc/network/if-up.d/ntpdate and "/etc/init.d/ntp start"
In case it wasn't clear, my patch is supposed to be for the debian/ntpdate.if-up file. Also, I think the priority of this bug should be higher, it was assigned 'low' when there was no clear problem caused by the race. Systems booting with uncorrectable clock skew can be a serious problem. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1125726 Title: boot-time race between /etc/network/if-up.d/ntpdate and "/etc/init.d/ntp start" Status in ntp package in Ubuntu: Confirmed Bug description: We're seeing a race between if-up.d/ntpdate and the ntp startup script. 1) if-up.d/ntpdate starts. 2) if-up.d/ntpdate acquires the lock "/var/lock/ntpdate-ifup". 3) if-up.d/ntpdate stops the ntp service [which isn't running anyway]. 4) if-up.d/ntpdate starts running ntpdate, which bids UDP *.ntp 5) /etc/init.d/rc 2 executes "/etc/rc2.d/S20ntp start" 6) /etc/init.d/ntp acquires the lock "/var/lock/ntpdate". 7) /etc/init.d/ntp starts the ntp daemon. 8) The ntp daemon logs an error, complaining that it cannot bind UDP *.ntp. 9) if-up.d/ntpdate now starts the ntp service. The result is a weird churn, though ntpd does end up running at the end. Should these not be using the same lock file? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1125726/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1125726] Re: boot-time race between /etc/network/if-up.d/ntpdate and "/etc/init.d/ntp start"
** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1125726 Title: boot-time race between /etc/network/if-up.d/ntpdate and "/etc/init.d/ntp start" Status in ntp package in Ubuntu: Confirmed Bug description: We're seeing a race between if-up.d/ntpdate and the ntp startup script. 1) if-up.d/ntpdate starts. 2) if-up.d/ntpdate acquires the lock "/var/lock/ntpdate-ifup". 3) if-up.d/ntpdate stops the ntp service [which isn't running anyway]. 4) if-up.d/ntpdate starts running ntpdate, which bids UDP *.ntp 5) /etc/init.d/rc 2 executes "/etc/rc2.d/S20ntp start" 6) /etc/init.d/ntp acquires the lock "/var/lock/ntpdate". 7) /etc/init.d/ntp starts the ntp daemon. 8) The ntp daemon logs an error, complaining that it cannot bind UDP *.ntp. 9) if-up.d/ntpdate now starts the ntp service. The result is a weird churn, though ntpd does end up running at the end. Should these not be using the same lock file? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1125726/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1514643] [NEW] package libc6 2.19-0ubuntu6.6 [modified: usr/share/doc/libc6/NEWS.gz usr/share/doc/libc6/changelog.Debian.gz usr/share/doc/libc6/copyright usr/share/lintian/overri
Public bug reported: I have been going through this everyday for a week now ProblemType: Package DistroRelease: Ubuntu 15.04 Package: libc6 2.19-0ubuntu6.6 [modified: usr/share/doc/libc6/NEWS.gz usr/share/doc/libc6/changelog.Debian.gz usr/share/doc/libc6/copyright usr/share/lintian/overrides/libc6] ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7 Uname: Linux 3.19.0-32-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.18 Architecture: amd64 Date: Mon Nov 9 19:04:10 2015 Dependencies: gcc-5-base 5.1~rc1-0ubuntu1.1 libc6 2.19-0ubuntu6.6 [modified: usr/share/doc/libc6/NEWS.gz usr/share/doc/libc6/changelog.Debian.gz usr/share/doc/libc6/copyright usr/share/lintian/overrides/libc6] libgcc1 1:5.1~rc1-0ubuntu1.1 multiarch-support 2.19-0ubuntu6.6 DuplicateSignature: package:libc6:2.19-0ubuntu6.6 [modified: usr/share/doc/libc6/NEWS.gz usr/share/doc/libc6/changelog.Debian.gz usr/share/doc/libc6/copyright usr/share/lintian/overrides/libc6]:subprocess new pre-installation script returned error exit status 128 ErrorMessage: subprocess new pre-installation script returned error exit status 128 InstallationDate: Installed on 2015-09-05 (65 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) RelatedPackageVersions: dpkg 1.17.5ubuntu5.4 apt 1.0.1ubuntu2.10 SourcePackage: eglibc Title: package libc6 2.19-0ubuntu6.6 [modified: usr/share/doc/libc6/NEWS.gz usr/share/doc/libc6/changelog.Debian.gz usr/share/doc/libc6/copyright usr/share/lintian/overrides/libc6] failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 UpgradeStatus: Upgraded to vivid on 2015-11-07 (2 days ago) ** Affects: eglibc (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package need-duplicate-check vivid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to eglibc in Ubuntu. https://bugs.launchpad.net/bugs/1514643 Title: package libc6 2.19-0ubuntu6.6 [modified: usr/share/doc/libc6/NEWS.gz usr/share/doc/libc6/changelog.Debian.gz usr/share/doc/libc6/copyright usr/share/lintian/overrides/libc6] failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 Status in eglibc package in Ubuntu: New Bug description: I have been going through this everyday for a week now ProblemType: Package DistroRelease: Ubuntu 15.04 Package: libc6 2.19-0ubuntu6.6 [modified: usr/share/doc/libc6/NEWS.gz usr/share/doc/libc6/changelog.Debian.gz usr/share/doc/libc6/copyright usr/share/lintian/overrides/libc6] ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7 Uname: Linux 3.19.0-32-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.18 Architecture: amd64 Date: Mon Nov 9 19:04:10 2015 Dependencies: gcc-5-base 5.1~rc1-0ubuntu1.1 libc6 2.19-0ubuntu6.6 [modified: usr/share/doc/libc6/NEWS.gz usr/share/doc/libc6/changelog.Debian.gz usr/share/doc/libc6/copyright usr/share/lintian/overrides/libc6] libgcc1 1:5.1~rc1-0ubuntu1.1 multiarch-support 2.19-0ubuntu6.6 DuplicateSignature: package:libc6:2.19-0ubuntu6.6 [modified: usr/share/doc/libc6/NEWS.gz usr/share/doc/libc6/changelog.Debian.gz usr/share/doc/libc6/copyright usr/share/lintian/overrides/libc6]:subprocess new pre-installation script returned error exit status 128 ErrorMessage: subprocess new pre-installation script returned error exit status 128 InstallationDate: Installed on 2015-09-05 (65 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) RelatedPackageVersions: dpkg 1.17.5ubuntu5.4 apt 1.0.1ubuntu2.10 SourcePackage: eglibc Title: package libc6 2.19-0ubuntu6.6 [modified: usr/share/doc/libc6/NEWS.gz usr/share/doc/libc6/changelog.Debian.gz usr/share/doc/libc6/copyright usr/share/lintian/overrides/libc6] failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 UpgradeStatus: Upgraded to vivid on 2015-11-07 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1514643/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1392297] Re: resolvconf 1.69ubuntu1.1 breaks network install
** Changed in: resolvconf (Ubuntu) Status: Incomplete => Triaged ** Changed in: resolvconf (Ubuntu) Assignee: (unassigned) => Mathieu Trudel-Lapierre (mathieu-tl) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to resolvconf in Ubuntu. https://bugs.launchpad.net/bugs/1392297 Title: resolvconf 1.69ubuntu1.1 breaks network install Status in resolvconf package in Ubuntu: Triaged Bug description: We are experiencing problems with Ubuntu 14.04 network installations, when using the 1.69ubuntu1.1 version of resolvconf. With this version the file /etc/resolv.conf gets reset to an empty file (does only include just the standard resolvconf comments) during the installation of the resolvconf package. After that the name resolution doesn't work anymore and the subsequent installation steps fail. If we use the 1.69ubuntu1 version, everything works fine. If I make a diff of both package contents, the most significant change seems to be the inclusion of a new Sys-V init script, which (besides other things) removes the contents of the resolvconf runtime directories when called with the option "start", and the postinst script calls "invoke-rc.d resolvconf start" at the end (included by dh_installinit), which I think should do nothing during the installation because of policy-rc.d (right?), but I wonder if it actually get's called and removes the resolv.conf file that got migrated to the runtime directories earlier in the postinst script. At least that would explain our problems, because I don't really see anything else, that could cause this problem. I see that the inclusion of the new init script is coming from debian, and they call the dh_installinit with the option "--no-start" in debian/rules, while the Ubuntu package calls the dh_installinit only with the option "-r". And debian inserts the debhelper code a lot earlier in the postinst script. Could this be what's causing the problem? As soon I have more time, I will try to debug this further and provide more information. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1392297/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 798414] Re: update-initramfs should produce a more helpful error when there isn't enough free space
No, Bill Canaday (bill13510). No, no, no. And no. The linux way is everyone does their bit to make the software better. Users, who are not developers or system administrators, report when things don't work properly. This is a time-consuming and often seemingly thankless, fruitless and pointless process. But they persist because they share with developers the hope that the system might become good enough one day for all users, and not just those who are prepared to put up with the unending extra hours is takes to put up with, work around, and fix all the problems inherent in this perpetually unfinished, half- finished, half-baked software. -- 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/798414 Title: update-initramfs should produce a more helpful error when there isn't enough free space Status in initramfs-tools: Confirmed Status in Ubuntu: Fix Released Status in initramfs-tools package in Ubuntu: Confirmed Bug description: Binary package hint: initramfs-tools When generating a new initramfs there is no check for available free space, subsequently its possible for update-initramfs to fail due to a lack of free space. This is resulting in package installation failures for initramfs-tools. For example: Setting up initramfs-tools (0.98.8ubuntu3) ... update-initramfs: deferring update (trigger activated) Processing triggers for initramfs-tools ... update-initramfs: Generating /boot/initrd.img-2.6.38-8-generic gzip: stdout: No space left on device E: mkinitramfs failure cpio 141 gzip 1 update-initramfs: failed for /boot/initrd.img-2.6.38-8-generic dpkg: error processing initramfs-tools (--configure): subprocess installed post-installation script returned error exit status 1 WORKAROUND: Remove unused kernels using computer janitor or manually free space on your partition containing the /boot file system. To manage notifications about this bug go to: https://bugs.launchpad.net/initramfs-tools/+bug/798414/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 780776] Re: Launcher - No feedback when application launched elsewhere
*** This bug is a duplicate of bug 893140 *** https://bugs.launchpad.net/bugs/893140 ** This bug has been marked a duplicate of bug 893140 Launcher - The Launcher should provide instant visual feedback when a user clicks on a icon to launch an application -- 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/780776 Title: Launcher - No feedback when application launched elsewhere Status in Ayatana Design: Fix Committed Status in BAMF: Won't Fix Status in One Hundred Papercuts: Triaged Status in Unity: Won't Fix Status in bamf package in Ubuntu: Triaged Status in unity package in Ubuntu: Won't Fix Status in unity8 package in Ubuntu: Fix Released Bug description: If you launch an application, for example the media player, and it take a few seconds to load there is no feedback that the OS is doing something. In my usual case I am launching by double clicking on a media file and the application can take up to 20 seconds to load. I often do not know whether I double clicked fast enough and do it again leading to multiple copies of the application opening (which leads to a separate set of issues) In other operating systems this is normally handled by immediately showing an hour glass icon or similar while the application is opened. Ubuntu 11.04, default setup except desktop effects are turned off. I'm not sure if this is easy to fix or not. --- Desired resolution: - As soon as a user chooses to open a file (for example by double clicking on the file in Nautilus, or single clicking on the file in the Dash File Lens), the 'loading' Launcher effect should be triggered *if* the target application is not currently running. (the 'loading' Launcher effect is currently triggered when a user clicks on a non-running application in the launcher) - If the target application is not pinned to the Launcher, it should be added to the Launcher instantaneously the moment the user chooses to open the file. - The 'application loading' should always be triggered instantaneously when ever a application starts to load, even if the application is not pinned to the Launcher. This includes when applications are launched via either the Dash or the command line. - also fix bug #893140 To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/780776/+subscriptions -- Mailing list: https://launchpad.net/~touch-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: [SRU] failure to start a container
** Changed in: lxc (Ubuntu Trusty) Status: Incomplete => Fix Released -- 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: [SRU] failure to start a container Status in lxc package in Ubuntu: Fix Released Status in lxc source package in Trusty: Fix Released Status in lxc source package in Utopic: Fix Released Bug description: [Impact] Without this patch containers that don't have a complete apparmor configuration fail to start. Making lxc unusable to run Debian Sid and Jessie (at least). This bug is not present in Trusty, which ships 1.0.7 (Debian Sid runs OK). [Test Case] - Create a debian sid container $ sudo env SUITE=sid lxc-create -t debian -n sid - Start the container $ sudo lxc-start -n sid Expected behavior: The container is started Actual behavior: $ sudo lxc-start -F -n sid 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 'sid' 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/sid-2 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 perf_event:lxc/sid-2 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 net_prio:lxc/sid-2 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 net_cls:lxc/sid-2 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 memory:lxc/sid-2 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 hugetlb:lxc/sid-2 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 freezer:lxc/sid-2 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 devices:lxc/sid-2 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 cpuset:lxc/sid-2 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 cpuacct:lxc/sid-2 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 cpu:lxc/sid-2 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 blkio:lxc/sid-2 lxc-start: lxc_start.c: main: 337 The container failed to start. lxc-start: lxc_start.c: main: 341 Additional information can be obtained by setting the --logfile and --logpriority options. [Regression Potential] No regressions expected, different versions of Ubuntu and Debian containers were tested with this patch applied. [Other Info] 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 Sw
[Touch-packages] [Bug 1436723] Re: Regression: Nested LXC is broken on Vivid
** Changed in: lxc (Ubuntu Vivid) Status: New => In Progress -- 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/1436723 Title: Regression: Nested LXC is broken on Vivid Status in lxc package in Ubuntu: Fix Released Status in lxc source package in Vivid: In Progress Bug description: The nested LXC functionality seems to be broken on Vivid, at least with the following setup: Vivid (Host) -> Trusty (Outer LXC) -> Trusty (Inner LXC) What happens: The Inner LXC start command fails when trying to start with: http://pastebin.ubuntu.com/10682639/ ( 631 cgroup error? 100 cgroups with this name already running seems to be the revelant error message). What is expected to happen: The inner LXC start command is expected to succeed and result in a running nested container. Steps to reproduce: - Install vivid server daily, update. - sudo apt-get install lxc - sudo lxc-create -n outer -t ubuntu -- --release trusty --mirror=http://ch.archive.ubuntu.com/ubuntu -b $USER - sudo su - echo 'lxc.aa_profile = lxc-container-default-with-nesting' >> /var/lib/lxc/outer/config - exit - sudo lxc-start -n outer - (SSH to outer) - sudo apt-get update && sudo apt-get dist-upgrade - sudo apt-get install lxc - sudo lxc-create -n inner -t ubuntu -- --release trusty --mirror=http://ch.archive.ubuntu.com/ubuntu -b $USER - sudo lxc-start -n inner Fails with: http://pastebin.ubuntu.com/10682639/ Enabling debug logs for this action yields: http://pastebin.ubuntu.com/10682658/ Control: The exact same scenario works on trusty and utopic. Tested by spinning up server installs (from isos) in KVMs and verifying manually. Any further log or information available on request, including KVM images demonstrating the problem. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: lxc 1.1.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2 Uname: Linux 3.19.0-10-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.16.2-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity Date: Thu Mar 26 08:43:56 2015 InstallationDate: Installed on 2015-03-12 (13 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150306) 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1436723/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1242074] Re: lxc-ls shows wrong status
** Changed in: lxc (Ubuntu Precise) Status: Confirmed => Invalid -- 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/1242074 Title: lxc-ls shows wrong status Status in lxc package in Ubuntu: Fix Released Status in lxc source package in Precise: Invalid Status in lxc source package in Quantal: Won't Fix Status in lxc source package in Raring: Won't Fix Status in lxc source package in Saucy: Fix Released Status in lxc source package in Trusty: Fix Released Bug description: = SRU Justification: 1. Impact: standard lxc-tools do not work (transparently) with autostarted containers. Importantely, a duplicate container can be started. 2. Development fix: make sure to start containers (in lxc-instance) such that their command sockets are not in an "anonymous" lxcpath. 3. Stable fix: same as development fix. 4. Test case: Create an autostart container; start it with lxc-instance; look for it with lxc-ls. 5. Regression potential: Incorrectly setup autostart containers may no longer start with a fix. (the /etc/autostart/$name link must be a symbolic link to /var/lib/lxc/$name/config) == I just upgraded to ubuntu saucy and found a strange behaviour. The command lxc-ls doesn't show the correct status of running machines. as you can see my output for jenkins is "stopped", but I am logged into the system (jenkins) at the very same moment, so it is running. I can also do thinks within the virtual machine, but the status doesn't change. # lxc-ls --fancy NAME STATEIPV4 IPV6 AUTOSTART - jenkinsSTOPPED - - NO php-54-32 STOPPED - - NO test STOPPED - - NO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1242074/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1304167] Re: syntax error, trusty beta-2 cloud image
** Changed in: lxc (Ubuntu Trusty) Status: New => Fix Released -- 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/1304167 Title: syntax error, trusty beta-2 cloud image Status in libvirt package in Ubuntu: Fix Released Status in lxc package in Ubuntu: Fix Released Status in libvirt source package in Trusty: Fix Released Status in lxc source package in Trusty: Fix Released Bug description: IMPACT: libvirt cannot be installed without apparmor TEST CASE: set up a new VM, apt-get install libvirt-bin; check whether apparmor was installed REGRESSION POTENTIAL: none, libvirt did not depend on apparmor previously. sudo apt-get install lxc -y Setting up lxc (1.0.2-0ubuntu2) ... AppArmor parser error for /etc/apparmor.d/lxc-containers in /etc/apparmor.d/abstractions/lxc/container-base at line 6: syntax error, unexpected TOK_END_OF_RULE, expecting TOK_MODE AppArmor parser error for /etc/apparmor.d/usr.bin.lxc-start in /etc/apparmor.d/abstractions/lxc/start-container at line 5: syntax error, unexpected TOK_END_OF_RULE, expecting TOK_MODE lxc start/running To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1304167/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1304936] Re: lxc-clone doesn't replace the hostname in some places
** Changed in: lxc (Ubuntu Trusty) Status: Confirmed => Fix Released -- 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/1304936 Title: lxc-clone doesn't replace the hostname in some places Status in lxc package in Ubuntu: Fix Released Status in lxc source package in Trusty: Fix Released Bug description: after cloning a container, /etc/hosts /etc/mailname still contained the old hostname so mail delivery inside the container was broken, and every invocation of sudo sent an error mail to root that the hostname couldn't be resolved ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lxc 1.0.2-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 Date: Wed Apr 9 11:27:37 2014 EcryptfsInUse: Yes ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 LANGUAGE=en_US:de:en SHELL=/bin/bash SourcePackage: lxc UpgradeStatus: Upgraded to trusty on 2013-03-06 (398 days ago) defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up lxc.network.hwaddr = 00:16:3e:xx:xx:xx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1304936/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1342960] Re: comments in common.conf must be updated
** Changed in: lxc (Ubuntu Trusty) Status: Triaged => Fix Released -- 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/1342960 Title: comments in common.conf must be updated Status in lxc: In Progress Status in lxc package in Ubuntu: Fix Released Status in lxc source package in Trusty: Fix Released Bug description: I tried to run a juju charm (jenkins-lxc) that starts a lxc container so I added lxc.aa_profile = lxc-container-default-with-nesting and lxc.hook.mount = /usr/share/lxc/hooks/mountcgroups to /var/lib/lxc /juju-trusty-template/config and then tried to deploy the service. I got a failure from juju: agent-state-info: 'error executing "lxc-start": The container failed to start.; To get more details, run the container in foreground mode.; Additional information can be obtained by setting the --logfile and --log-priority options.' So I tried to start the container manually: $ sudo lxc-start -n matsubara-local-machine-1 --logpriority DEBUG --logfile /tmp/lxc.log which gave me this log: http://paste.ubuntu.com/7805486/ I removed lxc.hook.mount = /usr/share/lxc/hooks/mountcgroups from the /var/lib/lxc/juju-trusty-template/config and tried again. Got the same error I created the file /etc/default/cgmanager and added cgmanager_opts="-- debug" And got in /var/log/upstart/cgmanager.log: http://paste.ubuntu.com/7805602/ Additional info: release, kernel version, lxc version, cgmanager version hallyn, I'm running this on Trusty, 3.13.0-30-generic, lxc 1.0.4-0ubuntu0.1 and 0.24-0ubuntu7 /proc/self/cgroup content: http://paste.ubuntu.com/7805492/ The config for the juju template used to start local provider containers in /var/lib/lxc/juju-trusty-template/config: http://paste.ubuntu.com/7805606/ And the config for /var/lib/lxc/matsubara-local-machine-1/config: http://paste.ubuntu.com/7805610/ To manage notifications about this bug go to: https://bugs.launchpad.net/lxc/+bug/1342960/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1253669] Re: unable to launch lxc application containers when dropping cap_sysadmin
** Changed in: lxc (Ubuntu Precise) Status: New => Won't Fix -- 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/1253669 Title: unable to launch lxc application containers when dropping cap_sysadmin Status in lxc package in Ubuntu: Fix Released Status in lxc source package in Precise: Won't Fix Status in lxc source package in Quantal: Won't Fix Status in lxc source package in Raring: Won't Fix Status in lxc source package in Saucy: Won't Fix Bug description: SRU Justification 1. Impact: cannot lxc-execute a container without cap_sys_admin 2. Development fix: don't fail if lxc-init cannot mount /proc 3. Stable fix: same as development fix. 4. Test case: sudo lxc-create -t ubuntu-cloud -n c1 sudo lxc-start -n c1 (log in) sudo apt-get -y install --no-install-recommends lxc sudo poweroff sudo lxc-execcute -n c1 -s lxc.cap.drop=sys_admin /bin/bash 5. Regression potential: none Using the 0.8.0~rc1 lxc release, it was possible to start an application container with the lxc.cap.drop=sys_admin option (# lxc- execute -n foo -s lxc.cap.drop=sys_admin -- /bin/bash). Since the new 1.0.0~alpha1 release, this is not possible anymore; the application immediately crashes upon being called by lxc-init, thus killing the container. When any other capability (or combination of capabilities) is dropped, the container still starts up however, only dropping cap_sys_admin results in an error. I've attached the debug output of # lxc-execute -o foo -l DEBUG -n foo -s lxc.cap.drop=sys_admin -- /bin/bash for reference. Release: 12.04.3 with HWE, Kernel 3.8.0-32-generic #47~precise1-Ubuntu SMP Wed Oct 2 16:19:35 UTC 2013 x86_64 LXC version: 1.0.0~alpha1-0ubuntu13~ubuntu12.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1253669/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1346815] Re: lxc-clone causes duplicate MAC address and IP address
** Changed in: lxc (Ubuntu Trusty)
Status: Triaged => Fix Released
--
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/1346815
Title:
lxc-clone causes duplicate MAC address and IP address
Status in lxc package in Ubuntu:
Fix Released
Status in lxc source package in Trusty:
Fix Released
Bug description:
A cloned container will have the same MAC address and IP address with
the original container.
How to reproduce:
1. $ sudo lxc-create -t ubuntu-cloud -n foo -- --release trusty
2. $ sudo lxc-clone foo bar
3. $ sudo lxc-start -d -n foo
4. $ sudo lxc-start -d -n bar
Expected result:
2 container will have different MAC and IP address each other.
Actual result:
2 container will have duplicate MAC and IP address.
# grep lxc.network.hwaddr /var/lib/lxc/{foo,bar}/config
/var/lib/lxc/foo/config:lxc.network.hwaddr = 00:16:3e:d8:d8:78
/var/lib/lxc/bar/config:lxc.network.hwaddr = 00:16:3e:d8:d8:78
$ sudo lxc-ls -f
NAME STATEIPV4 IPV6 GROUPS AUTOSTART
-
bar RUNNING 10.0.7.60 - - NO
foo RUNNING 10.0.7.60 - - NO
ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: lxc 1.1.0~alpha1-0ubuntu2
ProcVersionSignature: Ubuntu 3.16.0-4.9-generic 3.16.0-rc5
Uname: Linux 3.16.0-4-generic x86_64
ApportVersion: 2.14.4-0ubuntu2
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Jul 22 17:56:44 2014
EcryptfsInUse: Yes
InstallationDate: Installed on 2014-05-19 (64 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140518)
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
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1346815/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1410876] Re: Error executing lxc-clone: lxc_container: utils.c: mkdir_p 220 Not a directory - Could not destroy snapshot %s - failed to allocate a pty; Insufficent privileges to
** Changed in: lxc (Ubuntu Trusty)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1410876
Title:
Error executing lxc-clone: lxc_container: utils.c: mkdir_p 220 Not a
directory - Could not destroy snapshot %s - failed to allocate a pty;
Insufficent privileges to control juju-trusty-lxc-template
Status in juju-core:
Invalid
Status in lxc:
Fix Released
Status in lxc package in Ubuntu:
Fix Released
Status in lxc source package in Trusty:
Fix Released
Bug description:
This is for:
++ export OPENSTACK_RELEASE=juno
++ OPENSTACK_RELEASE=juno
++ export COMPUTE=nova-lxc
++ COMPUTE=nova-lxc
++ export UBUNTU_RELEASE=trusty
++ UBUNTU_RELEASE=trusty
Tool version is 1.20.14:
Launching instance
WARNING picked arbitrary tools &{1.20.14-precise-amd64
https://streams.canonical.com/juju/tools/releases/juju-1.20.14-precise-amd64.tgz
932640702b5d9f08a312118a4afe330444308f92b7de350de9e547719f084bd9 8130412}
- /MAAS/api/1.0/nodes/node-5f9c14e6-ae98-11e3-b194-00163efc5068/
and agent-version on node says 1.20.13.
Juju-status.yaml:
'5':
agent-state: started
agent-version: 1.20.13
containers:
5/lxc/0:
agent-state-info: 'error executing "lxc-clone": lxc_container:
utils.c: mkdir_p:
220 Not a directory - failed to create directory
''/run/lock/lxc//var/lib/lxc/juju-trusty-lxc-template/snaps'';
lxc_container: lxccontainer.c: do_snapshot_destroy: 3272 Could not
destroy
snapshot %s - failed to allocate a pty; Insufficent privileges to
control
juju-trusty-lxc-template'
instance-id: pending
series: trusty
5/lxc/1:
agent-state-info: cannot clone a running container
instance-id: pending
series: trusty
dns-name: apsaras.oil
hardware: arch=amd64 cpu-cores=4 mem=32768M
tags=hw-ok,oil-slave-1,hardware-dell-poweredge-R210
instance-id:
/MAAS/api/1.0/nodes/node-5f9c14e6-ae98-11e3-b194-00163efc5068/
series: trusty
and from log:
machine-0: 2015-01-14 15:32:12 DEBUG juju.state.apiserver apiserver.go:150 <-
[7C] unit-swift-storage-1
{"RequestId":42,"Type":"Uniter","Request":"CharmURL","Params":{"Entities":[{"Tag":"service-swift-storage"}]}}
machine-0: 2015-01-14 15:32:12 DEBUG juju.state.apiserver apiserver.go:157 ->
[7C] unit-swift-storage-1 383.812us
{"RequestId":42,"Response":{"Results":[{"Error":null,"Result":"local:trusty/swift-storage-90","Ok":false}]}}
Uniter[""].CharmURL
machine-0: 2015-01-14 15:32:12 DEBUG juju.state.apiserver apiserver.go:150 <-
[7C] unit-swift-storage-1
{"RequestId":43,"Type":"Uniter","Request":"CharmArchiveSha256","Params":{"URLs":[{"URL":"local:trusty/swift-storage-90"}]}}
machine-0: 2015-01-14 15:32:12 DEBUG juju.state.apiserver apiserver.go:157 ->
[7C] unit-swift-storage-1 777.029us
{"RequestId":43,"Response":{"Results":[{"Error":null,"Result":"b8aac93898c3cc661c0804613e5cce79a402fbe596400e8e80e8a3a1bb16c577"}]}}
Uniter[""].CharmArchiveSha256
machine-0: 2015-01-14 15:32:12 DEBUG juju.state.apiserver apiserver.go:150 <-
[61] machine-2
{"RequestId":57,"Type":"Provisioner","Request":"SetStatus","Params":{"Entities":[{"Tag":"machine-2-lxc-0","Status":"error","Info":"error
executing \"lxc-clone\": lxc_container: utils.c: mkdir_p: 220 Not a directory
- failed to create directory
'/run/lock/lxc//var/lib/lxc/juju-trusty-lxc-template/snaps'; lxc_container:
lxccontainer.c: do_snapshot_destroy: 3272 Could not destroy snapshot %s -
failed to allocate a pty; Insufficent privileges to control
juju-trusty-lxc-template","Data":null}]}}
machine-0: 2015-01-14 15:32:12 DEBUG juju.state.apiserver apiserver.go:150 <-
[7C] unit-swift-storage-1
{"RequestId":44,"Type":"Uniter","Request":"SetCharmURL","Params":{"Entities":[{"Tag":"unit-swift-storage-1","CharmURL":"local:trusty/swift-storage-90"}]}}
To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1410876/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1354375] Re: lxc-snapshot destroys container
** Changed in: lxc (Ubuntu Trusty) Status: Confirmed => Fix Released -- 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/1354375 Title: lxc-snapshot destroys container Status in lxc package in Ubuntu: Fix Released Status in lxc source package in Trusty: Fix Released Bug description: Was following instructions for lxc-snapshots at: https://help.ubuntu.com/lts/serverguide/lxc.html The problem I am reporting is that when I create a snapshot with: lxc-snapshot -n c1 which creates snap0 (snap1...snapN, etc.), after I try restore the snapshot with: lxc-snapshot -r snap0 -n c1 lxc seems to happily remove snap0 and c1, thus destroying the entire container. I would paste the output, but it was via a vbox vm and wasn't easy to copy/paste the text, so I have attached a screenshot instead. The release was 14.0.4.1 LTS with lxc 1.0.5-0ubuntu0.1. What I expected was for the snapshot to first remove c1 and then rename snap0 to c1. Seeing as how the c1 container was a LVM snapshot I can see that removing c1 (the origin of snap0) might be the reason for it killing snap0 and c1, but it seems a little unpexted, especially if this had been more than a test. Is this a real bug? ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lxc 1.0.5-0ubuntu0.1 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 Date: Fri Aug 8 05:58:41 2014 InstallationDate: Installed on 2014-08-07 (0 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) ProcEnviron: LANGUAGE=en_CA:en TERM=linux PATH=(custom, no user) LANG=en_CA.UTF-8 SHELL=/bin/bash 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1354375/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1514623] [NEW] New upstream bugfix release 1.0.8 (LXC MRE)
Public bug reported: We have released LXC 1.0.7 upstream: https://linuxcontainers.org/lxc/news This will be the eigth upstream bugfix release to hit trusty. The upstream changes are detailed at the URL above. The MRE was reviewed by Martin Pitt here: https://lists.ubuntu.com/archives/technical-board/2014-April/001869.html As for testing, this version went through both automated testing (all the tests present in lxc-tests + the python3 API tests) as well as manual testing done by myself, LXC contributors and LXC users who've been building the git stable branch for a while now. Xenial is now on LXC 1.1.5 (and 1.1.5 will hit vivid and wily as SRU) which bugfixes for 1.0.8 have been taken from. ** Affects: lxc (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: lxc (Ubuntu Trusty) Importance: Undecided Status: In Progress ** Also affects: lxc (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: lxc (Ubuntu Trusty) Status: New => In Progress ** Changed in: lxc (Ubuntu) Status: New => Fix Released -- 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/1514623 Title: New upstream bugfix release 1.0.8 (LXC MRE) Status in lxc package in Ubuntu: Fix Released Status in lxc source package in Trusty: In Progress Bug description: We have released LXC 1.0.7 upstream: https://linuxcontainers.org/lxc/news This will be the eigth upstream bugfix release to hit trusty. The upstream changes are detailed at the URL above. The MRE was reviewed by Martin Pitt here: https://lists.ubuntu.com/archives/technical- board/2014-April/001869.html As for testing, this version went through both automated testing (all the tests present in lxc-tests + the python3 API tests) as well as manual testing done by myself, LXC contributors and LXC users who've been building the git stable branch for a while now. Xenial is now on LXC 1.1.5 (and 1.1.5 will hit vivid and wily as SRU) which bugfixes for 1.0.8 have been taken from. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1514623/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1514621] [NEW] xorg crash on user switch
Public bug reported: Getting a couple of these per day at times. When switching from one user to another xorg completely locks up at times, at others just draws so slow it faster to reboot. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-32.37-generic 3.19.8-ckt7 Uname: Linux 3.19.0-32-generic x86_64 NonfreeKernelModules: fglrx .tmp.unity.support.test.0: ApportVersion: 2.17.2-0ubuntu1.7 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Nov 9 15:01:44 2015 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 5770] [1002:68b8] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:0344] InstallationDate: Installed on 2015-08-22 (79 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic root=UUID=3c41e9e3-b953-4380-b5a0-7f59928b46d0 ro quiet splash vt.handoff=7 SourcePackage: xorg UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/22/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F9 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H77M-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF9:bd08/22/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH77M-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.: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: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.12.1+15.04.20150922-0ubuntu1 version.fglrx-installer: fglrx-installer N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.9-2ubuntu1~vivid2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.9-2ubuntu1~vivid2 version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3.1 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.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Mon Nov 9 14:59:38 2015 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.17.1-0ubuntu3.1 xserver.video_driver: fglrx ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu vivid -- 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/1514621 Title: xorg crash on user switch Status in xorg package in Ubuntu: New Bug description: Getting a couple of these per day at times. When switching from one user to another xorg completely locks up at times, at others just draws so slow it faster to reboot. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-32.37-generic 3.19.8-ckt7 Uname: Linux 3.19.0-32-generic x86_64 NonfreeKernelModules: fglrx .tmp.unity.support.test.0: ApportVersion: 2.17.2-0ubuntu1.7 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Nov 9 15:01:44 2015 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 5770] [1002:68b8] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:0344] InstallationDate: Installed on 2015-08-22 (79 days ago) InstallationM
[Touch-packages] [Bug 1513985] Re: ffmpeg test idct8x8 (SIMPLE-ARM) fails on ARM32 when built with binutils from the trunk
Correction to the title of this bug report: while the test output makes it appear that the failing test is the last one (NEON), attempts to work around this build failure by temporarily disabling NEON support in the build revealed that it wasn't this test failing at all, but the test of the SIMPLE-ARM implementation. This is the implementation that Andreas pointed to in his comment, so it appears debugging this is on the right track, but since I was confused for a bit I thought I should set the record straight. Also, since the SIMPLE-ARM implementation will never be used on any Ubuntu architecture (it's superseded by either the NEON or the ARMV6 implementation on all armhf systems, which are by definition ARMv7 or later), I have uploaded ffmpeg to simply disable the test of this dead codepath at build time. ** Summary changed: - ffmpeg test idct8x8 (NEON) fails on ARM32 when built with binutils from the trunk + ffmpeg test idct8x8 (SIMPLE-ARM) fails on ARM32 when built with binutils from the trunk ** Changed in: ffmpeg (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1513985 Title: ffmpeg test idct8x8 (SIMPLE-ARM) fails on ARM32 when built with binutils from the trunk Status in binutils: Unknown Status in binutils package in Ubuntu: Confirmed Status in ffmpeg package in Ubuntu: Fix Released Bug description: ffmpeg test idct8x8 (NEON) fails on ARM32 when built with binutils from the trunk To manage notifications about this bug go to: https://bugs.launchpad.net/binutils/+bug/1513985/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1509752] Re: Bug in ensure_not_symlink() from 0003-CVE-2015-1335.patch
This bug was fixed in the package lxc - 1.0.7-0ubuntu0.10
---
lxc (1.0.7-0ubuntu0.10) trusty; urgency=medium
* Update the /proc/self/mountinfo no-symlink verification to accomodate
recursive mounts. (LP: #1509752)
-- Serge Hallyn Wed, 28 Oct 2015 12:21:38
-0500
** Changed in: lxc (Ubuntu Trusty)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1509752
Title:
Bug in ensure_not_symlink() from 0003-CVE-2015-1335.patch
Status in lxc package in Ubuntu:
Invalid
Status in lxc source package in Trusty:
Fix Released
Bug description:
===
SRU Justification
Impact: cannot start containers with lxc.mount.entries which are recursive
bind mounts
Regression potential: this makes assumptions about the ordering of
/proc/self/mountinfo, but no more so than the original CVE patch. So it should
not regress from the previous lxc version.
Test case:
#!/bin/sh
set -ex
cleanup() {
umount /mnt/etc /mnt/proc || true
lxc-stop -n t1 -k || true
lxc-destroy -n t1 || true
}
trap cleanup EXIT
mkdir -p /mnt/etc /mnt/proc
mount --bind /etc /mnt/etc
mount --bind /proc /mnt/proc
lxc-create -t download -n t1 -- -d ubuntu -r trusty -a amd64
cat >> /var/lib/lxc/t1/config << EOF
lxc.mount.entry = /mnt hostmnt none rbind,create=dir
EOF
lxc-start -n t1 -F -l trace -o /dev/stdout
echo "DONE"
===
This bug/limitation is present in lxc from 1.0.7-0ubuntu0.5 through
1.0.7-0ubuntu0.9 (or anything that incorporates 0003-CVE-2015-1335.patch).
Basically, the limitation is obvious when using recursive bind mounts because
ensure_not_symlink() only checks the last line of /proc/self/mountinfo which
will be a submount so will always fail the test and trigger:
ensure_not_symlink: 1413 Mount onto /usr/lib/x86_64-linux-
gnu/lxc/storage resulted in /usr/lib/x86_64-linux-
gnu/lxc/storage/submount, not /usr/lib/x86_64-linux-gnu/lxc/storage
Sorry if this is a duplicate, I did spend quite some time trying to
find a similar report.
Thanks!
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1509752/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1509752] Re: Bug in ensure_not_symlink() from 0003-CVE-2015-1335.patch
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1509752
Title:
Bug in ensure_not_symlink() from 0003-CVE-2015-1335.patch
Status in lxc package in Ubuntu:
Invalid
Status in lxc source package in Trusty:
Fix Released
Bug description:
===
SRU Justification
Impact: cannot start containers with lxc.mount.entries which are recursive
bind mounts
Regression potential: this makes assumptions about the ordering of
/proc/self/mountinfo, but no more so than the original CVE patch. So it should
not regress from the previous lxc version.
Test case:
#!/bin/sh
set -ex
cleanup() {
umount /mnt/etc /mnt/proc || true
lxc-stop -n t1 -k || true
lxc-destroy -n t1 || true
}
trap cleanup EXIT
mkdir -p /mnt/etc /mnt/proc
mount --bind /etc /mnt/etc
mount --bind /proc /mnt/proc
lxc-create -t download -n t1 -- -d ubuntu -r trusty -a amd64
cat >> /var/lib/lxc/t1/config << EOF
lxc.mount.entry = /mnt hostmnt none rbind,create=dir
EOF
lxc-start -n t1 -F -l trace -o /dev/stdout
echo "DONE"
===
This bug/limitation is present in lxc from 1.0.7-0ubuntu0.5 through
1.0.7-0ubuntu0.9 (or anything that incorporates 0003-CVE-2015-1335.patch).
Basically, the limitation is obvious when using recursive bind mounts because
ensure_not_symlink() only checks the last line of /proc/self/mountinfo which
will be a submount so will always fail the test and trigger:
ensure_not_symlink: 1413 Mount onto /usr/lib/x86_64-linux-
gnu/lxc/storage resulted in /usr/lib/x86_64-linux-
gnu/lxc/storage/submount, not /usr/lib/x86_64-linux-gnu/lxc/storage
Sorry if this is a duplicate, I did spend quite some time trying to
find a similar report.
Thanks!
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1509752/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1509752] Update Released
The verification of the Stable Release Update for lxc has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1509752
Title:
Bug in ensure_not_symlink() from 0003-CVE-2015-1335.patch
Status in lxc package in Ubuntu:
Invalid
Status in lxc source package in Trusty:
Fix Released
Bug description:
===
SRU Justification
Impact: cannot start containers with lxc.mount.entries which are recursive
bind mounts
Regression potential: this makes assumptions about the ordering of
/proc/self/mountinfo, but no more so than the original CVE patch. So it should
not regress from the previous lxc version.
Test case:
#!/bin/sh
set -ex
cleanup() {
umount /mnt/etc /mnt/proc || true
lxc-stop -n t1 -k || true
lxc-destroy -n t1 || true
}
trap cleanup EXIT
mkdir -p /mnt/etc /mnt/proc
mount --bind /etc /mnt/etc
mount --bind /proc /mnt/proc
lxc-create -t download -n t1 -- -d ubuntu -r trusty -a amd64
cat >> /var/lib/lxc/t1/config << EOF
lxc.mount.entry = /mnt hostmnt none rbind,create=dir
EOF
lxc-start -n t1 -F -l trace -o /dev/stdout
echo "DONE"
===
This bug/limitation is present in lxc from 1.0.7-0ubuntu0.5 through
1.0.7-0ubuntu0.9 (or anything that incorporates 0003-CVE-2015-1335.patch).
Basically, the limitation is obvious when using recursive bind mounts because
ensure_not_symlink() only checks the last line of /proc/self/mountinfo which
will be a submount so will always fail the test and trigger:
ensure_not_symlink: 1413 Mount onto /usr/lib/x86_64-linux-
gnu/lxc/storage resulted in /usr/lib/x86_64-linux-
gnu/lxc/storage/submount, not /usr/lib/x86_64-linux-gnu/lxc/storage
Sorry if this is a duplicate, I did spend quite some time trying to
find a similar report.
Thanks!
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1509752/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1514619] [NEW] nm dialog prematurely while reconnecting vpn after sleep
Public bug reported: 1. connect to vpn 2. close laptop lid so machine goes to sleep(?) 3. open laptop lid - notice that vpn is no longer connected 4. attempt to reconnect vpn At this point, the nm dialog opens, and connects to the remote vpn host, and offers the 'login' (password is saved). I guess there is a timing issue, but often, after pressing the 'login' button, there is a message that pops up saying the vpn connection has failed; resulting in me having to attempt to reconnect again. It is quite confusing and it seems like the login attempt has failed due to something wrong, but it is probably only informing me that the vpn was disconnected due to the machine going to sleep. IMO, the displaying of the 'vpn disconnected' message should not cause the attempt to reconnect to become invalid/cancelled. I don't mind seeing the message, but it should not delay my attempt to reconnect and should be followed by a 'connected' message. Description:Ubuntu 15.10 Release:15.10 $ apt-cache policy network-manager network-manager: Installed: 1.0.4-0ubuntu5.1 Candidate: 1.0.4-0ubuntu5.1 Version table: *** 1.0.4-0ubuntu5.1 0 500 http://archive.ubuntu.com/ubuntu/ wily-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.0.4-0ubuntu5 0 500 http://archive.ubuntu.com/ubuntu/ wily/main amd64 Packages ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1514619 Title: nm dialog prematurely while reconnecting vpn after sleep Status in network-manager package in Ubuntu: New Bug description: 1. connect to vpn 2. close laptop lid so machine goes to sleep(?) 3. open laptop lid - notice that vpn is no longer connected 4. attempt to reconnect vpn At this point, the nm dialog opens, and connects to the remote vpn host, and offers the 'login' (password is saved). I guess there is a timing issue, but often, after pressing the 'login' button, there is a message that pops up saying the vpn connection has failed; resulting in me having to attempt to reconnect again. It is quite confusing and it seems like the login attempt has failed due to something wrong, but it is probably only informing me that the vpn was disconnected due to the machine going to sleep. IMO, the displaying of the 'vpn disconnected' message should not cause the attempt to reconnect to become invalid/cancelled. I don't mind seeing the message, but it should not delay my attempt to reconnect and should be followed by a 'connected' message. Description: Ubuntu 15.10 Release: 15.10 $ apt-cache policy network-manager network-manager: Installed: 1.0.4-0ubuntu5.1 Candidate: 1.0.4-0ubuntu5.1 Version table: *** 1.0.4-0ubuntu5.1 0 500 http://archive.ubuntu.com/ubuntu/ wily-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.0.4-0ubuntu5 0 500 http://archive.ubuntu.com/ubuntu/ wily/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1514619/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1514556] Re: With occlusion detection, apps stop responding when switching from another app.
regression from last qtmir landing ** Also affects: canonical-devices-system-image Importance: Undecided Status: New ** Changed in: canonical-devices-system-image Importance: Undecided => Critical ** Changed in: canonical-devices-system-image Status: New => In Progress ** Changed in: canonical-devices-system-image Milestone: None => ww46-2015 ** Changed in: canonical-devices-system-image Assignee: (unassigned) => kevin gunn (kgunn72) -- 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/1514556 Title: With occlusion detection, apps stop responding when switching from another app. Status in Canonical System Image: In Progress Status in unity8 package in Ubuntu: Confirmed Bug description: If you switch from one app to the next, and start scrolling around (eg in dash) very soon after switching, the app will sometimes stop rendering. Reproduce: 1) Start an app (eg dialer) from dash 2) wait a few seconds in dialer. 3) Do a quick switch back to dash, and immediately start scrolling/swiping around. Expected: app behaves normally and responds to user input. Actual: sometimes the dash will stop responding for an undetermined amount of time, or until you interact with another part of the shell. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1514556/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1514609] [NEW] Deserialising a job with the attribute "kill_timer" and "kill_process"="PROCESS_MAIN" results in abort
Public bug reported:
Upstart sometimes aborts on a stateful re-execution
triggered by "telinit u":
job.c:1977: Assertion failed in job_deserialise: job->kill_process
Caught abort, core dumped
init:job.c:1977: Assertion failed in job_deserialise: job->kill_process
[ 69.668199] Kernel panic - not syncing: Attempted to kill init!
exitcode=0x0600
The attached file (sessions.json) is a salvaged dump of the Upstart state
that triggers the assertion failure; the problem evidently occurs while
processing the following piece:
[...]
"name": "",
"path": "\/com\/ubuntu\/Upstart\/jobs\/ureadahead\/_",
"goal": "JOB_STOP",
"state": "JOB_KILLED",
[...]
"kill_timer": {
"timeout": 180,
"due": 245
},
"kill_process": "PROCESS_MAIN",
[...]
The issue has been caught in the package ubuntu-1.12.1 (Ubuntu 14.04)
and is caused by the following code:
[init/job.c]
1954 json_kill_timer = json_object_object_get (json, "kill_timer");
1955
1956 if (json_kill_timer) {
[...]
1973 nih_local NihTimer *kill_timer =
job_deserialise_kill_timer (json_kill_timer);
1974 if (! kill_timer)
1975 goto error;
1976
1977 nih_assert (job->kill_process);
1978 job_process_set_kill_timer (job, job->kill_process,
1979 kill_timer->timeout);
1980 job_process_adj_kill_timer (job, kill_timer->due);
1981 }
The assertion (job->kill_process) fails in the routine job_deserialise()
if the deserialised job has an associated kill timer and
the field kill_process == PROCESS_MAIN.
It seems the issue might still affect the trunk as well:
there're no similar checks in the routines job_process_kill()
and job_serialise(), so if the Upstart state is serialised
after the job_process_kill() but before the job kill timer fires
then the resulting state representation cannot be restored
since job->kill_timer is non-NULL and job->kill_process
isn't PROCESS_INVALID that is a result of job_process_set_kill_timer()
operation.
Probably the assertion in question should read
(job->kill_process != PROCESS_INVALID)
if job_process_set_kill_timer() is assumed to operate correctly.
Unfortunately the issue is extremely difficult to reproduce
so additional diagnostics might be difficult to perform
and it might kill the race that triggers the issue.
** Affects: upstart (Ubuntu)
Importance: Undecided
Status: New
** Attachment added: "Serialised Upstart state dump"
https://bugs.launchpad.net/bugs/1514609/+attachment/4515781/+files/sessions.json
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upstart in Ubuntu.
https://bugs.launchpad.net/bugs/1514609
Title:
Deserialising a job with the attribute "kill_timer" and
"kill_process"="PROCESS_MAIN" results in abort
Status in upstart package in Ubuntu:
New
Bug description:
Upstart sometimes aborts on a stateful re-execution
triggered by "telinit u":
job.c:1977: Assertion failed in job_deserialise: job->kill_process
Caught abort, core dumped
init:job.c:1977: Assertion failed in job_deserialise: job->kill_process
[ 69.668199] Kernel panic - not syncing: Attempted to kill init!
exitcode=0x0600
The attached file (sessions.json) is a salvaged dump of the Upstart state
that triggers the assertion failure; the problem evidently occurs while
processing the following piece:
[...]
"name": "",
"path": "\/com\/ubuntu\/Upstart\/jobs\/ureadahead\/_",
"goal": "JOB_STOP",
"state": "JOB_KILLED",
[...]
"kill_timer": {
"timeout": 180,
"due": 245
},
"kill_process": "PROCESS_MAIN",
[...]
The issue has been caught in the package ubuntu-1.12.1 (Ubuntu 14.04)
and is caused by the following code:
[init/job.c]
1954 json_kill_timer = json_object_object_get (json, "kill_timer");
1955
1956 if (json_kill_timer) {
[...]
1973 nih_local NihTimer *kill_timer =
job_deserialise_kill_timer (json_kill_timer);
1974 if (! kill_timer)
1975 goto error;
1976
1977 nih_assert (job->kill_process);
1978 job_process_set_kill_timer (job, job->kill_process,
1979 kill_timer->timeout);
1980 job_process_adj_kill_timer (job, kill_timer->due);
1981 }
The assertion (job->kill_process) fails in the routine job_deserialise()
if the deserialised job has an associated kill timer and
the field kill_process == PROCESS_MAIN.
It seems the issue might still affect the trunk as well:
there're no similar checks in the routines job_process_kill()
and job_serialise(), so if the
[Touch-packages] [Bug 1514556] Re: With occlusion detection, apps stop responding when switching from another app.
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: unity8 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1514556 Title: With occlusion detection, apps stop responding when switching from another app. Status in unity8 package in Ubuntu: Confirmed Bug description: If you switch from one app to the next, and start scrolling around (eg in dash) very soon after switching, the app will sometimes stop rendering. Reproduce: 1) Start an app (eg dialer) from dash 2) wait a few seconds in dialer. 3) Do a quick switch back to dash, and immediately start scrolling/swiping around. Expected: app behaves normally and responds to user input. Actual: sometimes the dash will stop responding for an undetermined amount of time, or until you interact with another part of the shell. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1514556/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1514525] Re: Ubuntu 15.04 annoying system startup
Is there a way to redie this? ** Converted to question: https://answers.launchpad.net/ubuntu/+source/network-manager/+question/273980 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1514525 Title: Ubuntu 15.04 annoying system startup Status in network-manager package in Ubuntu: New Bug description: I Installed this version on a new built computer, everything was new. Installed ubuntu and have encountered on every boot or reboot; the system goes to sleep. I have to press Del, Del, Enter to wake up the program wich starts the boot process. Very annoying. Wiping the system and starting over is beyound me. It would be easier to buy a new hard drive and start over. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1514525/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1512454] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1512454/+attachment/4515745/+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/1512454 Title: Refresh change colours Status in xorg package in Ubuntu: Incomplete Bug description: I had experienced few times that refreshing window causes some places to lose right information about colour. I mean that colours change to different for e.g. grey become yellowish, and strips are visible. Also in web browser some letters disappear. It is happening not often, maybe about 2/3 times per month. I am using Ubuntu 14.04, with following Hardware: Intel core I5 540M 2.53 GHz x 2 with Intel Ironlake Mobile graphics. System Is 64 bit version. 3,7GiB Ram. I'm using two screens with different size. First one is built-in laptop screen with resolution 1366x768 (16:9) and second one is Hitachi 22HXJ06U with resolution 1920x1080 (16:9). This happened to me also in Ubuntu 15.04, and before on Ubuntu 14.10. (In all cases the same hardware and two screens). Until now I notice this bug only when on firefox so I thought it could be something wrong with firefox, but today I noticed this bug on Terminal Window. I cannot really provide information how to create this bug - twice it happened on facebook when board automatically refreshed, and today it happened on Terminal when I clicked on firefox. I tried to repeat the problem with terminal, using the same commands but without positive results. Bug is fixing when window / application getting refreshed - scrolling up / down or moving window on screen fixing it. Creating Screenshot doesn't fixing it (done by default Print Screen with animation that everything becoming white and going to normal imag e) I also checked logs (/var/log/Xorg.0.log) but I dont see any error message or something - log finishing after screen setting up. I attached picture with example in firefox window (screenshots was bit edited - facebook's board, chat and chat list been deleted). --- .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.18 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 DistUpgraded: Fresh install DistroCodename: trusty DistroRelease: Ubuntu 14.04 DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.10: added ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 18) (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd Device [144d:c06a] InstallationDate: Installed on 2015-10-17 (23 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) Lsusb: Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 004: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: SAMSUNG ELECTRONICS CO., LTD. R530/R730 Package: xorg 1:7.7+1ubuntu8.1 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic root=UUID=6a48f3d5-02ba-4f34-94c0-92cfcb90d476 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7 Tags: trusty ubuntu compiz-0.9 Uname: Linux 3.19.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 03/24/2010 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 04JV.M012.20100324.hkk dmi.board.asset.tag: Tag 12345 dmi.board.name: R530/R730 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr04JV.M012.20100324.hkk:bd03/24/2010:svnSAMSUNGELECTRONICSCO.,LTD.:pnR530/R730:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnR530/R730:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A: dmi.product.name: R530/R730 dmi.product.version: Not Applicable dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-m
[Touch-packages] [Bug 1512454] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1512454/+attachment/4515740/+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/1512454 Title: Refresh change colours Status in xorg package in Ubuntu: Incomplete Bug description: I had experienced few times that refreshing window causes some places to lose right information about colour. I mean that colours change to different for e.g. grey become yellowish, and strips are visible. Also in web browser some letters disappear. It is happening not often, maybe about 2/3 times per month. I am using Ubuntu 14.04, with following Hardware: Intel core I5 540M 2.53 GHz x 2 with Intel Ironlake Mobile graphics. System Is 64 bit version. 3,7GiB Ram. I'm using two screens with different size. First one is built-in laptop screen with resolution 1366x768 (16:9) and second one is Hitachi 22HXJ06U with resolution 1920x1080 (16:9). This happened to me also in Ubuntu 15.04, and before on Ubuntu 14.10. (In all cases the same hardware and two screens). Until now I notice this bug only when on firefox so I thought it could be something wrong with firefox, but today I noticed this bug on Terminal Window. I cannot really provide information how to create this bug - twice it happened on facebook when board automatically refreshed, and today it happened on Terminal when I clicked on firefox. I tried to repeat the problem with terminal, using the same commands but without positive results. Bug is fixing when window / application getting refreshed - scrolling up / down or moving window on screen fixing it. Creating Screenshot doesn't fixing it (done by default Print Screen with animation that everything becoming white and going to normal imag e) I also checked logs (/var/log/Xorg.0.log) but I dont see any error message or something - log finishing after screen setting up. I attached picture with example in firefox window (screenshots was bit edited - facebook's board, chat and chat list been deleted). --- .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.18 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 DistUpgraded: Fresh install DistroCodename: trusty DistroRelease: Ubuntu 14.04 DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.10: added ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 18) (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd Device [144d:c06a] InstallationDate: Installed on 2015-10-17 (23 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) Lsusb: Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 004: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: SAMSUNG ELECTRONICS CO., LTD. R530/R730 Package: xorg 1:7.7+1ubuntu8.1 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic root=UUID=6a48f3d5-02ba-4f34-94c0-92cfcb90d476 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7 Tags: trusty ubuntu compiz-0.9 Uname: Linux 3.19.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 03/24/2010 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 04JV.M012.20100324.hkk dmi.board.asset.tag: Tag 12345 dmi.board.name: R530/R730 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr04JV.M012.20100324.hkk:bd03/24/2010:svnSAMSUNGELECTRONICSCO.,LTD.:pnR530/R730:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnR530/R730:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A: dmi.product.name: R530/R730 dmi.product.version: Not Applicable dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libg
[Touch-packages] [Bug 1382233] Re: whoopsie does not upload UnreportableReason field in crash reports
** Changed in: whoopsie (Ubuntu Precise) Status: Triaged => In Progress ** Changed in: whoopsie (Ubuntu Precise) 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 whoopsie in Ubuntu. https://bugs.launchpad.net/bugs/1382233 Title: whoopsie does not upload UnreportableReason field in crash reports Status in whoopsie package in Ubuntu: Fix Released Status in whoopsie source package in Precise: In Progress Status in whoopsie source package in Trusty: In Progress Status in whoopsie source package in Vivid: In Progress Status in whoopsie source package in Wily: In Progress Bug description: In src/whoopsie.c we can see the following: /* We would only want this to see how many bugs would otherwise go * unreported: */ "UnreportableReason", The comment isn't exactly true. apport uses the UnreportableReason key to include the following information: "You have some obsolete package versions installed." It'd be useful if this information was sent to the Error Tracker so that we can decide not to ask for a core dump from these crash reports. The "obsolete package versions" check is done by checking to see if the most recent available version of the package is installed, so if someone does not have -updates enabled then that pocket is not checked and "obsolete package versions" will not be present. This is desirable because the retracers will check to see if the package version is available from any pocket. So if we send UnreportableReason to the Error Tracker we can stop asking for core dumps and retracing crashes that will fail to retrace. However, the value for UnreportableReason is translated so this may not end up helping much. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1382233/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1512454] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1512454/+attachment/4515744/+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/1512454 Title: Refresh change colours Status in xorg package in Ubuntu: Incomplete Bug description: I had experienced few times that refreshing window causes some places to lose right information about colour. I mean that colours change to different for e.g. grey become yellowish, and strips are visible. Also in web browser some letters disappear. It is happening not often, maybe about 2/3 times per month. I am using Ubuntu 14.04, with following Hardware: Intel core I5 540M 2.53 GHz x 2 with Intel Ironlake Mobile graphics. System Is 64 bit version. 3,7GiB Ram. I'm using two screens with different size. First one is built-in laptop screen with resolution 1366x768 (16:9) and second one is Hitachi 22HXJ06U with resolution 1920x1080 (16:9). This happened to me also in Ubuntu 15.04, and before on Ubuntu 14.10. (In all cases the same hardware and two screens). Until now I notice this bug only when on firefox so I thought it could be something wrong with firefox, but today I noticed this bug on Terminal Window. I cannot really provide information how to create this bug - twice it happened on facebook when board automatically refreshed, and today it happened on Terminal when I clicked on firefox. I tried to repeat the problem with terminal, using the same commands but without positive results. Bug is fixing when window / application getting refreshed - scrolling up / down or moving window on screen fixing it. Creating Screenshot doesn't fixing it (done by default Print Screen with animation that everything becoming white and going to normal imag e) I also checked logs (/var/log/Xorg.0.log) but I dont see any error message or something - log finishing after screen setting up. I attached picture with example in firefox window (screenshots was bit edited - facebook's board, chat and chat list been deleted). --- .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.18 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 DistUpgraded: Fresh install DistroCodename: trusty DistroRelease: Ubuntu 14.04 DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.10: added ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 18) (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd Device [144d:c06a] InstallationDate: Installed on 2015-10-17 (23 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) Lsusb: Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 004: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: SAMSUNG ELECTRONICS CO., LTD. R530/R730 Package: xorg 1:7.7+1ubuntu8.1 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic root=UUID=6a48f3d5-02ba-4f34-94c0-92cfcb90d476 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7 Tags: trusty ubuntu compiz-0.9 Uname: Linux 3.19.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 03/24/2010 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 04JV.M012.20100324.hkk dmi.board.asset.tag: Tag 12345 dmi.board.name: R530/R730 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr04JV.M012.20100324.hkk:bd03/24/2010:svnSAMSUNGELECTRONICSCO.,LTD.:pnR530/R730:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnR530/R730:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A: dmi.product.name: R530/R730 dmi.product.version: Not Applicable dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.li
[Touch-packages] [Bug 1512454] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1512454/+attachment/4515742/+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/1512454 Title: Refresh change colours Status in xorg package in Ubuntu: Incomplete Bug description: I had experienced few times that refreshing window causes some places to lose right information about colour. I mean that colours change to different for e.g. grey become yellowish, and strips are visible. Also in web browser some letters disappear. It is happening not often, maybe about 2/3 times per month. I am using Ubuntu 14.04, with following Hardware: Intel core I5 540M 2.53 GHz x 2 with Intel Ironlake Mobile graphics. System Is 64 bit version. 3,7GiB Ram. I'm using two screens with different size. First one is built-in laptop screen with resolution 1366x768 (16:9) and second one is Hitachi 22HXJ06U with resolution 1920x1080 (16:9). This happened to me also in Ubuntu 15.04, and before on Ubuntu 14.10. (In all cases the same hardware and two screens). Until now I notice this bug only when on firefox so I thought it could be something wrong with firefox, but today I noticed this bug on Terminal Window. I cannot really provide information how to create this bug - twice it happened on facebook when board automatically refreshed, and today it happened on Terminal when I clicked on firefox. I tried to repeat the problem with terminal, using the same commands but without positive results. Bug is fixing when window / application getting refreshed - scrolling up / down or moving window on screen fixing it. Creating Screenshot doesn't fixing it (done by default Print Screen with animation that everything becoming white and going to normal imag e) I also checked logs (/var/log/Xorg.0.log) but I dont see any error message or something - log finishing after screen setting up. I attached picture with example in firefox window (screenshots was bit edited - facebook's board, chat and chat list been deleted). --- .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.18 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 DistUpgraded: Fresh install DistroCodename: trusty DistroRelease: Ubuntu 14.04 DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.10: added ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 18) (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd Device [144d:c06a] InstallationDate: Installed on 2015-10-17 (23 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) Lsusb: Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 004: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: SAMSUNG ELECTRONICS CO., LTD. R530/R730 Package: xorg 1:7.7+1ubuntu8.1 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic root=UUID=6a48f3d5-02ba-4f34-94c0-92cfcb90d476 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7 Tags: trusty ubuntu compiz-0.9 Uname: Linux 3.19.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 03/24/2010 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 04JV.M012.20100324.hkk dmi.board.asset.tag: Tag 12345 dmi.board.name: R530/R730 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr04JV.M012.20100324.hkk:bd03/24/2010:svnSAMSUNGELECTRONICSCO.,LTD.:pnR530/R730:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnR530/R730:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A: dmi.product.name: R530/R730 dmi.product.version: Not Applicable dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-m
[Touch-packages] [Bug 1512454] GconfCompiz.txt
apport information ** Attachment added: "GconfCompiz.txt" https://bugs.launchpad.net/bugs/1512454/+attachment/4515739/+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/1512454 Title: Refresh change colours Status in xorg package in Ubuntu: Incomplete Bug description: I had experienced few times that refreshing window causes some places to lose right information about colour. I mean that colours change to different for e.g. grey become yellowish, and strips are visible. Also in web browser some letters disappear. It is happening not often, maybe about 2/3 times per month. I am using Ubuntu 14.04, with following Hardware: Intel core I5 540M 2.53 GHz x 2 with Intel Ironlake Mobile graphics. System Is 64 bit version. 3,7GiB Ram. I'm using two screens with different size. First one is built-in laptop screen with resolution 1366x768 (16:9) and second one is Hitachi 22HXJ06U with resolution 1920x1080 (16:9). This happened to me also in Ubuntu 15.04, and before on Ubuntu 14.10. (In all cases the same hardware and two screens). Until now I notice this bug only when on firefox so I thought it could be something wrong with firefox, but today I noticed this bug on Terminal Window. I cannot really provide information how to create this bug - twice it happened on facebook when board automatically refreshed, and today it happened on Terminal when I clicked on firefox. I tried to repeat the problem with terminal, using the same commands but without positive results. Bug is fixing when window / application getting refreshed - scrolling up / down or moving window on screen fixing it. Creating Screenshot doesn't fixing it (done by default Print Screen with animation that everything becoming white and going to normal imag e) I also checked logs (/var/log/Xorg.0.log) but I dont see any error message or something - log finishing after screen setting up. I attached picture with example in firefox window (screenshots was bit edited - facebook's board, chat and chat list been deleted). --- .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.18 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 DistUpgraded: Fresh install DistroCodename: trusty DistroRelease: Ubuntu 14.04 DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.10: added ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 18) (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd Device [144d:c06a] InstallationDate: Installed on 2015-10-17 (23 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) Lsusb: Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 004: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: SAMSUNG ELECTRONICS CO., LTD. R530/R730 Package: xorg 1:7.7+1ubuntu8.1 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic root=UUID=6a48f3d5-02ba-4f34-94c0-92cfcb90d476 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7 Tags: trusty ubuntu compiz-0.9 Uname: Linux 3.19.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 03/24/2010 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 04JV.M012.20100324.hkk dmi.board.asset.tag: Tag 12345 dmi.board.name: R530/R730 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr04JV.M012.20100324.hkk:bd03/24/2010:svnSAMSUNGELECTRONICSCO.,LTD.:pnR530/R730:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnR530/R730:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A: dmi.product.name: R530/R730 dmi.product.version: Not Applicable dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-m
[Touch-packages] [Bug 1512454] xserver.devices.txt
apport information ** Attachment added: "xserver.devices.txt" https://bugs.launchpad.net/bugs/1512454/+attachment/4515754/+files/xserver.devices.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/1512454 Title: Refresh change colours Status in xorg package in Ubuntu: Incomplete Bug description: I had experienced few times that refreshing window causes some places to lose right information about colour. I mean that colours change to different for e.g. grey become yellowish, and strips are visible. Also in web browser some letters disappear. It is happening not often, maybe about 2/3 times per month. I am using Ubuntu 14.04, with following Hardware: Intel core I5 540M 2.53 GHz x 2 with Intel Ironlake Mobile graphics. System Is 64 bit version. 3,7GiB Ram. I'm using two screens with different size. First one is built-in laptop screen with resolution 1366x768 (16:9) and second one is Hitachi 22HXJ06U with resolution 1920x1080 (16:9). This happened to me also in Ubuntu 15.04, and before on Ubuntu 14.10. (In all cases the same hardware and two screens). Until now I notice this bug only when on firefox so I thought it could be something wrong with firefox, but today I noticed this bug on Terminal Window. I cannot really provide information how to create this bug - twice it happened on facebook when board automatically refreshed, and today it happened on Terminal when I clicked on firefox. I tried to repeat the problem with terminal, using the same commands but without positive results. Bug is fixing when window / application getting refreshed - scrolling up / down or moving window on screen fixing it. Creating Screenshot doesn't fixing it (done by default Print Screen with animation that everything becoming white and going to normal imag e) I also checked logs (/var/log/Xorg.0.log) but I dont see any error message or something - log finishing after screen setting up. I attached picture with example in firefox window (screenshots was bit edited - facebook's board, chat and chat list been deleted). --- .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.18 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 DistUpgraded: Fresh install DistroCodename: trusty DistroRelease: Ubuntu 14.04 DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.10: added ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 18) (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd Device [144d:c06a] InstallationDate: Installed on 2015-10-17 (23 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) Lsusb: Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 004: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: SAMSUNG ELECTRONICS CO., LTD. R530/R730 Package: xorg 1:7.7+1ubuntu8.1 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic root=UUID=6a48f3d5-02ba-4f34-94c0-92cfcb90d476 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7 Tags: trusty ubuntu compiz-0.9 Uname: Linux 3.19.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 03/24/2010 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 04JV.M012.20100324.hkk dmi.board.asset.tag: Tag 12345 dmi.board.name: R530/R730 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr04JV.M012.20100324.hkk:bd03/24/2010:svnSAMSUNGELECTRONICSCO.,LTD.:pnR530/R730:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnR530/R730:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A: dmi.product.name: R530/R730 dmi.product.version: Not Applicable dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.
[Touch-packages] [Bug 1512454] xdpyinfo.txt
apport information ** Attachment added: "xdpyinfo.txt" https://bugs.launchpad.net/bugs/1512454/+attachment/4515753/+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/1512454 Title: Refresh change colours Status in xorg package in Ubuntu: Incomplete Bug description: I had experienced few times that refreshing window causes some places to lose right information about colour. I mean that colours change to different for e.g. grey become yellowish, and strips are visible. Also in web browser some letters disappear. It is happening not often, maybe about 2/3 times per month. I am using Ubuntu 14.04, with following Hardware: Intel core I5 540M 2.53 GHz x 2 with Intel Ironlake Mobile graphics. System Is 64 bit version. 3,7GiB Ram. I'm using two screens with different size. First one is built-in laptop screen with resolution 1366x768 (16:9) and second one is Hitachi 22HXJ06U with resolution 1920x1080 (16:9). This happened to me also in Ubuntu 15.04, and before on Ubuntu 14.10. (In all cases the same hardware and two screens). Until now I notice this bug only when on firefox so I thought it could be something wrong with firefox, but today I noticed this bug on Terminal Window. I cannot really provide information how to create this bug - twice it happened on facebook when board automatically refreshed, and today it happened on Terminal when I clicked on firefox. I tried to repeat the problem with terminal, using the same commands but without positive results. Bug is fixing when window / application getting refreshed - scrolling up / down or moving window on screen fixing it. Creating Screenshot doesn't fixing it (done by default Print Screen with animation that everything becoming white and going to normal imag e) I also checked logs (/var/log/Xorg.0.log) but I dont see any error message or something - log finishing after screen setting up. I attached picture with example in firefox window (screenshots was bit edited - facebook's board, chat and chat list been deleted). --- .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.18 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 DistUpgraded: Fresh install DistroCodename: trusty DistroRelease: Ubuntu 14.04 DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.10: added ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 18) (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd Device [144d:c06a] InstallationDate: Installed on 2015-10-17 (23 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) Lsusb: Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 004: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: SAMSUNG ELECTRONICS CO., LTD. R530/R730 Package: xorg 1:7.7+1ubuntu8.1 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic root=UUID=6a48f3d5-02ba-4f34-94c0-92cfcb90d476 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7 Tags: trusty ubuntu compiz-0.9 Uname: Linux 3.19.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 03/24/2010 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 04JV.M012.20100324.hkk dmi.board.asset.tag: Tag 12345 dmi.board.name: R530/R730 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr04JV.M012.20100324.hkk:bd03/24/2010:svnSAMSUNGELECTRONICSCO.,LTD.:pnR530/R730:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnR530/R730:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A: dmi.product.name: R530/R730 dmi.product.version: Not Applicable dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-gl
[Touch-packages] [Bug 1512454] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1512454/+attachment/4515743/+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/1512454 Title: Refresh change colours Status in xorg package in Ubuntu: Incomplete Bug description: I had experienced few times that refreshing window causes some places to lose right information about colour. I mean that colours change to different for e.g. grey become yellowish, and strips are visible. Also in web browser some letters disappear. It is happening not often, maybe about 2/3 times per month. I am using Ubuntu 14.04, with following Hardware: Intel core I5 540M 2.53 GHz x 2 with Intel Ironlake Mobile graphics. System Is 64 bit version. 3,7GiB Ram. I'm using two screens with different size. First one is built-in laptop screen with resolution 1366x768 (16:9) and second one is Hitachi 22HXJ06U with resolution 1920x1080 (16:9). This happened to me also in Ubuntu 15.04, and before on Ubuntu 14.10. (In all cases the same hardware and two screens). Until now I notice this bug only when on firefox so I thought it could be something wrong with firefox, but today I noticed this bug on Terminal Window. I cannot really provide information how to create this bug - twice it happened on facebook when board automatically refreshed, and today it happened on Terminal when I clicked on firefox. I tried to repeat the problem with terminal, using the same commands but without positive results. Bug is fixing when window / application getting refreshed - scrolling up / down or moving window on screen fixing it. Creating Screenshot doesn't fixing it (done by default Print Screen with animation that everything becoming white and going to normal imag e) I also checked logs (/var/log/Xorg.0.log) but I dont see any error message or something - log finishing after screen setting up. I attached picture with example in firefox window (screenshots was bit edited - facebook's board, chat and chat list been deleted). --- .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.18 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 DistUpgraded: Fresh install DistroCodename: trusty DistroRelease: Ubuntu 14.04 DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.10: added ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 18) (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd Device [144d:c06a] InstallationDate: Installed on 2015-10-17 (23 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) Lsusb: Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 004: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: SAMSUNG ELECTRONICS CO., LTD. R530/R730 Package: xorg 1:7.7+1ubuntu8.1 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic root=UUID=6a48f3d5-02ba-4f34-94c0-92cfcb90d476 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7 Tags: trusty ubuntu compiz-0.9 Uname: Linux 3.19.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 03/24/2010 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 04JV.M012.20100324.hkk dmi.board.asset.tag: Tag 12345 dmi.board.name: R530/R730 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr04JV.M012.20100324.hkk:bd03/24/2010:svnSAMSUNGELECTRONICSCO.,LTD.:pnR530/R730:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnR530/R730:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A: dmi.product.name: R530/R730 dmi.product.version: Not Applicable dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-m
[Touch-packages] [Bug 1512454] XorgLogOld.txt
apport information ** Attachment added: "XorgLogOld.txt" https://bugs.launchpad.net/bugs/1512454/+attachment/4515750/+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/1512454 Title: Refresh change colours Status in xorg package in Ubuntu: Incomplete Bug description: I had experienced few times that refreshing window causes some places to lose right information about colour. I mean that colours change to different for e.g. grey become yellowish, and strips are visible. Also in web browser some letters disappear. It is happening not often, maybe about 2/3 times per month. I am using Ubuntu 14.04, with following Hardware: Intel core I5 540M 2.53 GHz x 2 with Intel Ironlake Mobile graphics. System Is 64 bit version. 3,7GiB Ram. I'm using two screens with different size. First one is built-in laptop screen with resolution 1366x768 (16:9) and second one is Hitachi 22HXJ06U with resolution 1920x1080 (16:9). This happened to me also in Ubuntu 15.04, and before on Ubuntu 14.10. (In all cases the same hardware and two screens). Until now I notice this bug only when on firefox so I thought it could be something wrong with firefox, but today I noticed this bug on Terminal Window. I cannot really provide information how to create this bug - twice it happened on facebook when board automatically refreshed, and today it happened on Terminal when I clicked on firefox. I tried to repeat the problem with terminal, using the same commands but without positive results. Bug is fixing when window / application getting refreshed - scrolling up / down or moving window on screen fixing it. Creating Screenshot doesn't fixing it (done by default Print Screen with animation that everything becoming white and going to normal imag e) I also checked logs (/var/log/Xorg.0.log) but I dont see any error message or something - log finishing after screen setting up. I attached picture with example in firefox window (screenshots was bit edited - facebook's board, chat and chat list been deleted). --- .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.18 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 DistUpgraded: Fresh install DistroCodename: trusty DistroRelease: Ubuntu 14.04 DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.10: added ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 18) (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd Device [144d:c06a] InstallationDate: Installed on 2015-10-17 (23 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) Lsusb: Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 004: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: SAMSUNG ELECTRONICS CO., LTD. R530/R730 Package: xorg 1:7.7+1ubuntu8.1 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic root=UUID=6a48f3d5-02ba-4f34-94c0-92cfcb90d476 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7 Tags: trusty ubuntu compiz-0.9 Uname: Linux 3.19.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 03/24/2010 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 04JV.M012.20100324.hkk dmi.board.asset.tag: Tag 12345 dmi.board.name: R530/R730 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr04JV.M012.20100324.hkk:bd03/24/2010:svnSAMSUNGELECTRONICSCO.,LTD.:pnR530/R730:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnR530/R730:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A: dmi.product.name: R530/R730 dmi.product.version: Not Applicable dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mes
[Touch-packages] [Bug 1512454] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1512454/+attachment/4515746/+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/1512454 Title: Refresh change colours Status in xorg package in Ubuntu: Incomplete Bug description: I had experienced few times that refreshing window causes some places to lose right information about colour. I mean that colours change to different for e.g. grey become yellowish, and strips are visible. Also in web browser some letters disappear. It is happening not often, maybe about 2/3 times per month. I am using Ubuntu 14.04, with following Hardware: Intel core I5 540M 2.53 GHz x 2 with Intel Ironlake Mobile graphics. System Is 64 bit version. 3,7GiB Ram. I'm using two screens with different size. First one is built-in laptop screen with resolution 1366x768 (16:9) and second one is Hitachi 22HXJ06U with resolution 1920x1080 (16:9). This happened to me also in Ubuntu 15.04, and before on Ubuntu 14.10. (In all cases the same hardware and two screens). Until now I notice this bug only when on firefox so I thought it could be something wrong with firefox, but today I noticed this bug on Terminal Window. I cannot really provide information how to create this bug - twice it happened on facebook when board automatically refreshed, and today it happened on Terminal when I clicked on firefox. I tried to repeat the problem with terminal, using the same commands but without positive results. Bug is fixing when window / application getting refreshed - scrolling up / down or moving window on screen fixing it. Creating Screenshot doesn't fixing it (done by default Print Screen with animation that everything becoming white and going to normal imag e) I also checked logs (/var/log/Xorg.0.log) but I dont see any error message or something - log finishing after screen setting up. I attached picture with example in firefox window (screenshots was bit edited - facebook's board, chat and chat list been deleted). --- .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.18 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 DistUpgraded: Fresh install DistroCodename: trusty DistroRelease: Ubuntu 14.04 DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.10: added ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 18) (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd Device [144d:c06a] InstallationDate: Installed on 2015-10-17 (23 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) Lsusb: Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 004: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: SAMSUNG ELECTRONICS CO., LTD. R530/R730 Package: xorg 1:7.7+1ubuntu8.1 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic root=UUID=6a48f3d5-02ba-4f34-94c0-92cfcb90d476 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7 Tags: trusty ubuntu compiz-0.9 Uname: Linux 3.19.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 03/24/2010 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 04JV.M012.20100324.hkk dmi.board.asset.tag: Tag 12345 dmi.board.name: R530/R730 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr04JV.M012.20100324.hkk:bd03/24/2010:svnSAMSUNGELECTRONICSCO.,LTD.:pnR530/R730:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnR530/R730:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A: dmi.product.name: R530/R730 dmi.product.version: Not Applicable dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: li
[Touch-packages] [Bug 1512454] UnitySupportTest.txt
apport information ** Attachment added: "UnitySupportTest.txt" https://bugs.launchpad.net/bugs/1512454/+attachment/4515748/+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/1512454 Title: Refresh change colours Status in xorg package in Ubuntu: Incomplete Bug description: I had experienced few times that refreshing window causes some places to lose right information about colour. I mean that colours change to different for e.g. grey become yellowish, and strips are visible. Also in web browser some letters disappear. It is happening not often, maybe about 2/3 times per month. I am using Ubuntu 14.04, with following Hardware: Intel core I5 540M 2.53 GHz x 2 with Intel Ironlake Mobile graphics. System Is 64 bit version. 3,7GiB Ram. I'm using two screens with different size. First one is built-in laptop screen with resolution 1366x768 (16:9) and second one is Hitachi 22HXJ06U with resolution 1920x1080 (16:9). This happened to me also in Ubuntu 15.04, and before on Ubuntu 14.10. (In all cases the same hardware and two screens). Until now I notice this bug only when on firefox so I thought it could be something wrong with firefox, but today I noticed this bug on Terminal Window. I cannot really provide information how to create this bug - twice it happened on facebook when board automatically refreshed, and today it happened on Terminal when I clicked on firefox. I tried to repeat the problem with terminal, using the same commands but without positive results. Bug is fixing when window / application getting refreshed - scrolling up / down or moving window on screen fixing it. Creating Screenshot doesn't fixing it (done by default Print Screen with animation that everything becoming white and going to normal imag e) I also checked logs (/var/log/Xorg.0.log) but I dont see any error message or something - log finishing after screen setting up. I attached picture with example in firefox window (screenshots was bit edited - facebook's board, chat and chat list been deleted). --- .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.18 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 DistUpgraded: Fresh install DistroCodename: trusty DistroRelease: Ubuntu 14.04 DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.10: added ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 18) (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd Device [144d:c06a] InstallationDate: Installed on 2015-10-17 (23 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) Lsusb: Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 004: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: SAMSUNG ELECTRONICS CO., LTD. R530/R730 Package: xorg 1:7.7+1ubuntu8.1 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic root=UUID=6a48f3d5-02ba-4f34-94c0-92cfcb90d476 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7 Tags: trusty ubuntu compiz-0.9 Uname: Linux 3.19.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 03/24/2010 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 04JV.M012.20100324.hkk dmi.board.asset.tag: Tag 12345 dmi.board.name: R530/R730 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr04JV.M012.20100324.hkk:bd03/24/2010:svnSAMSUNGELECTRONICSCO.,LTD.:pnR530/R730:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnR530/R730:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A: dmi.product.name: R530/R730 dmi.product.version: Not Applicable dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A versio
[Touch-packages] [Bug 1512454] MonitorsUser.xml.txt
apport information ** Attachment added: "MonitorsUser.xml.txt" https://bugs.launchpad.net/bugs/1512454/+attachment/4515741/+files/MonitorsUser.xml.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/1512454 Title: Refresh change colours Status in xorg package in Ubuntu: Incomplete Bug description: I had experienced few times that refreshing window causes some places to lose right information about colour. I mean that colours change to different for e.g. grey become yellowish, and strips are visible. Also in web browser some letters disappear. It is happening not often, maybe about 2/3 times per month. I am using Ubuntu 14.04, with following Hardware: Intel core I5 540M 2.53 GHz x 2 with Intel Ironlake Mobile graphics. System Is 64 bit version. 3,7GiB Ram. I'm using two screens with different size. First one is built-in laptop screen with resolution 1366x768 (16:9) and second one is Hitachi 22HXJ06U with resolution 1920x1080 (16:9). This happened to me also in Ubuntu 15.04, and before on Ubuntu 14.10. (In all cases the same hardware and two screens). Until now I notice this bug only when on firefox so I thought it could be something wrong with firefox, but today I noticed this bug on Terminal Window. I cannot really provide information how to create this bug - twice it happened on facebook when board automatically refreshed, and today it happened on Terminal when I clicked on firefox. I tried to repeat the problem with terminal, using the same commands but without positive results. Bug is fixing when window / application getting refreshed - scrolling up / down or moving window on screen fixing it. Creating Screenshot doesn't fixing it (done by default Print Screen with animation that everything becoming white and going to normal imag e) I also checked logs (/var/log/Xorg.0.log) but I dont see any error message or something - log finishing after screen setting up. I attached picture with example in firefox window (screenshots was bit edited - facebook's board, chat and chat list been deleted). --- .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.18 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 DistUpgraded: Fresh install DistroCodename: trusty DistroRelease: Ubuntu 14.04 DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.10: added ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 18) (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd Device [144d:c06a] InstallationDate: Installed on 2015-10-17 (23 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) Lsusb: Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 004: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: SAMSUNG ELECTRONICS CO., LTD. R530/R730 Package: xorg 1:7.7+1ubuntu8.1 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic root=UUID=6a48f3d5-02ba-4f34-94c0-92cfcb90d476 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7 Tags: trusty ubuntu compiz-0.9 Uname: Linux 3.19.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 03/24/2010 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 04JV.M012.20100324.hkk dmi.board.asset.tag: Tag 12345 dmi.board.name: R530/R730 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr04JV.M012.20100324.hkk:bd03/24/2010:svnSAMSUNGELECTRONICSCO.,LTD.:pnR530/R730:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnR530/R730:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A: dmi.product.name: R530/R730 dmi.product.version: Not Applicable dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A versio
[Touch-packages] [Bug 1512454] make.log.txt
apport information ** Attachment added: "make.log.txt" https://bugs.launchpad.net/bugs/1512454/+attachment/4515752/+files/make.log.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/1512454 Title: Refresh change colours Status in xorg package in Ubuntu: Incomplete Bug description: I had experienced few times that refreshing window causes some places to lose right information about colour. I mean that colours change to different for e.g. grey become yellowish, and strips are visible. Also in web browser some letters disappear. It is happening not often, maybe about 2/3 times per month. I am using Ubuntu 14.04, with following Hardware: Intel core I5 540M 2.53 GHz x 2 with Intel Ironlake Mobile graphics. System Is 64 bit version. 3,7GiB Ram. I'm using two screens with different size. First one is built-in laptop screen with resolution 1366x768 (16:9) and second one is Hitachi 22HXJ06U with resolution 1920x1080 (16:9). This happened to me also in Ubuntu 15.04, and before on Ubuntu 14.10. (In all cases the same hardware and two screens). Until now I notice this bug only when on firefox so I thought it could be something wrong with firefox, but today I noticed this bug on Terminal Window. I cannot really provide information how to create this bug - twice it happened on facebook when board automatically refreshed, and today it happened on Terminal when I clicked on firefox. I tried to repeat the problem with terminal, using the same commands but without positive results. Bug is fixing when window / application getting refreshed - scrolling up / down or moving window on screen fixing it. Creating Screenshot doesn't fixing it (done by default Print Screen with animation that everything becoming white and going to normal imag e) I also checked logs (/var/log/Xorg.0.log) but I dont see any error message or something - log finishing after screen setting up. I attached picture with example in firefox window (screenshots was bit edited - facebook's board, chat and chat list been deleted). --- .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.18 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 DistUpgraded: Fresh install DistroCodename: trusty DistroRelease: Ubuntu 14.04 DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.10: added ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 18) (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd Device [144d:c06a] InstallationDate: Installed on 2015-10-17 (23 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) Lsusb: Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 004: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: SAMSUNG ELECTRONICS CO., LTD. R530/R730 Package: xorg 1:7.7+1ubuntu8.1 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic root=UUID=6a48f3d5-02ba-4f34-94c0-92cfcb90d476 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7 Tags: trusty ubuntu compiz-0.9 Uname: Linux 3.19.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 03/24/2010 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 04JV.M012.20100324.hkk dmi.board.asset.tag: Tag 12345 dmi.board.name: R530/R730 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr04JV.M012.20100324.hkk:bd03/24/2010:svnSAMSUNGELECTRONICSCO.,LTD.:pnR530/R730:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnR530/R730:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A: dmi.product.name: R530/R730 dmi.product.version: Not Applicable dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-gl
[Touch-packages] [Bug 1512454] XorgLog.txt
apport information ** Attachment added: "XorgLog.txt" https://bugs.launchpad.net/bugs/1512454/+attachment/4515749/+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/1512454 Title: Refresh change colours Status in xorg package in Ubuntu: Incomplete Bug description: I had experienced few times that refreshing window causes some places to lose right information about colour. I mean that colours change to different for e.g. grey become yellowish, and strips are visible. Also in web browser some letters disappear. It is happening not often, maybe about 2/3 times per month. I am using Ubuntu 14.04, with following Hardware: Intel core I5 540M 2.53 GHz x 2 with Intel Ironlake Mobile graphics. System Is 64 bit version. 3,7GiB Ram. I'm using two screens with different size. First one is built-in laptop screen with resolution 1366x768 (16:9) and second one is Hitachi 22HXJ06U with resolution 1920x1080 (16:9). This happened to me also in Ubuntu 15.04, and before on Ubuntu 14.10. (In all cases the same hardware and two screens). Until now I notice this bug only when on firefox so I thought it could be something wrong with firefox, but today I noticed this bug on Terminal Window. I cannot really provide information how to create this bug - twice it happened on facebook when board automatically refreshed, and today it happened on Terminal when I clicked on firefox. I tried to repeat the problem with terminal, using the same commands but without positive results. Bug is fixing when window / application getting refreshed - scrolling up / down or moving window on screen fixing it. Creating Screenshot doesn't fixing it (done by default Print Screen with animation that everything becoming white and going to normal imag e) I also checked logs (/var/log/Xorg.0.log) but I dont see any error message or something - log finishing after screen setting up. I attached picture with example in firefox window (screenshots was bit edited - facebook's board, chat and chat list been deleted). --- .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.18 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 DistUpgraded: Fresh install DistroCodename: trusty DistroRelease: Ubuntu 14.04 DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.10: added ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 18) (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd Device [144d:c06a] InstallationDate: Installed on 2015-10-17 (23 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) Lsusb: Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 004: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: SAMSUNG ELECTRONICS CO., LTD. R530/R730 Package: xorg 1:7.7+1ubuntu8.1 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic root=UUID=6a48f3d5-02ba-4f34-94c0-92cfcb90d476 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7 Tags: trusty ubuntu compiz-0.9 Uname: Linux 3.19.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 03/24/2010 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 04JV.M012.20100324.hkk dmi.board.asset.tag: Tag 12345 dmi.board.name: R530/R730 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr04JV.M012.20100324.hkk:bd03/24/2010:svnSAMSUNGELECTRONICSCO.,LTD.:pnR530/R730:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnR530/R730:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A: dmi.product.name: R530/R730 dmi.product.version: Not Applicable dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx:
[Touch-packages] [Bug 1512454] Xrandr.txt
apport information ** Attachment added: "Xrandr.txt" https://bugs.launchpad.net/bugs/1512454/+attachment/4515751/+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/1512454 Title: Refresh change colours Status in xorg package in Ubuntu: Incomplete Bug description: I had experienced few times that refreshing window causes some places to lose right information about colour. I mean that colours change to different for e.g. grey become yellowish, and strips are visible. Also in web browser some letters disappear. It is happening not often, maybe about 2/3 times per month. I am using Ubuntu 14.04, with following Hardware: Intel core I5 540M 2.53 GHz x 2 with Intel Ironlake Mobile graphics. System Is 64 bit version. 3,7GiB Ram. I'm using two screens with different size. First one is built-in laptop screen with resolution 1366x768 (16:9) and second one is Hitachi 22HXJ06U with resolution 1920x1080 (16:9). This happened to me also in Ubuntu 15.04, and before on Ubuntu 14.10. (In all cases the same hardware and two screens). Until now I notice this bug only when on firefox so I thought it could be something wrong with firefox, but today I noticed this bug on Terminal Window. I cannot really provide information how to create this bug - twice it happened on facebook when board automatically refreshed, and today it happened on Terminal when I clicked on firefox. I tried to repeat the problem with terminal, using the same commands but without positive results. Bug is fixing when window / application getting refreshed - scrolling up / down or moving window on screen fixing it. Creating Screenshot doesn't fixing it (done by default Print Screen with animation that everything becoming white and going to normal imag e) I also checked logs (/var/log/Xorg.0.log) but I dont see any error message or something - log finishing after screen setting up. I attached picture with example in firefox window (screenshots was bit edited - facebook's board, chat and chat list been deleted). --- .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.18 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 DistUpgraded: Fresh install DistroCodename: trusty DistroRelease: Ubuntu 14.04 DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.10: added ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 18) (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd Device [144d:c06a] InstallationDate: Installed on 2015-10-17 (23 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) Lsusb: Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 004: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: SAMSUNG ELECTRONICS CO., LTD. R530/R730 Package: xorg 1:7.7+1ubuntu8.1 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic root=UUID=6a48f3d5-02ba-4f34-94c0-92cfcb90d476 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7 Tags: trusty ubuntu compiz-0.9 Uname: Linux 3.19.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 03/24/2010 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 04JV.M012.20100324.hkk dmi.board.asset.tag: Tag 12345 dmi.board.name: R530/R730 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr04JV.M012.20100324.hkk:bd03/24/2010:svnSAMSUNGELECTRONICSCO.,LTD.:pnR530/R730:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnR530/R730:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A: dmi.product.name: R530/R730 dmi.product.version: Not Applicable dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: li
[Touch-packages] [Bug 1512454] UdevLog.txt
apport information ** Attachment added: "UdevLog.txt" https://bugs.launchpad.net/bugs/1512454/+attachment/4515747/+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/1512454 Title: Refresh change colours Status in xorg package in Ubuntu: Incomplete Bug description: I had experienced few times that refreshing window causes some places to lose right information about colour. I mean that colours change to different for e.g. grey become yellowish, and strips are visible. Also in web browser some letters disappear. It is happening not often, maybe about 2/3 times per month. I am using Ubuntu 14.04, with following Hardware: Intel core I5 540M 2.53 GHz x 2 with Intel Ironlake Mobile graphics. System Is 64 bit version. 3,7GiB Ram. I'm using two screens with different size. First one is built-in laptop screen with resolution 1366x768 (16:9) and second one is Hitachi 22HXJ06U with resolution 1920x1080 (16:9). This happened to me also in Ubuntu 15.04, and before on Ubuntu 14.10. (In all cases the same hardware and two screens). Until now I notice this bug only when on firefox so I thought it could be something wrong with firefox, but today I noticed this bug on Terminal Window. I cannot really provide information how to create this bug - twice it happened on facebook when board automatically refreshed, and today it happened on Terminal when I clicked on firefox. I tried to repeat the problem with terminal, using the same commands but without positive results. Bug is fixing when window / application getting refreshed - scrolling up / down or moving window on screen fixing it. Creating Screenshot doesn't fixing it (done by default Print Screen with animation that everything becoming white and going to normal imag e) I also checked logs (/var/log/Xorg.0.log) but I dont see any error message or something - log finishing after screen setting up. I attached picture with example in firefox window (screenshots was bit edited - facebook's board, chat and chat list been deleted). --- .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.18 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 DistUpgraded: Fresh install DistroCodename: trusty DistroRelease: Ubuntu 14.04 DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.10: added ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 18) (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd Device [144d:c06a] InstallationDate: Installed on 2015-10-17 (23 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) Lsusb: Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 004: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: SAMSUNG ELECTRONICS CO., LTD. R530/R730 Package: xorg 1:7.7+1ubuntu8.1 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic root=UUID=6a48f3d5-02ba-4f34-94c0-92cfcb90d476 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7 Tags: trusty ubuntu compiz-0.9 Uname: Linux 3.19.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 03/24/2010 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 04JV.M012.20100324.hkk dmi.board.asset.tag: Tag 12345 dmi.board.name: R530/R730 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr04JV.M012.20100324.hkk:bd03/24/2010:svnSAMSUNGELECTRONICSCO.,LTD.:pnR530/R730:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnR530/R730:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A: dmi.product.name: R530/R730 dmi.product.version: Not Applicable dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx:
[Touch-packages] [Bug 1512454] DpkgLog.txt
apport information ** Attachment added: "DpkgLog.txt" https://bugs.launchpad.net/bugs/1512454/+attachment/4515738/+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/1512454 Title: Refresh change colours Status in xorg package in Ubuntu: Incomplete Bug description: I had experienced few times that refreshing window causes some places to lose right information about colour. I mean that colours change to different for e.g. grey become yellowish, and strips are visible. Also in web browser some letters disappear. It is happening not often, maybe about 2/3 times per month. I am using Ubuntu 14.04, with following Hardware: Intel core I5 540M 2.53 GHz x 2 with Intel Ironlake Mobile graphics. System Is 64 bit version. 3,7GiB Ram. I'm using two screens with different size. First one is built-in laptop screen with resolution 1366x768 (16:9) and second one is Hitachi 22HXJ06U with resolution 1920x1080 (16:9). This happened to me also in Ubuntu 15.04, and before on Ubuntu 14.10. (In all cases the same hardware and two screens). Until now I notice this bug only when on firefox so I thought it could be something wrong with firefox, but today I noticed this bug on Terminal Window. I cannot really provide information how to create this bug - twice it happened on facebook when board automatically refreshed, and today it happened on Terminal when I clicked on firefox. I tried to repeat the problem with terminal, using the same commands but without positive results. Bug is fixing when window / application getting refreshed - scrolling up / down or moving window on screen fixing it. Creating Screenshot doesn't fixing it (done by default Print Screen with animation that everything becoming white and going to normal imag e) I also checked logs (/var/log/Xorg.0.log) but I dont see any error message or something - log finishing after screen setting up. I attached picture with example in firefox window (screenshots was bit edited - facebook's board, chat and chat list been deleted). --- .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.18 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 DistUpgraded: Fresh install DistroCodename: trusty DistroRelease: Ubuntu 14.04 DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.10: added ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 18) (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd Device [144d:c06a] InstallationDate: Installed on 2015-10-17 (23 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) Lsusb: Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 004: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: SAMSUNG ELECTRONICS CO., LTD. R530/R730 Package: xorg 1:7.7+1ubuntu8.1 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic root=UUID=6a48f3d5-02ba-4f34-94c0-92cfcb90d476 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7 Tags: trusty ubuntu compiz-0.9 Uname: Linux 3.19.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 03/24/2010 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 04JV.M012.20100324.hkk dmi.board.asset.tag: Tag 12345 dmi.board.name: R530/R730 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr04JV.M012.20100324.hkk:bd03/24/2010:svnSAMSUNGELECTRONICSCO.,LTD.:pnR530/R730:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnR530/R730:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A: dmi.product.name: R530/R730 dmi.product.version: Not Applicable dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx:
[Touch-packages] [Bug 1512454] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1512454/+attachment/4515736/+files/CurrentDmesg.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/1512454 Title: Refresh change colours Status in xorg package in Ubuntu: Incomplete Bug description: I had experienced few times that refreshing window causes some places to lose right information about colour. I mean that colours change to different for e.g. grey become yellowish, and strips are visible. Also in web browser some letters disappear. It is happening not often, maybe about 2/3 times per month. I am using Ubuntu 14.04, with following Hardware: Intel core I5 540M 2.53 GHz x 2 with Intel Ironlake Mobile graphics. System Is 64 bit version. 3,7GiB Ram. I'm using two screens with different size. First one is built-in laptop screen with resolution 1366x768 (16:9) and second one is Hitachi 22HXJ06U with resolution 1920x1080 (16:9). This happened to me also in Ubuntu 15.04, and before on Ubuntu 14.10. (In all cases the same hardware and two screens). Until now I notice this bug only when on firefox so I thought it could be something wrong with firefox, but today I noticed this bug on Terminal Window. I cannot really provide information how to create this bug - twice it happened on facebook when board automatically refreshed, and today it happened on Terminal when I clicked on firefox. I tried to repeat the problem with terminal, using the same commands but without positive results. Bug is fixing when window / application getting refreshed - scrolling up / down or moving window on screen fixing it. Creating Screenshot doesn't fixing it (done by default Print Screen with animation that everything becoming white and going to normal imag e) I also checked logs (/var/log/Xorg.0.log) but I dont see any error message or something - log finishing after screen setting up. I attached picture with example in firefox window (screenshots was bit edited - facebook's board, chat and chat list been deleted). --- .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.18 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 DistUpgraded: Fresh install DistroCodename: trusty DistroRelease: Ubuntu 14.04 DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.10: added ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 18) (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd Device [144d:c06a] InstallationDate: Installed on 2015-10-17 (23 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) Lsusb: Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 004: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: SAMSUNG ELECTRONICS CO., LTD. R530/R730 Package: xorg 1:7.7+1ubuntu8.1 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic root=UUID=6a48f3d5-02ba-4f34-94c0-92cfcb90d476 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7 Tags: trusty ubuntu compiz-0.9 Uname: Linux 3.19.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 03/24/2010 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 04JV.M012.20100324.hkk dmi.board.asset.tag: Tag 12345 dmi.board.name: R530/R730 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr04JV.M012.20100324.hkk:bd03/24/2010:svnSAMSUNGELECTRONICSCO.,LTD.:pnR530/R730:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnR530/R730:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A: dmi.product.name: R530/R730 dmi.product.version: Not Applicable dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1
[Touch-packages] [Bug 1512454] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1512454/+attachment/4515737/+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/1512454 Title: Refresh change colours Status in xorg package in Ubuntu: Incomplete Bug description: I had experienced few times that refreshing window causes some places to lose right information about colour. I mean that colours change to different for e.g. grey become yellowish, and strips are visible. Also in web browser some letters disappear. It is happening not often, maybe about 2/3 times per month. I am using Ubuntu 14.04, with following Hardware: Intel core I5 540M 2.53 GHz x 2 with Intel Ironlake Mobile graphics. System Is 64 bit version. 3,7GiB Ram. I'm using two screens with different size. First one is built-in laptop screen with resolution 1366x768 (16:9) and second one is Hitachi 22HXJ06U with resolution 1920x1080 (16:9). This happened to me also in Ubuntu 15.04, and before on Ubuntu 14.10. (In all cases the same hardware and two screens). Until now I notice this bug only when on firefox so I thought it could be something wrong with firefox, but today I noticed this bug on Terminal Window. I cannot really provide information how to create this bug - twice it happened on facebook when board automatically refreshed, and today it happened on Terminal when I clicked on firefox. I tried to repeat the problem with terminal, using the same commands but without positive results. Bug is fixing when window / application getting refreshed - scrolling up / down or moving window on screen fixing it. Creating Screenshot doesn't fixing it (done by default Print Screen with animation that everything becoming white and going to normal imag e) I also checked logs (/var/log/Xorg.0.log) but I dont see any error message or something - log finishing after screen setting up. I attached picture with example in firefox window (screenshots was bit edited - facebook's board, chat and chat list been deleted). --- .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.18 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 DistUpgraded: Fresh install DistroCodename: trusty DistroRelease: Ubuntu 14.04 DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.10: added ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 18) (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd Device [144d:c06a] InstallationDate: Installed on 2015-10-17 (23 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) Lsusb: Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 004: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: SAMSUNG ELECTRONICS CO., LTD. R530/R730 Package: xorg 1:7.7+1ubuntu8.1 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic root=UUID=6a48f3d5-02ba-4f34-94c0-92cfcb90d476 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7 Tags: trusty ubuntu compiz-0.9 Uname: Linux 3.19.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 03/24/2010 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 04JV.M012.20100324.hkk dmi.board.asset.tag: Tag 12345 dmi.board.name: R530/R730 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr04JV.M012.20100324.hkk:bd03/24/2010:svnSAMSUNGELECTRONICSCO.,LTD.:pnR530/R730:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnR530/R730:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A: dmi.product.name: R530/R730 dmi.product.version: Not Applicable dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1
[Touch-packages] [Bug 1512454] BootLog.txt
apport information ** Attachment added: "BootLog.txt" https://bugs.launchpad.net/bugs/1512454/+attachment/4515735/+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/1512454 Title: Refresh change colours Status in xorg package in Ubuntu: Incomplete Bug description: I had experienced few times that refreshing window causes some places to lose right information about colour. I mean that colours change to different for e.g. grey become yellowish, and strips are visible. Also in web browser some letters disappear. It is happening not often, maybe about 2/3 times per month. I am using Ubuntu 14.04, with following Hardware: Intel core I5 540M 2.53 GHz x 2 with Intel Ironlake Mobile graphics. System Is 64 bit version. 3,7GiB Ram. I'm using two screens with different size. First one is built-in laptop screen with resolution 1366x768 (16:9) and second one is Hitachi 22HXJ06U with resolution 1920x1080 (16:9). This happened to me also in Ubuntu 15.04, and before on Ubuntu 14.10. (In all cases the same hardware and two screens). Until now I notice this bug only when on firefox so I thought it could be something wrong with firefox, but today I noticed this bug on Terminal Window. I cannot really provide information how to create this bug - twice it happened on facebook when board automatically refreshed, and today it happened on Terminal when I clicked on firefox. I tried to repeat the problem with terminal, using the same commands but without positive results. Bug is fixing when window / application getting refreshed - scrolling up / down or moving window on screen fixing it. Creating Screenshot doesn't fixing it (done by default Print Screen with animation that everything becoming white and going to normal imag e) I also checked logs (/var/log/Xorg.0.log) but I dont see any error message or something - log finishing after screen setting up. I attached picture with example in firefox window (screenshots was bit edited - facebook's board, chat and chat list been deleted). --- .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.18 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 DistUpgraded: Fresh install DistroCodename: trusty DistroRelease: Ubuntu 14.04 DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.10: added ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 18) (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd Device [144d:c06a] InstallationDate: Installed on 2015-10-17 (23 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) Lsusb: Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 004: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: SAMSUNG ELECTRONICS CO., LTD. R530/R730 Package: xorg 1:7.7+1ubuntu8.1 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic root=UUID=6a48f3d5-02ba-4f34-94c0-92cfcb90d476 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7 Tags: trusty ubuntu compiz-0.9 Uname: Linux 3.19.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 03/24/2010 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 04JV.M012.20100324.hkk dmi.board.asset.tag: Tag 12345 dmi.board.name: R530/R730 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr04JV.M012.20100324.hkk:bd03/24/2010:svnSAMSUNGELECTRONICSCO.,LTD.:pnR530/R730:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnR530/R730:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A: dmi.product.name: R530/R730 dmi.product.version: Not Applicable dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx:
[Touch-packages] [Bug 1512454] Re: Refresh change colours
apport information ** Tags added: apport-collected compiz-0.9 trusty ubuntu ** Description changed: I had experienced few times that refreshing window causes some places to lose right information about colour. I mean that colours change to different for e.g. grey become yellowish, and strips are visible. Also in web browser some letters disappear. It is happening not often, maybe about 2/3 times per month. I am using Ubuntu 14.04, with following Hardware: Intel core I5 540M 2.53 GHz x 2 with Intel Ironlake Mobile graphics. System Is 64 bit version. 3,7GiB Ram. I'm using two screens with different size. First one is built-in laptop screen with resolution 1366x768 (16:9) and second one is Hitachi 22HXJ06U with resolution 1920x1080 (16:9). This happened to me also in Ubuntu 15.04, and before on Ubuntu 14.10. (In all cases the same hardware and two screens). Until now I notice this bug only when on firefox so I thought it could be something wrong with firefox, but today I noticed this bug on Terminal Window. I cannot really provide information how to create this bug - twice it happened on facebook when board automatically refreshed, and today it happened on Terminal when I clicked on firefox. I tried to repeat the problem with terminal, using the same commands but without positive results. Bug is fixing when window / application getting refreshed - scrolling up / down or moving window on screen fixing it. Creating Screenshot doesn't fixing it (done by default Print Screen with animation that everything becoming white and going to normal imag e) I also checked logs (/var/log/Xorg.0.log) but I dont see any error message or something - log finishing after screen setting up. I attached picture with example in firefox window (screenshots was bit edited - facebook's board, chat and chat list been deleted). + --- + .tmp.unity.support.test.0: + + ApportVersion: 2.14.1-0ubuntu3.18 + 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 + DistUpgraded: Fresh install + DistroCodename: trusty + DistroRelease: Ubuntu 14.04 + DistroVariant: ubuntu + DkmsStatus: virtualbox, 4.3.10: added + ExtraDebuggingInterest: Yes, including running git bisection searches + GraphicsCard: + Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 18) (prog-if 00 [VGA controller]) +Subsystem: Samsung Electronics Co Ltd Device [144d:c06a] + InstallationDate: Installed on 2015-10-17 (23 days ago) + InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) + Lsusb: + Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub + Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 001 Device 004: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) + Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + MachineType: SAMSUNG ELECTRONICS CO., LTD. R530/R730 + Package: xorg 1:7.7+1ubuntu8.1 + PackageArchitecture: amd64 + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic root=UUID=6a48f3d5-02ba-4f34-94c0-92cfcb90d476 ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7 + Tags: trusty ubuntu compiz-0.9 + Uname: Linux 3.19.0-32-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: + + _MarkForUpload: True + dmi.bios.date: 03/24/2010 + dmi.bios.vendor: Phoenix Technologies Ltd. + dmi.bios.version: 04JV.M012.20100324.hkk + dmi.board.asset.tag: Tag 12345 + dmi.board.name: R530/R730 + dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. + dmi.board.version: Not Applicable + dmi.chassis.asset.tag: No Asset Tag + dmi.chassis.type: 9 + dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. + dmi.chassis.version: N/A + dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr04JV.M012.20100324.hkk:bd03/24/2010:svnSAMSUNGELECTRONICSCO.,LTD.:pnR530/R730:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnR530/R730:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A: + dmi.product.name: R530/R730 + dmi.product.version: Not Applicable + dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. + version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1 + version.ia32-libs: ia32-libs N/A + version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1 + version.libgl1-mesa-dri: libgl1-mesa-dri N/A + version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A + version.libgl1-mesa-glx: libgl1-mesa-glx N/A + version.xserver-xorg-core: xserver-xorg-core N/A + version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A + version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A + version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A + version.xserver-xorg-video-nouveau: xserver-xo
[Touch-packages] [Bug 1514498] Re: Ubuntu update 15.04 now no network enp3s0
Wifi is no longer an option. set all files to what they were on upgrade. Settings>Network> "the system network services are not compatable with this version" ** Also affects: network-manager Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1514498 Title: Ubuntu update 15.04 now no network enp3s0 Status in NetworkManager: New Status in network-manager package in Ubuntu: New Bug description: New to Ubuntu and very upset that a system update killed my Ethernet network. Thank god I have this old windows laptop to find help. It appears that eth0 has a new build enp3s0. Nice... no fore warning no options, just throw the d*mn thing into the system and let everyone else worry about it. That is P!ss Poor Programming. I found a video on youtube that helped me get my ethernet up...But on reboot the damn thing crashed again. I tried system recovery from backup, crashing the program to rebuildnothing helped it just comes back..saying you have the latest update installedthanks WiFi on my combo card works and I can print to my network printer. /etc/network/interfaces - edited to Auto enp3s0 /// iface enp3s0 inet static /// adresses and masks set to my system Resolv.conf edited to map? networks - it worked but file was reverted back after reboot. reboot and Ethernet Network device not managed error /etc/networkManager/NetworkManager.confManaged=false Ethernet Network device not managed error /etc/networkManager/NetworkManager.conf edited to list Managed=true back to no network To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1514498/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1490412] Re: rollapp.com says not a supported browser
@ Olivier No, actually on my Android tablet it works well. Even if you look at the video presentation (https://www.youtube.com/watch?feature=player_embedded&v=0kW-sgBKtZI) works on iPad, and Android devices. the limit would seem only the use of Chrome cheers g -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1490412 Title: rollapp.com says not a supported browser Status in webbrowser-app package in Ubuntu: In Progress Bug description: It would be useful to use the service RollApp (www.rollapp.com) also on the browser of Ubuntu Touch. The service uses Chrome / Chromium as the default browser to virtualize OpenSource programs (OpenOffice, Stellarium, etc.). It could be a temporary solution pending the complete corvengence. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1490412/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1497420] Re: systemd 226 (moving pid 1 into /init.scope cgroup) breaks lxc-attach
This bug was fixed in the package lxc - 1.1.5-0ubuntu1 --- lxc (1.1.5-0ubuntu1) xenial; urgency=medium * New upstream bugfix release (1.1.5) (LP: #1514558, LP: #1497420, LP: #1466458, LP: #1510619) * Drop proxy detection from the autopkgtest exercise script. -- Stéphane Graber Mon, 09 Nov 2015 14:22:16 -0500 ** Changed in: lxc (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1497420 Title: systemd 226 (moving pid 1 into /init.scope cgroup) breaks lxc-attach Status in cgmanager package in Ubuntu: Fix Released Status in lxc package in Ubuntu: Fix Released Status in lxcfs package in Ubuntu: Fix Released Status in docker package in Debian: Fix Released Bug description: Once systemd 226 is installed in an unprivileged Debian Sid container, lxc-attach no-longer functions: % lxc-attach -n siddy lxc-attach: cgmanager.c: lxc_cgmanager_enter: 698 call to cgmanager_move_pid_abs_sync failed: invalid request lxc-attach: cgmanager.c: cgm_attach: 1460 Failed to enter group /user.slice/user-1000.slice/session-1.scope/lxc/siddy/init.scope lxc-attach: attach.c: lxc_attach: 909 error communicating with child process % journalctl -u cgmanager | tail -n 1 Sep 18 20:20:44 astoria cgmanager[1169]: cgmanager:per_ctrl_move_pid_main: pid 21918 (uid 1000 gid 1000) may not write to /run/cgmanager/fs/none,name=systemd//user.slice/user-1000.slice/session-1.scope/lxc/siddy/init.scope/tasks Full walkthrough: % lxc-create -n siddy -t download -- -d debian -r sid -a amd64 Using image from local cache Unpacking the rootfs ... % lxc-start -n siddy % lxc-attach -n siddy root@siddy:/# apt-get update Get:1 http://http.debian.net sid InRelease [253 kB] ... Get:7 http://http.debian.net sid/non-free amd64 Packages [91.3 kB] Fetched 13.2 MB in 3s (3789 kB/s) Reading package lists... Done root@siddy:/# apt-get install systemd Reading package lists... Done Building dependency tree Reading state information... Done The following extra packages will be installed: libsystemd0 Suggested packages: systemd-ui systemd-container Recommended packages: libpam-systemd dbus The following packages will be upgraded: libsystemd0 systemd 2 upgraded, 0 newly installed, 0 to remove and 47 not upgraded. Need to get 3668 kB of archives. After this operation, 1100 kB disk space will be freed. Do you want to continue? [Y/n] Get:1 http://http.debian.net/debian/ sid/main libsystemd0 amd64 226-2 [242 kB] Get:2 http://http.debian.net/debian/ sid/main systemd amd64 226-2 [3426 kB] ... Setting up systemd (226-2) ... Installing new version of config file /etc/X11/xinit/xinitrc.d/50-systemd-user.sh ... Installing new version of config file /etc/dbus-1/system.d/org.freedesktop.login1.conf ... addgroup: The group `systemd-journal' already exists as a system group. Exiting. Failed to set capabilities on file `/usr/bin/systemd-detect-virt' (Invalid argument) The value of the capability argument is not permitted for a file. Or the file is not a regular (non-symlink) file Failed to execute operation: File exists Removing obsolete conffile /etc/dbus-1/system.d/org.freedesktop.machine1.conf ... root@siddy:/# exit % lxc-attach -n siddy lxc-attach: cgmanager.c: lxc_cgmanager_enter: 698 call to cgmanager_move_pid_abs_sync failed: invalid request lxc-attach: cgmanager.c: cgm_attach: 1460 Failed to enter group /user.slice/user-1000.slice/session-1.scope/lxc/siddy/init.scope lxc-attach: attach.c: lxc_attach: 909 error communicating with child process ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: lxc 1.1.3-0ubuntu1 [modified: usr/lib/x86_64-linux-gnu/lxc/lxc-net] ProcVersionSignature: Ubuntu 4.2.0-10.11-generic 4.2.0 Uname: Linux 4.2.0-10-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.18.1-0ubuntu1 Architecture: amd64 Date: Fri Sep 18 20:19:58 2015 SourcePackage: lxc UpgradeStatus: Upgraded to wily on 2015-08-28 (20 days ago) defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up lxc.network.hwaddr = 00:16:3e:xx:xx:xx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cgmanager/+bug/1497420/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1508767] Re: IBM POWER8 unhandled signal 11 / SEGV
Another potentially related issue: https://bugs.launchpad.net/ubuntu/+source/python-greenlet/+bug/1446974 I just tried comment #26 w/ -O0 and I could get a segfault. -- 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/1508767 Title: IBM POWER8 unhandled signal 11 / SEGV Status in Ubuntu Cloud Archive: New Status in apparmor package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Status in linux-meta-lts-vivid package in Ubuntu: Confirmed Bug description: Hi, We have a few IBM POWER8 servers which we're currently using as OpenStack nova compute nodes. It seems we're regularly running into issues where processes are segfaulting: | hloeung@gligar:~$ zgrep -E '(SEGV)|(unhandled signal 11)' /var/log/syslog.5.gz | Oct 16 23:31:38 gligar kernel: [88351.465559] neutron-openvsw[29733]: unhandled signal 11 at 88f90100 nip 100ba0d8 lr 101ad860 code 30001 | Oct 16 23:31:38 gligar kernel: [88351.566909] init: neutron-plugin-openvswitch-agent main process (29733) killed by SEGV signal | Oct 16 23:31:38 gligar kernel: [88351.746611] apport[29500]: unhandled signal 11 at 8850e467250040a8 nip 10201f80 lr 10202984 code 30001 | Oct 16 23:31:39 gligar kernel: [88352.245829] neutron-rootwra[29749]: unhandled signal 11 at 0809c4b61000 nip 1014ae4c lr 1014b544 code 30001 | Oct 16 23:31:50 gligar kernel: [88364.040340] neutron-rootwra[30060]: unhandled signal 11 at 08a305c12b00 nip 100b74d0 lr 100b73e4 code 30001 | Oct 16 23:31:51 gligar kernel: [88364.174218] neutron-rootwra[30065]: unhandled signal 11 at 088eb28e2f004078 nip 100b5974 lr 100aa794 code 30001 | Oct 16 23:31:52 gligar kernel: [88365.195380] neutron-rootwra[30098]: unhandled signal 11 at 88c939e32208 nip 100c8b28 lr 10060384 code 30001 | Oct 16 23:31:52 gligar kernel: [88365.362374] neutron-rootwra[30106]: unhandled signal 11 at 882c58ad2800f04f nip 3fffaef81220 lr 3fffaef811a0 code 30001 | Oct 16 23:32:27 gligar kernel: [88400.966976] neutron-rootwra[30341]: unhandled signal 11 at 88d1fbe922001008 nip 100c8b28 lr 10060384 code 30001 | Oct 16 23:32:47 gligar kernel: [88420.953053] neutron-rootwra[30412]: unhandled signal 11 at 11b6629054008000 nip 3fff9a864ac4 lr 3fff9a84c42c code 30001 | Oct 16 23:34:49 gligar kernel: [88542.778503] neutron-rootwra[30977]: unhandled signal 11 at 88540f0010a8 nip 100aa768 lr 100b74e8 code 30001 | Oct 16 23:35:23 gligar kernel: [88576.700721] neutron-openvsw[29739]: unhandled signal 11 at 08bfcbf721a8 nip 100ab390 lr 100b7c38 code 30001 | Oct 16 23:35:23 gligar kernel: [88576.804961] init: neutron-plugin-openvswitch-agent main process (29739) killed by SEGV signal | Oct 16 23:36:01 gligar kernel: [88614.995497] nova-compute[31662]: unhandled signal 11 at 8846c1c81f004008 nip 1014c2f0 lr 10151080 code 30001 | Oct 16 23:36:02 gligar kernel: [88615.110735] nova-compute[4331]: unhandled signal 11 at 88befae9220010a8 nip 100b5c8c lr 1014c734 code 30001 | Oct 16 23:36:02 gligar kernel: [88615.219436] init: nova-compute main process (4331) killed by SEGV signal | Oct 17 03:59:56 gligar kernel: [104449.890256] landscape-packa[63283]: unhandled signal 11 at 02f8 nip 101abeac lr 100a8738 code 30001 | Oct 17 04:05:00 gligar kernel: [104753.718195] sudo[63915]: unhandled signal 11 at 08e06105d1dcfff8 nip 3fffb15cf7e4 lr 3fffb15cfa00 code 30001 | hloeung@floette:~$ zgrep -E '(SEGV)|(unhandled signal 11)' /var/log/syslog.7.gz | Oct 14 16:55:30 floette kernel: [149326.697938] rsync[9915]: unhandled signal 11 at 37cb nip 3fffa242d054 lr 3fffa2426560 code 30001 | Oct 14 21:05:57 floette kernel: [164353.333697] apparmor_parser[102284]: unhandled signal 11 at 08680f00 nip 1004bbf8 lr 10028de4 code 30001 | Oct 14 22:21:24 floette kernel: [168880.481778] neutron-rootwra[153488]: unhandled signal 11 at 8860fbe21fa8 nip 100aa768 lr 100b74e8 code 30001 | Oct 14 22:21:26 floette kernel: [168882.078608] neutron-openvsw[4546]: unhandled signal 11 at 8822cbf03d08 nip 100aa764 lr 100e6900 code 30001 | Oct 14 22:21:37 floette kernel: [168893.597834] init: neutron-plugin-openvswitch-agent main process (4546) killed by SEGV signal | Oct 14 22:21:39 floette kernel: [168894.949777] nova-rootwrap[153708]: unhandled signal 11 at 88d495c93ca8 nip 100a57d4 lr 100ab42c code 30001 | Oct 14 22:21:43 floette kernel: [168898.973700] neutron-rootwra[153847]: unhandled signal 11 at 08c90df31820 nip 101ac260 lr 101ad92c code 30001 | Oct 14 22
[Touch-packages] [Bug 1466458] Re: template 'none' doesn't work with lxc-create
This bug was fixed in the package lxc - 1.1.5-0ubuntu1 --- lxc (1.1.5-0ubuntu1) xenial; urgency=medium * New upstream bugfix release (1.1.5) (LP: #1514558, LP: #1497420, LP: #1466458, LP: #1510619) * Drop proxy detection from the autopkgtest exercise script. -- Stéphane Graber Mon, 09 Nov 2015 14:22:16 -0500 ** Changed in: lxc (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1466458 Title: template 'none' doesn't work with lxc-create Status in lxc package in Ubuntu: Fix Released Bug description: Hi, The man page lxc-create(1) says that with the '-t' option to specify a template '"none" can be used to force lxc-create to skip rootfs creation'. This does not appear to work. root@somehost:/var/lib/lxc# lxc-create -n test.lol -t none lxc_container: lxccontainer.c: get_template_path: 867 No such file or directory - bad template: none lxc_container: lxccontainer.c: lxcapi_create: 1264 bad template: none lxc_container: lxc_create.c: main: 271 Error creating container test.lol There is no template in the templates dir corresponding to the 'none' template. I've looked through the upstream tarballs from releases 0.5.0, 0.6.0, ... , 1.0.0, 1.1.0, and there is no 'none' template in any. Might be just a documentation mistake, I guess. Could be a missing template, or maybe 'none' has a special meaning to the lxc- create binary; I haven't looked yet. I'll dig a little further. I'm using lxc 1.0.7-0ubuntu0.1 on Ubuntu 14.04 . thanks, Kevin ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: lxc 1.1.2-0ubuntu3 ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6 Uname: Linux 3.19.0-18-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Jun 18 11:56:34 2015 InstallationDate: Installed on 2012-01-13 (1251 days ago) InstallationMedia: Kubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) SourcePackage: lxc UpgradeStatus: Upgraded to vivid on 2015-05-14 (34 days ago) 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/ubuntu/+source/lxc/+bug/1466458/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1510619] Re: Wily: add machine fails using kvm and lxcbr0
This bug was fixed in the package lxc - 1.1.5-0ubuntu1 --- lxc (1.1.5-0ubuntu1) xenial; urgency=medium * New upstream bugfix release (1.1.5) (LP: #1514558, LP: #1497420, LP: #1466458, LP: #1510619) * Drop proxy detection from the autopkgtest exercise script. -- Stéphane Graber Mon, 09 Nov 2015 14:22:16 -0500 ** Changed in: lxc (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1510619 Title: Wily: add machine fails using kvm and lxcbr0 Status in juju-core: Invalid Status in lxc package in Ubuntu: Fix Released Bug description: Juju fails to start a machine after add-machine takes place. My environments.yaml: local: type: local container: kvm network-bridge: lxcbr0 Status output: ubuntu@ancient-spot:~$ juju status environment: local machines: "0": agent-state: started agent-version: 1.24.7.1 dns-name: localhost instance-id: localhost series: wily state-server-member-status: has-vote "1": agent-state: pending instance-id: ubuntu-local-machine-1 series: wily hardware: arch=amd64 cpu-cores=1 mem=512M root-disk=8192M debug log: http://paste.ubuntu.com/12980615/ I never see anything in the logs which indicate machine-1 is being deployed or what else could be going on with it. To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1510619/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1514558] Re: New upstream bugfix release 1.1.5 (LXC MRE)
This bug was fixed in the package lxc - 1.1.5-0ubuntu1 --- lxc (1.1.5-0ubuntu1) xenial; urgency=medium * New upstream bugfix release (1.1.5) (LP: #1514558, LP: #1497420, LP: #1466458, LP: #1510619) * Drop proxy detection from the autopkgtest exercise script. -- Stéphane Graber Mon, 09 Nov 2015 14:22:16 -0500 ** Changed in: lxc (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1514558 Title: New upstream bugfix release 1.1.5 (LXC MRE) Status in lxc package in Ubuntu: Fix Released Status in lxc source package in Vivid: In Progress Status in lxc source package in Wily: In Progress Bug description: We have released LXC 1.1.5 upstream: https://linuxcontainers.org/lxc/news This will be the second and probably last upstream bugfix release to hit vivid. The upstream changes are detailed at the URL above. The MRE was reviewed by Martin Pitt here: https://lists.ubuntu.com/archives/technical- board/2014-April/001869.html As for testing, this version went through both automated testing (all the tests present in lxc-tests + the python3 API tests) as well as manual testing done by myself, LXC contributors and LXC users who've been building the git stable branch for a while now. This release is being uploaded to: - xenial (dev release) - wily (SRU with MRE) - vivid (SRU with MRE) - trusty (backports) We're looking forward to this consistency which should make keeping track of and fixing bugs significantly easier for us. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1514558/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1382233] Re: whoopsie does not upload UnreportableReason field in crash reports
** Changed in: whoopsie (Ubuntu Wily) Status: Triaged => In Progress ** Changed in: whoopsie (Ubuntu Wily) Assignee: (unassigned) => Brian Murray (brian-murray) ** Changed in: whoopsie (Ubuntu Vivid) Status: Triaged => In Progress ** Changed in: whoopsie (Ubuntu Vivid) Assignee: (unassigned) => Brian Murray (brian-murray) ** Changed in: whoopsie (Ubuntu Trusty) Status: Triaged => In Progress ** Changed in: whoopsie (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 whoopsie in Ubuntu. https://bugs.launchpad.net/bugs/1382233 Title: whoopsie does not upload UnreportableReason field in crash reports Status in whoopsie package in Ubuntu: Fix Released Status in whoopsie source package in Precise: Triaged Status in whoopsie source package in Trusty: In Progress Status in whoopsie source package in Vivid: In Progress Status in whoopsie source package in Wily: In Progress Bug description: In src/whoopsie.c we can see the following: /* We would only want this to see how many bugs would otherwise go * unreported: */ "UnreportableReason", The comment isn't exactly true. apport uses the UnreportableReason key to include the following information: "You have some obsolete package versions installed." It'd be useful if this information was sent to the Error Tracker so that we can decide not to ask for a core dump from these crash reports. The "obsolete package versions" check is done by checking to see if the most recent available version of the package is installed, so if someone does not have -updates enabled then that pocket is not checked and "obsolete package versions" will not be present. This is desirable because the retracers will check to see if the package version is available from any pocket. So if we send UnreportableReason to the Error Tracker we can stop asking for core dumps and retracing crashes that will fail to retrace. However, the value for UnreportableReason is translated so this may not end up helping much. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1382233/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 721786] Re: (Non-overlay) scroll-bar lacks sufficient contrast to easily identify its position in the scroll-track
** Branch linked: lp:~willcooke/ubuntu-themes/ubuntu-themes -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/721786 Title: (Non-overlay) scroll-bar lacks sufficient contrast to easily identify its position in the scroll-track Status in Ayatana Design: Confirmed Status in One Hundred Papercuts: Triaged Status in ubuntu-mate: Won't Fix Status in Ubuntu theme: Confirmed Status in ubuntu-themes package in Ubuntu: Triaged Bug description: Binary package hint: gnome-session The scroll-bars that appear on the right-side and bottom of gnome windows lack sufficient contrast to the scroll-track. I have difficulty identifying where in the scroll-track the bar is positioned. I often mistake the background of the scroll-track as the scroll-bar itself. I'm using Inverted Control theme. More contrast and better color separation is needed here. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: gnome-session-bin 2.30.0-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.32-28.55-generic 2.6.32.27+drm33.12 Uname: Linux 2.6.32-28-generic i686 Architecture: i386 Date: Sat Feb 19 09:19:22 2011 ExecutablePath: /usr/bin/gnome-session InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release i386 (20100816.1) ProcEnviron: LC_TIME=en_GB.UTF-8 LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: gnome-session XsessionErrors: (polkit-gnome-authentication-agent-1:1387): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/721786/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 424215] Re: Bluetooth mouse usage makes A2DP audio stutter
Thanx to the fix in #23 I can now listen to uninterrupted A2DP audio from my laptop and use (or better, -not- use) the mouse without causing audio stutter. I'm running Kubuntu Wily (Frameworks 5.15.0, Applications 15.08.2, Plasma 5.4.2, Bluez 5.35). -- 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/424215 Title: Bluetooth mouse usage makes A2DP audio stutter Status in bluez package in Ubuntu: Fix Released Bug description: Binary package hint: bluez When I use my Bluetooth A2DP headset (Philips SHB7102) together with my mouse (Lenovo Bluetooth Laser Mouse), I notice this: Whenever I leave the mouse still for a few seconds (it seems to enter some kind of lower-power-mode) and then start to move it, my music most of the time skips for a second. This makes using these two bluetooth devices together quite annoying... The adapter is a Lenovo "ThinkPad Bluetooth with Enhanced Data Rate II" (Bus 004 Device 005: ID 0a5c:2145 Broadcom Corp.) I am running current karmic amd64 (linux 2.6.31-9). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/424215/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1508767] Re: IBM POWER8 unhandled signal 11 / SEGV
This is another bug that produces segvs on power8 (could be related, not sure yet): https://bugzilla.redhat.com/show_bug.cgi?id=1180633 I was able to reproduce this on wily/4.2 ppc64el machine trivially, and got the following output: gcc -g test.c -O2 -o test -fgnu-tm -lpthread ulimit -c unlimited while ./test ; do :; done Segmentation fault (core dumped) [13861.517681] test[78415]: unhandled signal 11 at 0284 nip 1000ccc8 lr 1000d1c8 code 30001 (gdb) core ./core [New LWP 78415] [New LWP 78412] [New LWP 78411] [New LWP 78416] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/powerpc64le-linux-gnu/libthread_db.so.1". Core was generated by `./test '. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x1000ccc8 in GTM::gtm_thread::trycommit() () [Current thread is 1 (Thread 0x3fff90cef040 (LWP 78415))] (gdb) bt #0 0x1000ccc8 in GTM::gtm_thread::trycommit() () #1 0x3fff90cee600 in ?? () #2 0x in ?? () ; However all this being said, a generic crash like this could happen from many different causes. Since we hit this with many packages could mean a shared library or compiler is causing the issue. For the reported bug, can I please have core files produced from these crashes along with the exact binary version of the program that crashes? This way I can get some analysis similar to the above and start debugging. Thanks, --chris ** Bug watch added: Red Hat Bugzilla #1180633 https://bugzilla.redhat.com/show_bug.cgi?id=1180633 -- 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/1508767 Title: IBM POWER8 unhandled signal 11 / SEGV Status in Ubuntu Cloud Archive: New Status in apparmor package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Status in linux-meta-lts-vivid package in Ubuntu: Confirmed Bug description: Hi, We have a few IBM POWER8 servers which we're currently using as OpenStack nova compute nodes. It seems we're regularly running into issues where processes are segfaulting: | hloeung@gligar:~$ zgrep -E '(SEGV)|(unhandled signal 11)' /var/log/syslog.5.gz | Oct 16 23:31:38 gligar kernel: [88351.465559] neutron-openvsw[29733]: unhandled signal 11 at 88f90100 nip 100ba0d8 lr 101ad860 code 30001 | Oct 16 23:31:38 gligar kernel: [88351.566909] init: neutron-plugin-openvswitch-agent main process (29733) killed by SEGV signal | Oct 16 23:31:38 gligar kernel: [88351.746611] apport[29500]: unhandled signal 11 at 8850e467250040a8 nip 10201f80 lr 10202984 code 30001 | Oct 16 23:31:39 gligar kernel: [88352.245829] neutron-rootwra[29749]: unhandled signal 11 at 0809c4b61000 nip 1014ae4c lr 1014b544 code 30001 | Oct 16 23:31:50 gligar kernel: [88364.040340] neutron-rootwra[30060]: unhandled signal 11 at 08a305c12b00 nip 100b74d0 lr 100b73e4 code 30001 | Oct 16 23:31:51 gligar kernel: [88364.174218] neutron-rootwra[30065]: unhandled signal 11 at 088eb28e2f004078 nip 100b5974 lr 100aa794 code 30001 | Oct 16 23:31:52 gligar kernel: [88365.195380] neutron-rootwra[30098]: unhandled signal 11 at 88c939e32208 nip 100c8b28 lr 10060384 code 30001 | Oct 16 23:31:52 gligar kernel: [88365.362374] neutron-rootwra[30106]: unhandled signal 11 at 882c58ad2800f04f nip 3fffaef81220 lr 3fffaef811a0 code 30001 | Oct 16 23:32:27 gligar kernel: [88400.966976] neutron-rootwra[30341]: unhandled signal 11 at 88d1fbe922001008 nip 100c8b28 lr 10060384 code 30001 | Oct 16 23:32:47 gligar kernel: [88420.953053] neutron-rootwra[30412]: unhandled signal 11 at 11b6629054008000 nip 3fff9a864ac4 lr 3fff9a84c42c code 30001 | Oct 16 23:34:49 gligar kernel: [88542.778503] neutron-rootwra[30977]: unhandled signal 11 at 88540f0010a8 nip 100aa768 lr 100b74e8 code 30001 | Oct 16 23:35:23 gligar kernel: [88576.700721] neutron-openvsw[29739]: unhandled signal 11 at 08bfcbf721a8 nip 100ab390 lr 100b7c38 code 30001 | Oct 16 23:35:23 gligar kernel: [88576.804961] init: neutron-plugin-openvswitch-agent main process (29739) killed by SEGV signal | Oct 16 23:36:01 gligar kernel: [88614.995497] nova-compute[31662]: unhandled signal 11 at 8846c1c81f004008 nip 1014c2f0 lr 10151080 code 30001 | Oct 16 23:36:02 gligar kernel: [88615.110735] nova-compute[4331]: unhandled signal 11 at 88befae9220010a8 nip 100b5c8c lr 1014c734 code 30001 | Oct 16 23:36:02 gligar kernel: [88615.219436] init: nova-compute main process (4331) killed by SEGV signal | Oct 17 03:59:56 gligar kernel: [104449.890256] landscape-packa[63283]: unhandled signal 11 at 02f8 nip 101abeac lr 100a8738 code 30001
[Touch-packages] [Bug 1512902] Re: apport will create .upload files for incomplete or corrupt crash reports
The test case for this bug fails with the version of apport from
precise-proposed with the following.
*** Error: Invalid problem report
This problem report is damaged and cannot be processed.
IOError('CRC check failed 0xfd06bf8f != 0xe96ce39bL',)
Press any key to continue...
Traceback (most recent call last):
File "/usr/bin/apport-cli", line 365, in
if not app.run_argv():
File "/usr/lib/python2.7/dist-packages/apport/ui.py", line 565, in run_argv
self.run_crash(self.options.crash_file, False)
File "/usr/lib/python2.7/dist-packages/apport/ui.py", line 232, in run_crash
self.report['_MarkForUpload'] = 'False'
TypeError: 'NoneType' object does not support item assignment
So it seems, with the IOError, that the crash would not have been
uploaded anyway. The crash happens in Precise because the correct field
is MarkForUpload not _MarkForUpload.
** Tags removed: verification-failed
** Tags added: verification-failed-precise
--
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/1512902
Title:
apport will create .upload files for incomplete or corrupt crash
reports
Status in apport package in Ubuntu:
Fix Released
Status in apport source package in Precise:
Fix Committed
Status in apport source package in Trusty:
Fix Committed
Status in apport source package in Vivid:
Fix Committed
Status in apport source package in Wily:
Fix Committed
Bug description:
SRU information appears in comment #3.
apport will set an UnreportableReason in the following situations for
crash reports where information collection fails or for packages that
do not exist. From apport/ui.py:
1036 try:
1037 icthread.exc_raise()
1038 except (IOError, EOFError, zlib.error) as e:
1039 # can happen with broken core dumps
1040 self.report['UnreportableReason'] = '%s\n\n%s' % (
1041 _('This problem report is damaged and cannot be
processed.'),
1042 repr(e))
1043 except ValueError: # package does not exist
1044 self.report['UnreportableReason'] = _('The report
belongs to a package that is not installed.')
1045 except Exception as e:
1046 apport.error(repr(e))
1047 self.report['UnreportableReason'] = _('An error
occurred while attempting to '
1048 'process this
problem report:') + '\n\n' + str(e)
Because an UnreportableReason exists in the report, apport will stop
collecting information. Subsequently, there is "_MarkForUpload" is
left as True (the default) so apport calls mark_report_upload which
creates a .upload file such that the report which is incomplete or
corrupt is then uploaded to the Error Tracker.
In these cases the "_MarkForUpload" key should be set to "False"
thereby preventing uploads to the Error Tracker.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1512902/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1513802] Re: [Wily] [armhf] Could not import PyQt5.QtCore
** Tags added: bot-stop-nagging -- 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/1513802 Title: [Wily] [armhf] Could not import PyQt5.QtCore Status in apport package in Ubuntu: New Bug description: When trying to start apport from the iconbar or here via terminal, I get this: $ apport-collect ERROR: Could not import module, is a package upgrade in progress? Error: No module named PyQt5.QtCore But PyQt5.QtCore is definitly there, because running the python3 interpreter and doing the import PyQt5.QtCore manually works well! ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: apport-kde 2.19.1-0ubuntu5 ProcVersionSignature: Uname: Linux 3.8.13.30-hardkernel armv7l ApportVersion: 2.19.1-0ubuntu5 Architecture: armhf CurrentDesktop: KDE Date: Fri Nov 6 11:55:13 2015 PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1513802/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1514487] Re: pua.http exploit.cve_2015_1692
Hello - CVE-2015-1692 was assigned to Microsoft Internet Explorer and does not affect Ubuntu. It seems like you're requesting support rather than reporting a security issue. Please see http://www.ubuntu.com/support for a number of support options. ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2015-1692 ** Changed in: xorg (Ubuntu) Status: New => Invalid ** Information type changed from Private Security to Public Security -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1514487 Title: pua.http exploit.cve_2015_1692 Status in xorg package in Ubuntu: Invalid Bug description: also other infections like xored witch is a trojan. I also point google on this problem . Each time I removed them, the next time I start up a browser last week I used chromium before that I used firefox I get the same result . Please what to do about it . Greetings Rob ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.16.0-52.71~14.04.1-generic 3.16.7-ckt18 Uname: Linux 3.16.0-52-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.18 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Mon Nov 9 16:09:50 2015 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller [8086:27a2] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Elitegroup Computer Systems Device [1019:0090] Subsystem: Elitegroup Computer Systems Device [1019:0090] InstallationDate: Installed on 2015-10-05 (34 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release i386 (20150218.1) MachineType: ECS P60 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-52-generic root=/dev/mapper/ubuntu--vg-root ro SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/23/2006 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080013 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: To be filled by O.E.M. dmi.board.vendor: To be filled by O.E.M. dmi.board.version: To be filled by O.E.M. 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.:bvr080013:bd02/23/2006:svnECS:pnP60:pvrToBeFilledByO.E.M.:rvnTobefilledbyO.E.M.:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: P60 dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: ECS version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1 version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Mon Nov 9 14:58:39 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.16.0-1ubuntu1.2~trusty2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1514487/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1512902] [apport/wily] possible regression found
As a part of the Stable Release Updates quality process a search for
Launchpad bug reports using the version of apport from wily-proposed was
performed and bug 1513802 was found. Please investigate this bug report
to ensure that a regression will not be created by this SRU. In the
event that this is not a regression remove the "verification-failed" tag
from this bug report and add the tag "bot-stop-nagging" to bug 1513802
(not this bug). Thanks!
** Tags added: verification-failed
--
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/1512902
Title:
apport will create .upload files for incomplete or corrupt crash
reports
Status in apport package in Ubuntu:
Fix Released
Status in apport source package in Precise:
Fix Committed
Status in apport source package in Trusty:
Fix Committed
Status in apport source package in Vivid:
Fix Committed
Status in apport source package in Wily:
Fix Committed
Bug description:
SRU information appears in comment #3.
apport will set an UnreportableReason in the following situations for
crash reports where information collection fails or for packages that
do not exist. From apport/ui.py:
1036 try:
1037 icthread.exc_raise()
1038 except (IOError, EOFError, zlib.error) as e:
1039 # can happen with broken core dumps
1040 self.report['UnreportableReason'] = '%s\n\n%s' % (
1041 _('This problem report is damaged and cannot be
processed.'),
1042 repr(e))
1043 except ValueError: # package does not exist
1044 self.report['UnreportableReason'] = _('The report
belongs to a package that is not installed.')
1045 except Exception as e:
1046 apport.error(repr(e))
1047 self.report['UnreportableReason'] = _('An error
occurred while attempting to '
1048 'process this
problem report:') + '\n\n' + str(e)
Because an UnreportableReason exists in the report, apport will stop
collecting information. Subsequently, there is "_MarkForUpload" is
left as True (the default) so apport calls mark_report_upload which
creates a .upload file such that the report which is incomplete or
corrupt is then uploaded to the Error Tracker.
In these cases the "_MarkForUpload" key should be set to "False"
thereby preventing uploads to the Error Tracker.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1512902/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1496877] Re: apparmor profile fails to load in Ubuntu 15.04
Hello - This is expected behavior. When a profile requested in the changeprofile operation has not been loaded into the kernel, the write() on /proc/PID/attr/current will fail with errno set to ENOENT. This is documented in the aa_change_profile(2) man page: ENOENT The specified profile does not exist, or is not visible from the current Namespace. ** Changed in: apparmor (Ubuntu) Status: Incomplete => Invalid -- 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/1496877 Title: apparmor profile fails to load in Ubuntu 15.04 Status in apparmor package in Ubuntu: Invalid Bug description: With the latest Ubuntu 15.04 Vivid( Kernel 3.19), I tried to ran the sample program for aa_change_profile from the man page. Whenever I tried to execute the program, it says No such file or directory. I ran strace for this program, whenever aa_change_profile is called, looks like changeprofile is prefixed with profile. Not sure whether it is intended from asprintf called from aa_change_profile strace output write(3, "changeprofile i_cant_be_trusted_"..., 39) = -1 ENOENT (No such file or directory) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1496877/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 762349] Re: Difficult to distinguish which tab is selected
** Changed in: ubuntu-themes Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/762349 Title: Difficult to distinguish which tab is selected Status in Ayatana Design: New Status in Ubuntu theme: In Progress Status in ubuntu-themes package in Ubuntu: In Progress Bug description: Binary package hint: unity In tabbed interfaces such as in gnome-terminal under unity it is difficult to visually distinguish the selected tab from the unselected ones. In the attached screenshot, gnome-terminal has three tabs open, and the third one is selected. If you look close you can see the text is slightly whiter than the other tabs, and the border is a little more prominent but to my old man eyes it's really hard to see it at a glance. Under metacity, the difference is more notable (or at least, the theme is different). My guess is this is a theme issue rather than unity, but I'm unsure. If it is just a theme issue please refile to the right project. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: unity 3.8.8-0ubuntu2 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic-pae 2.6.38.2 Uname: Linux 2.6.38-8-generic-pae i686 Architecture: i386 CompizPlugins: [core,bailer,detection,composite,opengl,decor,mousepoll,vpswitch,regex,animation,snap,expo,move,compiztoolbox,place,grid,gnomecompat,wall,ezoom,workarounds,staticswitcher,resize,fade,scale,session,unityshell] Date: Fri Apr 15 17:41:12 2011 InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110202) ProcEnviron: LANGUAGE=en_US:en PATH=(custom, user) LANG=C SHELL=/bin/bash SourcePackage: unity UpgradeStatus: Upgraded to natty on 2011-04-04 (11 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/762349/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1514531] Re: package python3.4 3.4.3-9ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 139
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that there was an error on your system when trying to install a particular package. Please execute the following command, as it will clear your package cache, in a terminal: sudo apt-get clean Then try performing the update again. This will likely resolve your issue, but the failure could be caused by filesystem or memory corruption. So please also run a fsck on your filesystem(s) and a memory test. Thanks in advance! [This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.] ** Tags added: corrupted-package ** Changed in: python3.4 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3.4 in Ubuntu. https://bugs.launchpad.net/bugs/1514531 Title: package python3.4 3.4.3-9ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 139 Status in python3.4 package in Ubuntu: Invalid Bug description: Upgrade Linux ubuntu 15.04 to 15.10 ProblemType: Package DistroRelease: Ubuntu 15.10 Package: python3.4 3.4.3-9ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-17.21-generic 4.2.3 Uname: Linux 4.2.0-17-generic x86_64 ApportVersion: 2.19.1-0ubuntu4 Architecture: amd64 Date: Mon Nov 9 02:23:24 2015 DuplicateSignature: package:python3.4:3.4.3-9ubuntu1:subprocess installed post-installation script returned error exit status 139 ErrorMessage: subprocess installed post-installation script returned error exit status 139 InstallationDate: Installed on 2015-05-15 (178 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) RelatedPackageVersions: dpkg 1.18.2ubuntu5 apt 1.0.10.2ubuntu1 SourcePackage: python3.4 Title: package python3.4 3.4.3-9ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 139 UpgradeStatus: Upgraded to wily on 2015-11-09 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3.4/+bug/1514531/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1261045] Re: Security bugfix in lxc-sshd template: add ro to the init-script
** Changed in: lxc (Ubuntu Precise) Status: Confirmed => Won't Fix -- 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/1261045 Title: Security bugfix in lxc-sshd template: add ro to the init-script Status in lxc package in Ubuntu: Fix Released Status in lxc source package in Precise: Won't Fix Status in lxc source package in Quantal: Won't Fix Status in lxc source package in Raring: Won't Fix Status in lxc source package in Saucy: Fix Released Status in lxc source package in Trusty: Fix Released Bug description: Being logged in inside a container that was created with the lxc-sshd template the mount of $rootfs/sbin/init allows to modify the init script of the container. So harm could be done to the host system at the next execution of lxc-start or lxc-create -t sshd. This can be used to gain root access since lxc is likely to be run by root. -lxc.mount.entry=@LXCTEMPLATEDIR@/lxc-sshd $rootfs/sbin/init none bind 0 0 +lxc.mount.entry=@LXCTEMPLATEDIR@/lxc-sshd $rootfs/sbin/init none ro,bind 0 0 (see https://github.com/dotcloud/lxc/pull/1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1261045/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1514257] Re: create Persian keyboard
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu-keyboard (Ubuntu) Status: New => Confirmed -- 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/1514257 Title: create Persian keyboard Status in ubuntu-keyboard package in Ubuntu: Confirmed Bug description: There isn't any Persian layout on keyboard layouts. Description: Ubuntu 15.04 Release: 15.04(r282) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyboard/+bug/1514257/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1514556] Re: With occlusion detection, apps stop responding when switching from another app.
** Branch linked: lp:~unity-team/qtmir/revert-occlusion-detection -- 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/1514556 Title: With occlusion detection, apps stop responding when switching from another app. Status in unity8 package in Ubuntu: New Bug description: If you switch from one app to the next, and start scrolling around (eg in dash) very soon after switching, the app will sometimes stop rendering. Reproduce: 1) Start an app (eg dialer) from dash 2) wait a few seconds in dialer. 3) Do a quick switch back to dash, and immediately start scrolling/swiping around. Expected: app behaves normally and responds to user input. Actual: sometimes the dash will stop responding for an undetermined amount of time, or until you interact with another part of the shell. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1514556/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1322067] Re: 3.15.0-1.x breaks lxc-attach for unprivileged containers
** Changed in: lxc (Ubuntu Trusty) Status: Confirmed => Won't Fix -- 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/1322067 Title: 3.15.0-1.x breaks lxc-attach for unprivileged containers Status in lxc package in Ubuntu: Fix Released Status in lxc source package in Trusty: Won't Fix Status in lxc source package in Utopic: Fix Released Bug description: An unprivileged call to lxc-attach fails with kernel 3.15.0.1.2, but works fine using 3.13.0-24-generic. Under 3.15.0.1.2, attempting to connect to a running unprivileged container: $ lxc-attach --clear-env -n trusty -- /bin/true lxc-attach: Permission denied - Could not open /proc/3805/personality lxc-attach: failed to get context of the init process, pid = 3805 Note that lxc-start and lxc-console are not affected. To recreate: 1) Create an unpriv container: $ lxc-create -n utopic -t download -- -d ubuntu -r utopic -a amd64 2) Boot with 3.13.0-24-generic 3) Start the container: $ lxc-start -n utopic 4) Run a command in the container: $ lxc-attach -n utopic --clear-env -n trusty -- /bin/true 5) Reboot into 3.15.0.1.2 and re-run the lxc-start and lxc-attach. 6) Observe the EPERM error. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-generic 3.15.0.1.2 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.2-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: james 2827 F pulseaudio /dev/snd/pcmC1D0p: james 2827 F...m pulseaudio /dev/snd/controlC0: james 2827 F pulseaudio CurrentDesktop: Unity Date: Thu May 22 07:21:55 2014 HibernationDevice: RESUME=UUID=db600bbe-faca-41f4-9338-c3e8e227599a InstallationDate: Installed on 2014-04-11 (40 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Daily amd64 (20140409) MachineType: LENOVO 20AQCTO1WW ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-24-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware 1.129 SourcePackage: linux UpgradeStatus: Upgraded to utopic on 2014-05-08 (13 days ago) dmi.bios.date: 02/10/2014 dmi.bios.vendor: LENOVO dmi.bios.version: GJET71WW (2.21 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AQCTO1WW dmi.board.vendor: LENOVO dmi.board.version: 0B98405 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGJET71WW(2.21):bd02/10/2014:svnLENOVO:pn20AQCTO1WW:pvrThinkPadT440s:rvnLENOVO:rn20AQCTO1WW:rvr0B98405STD:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20AQCTO1WW dmi.product.version: ThinkPad T440s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1322067/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1313796] Re: [No Network] ifupdown/bridge-utils & udev/bridge-utils race condition preventing the addition of non-pre-up ports to a bridge
** Changed in: bridge-utils (Ubuntu)
Assignee: Stéphane Graber (stgraber) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bridge-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1313796
Title:
[No Network] ifupdown/bridge-utils & udev/bridge-utils race condition
preventing the addition of non-pre-up ports to a bridge
Status in bridge-utils package in Ubuntu:
Confirmed
Bug description:
Problem:
I have configured a bridge (br0) between a physical port (eth0) and a
tap device (tap0) using the ifupdown package. About 75% of the time
eth0 fails to be added to br0 during boot, leaving networking
inoperable. This suggests a race condition between ifupdown/bridge-
utils and some other component which I believe to be udev/bridge-
utils.
Layout:
Files involved:
/etc/network/interfaces
/etc/network/if-pre-up.d/bridge
/lib/bridge-utils/bridge-utils.sh
/var/log/upstart/networking.log
/var/log/upstart/network-interface-br0.log
/lib/udev/bridge-network-interface
/lib/udev/rules.d/40-bridge-network-interface.rules
/etc/default/bridge-utils
This rules out conflict between ifupdown's sysvinit and upstart integration:
$ find /etc/rc?.d/ -iname '*network*'
/etc/rc0.d/S35networking
/etc/rc6.d/S35networking
$ find /etc/init* -iname '*network*' | sort
/etc/init.d/networking
/etc/init/networking.conf
/etc/init/network-interface.conf
/etc/init/network-interface-container.conf
/etc/init/network-interface-security.conf
This rules out conflict between ifupdown/bridge-control and other ifupdown
scripts
...:/etc/network$ tree
.
+-- if-down.d
¦ +-- bind9
¦ +-- openvpn
¦ +-- postfix
¦ +-- resolvconf
¦ +-- upstart
¦ +-- wpasupplicant -> ../../wpa_supplicant/ifupdown.sh
+-- if-post-down.d
¦ +-- avahi-daemon -> ../if-up.d/avahi-daemon
¦ +-- bridge -> /lib/bridge-utils/ifupdown.sh
¦ +-- vde2
¦ +-- wireless-tools
¦ +-- wpasupplicant -> ../../wpa_supplicant/ifupdown.sh
+-- if-pre-up.d
¦ +-- bridge -> /lib/bridge-utils/ifupdown.sh
¦ +-- ethtool
¦ +-- vde2
¦ +-- wireless-tools
¦ +-- wpasupplicant -> ../../wpa_supplicant/ifupdown.sh
+-- if-up.d
¦ +-- 000resolvconf
¦ +-- avahi-daemon
¦ +-- bind9
¦ +-- ethtool
¦ +-- ntpdate
¦ +-- openssh-server
¦ +-- openvpn
¦ +-- postfix
¦ +-- upstart
¦ +-- wpasupplicant -> ../../wpa_supplicant/ifupdown.sh
+-- interfaces
+-- interfaces.d
+-- run -> /run/network
Software Versions:
Ubuntu 14.04 LTS
ifupdown 0.7.47.2ubuntu4
bridge-utils 1.5-6ubuntu2
upstart 1.12.1-0ubuntu4
udev 204-5ubuntu20
Logs:
/var/log/upstart/networking.log
Sun Apr 27 17:27:03 2014 TUN/TAP device tap0 opened
Sun Apr 27 17:27:03 2014 Persist state set to: ON
device br0 already exists; can't create bridge with the same name
run-parts: /etc/network/if-pre-up.d/bridge exited with return code 1
Internet Systems Consortium DHCP Client 4.2.4
...
Listening on LPF/br0/46:33:ab:47:a7:05
Sending on LPF/br0/46:33:ab:47:a7:05
Sending on Socket/fallback
DHCPDISCOVER on br0 to 255.255.255.255 port 67 interval 3 (xid=0x5d7de88)
...
<>>
/var/log/upstart/network-interface-br0.log
ifup: interface br0 already configured
My ifupdown configuration:
/etc/init.d/networking
auto lo
iface lo inet loopback
auto eth0
iface eth0 inet manual
auto br0
iface br0 inet dhcp
bridge_ports eth0 tap0
pre-up openvpn --mktun --dev tap0
Demonstrating that "pre-up openvpn --mktun --dev tap0" triggers
/lib/udev/rules.d/40-bridge-network-interface.rules, which in turn runs
/lib/udev/bridge-network-interface:
$ brctl show
bridge name bridge id STP enabled interfaces
br0 8000.000129f5f026 no eth0
$ sudo ip tuntap del mode tap tap0
KERNEL[59526.262768] remove /devices/virtual/net/tap0 (net)
UDEV [59526.263236] remove /devices/virtual/net/tap0 (net)
$ pre-up openvpn --mktun --dev tap0
Mon Apr 28 10:00:32 2014 TUN/TAP device tap0 opened
Mon Apr 28 10:00:32 2014 Persist state set to: ON
KERNEL[59622.299324] add /devices/virtual/net/tap0 (net)
UDEV [59622.323388] add /devices/virtual/net/tap0 (net)
$ brctl show
bridge name bridge id STP enabled interfaces
br0 8000.000129f5f026 no eth0
tap0
Confirming the problem:
By default, BRIDGE_HOTPLUG=yes in /etc/default/bridge-utils. Once disabled,
however, both interfaces (eth0, tap0) are consistently added to br0 during
boot, tested across five reboots.
Note that this resolves the problem and the errors logged to
/var/log/upstart/networking.log ("device br0 already exists; can't
create
[Touch-packages] [Bug 1392297] Re: resolvconf 1.69ubuntu1.1 breaks network install
** Changed in: resolvconf (Ubuntu) Assignee: Stéphane Graber (stgraber) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to resolvconf in Ubuntu. https://bugs.launchpad.net/bugs/1392297 Title: resolvconf 1.69ubuntu1.1 breaks network install Status in resolvconf package in Ubuntu: Incomplete Bug description: We are experiencing problems with Ubuntu 14.04 network installations, when using the 1.69ubuntu1.1 version of resolvconf. With this version the file /etc/resolv.conf gets reset to an empty file (does only include just the standard resolvconf comments) during the installation of the resolvconf package. After that the name resolution doesn't work anymore and the subsequent installation steps fail. If we use the 1.69ubuntu1 version, everything works fine. If I make a diff of both package contents, the most significant change seems to be the inclusion of a new Sys-V init script, which (besides other things) removes the contents of the resolvconf runtime directories when called with the option "start", and the postinst script calls "invoke-rc.d resolvconf start" at the end (included by dh_installinit), which I think should do nothing during the installation because of policy-rc.d (right?), but I wonder if it actually get's called and removes the resolv.conf file that got migrated to the runtime directories earlier in the postinst script. At least that would explain our problems, because I don't really see anything else, that could cause this problem. I see that the inclusion of the new init script is coming from debian, and they call the dh_installinit with the option "--no-start" in debian/rules, while the Ubuntu package calls the dh_installinit only with the option "-r". And debian inserts the debhelper code a lot earlier in the postinst script. Could this be what's causing the problem? As soon I have more time, I will try to debug this further and provide more information. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1392297/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1396153] Re: devel alias should point to vivid
a tad outdated ** Changed in: system-image (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to system-image in Ubuntu. https://bugs.launchpad.net/bugs/1396153 Title: devel alias should point to vivid Status in system-image package in Ubuntu: Invalid Bug description: devel currently is ubuntu-touch-utopic which is not even a live channel devel should alias ubuntu-touch/vivid devel-proposed is an alias to ubuntu-touch/vivid-proposed We'd like this clarified as we update documents and training for developers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/system-image/+bug/1396153/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1347020] Re: systemd does not boot in a container
Fixed through trusty-backports. ** Changed in: lxc (Ubuntu Trusty) Status: Triaged => Fix Released -- 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/1347020 Title: systemd does not boot in a container Status in lxc package in Ubuntu: Fix Released Status in lxc source package in Trusty: Fix Released Bug description: Opening against cloud-init for now, but ultimately might end up as bug-fixes / srus against some other packages in trusty. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1347020/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1237041] Re: Networking crashes all other ubuntu components on start / stop
** Changed in: ifupdown (Ubuntu) Assignee: Stéphane Graber (stgraber) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1237041 Title: Networking crashes all other ubuntu components on start / stop Status in ifupdown package in Ubuntu: New Bug description: While running the command sudo service networking start / stop all other ubuntu components namely launch screen ... gets terminated ... Info: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Ubuntu 13.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center 3) What you expected to happen Network to be restarted for fixed line 4) What happened instead Everything except the current command line disappeared i had to re- install whole ubuntu base system. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1237041/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1229409] Re: Should unmount real filesystems once all loop-mounted filesystems are unmounted
** Changed in: lxc-android-config (Ubuntu) Assignee: Stéphane Graber (stgraber) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc-android-config in Ubuntu. https://bugs.launchpad.net/bugs/1229409 Title: Should unmount real filesystems once all loop-mounted filesystems are unmounted Status in lxc-android-config package in Ubuntu: New Bug description: Hi, I'm sometimes getting what appears to be filesystem corruption when I mount -o remount,rw + apt-get install stuff + immediately reboot. I suspect this could similary affect user data in /home. I'm rebooting cleanly with shutdown -r now or reboot, so either software drivers / hardware is doing the sync wrong, or we're not unmounting the loop-mounted fses correctly. Since I don't think we have any code to unmount the loop-mounted filesystems I'm assuming the latter and filing this here where we could fix it. It would also be good to ensure we have "sync"s in place after applying a system-update. Cheers, To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc-android-config/+bug/1229409/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
